Adding your own scripts

01Your folder: resources/[client]

Your scripts, maps and personal resources go into the resources/[client] folder, from the server's Files screen. This folder is yours, and the only one counted against your space: the Nova framework, the cache and the logs live elsewhere, managed and updated by us.

The "Your files" gauge shows how much of your plan's quota is used. The trash counts too: a deleted file stays there for 7 days, restorable, then it is destroyed. To free space right away, open "Trash" and empty it.

02Uploading files

"Upload a file" and "Upload a folder" send from your computer, and dragging onto the list does the same. "New folder", "Rename", "Move" and "Delete" handle the rest. A text file of up to 512 KB opens with "Edit"; beyond that, download it.

Some types are always refused, alone or inside an archive: system scripts and programs such as .sh, .bat, .exe or .dll. A FiveM resource does not need them; a package that contains them deserves a close look before you install it.

03Importing an archive

An uploaded archive (zip, rar, 7z, tar.gz…) is imported: every folder that contains a manifest (fxmanifest.lua, or the older __resource.lua) is extracted here, then the archive is deleted. What is not a resource is left out, and the result lists it. An archive without any manifest is refused, with nothing written. To upload an archive as is, tick "Keep the archive as is", then use "Extract here" on the file.

If a resource with the same name already exists, nothing is written before you choose: "Replace" sets the old version aside and only deletes it once the new one is in place, "Import under another name" adds -2, -3… and keeps both. Only one archive is processed at a time per server; processing continues on the server, keep the page open to see the result.

"Import from a link" downloads an archive from an https address, for example the file attached to a GitHub release, up to 2 GB. Paste the link of the attached file rather than the source code one: the site needs to know the file size before receiving it.

04Enabling and ordering

A new resource arrives switched off. Below the files, the "Resources" card lists everything that has a manifest: enable what should start, drag to choose the order, then "Save". Everything starts after the Nova framework, at the next server restart; "Restart now" applies it right away.

The card reads the dependencies of each manifest. A resource that asks for a missing dependency will not start; a disabled dependency is started anyway, and "Enable and place before" puts the order right. A folder you want to keep without starting it is excluded from its row menu, and can be brought back later.

The "To fix" section says why a folder cannot be enabled: name refused (unaccented letters, digits, _, - and . only), more than three levels of nested categories, no manifest, same name as a Nova framework resource, or same name in another folder. Fix it in your files, then click "Refresh" in the card.

05Common pitfalls

ox_lib is provided by nova_lib, and no ox_lib folder exists on disk. In the fxmanifest of a script, the @ox_lib/init.lua line must be replaced with @nova_lib/shared/lib_init.lua, or the console shows "Failed to load script". It is the most frequent fix for a recent script.

Do not import a whole framework or its base resources (inventory, phone, targeting): Nova already provides them, and two versions of the same resource get in each other's way. A script written for ESX will not work without being adapted; coming from another framework says what carries over.

A server script runs with access to the server's database. Only install resources whose origin you know: the risks of FiveM packs details what a dubious package can hide. If a script needs an ACE permission, grant it from Configuration, "Script permissions" card (server configuration).