All postsStaff tools

How to run a FiveM staff team: command logs, ranks, pluses and minuses, recorded calls

Most staff trouble on a FiveM server goes unseen. An admin spawns a car for a friend, bans someone after an argument with "rdm" as the reason, or is rude to a player on a help call. Players complain, the admin denies it, and the owner has nothing to check. FiveBot gives the owner a record of what each admin does in game and on Discord, and turns the bad parts into cases.

The command log, ranks and shift desks below work together with Decisions. Bodycam is available on Pro.

Every command an admin runs

FiveM has no single place that hears every command, so admin logs usually cover only what one menu reports. FiveBot's bridge ships hooks/commands.lua, one line a resource puts above its own scripts. Inside that resource, every command it registers reports who ran it, the arguments and the target before the command runs. fivebot hooks install in the server console adds that line to every resource that needs it. Setting up the command log.

In a framework core, one line covers every command on the server: every ESX.RegisterCommand in es_extended and every QBCore.Commands.Add in qb-core or qbx_core. txAdmin menu actions arrive on their own. Only staff are logged, judged by txAdmin admin status, the command permission and the framework group. Chat commands such as /me and /do are skipped through a list you can edit. The dashboard warns you about resources that register commands without the hook, so you know what is not logged yet.

Who is on the server right now

The Staff team page has an "On the game server now" strip, refreshed every 20 seconds, with each admin's in-game name, server ID and how long they have been on. A staff record lists everything open around that person: tickets they claimed, wrote in or were added to, cases about them waiting in Decisions and appeals against their bans.

Every admin also gets their own shift desk on the dashboard home, with the decisions they can make, their open tickets and the appeals against their bans.

Ranks, pluses, minuses and warnings

  • Staff and the owner hand out pluses and minuses with /staff plus and /staff minus, and warnings with /staff warn. /staff profile shows someone's standing.
  • Minuses add up to a warning, and warnings up to a demotion. Pluses add up to a promotion. You set every threshold and how long a mark lasts.
  • Reaching a threshold never changes a rank by itself. It opens a case in Decisions, and the owner decides.
  • A rank change moves the Discord roles, the group in ESX, QBCore or Qbox and the txAdmin permissions in one step.

Admin tools used for themselves

An admin who gives themselves something with admin tools, or hands out more money or items than your limit, comes up as a case with the log lines attached. Spawned vehicles can be logged too if you turn it on.

To see what an admin handed out, open the player's card in the dashboard: money, items, job and cars, read live from the game server. Checking a player without joining.

Recorded admin calls

Bodycam records the voice channels you mark, such as help rooms and check rooms, and keeps a transcript and a short summary of each call. Every player in the channel is told by message and by DM that the call is recorded. Each call can be checked against your staff rules, and an admin who broke them comes up in Decisions with the quotes. The moment that matters plays right in the case, so you hear it before you decide. On FutureRP, Bodycam recorded 566 calls in its first week. More on Bodycam.

Closed tickets can be reviewed against the same rules, and players can report an admin. Reports about one admin are merged into one case.

Compared with logs alone

txAdmin keeps its own action log, and Discord log bots post webhooks into a channel. Both tell you that something happened. Neither tells you which admin is on the server now, adds up an admin's minuses, or opens a case when a ban has no grounds. FiveBot puts the log, the ranks, the recorded calls and the decision in one place.

Questions people ask

Which frameworks does the command log work with?

Any. A resource that adds the hook line is covered whatever framework it uses. In ESX, QBCore and Qbox, one line in the core covers every command the core registers.

Can admins see what is logged about them?

Their own desk shows their tickets, decisions and appeals. Cases about an admin never show to that admin.

Which plan do I need?

The bridge, the command log, ranks and shift desks work on every plan. Bodycam needs Pro. Prices are on fivebot.ai/pricing.

Keep reading

Your staff has answered that one forty times today.

Setup takes about ten minutes, and there's no cap on tickets.