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

# Introduction

Clean, modern notifications for QBCore, Qbox and ESX.

**Striga Notify** replaces the notifications on your server with a clean design that matches **Striga Tokyo HUD**.

You install it once, and every notification on your server uses the new look: your Striga scripts, your framework and your other scripts.

Current version: **1.0.0**

## Features

| Feature                    | What it means                                                                                |
| -------------------------- | -------------------------------------------------------------------------------------------- |
| **3 looks**                | Card, Tinted and Compact                                                                     |
| **3 icon looks**           | Plain, Tile and Bar                                                                          |
| **4 types**                | Info, Success, Warning and Error, each with its own color and icon                           |
| **Follows your HUD color** | With Striga Tokyo HUD, notifications use the theme color the player picked, live             |
| **Player settings**        | Every player can change look, icon, color, position, opacity, size, blur, time bar and sound |
| **Smart stacking**         | The same message again shows a counter (x2, x3) instead of filling the screen                |
| **Updates in place**       | A notification with the same `id` changes instead of adding a new one                        |
| **Catches other scripts**  | ESX, QBCore, Qbox and ox\_lib notifications all show in the new design                       |
| **Background blur**        | Soft blur of the game behind each notification                                               |

## Supported frameworks

| Framework | How other scripts are caught                  |
| --------- | --------------------------------------------- |
| ESX       | Automatic, no file to edit                    |
| QBCore    | One line in `qb-core`                         |
| Qbox      | One line in `ox_lib`                          |
| ox\_lib   | One line in `ox_lib` (works on any framework) |

The steps are on the [Integration](/docs/striga-notify/integration.md) page.

## Requirements

* **striga-core 0.1.0 or newer** (started before Striga Notify)
* One of: QBCore, Qbox, ESX

{% hint style="info" %}
**Striga Tokyo HUD is optional.** Without it, Striga Notify uses the color from its config. With it, the color follows the HUD theme (unless the player picks a color) and the `/hud` menu gets a **Notifications** section, through the striga-core settings hub.
{% endhint %}

## Player commands

| Command           | What it does                                                                                                                         |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| `/notifysettings` | Opens the settings panel with a live preview                                                                                         |
| `/hud`            | Tokyo HUD menu, has a **Notifications** block (if the HUD runs). See [Settings Menu (/hud)](/docs/striga-tokyo-hud/settings-menu.md) |

Both places change the same settings. They are saved on each player's own PC, so every player keeps their own look.

{% content-ref url="/pages/tgRe5jMsN1afn5ilhqbI" %}
[Installation & Configuration](/docs/striga-notify/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-notify/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.