Why don’t I get a ZIP by email?

Serious FiveM scripts are delivered through Asset Escrow / Keymaster. Cfx.re holds the licence and you avoid leaked copies. If someone only sends a .zip on Discord, walk away.

The resource does not start after ensure

Check that the folder name matches ensure, that dependencies (ox_lib, framework, mysql) start first, and that the script matches your city’s framework. The TXAdmin log usually names the exact line.

Can I install the same script on two servers?

A FireCorp catalogue licence is for one server. If you need a second city, buy another licence or talk to us about a custom job.

Guide · 8 min read

How to install FiveM scripts, step by step

If you just bought a FiveM script, skip the forum thread. Legal delivery goes to Keymaster; then you mount it in TXAdmin like any other escrow resource.

Installing FiveM scripts is not “drag a folder and pray”. If the resource is legit, the flow is: payment → Keymaster licence → resource on the server → ensure → test on the right framework. This guide is that flow, for ESX, QBCore and QBox.

Before you install: a real purchase, not a leak

A leaked script can get the server banned (Cfx.re ToS), ship malware, and leave you with zero updates. FireCorp’s catalogue is charged and assigned to your account. We do not send “premium packs” or dumps. If someone offers the same resource for $3 on Discord, it is not a deal — it is a burned copy.

Open the FiveM script store ESX, QBCore and QBox.

1. Cfx.re account and Keymaster

You need a portal.cfx.re account (the same one you use in FiveM). At checkout we ask you to link it. The script is not “magically downloaded to the VPS”: it is bound to your Keymaster. Open Granted Assets and check the product name is there.

2. Install the resource in TXAdmin

Open TXAdmin → Resources / whatever file manager you use.
Add the asset from Keymaster or clone it into that instance’s resources folder.
The folder name must match what you will put in ensure (no messy spaces).
If the script needs dependencies (oxmysql, ox_lib, es_extended, qb-core, qbx_core), those must be started first.

3. server.cfg: order matters

An ensure at the bottom, after the framework and shared libraries, avoids the classic “nil value of ESX/QBCore”. Do not start a police job before the core. If you use a third-party voice, inventory or HUD pack, read the product page: many FiveM scripts assume ox_inventory or a specific inventory.

ensure [framework] (es_extended, qb-core or qbx_core)
ensure libraries (ox_lib, oxmysql…)
ensure the script you just bought
resource restart or full server restart

4. Test it in your city, not on an empty local

Join with a dummy character, without admin godmode hiding inventory errors. Watch F8 and the server log. If the script is ESX and your city is QBCore, it will not “adapt itself”: buy the right variant or hire the port. That is why every FireCorp product lists its framework.

Browse scripts by framework ESX, QBCore or QBox.

Typical FiveM script install errors

Could not find dependency: you are missing ox_lib, mysql or the core. Install it and reorder the cfg.
No such export: the resource started before the framework. Move the ensure.
Escrow timeout / failed to verify: Keymaster does not recognise the licence on that server key. Re-grant the asset or check the server key is yours.
Encrypted script with no support: if you bought a leak, there is no support. Buy the licence.

Updates

While the product is on sale, FireCorp catalogue updates are included. You take them from Keymaster / the delivery channel, not by “asking for the zip again”. Do not clobber your config: copy config.lua (or whatever we document) before overwriting the folder.

Stuck on install? A 30-minute call, in English or Spanish.