Aurel

Also consider properly setting permissions to begin with to avoid that issue on other plugins too. (Referring to giving * for example)

Due to the nature of how this plugin is made, aka it not being open source, I cannot give a definite answer to that. What I'm thinking is happening here...

This still does not bring this issue further, as neither I or the actual Developers of AdvancedBan can look into how ChatControl acts on event priorities. There had been issues...

Use Jitpack https://jitpack.io/#DevLeoko/AdvancedBan

Greetings! Thanks for opening this issue. There is already somewhat of a ban id option, which is the case id. You can use `%ID%` to display it in applicable messages...

there's not, no. Ban IDs are incremental. You could use the hexadecimal version by using `%HEX_ID%` to make it somewhat unique.

https://en.m.wikipedia.org/wiki/Hexadecimal

That can be done by giving the default group (or any preferred group) the notify permission. `ab.notify.`. More on the [spigot page.](https://www.spigotmc.org/resources/advancedban.8695/)

Maybe just fully state your issue or join our discord server for help: https://discord.com/invite/ycDG6rS

in this case, ab.notify.all can be used if on Bungeecord, the normal ab.notify.* on spigot. You will need to change the AllPermissionNodes setting on your configuration.