> For the complete documentation index, see [llms.txt](https://striga.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://striga.gitbook.io/docs/striga-core/introduction.md).

# Introduction

The shared base every Striga script runs on. One layer over QBCore, Qbox, ESX and standalone.

**Striga Core** is the base layer of the Striga suite. Every Striga script (Tokyo HUD, Chat, Inventory, Multicharacter, Notify, Text UI) talks to your framework through it.

You install it once, set a few options in one JSON file, and every Striga script works the same on QBCore, Qbox, ESX or standalone.

{% hint style="info" %}
**Version:** striga-core `0.1.0`. Every Striga script needs striga-core `0.1.0` or newer. **Install it first.**
{% endhint %}

## Why it exists

| Benefit                 | What it means                                                                                                |
| ----------------------- | ------------------------------------------------------------------------------------------------------------ |
| **One place to update** | When a framework changes, only striga-core needs a fix, not every script                                     |
| **No bridge files**     | Striga scripts have no framework code of their own. Money, jobs and items work the same everywhere           |
| **Escrow friendly**     | All Lua stays escrowed. You set things in `config.json`, and plug in your own systems with `RegisterAdapter` |
| **Version check**       | Core tells you in the console when a Striga script has an update                                             |
| **One settings hub**    | Players change the settings of every Striga script in one place (the Tokyo HUD `/hud` menu)                  |
| **Shared theme**        | When Tokyo HUD runs, the other Striga UIs follow its accent color                                            |

## Supported systems

Core finds these by itself (`"auto"`). You can also pick one by name in `config.json`.

| System    | Supported                                                                             | Page                                                      |
| --------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| Framework | QBCore, Qbox, ESX, standalone                                                         | [Frameworks](/docs/striga-core/integration/frameworks.md) |
| Inventory | Striga Inventory, qb-inventory, ox\_inventory, ESX inventory                          | [Inventory](/docs/striga-core/integration/inventory.md)   |
| Notify    | Your framework's notify, ox\_lib, Striga Notify                                       | [Notify](/docs/striga-core/integration/notify.md)         |
| Text UI   | Striga Text UI, qb-core DrawText, esx\_textui, ox\_lib                                | [Text UI](/docs/striga-core/integration/text-ui.md)       |
| Clothing  | illenium-appearance, fivem-appearance, qb-clothing, skinchanger                       | [Appearance](/docs/striga-core/integration/appearance.md) |
| Fuel      | ox\_fuel, LegacyFuel, cdn-fuel, ps-fuel, qb-fuel, lc\_fuel (else the game's own fuel) | [Fuel](/docs/striga-core/integration/fuel.md)             |
| Voice     | pma-voice                                                                             | -                                                         |

{% hint style="success" %}
Using something else? Your own inventory, notify, text UI, fuel or clothing script can be plugged in with `RegisterAdapter`. See [Integration](/docs/striga-core/integration.md).
{% endhint %}

## Requirements

* **ox\_lib**
* **oxmysql**
* One of: QBCore, Qbox, ESX (or none = standalone)

## What players see

Striga Core has no screen of its own. Players see it through the other Striga scripts:

* One settings menu for the whole suite in Tokyo HUD (`/hud`).
* The same accent color on every Striga UI.

{% content-ref url="/pages/k3Cvtdo9uJ60DuIMm4fd" %}
[Installation & Configuration](/docs/striga-core/installation-and-configuration.md)
{% endcontent-ref %}


---

# 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://striga.gitbook.io/docs/striga-core/introduction.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.