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

# Escrow & config

Which files you can edit, how to edit them safely, and how to apply your changes.

## What is escrow?

Waro scripts are protected with **FiveM Asset Escrow**. Most of the code is encrypted, so you can't open or edit it. This protects our work, and it is how every paid script on Tebex is delivered.

You can still change everything a server owner normally needs. Those files are left readable on purpose.

## Files you can edit

Each script lists its readable files in `fxmanifest.lua` under `escrow_ignore`. For example:

```lua
escrow_ignore {
    'config.lua',
}
```

Every script has a **`config.lua`**. Some scripts have a few more readable files:

| Script       | Extra readable files | What they are for                               |
| ------------ | -------------------- | ----------------------------------------------- |
| Casino Games | `install/*.lua`      | Ready-to-paste item snippets for your inventory |

{% hint style="danger" %}
Don't edit or rename encrypted files, and don't remove the `.fxap` file from a script folder. The script will stop working.
{% endhint %}

## What is config.lua?

`config.lua` holds all the options for one script: prices, locations, jobs, commands, keys and so on. Each option has a short comment above or beside it that explains what it does.

```lua
requireOnDuty = true,          -- only on-duty employees can send invoices
maxDistance = 5.0,             -- metres; you can only invoice players this close
```

Each script's page in these docs walks through its `config.lua` in plain words.

## Editing safely

1. **Make a copy first.** Save `config.lua` as `config.backup.lua` (or anywhere outside the server), so you can go back.
2. **Use a proper text editor**, such as [Visual Studio Code](https://code.visualstudio.com) or Notepad++. Plain Windows Notepad works but makes mistakes easy to miss.
3. **Change values, not structure.** Keep every comma, bracket `{ }` and quote mark `' '` where it is.
4. **Text goes in quotes**, numbers and `true` / `false` don't:

```lua
label = 'Los Santos Police',   -- text: in quotes
maxAmount = 25000,             -- number: no quotes
allowDecline = true,           -- true or false: no quotes
```

5. **Every line inside a list ends with a comma.** A missing comma is the most common mistake.

{% hint style="warning" %}
If the script stops starting after you edit the config, look at the server console. A message such as `config.lua:12: '}' expected` tells you the line number with the mistake.
{% endhint %}

## Applying changes

After you save `config.lua`, restart that script. In the server console (or txAdmin live console) type:

```
restart waro_casino
```

Replace `waro_casino` with the script's folder name.

## When you update a script

Updates replace the whole folder, including `config.lua`. Keep your edited copy and compare it with the new one before you overwrite it. See [Updating](/getting-started/updating.md).


---

# 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.warostudios.com/getting-started/escrow-and-config.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.