FiveM Fake Players Activation: What Happens in 60s

First-time buyers almost always message support within the first two minutes of activation because their players have not appeared yet. They assume something is broken. Usually nothing is broken. The connection sequence for FiveM fake players takes longer than most people expect, and the reason is that each fake player establishes a real network connection to your server rather than appearing as a database entry.

This post explains what happens in the first 60 seconds after you activate, what each step looks like in your txAdmin console, and what the three most common activation failures look like and how to fix them. For how these bot players build your server population over time, see the complete FiveM fake players guide.

The connection sequence from your dashboard to your server

When you activate fake players in the FiveFake dashboard, the sequence runs as follows:

1. Your activation request reaches our backend. This takes under one second.
2. Our backend selects the connection nodes closest to your server's reported region.
3. Nodes begin establishing connections to your server endpoint. Connections are staggered, not simultaneous, to mimic realistic join behavior.
4. Each connection completes the FiveM handshake: version negotiation, identifier exchange, and resource loading acknowledgment.
5. Players appear in your server's player list one by one as each handshake completes.
6. txAdmin registers each connection after the player appears in the server list and fires the server-side player connect event.

The time from activation to first visible player is typically 15 to 30 seconds depending on your server's geographic location relative to our connection nodes and your server's current tick load. Full activation to your configured count takes two to four minutes for counts up to 50 players and four to eight minutes for larger counts.

What you see in the txAdmin console during activation

If you are watching your txAdmin console during activation, here is what each stage looks like.

During the handshake phase, you will see incoming connection log entries appearing in the console. These look identical to real player connection events. Each entry includes the connecting player's name, the connection source identifier, and the handshake status.

During the player list phase, the txAdmin player count in the panel header begins incrementing. Players appear in the player management list with a join time, a session duration counter, and connection metadata. The session duration starts counting from zero when each player's connection completes.

After full activation, the player list shows your configured count. The txAdmin overview panel reflects the new player count. Your server browser listing updates within 30 to 60 seconds as the browser cache refreshes.

The three most common activation failures

When players do not appear after eight minutes, the cause is almost always one of three things. Here is how to identify each one.

Failure one: server endpoint not reachable

The most common activation failure is a server endpoint configuration mismatch. The IP address and port you entered in the FiveFake dashboard does not match the address your server is actually accessible on, or your server is behind a firewall that blocks connections from outside a trusted IP range.

To diagnose this: check your txAdmin console for any incoming connection attempts during the activation window. If you see no connection events at all, our nodes cannot reach your server. Verify the IP and port in your dashboard match your server's outward-facing endpoint. If your server uses a hosting provider, verify that the provider's firewall allows inbound connections on the FiveM game port from external IPs.

Failure two: artifact version incompatibility

If you see connection attempts in the txAdmin console but players are kicked immediately after the handshake, the cause is typically an artifact version incompatibility. The handshake parameters our connection layer uses are calibrated to specific artifact version ranges. An artifact that falls outside our tested range may reject the connection after the initial handshake.

To diagnose this: check the console kick message. It will indicate whether the rejection is a version mismatch or an identifier validation failure. If it is a version mismatch, check the artifact compatibility page in the dashboard. To update, go to your server page in the FiveFake dashboard, click the download button, select the compatible artifact version, and drop the resulting files into your resources folder.

Failure three: server slot limit reached

If your server is already at or near its slot maximum when activation begins, incoming fake player connections will be rejected with a "server full" response. This can happen if you misconfigure your slot count, if your server is genuinely full of real players, or if another resource is artificially reducing your available slot count.

To diagnose this: check the txAdmin player count against your configured slot maximum before activating. If the server is at capacity, wait for players to leave or increase your slot maximum before activation.

Activation speed and your schedule configuration

If you are using the scheduler to control when fake players are active, activation speed behavior changes slightly. When a scheduled window opens, the connection sequence begins automatically without manual action on your part. The same two to eight minute activation window applies from the start of the scheduled window to full count.

This means your scheduler windows should start slightly before the time you want players visible in the browser. If you want full count by 6pm, set your schedule window to open at 5:50pm. The 10-minute buffer accounts for the staggered connection window.

What happens when fake players disconnect

Fake players maintain persistent connections for the duration of their scheduled window. If a connection drops due to network conditions, our system automatically re-establishes it. The re-establishment typically takes 30 to 60 seconds and appears in your txAdmin console as a player leaving and rejoining.

When a scheduled window closes, fake players disconnect in a staggered sequence rather than all at once. The departure pattern mirrors the arrival pattern to avoid a sudden mass departure that looks unnatural to anyone watching the player list.

How server resource loading affects activation time

Servers with large resource lists take longer to complete fake player connection handshakes because the connection sequence includes a resource acknowledgment step. A server running 200 resources completes handshakes more slowly than a server running 30 resources. This is relevant when calibrating your scheduler buffer window.

If you have a large resource count and your players are not reaching full count within the standard two to eight minute window, extend your pre-activation buffer to 15 minutes in your scheduling configuration. The connection sequence itself is not slower, but the handshake completion time increases with resource list length. You will see connections completing in your txAdmin console throughout the full buffer period rather than clustering in the first two minutes.

Re-activation after a server restart

When your server restarts (manually or via txAdmin scheduled restart), all fake player connections drop because the connection state is not preserved across server restarts. Our system detects the disconnections within one to two minutes of the restart completing and automatically begins the re-activation sequence if the current time falls within a scheduled window.

The re-activation behaves identically to the initial activation sequence. Expect the same two to eight minute window for full count to restore after a restart. This is why coordinating your txAdmin restart schedule with your fake player schedule gap windows matters: a restart in the middle of a scheduled window means your players are offline for the restart duration plus the re-activation duration.

• Schedule server restarts during your schedule gap windows, not during active fake player windows.
• If a restart is unplanned (server crash), your players will re-activate automatically once the server is back online.
• txAdmin's scheduled restart feature supports time-based restart windows that you can coordinate with your FiveFake schedule gaps.

Next steps

If your activation is failing due to an artifact version issue, the

explains which build ranges are tested, how to check your current artifact version, and how to pin your server to a stable build.