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

# Updates & backups

Update assets while preserving your settings and a recovery path.

## Before updating

Back up the existing resource, your changes, and the relevant server configuration. Include a database backup if the update changes data or schema. Record the current product version and read the included release notes.

## Update safely

1. Download the complete new package through the product's delivery method.
2. Extract it into a separate folder and compare the new instructions with your installed version.
3. Transfer your settings deliberately. Do not overwrite the new default configuration with the entire old file: new required fields may be missing.
4. Apply database changes only when the update instructions require them. Check whether they have already been applied.
5. Replace the resource completely during a maintenance window. Avoid mixing old and new files.
6. Restart the required resources or server and test both the core feature and your integrations.

{% hint style="info" %}
Configuration and saved-settings filenames vary by product. Update instructions for another developer's script do not automatically apply to StudioWorks assets.
{% endhint %}

## Test after updating

| Product | Minimum checks                                       |
| ------- | ---------------------------------------------------- |
| Vehicle | Spawn, enter, drive, extras, and included tuning     |
| Ped     | Load, visibility, movement, and intended animations  |
| Script  | Startup, core feature, permissions, and integrations |
| Weapon  | Give, equip, and included components                 |

## If the update fails

Compare the first error with the changes you made. Test the new version with its untouched default settings on your test server and keep the error log.

To roll back, restore the backed-up resource version and matching settings. Database changes need a compatible recovery plan; do not blindly restore isolated tables. If you are unsure, stop testing and [contact support](/studioworks-docs/support/preparing-a-ticket.md) with both version numbers.

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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://studioworks.gitbook.io/studioworks-docs/installation/updates-backups.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.