You found the perfect script, checked out, and now you are staring at a zip file wondering what happens next. Take a breath, because this is the easy part. Learning how to install fivem script files is a repeatable process, and once you have done it once you will do it half-asleep. This guide walks you through every step from the moment your order completes to the moment your new resource is running in-game, in plain language for newer server owners. Nothing here is hard, it just has an order to it.
Where Your Files Come From After Checkout
Right after payment, your download usually appears in two possible places. Simpler products give you a direct Tebex download link on the confirmation page and in your order email, and that link hands you a zip straight away. Many quality FiveM scripts, however, are escrow-protected, which means the code is encrypted and tied to your Cfx.re account through the creator's Keymaster. That is completely normal and nothing to worry about, it simply protects the developer's work while still letting your server run it.
For escrow assets, the one thing you must do is link your Cfx.re account so the product gets attached to your account. After that the resource shows up in your Keymaster portal and downloads from there. If a product asks for your Cfx.re account ID or FiveM license at checkout, that is why. Encrypted does not mean limited, the script still installs and runs exactly like any other, you just download it from the right place.
Unzip and Look at the Folder Structure
Unzip your download somewhere on your computer first, before touching the server. Inside you are looking for one resource folder, the one that contains an fxmanifest.lua (older scripts use __resource.lua). Open it up and sanity-check three things:
- Watch for double-nested folders. Sometimes you unzip and find
coolscript/coolscript/fxmanifest.lua. You want the inner folder, the one that actually holds the manifest, not the wrapper around it. - Rename the folder to a clean resource name, not a version string. A folder called
coolscript-v1.4.2should becomecoolscript. Avoid spaces and capitals. - Keep the name consistent, because whatever you name this folder is exactly what you will type later in
server.cfg.
Drop It in the Right Place
Resources live in your server's resources folder. You can place a script directly in there, but a tidy server groups things into bracketed category folders, like [scripts] or [jobs]. So your new script might land at resources/[scripts]/coolscript. FiveM loads everything inside bracketed folders automatically, so this keeps your server organized without any extra configuration. A clean structure now saves you real headaches when you have forty resources later.
Read the README Before Anything Else
This is the step everyone skips and everyone regrets. Open the included README, documentation file, or docs link and read it first. It tells you exactly which dependencies the script needs, whether there is a database step, and which config values matter. Five minutes of reading here prevents most first-run errors entirely.
Install Dependencies and Run the SQL
Most modern scripts depend on a few shared resources, and the script will not start without them. Common ones include:
oxmysqlfor database accessox_libfor menus, notifications, and callbacks- a framework such as ESX, QBCore, or Qbox
- a target system like
ox_targetorqb-target
Install any you do not already have, the README will list them. If the script ships with a .sql file, you must import it into your server's database (using a tool like HeidiSQL, phpMyAdmin, or your panel's database manager). That SQL creates the tables the script reads and writes, so skipping it is the number-one cause of "it starts but nothing saves."
Add It to server.cfg With the Right Load Order
A resource sitting in the folder does nothing until you tell the server to start it. Open server.cfg and add a line:
ensure coolscriptLoad order matters. Dependencies must start before the script that needs them, so a typical block looks like this:
ensure oxmysql
ensure ox_lib
ensure es_extended
ensure ox_target
ensure coolscriptThe resource name after ensure must match your folder name exactly, capitalization included.
Configure config.lua and Items
Open the script's config.lua and set it to your server. This is where you adjust things like which framework to use, prices, locations, and job names. If the script adds new usable items, the README will tell you to register those items in your framework or inventory (for example adding an item entry so ox_inventory or qb-inventory knows it exists). Do this now, before you start the server, so everything lines up on first boot.
Start It and Read the Console
Save everything, then start your server (or refresh and ensure coolscript from the live console). Now watch the server console and your in-game F8 console for messages. A clean start with no red text means you are likely good. If you see errors, do not panic, the console almost always tells you precisely what is wrong.
The Most Common First-Run Errors
- Script error or "attempt to index nil" / nil framework usually means a missing dependency or the wrong framework selected in
config.lua. Confirm the framework matches your server and that it starts before your script. - "Couldn't load resource" points at a bad folder name or a broken
fxmanifest.lua, often from that double-nested folder or a typo inserver.cfg. - Items or data not saving means the SQL was never imported. Run the
.sqlfile and restart.
Quick Post-Install Test Checklist
- Server console shows the resource starting with no red errors.
- The feature appears in-game (menu opens, target prompt shows, item works).
- Data persists after a relog or server restart.
- No new F8 errors when you actually use it.
If all four pass, congratulations, you have a live resource. Run through this enough times and installing becomes muscle memory.
When you are ready for your next addition, browse more tested resources at scripts-tebex.io, find QBCore and Qbox-ready options at qb-tebex.io, and compare across every category in one place at marketplace-tebex.io.
