Admin & Permissions

#The ACE gate

add_ace group.admin recognition.admin allow
add_principal identifier.license:YOUR_LICENSE_HERE group.admin

Or for a single person, without a group:

add_ace identifier.license:YOUR_LICENSE_HERE recognition.admin allow

#The six levels

Give a staff role one child ACE instead of the parent.

add_ace group.mod recognition.admin.view allow
add_ace group.mod recognition.admin.export allow

#The admin panel

/recognition:admin opens the panel: a tablet with an icon sidebar on the left. A page or button you have no level for stays hidden or read-only.

Page by page with pictures: Admin Panel.

#Reasons

Every reason ends up in recognition_admin_log, which is tamper-evident like the proof log (recognition:verifyproofs checks both), and in the Admin webhook when one is set.

#Self-protection

#Panel behaviour

#The in-game settings editor

Admins with the settings level can change most of config.lua from the panel, without a restart. Changes are stored in recognition_settings and survive restarts.

Every setting has a plain title and an (i) tip that says what it does in one or two sentences; the settings are sorted into groups with friendly names (Memory, Scan and quick look, Face implant, ...). Search the list, or use the All / Changed / File only chips. A lock shows why a row cannot be changed here: Only in config.lua, Needs the … admin level, or Edit this one in config.lua (lists and tables).

The titles and tips come from locales/en_settings.lua. To translate them, copy it to locales/xx_settings.lua (your language code) and translate the values.

With LiveSettings = 'all' that includes the implant price and wait, the police and description caps, the lab settings and the death radius.

#What every change goes through

1. ACE gate — the settings level, plus any extra level from SettingPerms.
2. Schema check — the value has to be the right type and shape.
3. Range — numbers are kept inside their allowed range on the server; the page shows "Limited to …" when a value was cut.
4. Audit log — the old and new value, the admin, and the written reason, into the tamper-evident recognition_admin_log.
5. Discord — per DiscordActions.
6. Reset to file — any override can be undone, individually or all at once, back to the config.lua value.

#Extra levels per area

SettingPerms = {
    ['Implant.'] = 'identity',   -- free implants are an identity reset
    ['Report.']  = 'edit',
    ['Lab.']     = 'edit',
    ['Death.']   = 'edit',
}

An admin with settings alone sees those rows read-only. {} means settings is always enough.

#What can never be changed in game

FileOnly = {
    'ServerConfig.*',
    '*System', 'Framework', 'MulticharSystem', 'MDT',
    'Admin.Ace', 'Admin.FrameworkGroups', 'Admin.TxAdmin', 'Admin.TxAdminPerms', 'Admin.Perms',
    'Admin.GroupPerms', 'Admin.LiveSettings', 'Admin.FileOnly',
    'Admin.SettingPerms',
    'Admin.BlockSelfEdit', 'Admin.BlockSelfView', 'Admin.RequireReason',
    'Admin.LogViews', 'Admin.DiscordActions',
    'Memory.Disguises',
}

'<Table>.*' locks a whole table and '*System' locks every integration selector. Add your own paths to this list to lock more — entries are added to the built-in list, never replace it.

#Discord for admin actions

#Boot lines

[5code-recognition] Admin settings overrides active: 7 (see the admin panel > Settings, or reset them to the file defaults).

Printed only when there are any. Nothing is printed when there are none.

[5code-recognition] Ignored 1 stored setting override (Config.Foo.Bar): unknown or invalid. The config.lua value is used.

An override whose key no longer exists — usually after an update that renamed something — is dropped with that one warning and the file value is used.

#Commands and the level each needs

Rename any command, or set it to false to turn it off, in Config.Commands.

#Admin menu buttons

Any admin menu can open the panel with one server-side call:

exports['5code-recognition']:OpenAdminPanel(source, targetA, targetB)

The permission check happens on our side, so the button is safe to add anywhere. See Admin Menus.