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

# 6LY Scripts Docs

Premium FiveM scripts built for performance, customization, and control.

Welcome to the 6LY Scripts documentation hub. Every script you buy from our store has its setup guide, config walkthrough, framework integration steps, and troubleshooting notes here.

Pick the script you're installing from the sidebar to jump straight to its docs, or use the search bar (top right) to find a specific config option or export.

## What you'll find here

* **Installation** — server setup, dependencies, and database imports. Most scripts are up and running in under five minutes.
* **Configuration** — every config option explained, with examples for common server setups.
* **Frameworks** — ESX, QBCore, and QBox integration steps (most scripts ship with auto-detect bridges).
* **API & exports** — hook into our scripts from your own resources via exported functions and events.
* **Troubleshooting** — common failure modes with copy-pasteable fixes.

## Supported frameworks

Our scripts are tested against the major FiveM frameworks. Most ship with out-of-the-box presets for **ESX**, **QBCore**, and **QBox**. Some scripts are framework-agnostic (standalone) — the product page on the store lists which frameworks each script supports.

{% hint style="info" %}
Can't find what you're looking for? Open a ticket in our [Discord](https://discord.gg/JUyc3rVkDM) — we typically reply within a few hours. Bug reports and feature requests are both welcome.
{% endhint %}


---

# 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://6ly-scripts.gitbook.io/product-docs/readme.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.