FiveM Guide

HOW TO INSTALL FIVEM SCRIPTS

A complete step-by-step guide for new server owners. Learn how to add scripts to FiveM the right way — covering both Escrow-protected and Open Source resources, server.cfg setup, dependencies, and common troubleshooting.

BEFORE YOU BEGIN

You'll need a working FiveM server (Windows, Linux, or a hosted panel like Zap-Hosting / txAdmin), file access via FTP or the panel's file manager, and a text editor such as VS Code. If you're on a shared host, make sure you can edit server.cfg.

INSTALLATION STEPS

01Download the script

After purchase, open your Dashboard → Downloads and download the latest .zip for the script. Always use the newest version — older releases may be missing bug fixes and framework updates.

02Extract into your resources folder

Unzip the file into your FiveM server's resources/[custom]/ directory (or any nested category folder loaded by server.cfg). Keep the original folder name — resource names in fxmanifest.lua and server.cfg must match exactly.

03Install required dependencies

Check the script's README for required resources such as ox_lib, oxmysql, es_extended, qb-core, or ox_target. Install and ensure them BEFORE the script — missing dependencies are the #1 cause of failed startups.

04Edit config.lua

Open config.lua in the resource folder. Set Config.Framework (ESX / QBCore / Standalone), enable the correct target/inventory bridges, and adjust prices, jobs, and locale. Job names are case-sensitive.

05Add ensure to server.cfg

Add ensure your_script_name to server.cfg below its framework and any shared dependencies. Order matters: dependencies must load first, or the script fails to reference their exports.

06Start the server and verify

Boot the server and watch txAdmin or the console. A successful install prints a version banner and dependency check. If anything is missing, the log tells you the exact resource name to install.

ESCROW VS OPEN SOURCE

FiveM scripts ship in two flavors. The install flow is identical, but a few details differ once the resource is on your server.

Escrow scripts

Encrypted files load through Cfx.re asset escrow — your Tebex account must own the license.
Only config.lua, locales, and UI files are editable.
Server console must show your Cfx account linked, or the resource refuses to start.

Open Source scripts

Full Lua source — modify any file to fit your server's logic.
No Cfx account link required; the resource runs anywhere.
Keep a clean backup of the original before editing so you can diff against updates.

EXAMPLE SERVER.CFG ORDER

Load order matters. Ensure shared libraries and your framework first, then individual scripts.

# Shared libraries
ensure oxmysql
ensure ox_lib
ensure ox_target

# Framework (choose one)
ensure es_extended        # ESX
# ensure qb-core          # QBCore

# Your scripts
ensure my_new_script

COMMON PROBLEMS

Resource couldn't be started

The console prints the exact reason. Usually a missing dependency (install it and add to server.cfg) or a syntax error in config.lua (a stray comma or missing quote).

Attempt to index a nil value (ESX / QBCore)

The framework isn't ensured before the script. Move the framework's ensure line above the script in server.cfg and restart.

Escrow: this asset was not granted to this account

The Cfx account linked to your server doesn't own the license. Link the correct account in txAdmin or move the purchase to that account on Tebex.

UI opens as a blank white box

A NUI file failed to load. Restart the resource, clear the FiveM client cache, and confirm the html/ folder was extracted alongside the Lua files.

Still stuck?

Our team helps every buyer get their scripts running. Open a support ticket.

Visit support