# Getting started

> How to download, install and update any XeX script, and what to include in a support ticket when something fails.

- URL: https://xexstudio.com/docs/getting-started
Every XeX script installs the same way. This page covers the common steps; each script's page has its own requirements and configuration.

## Download

1. Buy or claim the script on [xexstudio.com](https://xexstudio.com). You sign in with your Cfx.re account during checkout.
2. Open [Keymaster → Granted assets](https://keymaster.fivem.net/asset-grants) with the **same** Cfx.re account and download the resource.
3. The game management panel is not a FiveM resource: Tebex emails you its download link.

Escrowed scripts only run on a server whose license key belongs to the account that owns the asset. Open source scripts run anywhere.

## Requirements

- Recent server artifacts and OneSync.
- [ox_lib](https://github.com/overextended/ox_lib/releases/latest): download the **release** zip, not the source code.
- [oxmysql](https://github.com/overextended/oxmysql/releases/latest) when a script stores data.
- ESX Legacy, QBCore or Qbox. Each script lists the ones it supports.

## Install

1. Put the folder in your `resources` directory **without renaming it**. Exports and the version check use the resource name.
2. Run the SQL file from `install/` if the script has one.
3. Start it in `server.cfg` after your framework and its dependencies:

   ```cfg
   ensure oxmysql
   ensure ox_lib
   ensure es_extended # or qb-core / qbx_core
   ensure xex_weaponlicense
   ```

4. Set the language with `setr ox:locale en` (or `es`). Scripts read it through ox_lib.
5. Edit `config.lua`. Settings marked as server-only never reach players.

## Updates

Updates are free. When a new version is out, the server console says so on start. Download it again from Keymaster, replace the folder and keep your `config.lua` unless the changelog says otherwise. Every change is listed on the script's page.

## Getting help

Open a ticket on [Discord](https://discord.gg/9yY3Jxnhh8) with:

- The script and its version (from `fxmanifest.lua`).
- Your framework and its version.
- The exact error from the server console or F8, as text.

Most issues are solved faster with that information than with a video. Check [Troubleshooting](/docs/troubleshooting) first.