Everyday admin with txAdmin

Once the server is running, txAdmin is where you spend your time: dealing with players, restarting, reading logs and managing staff. This page covers the features you’ll use every day and the settings worth changing early.

txAdmin Menu Beta: Introduction (Project Error)

The dashboard

The dashboard shows server status, player count, uptime, the next scheduled restart and the performance chart: server thread tick times plotted against the number of players. Spikes that line up with player joins or specific times often point to a resource doing heavy work. Pair it with the profiler (see Threads and performance).

From the dashboard you can start, stop and restart the server and send an announcement to everyone.

Players

Finding a player

The Players page searches everyone who has ever joined, by name, identifier or notes, not just who is online. Click a player to open their player modal: play time, first and last join, identifiers (license, Discord, Cfx.re, Steam), hardware IDs, their history of warns and bans, and notes your staff left.

In game, /tx opens the menu’s player list, sortable by ID, name or distance. /tx 12 jumps straight to player 12.

Warn, kick, ban

Always write a clear reason. The player sees it, and your team sees it months later. By default txAdmin hides the admin’s name in bans and warns (txAdmin-hideAdminInPunishments).

You can revoke a ban or warn from the player’s history, and ban by identifier for someone who isn’t online.

Freeze, spectate, bring, go to

Menu only, from the player’s page in /tx: freeze their ped, spectate them, bring them to you, go to them, heal them. Troll actions (drunk, fire, wild attack) exist too and are behind their own permission. Give that permission to nobody you wouldn’t trust with a ban hammer.

Whitelist

Settings > Player Manager has the whitelist mode:

With Approved license, a rejected player sees a request ID on the connect screen. Approve it on the Whitelist page or with the bot’s whitelist command.

Scheduled restarts

FiveM servers run better with regular restarts: memory from leaky scripts is freed and state is reset. In Settings > Restarter, add times in 24 hour format:

06:00, 12:00, 18:00, 00:00

Players get warnings at 30, 15, 10, 5, 4, 3, 2 and 1 minutes. Resources can react to the txAdmin:events:scheduledRestart event (for example to save data), and frameworks usually save players on shutdown.

From the dashboard you can skip the next restart or schedule a one off temporary restart.

Crash and hang handling

txAdmin restarts FXServer automatically when it crashes or hangs (stops responding to txAdmin’s checks). If it keeps restarting in a loop, open the Live Console, scroll to the last lines before the crash, and look at Common errors.

Live Console

The Live Console shows everything FXServer prints and lets you type server commands (ensure myresource, restart ox_inventory, refresh). It keeps a command history and has search. The same log is written to files in txData, so you can read yesterday’s output.

Handy commands:

refresh                 rescan the resources folder
ensure my_resource      start or restart a resource
stop my_resource
status                  list connected players
clientkick 12 reason    kick player 12
say Hello everyone      message from the console

Logs

• Server log (Server Log page): joins, leaves, deaths, chat, explosions, menu actions, plus custom lines resources add. Filter by player to see what someone did.
• Action log (System logs): what every admin did in txAdmin: bans, warns, restarts, settings changes, console commands. This is how you keep staff honest.
• Console log files in txData.

Resources page

Lists every resource with its state. Start, stop and restart single resources without touching the console. Useful for a quick restart after editing a config on a live server (if the resource supports restarting cleanly).

CFG editor

CFG Editor edits server.cfg (and other cfg files it references) in the browser. Changes apply on the next restart. Restrict it with the server.cfg.editor permission: whoever can edit the cfg can effectively run any command.

Admins and permissions

Admin Manager (needs manage.admins or the master account):

1. Add admin: a name, and their Cfx.re username and/or Discord ID. The identifiers let them use the in-game menu and log in with Cfx.re.
2. Give them a backup password or let them set one on first login.
3. Pick permissions. From txAdmin’s permission list:

A sensible moderator: players.direct_message, players.warn, players.kick, players.ban, players.spectate, players.freeze, players.teleport, menu.viewids, server.log.view. A senior admin adds control.server, commands.resources, announcement, players.whitelist.

Permissions are stored in txData/admins.json.

Backups

txAdmin keeps its own data (players, bans, warns, whitelist, settings) in txData, not in MariaDB. It does not back up your server folder or your framework database. Back up:

• txData (whole folder),
• your server data folder (server.cfg, resources, ideally in git),
• your MariaDB database, nightly (see Database setup).

Copy them off the machine. txAdmin also has a database cleanup action (on the master admin’s Master Actions page) that removes old players with little play time, old warns and expired bans, to keep its player database small on busy servers.

Settings worth changing early

• Game > Menu: enable or disable the in-game menu, align it right, change the page key.
• Game > Notifications: hide the default announcement, DM, warning or restart UI if a resource of yours shows them instead (it listens to the txAdmin events).
• Player Manager: whitelist mode, ban templates, and the message players see when banned or not whitelisted (put your Discord link there).
• Restarter: schedule.
• Discord Bot: see the Discord bot page.