> 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/dependencies.md).

# Dependencies

## Required

| Resource                                           | Used by            | Notes                                                                |
| -------------------------------------------------- | ------------------ | -------------------------------------------------------------------- |
| [oxmysql](https://github.com/overextended/oxmysql) | Almost all scripts | Declared as a dependency in each `fxmanifest.lua`.                   |
| Framework                                          | All scripts        | ESX Legacy (`es_extended`), QBCore (`qb-core`) or QBox (`qbx_core`). |

## CrankChaos free resources

| Resource                                     | Purpose                                                        |
| -------------------------------------------- | -------------------------------------------------------------- |
| cc\_lib/00%20Overview\.md)                   | Shared notifications and hint texts used by the CrankChaos UI. |
| cc\_jobs/00%20Overview\.md)                  | Job locations used by job-related scripts.                     |
| cc\_images%20(cc\_images)/00%20Overview\.md) | Image tool for item and clothing pictures.                     |

All three are optional soft dependencies: scripts work without them and fall back to their own config (for example job locations) or built-in notifications. Installing them is recommended for the full feature set. Each script's installation page lists how it uses them.

## Optional

| Resource         | Used by                                                                                                         |
| ---------------- | --------------------------------------------------------------------------------------------------------------- |
| screenshot-basic | cc\_admin (screenshot feature, off by default), cc\_character (photos), cc\_images (photo studio and portraits) |

{% hint style="info" %}
CrankChaos scripts do **not** require ox\_lib. Callbacks and UI helpers are built in.
{% endhint %}

## Recommended start order

```cfg
ensure oxmysql
ensure es_extended      # or qb-core / qbx_core
ensure screenshot-basic # optional
ensure cc_lib
ensure cc_jobs
ensure cc_images        # optional
# ...CrankChaos scripts
```


---

# 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/dependencies.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.