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

# Updating

How Waro script updates work and how to install one without losing your settings.

## How versions work

Every Waro script has a version number, for example `0.1.1`. You can see it at the top of the script's `fxmanifest.lua` and in its `CHANGELOG.md`.

While a script is below **1.0**, the numbers mean:

| Change                | Example           | What it means                                                                    |
| --------------------- | ----------------- | -------------------------------------------------------------------------------- |
| Middle number goes up | `0.1.x` → `0.2.0` | New features. Read the changelog: config options may have been added or changed. |
| Last number goes up   | `0.2.0` → `0.2.1` | Fixes only. Usually safe to drop in.                                             |

{% hint style="info" %}
**Early access.** Before 1.0, new features can change how a script is set up. Always read the release notes before you update.
{% endhint %}

## Where to find updates

* **Discord:** every release is posted in our changelog channel. Follow it to get notified.
* **Cfx.re portal:** the newest version is always the one you download from [Keymaster](https://portal.cfx.re).
* **CHANGELOG.md:** each script folder has a `CHANGELOG.md` that lists what changed in every version.

## How to update

1. **Back up** the script's current folder, especially `config.lua` (and any other files you edited).
2. **Download** the new version from the Cfx.re portal.
3. **Read** the new `CHANGELOG.md`. Look for anything under *Changed* or *Removed*, and for new config options.
4. **Replace** the old folder with the new one.
5. **Copy your settings back.** Open your old `config.lua` and the new one side by side, and copy your values into the new file. Don't paste the old file over the new one: new options would be missing.
6. **Restart** the script, or the whole server.

{% hint style="warning" %}
If you update `waro_lib`, update it before the scripts that need it.
{% endhint %}

## Your data is safe

Updates don't delete your database. Tables are created only if they don't exist yet, so players keep their vehicles, money, progress and settings.


---

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