FAM Tools
Sign in
Core · Cfx.re

cfx-server-data for FiveM

What it is

The official base resource set every FiveM server starts from: mapmanager, chat, spawnmanager, sessionmanager, hardcap and friends.

cfx-server-data is the pile of resources a blank FiveM server needs before it can accept a connection. It is unglamorous and almost never edited, but knowing what is in it explains a surprising number of 'why does my server do that' questions — including which resource decides that a loading screen is allowed to stay up.

Official documentation Repository All resources

At a glance

MaintainerCfx.re
Latest releaseRolling — no tagged releases
Last code change2026-08-24
Licencesee the repository
Written inLua
GitHub stars415
StatusActive

Figures read from the repository on 2026-09-22.

What starts, in what order, before a player is in the worldFXServer starts, txAdmin supervises it, the base resources come up, then the database layer, then the framework, then everything else. The loading screen is shown from the moment the client connects until a script tells the game to hide it.FXServer+ txAdminBase resourcessessionmanager, hardcapoxmysqldatabaseFrameworkesx / qb / qbxYour scriptsLoading screen visible — from connection until shutdownLoadingScreen() or the first spawnA player stuck after the loading screen is almost never the loading screen: nothing spawned them.
What starts, in what order, before a player is in the world

Why servers run it

  • It is the reference for what a minimal working server contains.
  • mapmanager decides the gametype and map, which is what a 'no maps found' console error is about.
  • sessionmanager and hardcap own the connection and slot handling every server depends on.
  • spawnmanager is the piece a custom spawn script has to replace or cooperate with.

Installing cfx-server-data

  1. 1. Clone it into resources

    A server built by txAdmin already has it. A hand-built one needs it.

  2. 2. Ensure the essentials

    mapmanager, chat, spawnmanager, sessionmanager, basic-gamemode and hardcap, in that order, before your own resources.

  3. 3. Replace rather than delete

    If you write your own spawn handling, stop spawnmanager — do not delete it, because other resources check for it.

Working examples

The minimum viable server.cfg block

ensure mapmanager
ensure chat
ensure spawnmanager
ensure sessionmanager
ensure basic-gamemode
ensure hardcap

# then your own
ensure my_loadingscreen
ensure my_framework

What goes wrong

Deleting basic-gamemode without a replacement leaves a server that starts and never spawns anybody.

Two spawn managers — the bundled one and a framework's — fight over the first spawn, which is the usual cause of a player stuck on a black screen after the loading screen ends.

cfx-server-data — questions people ask

Do I need all of cfx-server-data?
Not all, but more than you would guess. sessionmanager and hardcap are not optional; basic-gamemode can be replaced by a framework's own spawn handling.
My players get stuck after the loading screen. Why?
Almost always nothing spawned them: no gametype, a stopped spawnmanager, or two spawn systems cancelling each other out. The loading screen is innocent — it is waiting to be told the player is in the world.

Runs alongside

txAdmin

The web panel bundled with every FXServer build: process management, recipes, players, bans, scheduled restarts and live console.

es_extended (ESX Legacy)

The original FiveM roleplay framework, still running a very large share of live servers — jobs, money, society accounts and a huge script catalogue.

qb-core (QBCore)

The roleplay framework most new FiveM servers are built on, with the largest modern script ecosystem and a one-click txAdmin recipe.