[Bedrock] Minecart remains stationary on powered activator rail when Bedrock rider holds forward movement direction (MC:BE 1.21.81.2)
Describe the bug
When a Bedrock Edition player (v1.21.81.2) rides a stationary minecart placed on a powered activator rail, holding the forward movement input (W key/joystick) fails to initiate motion. This behavior exclusively affects Bedrock players via Geyser, while Java Edition players can activate the minecart normally under identical conditions.
Steps to Reproduce
Place an activator rail and power it with redstone on a Fabric server (1.21.5).
Position a minecart on the powered rail (remains stationary).
Join the server as a Bedrock player via Geyser and enter the minecart.
Hold the forward movement control (facing the rail's direction).
Observe the minecart's behavior.
Expected Behavior The minecart should launch and move along the rail (consistent with Java Edition behavior).
Actual Behavior The minecart remains completely stationary, showing no movement response to Bedrock player input.
Environment Details
Component Version Server Fabric (Vanilla) 1.21.5 Geyser Fabric implementation (~June 11, 2025 build) Bedrock Client Minecraft Bedrock 1.21.81.2 Reproduction Context Powered activator rails only Additional Context
✅ Bedrock-exclusive issue: Java players activate minecarts normally on same rails.
✅ No mod interference: Tested without movement/redstone-altering mods.
✅ Other rails unaffected: Normal rails and downward slopes work correctly.
❌ Temporary workaround: Requires Java player push or external momentum (e.g., slopes).
Required for Diagnosis
Output of /geyser dump (upload to dump.geysermc.org)
Exact Geyser-Fabric version from server logs
Confirmation of reproduction in pure vanilla world
(Translated by DeepSeek-R1)
To Reproduce
as above
Expected behaviour
as above
Screenshots / Videos
No response
Server Version and Plugins
No response
Geyser Dump
No response
Geyser Version
as above
Minecraft: Bedrock Edition Device/Version
as above
Additional Context
No response
Unable to replicate. Is this still an issue?