Skip to content

Conversation

@GigaZelensky
Copy link
Contributor

Add debugchannel Command for Plugin Message Debugging

Summary

This PR introduces the /grim debugchannel command, allowing users to inspect plugin message channels received by a specified player. It is useful for debugging custom payloads, Fabric channel registration, and other client-server communication aspects.

Changes

  • New Command: debugchannel
    • Registered under grim|grimac
    • Requires permission: grim.debugchannel
    • Displays plugin channels a player has registered or interacted with
  • Packet Listener:
    • Captures minecraft:register and minecraft:unregister messages
    • Maintains a map of player UUIDs to registered channels
    • Supports real-time updates and removal on player quit
  • Localization Updates:
    • Added translations for debugchannel in all supported languages

Usage

/grim debugchannel <player>

Displays the plugin message channels registered by the specified player. If no player is provided, it defaults to the sender.

Impact

This command provides server administrators and developers with greater insight into player-client communication, aiding in debugging and cheat detection.

@GigaZelensky
Copy link
Contributor Author

I made this PR on mobile that's why the commits are all over the place lol but you can see what files changed :D

@Axionize
Copy link
Contributor

Won't be merged not because this is a bad idea but the entire command system is being redone anyways so none of this will work.

I'll take a look after assuming you update it to fit the design.

@GigaZelensky
Copy link
Contributor Author

Alright, I will take a look at the redone command system whenever it's out and will adapt the code accordingly.

@ManInMyVan
Copy link
Contributor

debugchannels suggests that this is a command for developers, which is not the case. I suggest making the placeholder channels, and putting this in the profile command

@ManInMyVan ManInMyVan added the status: rebase required The pull request needs rebasing onto the merge branch label May 4, 2025
@Axionize Axionize force-pushed the 2.0 branch 3 times, most recently from 5bef6b9 to 0374b8c Compare August 9, 2025 01:52
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: rebase required The pull request needs rebasing onto the merge branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants