Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-160298

Conditional Command Blocks continue to run, even after the command block before it stops running



    • Type: Bug
    • Status: Resolved
    • Resolution: Invalid
    • Affects Version/s: 1.14.4, 19w34a, 19w35a
    • Fix Version/s: None
    • Environment:
      Windows 10
      Java 8 Update 221
      6x Intel i5-9600k 3.70GHz
      Nvidia RTX 2070
      32 GB DDR4 RAM
    • Confirmation Status:
    • Game Mode:
    • Category:


      https://youtu.be/Y1iEmcixiQk <-- Example for the bug

      This bug actually affects everything from 1.12 and up, the "Affected Versions" wouldn't let me select those, but this bug has existed for a while now.

      Whenever designing a command block chain with sections of conditional command blocks, the conditional command blocks will break out of the "conditional" state and start running every tick, even when the block before it isn't running.

      For example, this command chain was used as a test:
      1. execute as @p at @p if block ~ ~-1 ~ bedrock run particle minecraft:bubble ~ ~ ~ 0 0 0 0 1 normal
      Repeating command block
      2. setblock ~ ~1 ~1 redstone_block replace
      Chain command block set to conditional and always active
      3. tp @p ~1 ~ ~
      Chain set to unconditional and needs redstone

      4. say This should only display once.
      Chain set to conditional and always active

      5. setblock ~ ~1 ~-2 glass replace
      Chain set to unconditional and always active

      So the expected result of this would be the words "This should only display once" should be pasted in chat whenever the nearest person stands on bedrock, and in 1.9-1.11.2, it functions exactly that way; however, in 1.12 and up, the 2nd conditional block continues to run even after the previous command is no longer running, seemingly "breaking" the conditional state.
      In the 1.12 changelog, there was this posted:
      "Now executes all of the commands in a chain before scheduling them for the next tick "
      However, I do not understand how that change would cause this change in behavior




            Unassigned Unassigned
            Pichu2002 Samuel Glass
            0 Vote for this issue
            2 Start watching this issue