Permissions
Access to the panel (and to sensitive actions) is checked on the server every time — the client is never trusted.
Who can open the panel?
Detection runs in this order (first match wins):
- ACE permission —
command.zonecreator - QBCore permission — one of
Config.QBPermissions(defaultadmin,god) - ESX group — one of
Config.ESXGroups(defaultadmin,superadmin)
ACE (framework-agnostic)
add_ace group.admin command.zonecreator allow
You can also grant it to a single player by identifier:
add_ace identifier.license:xxxxxxxx command.zonecreator allow
Role tiers (badge + action gate)
Each admin is resolved to a role shown as a badge in the panel and used to gate actions. Mapping lives in Config.Roles:
| Framework | Detected value → role |
|---|---|
| QBCore | god → superadmin, admin → admin, mod → moderator |
| ESX | superadmin → superadmin, admin → admin, mod → moderator |
| ACE | zonecreator.role.<role> (e.g. zonecreator.role.admin) |
Action requirements
Most actions need only moderator. Sensitive ones require a higher tier and are configured in Config.ActionRoles:
Config.ActionRoles = {
kick = 'admin', ban = 'admin', kill = 'admin', zoneban = 'admin',
}
The bulk actions and delete require superadmin by default (see the can() tiers in the panel). Anything not listed is allowed at moderator level.
Because the gate is server-side, a lower-tier admin who tries a higher-tier action gets a `"… requires role"` notification and nothing happens — even if the UI button was reached.
Commands
| Command | Who | What |
|---|---|---|
/zonemanager |
Admins (per above) | Opens the management panel. The command name is Config.Command. |
/zonehud |
Everyone | Toggles the player-facing restriction HUD. Players can also rebind the key (default F7, Config.Hud.toggleKey). |