Minecraft Forums

Alright so here is the breakdown. I have come across one really really really annoying crash. Here is what happens. Player dies. They are then frozen and have to log out and log back in. Once they do that, they regain control of their character and no issues occur. What I can't figure out is all that was changed was a Botania Update.

However here is the kicker, I resolved all potion ID conflicts. Now naturally this isn't very valid information because there is no real crash report. So then I took this a step further. I tried to replicate the bug by killing myself and NOT logging out. In other words I stood frozen and low and behold a client crash occured. Here is the log:

http://pastebin.com/tuccPxbJ

My guesses are this: It has NOTHING to do with the Botania/Forge update I applied, since reading through their changelogs doesn't seem to show anything that could cause this.

Instead I think it might have to do with a potionID conflict that I resolved. I resolved potionID conflicts for Blood Magic, AM2, Botania, AbbysalCraft, and Thaumcraft, as well as a few others. Perhaps there is a mod here that is looking for a potion ID that I changed in order to resolve a conflict (I would bet AM2 since that mod always fights with me)? Thus this causes the client to get confused, not give you control of your character and then crash. However, if you log out and log back in, this "missing" potionID/Effect goes away and that is why you regain control of your character without the crash.

Now I know this is not a lot to go on. But has anyone stumbled across this elsewhere? Or perhaps someone can decipher from the crash log what is going on?

Clearly there is an ID conflict that is out of the limits. Maybe the potion array isn't expanded properly and me adjusting some IDs put it out of the limit? Or maybe I am totally wrong and it has nothing to do with that.

Thanks,

-H

I'd like to bump this thread as this error is still concurring and I am looking for some information that perhaps others can share.

Nipped this one in the butt. I am gunna reply to you on Technic as well as this seems to be a serious issue across all 1.7.10 servers. So thanks to your help it has been resolved. Here is how you can resolve it.

The error is caused by as we originally knew a potion ID array extending beyond the boundaries. Sure enough the potion effect was indeed from Blood Magic, the Soul Flay or Fray. Many mods do expand the potion array to 128 as we have discussed, however few mods expand it correctly. So in order to resolve this issue I took a potion extension plugin. This correct the issue relating to the render issue. However as you state a new error creeps up. This error, after doing some research and using some of my own code knowledge, seems to pop up because the server does not like when you break the array boundary, as it effects other things that stay within this boundary. In the particular case of this error (the one you linked above), by extending the potion array it is somehow connected to signs. (I have no idea how)

So that error is caused by signs having too many characters, or having user names that have too many bytes; that and Minecraft cannot handle it. My theory is that the potion array uses bytes also. So by extending the array we overwrite a class that call out to a byte reader which as you guessed it is used in signs to display proper information. How to be rectify this issue? We download a patch SamistineSignFix. Now how does this help? Well kCauldron is an implementation of Spigot, Bukkit, and Forge all wrapped in one. That is a double-edged sword. That means that whatever issues exist in the other software may exist if not be worse in kCauldron. However the reverse is also true. Whatever issues exist can be fixed generally by plugins.

So that was a super long winded explanation but it made me happy to figure it out and I see that a variety of people have also come across this issue. And I am happy to report that so far *knock on wood* both the render crash as well as the netty error have both been resolved in a case of Plugin needing a Mod and Mod needing a Plugin to become compatible with one another.

TDLR: This error is caused by an extension of a potion array -> Download a Mod to Extend the Array the correct way -> Download the Patch so that the byte class that is called out to, to extend the potion array doesn't also break the signs and player names that use the same class.