Walker Christie

Just ran into this issue and found this thread via Google search. I'd be interested in learning more about the design decisions around this as its causing some awkward workarounds...

> Send the client a disconnect packet and then close the connection after instead How do I send a disconnect packet (assuming this is a suggested change on my end...

Thanks I'll give that a try. Will this apply to all previous versions as well? i.e. I don't have to have separate paths for older versions using `client.end` and 1.19+...

Great, thanks. Do we want to keep this issue open for the purpose of keeping `client.end`'s implementation consistent across versions (e.g. used for relaying the passed `reason` to the client)?...

After sending the `kick_disconnect` packet the Java client is still running into the same exception (albeit with a slightly different message) Function I'm calling ```js async function disconnect(reason: string) {...

When you say `disconnect` and close afterwards are you suggesting something like this? ```js async function disconnect(reason: string) { await client.write('disconnect', { reason }); await client.end(); } ``` Because doing...

I see-- while I am referencing the server example, I'm not sending any packets at all, basically all I'm doing is: 1. Intercepting the `login` event 2. Grabbing the host...

Seems like this is still an issue in the latest release-- is anyone else experiencing this when logging in with v1.19.2+ ?