Before you startLink to this section
You need three things:
- access to your server’s files and its
server.cfg - a way to restart the server, such as txAdmin or the server console
- the dependencies the script lists, at or above the version it names. Each script’s docs page has them under Install.
Install on a copy of your server first if you can. A script that works on a test server will not surprise your players.
Get the filesLink to this section
Free scripts download from their docs page on this site, with no sign-up and no gated link. Each version has its own address, so a link you save keeps working.
Pro scripts are delivered to your Cfx.re account through Tebex and downloaded from the Cfx.re portal. See Getting a Pro script.
Add it to your serverLink to this section
Step 1: Put the folder in your resources
Unzip the download into your
resourcesfolder. Keep the folder name exactly as it is, for examplefwd-garages. The folder name is the resource name:server.cfgand other scripts refer to it.Step 2: Check for SQL
Some scripts create their database tables on first start. If the download includes an
.sqlfile and the script’s docs page says to import it, or the console later reports a missing table, run it against your server’s database.Step 3: Start it after its dependencies
Add an
ensureline below your framework and below every dependency the script lists. Resources start in the order they appear.server.cfg # After your framework ensure ox_lib ensure oxmysql ensure fwd-garagesStep 4: Set it up
Settings live in the script’s config file, usually
config.lua. Change what you need before the first start.Step 5: Restart and check the console
Restart the server, or run
refreshand thenensure fwd-garagesin the server console. The console prints a line when the resource starts. Anything in red after it is worth reading before players join.
When it does not startLink to this section
| What you see | What to do |
|---|---|
| The console cannot find the resource | The folder name and the name in server.cfg must match exactly, and the folder must sit inside resources. |
| The console names a dependency | Install that resource at the version the script lists, and move its ensure line above the script’s. |
| Database errors on start | Import the script’s SQL file, then restart. |
| A Pro script reports a missing or invalid licence key | Check the licence key line in server.cfg. See Licence key. |
Still stuckLink to this section
Ask in #questions with the script’s name, its version and the console output. Getting help lists what to include so the first reply is an answer.