Installing Resources and Scripts

FiveM – Installing Resources and Scripts

This guide shows you how to install resources and scripts on your FiveM server – from ESX to QBCore to individual scripts.

What are resources?

Every function on a FiveM server is a resource – jobs, inventories, vehicles, HUDs and entire frameworks. Resources are located in the resources/ folder of your server and are activated in the server.cfg.

Step 1: Download the resource

• Most FiveM resources can be found on GitHub or in the Cfx.re Forum
• Download the resource as ZIP or clone it via Git
• Make sure the resource is compatible with your framework (ESX, QBCore, Standalone)

Step 2: Upload the resource to the server

1. Extract the downloaded file
2. Upload the extracted folder to your server's resources/ directory
3. The folder name is the resource name – rename it if needed

Step 3: Activate the resource in server.cfg

Open your server.cfg and add the resource:

# Simple resource
ensure my-resource

# Or with start priority
start my-resource

Pay attention to order: Dependencies (frameworks, libraries) must be listed before the resources that use them.

Step 4: Set up database (if needed)

Many resources require a MySQL/MariaDB database:

1. Import the included .sql file into your database
2. Enter the database credentials in the resource's config.lua

Step 5: Start and test the resource

# In the server console
start my-resource

# Or in-game (as admin)
/start my-resource

Check the console for error messages. If the resource runs without errors, it's active.

Typical resource folder structure

my-resource/
├── fxmanifest.lua     # Metadata (name, version, dependencies)
├── client/
│   └── client.lua     # Client-side code
├── server/
│   └── server.lua     # Server-side code
├── config.lua         # Configuration
└── html/              # NUI interface (optional)

Common problems

• Resource won't start: Check the console for errors. Missing dependencies or wrong framework version are the most common causes
• Script doesn't work in-game: Check if the client part loads correctly. Some scripts need a trigger
• Database error: Check if MySQL is running and the credentials in the config are correct