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
{{ message }}
This repository has been archived by the owner on Jul 7, 2023. It is now read-only.
Before proceeding on taking any further actions on this issue. Please describe the following.
In the case, Faction Ownership becomes the higher (besides Faction Admin/Leadership) permission towards a chunk, how would the other permissions interact within this behavior? Explaining as follow:
Faction Leader, being the higher permission on the hierarchy: Can add, remove, edit entities on every faction claimed land, regardless of any other permission.
Faction Ownership, being the second permission on the hierarchy: Can add, remove, edit entities within a chunk that has previously been declared as Owned by the current user, regardless of this user permissions, and also, preventing others to interact, regardless of their applied permissions, but this does not affect faction leaders.
Default Faction Permissions, being the last permission on the hierarchy: Can add, remove, edit entities within the whole faction, able to execute this operations based on the given permissions, on every faction claimed land.
Will Default Faction Permissions be totally useless within Faction Owned land?
Will Faction Leaders be able to assign special permissions, to bypass Faction Ownership protection, without giving full Faction Ownership?
How can you manage Faction Land, if only faction owners will be able to interact with it?
Are Faction Owners supposed to give permissions to specific players to interact within the owned land?
If you use /f owner on chunks /f perms take priority making /f owner completely useless
Steps to reproduce the behavior:
If /f owner should take priority over /f perms at all times
The text was updated successfully, but these errors were encountered: