Fix SystemChatPacket: read boolean instead of varint #1461
Merged
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.
Since Velocity does not use SystemChatPacket's decode, it's missing proper attention and has a mistake in decoding.
But plugins managing protocol changes on proxy rely on it, so it's better to keep it working (working code is better than non-working code, right?).
The packet provides a boolean which determines if it is an actionbar message or a chat message, but for some reason SystemChatPacket reads varint which breaks ChatType determination during decode.