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

# Download & Updates

Where to find your purchase, how to install it, and how to update it safely.

These steps are the same for every script. The script's own **Installation** page then covers what is specific to it.

## Download

{% stepper %}
{% step %}

### Open your granted assets

After the purchase the script appears in the Cfx.re Portal: [portal.cfx.re/assets/granted-assets](https://portal.cfx.re/assets/granted-assets).

{% hint style="info" %}
Log in with the Cfx.re account you used for the purchase. The asset is tied to that account.
{% endhint %}
{% endstep %}

{% step %}

### Download and unzip

Download the `.zip` and unzip it on your computer.
{% endstep %}

{% step %}

### Upload the folder

Put the resource folder into your server's `resources` directory, for example `resources/[kossek]/`.

{% hint style="warning" %}
Keep the folder name as shipped. Exports and events are addressed by the resource name, so a renamed folder breaks integrations with other scripts.
{% endhint %}
{% endstep %}

{% step %}

### Start it after its dependencies

Add `ensure <resource>` to `server.cfg` **below** the resources it depends on (database, ox\_lib, your framework, your target resource). The exact order is on each script's Installation page.
{% endstep %}
{% endstepper %}

## The server license key must match

Escrow-protected scripts only start on a server whose license key (`sv_licenseKey`) belongs to the **same Cfx.re account** that owns the asset. If your server runs on somebody else's key, the script will refuse to start — see [Common Issues](/docs/getting-started/common-issues.md).

## Updating

{% hint style="warning" %}
Back up the script's folder before every update.
{% endhint %}

1. Download the new version from the Portal.
2. Replace the resource folder on the server.
3. Put back the files you edited. These are the ones left open for you, typically:
   * `config/` — your settings
   * `locales/` — your translations
   * `bridge/` and `editable` files — your framework or notification changes
4. Compare your config with the new one and copy over any **new options**. A missing option is the most common reason a script errors right after an update.
5. Restart the server (or the resource).

Data stored in the database is not touched by an update.