Fix DisconnectClient
disconnecting clients before kicking them with message
#548
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
There was a bug in the implementation of
DisconnectClient
where the client would be disconnected before receiving the kick message.Solution
Replace
entity.remove::<Client>();
withentity.insert(Despawned);
. This way, the client will be removed at the end of the tick to give time for the packets to be sent.Playground