FiveM Script Install Guide: Add Resources Without Breaking Your Server

Inspect the folder before installing

The safest FiveM install starts before you touch server.cfg. Open the downloaded folder and confirm the real resource folder contains fxmanifest.lua directly. Many downloads unzip into a wrapper folder such as resource-main/resource. If you place the wrapper in resources, FiveM may never see the manifest. It can look like the script is broken when the actual issue is one extra folder level. Rename only when the resource supports it, because exports, dependencies and documentation may expect a specific folder name.

Read the manifest and identify whether the script has client files, server files, shared config, NUI assets or map data. If files listed in the manifest are missing, do not try to force the script to start. Fix the folder structure or download the correct release. If the resource includes config examples, copy the intended config file into place rather than editing a backup or sample file that the manifest does not load.

resources/[custom]/my_resource/fxmanifest.lua
resources/[custom]/my_resource/config.lua
resources/[custom]/my_resource/client/main.lua
resources/[custom]/my_resource/server/main.lua

Handle dependencies in order

FiveM resources rarely run alone. A QBCore job may require qb-core, ox_lib, oxmysql, an inventory, a target resource and a menu library. An ESX script may require es_extended and database dependencies. Install and start the dependency resources first. Then add the custom script below them. If you add the custom script above its framework, the first export call can fail and make the new script look broken even though the code is correct.

Keep install changes small. Add one resource, start the server, read the console and test one feature. If you install five scripts at once, you will not know which one caused the error. For paid or complex scripts, document the installed version and any config changes so you can undo them later.

Import SQL carefully

If the script includes SQL, back up the database first. Check whether the SQL creates new tables, alters existing tables or inserts configuration rows. Do not run random old SQL from a forum unless it matches the script version. A missing column error after install often means the wrong SQL was imported, the SQL was imported into the wrong database, or a migration was skipped. Confirm the database name in the connection string before importing.

Test privately before launch

After installation, boot the server with a private test player. Confirm no startup errors, then test the feature with the right job or permission. Next test the denied path: wrong job, no item, low grade, off duty or invalid target. A safe install is not only about making the happy path work; it is about making sure restricted actions remain restricted. If the script touches money, inventory, vehicles or staff tools, inspect those actions server-side.

Ask Stellar AI to review your folder tree, manifest, start order, config and first console output. A good answer should tell you the install risk, the smallest patch and the exact test sequence. Avoid accepting broad rewrites when the real issue is folder placement or dependency order.