RedCraftChat 0.2.3-SNAPSHOT

Stop a message sent just before a server switch from kicking the player

/hub disconnected the client with "unknown packet id 121". The transfer
itself worked, and the drop came a second later, which is the shape of a
packet written into a connection that has moved on.

System messages are not sent straight through here. The original is
cancelled and a copy is written back after the chat grouping window, and
a player can leave PLAY inside that window by switching servers or
quitting. A play packet written to a connection already in configuration
is decoded against the wrong table, and the client does not recover.

So the delayed write now drops anything whose flush lands outside PLAY.
That guard is not about /servers: any message sent shortly before a
switch or a quit could do this, it just took something that reliably
pairs a message with an immediate switch to make it show. getEncoderState
rather than getConnectionState, because the latter throws while the
encoder and decoder disagree, which is the moment being guarded.

The "sending you to X" line goes with it. It was the trigger, and a
message nobody would have read, since the screen changing says it sooner.

Also aliases the servers people actually ask for by name.