txAdmin and an anticheat: what each one does on your FiveM server

"Do I still need an anticheat if I have txAdmin?" comes up in every FiveM community. The short answer: yes, because they solve different problems. txAdmin is the control panel for your server. An anticheat is the thing that notices when a player is cheating. This post explains where one ends and the other begins, and how to set them up so they work together.

What txAdmin is

txAdmin is the web panel for FXServer. It is free, comes with every server build, and most servers already run it. It handles:

• Server control: start, stop, scheduled restarts, crash recovery and the live console.
• Players: a player list with join history, notes, warnings, kicks and bans.
• Bans by identifier: bans stick to the identifiers a player connects with, and txAdmin also stores hardware tokens to catch some alt accounts.
• Whitelisting: admin-only, approved licences or a Discord role.
• Admin accounts and permissions, with login through a Cfx.re account, and an action log of what each admin did.
• The in-game menu for staff: spectate, teleport, heal, noclip and so on.

What txAdmin does not do

txAdmin acts when a person tells it to. It does not watch players for cheating. Nothing in it notices that a player is aiming through walls, moving faster than possible, spawning vehicles or running injected code. Someone has to report it, a staff member has to be online, watch, decide and ban by hand. On a busy server, that loop takes minutes to hours, and the cheater has already ruined the evening.

What an anticheat adds

An anticheat runs inside your server and on every player's client and acts on its own:

• It detects cheating behaviour as it happens, on the client and on the server.
• It acts with the action you chose for that detection: log it, kick, or ban.
• It records evidence so you can review a ban later and answer appeals.
• It remembers banned players, so a new account does not mean a clean slate.

So txAdmin is your staff's tool, and an anticheat is the staff member that never sleeps. You want both.

Running both without conflicts

A few things to get right when you add an anticheat next to txAdmin:

Staff tools must not look like cheats

txAdmin's menu gives staff noclip, teleport, god mode and spectate. To an anticheat, a player suddenly flying through a building looks exactly like a cheat. Make sure your anticheat knows who your staff are and which admin tools you use, or limit those tools to staff the anticheat exempts.

In Parity you add your staff under Configuration → Permissions. Staff with the Bypass AntiCheat permission don't trigger detections. Admin menu access alone does not exempt them from most detections.

Pick one place for bans, or connect them

Two ban lists drift apart: a player unbanned in one is still banned in the other. Decide which system is the source of truth for cheating bans. Many servers keep rule-breaking bans (RDM, toxicity) in txAdmin and cheating bans in the anticheat, where the evidence lives. If you are moving from another anticheat, import its ban list so nobody gets a fresh start.

Start order

Follow your anticheat's install guide for where its ensure line goes in server.cfg. Parity's goes after your framework and your other resources. txAdmin itself is not a resource in your list and needs nothing special.

Restarts and updates

txAdmin's scheduled restarts are a good time for anticheat updates to take effect. With Parity, configuration changes don't need a restart at all: they are pushed to the running server.

Quick comparison

Next steps

• Harden the server first: How to protect your FiveM server from cheaters.
• Comparing anticheats? 12 questions to ask before you buy.
• See Parity running next to a real server: open the demo dashboard or watch detection clips.