Live index feed: recent name changes, bans and signals across monitored servers.
argos · guard
Stop cheaters at connect.
Argos Guard screens every player connecting to your FiveM server against 110,000+ cross-server ban records, confirmed cheat-shop customers and known alt accounts. Drop in one resource and a banned license never reaches your spawn point.
Product demo, a sample FiveM connect alert for a demonstration player.
file 01 / 02 · doctrine
01
Connect-time screening
Every player is checked the moment they connect, against their Steam, license, Discord and FiveM identifiers — before they ever spawn in. A rejected connection stays rejected on reconnect.
playerConnecting · identifiers matched · reject
02
Live roster X-ray
See your entire current player list classified in one pass: banned elsewhere, alt of a banned account, cheat-shop customer, seller. Not just new joins — everyone already online.
roster · bulk classify · O(1) per player
03
Action per category
Decide what each category earns: alert only, kick, or ban. Confirmed sellers can be banned while a fuzzy name match only raises an alert — a name collision alone never kicks anyone.
banned→kick · seller→ban · name→alert
04
Alerts where your staff already are
Flagged players land in your Discord as a live message with their connect identifiers and in-game slot ID, and the same message updates itself when they leave.
discord · slot id enriched · leave-edit
05
Allowlist and appeals
A streamer or staff member whose name collides with a banned record can be allowlisted so they are never re-flagged. Kicked players get an appeal link you review.
allowlist · appeal token · owner review
06
Cross-server evidence
Argos records come from monitored cheat servers, not from one owner’s grudge: ban logs, cheat-shop customer roles, support tickets and public-message signals.
110,000+ bans · cross-server archive
file 02 / 02 · coverage
Guard covers the FiveM side of your community. For the Discord side see Argos Sentry Discord server protection, and the free and premium plan comparison covers both. To screen a player earlier still — at the application stage, before they ever connect — the pre-whitelist vetting guide walks through it step by step.
>_ one resource
Screening starts at the next connect.
Register your server in the panel, download the Argos resource, and Guard starts screening immediately. Setup help and launch news land in the Argos Discord first.
Frequently asked questions
How do I stop cheaters getting into my server?
The check has to run before the player is inside. As a player connects, Guard compares their identifiers (license, Steam, Discord) against cross-server ban records and cheat-network memberships, and can reject the connection on a match. A check afterwards only limits the damage.
If I ban a cheater, will they come back on a new account?
Usually yes — a ban only closes the account in front of you. When they return they still have to reuse the same game-account traces (license, Steam), which is why Guard checks identifiers at connect time rather than names.
Does it work alongside my existing anti-cheat?
Yes. Guard runs as a separate server-side resource and does not touch your in-game detection layer. Anti-cheat catches cheating while it runs; Guard stops a known player from getting in at all.
What happens if it blocks the wrong person?
The appeal path is open: a rejected player can be given an appeal link, and an approved appeal adds them to an allowlist so the same reason does not block them twice. Automatic action rests on identifier matches only; a name similarity alone is never an action reason.
Do I choose what happens on each kind of match?
Yes. Per category — banned record, alt account, seller customer, name similarity — you set alert, kick or ban from the panel. Hard evidence runs as a rule; name similarity goes to a review queue.