txAdmin and Discord: every ban, warning and kick with the admin who gave it

On most FiveM servers the ban lives in txAdmin and the appeal lives in a Discord ticket, and staff copy IDs between the two. FiveBot's game server resource listens to txAdmin's own events, so every ban, warning, kick and lifted ban reaches FiveBot with the admin who gave it and the reason. The ticket side can then use that record.

What reaches FiveBot

txAdmin needs no setup. The bridge picks up:

  • Bans with txAdmin's action ID, the reason and how long they last.
  • Warnings and kicks, with the reason.
  • Lifted bans, so a ban that was revoked in txAdmin stops counting.

Each one carries the admin who did it. That matters later, when a player says "the admin banned me for nothing" and someone has to look at who it was and what they wrote.

Anticheats and other admin menus

WaveShield, Fiveguard, ElectronAC, FiniAC, FIREAC, SecureServe, Valkyrie, ReaperAC and PhoenixAC report their bans on their own when they run on the server. The bridge's black box then sets each anticheat ban against what the server saw the player do in the 3 minutes before it. Anticheat bans with evidence.

Any other admin menu or anticheat reports through one export from its own resource:

exports.fivebot_bridge:reportAction({
  kind = 'ban',
  id = 'MA-1042',
  author = source,
  target = targetId,
  reason = 'Aimbot, clip in ticket #482',
  expiresAt = os.time() + 7 * 86400,
  anticheat = false,
})

kind can be ban, warn, kick, jail, mute, or revoke when you lift one. id is the ID in your own system, so a later revoke finds the right ban. expiresAt is nil for a permanent ban.

Lifting bans from the dashboard

Reading needs no setup. To let FiveBot write back, type fivebot txadmin in the server console (bridge 0.28.0 or newer) and restart. The command copies a small file into txAdmin's own monitor resource and adds an admin named FiveBot with the Ban, Warn and Allowlist permissions. There is no password: the token stays inside txAdmin, only fivebot_bridge may use it, and the bridge puts the file back after an FXServer update. Settings, Game Server Bridge has a txAdmin tile that says Connected or what is still missing.

You can then lift a ban or withdraw a warning from Decisions, and txAdmin shows the change under FiveBot's name. A player you block through the ban network is banned in txAdmin as well. An appeal also finds the player's older txAdmin bans, from before the bridge was installed, so Lift works on those too.

Setting or taking away a staff member's txAdmin permissions from a rank change or a staff case still uses a login: an admin with Manage Admins and two lines in server.cfg. That password stays on your game server and never reaches FiveBot.

set fivebot_txadmin_user     "fivebot"
set fivebot_txadmin_password "..."

Where your team sees it

In appeal tickets

In a ban appeal ticket, staff press Appeal Cockpit and get a card only they can see: the player's linked accounts, their moderation history, the ban on record, earlier appeals and how they ended, and their purchases. From Starter it also lists similar past tickets in that category and how each was closed, so two admins do not decide the same case two different ways. How to run ban appeals.

In the AI's answers

When a player asks in a ticket whether they are banned or why, the AI can look up that player's record and answer from it. The lookup is tied to whoever opened the ticket, so nobody can ask about someone else's ban. It costs one credit on top of the answer and can be turned off in the AI settings.

On the staff board

With Bodycam on (Pro and up), the staff board shows each admin's recorded conversations next to the bans, kicks and warnings they gave. An admin who bans a lot more often than the rest stands out. More on Bodycam.

The ban network

If you opt in to the ban network, your txAdmin bans are shared with the other servers in it, and a ban you lift in txAdmin is taken off the network. Players banned for cheating often turn up on the next server the same week, and the network shows staff that history in the ticket.

An anticheat ban is held back from the network while it looks like a false alarm: a player with no earlier bans, warnings or kicks on your server, nothing in the network and at least 20 hours of play. That keeps one jumpy detection from following an innocent player around.

Setting it up

  1. Install fivebot_bridge on the game server. Installation and frameworks.
  2. Keep fivebot_report_bans on so in-game bans reach the ticket system.
  3. For an admin menu or anticheat that is not listed above, add one reportAction call where it bans, warns or kicks.
  4. Optional: type fivebot txadmin in the server console so you can lift bans from the dashboard.

Questions people ask

Does FiveBot change anything in txAdmin?

Not unless you let it. Reading bans needs nothing from txAdmin, since the bridge listens to the events txAdmin already sends to every resource. FiveBot writes to txAdmin only as its own admin, named FiveBot, and only when you lift a ban, withdraw a warning, block a player or change an admin's rank.

Which plan do I need?

The bridge and the Appeal Cockpit work on every plan. Similar past tickets and the AI ban lookup start at Starter. Prices are on fivebot.ai/pricing.

Is FiveBot affiliated with Cfx.re or txAdmin?

No. FiveBot is not affiliated with Cfx.re, txAdmin, Rockstar Games or Take-Two Interactive.

Keep reading

Your staff has answered that one forty times today.

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