> For the complete documentation index, see [llms.txt](https://ccfivem.gitbook.io/ccfivem-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ccfivem.gitbook.io/ccfivem-docs/getting-started/installation-basics.md).

# Installation Basics

Every CrankChaos script is installed the same way.

## 1. Download

Download the resource from the Cfx Portal (see Downloading Your Scripts) and extract it into your `resources` folder. Keep the folder name exactly as delivered (for example `cc_garage`). Renaming breaks escrow and exports.

## 2. Install dependencies

* [oxmysql](https://github.com/overextended/oxmysql), required by almost every script.
* Your framework: ESX Legacy, QBCore or QBox.
* Free CrankChaos resources as needed: cc\_lib/00%20Overview\.md), cc\_jobs/00%20Overview\.md), cc\_images%20(cc\_images)/00%20Overview\.md).

Full list: Dependencies.

## 3. Import SQL

Some scripts ship a `sql/` folder. Import those files once into your database (HeidiSQL, phpMyAdmin or the MySQL CLI) before the first start. Other scripts create their tables automatically on start. Each script's installation page lists what applies.

## 4. server.cfg order

Start dependencies before CrankChaos scripts:

```cfg
ensure oxmysql
ensure es_extended      # or qb-core / qbx_core

ensure cc_lib
ensure cc_jobs
ensure cc_images        # optional

# CrankChaos scripts afterwards, e.g.
ensure cc_inventory
ensure cc_garage
```

## 5. Permissions (ACE)

Staff features are protected with ACE permissions. Each script's installation page lists the exact lines, for example:

```cfg
add_ace group.admin <permission> allow
add_principal identifier.license:<your-license> group.admin
```

{% hint style="warning" %}
ACE entries are read when the server starts. After editing `server.cfg`, restart the server, not just the resource.
{% endhint %}

## 6. Configure

Open `config/config.lua` in the resource. Configuration files, locales and SQL files are never encrypted and can be edited freely.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ccfivem.gitbook.io/ccfivem-docs/getting-started/installation-basics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.