I was working on a new Map in Singleplayer and added 4 teams:
EgyptKiller, EgyptRunner, EgyptSpec and Lobby.
after that i used NBTExplorer to edit the teamprefix, for example:
§e§lKiller:§r§e to let the playersname look like Killer: DeathTheFreaky
This works fine in Singleplayer:
after the map was ready for testing, i uploaded it to a vanilla minecraft server v 1.5.2 and tryed to connect. But i can't!
I just get this Error: Internal exception: java.io.IOException: Received string length longer than maximum allowed (18 > 16)
A friend of mine tryed it to (Minecraftname: gekxus) and he got the same error.
After that i just used a colorcode in teamprefix and it worked fine.
Linked issues
is duplicated by 6
relates to 1
Attachments
Comments 8
It is because the minecraft client only allows a max string length of 16 characters.
I also had it when i was working on my map.
I had the Lobby having the prefix of §4§l[Lobby]§r
And everything worked fine.
But on the spectator team. §4§l[Spectator]§r that didn't
But if i removed only 1 character from it, it would.
And that was because the string was 17 characters long. which it doesn't support.
This will only show up when it is on a server tho.
I had a similar problem in the latest snapshot, but it was with command blocks that didn't have anything to do with teams.
I was telling the command blocks to make minecart with command blocks, then I crashed when I entered the command that makes them.
The error said that it "Recieved string length longerr than maximum allowed (88 > 64)".
This was also on a server.
Ben, thats MC-33182
As of last night; my server members and I are receiving the following Internal Exception:
io.netty.handler.codec.DecoderException:java.io.IOException:
The received string length is longer than maximum allowed (36 > 16)
I am using 14w08a and have been since its release.
I have rebooted (computer and internet) re installed Minecraft server files and my client files but the error remains constant no matter the remedy I ply. The server has been running fine for over a year up until yesterday.
WmMichael Irwin: Look here MC-39731 for a possible solution.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
(Automatic Message)