Sticky piston not dropping block after one-tick pulse on some y-axis values
I discovered this bug where a sticky piston won't spit out its block when a 1 tick pulse is passed on the block over it. It causes the piston NOT to spit out its block on even -y axis values and on all +y axis values. the sticky piston DOES spit out the block on odd -y axis values. Here is a video of it, I have opened the F3 screen during the video so that you can see what the position of the piston is in the "Targeted block:" part of the F3 menu. I am playing in Minecraft version 1.18.2. No mods.
I know this has something to do with Quasiconnectivity but I don't know how or why, and something to do with directional features (similar to some directional 0 tick pulse generators). How and why does this happen?
Best Answer
In some cases, the dust that powers the piston diagonally gets depowered last. The piston only gets updated and finds this when the b36 of its piston head finalizes.
Redstone dust update order is locational and unpredictable. See MC-11193.
Pictures about "Sticky piston not dropping block after one-tick pulse on some y-axis values"
Why is my sticky piston not extending?
A sticky piston simply leaves a block behind if it cannot pull it. Pistons cannot push blocks into the void or beyond the top of the map. They also cannot push more than 12 blocks. If the requirements for a block to be pushed are not met, the piston simply does not extend.How do you get a sticky piston to let go of a block?
On Xbox 360 and Playstation 4, when a sticky piston is activated by an observer, the quick pulse of energy causes a fast reciprocation of the sticky piston, which then leaves the redstone block behind. When reactivated by the observer, the the sticky piston picks up the redstone block and takes it away.How many blocks can a sticky piston pull?
A sticky piston can push up to twelve blocks in a row when engaged, but will only pull one back with it when disengaged unless you're using a slime block.Why wont my pistons work in Minecraft?
Pistons only extend when unblocked if you remove the block directly in front of them, otherwise they don't get a block update. The workaround would be to power them later.Piston bug(?)
Sources: Stack Exchange - This article follows the attribution requirements of Stack Exchange and is licensed under CC BY-SA 3.0.
Images: Joshua Miranda, Joshua Miranda, Tatiana Syrikova, Mikhail Nilov