You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hey there! I am confident in my permission setup, but my problem is that certain plugins have commands that can be called upon by players even when they can't access them, which confuses them. It is significantly easier just listing those annoying commands than adding 3 times more commands to whitelist, and keep updating the list after every new plugin is added.
If it is possible, could there be an option to treat the whitelist as a blacklist, so the plugin blocks the command in the list?
I know this is weird considering the name of the plugin, but it would be nice.
Thanks!
The text was updated successfully, but these errors were encountered:
I looked over what I can do, but none of the ideas I had to implement this made sense nor were intuitive. It just makes sense to have subommand blacklist for command whitelist. I will leave this open and if someone comes up with a system that makes sense I'll see what I can do to implement it.
Is your feature request related to a problem? Please describe.
Hey there! I am confident in my permission setup, but my problem is that certain plugins have commands that can be called upon by players even when they can't access them, which confuses them. It is significantly easier just listing those annoying commands than adding 3 times more commands to whitelist, and keep updating the list after every new plugin is added.
If it is possible, could there be an option to treat the whitelist as a blacklist, so the plugin blocks the command in the list?
I know this is weird considering the name of the plugin, but it would be nice.
Thanks!
The text was updated successfully, but these errors were encountered: