GeyserMC
You cannot place torches on containers while flying + sneaking
Describe the bug
As a Bedrock player on our server, we have the problem that if the player is in Fly mode, he cannot place fakels or similar on containers, which is very annoying for our Bedrock players because they like to build machines with redstone.
To Reproduce
- Go to fly mode in the Bedrock version.
- Place an Furnace
- Get a redstone Torch from the inventory
- Fly and try to place it with "Sneaken" on it
- The Furnace opens and the fakel is not placed.
Expected behaviour
I was hoping that the Torch would be placed on the furnace and not that the furnace would open
Screenshots / Videos
https://youtu.be/wEy4fpjwMsQ
Server Version and Plugins
Geyser Version 2.2.0-SNAPSHOT (git-master-44174fd) (Java: 1.20.2, Bedrock: 1.20.0/1.20.1 - 1.20.50)
Geyser Dump
https://dump.geysermc.org/qaVkG4r165QHrtxrjf1iPzaX1iJWqaAr
Geyser Version
Geyser Version 2.2.0-SNAPSHOT (git-master-44174fd)
Minecraft: Bedrock Edition Device/Version
Minecraft Windows / Pocket Edition
Additional Context
No response
Does shifting+placing a torch on a container work while on the ground? Or is it just broken while flying?
Only when you fly, and with Velocity there is the problem when the players change the server then they have to rejoin because the error message "no connection to the world" appears
Does shifting+placing a torch on a container work while on the ground? Or is it just broken while flying?
Okay, I'll try to replicate the issue later today. As for the server switching issue; that's likely the following issue: https://github.com/GeyserMC/Geyser/issues/4236 - that can be resolved by installing ViaVersion/ViaBackwards on the actual backend servers instead of the proxy.
i think it is removed in bedrock. it used to work, but it seems that it doesn't anymore even without packet translation (native bedrock world)...
I'm able to sneak+place a torch on a container on 1.20.50 Bedrock singleplayer, so it seems like it's possible on Bedrock. Geyser however doesn't seem to properly handle this at the moment - marking as confirmed bug.