Repository navigation
Improvement to Plugin messaging on dev documentation: #740
Description
Activity
you've always been able to use your own channel, the API side of stuff on the server doesn't change at all, you would just use your channel name instead; The only real thing is that whatever is sending messages to the backend server needs to ensure that it sends a registration method to the backend, otherwise the bukkit plugin messaging logic will silently ignore it
https://docs.papermc.io/velocity/dev/plugin-messaging/ - is for doing this from velocity
Now we can create our own channel instead of using Bungeecord's, so implementing it in the docs is necessary for cases with personal channels.