1
Can anyone explain this?
Ok so i was playing around in minecraft 1.8 with a new take on castle doors using slime blocks instead of multiple pistons or falling gravel
Essentially it uses all the regular mechanics of a castle door abba switch on the bottom,
Repeaters to time the closing of the door and a torch tower to activate the top 2 pistons
Screenshot 1
But as you can see in the screenshot 1 of the pistons is extended and it shouldn't be
heres a close up including the top redstone
Screenshot 2
Im unsure why this happens when i place a block nearby and force a block update it resets.
Edit I have resolved this by changing the path the redstone takes at the top as i realized it could be simpler than what i already had.
But i am still unsure why the piston did what it did.
Essentially it uses all the regular mechanics of a castle door abba switch on the bottom,
Repeaters to time the closing of the door and a torch tower to activate the top 2 pistons
Screenshot 1
But as you can see in the screenshot 1 of the pistons is extended and it shouldn't be
heres a close up including the top redstone
Screenshot 2
Im unsure why this happens when i place a block nearby and force a block update it resets.
Edit I have resolved this by changing the path the redstone takes at the top as i realized it could be simpler than what i already had.
But i am still unsure why the piston did what it did.
Create an account or sign in to comment.
3
1
I have this problem too. I remember reading somewhere why this is and it actually made sense but I can't remember the reason...
Point is, it's not a glitch or lag or anything like that; it's supposed to do that as annoying as it can be.
Point is, it's not a glitch or lag or anything like that; it's supposed to do that as annoying as it can be.
1
Erm, looks like lag to me, but I don't know to much about redstone.
1
woah...