Network protocol error in accessing Spigot server
shotadft opened this issue · 17 comments
Modloader
Fabric
Minecraft Version
1.21.1
Modloader Version
Loader 0.16.7
No Chat Reports Version
fabric-2.9.0
Modpack Info
No response
The latest.log File
See Other Information
Bug Description
Attempting to connect to a Spigot server causes a network protocol error and fails to connect to the server.
Steps to Reproduce
- Access to spigot server
- Crash
Other Information
Crash Log:
---- Minecraft Network Protocol Error Report ----
// Could be worse, I guess
Time: 2024-10-29 21:11:04
Description: Packet handling error
java.lang.NullPointerException: Cannot invoke "net.minecraft.class_638.method_30349()" because "this.field_2062.field_1687" is null
at knot//net.minecraft.class_338.localvar$ekd000$nochatreports$modifyGUIMessage(class_338.java:2629)
at knot//net.minecraft.class_338.method_44811(class_338.java:213)
at knot//net.minecraft.class_338.method_1812(class_338.java:208)
at knot//net.minecraft.class_7594.method_44736(class_7594.java:196)
at knot//net.minecraft.class_634.method_43596(class_634.java:904)
at knot//net.minecraft.class_7439.method_43631(class_7439.java:25)
at knot//net.minecraft.class_7439.method_11054(class_7439.java:11)
at knot//net.minecraft.class_2600.method_11072(class_2600.java:27)
at knot//net.minecraft.class_1255.method_18859(class_1255.java:162)
at knot//net.minecraft.class_4093.method_18859(class_4093.java:23)
at knot//net.minecraft.class_1255.method_16075(class_1255.java:136)
at knot//net.minecraft.class_1255.method_5383(class_1255.java:121)
at knot//net.minecraft.class_310.method_1523(class_310.java:1240)
at knot//net.minecraft.class_310.method_1514(class_310.java:882)
at knot//net.minecraft.client.main.Main.main(Main.java:256)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:480)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
Can confirm this happens with me as well, when connecting to servers like thearchive.world
Couldn't reproduce issue on Minecraft 1.21.1 Fabric and 1.21.1 Spigot (4344) Server.
Could you provide more informtion on your configuration of No Chat Reports.
Also could you please upload full logs of client and server on https://mclo.gs/ and send the link of both logs here
Haha now I also have the error!
Could also be because of other mods 🤔
https://mclo.gs/0BOmtKN
I think it's related to permissions/operator:
When trying to connect with * permissions (=- operator, since LuckPerms does that automatically), the error occurs 100% of the time.
When using my alt account that has no special perms, I can't reproduce it.
When using my admin account the usual way (connect with no perms, type 2FA code, get * permission from plugin, switch to hub server), the error occurs 100% when switching servers (verify -> hub/verify -> survival/etc.)
I cannot reproduce it with 2.8.0 of NCR however, only 2.9.0
I have it on a Paper server, but not always, and usually when switching between the different servers behind Velocity.
I'll investigate.
Yup, also happens to me 100% of the time on my own personal paper server... (I also have Velocity)
Also, as reported on #493, maybe via version is part of the problem?
As a matter of fact, the server I tried to connect to did not have anything like Luckperms, but it did have ViaVersion. This is probably a duplicate or similar bug to #493.
Yeah... It's unfortunate that disabling the mod doesn't resolve the issue, at least not in my case. I have to remove the mod entirely
I cannot reproduce the issue with 2.8.0 or without having admin perms on the server so try using 2.8.0 for now
Can confirm with the server posted to #494, even with the NCR "enable mod" is set to OFF.