FiveM alt account detection: what a script can and cannot do

A FiveM server-side script sees only this: the players connecting to your server, the identifiers they present at that moment, their IP, and the player’s history on your own server. Everything else — what the player has done on other servers, which accounts they are linked to — is not in your data.

That is why `GetPlayerIdentifiers(source)` gives you only the first half of alt-account detection: it reads identities. The second half is comparing those identities against something, and if the server has nothing to compare against, no amount of good code produces a result.

There are three things you can do with your own data. Each produces a real signal and each has a known blind spot.

• Identifier history: match a connecting player’s identifiers against your own ban table. A new account sharing a license with a banned one gets caught. Limit: it knows only the accounts YOU banned, and it knows nothing about a genuinely new player.
• Device and network repetition: link accounts arriving from the same IP or the same device trace. Limit: one house, one dormitory or one VPN exit puts hundreds of innocent players behind the same address — so it should never be an action reason on its own.
• Behavioural pattern: a freshly created account, abnormal movement in the first minute, bulk joins. Limit: a weak signal that also catches new players who are not cheaters; it only means something combined with the others.

The real question is: "was this player banned on another server?" The answer is not in your database — Cfx.re does not forward one server’s ban to another and exposes no query endpoint. So answering it is a DATA problem, not a code problem; the data comes from communities that share it.

That sets the ceiling for a script author: your own archive. Beyond it you either connect to an archive shared by co-operating servers, or use a layer that checks the player before they are let in at all.

Whatever data you use, the timing decides the outcome. A check running on the `playerConnecting` event lets you decide before the player is inside; a check afterwards only limits the damage.

Argos Guard is exactly that layer: as a player connects it compares their identifiers against 110,000+ cross-server ban records and alt-account clusters. It does not replace your detection script — it adds the data your script cannot see.

Alt-account detection is probabilistic. Two siblings sharing a device, hundreds of people behind one VPN exit, and repeated popular avatars all produce false matches. So when writing the script, do not take automatic action on a single signal; score the signals and leave the threshold to the owner.

Second: an appeal path. When an automatic decision catches the wrong person, the mistake becomes permanent unless the player has a way to dispute it. That is a design requirement, not a detail.