5ed8181adc
A server's client never took the chest slot's Elytra into its own movement (player.glider) and never told the server it started gliding, so on the server thread and as a LAN guest the player just fell. The client now sets the glider as the window's own tick does and sends ServerboundPlayerCommandPacket START_FALL_FLYING when a glide starts. The hub used to accept that command blindly and never clear it. The game now answers it as handlePlayerCommand does (Player.tryToStartFallFlying, else stopFallFlying), and each tick runs LivingEntity.updateFallFlying for a gliding guest: the glide ends once canGlide fails (landed, riding, flying, levitation, a glider about to break), every 20th tick wears the Elytra, every 10th is an elytra_glide game event, and a glide that isn't diving keeps the fall distance at 1 (checkFallDistanceAccumulation). lan_e2e gets an elytra check, for the host and the guest, both modes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>