A txAdmin ban saves the player’s identifiers and hardware ID tokens, then blocks joins that match them. You ban from the web panel or from the in-game menu, pick a reason and a length, and txAdmin does the rest. This guide covers the settings, permissions and events behind that, checked against txAdmin v8.1.1.
Ban, warn or kick
txAdmin gives staff three actions. A kick removes the player now, and they can rejoin straight away. A warn saves a warning to the player’s record. A ban stops them joining until it expires or someone revokes it.
The ban form offers lengths from 2 hours to 2 weeks, a custom length and permanent. Ban templates in the Bans settings let you save common reasons with a length, so staff pick them from a dropdown. That keeps wording the same across your whole team.
You can also ban a player who isn’t online. The Ban Identifiers page takes identifiers such as license or discord. txAdmin calls a ban without a license identifier a legacy ban and says to avoid it when you can.
HWID bans and the threshold setting
Since v6.0, a txAdmin ban also stores the player’s hardware ID tokens. If a banned player returns on a new account, matching tokens can still block the join.
The setting is Required Ban HWID Matches, under the advanced options in the Bans settings. It sets how many tokens must match before txAdmin blocks a join.
- 1: recommended, and the default.
- 2: lax.
- 3: very lax.
- 4: virtually disabled.
- Disable HWID Bans: turns the check off.
txAdmin’s own note says tokens aren’t guaranteed to be unique, so two unrelated players can match. It also says most players have 3 to 6 tokens. Keep the default. Raise it to 2 only if innocent players start getting blocked.
Read the full FiveM HWID ban guide
Who should be allowed to ban
Permissions are set per admin account in txAdmin. These are the ones that touch bans, or reach further than they look.
- players.ban: ban or unban a player. Give it to trusted staff only.
- players.warn and players.kick: lighter actions that suit newer moderators.
- players.remove_ids: removes a player’s identifiers and HWIDs from the database. Keep it with the owner or head admin.
- console.write: sends any command to the server console, which reaches far beyond bans.
- commands.resources: starts or stops resources, including the ones that protect your server.
- all_permissions: allows everything and replaces every other permission. Owner only.
Set up in-game staff commands with ACE permissions
Ban reasons that hold up in appeals
txAdmin needs a reason of at least 3 characters, but a good reason needs more. A banned player sees it, and so does the staff member who reviews the appeal months later.
- Name the rule that was broken.
- Say what happened in one short line.
- Note where the proof is kept, such as a clip, a screenshot or a report ticket.
- Use ban templates so the same offence gets the same wording.
Set the Ban Rejection Message too. Banned players see it when they try to join, and the default points them to a Discord for appeals. Put your own appeal link there. By default, txAdmin also hides the admin’s name from players on bans and warns. Leave that on to keep staff out of personal fights.
Why every ban needs screenshot evidence
Write rules your bans can point to
Listening to ban events from your scripts
txAdmin broadcasts server events named txAdmin:events: followed by the event name, with one table as the only argument. Your developer can listen with AddEventHandler in a server script, for example to post bans to Discord. Here is the txAdmin:events:playerBanned payload.
- author: the admin’s name.
- reason: the ban reason.
- actionId: the ID of this ban.
- expiration: when the ban ends as a timestamp, or false if permanent. Added in v4.9.
- durationInput and durationTranslated: listed in the docs without a description. Added in v5.0.
- targetNetId: the banned player’s server ID, or null for a ban on identifiers only. Added in v5.0.
- targetIds: the identifiers that were banned. Added in v5.0.
- targetHwids: the hardware ID tokens that were banned, possibly an empty list. Added in v6.0.
- targetName: the player’s clean name, or identifiers for a legacy ban. Added in v5.0.
- kickMessage: the message shown to the player as the kick reason. Added in v5.0.
Since v5.0, targetNetId and targetIds replace the old target field. Don’t build on the format of the two duration fields, because the docs don’t define it.
txAdmin also warns against relying on these events where consistency matters. Someone can ban identifiers while the server is stopped, and your resource never hears about it. Treat the event as a notification. txAdmin’s own list stays the source of truth.
Using txAdmin alongside an anticheat
Some anticheats write into txAdmin’s ban list and others keep their own. Find out which kind you run before you write staff routines around it.
Daddy Shield keeps its own ban list and does not read or write txAdmin bans. A player it bans won’t appear in txAdmin. Revoking a txAdmin ban won’t lift an anticheat ban either. Staff handle anticheat cases in our panel and manual bans in txAdmin. Write that split into your staff guide, so nobody revokes the wrong ban during an appeal.
Revoking bans and keeping records
Open the ban in txAdmin and use Revoke Ban. Revoking a ban needs players.ban, and revoking a warn needs players.warn. txAdmin then broadcasts txAdmin:events:actionRevoked with these fields.
- actionId: the ID of the revoked action.
- actionType: the kind of action, such as ban or warn.
- actionReason: the original reason.
- actionAuthor: the admin who issued it.
- playerName: the player’s name, or false if it doesn’t apply.
- playerIds: every identifier the action covered.
- playerHwids: every hardware ID token it covered, possibly an empty list. Added in v6.0.
- revokedBy: the admin who revoked it.
Log both events to a private staff channel. Every ban and every unban then has a time and a name next to it.
Is there a txAdmin ban command?
The in-game command is /tx, or /txadmin. Add a player ID, such as /tx 12, to open that player’s page and ban from there.
Can banned players evade a txAdmin ban?
A new account alone won’t get past a matching HWID ban, unless you raised the threshold or turned HWID bans off. Tokens make evasion harder, but no identifier is perfect. Watch new accounts that play like someone you banned.
If you want every anticheat ban to come with a screenshot, Daddy Shield costs €24.99 a month, or €19.99 a month on the 6-month plan. Your first payment has a 7-day refund.