txAdmin: how to warn, kick and ban players (and revoke a ban)

A player is breaking the rules and you need to deal with it without touching the database or server.cfg. txAdmin has moderation built in: warnings, kicks, bans, a full history per player, and a log of what every admin did. This guide covers how to use them and how to give your staff the right permissions.

Menu names change a little between txAdmin versions, so look for the same words in your panel rather than an exact click path.

#Where to moderate

You have two places:

• The web panel (the txAdmin address you use to start and stop the server). The Players page lists connected and past players, and the History page lists every action.
• The in-game menu. Admins linked to their Cfx.re account can open it in game with the /tx command, then use the Players section to act on someone nearby or online.

Both write to the same history, so it does not matter which you use.

#Warn, kick or ban

Pick the lightest action that works.

Always type a reason. The player sees it, and the next admin reads it in the history.

#Temporary or permanent

When you ban, you choose the duration: hours, days, weeks, or permanent. A temporary ban ends on its own. Use a short ban for a heated argument and a permanent one for cheating.

#Identifiers: what a ban really blocks

Each player has a set of identifiers, and txAdmin shows them on the player's details. Typical ones:

• license (the Rockstar license, the main one)
• discord, steam and fivem if present
• ip and hwid values

A ban saves them. When someone tries to join, txAdmin compares their identifiers with active bans and rejects the connection with the ban reason.

Tip: the ban message can tell the player who to contact. Put your Discord link in the reason so they know where to appeal.

Because several identifiers are saved, a new account usually does not escape a ban. It is still not perfect: someone who changes all of them can come back. For servers with that problem, a Discord whitelist adds a second barrier.

#Player history

Open a player's details and look at the history tab. You see every warning, kick and ban, who issued it, when, and the reason. Check it before deciding on a punishment, so a first offence and a fifth are not treated the same.

The same page shows how long they have played, and the names they used.

#Revoking a ban or warning

Mistakes happen, and some bans get appealed.

1. Open the player's history, or the global History page.
2. Find the action.
3. Choose Revoke.

The player can join again right away. The record stays in the history and shows it was revoked, so you keep the full picture. You can only revoke actions if your admin account has that permission.

You can also search the history by player name or identifier, which helps when a banned player writes to you without knowing their ban ID.

#Admin permissions

Do not give every moderator full control. In txAdmin's Admin Manager, each admin has their own login (or is linked to a Cfx.re account) and a set of permissions. Roughly, they are split by topic:

• Players: warn, kick, ban, revoke
• Server control: start, stop, restart
• Settings and resources
• Whitelist
• Console access

Give a new moderator the player permissions only. Keep the owner/master account for yourself. If a staff member leaves, remove their admin entry at once.

This is separate from ACE permissions that control in-game commands. For those, see ACE permissions for admins.

#The action log

txAdmin keeps a log of admin actions: who warned, kicked or banned whom, who restarted the server, who changed settings. Use it to:

• see who issued a ban when a player complains,
• check what changed before a problem started,
• review staff activity.

Combine it with your own logging. For example, send suspicious events to a Discord webhook (see anticheat basics) and then ban the player from txAdmin.

#Good moderation habits

• Warn first for small things, ban for real cheating.
• Write the reason clearly and with evidence, such as a clip or a log line.
• Use temporary bans where you can. They are easier to defend than permanent ones.
• Keep your rules in one place and link to them in the warning or ban text.
• Review the history before an appeal, and revoke if you were wrong.

#Checklist