mojira.dev
MC-135100

Piston stays pushed while there is no redstone.

This rarely happens, a piston or sticky piston stays powered though there is no physical interactions with redstone. 

How to reproduce:

  1. Place a redstone block.

  2. Place a sticky or normal piston underneath it (facing any direction) (on top or on side won't work).

  3. Destroy the redstone block or move it away.

  4. The piston might be activated and will push even though in F3 mode, it says unpowered.

Related issues

Comments

migrated

Can confirm, additional information I've seen concerning this issue:

  1. Redstone dust on top of a solid block above the piston yields similar results.

  2. The piston in question does not fix itself when updated by another redstone signal.

  3. Problem appears to be tied to location where piston is placed as replacing the piston results in the same piston getting stuck.

  4. Duration of redstone signal does not seem to change the result of piston getting stuck.

My testing has only been done on my Java Realms server as of this moment. I have not gotten a chance to duplicate this issue experienced by my group in a single player environment.

 

EDIT: specified Java edition Realms testing environemt

migrated

What I've noticed is that it seems like the piston is getting powered from the front which doesn't happen when the piston is any other orientation. Whenever the piston is facing upwards and there is a redstone signal powering the front face of the piston, the piston will get stuck in an extended position and remain in that state until broken. 

migrated

this has been in the game for a very long time, its most likely not gonna get 'fixed' anytime soon

 

migrated

idk why it is resolved, pops up constantly on my server ( 1.18.1 ), cannot place pistons in that spot ever again, unless I want it to be extended forever . . .

migrated

still in 1.20.1

and I dumb or does it say this issue is resolved, it clearly isnt

[Mod] Jingy

@unknown, the ticket itself resolved as a duplicate, meaning the bug/issue has already been reported before, not that the bug/issue has been fixed.
For clarity sake, this behavior is working as expected, and for the foreseeable future will not be fixed.

migrated

(Unassigned)

Unconfirmed

(Unassigned)

Minecraft 1.13, Minecraft 18w30b, Minecraft 1.13.1

Retrieved