> For the complete documentation index, see [llms.txt](https://docs.limescripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limescripts.com/lime-scripts.md).

# Lime Scripts

Your city. Your rules.

Guides for purchasing, installing and maintaining Lime Scripts resources for your FiveM server.

## Start here

1. Choose the Cfx.re account that should own your purchase.
2. Sign in through the store's FiveM login and complete payment through Tebex.
3. Download your granted resource from the Cfx.re Portal.
4. Check the product's requirements, then install and test on a staging server.

[Read the setup guides](/documentation/getting-started.md) · [Get help](/help-center/help-center.md) · [Join Discord](https://discord.gg/p58kubnUx8)

## Before you install

Compatibility, dependencies and configuration differ between resources. Check the listing for your specific script; do not assume all scripts support the same framework or integrations.

## Documentation status

General setup and support guides are available. Resource-specific requirements, configuration keys, exports and events will be added after their release files have been verified.


---

# 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://docs.limescripts.com/lime-scripts.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.