Admins, ACE permissions and moderation
In short
Two permission systems run side by side: txAdmin permissions for the web panel and in-game admin menu, and ACE permissions for commands and scripts.
# groups
add_ace group.admin command allow
add_ace group.admin command.quit deny
add_ace group.mod command.kick allow
add_principal group.admin group.mod
# people
add_principal identifier.fivem:1 group.admin
add_principal identifier.discord:123456789012345678 group.mod
# check from the console
test_ace group.mod command.kickRegisterCommand('kickidle', function(source)
if source ~= 0 and not IsPlayerAceAllowed(source, 'command.kick') then return end
-- ...
end, false)| Identifier | Always there? | Notes |
|---|---|---|
license | Yes | Rockstar licence — the stable key for players |
license2 | Usually | Second licence (for example Steam users) |
discord | If Discord is running | Needed for Discord roles and whitelists |
fivem | If logged in to Cfx.re | Used by txAdmin |
steam | Only with steam_webApiKey | And Steam running |
ip | Yes | Changes; never use alone |
- One txAdmin account per staff member with only the permissions their role needs.
- txAdmin bans store identifiers and hardware tokens and log who banned and why.
- Write down punishments and an appeal route, and link them from Discord.
- Separate moderation powers from infrastructure access (files, database, host).