Skip to content

Don't send legacy clients their own death event#1296

Merged
kennytv merged 1 commit into
ViaVersion:masterfrom
Term4:fix/legacy-death-inventory-clear
Jul 18, 2026
Merged

Don't send legacy clients their own death event#1296
kennytv merged 1 commit into
ViaVersion:masterfrom
Term4:fix/legacy-death-inventory-clear

Conversation

@Term4

@Term4 Term4 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Clients up to 1.13.2 run the local death handling on their own entity death event, clearing their own inventory client-side (most visibly an emptied hotbar on the death screen, since modern servers don't resync the inventory on death). The death screen still shows from the health update. 1.14+ clients no longer clear the inventory.

Clients up to 1.13.2 run the local death handling on their own entity death event, clearing their own inventory client-side (most visibly an emptied hotbar on the death screen, since modern servers don't resync the inventory on death). The death screen still shows from the health update. 1.14+ clients no longer clear the inventory.
@Term4
Term4 force-pushed the fix/legacy-death-inventory-clear branch from 9d4f902 to 939226c Compare July 17, 2026 15:43
@kennytv
kennytv merged commit 483c0ec into ViaVersion:master Jul 18, 2026
1 check passed
@Term4

Term4 commented Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

I actually want to go back and check something beanes brought to me, that we need to ensure that a corresponding update health packet is sent so the client properly handles its own death. For a case in which a modern server sends a death event directly without updating health, should that occur with plugins or what have you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants