How to add FiveM scripts and resources without errors

Adding resources in FiveM looks trivial until the server won’t boot, the console shows Couldn't load resource or a new script takes down the entire framework. Most errors don’t come from the resource itself — they come from the wrong folder structure, an invalid fxmanifest, incorrect order in server.cfg or conflict with another script.

This guide is for anyone running their own FiveM server (Windows or Linux), who already has a framework installed (ESX or QBCore) and wants to add community or paid scripts without breaking anything. Estimated time: 10 to 15 minutes per properly tested resource.

Prerequisites

If your server is on a Linux VPS, connect via SSH first. On Windows, connect via RDP and open a PowerShell terminal in the server folder.

Understanding the structure of a resource

Before adding anything, it’s worth knowing what FXServer expects. A valid FiveM resource is a folder inside resources/ (or in subfolders prefixed with [category]) containing at least an fxmanifest.lua at the root. Without that file, FXServer ignores the resource — no matter how many .lua or .js files are inside.

The typical structure:

resources/
└── [scripts]/
    └── my-resource/
        ├── fxmanifest.lua
        ├── client.lua
        ├── server.lua
        ├── config.lua
        └── html/
            ├── index.html
            ├── style.css
            └── script.js

Folders in brackets ([scripts], [esx], [qb]) are just visual organization — FXServer scans them recursively. You can nest 2-3 levels deep without problems. Avoid more than that to keep maintenance simple.

The minimal fxmanifest.lua

Every resource needs to declare the API version and target game. The minimum viable file:

fx_version 'cerulean'
game 'gta5'

author 'Author name'
description 'Short description'
version '1.0.0'

client_scripts {
  'client.lua'
}

server_scripts {
  'server.lua'
}

shared_scripts {
  'config.lua'
}

fx_version 'cerulean' is the current recommended value (supports modern FiveM features). Older versions like adamant or bodacious still work but lose capabilities.

Adding a resource step by step

scp -r my-resource/ user@server-ip:/path/to/server-data/resources/[scripts]/

ls /path/to/server-data/resources/[scripts]/my-resource/

ensure my-resource

# Frameworks first
ensure qb-core

# Libraries and dependencies
ensure ox_lib
ensure oxmysql

# Gameplay scripts
ensure qb-multicharacter
ensure qb-spawn
ensure my-resource

refresh
ensure my-resource

Started resource my-resource

Verifying everything is working

In the server console, run resources to see the full list of active resources. Your resource name should appear with status started. If it shows up as stopped, it was recognized but isn’t running — check the ensure in server.cfg.

To test functionally, join the server with your FiveM client. Client-side scripts usually react to commands (/command), inventory items or automatic events. Open the F8 client console (~ or F8) — Lua or JavaScript errors on the client side show up there with a stack trace.

Common troubleshooting

”Couldn’t load resource X”

Almost always a missing or invalid fxmanifest.lua. Check:

• The file is named exactly fxmanifest.lua (lowercase, with .lua)
• It declares fx_version 'cerulean' and game 'gta5'
• Valid Lua syntax (balanced commas and quotes)

If the file is fine, confirm that the folder name matches exactly the ensure in server.cfg. On Linux, MyResource and myresource are different folders — case-sensitive.

”Error loading script” with a Lua error

The console shows the exact line of the error. Frequent causes:

• Framework variable used before the framework loaded (wrong order in server.cfg)
• Missing dependency (exports['ox_lib'] called without ox_lib running)
• Lua syntax broken by manual editing

To isolate: comment the resource in server.cfg, restart, then add resources one by one until you reproduce the error.

Server crashes on startup

Comment out every ensure except the core ones (mapmanager, chat, spawnmanager, sessionmanager, framework). Restart. If it boots without crashing, add resources one at a time until you identify the culprit. This process is slow but it’s the only reliable way when the error happens very early in the boot.

Conflict between two scripts on the same event

Two resources registering a handler for the same event (AddEventHandler('playerSpawned', ...)) may compete for execution order. FiveM doesn’t guarantee handler order across resources for the same event. Solution: explicitly declare a dependency in the fxmanifest.lua of the resource that must run later:

dependencies {
  'other-resource'
}

This guarantees other-resource loads first.

Next steps

With a clean structure and resources running stably, it’s worth digging into:

• Script optimization: identify resources that consume a lot of CPU using resmon on the client (Shift+~). Resources above 1.0ms client-side deserve review.
• Automated resource backups: versioning the resources/ folder in a private Git repo prevents losses when you break something while testing.
• Script whitelist: on roleplay servers, keeping a curated list of approved resources reduces bug and exploit surface.
• Separate databases per category: heavy scripts (jobs, inventory) can use isolated databases to reduce contention.

If you’re running FiveM in production with 32+ slots and want infrastructure that keeps low latency for the Americas, Hostini’s game servers deliver sub-30ms latency across the region with DDoS protection included in the price.