Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#267 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
53/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Calme
Stack technique
java
Domaine
backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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.

Langage dominant
Java
Étoiles
181
Forks
41
Merge moyen
16 h 38 min
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Sinytra/ForgifiedFabricAPI

Toutes les issues de Sinytra/ForgifiedFabricAPI

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.