Appearance
Staff ranks and permissions
Staff privilege belongs to the account. Faction tier belongs to the character. These are independent systems with different number ordering.
Staff levels
| Level | Rank |
|---|---|
| 0 | Regular player |
| 1 | Beta Tester |
| 2 | Junior Admin |
| 3 | General Admin |
| 4 | Senior Admin |
| 5 | Lead Admin |
| 6 | Head Admin |
| 7 | Manager |
| 8 | Developer |
The Pawn enum is in gamemodes/admin/data.pwn; the web mirror is web-platform/web/lib/constants.ts. The initial bootstrap creates level 8, not 9. Keep these definitions aligned if you change the rank structure.
ACP access
Junior level and above can enter ACP, with individual areas gated more narrowly. A navigation link is not the complete permission rule: page reads and write actions perform their own server-side checks. Staff level is read from the database rather than relying only on a login-time label.
The generated ACP page reference lists navigation minimums. Important operations include:
| Operation | Minimum checked by the operation |
|---|---|
| Armory type, equipment and locker editing | General, 3 |
| Faction skin/custom skin management | Manager, 7 |
| Start game / schedule a start | Lead, 5 |
| Stop game | Manager, 7 |
| Console commands / console stream | Developer, 8 |
Verify the specific action if you change its implementation; do not implement security by merely hiding a button.
In-game checks
Commands can also require staff duty, logged-in character state, target validity, rank hierarchy, range or other conditions. /aduty enables the intended staff tools; it is not faction /duty.
The command inventory includes source locations and staff constants referenced in each handler. These are clues, not an automatically proven minimum: helper functions and aliases can enforce additional restrictions. For example, some legacy helper thresholds differ from a rank’s display name. Read the actual guard when modifying permissions.
Grant and revoke access
Use the first-admin bootstrap only for an empty staff setup. Use the appropriate ACP account settings or /makeadmin for later assignments, respecting their own hierarchy checks. Give each staff member their own account and only the role needed.
Test demotion and action access with a lower-rank account. Do not validate the entire ACP only as Developer; that rank bypasses many ordinary navigation limitations.