> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabihosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Install FiveM Resources - Scripts, Maps & Vehicles

> Install scripts, maps, and vehicle resources on your FiveM server hosting at Wasabi Hosting - folder structure, fxmanifest.lua, and load order explained.

Resources are how you add everything to a FiveM server: jobs, vehicles, MLO interiors, HUDs, minigames, and entire frameworks. Installing one is simple — upload it, register it in `server.cfg`, restart — but getting the structure and start order right is what separates a stable server from one that floods the console with errors. This guide covers the whole process.

## How the resources Folder Works

All resources live in the `resources` folder of your server. Two structural rules matter:

* **Category folders use square brackets.** A folder named `[qb]`, `[maps]`, or `[standalone]` is not a resource itself — it's a category that FXServer scans for resources inside it. You can nest categories to keep things tidy.
* **Every resource needs an `fxmanifest.lua`.** This manifest tells the server what scripts and files the resource contains. A folder without one (or the legacy `__resource.lua`) is not a valid resource.

```
resources/
├── [core]/
│   ├── qb-core/
│   │   └── fxmanifest.lua
│   └── oxmysql/
│       └── fxmanifest.lua
├── [jobs]/
│   └── qb-police/
│       └── fxmanifest.lua
└── [maps]/
    └── custom-pd-mlo/
        └── fxmanifest.lua
```

<Warning>
  The resource name is the folder that **directly contains** `fxmanifest.lua`. If you unzip a download and get `coolscript-main/coolscript/fxmanifest.lua`, upload the inner `coolscript` folder — not the wrapper. Keep resource names lowercase and **without spaces**.
</Warning>

## Installing a Resource

<Steps>
  <Step title="Download from a trusted source">
    The safest places to find resources are the [Cfx.re forum Releases section](https://forum.cfx.re/c/development/releases) and **GitHub** repositories linked from it. Avoid resold or "leaked" scripts — they frequently contain backdoors that hand strangers admin access to your server.
  </Step>

  <Step title="Upload to the resources folder">
    Open the **File Manager** in the [Wasabi Hosting Game Panel](https://panel.wasabihosting.com) and upload the resource folder into `resources` (or a `[category]` inside it). For large resources like MLOs and vehicle packs, [SFTP is faster](/server/file-management) — you can drag entire folders across.
  </Step>

  <Step title="Register it in server.cfg">
    Add a line to your [server.cfg](/games/fivem/server-cfg):

    ```bash theme={null}
    ensure coolscript
    ```

    `ensure` starts the resource at boot (and restarts it if it's already running). You reference the folder name only — never the category, so `ensure coolscript`, not `ensure [standalone]/coolscript`.
  </Step>

  <Step title="Restart and check the console">
    Restart the server, then watch the live console. A healthy start looks like `Started resource coolscript`. Red error lines mean something is wrong — see troubleshooting below.
  </Step>
</Steps>

## Start Order and Dependencies

Resources start in the order of their `ensure` lines in `server.cfg`, top to bottom. Most script errors on fresh servers come from wrong ordering:

```bash theme={null}
# 1. Database connector first
ensure oxmysql

# 2. Framework core next
ensure qb-core

# 3. Framework modules and everything else after
ensure qb-police
ensure coolscript
```

Many resources also declare a `dependency` in their `fxmanifest.lua` — read each resource's README, as some require specific libraries (e.g. `ox_lib`) to be started first.

## Framework Resources vs. Standalone

* **Framework resources** are built for ESX, QBCore, or Qbox and call into the framework's core (`es_extended`, `qb-core`). They only work if the matching framework is installed and started first — a QBCore job script will not run on an ESX server.
* **Standalone resources** work on any server without a framework. Releases usually state "standalone" explicitly.

Always check which framework (and version) a resource targets before installing it.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Couldn't find resource X">
    The folder name doesn't match your `ensure` line, the resource is nested one folder too deep, or it's missing `fxmanifest.lua`. Verify the path in the File Manager.
  </Accordion>

  <Accordion title="Script errors mentioning nil values or missing exports">
    A dependency isn't started, or it starts after this resource. Move the dependency's `ensure` line higher in server.cfg, and confirm the resource matches your framework.
  </Accordion>

  <Accordion title="Resource starts but nothing happens in-game">
    Check the resource's config file (usually `config.lua`) — many scripts ship disabled or with placeholder job names/coordinates. Also check the F8 client console for client-side errors.
  </Accordion>

  <Accordion title="Server got slower after adding resources">
    Every resource costs performance. Use the `resmon` command in the F8 console (as admin) to spot resources with high ms usage, and remove or replace the heavy ones.
  </Accordion>
</AccordionGroup>

<Tip>
  Take a [backup](/server/backups) before installing a batch of new resources — rolling back is much faster than untangling a broken load order.
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="server.cfg Explained" icon="gears" href="/games/fivem/server-cfg">
    Understand the file where all your ensure lines live.
  </Card>

  <Card title="Add Admins" icon="user-shield" href="/games/fivem/add-admins">
    Grant yourself permissions to use admin-only resources.
  </Card>
</CardGroup>

<Card title="Room for more scripts" icon="rocket" href="https://wasabihosting.com/game-servers/fivem">
  Big resource collections love fast disks and CPUs — FiveM hosting from **€4.80/month** on NVMe and Ryzen hardware at Wasabi Hosting.
</Card>