> For the complete documentation index, see [llms.txt](https://docs.fivemdevlab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fivemdevlab.com/home.md).

# Home

Dev Lab builds complete, ready-to-run FiveM server bases. Rather than a script you bolt onto an existing server, each one is the whole thing - framework, gameplay, interface, admin tools - configured and working out of the box. This space documents both of them.

### What is documented here

dl-rz (Combat/PvP) and dl-rp (Roleplay/Economy) each have their own handbook. They are separate products and share no configuration. Pick yours in the sidebar and stay in that section; nothing in one applies to the other.

### The Setup Wizard

Before you touch a single config file, there's the Setup Wizard - a first for FiveM base files, and the fastest way to stand your server up. Drop the files in, boot the server, and run **/setupserver** in-game. Instead of hunting through Lua, you configure your server from one menu:

* **Branding** - server name, logo, colours, Discord link, store URL
* **Interface** - a page per UI, where you pick its style, layout, theme, border radius and watermark
* **Live 1:1 previews** - you're looking at the real interface as you choose, not a screenshot
* **Applies to everyone instantly** - no restart, no relog
* **Saved to your database** - your choices survive restarts
* **Owner-locked after first run** - once you're set up, it can't be reopened by anyone else

The wizard is for branding and the look of the UI. Everything below it - gameplay rules, zones, jobs, permissions, weapon stats - still lives in Lua, documented page by page. Think of the wizard as the front door and the config files as full control once you're inside.

### Finding things

The sidebar is grouped by product, then by area - getting started, gameplay, menus, interface, admin, and so on. Every page in a handbook is listed there; nothing is hidden.

Each product's home page is the better starting point. It carries an ordered first-run path and a "find it fast" table that maps what you want to change to the page that covers it. DL-RZ also has a full file map, listing every configurable file against its page.

Search (top of the sidebar) is usually quickest once you know the vocabulary. Searching the exact config key - borderRadiusByScript, PrioRoles, reviveZones - will land you on the page that documents it, because every page names its keys verbatim.

### How a page is laid out

Every page follows the same shape:

* The file it documents, named at the top
* Every field, with a one-line description of what it does
* A Lua example you can paste straight in
* Links to whatever it relates to

Where a setting has a non-obvious consequence - a bucket range that must not collide, a key you cannot rename after launch, a default that locks players out if you get it wrong - it is called out inline rather than left for you to discover on a live server.

### Conventions that apply to both bases

**Set up in-game, then fine-tune in Lua.** The Setup Wizard handles branding and UI look from a menu and writes those choices to your database for you - no manual database editing. Everything deeper is Lua: edit a config file, restart the resource, done. No build step.

**Turning a feature off is one word.** Each pack has an Enabled flag at the top of its own config. Set it to false. You never edit server.cfg or a fxmanifest.lua to disable something.

**Secrets stay server-side.** Bot tokens, webhook URLs and staff permissions belong in server-only files - sconfig.lua on DL-RP, server\_config.lua on DL-RZ. A shared config.lua is downloaded by every client, so anything in one can be read by any connected player.

**The interface ships prebuilt.** Colours, themes, layouts and text are all set through the Setup Wizard or in Lua and read at runtime; you never need Node or a build step to change how the UI looks.

**Discord role gating needs your own bot.** Admin powers, priority queue, VIP tabs and chat tags all resolve through it. Until it is configured nobody matches a role, including you - so set it up before you start handing out permissions.

### Support

Questions, bug reports and update notices go through discord.gg/devlab.