Paper 1.21.8: DiscordSRV grabbing messages suppressed by rules.

[Gamersxp6248]

Are you using MySQL?

Yes

Are you using a proxy?

Yes

Question

I'm trying to use the following rule for global chat:
match ^.lc(.+) then console channel sendas {player} ranged $1 then deny dont verbose
So that if anyone types ".lc Message" it will automatically redirect it to "ranged" chat. This rule works perfectly, the global message is suppressed, no one sees it, and the ranged message functions exactly as intended.
However, DiscordSRV grabs the message as a whole (since it was sent to global), and even though it was deleted / suppressed, it still manages to go all the way through and show up on the discord under the global channel as "username: .lc My base coords are 852x 9350z"

[devpedrobarbosa]

HI @Gamersxp6248

Thanks for sharing this.

I'll be looking into it.

[Gamersxp6248]

Hey, slight mistake, turns out the server I'm currently developing on does in fact use a proxy they didn't inform me of, so I edited the main post.

[devpedrobarbosa]

@Gamersxp6248 no worries!

[devpedrobarbosa]

@Gamersxp6248

I believe this has to do with Listener Priorities.

ChatControl needs to filter the messages before they're sent to DiscordSRV.

Have you been able to read this page from our docs?

https://docs.mineacademy.org/chatcontrol/listener-priorities.html

If so, have you tried all priorities?

If you weren't able yet, please refer to it and try changing between the available priorities.

Please let me know if you get it to work!

[Gamersxp6248]

Seems as though I've set ChatControl to the Lowest Priority (meaning it should be able to cancel the event before DiscordSRV). I now believe this issue stems from the fact that DiscordSRV uses the non-async chat event and will redirect this issue to them and ask if they have an option to change the event / listening type. (For reasons I just don't want to change ChatControl to stop using the async chat event)

In other words, feel free to close this issue, since it has nothing to do with ChatControl as they've already provided the tools to fix everything.

[devpedrobarbosa]

Hi @Gamersxp6248

I was not able at all to identify something that could be causing this issue on our end. Rules are parsed before everything and if you have Event Priority set to LOWEST then it should be blocking the message before it reaches any other plugin.

So, just to clarify, is this resolved? I didn't get if they actually provided a fix or not.

I'll be closing this issue but feel free to reach back if you need any further help.

Thanks a lot!

[devpedrobarbosa]

@Gamersxp6248

Just found out about this option in DiscordSRV settings called RespectChatPlugins.

It should be set to true.

Hope it helps.