FiveM Overview

Every FiveM resource has its own installation and configuration guide. This page lists what is available, which frameworks each one supports, and the conventions the guides share.

Resources

RX Reports V1 is the only resource on this list that needs a database; it ships an SQL file to import. The others store nothing of their own, or keep their data client-side as RX HUD V3 does with each player’s layout and settings.

Shared conventions

Start order matters

Resources that integrate with a framework detect it on startup. If the framework object does not exist yet, detection fails and the resource behaves as though no framework is present. Always start qb-core, es_extended, or qbx_core before the resource that depends on it.

Folder names

Each installation guide names the default extracted folder. If you rename the folder, the ensure line must use your name exactly. A mismatch here is silent: the resource simply never starts.

Restart after editing the config

Configuration is read on start. Changing config.lua while the server is running has no effect until the resource restarts, and a client that is already connected keeps the old values until then.

Debug mode

Every resource ships a debug flag, disabled by default. Enable it while diagnosing a specific problem to see what the resource receives from the framework, then disable it again so the console stays readable.

Running only one HUD

RX HUD V1, V2, and V3 each replace the player interface and take over the minimap. Run one of them, and stop the HUD your framework ships with, such as qb-hud. Two HUDs at once leave duplicate status bars and fight over the same minimap state.

Where to start

If you are setting up a server for the first time, install in this order:

1. Your framework.
2. A loading screen, so players see something while the rest connects.
3. A HUD, after stopping the framework’s default one.
4. Everything else.