txAdmin and Fake Players: Full Integration Guide

txAdmin is the most widely used FiveM server management platform. Your staff and moderators use it to monitor player sessions, check player counts, and manage connections in real time. Without txAdmin integration, your staff would see a disconnect between the player count shown in the public server browser and the sessions visible in the txAdmin panel. That mismatch is an obvious tell. Connecting a FiveM fake players service to that panel keeps your bot players visible as part of the server population everywhere your staff look.

With FiveFake, fake players appear inside the txAdmin web panel and in the in-game player list, identical to how real players appear. This is the entire purpose of the txAdmin integration. Your staff see a consistent player list and nothing stands out.

The setup is straightforward. Go to the FiveFake dashboard, navigate to your server page, and download the artifact for the version that matches your FiveM server build. Drop the resulting files into your server's resources folder. Then toggle the txAdmin integration option on. From that point forward, fake players are visible in your txAdmin panel exactly as real players are.

What you need before you start

1. A running FiveM server with txAdmin installed and accessible via its web panel
2. Your server's public IP address and server port (default is 30120 unless you changed it)
3. Your txAdmin panel port (default is 40120)
4. A FiveFake account with an active subscription of at least 15 players
5. A compatible FiveM artifact build — see the artifacts compatibility guide for supported build ranges

You do not need to modify your server.cfg beyond what is already required to run txAdmin. The artifact files go in your resources folder and the rest of the integration is managed from the FiveFake dashboard side.

Enabling txAdmin integration in the dashboard

In the FiveFake dashboard, navigate to your server configuration. You will enter three pieces of information: your server IP, your server port, and an optional display label so you can distinguish this server from others in your account if you manage multiple servers. Then toggle the txAdmin integration option to on. No account linking, no token exchange, and no OAuth flow is required. The toggle is all it takes.

After entering the IP and port, use the connection test tool in the dashboard before saving. The test tool sends a probe request to your server's connection endpoint and checks whether it receives a valid response. If the test fails, the most common reasons are:

• Your server firewall is blocking inbound connections on port 30120 from external IPs
• Your server is not running at the time of the test
• You entered the LAN IP instead of the public IP
• Your host uses a non-standard port that differs from 30120
• txAdmin is running but the FiveM server process it manages has crashed or not yet started

What fake player connections look like in txAdmin

Once connections are active, open your txAdmin panel and navigate to the players list. You will see the fake player sessions listed alongside any real player sessions. Each connection shows a player name, a server ID, and an uptime counter. The uptime counter for fake players increments normally because the sessions are maintained continuously.

Player names in the session list

The names that appear in txAdmin are the names you configured in the FiveFake dashboard. If you are using one of our regional name packs, the names will reflect that pack. If you have edited individual player name fields directly, those names appear. If you have not configured names yet, the connections use the default names from our base pack, which are generic English names.

We recommend configuring names before your first activation. Seeing 30 connections named Player_1 through Player_30 in your txAdmin panel is a visual red flag for any admin who looks at the session list without knowing the context.

Server ID assignment

Your FiveM server assigns server IDs sequentially as connections join. Fake players receive server IDs in the same pool as real players. If you have 5 real players already connected when 20 fake players join, the server IDs for the fake players will be 6 through 25 or wherever the next available ID falls. This is normal behavior.

Verifying the connection is stable

After activation, wait 90 seconds, then check three things to confirm the integration is healthy:

1. Player count in the FiveFake dashboard matches the count you configured
2. txAdmin player list shows the correct number of active sessions
3. The CFX server browser (servers.fivem.net) shows your server's player count updated to include the new connections

The CFX server browser update can take up to 5 minutes because it polls on its own schedule. Do not expect the browser count to update the moment you activate. The txAdmin panel updates in real time.

If the count in the FiveFake dashboard shows the correct number but txAdmin shows fewer, your server may be applying a connection rate limit. By default, txAdmin and FiveM do not impose strict connection rate limits for small counts, but some server frameworks or custom scripts add their own. Check your server console for any connection rejection messages.

Common errors and what they mean

Connections not appearing in txAdmin

If you activate fake players but see nothing in txAdmin after 2 minutes, the connection is failing before it reaches the player session stage. Check your server console for connection rejection entries. The most common cause is a resource on your server that blocks connections from IP ranges it does not recognize. Some anti-cheat or anti-exploit resources have IP allowlists. Our connection infrastructure uses a defined IP range that you can allowlist in such resources.

Connections appearing then dropping

If connections appear in txAdmin for a few seconds and then disappear, a resource on your server is kicking the connections after the initial join. The most common culprits are session validation scripts that check for a valid game license, scripts that verify client software versions, or custom connection validation handlers. Identify which resource is firing the kick event by checking the txAdmin kick log for the player ID and the kick reason.

Player count showing in dashboard but not in browser

This is almost always a timing issue. The CFX server browser does not update in real time. Give it 5 to 10 minutes after activation before checking the browser count. If the count still does not update after 15 minutes, verify that your server is listed on the browser at all by searching for it directly. Some servers are unlisted by choice or misconfiguration, in which case fake players will not appear in public browser results even though they are connected.

Artifact versions and compatibility

FiveM artifacts are the versioned builds of the FiveM server binary. Compatibility between fake player services and FiveM artifacts is not guaranteed across all build numbers. When FiveM updates its connection handshake protocol, fake player services that have not updated their connection logic will fail to establish sessions.

We test against new artifact releases before they become stable in the txAdmin artifact selector. When a new build breaks compatibility, we push a fix within 24 hours. If you are on a build that is not in our tested range, the dashboard will show a compatibility warning before you attempt to activate. Do not override that warning without reading the details.

Managing multiple servers in one account

If you operate more than one FiveM server, you can manage all of them from a single FiveFake account. Each server gets its own configuration entry with independent player counts, schedules, and name packs. Billing is per-player across all active servers, so your total daily cost is the sum of all configured player counts.

The dashboard shows each server's active status, current player count, and connection health independently. If one server has a configuration issue, it does not affect the others. You can pause one server's fake players while keeping another active.

Next steps

Once your connections are stable in txAdmin, the next step is setting up a schedule that mirrors real player behavior for your region. A flat 24-hour player count is the most common mistake after initial setup.