[MC-11309] Piston bug! wrong update mechanism - BUD Created: 08/Mar/13  Updated: 06/May/15  Resolved: 26/Nov/13

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

Type: Bug
Reporter: Stephan Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: BUD, piston, redstone
Environment:

Mac OSX


Attachments: Zip Archive Bug.zip     File Bugreport.m4v    
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

The update mechanism of pistons are broken since 13w09b. I tested an elevator design from 1.4.7 in all snapshots and now its broken. The design was based on a perfect timing and logic. In the Video I show you the Problem exactly. I think the reason is the changed updating mechanism of pistons. The BUD-powered Sticky fires first, not the normal piston. And thats the bug. Actually the directly powered normal piston should fire first! ... please fix this!



 Comments   
Comment by Tails [ 26/Nov/13 ]

No answer, assuming no longer an issue.

Comment by Tails [ 29/Jul/13 ]

Is this still a concern in the current Minecraft version 1.6.2 / Launcher version 1.1.3 ? 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 Stephan [ 08/Mar/13 ]

I added the world file.

Comment by Stephan [ 08/Mar/13 ]

Jeah they changed the way pistons are updating. BUT its illogical that a BUD-powered piston is preferred. The normal piston is powered directly, so this one should extend first. Like it was before. Im very sad about that bug Because it took ages to invent this thing and as i said it is based on a perfectly calculated timing difference...

Comment by Sebastien Caisse [ 08/Mar/13 ]

Also check MC-11193, it might be similar

Comment by Miha [ 08/Mar/13 ]

They said that they changed the way pistons update and that it might break BUD-s, so i think this is not a bug.

Comment by Anonymous User [ 08/Mar/13 ]

Can you zip up the world file and upload it? Also, maybe they fixed that bug in the 1.5 prerelease

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