Players are Disconnected when recieving Death Message with Chat Open (incompatibility with Supplementaries)
Nadie ha tomado este issue todavía.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Minecraft version
1.21.1
Describe the bug
Dying with Chat Open Crashes Game
Steps to reproduce
- Play with the Forgified Fabric API.
- 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.
- Place yourself at a Y level high off the ground and die with chat open.
- 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]
- Player is booted back to the multiplayer menu, even in singleplayer.
Logs
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.
- Lenguaje dominante
- Java
- Estrellas
- 181
- Forks
- 41
- Merge medio
- 19 d 17 h
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Sinytra/ForgifiedFabricAPI
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Sinytra/ForgifiedFabricAPI#298 ·
-
Missing mixin in fabric-registry-sync-v0 suspected to break modded registry loadingQuizá libre de nuevo @Su5eD la tomó hace 87 días y no hay ningún pull request abierto. Abierto26.1.x bug
Sinytra/ForgifiedFabricAPI#280 · 6 comentarios · 1 asignado ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#276 ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#269 ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#265 · 6 comentarios ·
Todos los issues de Sinytra/ForgifiedFabricAPI
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
floci-io/floci#5369 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
sqlcipher/sqlcipher-android#97 · 1 comentario ·
-
bug IIIF interoperability
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Netcracker/qubership-integration-platform#1046 ·
Los mantenedores suelen responder en 2 días