Esta guía aún no está disponible en español. Se muestra el contenido completo en inglés.
Leer el original en inglésTroubleshoot a resource from RPScripts
Match the first console error of a FiveM script, MLO or asset from RPScripts to its cause, and know when to send it to support.
Start with the server console (or txAdmin's live console). Restart the server, then search the output for the resource name. The first red line about it is usually the cause; later errors often follow from it.
Paste that output into the error doctor of the free FiveM Script Tester: it explains known FXServer and txAdmin errors in your browser and redacts license IDs, IPs and keys. With the resource loaded too, it points at the file and line.
This page is the short triage for resources from the shop. The guide FiveM resource won't start explains every message with example console output. If the resource was never installed cleanly, start again with Install a resource.
Which message do you have?
| First console line | Usual cause | Details |
|---|---|---|
Couldn't find resource | The folder name does not match the ensure line, or fxmanifest.lua sits one folder too deep. | Guide |
| Manifest missing or too new | Renamed or edited manifest, or an old FXServer build. | Guide |
| A dependency is missing | A resource from the product page is not installed or starts later. | Guide |
No such export | The called resource is not started or has another folder name. | Guide |
SCRIPT ERROR | Framework object is nil or the config points at a resource you do not run. | Below |
Database or oxmysql errors | Missing tables, wrong SQL file or no connection. | Database errors |
You lack the required entitlement | Asset Escrow: the server key is not on the account that owns the asset. | Below |
A newly copied resource that FXServer does not list yet needs refresh in the server console, then ensure resource_name, or a server restart. Core, item and job changes may still require a full restart.
If the untouched release fails with a parse error in its own files, do not repair it by renaming files or inventing exports: send the error and the resource version to support.
Asset Escrow and entitlements
You lack the required entitlement means the server is not authorized to run that protected asset. This is different from the RPScripts download API's no_entitlement error, which concerns your shop account.
Check the creator's delivery instructions and that the asset is granted to the intended Cfx.re account. Verify the server registration key belongs to that account without sharing the key. Keep the supplied protected files intact and use a supported FXServer version. If access is missing, contact the seller with the order reference; do not try to bypass protection.
Asset Escrow availability also depends on the GTA V edition. Check the current Cfx.re Asset Escrow documentation and Legacy/Enhanced migration notes rather than treating a framework badge as proof.
SCRIPT ERROR lines
The resource starts, but its code fails. The line shows the file and line number:
SCRIPT ERROR: @resource_name/server/main.lua:42: attempt to index a nil valueCommon causes, in this order:
- Framework object is nil (
QBCore,ESX): the framework starts later, or it is the wrong framework. See QBCore, ESX, Qbox. - Config points at a resource you do not run: inventory, target, notify or fuel set to something else. Check
config.lua. No such export: the script calls a resource that is not started or has a different name on your server.- Database errors such as missing tables: see Database errors.
It starts but nothing happens in game
- Items: registered in the framework? See your framework page.
- Jobs: does your character have the job and grade the config requires?
- Client errors: press F8 in game and look for red lines that mention the resource. F8 console commands lists the commands that help, such as
resmon. - Maps and vehicles: check for a conflict with another resource that streams the same files.
Still stuck
Collect the relevant console output from server start, the resource's config.lua settings you changed and your framework version. Redact passwords, server keys and tokens, then contact support. For client-side crashes and error codes see FiveM error codes.
Install a script on Qbox
Start order, ox_inventory items, the QBCore bridge and common pitfalls when you install an RPScripts script on a Qbox (qbx_core) FiveM server.
SQL files and database errors
Import a FiveM resource's SQL file safely, and fix missing tables, duplicate entries and oxmysql connection problems.