[MC-9714] Cut redstone doesn't de-power for one tick Created: 13/Feb/13  Updated: 05/Feb/24

Status: Reopened
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w05b, Snapshot 13w06a, Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Snapshot 13w18c, Snapshot 13w19a, Minecraft 1.8.1-pre3, Minecraft 1.8.8, Minecraft 15w49b, Minecraft 1.9.4, Minecraft 1.10.2, Minecraft 16w32b, Minecraft 16w44a, Minecraft 1.11 Pre-Release 1, Minecraft 1.11, Minecraft 16w50a, Minecraft 1.11.1, Minecraft 1.11.2, Minecraft 17w06a, Minecraft 17w13b, Minecraft 17w15a, Minecraft 17w16b, Minecraft 17w17b, Minecraft 17w18b, Minecraft 1.12 Pre-Release 2, 20w07a, 1.16.1, 1.16.2 Pre-release 1, 1.16.2 Pre-release 2, 1.16.2 Release Candidate 1, 1.16.2, 20w51a, 1.17.1 Release Candidate 1, 1.17.1, 1.20.4, 24w05b
Fix Version/s: None

Type: Bug
Reporter: Topher Donovan Assignee: Unassigned
Resolution: Unresolved Votes: 19
Labels: redstone

Attachments: PNG File 2013-05-20_17.43.26.png     PNG File Bildschirmfoto 2020-02-15 um 18.16.19.png     PNG File MC-9714.png     PNG File off.png     PNG File on.png    
Issue Links:
Duplicate
is duplicated by MC-114311 Commandblock triggers false Resolved
Relates
relates to MC-8328 Powered mechanisms react when receivi... Reopened
relates to MC-157644 Extended block updates do not propaga... Resolved
relates to MC-11193 The order in which powerable blocks (... Open
CHK:
Confirmation Status: Confirmed
Category:
Redstone
Mojang Priority: Low
Area: Platform

 Description   

When cutting/breaking redstone wire, the portion of the wire that is no longer connected to the power source remains powered even though the line has been cut.

http://www.youtube.com/watch?v=5UNpLokCduo

Narrative:

http://www.youtube.com/watch?v=Jk1rp8FmJN8



 Comments   
Comment by [Mod] ampolive [ 04/Jul/21 ]

Can confirm in 1.17.1 Release Candidate 1.

Comment by [Mod] Avoma [ 14/Jan/21 ]

Can confirm in 20w51a.

Comment by [Mod] redstonehelper [ 15/Feb/20 ]

Can still reproduce in 20w07a. Attaching screenshot.

Comment by [Mod] Greymagic27 [ 15/Feb/20 ]

I can't reproduce this in 20w07a, there's a tiny black flicker of the redstone indicating that power has been cut.

Comment by [Mod] NeunEinser [ 06/Oct/17 ]

If it was a game tick, a piston would react to the signal if you placed it where the repeater is (and remove the block below). It does not react. It is true, that pistons usually react to 0 ticks, that kind of 0 tick is however even too short for a piston to react.

Comment by user-f2760 (Inactive) [ 06/Oct/17 ]

It is correct in the sense of game ticks.

Marking as related instead.

Comment by [Mod] NeunEinser [ 06/Oct/17 ]

Okay reviewing the ticket, from the screenshots:

It is not true that the redstone dust stays on for one game tick. The repeater will update, but it is actually a 0 tick. So this issue should be marked as Dupe of MC-8328.

Comment by [Mod] NeunEinser [ 23/Jul/17 ]

I just tested the bug with the simple design of the two high smart piston from the video. In the current version, 1.12, it is not the case anymore, that the redstone dust doesn't get unpowered.
It is true, that the two high smart piston does not work in that way anymore, but that is not because the redstone dust doesn't get unpowered, it's because the off pulse is too short for the torch to react. If you attach a dropper directly to the output, it will fire.
So while the behavior compared to 1.4 obviously changed I do not think, this should be considered a bug. The redstone wire changes state as expected and I assume that the created pulse is actually a 0 tick pulse which means, it is too short for even a 1 tick repeater to react.

An alternative design that works similar can be seen here: MC-9714.png

Comment by Topher Donovan [ 20/Dec/16 ]

disregarding my comments from before, I wonder how fixing this bug would speed up some redstone contraptions?? hmmm....

Comment by SunCat [ 14/May/16 ]

Still in 1.9.4 ("on" and "off" screenshots, same contraption but in different directions/mirrored, diamond blocks moved, gold blocks didn't)

Comment by bob [ 06/Dec/15 ]

This is a bit like quasi connectivity IMO as it is useful for pulse limiters.

Comment by Topher Donovan [ 06/Dec/15 ]

Still an issue. It last worked in release 1.4.7, Has been broken since 1.5.0.

But it's nearly been three years, so what's the point of fixing it? Everyone's already gotten used to this particular redstone mechanic, so fixing it would probably create even more tickets

Comment by Galaxy_2Alex [ 25/Oct/14 ]

Reopened, thanks. It's still an issue nontheless.

Comment by Topher Donovan [ 25/Oct/14 ]

Sorry, For some reason, I didn't see the updates in my email. I just tested it and it is still present in 1.8.1-pre3, but since the rest of the redstone community isn't complaining about it, perhaps it just isn't something that's supposed to be fixed.

Comment by Tails [ 20/May/13 ]

Confirmed with the setup and orientation seen in the screenshot.

Comment by Topher Donovan [ 18/Mar/13 ]

Yes, the error is still present in 1.5

Comment by Topher Donovan [ 02/Mar/13 ]

Dear Dico Karssiens, This is NOT a pre-existing bug and I can prove it.

http://www.youtube.com/watch?v=Jk1rp8FmJN8

This video illustrates the difference between the redstone getting cut in 1.4.7 and the pre-releases of 13w0x. Something has indeed changed and it has to be looked at. I'm sure that this is not the only use case where powered redstone getting cut needs to be consistent.

Also, if you watch the video, there is NO repeater in this setup. it's very simple.

Comment by DicoTheRedstoner [ 25/Feb/13 ]

Its actually not the redstone not getting de-powered for 1 tick.
Its just the repeater taking a signal from it.
If you set this up with 2 repeaters coming from the block
in each orientation, you will see that some do take a signal and some dont.
So its not the dust's fault, its the repeater's fault.

Comment by Topher Donovan [ 24/Feb/13 ]

Just to be super explicit about it, The cut wire DOES eventually de power, but shouldn't it de-power immediately, not wait a tick or two?

Comment by Topher Donovan [ 14/Feb/13 ]

This now happens in all directions. I built a 30 second timer that required the redstone to cut properly, but since 13w0x, it doesn't work./

Images won't do it justice, I uploaded a video in the description which illustrates the error. And the piston/wire in the video is from one of my other videos where I show it working properly.

Comment by Kumasasa [ 13/Feb/13 ]

Please attach the images to that ticket.

Comment by DicoTheRedstoner [ 13/Feb/13 ]

An orientational shift register relied on this. Here's a setup to easily see what happens (in 1 of 2 orientations):
Setup: https://www.dropbox.com/s/cd5aag78gz556rm/2013-02-13_23.18.16.png
When powered: https://www.dropbox.com/s/3djwzq1q131bvfp/2013-02-13_23.18.04.png?m

Comment by DicoTheRedstoner [ 13/Feb/13 ]

I've seen this for a long time, it only happens in 1 orientation.

Comment by Topher Donovan [ 13/Feb/13 ]

Stays powered for about 1 tick, causing multi-leveled smart-pistons to fail.

Generated at Sun Jan 12 12:22:00 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.