-
Notifications
You must be signed in to change notification settings - Fork 11
Permission Handler
Mike Liu edited this page May 4, 2018
·
15 revisions
NOTE: The Permission Handler is non-functional in FoxGuard versions between 0.19.X - 0.20.1 inclusive.
There's supposed to be docs here, but I'm too tired to write them, so here are some notes:
- Permission handler is now editable
- Permission handler is not configured by default
- You need to add entries, which map a flag-set to a permission node
- This is because flags are now a set, instead of being standalone.
-
/foxguard detail
on this handler produces clickable text. Use this along with tab completion to figure it out. - I'll add more docs when I feel better.
For now, it might be better to use the group
handler, which is easier to understand. More people know how to use it in my support discord, so you're more likely to receive help.
Wheeeeeee!
- The name of the Handler is used as part of the permission string by default, which means two Permission Handlers don't check the same permissions. You can use this to require different permissions for different regions.
- Permission Handlers will return
passthrough
by default, instead ofdeny
. To make the default behaviordeny
, you can use another handler with a lower priority to deny everything by default. - You can also configure a
debuff
entry and deny it by default in your permissions plugin. You can then proceed to set individual permissions toallow
.