[MC-8167] Weird pulse behaviour. Created: 23/Jan/13  Updated: 07/Feb/15  Resolved: 17/Mar/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w03a, Snapshot 13w04a
Fix Version/s: None

Type: Bug
Reporter: SewdiO Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None

Attachments: PNG File 2013-01-23_22.44.01.png     PNG File 2013-01-23_22.44.25.png     PNG File 2013-01-23_22.44.47.png     PNG File 2013-01-23_22.45.01.png     PNG File 2013-01-23_22.45.12.png     PNG File 2013-01-23_22.45.20.png     PNG File 2013-01-23_22.45.24.png     PNG File 2013-01-23_22.45.54.png    
Confirmation Status: Unconfirmed

 Description   

A serial data transfer gone wrong. See this to understand the mechanism (at least the recepter) : http://www.youtube.com/watch?v=gqryvkOpOJ0 (properinglish19)

What I expected to happen was...:
A inverted one tick pulse "unBUDs" a piston, updated by a comparator. Said piston retracts, depowering the redstone piece below the attached redstone block. The torch on the redstone piece's block then activates after a tick, powering the block above back to it's source wich in turn deactivate the torch one tick after, and before it can repeat the redstone block is pushed back in place.
There's a serie of these, one tick apart.

The data line then feeds into the recepters as shown in the video above (only the timings and emeters are different).

What actually happened was...:
When placing the first 6 redstone blocks (the upper ones to prevent a pulse and write a 0) from right to left as shown in screenshots, the fifth bit is made a 1 in place of a 0. Place a redstone block in 6th bit and the 5th is a 0 again.

Steps to reproduce:
Screenshots should hopefully be enough to reproduce it. Don't mess up the timing, it's important.



 Comments   
Comment by Tails [ 17/Mar/13 ]

No answer on querry, assuming no longer an issue.

Comment by Tails [ 04/Mar/13 ]

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.

Comment by SewdiO [ 27/Jan/13 ]

It looks like the bug happens at the piston level, it may be because of the <1 tick pulse it receive.
http://imgur.com/T8bYBYz

Comment by SewdiO [ 27/Jan/13 ]

Still there as of 13w04a

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