Setup: Have two accounts both connected to a new LAN world (run by UserA) on the same PC; /debug mode is running to get more info into the log (also works if /debug is off).

When UserA runs the command "/say @e" the user UserB gets disconnected with the attached error message. The log below is from the latest.log of UserA (because the chat is too big and exceeds the normal chat limit).

[20:44:36] [Server thread/INFO]: [UserA] Rabbit, Rabbit, Rabbit, Rabbit, .... (and loads more)
[20:44:36] [Client thread/INFO]: [CHAT] [UserA] Rabbit, Rabbit, Rabbit, .... (and loads more)
[20:44:36] Netty Server IO #7/ERROR: java.io.IOException: String too big (was 73668 bytes encoded, max 32767)
[20:44:36] [Server thread/INFO]: UserB lost connection: TextComponent{text='Disconnected', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
[20:44:36] [Server thread/INFO]: UserB left the game

This also works on 14w27b SMP servers too (all clients get disconnected in this case) and since @e is not a restricted "command" this could effectively grief/DOS servers.

I know this is rather silly of a bug; but the chat should be a little more graceful when dealing with unexpectedly large chat messages.

Thanks,
Michael