Better disconnect messages sent to client

[MSKatKing]

Is your feature request related to a problem?

Whenever there’s an error server side that causes the client to disconnect, the only thing (for the most part) that is displayed on the client is “Disconnected”. This isn’t descriptive at all, and server logs are required to figure out what went wrong.

Describe the solution / feature you'd like.

Create some kind of trait that errors can implement that gives them a message to display to the client. It would work like Rust’s Error::description but be client friendly. This should hopefully give the client more information on what went wrong, especially when it’s data from the client causing the server to error. The disconnect method on PlayerList can take in this trait and forward the message to the client.

Alternatives you've considered.

N/A

Additional Context

N/A

I have confimed that...

• ... such a feature does not exist already.
• ... I ticked all the boxes without reading them
• ... such a feature request has not been submitted already.

[Sweattypalms]

So we need error handling to provide a user-friendly error to the client. Would we save the said "Error::description" in the player's state, or would we approach this?

[MSKatKing]

I would just send the description directly to the disconnect packet if possible