There have been a recent flood of bugs on permissions due to
misunderstanding how permissions work (for manses, totems, etc.). I have
changed how permissions are displayed if you probe a totem or list manse
permissions, etc. Many people try to do a full ban of some group by say
NOT. For example, NOT MEMBER OF HARTSTONE is often used as an attempt to
ban all members of Harstone from entering a manse. You really should use
the EXCEPT syntax for that. If you have any NOT clauses in your
permissions, upon viewing the permissions you will see the following
warning, which I hope helps clarify why NOT is improper for making
exceptions to the rule.

Warning: there is a rule that begins with "is not" for those who are hit
by this permissions set. This can lead to unexpected results. For
example, if you say "is member of Celest or is not member of clan
Roark's Fanclub" (MEMBERS OF CELEST / NOT MEMBERS OF ROARKFAN), your
intent might be to allow citizens of Celest except for those in the
Roark's Fanclub clan. In reality, it will allow anyone who is a citizen
of Celest and also anyone who is not a member of the Roark's Fanclub
clan, regardless of citizenship. This means Magnagorans who are not a
member of the clan would be allowed by this rule set. If your intent is
to always ban people meeting a certain criteria then you want to use the
exceptions syntax, such as "is member of Celest and except is member of
Magnagora" (MEMBERS OF CELEST / EXCEPT MEMBERS OF ROARKFAN).

In other words, a permission set is true if a person satisfies *any one
line* in the list of permissions that does not begin with "EXCEPT". For
those lines that do begin with "EXCEPT", the permission set will be true
for a player who satisfies any one EXCEPTion line, overriding any other
qualifications they have from the other permission lines.

Penned by My hand on the 18th of Dvarsh, in the year 146 CE.