NewsFiveM

FiveM xbl and live Identifiers Removed: Fix Your Bans (2026)

Since 27 April 2026, FiveM no longer returns xbl and live player identifiers. What broke, which identifiers to use instead and how to fix ban scripts.

Updated Oct 3, 2026 · 5 min read

On this page

FiveM stopped returning the xbl: and live: player identifiers on 27 April 2026, as Cfx.re announced on 14 April 2026 in a deprecation notice. GetPlayerIdentifiers no longer includes Xbox Live or Microsoft account IDs, so bans, whitelists or anticheat checks keyed to them need moving to license:, fivem: or discord:.

What did Cfx.re change?

Cfx.re removed two identifier types from the results of the GetPlayerIdentifiers native (and the related identifier functions scripts use):

Identifier What it was Status since 27 April 2026
xbl: Xbox Live account ID Removed
live: Microsoft account PUID Removed

Cfx.re gave the reason as "ongoing efforts to improve platform integrity and protect our players' privacy", and asked owners to "review your resources to confirm nothing relies on these identifiers". The change was also posted by the official @FiveM account on X.

Which identifiers can I still use?

The common identifiers most servers already rely on are not part of the deprecation. These are the ones worth building on:

Identifier Comes from Good for
license: The player's Rockstar license Main key for bans, characters and money
license2: A second Rockstar license identifier Extra ban matching
fivem: The player's Cfx.re account Admin permissions, txAdmin admins
discord: A linked Discord account Whitelists, roles, Discord bots
steam: Steam, when a Steam Web API key is set Older ESX servers, Steam checks
ip: The connection's IP Short term matching only, it changes

license: is the safest primary key because every player who owns GTA V on PC has one and FiveM always sends it. discord: only appears if the player has Discord running and linked, and steam: needs the server's steam_webApiKey and Steam running on the player's PC.

What this means for your server

Most servers noticed nothing. If you were affected, it showed up in one of these ways:

  • Bans stopped matching. A ban saved only as xbl:2535... or live:... now matches nobody, so the banned player can walk back in.
  • Whitelists rejected people. A whitelist that compared xbl: or live: IDs started refusing players who were on it.
  • Scripts threw errors. Code that assumed an xbl: entry existed and indexed it straight away can fail with attempt to index a nil value.
  • Anticheat flagged the wrong players. Tools that matched alt accounts by Microsoft IDs lost that signal.

How do I fix bans and scripts that used xbl or live?

Search your resources for the old prefixes, move anything that depends on them to another identifier, and re-check your ban lists.

  1. Search your resources. From your server's resources folder, look for the prefixes:
grep -rn --include=*.lua -e "xbl:" -e "live:" resources/

On Windows, use the search in your code editor for xbl: and live: across the folder.

  1. Change the lookup. Replace code that picks the Xbox identifier with one that picks the license. A safe pattern in Lua:
local function getLicense(src)
    for _, id in ipairs(GetPlayerIdentifiers(src)) do
        if id:sub(1, 8) == "license:" then return id end
    end
    return nil
end

Always handle nil, because any identifier other than the license can be missing.

  1. Fix the database. If a ban or whitelist table stored only xbl: or live: values, those rows are now useless. Ban records that also stored license: keep working. For rows with nothing else, the player has to be banned again by license when they next connect.

  2. Check txAdmin. txAdmin bans store every identifier the player had at the time, so most txAdmin bans still match on license: or fivem:. Bans created from the console with only an Xbox ID do not.

  3. Restart and test. Restart the server, join with a test account and confirm your framework loads your character and that a test ban blocks the right account.

Should I store more than one identifier?

Yes. Store every identifier you get when a player first joins, and match bans on any of them. Players can unlink Discord or skip Steam, so a ban system that depends on one optional identifier is easy to dodge. Keeping license:, license2:, fivem: and discord: together, as txAdmin does, is the most reliable approach.

Your FiveM server on GamezServers

On our FiveM servers txAdmin handles bans and the whitelist with identifiers that were not affected, and the Players view in your panel lets you kick troublemakers directly. If you run a whitelisted roleplay community, our txAdmin whitelist guide and how to make yourself admin on a FiveM server use license:, fivem: and discord: identifiers throughout. Take a one click backup before you edit ban tables.

FAQ

When were the xbl and live identifiers removed from FiveM?

They were removed on 27 April 2026. Cfx.re announced the change on 14 April 2026 on the Cfx.re forum.

Why did FiveM remove Xbox Live identifiers?

Cfx.re said the change supports platform integrity and player privacy. The two identifiers come from Microsoft's account system and could be used to look up and cross reference player accounts.

What is the best identifier to ban FiveM players with?

Use license: as the main key and store license2:, fivem: and discord: alongside it. Matching on several identifiers makes bans much harder to get around.

Do I need to update QBCore, Qbox or ESX?

The frameworks key players on their Rockstar license (license: or license2:) by default, so a standard install was not affected. Check custom ban, whitelist and anticheat scripts, which are where xbl: and live: were usually used.

Will FiveM remove other identifiers?

Cfx.re has not announced any other removals. Keeping several identifiers per player protects you if that ever changes.

Skip the setup. Your own FiveM server.

$4.99USD first month

Then $9.99/mo. Just trying it? $2.50 for 3 days

Keep reading