/f perms¶

You can control who, inside or outside your faction, has access to various actions within your territory.

How it all works: Selectors and Actions¶

Determination of who can perform what actions is sorted out by selectors, which then have defined for them a series of allowed or denied actions. For example, a selector may describe all members of the faction with at least the moderator role, and that selector is allowed the setwarp action, so they may set warps within the faction. Or, perhaps a selector describing allies of the faction is allowed to open doors within the faction, as this faction wants their allies to enter their territory.

To determine if a player can perform an action, the selectors for a given faction are checked in order. If a player matches a selector, the matched selector is then checked for the action. If the action is found then that state, allow or deny, is used. Only the first selector-matched action state (allow/deny) is used. For anyone familiar with Discord permissions, this system behaves similarly. If no selectors match, or the action is not present in any matching selectors, the action is denied.

Server admins can control override permissions, defining selectors and actions that will apply to all factions and will be processed before any faction-set selectors are checked. As an example usage, a server admin could force all factions to allow allies to use buttons through an ally matching override selector with button set to allow. In the config, admins can additionally set actions to hidden and this will prevent the action from showing up anywhere. It is not advisable to hide an action after the server has been running without also setting an all override selector for it to avoid any previously set options from being unchangeable by faction admins.

All of this functionality can be controlled by a faction leader through the /f perms command, just by running that base command and clicking the text within to add/remove/reorder selectors.

Actions¶

Selectors¶