Fix chat formatting on Cardboard servers - #31
Open
slyphmp4 wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Что исправлено
Cardboard exposes Paper's
AsyncChatEventclass for API compatibility, but its chat pipeline may continue to dispatch the legacy BukkitAsyncPlayerChatEvent. CloverChat previously treated mere class availability as proof thatAsyncChatEventwas usable and therefore skipped registration of the legacy listener entirely.This caused CloverChat commands to work while normal player chat bypassed CloverChat formatting on Cardboard.
Изменения
ModernChatBridgeand register the existingChatListenerusingAsyncPlayerChatEvent.AsyncChatEventbehavior unchanged on Paper/Purpur-compatible servers.AsyncPlayerChatEvent (Cardboard compatibility)in the startup banner.Scope
Only
CloverChatPlugin.javais changed. No chat formatting, permissions, proxy sync, or message dispatch logic was modified.