bedrock players get stuck in an infinite falling state if they get killed upon logout

[JHarris12345]

Describe the bug

If you kill a bedrock player when they log out (like combat log) they get trapped in an infinite falling state and can't do anything

To Reproduce

1. On the quit event kill the player
2. They're stuck

Expected behaviour

Not stuck

Screenshots / Videos

No response

Server Version and Plugins

No response

Geyser Dump

No response

Geyser Version

2.7.0-b806 (git-master-150e991)

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

No response

[onebeastchris]

Please fill out the issue report fully. You're missing a Geyser dump, and you didn't fill out server version/plugins/bedrock versions affected. Further, please specify - is the stuck death screen shown upon login? Please provide a screenshot.

[JHarris12345]

Geyser dump is https://dump.geysermc.org/4xPN1vOtBwMLri6Rzv3WiLaQOzDHlZFz

Server version is 1.21.1

I will need to confirm with a player when they next get stuck but afaik they are not stuck on the death screen, they are just free falling in the void continiously

[Tizooo]

Having the same issue.
https://dump.geysermc.org/cBZRg6Swq1Te8VLocYVE3k2lo6GgY6wK

This server is running Paper version 1.21.4-212-main@bb1beda (2025-03-17T10:10:58Z) (Implementing API version 1.21.4-R0.1-SNAPSHOT)
You are 13 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21.4-185-0a6e743 (MC: 1.21.4)

using VelocityCTD as proxy

velocity plugins: velocity, commandwhitelist, floodgate, forcepack, geyser, litebans, luckperms, papiproxybridge, velocity-scoreboard-api, tab, sayanvanish, spark, tebex, vulcan

papermc plugins: - EconomyShopGUI, FancyHolograms, nightcore, TotemGuard, TradeCycle
[23:53:38 INFO]: Bukkit Plugins (45):
[23:53:38 INFO]: - AdvancedPortals, AntiHealthIndicator, AxEnvoy, AxGraves, AxSellwands, AxShulkers, BackpackPlus, BlueSlimeCore, ChatSentry, Chunky
[23:53:38 INFO]: CoinsEngine, CommandWhitelist, CoreProtect, EntityDetection, Essentials, EssentialsSpawn, Fadah, FreedomChat, GSit, InventoryRollbackPlus
[23:53:38 INFO]: InvSeePlusPlus, LPC, LuckPerms, Multiverse-Core, packetevents, PlaceholderAPI, PvPManager, RayTraceAntiXray, SayanVanish, SmartSpawner
[23:53:38 INFO]: TAB-Bridge, Textfilter, Topper, UltimateAutoRestart, UltimateTeams, Vault, ViaBackwards, ViaVersion, voicechat, VoidGen
[23:53:38 INFO]: Vulcan, WildRTP, WorldEdit, WorldGuard, ZNPCsPlus

teleoprting or kiling the player did nothing, as if the player was in the death state but does not have a respawn button

[onebeastchris]

Can you describe the setup necessary to reproduce this in a bit more detail?

I've tested the following:

• 1.21.5/.4 paper with a plugin that kills ok leave, but the screen is shown fine when respawning
• Velocity with a 1.21.4 paper backend, also same behaviour

Do your setups "kick" the player to another server?

[JHarris12345]

I have a fallback server set in bungee when players get disconnected

[Tizooo]

so the bedrock user who had this bug on my server states:

i logged out while being in combat (we use pvpmanager to kill players on combatlog) and when i came back on i was in void with half a heart and could not type anything in chat

as far as i can see in the logs he died in our spawn world (multiversecore) where gamerule keepinventory is true and everything is protected by worldguard and theres one area where pvp is true. (a pvp arena).

my players only get kicked to another server (Lobby) if the server they are on goes offline

[onebeastchris]

Can you try and test whether the build found under "artifacts" in #5499 resolves this issue?

[OurLobanov]

I am unable to reproduce this bug, as no complaints have been received regarding it. I have tried without a fix from you: onebeastchris@fa2d465.

[onebeastchris]

As always - we're going to need replication steps, we can't fix the issue otherwise

[OurLobanov]

This commit did not solve the problem, players have been sending complaints for the last 3 days, this fix stood for 2 weeks onebeastchris@fa2d465

[OurLobanov]

As always - we're going to need replication steps, we can't fix the issue otherwise

I myself don't understand how this happens, but usually players explain it like this: they were in PvP and Minecraft crashed and after that they had this

[OurLobanov]

As always - we're going to need replication steps, we can't fix the issue otherwise

I myself don't understand how this happens, but usually players explain it like this: they were in PvP and Minecraft crashed and after that they had this

I tried to repeat this but I couldn't do it

[OurLobanov]

VID_20250506_222102_853.mp4

https://www.spigotmc.org/resources/combatlogx.31689/

purpur 1.20.1

But here the chunks somehow loaded up, it's strange.

[OurLobanov]

The player says he was on pvp and left via the exit button and after he entered There was a problem when he writes to him he writes that the chat is disabled in the client settings, I couldn't find such a text in the client, and in geyser

VID_20250507_145612_399.mp4

[OurLobanov]

I logged into the player's account from 1.21.80, I showed it to be glad I clicked everything works fine for the player version 1.21.70 was

[OurLobanov]

I discovered that the message sent when executing the /spawn command comes from the Purpur server — it considers the player to be dead. During PvP, I closed the Minecraft tab, and when I rejoined, I didn't see the death screen but could move freely around the map. However, chunks didn't load, and the chat wasn't working. After reconnecting again, the "Respawn" button appeared, and everything started working correctly. Perhaps the death state information should be delayed slightly to prevent situations like this?

[OurLobanov]

public void join(PlayerJoinEvent event) { Player player = event.getPlayer(); if (player.isDead()) { player.spigot().respawn(); } }
Corrected the situation

[Adrigamer2950]

public void join(PlayerJoinEvent event) { Player player = event.getPlayer(); if (player.isDead()) { player.spigot().respawn(); } } Corrected the situation

tried it and it solved the issue. thanks for the workaround