When you (un)power a torch with a 2-tick pulse (here and from now on I mean redstone ticks), it turns off/on for 2 ticks as expected.
But if in the same tick you update the torch and then (un)power it, it produces only a 1-tick pulse (so they won't unpower 2-tick repeaters or (un)power other redstone torches).
This can be reproduced in multiple ways (all pistons in the screenshots are sticky):
Updating with other torches (see
torches-#.png
: only 1 repeater will be unpowered)Updating with redstone (see
redstone-#.png
andold-fixed.png
: repeater/torch to the right won't unpower)Updating with a repeater (see
torch-repeater.png
: repeater to the right won't unpower)
All setups (beside
old-fixed.png
) show the issue with powering the torch; for unpowering you can just invert the input signal and use torches to see the bug (seeinverted.png
)
Linked issues
is duplicated by 17
relates to 3
Attachments
Comments 34
The first 1.5 snapshot seems to have slightly affected this behavior, but still not fixed it. Torches still don't respond to short pulses in an expected way.
Well that doesn't have with this glitch to do.
It's still not completely fixed in the 1.5 snapshot, if you have two output torches one of them will give a 1 tick pulse, the other a 2 tick one.
Updated the description 🙂
This bug is back in snapshot 13w06a. Can a mod or someone reopen maybe?
Reopened.
@unknown Bugposts must not be ( ab ) used for discussion, but I can tell you really care for Redstone in Minecraft, so I hope the moderators won't scold me too much for replying to you 🙂 It may also clear similar concerns/worries or anger reasons for whoever may run into this bugpost in the future.
If you follow Panda's channel you hopefully also saw this video here: https://www.youtube.com/watch?v=NnkSSs-I8XM where he explained why it is not so easy to implement a change (if not, watch the video, listen closely).
"It's impossible to fix old problems without also breaking some old behaviour."
For such substantial changes, Mojang needs to overhaul the complete Redstone system, not only a single part.
This would be better to be done in a gigantic future overhaul which might break many, if not most, contraptions, but that's better than having "bit by bit" changes, so the tech community wouldn't have to adapt with every new MC version that comes out and gets upset even more (which we could see happening during the 1.11 snapshots with several changes to Redstone components, as sadly many people treat snapshot versions like release versions, but with the latter the reactions would probably be even worse).
I like to compare it with the Minecraft boats: They never really fixed boats, they implemented new ones.
Let me just assure you that the Java-Devs are not ignoring this problem, you don't know what some of them are working on behind the scenes, unbeknownst to the public, so please don't make such assumptions without knowing it with a 100% certainty from the Java-Devs themselves 🙂
It might take a while until we might see a future totally new Redstone system with less lag and more logic, and maybe also new components even, but, given the current state of the code, plus other implementations that have to be done beforehand (e.g. also such a seemingly unrelated thing like "unlimited" block IDs), this is not an easy task.
From the current path Minecraft seems to go generally, I'm just relieved the Java-version seems to still render enough money to be supported and updated at all by Mojang, which they are (technically) not obliged to, and that they didn't change the Redstone system completely to be like the PE/WIN10-version, although Mojang always said they want feature parity.. but we still got e.g. Quasi-Connectivity in Java-MC which does not (and surely never will, as it's considered a bug) exist in PE-/WIN10-MC, but which maybe might not be in Java-MC anymore, once the Redstone system would be completely overhauled.
A loss of QC might make the majority of Java-Redstone community go "berserk", unless Mojang would introduce new shiny elements in the future Redstone system, so the Java-Redstone community could live with that possible loss of QC at that time, and that means they need a bigger amount of time to create a "perfect" overhauled, improved Redstone system that also somewhat got feature parity to other Minecraft platforms, if that's what they're going to do with Java-MC.
We'll see, I'm curious about it myself!
I can only ask you to be patient and hope for the best 😉
I got a bit confused that MC-32296 got marked as a duplicate of this one.
After reading the comments I understood, that they are just different manifestations of the same issue.
Still I would like to suggest changing the description of this issue to contain a short notice about 1-tick unpowering of repeaters being affected too.
Can confirm for 17w43a/b
And once more.
Looks like this is fixed in the lastest 18w1 snapshot, thanks to Gnembon and Grum!
A annoying, and reproducable issue, luckily, couple lines of code, and It's le fix!