Basically a conditional repeating command block is triggering twice when it should only trigger once.
What I expected to happen:
I thought when I ran the device in picture one the conditional repeating command block and it's following line would only run once, because the beginning impulse block is no longer true before the device runs the second time.
What actually happened:
The conditional repeating block (and the chain blocks following it) runs twice even when the impulse command block before it (see picture 1) is untrue before it runs the second time.
Steps to reproduce:
1. Run /scoreboard objectives add twice dummy
2. Run /scoreboard objectives setdisplay sidebar twice
3. Copy the command block setup in the picture
4. Click the button
5. Observe the order of the commands in the chat log (you should see that the commands got run twice even after the impulse block was no longer successful)
Linked issues
is duplicated by 3
Attachments
Comments 6
If the command block execution is scheduled to happen "next tick", why does it make a difference what command block "stops" the repeating? (See MC-97060 for detail)
I find this behaviour really annoying!
The execution of the command that "stops" the loop should definately run before the next iteration is queued.
Imagine if breaking out of a loop in java would let one extra iteration pass through.
Can you flag this for review?
Command block execution is scheduled to happen "next tick", not immediately