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

# Requirements

Check the server environment before changing files or configuration.

## Check before purchase and installation

| Requirement        | What to compare                                                          |
| ------------------ | ------------------------------------------------------------------------ |
| Product type       | Add-on, replacement, streaming resource, or script                       |
| Framework          | The product's supported ESX, QBCore, Qbox, or standalone version         |
| Additional systems | Inventory, target, menu, database adapter, audio, or lighting controller |
| Server and game    | Required FXServer artifacts, game build, and OneSync if specified        |
| Access             | Correct purchase account and entitlement for protected assets            |
| Administration     | File access, server console, and permissions needed for testing          |

## Understand the different versions

**FXServer artifacts** are the server files. The **game build** determines available GTA game content. The **product version** belongs to the purchased asset. These numbers are not interchangeable.

Do not change the game build randomly to fix one asset. Check the product's requirement and the effect on your other resources first. Test environment changes with a backup and a planned restart.

## Framework compatibility

A vehicle may stream correctly while its dealership entry still requires framework configuration. A weapon model may load while inventory items or components are missing. A script can require specific exports, events, or database tables.

{% hint style="warning" %}
“FiveM compatible” does not promise support for every framework or inventory. The individual StudioWorks product listing is the source for supported combinations. Ask support before purchasing if your combination is not listed.
{% endhint %}

## Keep an installation record

Record the product version, resource folder name, relevant dependencies and their versions, the date, and your configuration changes. This makes later problems much easier to diagnose.

***

[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/requirements.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.