MG127
- MG127
- mg127
- Europe/Stockholm
- Yes
- No
MC-15616
looks very similar to my problem: http://youtu.be/Q-AOr8dD2F4?t=29s
as you can see in this video: http://youtu.be/Q-AOr8dD2F4?t=29s
there is still a bug with retracting double-extenders.
while exploring a bug on bukkit, i found another one that was in vanilla too. even if no one uses this timings for a doubleextender, it is still a bug. at least it is consistent for each piston and not random.configuration: the clock used for this is 8*1 tick long, 4 tick-repeater to a block, 2x1 tick repeater to bottom row of pistons, redstone-torch + 2 and 4 tick repeater to the top row of pistons, each piston has also a block to retract ontop.
as you can see in this video: http://youtu.be/Q-AOr8dD2F4?t=29s
there is still a bug with retracting double-extenders.
while exploring a bug on bukkit, i found another one that was in vanilla too. even if no one uses this timings for a doubleextender, it is still a bug.at leastit is consistent for each piston and not random.configuration: the clock used for this is 8*1 tick long, 4 tick-repeater to a block, 2x1 tick repeater to bottom row of pistons, redstone-torch + 2 and 4 tick repeater to the top row of pistons, each piston has also a block to retract ontop.
as you can see in this video: http://youtu.be/Q-AOr8dD2F4?t=29s
there is still a bug with retracting double-extenders.
while exploring a bug on bukkit, i found another one that was in vanilla too. even if no one uses this timings for a doubleextender, it is still a bug. it is consistent for each piston, als long as you don't change the redstone-current-strength.configuration: the clock used for this is 8*1 tick long, 4 tick-repeater to a block, 2x1 tick repeater to bottom row of pistons, redstone-torch + 2 and 4 tick repeater to the top row of pistons, each piston has also a block to retract ontop.
is fixed with 1.6.2, thx!
Important: this bug is constent though all pistons/locations unlike this bug
Important: this bug is constent though all pistons/locations unlike this bug
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.
when you don't place a block ontop the double-extender it should behave the same like a single piston with a block above, but it pulses somehow buggy (video following)
Pistons pushing other pistonsisdifferend from pushing normal blocksPistons pushing other pistons bahave differend from pushing normal blocks
Pistons pushing other pistons bahave differendfrom pushing normal blocksPistons pushing other pistons bahave different from pushing normal blocks
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.
when you don't place a block ontop the double-extender it should behave the same like a single piston with a block above, but it pulses somehowbuggy (video following)Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.
when you don't place a block ontop the double-extender it should behave the same like a single piston with a block above, but it pulses somehow different (lower piston pushes upper piston intsantly and is extended twice each cycle
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.
when you don't place a block ontop the double-extender it should behave the same like a single piston with a block above, but it pulses somehow different (lower piston pushes upper piston intsantly and is extended twice each cycle)
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.
when you don't place a block ontop the double-extender it should behave the same like a single piston with a block above, but it pulses somehow different (lower piston pushes upper piston intsantly and is extended twice each cycle) and it shouldn't be different if you place a block ontop the double-extender
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.
when you don't place a block ontop the double-extender it should behave the same like a single piston with a block above, but it pulses somehow different (lower piston pushes upper piston intsantly and is extended twice each cycle) and it shouldn't be different if you place a block ontop the double-extenderImportant: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.edit: i thought about it a while and i came to the conclusion that the different behavior is, because the BUD-effect caused by the upper piston. but the fast movement is still abnormal.
Pistons pushing other pistons bahave different from pushing normal blocksPiston timing (instant push)
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.edit: i thought about it a while and i came to the conclusion that the different behavior is, because the BUD-effect caused by the upper piston. but the fast movement is still abnormal and somehow not an important bug ...
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.edit: i thought about it a while and i came to the conclusion that the different behavior is, because the BUD-effect caused by the upper piston. but the fast movement is still abnormal and somehow not an important bug ...
Important: this bug is constent though all pistons/locations unlike this bug: https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a 3-tick pulse into the whole system, powering the lower piston(s), redstone-torch for powering the upper piston.edit: i thought about it a while and i came to the conclusion that the different behavior is, because the BUD-effect caused by the upper piston. but the fast movement is still abnormal and somehow not an important bug ...
notice that the double-extender with a block and the middle one without a block ontop still move different, maybe inteded? dunno
Important: this bug is constent though all pistons/locations unlike this bug:https://mojang.atlassian.net/browse/MC-15616
using a double-extender with the same setup. pulsing a3-tickpulse into the whole system,powering the lower piston(s),redstone-torchforpoweringtheupperpiston.edit: i thought about it a while and i came to the conclusion that the different behavior is, because the BUD-effect caused by the upper piston. but the fast movement is still abnormal and somehow not an important bug ...
notice that the double-extender with a block and the middle one without a block ontop still move different, maybe inteded? dunnowhen you compare a double-extender with a block on top and one that doesn't have a block, you will notice that it behaves different and the in the D.E. without a block, the bottom piston pushes the top piston, then retracts and pushes again. it looks like a normal 1-tick pulse, but with the BUD it isn't. on the first extension, the movement is instant (abnormal).
http://youtu.be/lVh_F1KJK58
setup is the following:
8x1 tick clock -> 3 tick repeater -> block ->powering the lower pistons and redstone-torch ontop the block to power the top pistonssomewhere in this bug lies the reason for a bug on bukkit (http://youtu.be/IOawoo2l4KM)
when you compare a double-extender with a block on top and one that doesn't have a block, you will notice that it behaves different and the in the D.E. without a block, the bottom piston pushes the top piston, then retracts and pushes again. it looks like a normal 1-tick pulse, but with the BUD it isn't. on the first extension, the movement is instant (abnormal).
http://youtu.be/lVh_F1KJK58
setup is the following:
8x1 tick clock -> 3 tick repeater -> block ->powering the lower pistons and redstone-torch ontop the block to power the top pistonssomewhere in this bug lies the reason for a bug on bukkit (http://youtu.be/IOawoo2l4KM)
when you compare a double-extender with a block on top and one that doesn't have a block, you will notice that it behaves different and the in the D.E. without a block, the bottom piston pushes the top piston, then retracts and pushes again. it looks like a normal 1-tick pulse, but with the BUD it isn't. on the first extension, the movement is instant (abnormal).
http://youtu.be/lVh_F1KJK58
setup is the following:
8x1 tick clock -> 3 tick repeater -> block ->powering the lower pistons and redstone-torch ontop the block to power the top pistonssomewhere in this bug lies the reason for a bug on bukkit (http://youtu.be/IOawoo2l4KM from 0:00 to 0:22)
when you compare a double-extender with a block on top and one that doesn't have a block, you will notice that it behaves different and the in the D.E. without a block, the bottom piston pushes the top piston, then retracts and pushes again. it looks like a normal 1-tick pulse, but with the BUD it isn't. on the first extension, the movement is instant (abnormal).
http://youtu.be/lVh_F1KJK58
setup is the following:
8x1 tick clock -> 3 tick repeater -> block ->powering the lower pistons and redstone-torch ontop the block to power the top pistonssomewhere in this bug lies the reason for a bug on bukkit (http://youtu.be/IOawoo2l4KM from 0:00 to 0:22)
even though this behaves allmost normal, it is a bug. it should be solved because the bukkit team has the policity not to interfere with vanilla bugs.
has been around forever? if forever is since 1.5 or 1.5.1, then yes. or it has been gotten worse since 1.5.1 and was unnoticeable b4. since 1.5.1 it takes 3-20 seconds to completely "sit down" in a minecart. only then you are able to press buttons etc.
are you sure that this is 100% fixed?
http://youtu.be/Q-AOr8dD2F4?t=29s
maybe i'll just open another issue for that
and coal blocks too
or coal should be like netherrack
it seems like the bottom pistons pull the pistons ontop even though they weren't allowed to, because these are extended(retracting)
This is the BUD-effect
Destroying activated redstone causes a lesser radius of block-update than unpowering the redstone.
And with this technique you could create one-time BUDs that don't take up much space
reopen please!
dunno what i've seen, but this bug is still in, maybe shifted by a few pistons in one row