-
-
Notifications
You must be signed in to change notification settings - Fork 201
Console spam: Unexpected packet during modded negotiation #572
Comments
This shouldnt happen unless somehow the vanilla client sends packets out of order. |
I'm using forge-1.8-11.14.1.1309-universal.jar for a generic server where everyone is vanilla. The only plug-in (mod) is Dynmap-2.1-forge-1.8.0.jar Server log 1 (debug info etc) 3.6Mb zipped 100kb Server log 2 (chats etc) latest.txt
|
I found out that whenever this happens, nether portals send you to the wrong location, killing people, or getting them lost in the nether forever miles away from any portal. For a full description, see http://www.minecraftforum.net/forums/support/server-support/2399373-serious-nether-portal-bug-player-spawns-at-same Because of this new finding I like to change the bug severity to critical but I don't know how to do that as I'm quite new to Github. I understands that it has something to do with labels, but all I can find is a labels such as 'prio:high' but not how to actually add it. |
Find a way to reproduce this and post full logs and we can take a look at it. |
Sometimes, when connecting to a FML server with a vanilla client, FML keeps spamming about unexpected packets during "modded negotiation", while the client is already connected and playing.
I haven't been able to reliably reproduce this, but it happens from time to time.
Example line:
The text was updated successfully, but these errors were encountered: