[SEVERE] java.io.IOException: Bad packet id 81

Discussion in 'Bukkit Help' started by Pixelzz, Aug 11, 2011.

Thread Status:
Not open for further replies.
  1. Offline


    >13:54:13 [SEVERE] java.io.IOException: Bad packet id 81
    >13:55:09 [SEVERE] at net.minecraft.server.Packet.a(Packet.java:73)
    >13:56:30 [SEVERE] at net.minecraft.server.NetworkManager.g(NetworkManager.java:149)
    >13:57:01 [SEVERE] at net.minecraft.server.NetworkManager.c(NetworkManager.java:259)
    >13:57:01 [SEVERE] at net.minecraft.server.NetworkReaderThread.run(SourceFile:84)

    I MAD BRO. jk

    help ma please it keeps spamming my console

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 18, 2016
  2. Offline


    bump like a boss
  3. Offline


    BUMP!!! I need help with this too!!!
  4. Offline


    It's probably caused by some plugin. I'm think it is Minequery or MinecraftrViewer but i'm don't know why. You may ignore this.
  5. Offline


    Minequery/MinecraftViewer love to make lag babies together, because it's running multiple ports, (UDP and TCP) versions of 25565. And sometimes the packets are accidently sent through the wrong protocol, and therefore, causes Bad Packets. Kind of like bumper cars, if one hits another, they are ALL messed up, and sometimes your server can either 1, crash, or 2, cry with errors. Most of the time, it crashes and freezes the console.
  6. Offline


    removed said minequirky packets Bad packet ID 81 continues.
  7. Offline

    Steve Member

    TCP and UDP can never conflict as they effectively run on separate zones of the network stack.

    MinecraftViewer uses UDP so also cant conflict with the server <-> client communication which is TCP even if it tried ;-)
  8. Offline


    Ah, well, I had a problem with MinecraftViewer, it fixed alot of my server crashes
  9. Offline


    22:14:15 [SEVERE] java.io.IOException: Bad packet id 81
    22:14:15 [SEVERE]       at net.minecraft.server.Packet.a(Packet.java:71)
    22:14:15 [SEVERE]       at net.minecraft.server.NetworkManager.h(NetworkManager.java:149)
    22:14:15 [SEVERE]       at net.minecraft.server.NetworkManager.c(NetworkManager.java:263)
    22:14:15 [SEVERE]       at net.minecraft.server.NetworkReaderThread.run(SourceFile:77)
    Clean server from the latest dev build.
  10. Offline


    I have this problem in the latest 1.0.0 recommended build. I have minecraftviewer on my server, is this the problem? Is it fatal to the server?
  11. Offline


    I get similar errors with various packet IDs occasionally. The funny thing is, I have worked with remote connections to Minecraft servers unrelated to gameplay. This could be caused by anything from a sloppy or obselete plugin, to someone trying to access your server with a weird client.
  12. Offline


    same problem.
  13. Offline


    I JUST FOUND OUT SOMETHING!!!!! Here is how minecraft works, the server and client sends "Packets" of data back and forth. Each packet type has an id (ex. a login packet has an id of 1, a kick packet has an id of 255 [actual id's]). As defined in the minecraft server java code, there is no packet with the id of 81! This means that some non-mojang client (MOST LIKELY NOT A PLUGIN, but could be) is sending a wierd packet. I will look into the spoutcraft client code and maybe asking some network plugin developers if they use such packets (minequery, mcbans, spout) to see if it could be a plugin (though I ran a no plugin, bukkit, server and still got the error). Try sticking with the regular minecraft clients. [note that I may be wrong, but I think I have a clue of what the problem could be]
  14. Offline


    I got this too.. when someone tries connect .. with this IP46.28.105.62 I cant find this ip in essentials user data..
Thread Status:
Not open for further replies.

Share This Page