Sticky Piston Bug

[7Wdev]

Describe the bug

a sticky piston does not close after removing redstone source.

To Reproduce

just make a paper/spigot server, put in geysermc and floodgate. now try to play with sticky pistons and you should notice the bug.

Expected behaviour

the sticky piston to update properly

Screenshots / Videos

Server Version and Plugins

1.21

Geyser Dump

https://dump.geysermc.org/pFM4ZL8jk9DbCQVGIcAfy5Fcn1SVolR6

Geyser Version

Geyser version 2.4.0-b604

Minecraft: Bedrock Edition Device/Version

Windows 11 PC

Additional Context

No response

[onebeastchris]

Does this also occur when testing with a 1.21 Java client?

[7Wdev]

No, only in the bedrock client. and this issue is still persistent even after establishing a clean server setup without plugins.

[onebeastchris]

There are two potential options here:

1. You may have accidentally discovered the fun concept of Java's quasi-connectivity (https://youtu.be/eyuYNDsxIHY), or a YouTube short that's a bit simpler: https://youtube.com/shorts/9r7BoMa-LEM - in which case the piston staying extended is exactly what Java behavior is (which Geyser doesnt modify).

or:

2. This could be a Geyser issue related to pistons not updating, however, this is unlikely - I've not been able to reproduce this issue on a paper 1.21 paper server.

If you believe it's 2., please provide exact replication steps for how to reproduce the issue. Thanks!

[7Wdev]

I am sure it's 2, I have tried it in a clean paper 1.21 server. The piston works well, I am talking about sticky pistons they do not update as you can see in the image I detached it from any other redstone source and it is still open.

to see it updated and closed I have to quit from the server and rejoin.

[onebeastchris]

We've received another report that it is apparently also occurring with Java clients, so there's probably a third option - please double-check that this isnt occurring for Java players

[7Wdev]

for me in java it is working normally

[onebeastchris]

For me, Bedrock is working fine, so here we are. If possible, please provide detailed replication step on how to run into that issue - further, see if paper's non-experimental 1.21 builds work.