How to Install FiveM Scripts: A Complete Guide for Server Owners

Tutorials · 6 min read · Published: 2026-05-18 · Updated: 2026-06-08

Most FiveM script installation problems come down to three things: wrong folder location, dependencies not loaded before the script, or SQL not imported. This guide covers all of them.

Step 1: Get the script files

For scripts bought through Tebex and delivered via CFX Portal (the case for all Revo Scripts), you download from portal.cfx.re. Go to Assets → My Assets after your purchase confirmation email arrives. Scripts that use FiveM Escrow will download as a folder with some Lua files already compiled — this is normal and expected.

Free scripts are usually a direct GitHub download. Click the green Code button → Download ZIP, then extract it.

Step 2: Correct folder structure

Every FiveM resource needs to live inside your server's resources directory. The typical layout looks like this:

server-data/
└── resources/
    ├── [esx]/           ← framework resources folder
    │   ├── es_extended/
    │   └── esx_jobs/
    ├── [custom]/        ← your custom resources folder
    │   ├── revo-stock-trading/
    │   └── revo-fps-booster/
    └── [standalone]/    ← resources that work on any framework

Example resources folder layout. Square bracket folders are categories — not required, but highly recommended for organisation.

The square bracket folders are optional category folders. FiveM ignores them for resource loading purposes but they help keep your server organised. The critical rule: the resource folder name must match the folder that contains the fxmanifest.lua file.

WARNING: Do not rename resource folders after installation unless you also update every `ensure` line that references the old name in server.cfg. A renamed resource that is still ensured under its old name simply will not start.

Step 3: Check fxmanifest.lua dependencies

Open the resource's fxmanifest.lua file. Look for a `dependencies` or `dependency` block. These are other resources that must be running before this one loads.

fx_version 'cerulean'
game 'gta5'

description 'Revo FPS Booster'
version '1.0.0'

-- These must be loaded BEFORE this resource
dependency {
  'es_extended',  -- or 'qb-core' / 'ox_core' depending on your framework
  'ox_lib',
}

shared_scripts {
  '@ox_lib/init.lua',
  'config.lua',
}

client_scripts {
  'client/*.lua',
}

Example fxmanifest.lua showing dependency declarations.

Every resource listed in `dependency` must be ensured in server.cfg before the script that depends on it. Get this wrong and you will see "module not found" errors in the server console.

Step 4: server.cfg ensure order

The `ensure` keyword in server.cfg tells your server to load that resource on startup. Order matters — dependencies must come before dependents.

# Framework — always first
ensure es_extended

# Libraries — before any script that uses them
ensure oxmysql
ensure ox_lib

# Your custom scripts — after everything they depend on
ensure revo-stock-trading
ensure revo-fps-booster
ensure revo-server-backup

Correct ensure order in server.cfg. Libraries (oxmysql, ox_lib) must come before any script that imports them.

Step 5: Import SQL

Many scripts come with a .sql file in their folder. If yours does, you need to import it into your database before the server will work correctly. Use phpMyAdmin (available in most server control panels) or a MySQL client like TablePlus. Open your database, find the Import tab, select the .sql file, and run it.

TIP: Always import SQL on a test server before running it on your live server. A bad import can corrupt existing tables. Back up your database first with revo-server-backup or your hosting panel tools.

Step 6: Configure the script

Most scripts have a config.lua in their root folder. Read it before starting the server. Revo Scripts are heavily documented in the config — each setting has a comment explaining what it does and what values are valid. Change what you need, save, then restart the resource.

Common errors and fixes

• "Module not found: es_extended" — your framework resource is either not ensured or named differently. Check server.cfg and the exact folder name.
• "Failed to load resource" — usually a syntax error in a Lua file. Check the server console for the line number, or verify you have not accidentally edited an Escrow-protected file.
• "Unknown column X in SQL" — the SQL import either did not run or ran against the wrong database. Re-import and confirm you selected the right database.
• "oxmysql is not started" — you are trying to start a script before oxmysql. Move the `ensure oxmysql` line higher in server.cfg.
• Script starts but nothing works in-game — check that ox_lib is installed and ensured if the script requires it.

Back up your database before experimenting