> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revoscripts.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Update

> Learn how to update Revo HUD to the latest version without losing your configuration, logo or custom files.

> [!WARNING]
>
> **IMPORTANT:** Always back up your current `revo_hud` folder before updating. This ensures you can revert if needed.

Keeping Revo HUD up-to-date ensures access to the latest features, improvements and bug fixes. Revo HUD uses no database, so an update is just replacing files and restoring the few things you customized.

**1. Visit CFX.re Keymaster**

Go to the [CFX.re Keymaster Granted Assets](https://keymaster.fivem.net/asset-grants) and log in using the same CFX account used to purchase the script.

![Granted Assets Page](https://mintcdn.com/revoscripts/Y8iz3JZxQ2m-BeSj/images/granted-assets.jpg?fit=max\&auto=format\&n=Y8iz3JZxQ2m-BeSj\&q=85\&s=5712bda9a7abf6bbe25fac5119287c2d)

**2. Download the Latest Version**

Locate Revo HUD in your granted assets and download the latest available bundle.

> [!NOTE]
>
> The latest version will always be available in your asset grant. There's no need to repurchase.

**3. Back Up Your Customized Files**

Before replacing the old script, copy these files from your current `revo_hud` folder to a safe place:

* `config.lua`: your settings
* `html/dist/server-logo.png`: your logo (or whichever file `logoPath` points to)
* `locales/`: only if you edited a language or added your own
* `maps/postal/` or `maps/satellite/`: only if you installed a map pack

> [!TIP]
>
> You can copy the entire `revo_hud` folder as a backup before proceeding.

**4. Replace the Old Script**

1. Unzip the newly downloaded script bundle
2. Open your server directory and navigate to the `resources` folder
3. Delete the old `revo_hud` folder
4. Move the new `revo_hud` folder into the `resources` folder

> [!WARNING]
>
> Keep the folder name `revo_hud`. Nitrous kits, stress and each player's best drift are saved under that resource name, so renaming it would start from scratch.

**5. Restore Your Customizations**

Put your logo and any edited language or map files back in the new folder.

For `config.lua`, **do not simply overwrite the new file with your old one**. A new version can add options. Open the new `config.lua` and copy your values from the old one into it, so any new options are kept.

> [!WARNING]
>
> Review the new `config.lua` for any options that were added or changed in the update. See the [changelog](/products/hud/changelog).

**6. Restart the Resource**

You can either restart your server or refresh the resource using:

```bash theme={null}
refresh
restart revo_hud
```

## What Is Kept Across Updates

* **Players' personal settings** (colors, styles, layout, saved presets) are stored on each player's own PC, so an update does not reset them.
* **Nitrous kits and bottle levels**, **stress** and **best drift scores** are saved by FiveM under the `revo_hud` resource name, not in the resource folder.
* **Your `config.lua`** is the only server-side file you normally edit.

> [!NOTE]
>
> When an update adds new text to the HUD, other languages show those lines in English until their language file has them. Copy the new lines from `en.json` into your edited language files if you changed any.

## Verification

After updating, verify that everything is working correctly:

1. **Check the Console:** Make sure the resource starts without errors.
2. **Open the Menu:** Type `/hud` and make sure the settings menu opens.
3. **Check Your Branding:** Confirm your server name and logo still show.
4. **Check a Vehicle:** Get in a car and check the speedometer, **F7** panel and, if you use it, nitrous.
5. **Review Config:** Confirm your custom settings in `config.lua` are preserved.

> [!TIP]
>
> If you encounter any issues after updating, turn on `Config.Debug` and check the F8 and server consoles. See [Troubleshooting](/products/hud/troubleshooting).

## Version-Specific Update Instructions

### Version 1.0

Version 1.0 is the first release, so there is nothing to migrate. Follow the steps above for any future update. Version-specific notes will be added here when a release needs extra steps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.