Join Screening
Join screening runs while a player is still on the FiveM connecting screen, before they load into your server. CXA checks their identifiers, their name, your ban list, the CXA network, duplicate sessions and, if you want, VPNs, and turns the player away with a clear message when something is wrong.
Join Screening Also Enforces Bans
The ban check is one of the join screening steps. If you switch off Connection checks, banned players are no longer stopped when they connect. Turn off single checks instead of the whole group.
How It Works
FiveM lets a server hold a connecting player on the loading card for a moment and show them short status lines. This is called deferrals. CXA uses this pause to run its checks in a fixed order. The first check that fails ends the connection, and the player sees why.
- Identity: the card shows
Verifying your identity.... CXA checks that the player has every required identifier, for example a Rockstarlicense. - Name: the name filter checks length, HTML characters and blocked words.
- Ban list: the card shows
Checking ban records.... CXA looks the player up in your ban list by identifiers and hardware tokens. Right after a server start, this step waits until the ban list has loaded, for at most 15 seconds. - CXA network: the card shows
Checking your account on the CXA network.... CXA asks the network about global bans and account trust. - Duplicate session: CXA checks that the same account is not already playing on your server.
- VPN: if the VPN check is on, the card shows
Checking your connection...and CXA asks your VPN provider about the player's IP. - Join: all checks passed and the player loads in.
Players whose identifiers are in the Bypass Identifiers list skip steps 2 to 6. The required identifiers check still applies to them. During join screening CXA only uses that Identifiers list; txAdmin logins, ACE permissions and framework groups are not used at this point. See Staff Bypass.
Your own rules on the playerConnecting event run alongside these steps. They are explained under Rules at Join.
Setting It Up
Open Configuration → Connection in the web panel. The section has four groups, each with its own switch:
| Panel group | Config key | What it controls |
|---|---|---|
| Connection checks | Config.Connection.Enabled | The whole join screening, including the ban check |
| Duplicate accounts | Config.Connection.DuplicateCheck | Same account joining twice |
| Name filter | Config.Connection.NameFilter | Blocked player names |
| VPN / proxy check | Config.Connection.VpnCheck | VPN and proxy connections |
These are the defaults, as they appear in config.lua. With a license, the values you save in the panel replace them.
Config.Connection = {
Enabled = true,
LogBannedAttempts = true, -- Logs banned players trying to join (Connections webhook)
RequiredIdentifiers = { 'license' }, -- e.g. { 'license', 'steam', 'discord' }
DuplicateCheck = { -- Same account joining twice
Enabled = true,
Identifiers = { 'license', 'license2' }, -- A match on any of these counts as duplicate
Action = 'reject', -- 'reject' the new connection or 'drop_old' session (crash friendly)
Log = true,
Mention = '@everyone', -- Mention added to the duplicate log, '' to disable
},
NameFilter = { -- Blocks player names
Enabled = true,
MinLength = 2,
MaxLength = 32,
Words = { 'lynx', 'eulen', 'hammafia', 'desudo', 'brutan', 'skript.gg', '<script', 'http://', 'https://' },
BlockHtml = true, -- Names with < or > (script / meta tag injection in logs and panels)
AlphanumericOnly = false, -- Only a-z, 0-9, space, _ . - are allowed
},
VpnCheck = { -- Provider and key are in sv_config.lua
Enabled = false, -- [PERF] One HTTP request per new IP (cached), slightly slower joins
BlockOnError = false, -- Reject the player when the API fails
Timeout = 4000, -- ms to wait for the API
CacheMinutes = 120, -- Results are cached per IP
Log = true,
},
}Required Identifiers
An identifier is an account ID FiveM gives a player, for example license:... from their Rockstar account or discord:... from Discord. Required identifiers (RequiredIdentifiers) lists the types a player must have. You can pick license, license2, steam, discord, xbl, live and fivem. The default is { 'license' }.
A player without one of them sees A valid discord identifier is required to join this server. Make sure the related application is running and linked., with the missing type in place of discord. Players only get an identifier when the matching app or account is running and linked to FiveM, so every type you add turns some honest players away. Require only what your server really needs, for example discord if your whitelist runs on Discord.
Duplicate Accounts
The duplicate check compares the identifiers in Compared identifiers (DuplicateCheck.Identifiers) with the players who are already online. One match counts as a duplicate. The default compares license and license2, the two Rockstar license IDs.
Action (DuplicateCheck.Action) decides which session stays:
| Panel option | Value | What happens |
|---|---|---|
| Reject new connection | reject | The new connection is refused. The player who is already online stays. |
| Drop old session (crash friendly) | drop_old | The session that is already online is removed with Your account connected from another session. and the new connection goes through. |
drop_old is called crash friendly because of how FiveM handles crashes. When a player's game crashes, the server keeps their old session for a while until it times out. With reject, that player cannot reconnect until then and sees An account with the same identifier is already connected. If you just crashed, wait a moment and try again. With drop_old, the old session is closed and they get straight back in. The trade-off: anyone who logs in with the same account removes the player who is currently online.
Log (DuplicateCheck.Log) writes a Duplicate Account entry to the Connections channel. Mention (DuplicateCheck.Mention, up to 64 characters) is added to that log message. The default @everyone pings everyone who can read the channel. Use a role mention like <@&ROLE_ID> or leave it empty.
Name Filter
The name filter checks the player's FiveM name. Colour codes such as ^1 are removed first, and the length is counted in characters, so names with accented letters are measured correctly.
| Option | Key | Default | What it does |
|---|---|---|---|
| Min length | NameFilter.MinLength | 2 | Shorter names are refused. Panel range 1 to 32. |
| Max length | NameFilter.MaxLength | 32 | Longer names are refused. Panel range 4 to 64. |
| Blocked words | NameFilter.Words | 9 entries | A name that contains one of these words anywhere is refused. Not case-sensitive. Up to 200 words. |
| (not in the visual editor) | NameFilter.BlockHtml | true | Refuses names with < or >, which could inject HTML into logs and panels. |
| (not in the visual editor) | NameFilter.AlphanumericOnly | false | When true, only English letters, digits, spaces and _ . - are allowed. |
Blocked words match inside other words. The default word lynx also blocks a player called Lynxie, so keep the list to words that are never part of a normal name.
BlockHtml and AlphanumericOnly have no field in the visual editor. To change them, click Import code in the Configuration tab, paste the part below, press Validate, then Apply to draft and Save changes.
Config.Connection = {
NameFilter = {
BlockHtml = true, -- Refuse names with < or >
AlphanumericOnly = false, -- true = only English letters, digits, spaces and _ . -
},
}A refused player sees Your name is not allowed on this server. Please change it and reconnect. The Blocked Player Name log shows the reason: the matched word, or length, html or symbols.
VPN / Proxy Check
[PERF] The VPN check asks an outside service whether the player's IP belongs to a VPN or proxy. That is one web request for every new IP. Results are cached per IP, but joins get slightly slower. It is off by default.
| Option | Key | Default | What it does |
|---|---|---|---|
| VPN / proxy check | VpnCheck.Enabled | false | Turns the check on. |
| Block on API error | VpnCheck.BlockOnError | false | When the service fails or does not answer in time, true refuses the player, false lets them in. |
| Timeout | VpnCheck.Timeout | 4000 ms | How long CXA waits for the answer. Panel range 500 to 15000 ms. |
| Cache | VpnCheck.CacheMinutes | 120 min | How long a result is remembered per IP. Panel range 1 to 10080 minutes. |
| Log | VpnCheck.Log | true | Writes a VPN Connection Blocked log to the Connections channel. |
The check is skipped for local and private network addresses such as 127.0.0.1, 10.x.x.x and 192.168.x.x. Failed lookups are not cached, so CXA asks again on the next attempt. The cache is cleared every time the anticheat reloads, for example after you save a new config.
Pick the provider and its key in the panel under Webhooks & keys → API keys → VPN provider and VPN API key. Two providers are supported:
| Provider | Value | Key |
|---|---|---|
| proxycheck.io | proxycheck | Optional. Works without a key with a low daily limit. |
| iphub.info | iphub | Required. |
You can also set them in sv_config.lua, which never leaves your server:
SvConfig.Vpn = {
Provider = 'proxycheck', -- 'proxycheck' (proxycheck.io) or 'iphub' (iphub.info)
ApiKey = '', -- proxycheck works without a key (low daily limit), iphub requires one
}With UsePanelSecrets = true in SvConfig.License (the default), the panel wins. The provider chosen in the panel is always used, and a key saved in the panel replaces the one in sv_config.lua. So with the default settings, choose the provider in the panel.
A player on a VPN sees VPN or proxy connections are not allowed on this server. If the lookup fails and Block on API error is on, they see Your connection could not be verified, please try again later.
Banned Join Attempts
The ban check itself has no switch: it always runs while Connection checks are on. A banned player sees the ban screen with the ban ID, the reason, the expiry and your appeal link (Config.AppealUrl). If Extend identifiers is on in the ban settings, new identifiers and hardware tokens from the attempt are added to the ban. See Bans & the CXA Network.
Log banned join attempts (LogBannedAttempts, default true) writes a Banned Player Tried To Connect entry with the ban ID, reason and expiry to the Connections channel. Turning it off only stops the log; the player is still refused.
Network Check, Global Bans and Account Trust
When the network check is on and your license is active, CXA asks the CXA network about every connecting player. The answer can turn the player away for three reasons:
- They were automatically banned on other CXA servers and you enforce global bans. See Bans & the CXA Network.
- Their account is below the trust level you require. See Account Trust.
- They lack an account link you require, for example Discord. See Account Trust.
The settings are in Configuration → Network & trust → Network check on connect:
| Option | Key | Default | What it does |
|---|---|---|---|
| Network check on connect | Config.NetworkCheck.Enabled | true | Asks the network about every connecting player. |
| Timeout | Config.NetworkCheck.Timeout | 3000 ms | How long CXA waits. Panel range 500 to 10000 ms. |
| Let players in when unreachable | Config.NetworkCheck.FailOpen | true | If the network does not answer in time, the player joins normally. |
[PERF] This is one HTTPS request per connecting player and adds at most Timeout milliseconds to the join. Every flag the network reports is logged to the Connections channel as Network check: <kind> with the trust score, the reason and the action.
Keep "Let players in when unreachable" On
With FailOpen = false, nobody can join while the network cannot be reached. Players see Security check could not be completed, please try again in a minute.
Rules at Join
Security rules with the event playerConnecting run when a player connects. They can check the name, the age of the Discord account, whether Discord or Steam is linked and the number of identifiers. A rule with the block or kick action refuses the player with You cannot join this server: <reason>, where the reason is the text you wrote for the rule. The Rule Engine page explains the condition language.
Like the other steps, these rules skip players whose identifiers are in the Bypass Identifiers list.
Messages Players See
These are the texts players see on the connecting screen with Config.Locale = 'en'. With the Language setting on Turkish (tr), players see the Turkish versions. You can change any of them in locales.lua; the panel does not override that file.
| Locale key | When it appears | Text |
|---|---|---|
connect_checking | First step, every connection | Verifying your identity... |
connect_missing_identifier | A required identifier is missing | A valid %s identifier is required to join this server. Make sure the related application is running and linked. |
connect_bad_name | The name filter refused the name | Your name is not allowed on this server. Please change it and reconnect. |
connect_checking_ban | Ban check step | Checking ban records... |
connect_checking_network | Network check step | Checking your account on the CXA network... |
connect_global_ban | Global ban, when you enforce them | You are banned on the CXA Anticheat network and cannot join %s. If you believe this is a mistake, contact the server that banned you. |
connect_low_trust | Account trust too low | Your account did not pass this server's security check (TrustScore: %s). Link your Discord, Steam and Cfx.re accounts to FiveM or try again later. |
connect_missing_account | A required account link is missing | This server requires a linked account: %s. Link it in FiveM settings and reconnect. |
connect_network_unavailable | Network unreachable and FailOpen = false | Security check could not be completed, please try again in a minute. |
connect_duplicate | Duplicate session, Action reject | An account with the same identifier is already connected. If you just crashed, wait a moment and try again. |
connect_duplicate_old | Shown to the old session, Action drop_old | Your account connected from another session. |
connect_checking_vpn | VPN check step | Checking your connection... |
connect_vpn | VPN or proxy found | VPN or proxy connections are not allowed on this server. |
connect_vpn_error | VPN lookup failed and Block on API error is on | Your connection could not be verified, please try again later. |
connect_rule_blocked | A playerConnecting rule refused the player | You cannot join this server: %s |
%s is filled in by CXA: the identifier type, your server name (Config.ServerName), the trust band, the missing account or the rule reason.
Connection Logs
Join screening writes to the Connections webhook channel. Set it in the panel under Webhooks & keys → Discord webhooks → Connections, or in SvConfig.Webhooks.Connections in sv_config.lua. When the channel is empty, the Default webhook is used.
| Log title | Written when | Controlled by |
|---|---|---|
| Blocked Player Name | The name filter refused a player | Name filter switch |
| Banned Player Tried To Connect | A banned player tried to join | LogBannedAttempts |
Network check: <kind> | The CXA network reported a flag | Network check on connect |
| Duplicate Account | A second session of an online account | DuplicateCheck.Log, plus Mention |
| VPN Connection Blocked | The VPN check refused a player | VpnCheck.Log |
| Security rule matched | A playerConnecting rule matched | The rule's actions |
Every entry shows the player's name and identifiers. IPs appear only when Show IPs (Config.Logs.ShowIp) is on; the VPN log shows hidden otherwise. These logs go to Discord only. They are not listed in the panel's Detections tab. See Logging & Discord.
Recommendations
Recommended:
- Keep Connection checks on at all times, because the ban check lives here.
- Use
drop_oldif players often crash and complain that they cannot reconnect. - Replace the
@everyonemention with a staff role, or leave it empty. - Turn the VPN check on with Block on API error off first, and watch the VPN Connection Blocked logs for a few days.
- Put your owner's identifier in the Bypass Identifiers list, so you can always join even with a test name or a VPN.
Avoid:
- Requiring
steam,discordorxbl"just in case". Every required identifier turns away honest players who don't use that app. - Short or common words in Blocked words, because they match inside normal names.
- Turning on
AlphanumericOnlyon a server with Turkish or other non-English names. Letters likeşoréare refused. - Setting Let players in when unreachable to off unless you accept that nobody can join during an outage.
Related Features
Staff Bypass
- Only the Bypass Identifiers list is used during join screening.
- Listed players skip every step except the required identifiers.
- See Staff Bypass.
Bans & the CXA Network
- The ban check matches identifiers and hardware tokens from your ban settings.
- Global bans are enforced here when you opt in.
- See Bans & the CXA Network.
Account Trust
- The trust check and required account links run in the network check step.
- See Account Trust.
Rule Engine
playerConnectingrules add your own conditions, for example new Discord accounts.- See Rule Engine.
Logging & Discord
- All join screening logs use the Connections channel.
- See Logging & Discord.
Limitations
- Join screening only sees what FiveM provides at connect time: name, identifiers, hardware tokens and IP.
- Duplicate checks only compare against players who are fully online.
- The VPN check depends on your provider. Its answer, its daily limit and its uptime are outside CXA's control.
- The network check needs an active license and a connection to
codexart.net.
Common Problems
Players See "A valid ... identifier is required to join this server"
What you see: Players are refused with A valid steam identifier is required to join this server. or the same text with another type.
How to fix it:
- Remove types you don't really need from Required identifiers. The default is only
license. - Tell players to open the related app (Discord, Steam) before starting FiveM and to link it.
- For
steam, FiveM only provides Steam identifiers when your server has a Steam Web API key set (steam_webApiKeyinserver.cfg).
A Player Who Crashed Cannot Reconnect
What you see: After a crash, the player sees An account with the same identifier is already connected. If you just crashed, wait a moment and try again.
How to fix it:
- Wait until the old session times out, or kick the old session.
- Switch Duplicate accounts → Action to Drop old session (crash friendly).
Names With Turkish or Accented Letters Are Refused
What you see: Players with names like Şahin see Your name is not allowed on this server.
How to fix it:
- Set
AlphanumericOnly = falsewith Import code. It only allows English letters. - Check the Blocked Player Name log: if the reason is a word, that word is inside the name. Remove it from Blocked words.
Joining Takes Longer Than Before
What you see: The connecting card stays on Checking your account on the CXA network... or Checking your connection... for a few seconds.
How to fix it:
- Lower the VPN Timeout and the network check Timeout. The join never waits longer than these values.
- Turn the VPN check off if you don't need it.
- Repeat joins from the same IP are faster, because VPN results are cached for
CacheMinutes.
VPN Players Still Get In
What you see: Players you know use a VPN join without a VPN Connection Blocked log.
How to fix it:
- Make sure VPN / proxy check is on and saved.
- Check the provider in Webhooks & keys → API keys. With the default
UsePanelSecrets = true, the panel's provider is used, not the one insv_config.lua. - Without a key, proxycheck has a low daily limit. When it is used up, lookups fail and players are let in unless Block on API error is on. Add a key.
- Players in the Bypass Identifiers list are never checked.
A Banned Player Was Able to Join
What you see: A player with an active ban joined the server.
How to fix it:
- Check that Configuration → Connection → Connection checks is on.
- Check that the player is not in the Bypass Identifiers list.
- Compare the player's identifiers with the ban. Bans only match the identifier types in Match identifiers and, if Match hardware tokens is on, hardware tokens. See Bans & the CXA Network.
Nobody Can Join and Players See "Security check could not be completed"
What you see: Every player gets Security check could not be completed, please try again in a minute.
How to fix it:
- Turn Let players in when unreachable back on.
- Check that your host allows outgoing HTTPS connections to
codexart.net.
Connection Logs Don't Appear in Discord
What you see: Players are refused, but the Connections channel stays empty.
How to fix it:
- Set a Connections webhook, or a Default webhook as fallback, in Webhooks & keys.
- Check that Configuration → Logs → Logging → Discord webhooks (
Config.Logs.Discord) is on. - Remember that these logs are Discord only; they are not in the panel's Detections tab.
© 2026 CodeXart Studios · CXA Anticheat