mojira.dev
MC-48373

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

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.

Linked issues

Attachments

Comments 13

Is this still a concern in the current Minecraft version 14w30c or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Note that it is the cloning of the powered Repeater that is causing the re-trigger. See MC-99916 for details.
The repeater is cloned along with its powered status, but the delay timer is re-started so that its output is unpowered immediately after cloning and is powered again after the delay.
MC-99916 also has details of problems caused by cloning a button while it is pressed (the clone of the button stays pressed indefinitely)

@Kevin Taylor: In the reproduction steps, the repeater is not included in the clone source region; only the command block that is cloned, and three air blocks near it.

3 more comments

That the button stays pressed is already reported before, if I'm not mistaken.

That a button stays pressed after cloning has not been reported before, that I can find.
Only MC-53463, which is marked "cannot reproduce" and does not mention cloning.

Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.

This is an automated comment on any open or reopened issue with out-of-date affected versions.

Is this still an issue in the most recent versions (currently that is 1.11) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.

Thank you for your report!
We're tracking this issue in MC-155690, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit

Saposhiente

(Unassigned)

Unconfirmed

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

Retrieved