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

Under specific circumstances, cloning a command block while running it causes it to run twice

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 14w06b, Minecraft 14w11b, Minecraft 14w30c, Minecraft 1.9.2, Minecraft 1.9.3 Pre-Release 3, Minecraft 1.9.3, Minecraft 1.9.4, Minecraft 16w20a
    • None
    • Windows 7, Java 7
    • Unconfirmed

      Under specific circumstances, cloning a command block while running it causes it to run twice.
      How to reproduce:
      1. Face towards positive Z (Bug occurs in multiple orientations, but the command to cause it is orientation specific)
      2. Place a command block, and enter the command "/say bug" (or another command to be run twice)
      3. Place another command block adjacent to it and between it and you (1 block towards negative Z), and enter the command "/clone ~ ~ ~1 ~1 ~ ~2 ~3 ~ ~1"
      4. Again moving 1 block towards negative Z, place a redstone repeater facing the /clone command block
      5. Again moving 1 block towards negative Z, place a redstone torch or other power source. "[@] bug" will be displayed twice, instead of the expected once.
      Observations:
      Clone source region has to include 1 block to the left (+X from this perspective) and 1 block behind (+Z from this perspective) the target command block. Including 1 block to the right or 1 block in front of the target does not cause the bug on its own. Clone target region makes no difference.
      Replacing the repeater with redstone dust prevents this bug (displayed only once)
      Bug still occurs if the two command blocks are separated by redstone dust, as long as the clone source region is adjusted accordingly.

            Unassigned Unassigned
            Saposhiente Saposhiente
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: