Install a script
How to add any lation script to a FiveM server running Qbox, QBCore or ESX, from download to first start.
Every lation script installs the same way. Each script's own page lists what it needs on top of this, such as a database, items or another resource.
Download
Scripts bought on the store are delivered to your Cfx.re account. Sign in at portal.cfx.re with the account you bought with, open Granted Assets, download the latest version of the script and unzip it into your server's resources folder.
The server's license key has to belong to the same Cfx.re account that bought the script. If the console says the server lacks the entitlement to run a script, check that key first.
Keep the folder name exactly as it comes (for example lation_banking). Scripts find each other by resource name, and several of them stop with a console message if the folder was renamed.
Ensure it
Add the script to server.cfg after your framework and after anything it depends on. lation ui goes first, above ox_lib, because the lation ox_lib fork looks for it when ox_lib starts. lation interact (or ox_target) goes after your framework and above your inventory and the scripts that use it, because they look for it as they start:
ensure lation_ui
ensure ox_lib
ensure oxmysql
ensure qbx_core
ensure lation_interact
ensure ox_inventory # your inventory
ensure lation_bankingWith lation ui, the lation ox_lib fork is optional but recommended. It replaces ox_lib, and scripts written for ox_lib then show their menus, notifications and progress bars in lation ui.
Admin permissions
If the script has an admin panel or command, its install steps give you an add_ace line for it, such as add_ace group.admin lation_banking.admin allow. If you are on the Qbox framework, the recommended place to paste these permissions is the permissions.cfg file instead of server.cfg.
Start
Restart the server, or run ensure <resource> from the server console. lation ui is the exception: restart the whole server, so ox_lib starts after it. Scripts that keep data create their database tables on first start, so there is usually no SQL to import. Watch the console for the script's start-up lines; anything it needs and can't find is named there.
Next
Open the page for the script you installed for its requirements, settings and commands.
Still stuck? Ask in our Discord: the people who write the scripts answer.
Last updated