Annikka/evennia
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Relinked with correct relative links

Browse source
This commit is contained in:
Griatch 2020-06-19 15:56:02 +02:00
parent 3e8017a874
commit 061dfbffaa
91 changed files with 633 additions and 631 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/source/Concept/Building-Permissions.md
View file

@ -2,7 +2,7 @@
*OBS: This gives only a brief introduction to the access system. Locks and permissions are fully
detailed* [here](Component/Locks).
detailed* [here](../Component/Locks).
## The super user
@ -17,7 +17,7 @@ but one superuser.
Whereas permissions can be used for anything, those put in `settings.PERMISSION_HIERARCHY` will have
a ranking relative each other as well. We refer to these types of permissions as *hierarchical
permissions*. When building locks to check these permissions, the `perm()` [lock function](Component/Locks) is
permissions*. When building locks to check these permissions, the `perm()` [lock function](../Component/Locks) is
used. By default Evennia creates the following hierarchy (spelled exactly like this):
1. **Developers** basically have the same access as superusers except that they do *not* sidestep