Minecraft Execute command block, Redstone signal from comparator too weak (Minecraft Execute command block, redstone signal from comparator too weak)?
-------------------------------
English
Hey
I'm currently working on a new multi-player Minecraft adventure map.
In one part of the map, all players have to reach a certain point on the map on many specified ways.
Every player has their own parkour etc.
If everyone has arrived at one exact destination, they should be teleported to the next part of the map.
The command I use for this is:
/ execute if entity @a [distance =. 10]
As is known, this tests how many players are within the specified radius.
And now I have a problem.
No matter how many players are within this radius, there's only a one-block redstone signal from the command block (or the comparator), which then does not power the remaining 3 command blocks.
As a clarification:
I stand here with my 2nd Acc in the specified radius.
And no matter how many players would still be here, the other 3 will not be powered.
I hope that someone can help me here.
I've tried a lot, but so far nothing has really worked.
LG
~ Max
------------------------------------------
German:
Hey
I'm currently working on a new multi-player Minecraft adventure map.
In one part, e.g. Then create all 4 players by 4 different ways to a certain goal.
If everyone has arrived at their destination, they should be teleported to the next part of the map.
The command I use for this is:
/ execute if entity @a [distance = .10]
As is known, this tests how many players are within the specified radius.
There's now a problem with this.
No matter how many players are within this radius, there's only one red block signal from the command block (or the comparator), which then does not power the remaining 3 command blocks.
Here as a clarification.
I stand here with my 2nd Acc in the specified radius.
And no matter how many players would still be here, the other 3 will not be powered.
I hope that someone can help me here.
I've tried a lot, but so far nothing has really worked.
In contrast to the old "/ testfor", the new "/ execute if entity" command does not count how many entities there are. It only checks whether there are one or more entities.
So you can forget it in your case.
To count the number of players you would need to use a scoreboard. For example, you could do that
execute as @a [distance = .10] run scoreboard add… 1 (no longer knows how to increase a scoreboard by 1 but this is easy to google)
execute. So you add 1 to the scoreboard for each player nearby. And if it is 4 then there are 4 players, if not then you set it back to 0 and do it again.
