[MC-50187] redstone updates inconsistent based on location

I have encountered redstone issues where the specific location of the redstone circuit will effect how it works. This is most visible when using command blocks that change the area they are near, as the exact execution order can have clear effect. For instance, if you have 3 command blocks in a row, and they are all powered simultanously with a redstone signal, sometimes they will execute in sequence, and sometimes they will execute out of sequence. This seems to be deterministic based on where it is built.

I have attached a world where this behavior can be seen. You are standing on a platform with a level. When the lever is toggled, the platform will move one block forward, resulting in an identical copy of the current configuration in a different location, as well as teleporting the player forward. . You start with the lever at -10, 118 -111, and until it gets to -5 118 -111 it works, but when the lever is pulled at that location, the copy messes up

Related issues

duplicates

MC-11193 The order in which powerable blocks (e.g. redstone dust blocks) along a wire are powered or de-powered is not clearly defined and causes a non-deterministic behavior for redstone contraptions

Attachments

Clock Bug.rar

Copy of creative 1_8.rar

Comments

migrated 2014-03-05T15:00:08Z

[media][media]

migrated 2014-03-27T23:31:32Z

I'm having the exact same issue. I have a clock and command block combo which adds scoreboard objectives until it counts to 97 which causes the device to stop at 100 due to how it is designed. In certain locations it will count to 100 as expected and in others it will count to 102. Putting it in an identical position but in another chunk, can also result in the behaviour changing. I'll add a copy of the world.

I'm having this in 14w11b.

marcono1234 2014-05-31T15:48:52Z

Maybe relates to: MC-11193

galaxy_2alex 2014-10-31T10:07:04Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.

migrated 2015-03-06T07:11:28Z

Confirmed in 1.8.3. I think it's just a dupe of MC-11193.