I’ve also noticed someone was able to get more readable version, so I’m just reposting it here:
---- Minecraft Network Protocol Error Report ----
--
| // Too many suspicious packets
|
| Time: 2025-07-12 21:37:51
| Description: Packet handling error
|
| java.lang.NullPointerException: Cannot invoke "fkr.a(fkr)" because the return value of "java.util.Map.get(Object)" is null
| at net.minecraft.client.waypoints.ClientWaypointManager.updateWaypoint(SourceFile:24)
| at net.minecraft.client.waypoints.ClientWaypointManager.updateWaypoint(SourceFile:14)
| at net.minecraft.network.protocol.game.ClientboundTrackedWaypointPacket.apply(SourceFile:69)
| at net.minecraft.client.multiplayer.ClientPacketListener.handleWaypoint(SourceFile:2430)
| at net.minecraft.network.protocol.game.ClientboundTrackedWaypointPacket.handle(SourceFile:65)
| at net.minecraft.network.protocol.game.ClientboundTrackedWaypointPacket.handle(SourceFile:20)
| at net.minecraft.network.protocol.PacketUtils.ensureRunningOnSameThread(SourceFile:27)
| at net.minecraft.util.thread.BlockableEventLoop.doRunTask(SourceFile:164)
| at net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(SourceFile:23)
| at net.minecraft.util.thread.BlockableEventLoop.pollTask(SourceFile:138)
| at net.minecraft.util.thread.BlockableEventLoop.runAllTasks(SourceFile:123)
| at net.minecraft.client.Minecraft.runTick(SourceFile:1318)
| at net.minecraft.client.Minecraft.run(SourceFile:947)
| at net.minecraft.client.main.Main.main(SourceFile:265)
|
|
| A detailed walkthrough of the error, its code path and all known details is as follows:
| ---------------------------------------------------------------------------------------
|
| -- Head --
| Thread: Render thread
| Stacktrace:
| at net.minecraft.client.waypoints.ClientWaypointManager.updateWaypoint(SourceFile:24)
| at net.minecraft.client.waypoints.ClientWaypointManager.updateWaypoint(SourceFile:14)
| at net.minecraft.network.protocol.game.ClientboundTrackedWaypointPacket.apply(SourceFile:69)
|
| -- Incoming Packet --
| Details:
| Type: clientbound/minecraft:waypoint
| Is Terminal: false
| Is Skippable: false
| Stacktrace:
| at net.minecraft.network.protocol.PacketUtils.fillCrashReport(SourceFile:56)
| at net.minecraft.client.multiplayer.ClientCommonPacketListenerImpl.storeDisconnectionReport(SourceFile:142)
| at net.minecraft.client.multiplayer.ClientCommonPacketListenerImpl.onPacketError(SourceFile:121)
| at net.minecraft.network.protocol.PacketUtils.ensureRunningOnSameThread(SourceFile:32)
| at net.minecraft.util.thread.BlockableEventLoop.doRunTask(SourceFile:164)
| at net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(SourceFile:23)
| at net.minecraft.util.thread.BlockableEventLoop.pollTask(SourceFile:138)
| at net.minecraft.util.thread.BlockableEventLoop.runAllTasks(SourceFile:123)
| at net.minecraft.client.Minecraft.runTick(SourceFile:1318)
| at net.minecraft.client.Minecraft.run(SourceFile:947)
| at net.minecraft.client.main.Main.main(SourceFile:265)
|
| -- Connection --
| Details:
| Protocol: play
| Flow: CLIENTBOUND
| Is Local: false
| Server type: OTHER
| Server brand: Leaf (Velocity)
|
| -- System Details --
| Details:
| Minecraft Version: 1.21.6
| Minecraft Version ID: 1.21.6
| Operating System: Windows 11 (amd64) version 10.0
| Java Version: 21.0.7, Microsoft
| Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Microsoft
| Memory: 287924128 bytes (274 MiB) / 671088640 bytes (640 MiB) up to 2147483648 bytes (2048 MiB)
| CPUs: 12
| Processor Vendor: AuthenticAMD
| Processor Name: AMD Ryzen 5 5500
| Identifier: AuthenticAMD Family 25 Model 80 Stepping 0
| Microarchitecture: Zen 3
| Frequency (GHz): 3.80
| Number of physical packages: 1
| Number of physical CPUs: 6
| Number of logical CPUs: 12
| Graphics card #0 name: Intel(R) Arc(TM) A750 Graphics
| Graphics card #0 vendor: Intel Corporation
| Graphics card #0 VRAM (MiB): 8096.00
| Graphics card #0 deviceId: VideoController1
| Graphics card #0 versionInfo: 32.0.101.6881
| Memory slot #0 capacity (MiB): 8192.00
| Memory slot #0 clockSpeed (GHz): 3.60
| Memory slot #0 type: DDR4
| Memory slot #1 capacity (MiB): 8192.00
| Memory slot #1 clockSpeed (GHz): 3.60
| Memory slot #1 type: DDR4
| Virtual memory max (MiB): 24879.32
| Virtual memory used (MiB): 18503.74
| Swap memory total (MiB): 8704.00
| Swap memory used (MiB): 133.61
| Space in storage for jna.tmpdir (MiB): available: 497974.88, total: 953108.00
| Space in storage for org.lwjgl.system.SharedLibraryExtractPath (MiB): available: 497974.88, total: 953108.00
| Space in storage for io.netty.native.workdir (MiB): available: 497974.88, total: 953108.00
| Space in storage for java.io.tmpdir (MiB): available: 497974.88, total: 953108.00
| Space in storage for workdir (MiB): available: 497974.88, total: 953108.00
| JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32MHello, I’ve noticed this issue is happening across more server owners & people usually solve this by disabling the Locatorbar, which is a bit sad. It doesn’t look like to be caused by external plugin.
On client, before the user get’s the specified error, he receives this too:
[22:12:12] [Render thread/WARN]: Unsupported Waypoint update operation: class fvr$a
and then after that the kick is executed, usually if user is AFK then when he return, and with that message shown.
I tried to inspect packets but I do not see anything strange probably? This one was last packed I captured
{
"operation": 2,
"waypoint": {
"data": {
"vector": [
8,
65,
-28
]
},
"icon": {
"style": {
"raw_string": "minecraft:default"
}
},
"identifier": {
"left": [
206,
114,
184,
226,
178,
105,
63,
219,
171,
12,
15,
15,
127,
30,
95,
59
]
},
"type": 1
}
}{
"operation": 1,
"waypoint": {
"data": null,
"icon": {
"style": {
"raw_string": "minecraft:default"
}
},
"identifier": {
"left": [
206,
114,
184,
226,
178,
105,
63,
219,
171,
12,
15,
15,
127,
30,
95,
59
]
},
"type": 0
}
}this one shown null data, not really sure if it tells something useful.
I think the error is in the updateWaypoint of the ClientWaypointManager. Basically it tries to get the waypoint at [id] and calls update, except there is no waypoint with the given id and as such it calls null->update and java doesn't like that. Now why would the server be sending an update waypoint to the client for a waypoint the client doesn't know exist, that is the question.
I think I won’t be able to reproduce on local multiplayer because there won’t be players 😅
So yes it’s happening on particular server, but I think it can happen on more servers?
There’s probably nothing useful in log except this:
[17:23:30] [Render thread/ERROR]: Failed to handle packet ahs[operation=UPDATE, waypoint=fvr$a@7555da04], disconnecting
java.lang.NullPointerException: Cannot invoke "fvr.a(fvr)" because the return value of "java.util.Map.get(Object)" is null
at iry.b(SourceFile:24)
at iry.b(SourceFile:14)
at ahs.a(SourceFile:69)
at hig.a(SourceFile:2422)
at ahs.a(SourceFile:65)
at ahs.a(SourceFile:20)
at xl$a.a(SourceFile:55)
at xl.b(SourceFile:38)
at gfj.d(SourceFile:1337)
at gfj.j(SourceFile:966)
at net.minecraft.client.main.Main.main(SourceFile:250)
[17:23:31] [Render thread/WARN]: Client disconnected with reason: Network Protocol Error
nothing useful before it & after that error, I don’t really wanna share full logs cause of leaking personal information 😅
Hello, I unfortunately don’t have exact steps to reproduce, but let me try to follow the template.
Steps to Reproduce:
Usually I stand on the server, probably alt tab, and like I’m AFK.
After some time I come into the game.
After moving it kicks me with “Network Protocol Error” & the mentioned error in the client log in %appdata%.
Observed Results:
After being like “AFK” alt tabbed, it just kicks me after I move on return with the mentioned error in the first message.
Expected Results:
There shouldn’t be no kick and game should work normally.
Also maybe can you translate this error into readable form please?
Players get kicked usually by Network Protocol Error when this happens & this is in the log… but I’m not really sure what exactly it means other than when I disabled locatorbar it got fixed.
What is a duplicated issue? I cannot find any existing one referring to this