The bug
When a line of redstone dust updates and does not / points at a block, the block is not updated under certain circumstances. (redstone redirection)
Affected situations
Block connecting to redstone dust is placed. This includes all blocks that connect to redstone dust (like repeaters, levers...) without creating a redstone signal, see
Redstone dust which was blocked before connects, see
Redstone dust connecting downwards from glowstone (see
), slabs, hoppers, redstone blocks (see also MC-123850)
Related issues
is duplicated by
MC-11113
Deviation redstone
MC-13045
Redstone Torch BUD
MC-17241
Placing a comparator doesnt update the torch.
MC-27238
Redstone Lamp Not Powered Correctly
MC-41318
Redstone torch is on, even though it's receiving power
MC-44459
Redstone doesn't power when a block changes its direction.
MC-55870
Redstone-Torch doesn't update
MC-92678
Repeater BUDdiness
MC-93296
Redstone Torch does not update to signal
MC-94405
when i first power the lamp then piston -which cuts the line- it does not update
MC-96769
Redstone
MC-108637
Redstone torch not update properly
MC-119603
Redstone connectivity doesn't properly update redstone lamps
MC-120975
Redstone components don't update when redstone redirects on a transparent block
MC-132819
Weird redstone behavior with slabs
MC-152225
Redstone not correctly updating Torch
MC-176773
Redstone not properly updating on redirection
MC-181690
Redstone line does not update after removing the target block
MC-184022
Redstone repeater won't be powered after redirecting redstone wire
MC-184639
Redstone does not fully update from being a dotted form to a crossed form when it's state is changed by non-players
MC-184659
Redstone line being bugged when indirectly changed from redstone dot
MC-184706
piston and probably other redstone blocks arent powered by a redstone signal when using two redstone torches
MC-189307
moving target block such that redstone wire changes does not update block
MC-206729
Inconsistency with block updates when rewiring redstone dust
MC-211392
repeat command block gets powered by diverted redstone
MC-216671
Blocking a vertical connection of redstone dust does not update the components it's powering
MC-238144
Repeater Not Activating and Deactivating
MC-263408
Redstone dust behavior change?
relates to
Attachments
Comments
migrated
Still in 13w01b.
Could not reproduce in 13w09b.
Reproduced in 13w09b: A little "random BUD-Flop" as seen in the screenshot. Observe how the torch is off eventhough no wire is connected. (the randomness comes from the fact that the torch receives updates randomly)
Hmmm. This looks too stable and consistent to be a BUD... at first glance.
I toggle the switch - torch goes off - piston retracts - redstone orientation changes - torch magically stays depowered. Then I toggle the switch again - torch magically regains power - piston extends - redstone reorientates to correct state. I get this 100% of the time, but when left alone for some time in this magic state, torch updates itself and piston performs a cycle. Such a funny device...
The pistonless setup on the first screenshot works as expected to me though.
With "detector rails" also works, alias, you can move the rails with pistons without breaking, that is also a bug?
Still here in snapshot 14w02c ...
marcono1234
*Confirmed for 14w21b
No, Tails' device still exploits this bug like it ever did.
14w33a - not fixed
Yes. Tails' device behaves just as in description.
galaxy_2alex
Reopened, Thanks.
Still happens in 1.8.3
marcono1234
Confirmed for
15w39c
Gave the ticket to Marcono1234.
Still happens in Minecraft 1.12, i think
It seems that technical users find this behavior to be extremely useful, while pretty much nobody finds it to be harmful. BUDs weren't initially intended, but it's one of those "emergent behaviors" that even Mojang developers have acknowledged it as being generally productive and desirable, even if some less experienced uses may initially find it to be unintuitive. Intuitive behavior is always a good objective, but we can see how trying to make redstone more intuitive has basically made it broken and useless in Bedrock edition, while at the same time introducing even uglier bugs and even more nondeterminism.
If you want to see an example of productive use of this feature, check out this video: https://www.youtube.com/watch?v=vMYygzMYUs4&feature=youtu.be
I suggest marking this but as "works as intended" or "won't fix," because of all the frustration "fixing" it would cause.
Any further discussion, we can move to /r/mojira or the EigenCraft discord.
Thanks.
[Mod] Neko
Just because a bug is useful to technical users does not justify calling it a feature or leaving it as is.
NeunEinser
Can confirm for 1.13-pre3
Artimipa
Confirmed for 20w18a.
Artimipa
Confirmed for 20w19a.
Artimipa
Confirmed for 20w20b.
ampolive
Can confirm in 1.17.1.
BeeTeeKay
Affects 1.21