Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Players are Disconnected when recieving Death Message with Chat Open (incompatibility with Supplementaries)

Open
  • Is something wrong?
#267 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
53/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
backend

Research direction

Start with MinecraftClientMixin.java and ScreenEvents.remove, the locations named in the report, then inspect how the death packet is handled when chat is open alongside Supplementaries. Reproduce on Minecraft 1.21.1 with Forgified Fabric API and Supplementaries; done means dying with chat open no longer disconnects the player.

Written by the indexing model from the issue text.

Description

1.21.x bug
Minecraft version

1.21.1

Describe the bug

Dying with Chat Open Crashes Game

Steps to reproduce
  1. Play with the Forgified Fabric API.
  2. Install Supplementaries. I tested it without supplementaries and the error doesn't occur, but the error originates from the onScreenRemove function, which is likely not called by Supplementaries.
  3. Place yourself at a Y level high off the ground and die with chat open.
  4. Causes error upon the death packet being received:
[Server thread/INFO][net.minecraft.server.MinecraftServer/]: PlayerName fell from a high place
[Render thread/ERROR][net.minecraft.client.multiplayer.ClientCommonPacketListenerImpl/]: Failed to handle packet ClientboundPlayerCombatKillPacket[playerId=79, message=translation{key='death.fell.accident.generic', args=[empty[style={clickEvent=ClickEvent{action=SUGGEST_COMMAND, value='/tell PlayerName '},hoverEvent=TypedHoverEvent[action=<action show_entity>, value=net.minecraft.network.chat.HoverEvent$EntityTooltipInfo@aff16f4a],insertion=PlayerName}, siblings=[literal{PlayerName}]]]}]
java.lang.NullPointerException: Screen cannot be null
	at java.base/java.util.Objects.requireNonNull(Objects.java:259) ~[?:?]
	at TRANSFORMER/[email protected]+4228281319/net.fabricmc.fabric.api.client.screen.v1.ScreenEvents.remove(ScreenEvents.java:111) ~[fabric-screen-api-v1-2.0.25+4228281319.jar%23428!/:2.0.25+4228281319]
  1. Player is booted back to the multiplayer menu, even in singleplayer.
Logs

latest.log

Additional context

This issue has already been reported to the Supplementaries developers and marked as not an issue on their end, then moved to this Forgified Fabric API issue, but judging by the comments saying that it is still an issue months after its fix I'm assuming issues here aren't reopened and a new one needs to be made.

Dominant language
Java
Stars
181
Forks
41
Avg merge
10d 5h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Sinytra/ForgifiedFabricAPI

All issues in Sinytra/ForgifiedFabricAPI

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.