FiveM warns server owners, xbl and live identifiers ending soon

FiveM server scripts that still depend on xbl: or live: identifiers will lose those values on April 27, 2026, when Cfx.re removes both types from GetPlayerIdentifiers. Cfx.re said the change is not expected to affect the majority of servers, but it is a hard cutoff for any resource that still treats Xbox Live and Microsoft PUID as core identity fields.

The warning landed on April 14 and reads like the kind of backend cleanup that only becomes visible when a server starts rejecting the wrong player, skipping a ban check, or printing incomplete logs. Cfx.re’s own documentation spells out the identifier types it is phasing out, with xbl listed as Xbox Live and live as Microsoft PUID, while license, license2, and fivem remain in the mix. The platform also points server owners toward GetPlayerIdentifierByType when they only need one value, instead of looping through every identifier manually.

The real risk sits in older moderation and access-control workflows. In FiveM communities, identifiers often power whitelists, admin access, ban enforcement, and console logging, especially on custom resources written before newer platform assumptions became standard. Cfx.re’s playerConnecting documentation shows the pattern clearly: a connecting player’s license identifier is checked against a ban list, and the player is kicked if that match hits. Any server that built similar logic around xbl: or live: will need to replace those checks before April 27 or expect the workflow to fail at the exact moment it matters most.

The timing also fits a broader tightening of identifier exposure across the platform. In late 2024, Cfx.re said it would deprecate player identifiers from public players.json exposure and from the server list backend, while offering sv_exposePlayerIdentifiersInHttpEndpoint as a backward-compatibility option. By early 2025, users were still reporting console warnings about players.json no longer returning identifiers without authentication, showing that this April 2026 removal is part of a longer privacy and safety shift rather than a one-off change.

For servers that still run older moderation tooling, the checklist is simple: inspect every permission script, ban list, whitelist, audit log, and custom account-matching resource for xbl: and live:. The broader FiveM ecosystem is large enough that even a narrow identifier change matters, especially after Cfx.re said FiveM passed 300,000 concurrent players in 2023 and that more than 20 million unique players have used FiveM and RedM to date. On a platform that big, one small identifier swap can break a lot of quiet infrastructure all at once.