> 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-tokyo-hud/settings-menu.md).

# Settings Menu (/hud)

The /hud menu, the settings place of every Striga script.

Players open the menu with `/hud` or **F9**. From here they change the HUD **and** the settings of every other Striga script on the server.

## What is in the menu

| Part               | What it does                                                           |
| ------------------ | ---------------------------------------------------------------------- |
| **Edit HUD**       | Opens the layout editor (see below)                                    |
| **Cinematic mode** | Hides the HUD and radar, adds black bars. Only for the current session |
| **Theme**          | The main color of the HUD, sent to every Striga script                 |
| **Minimap**        | Position, shape, waypoint color, vehicle only, frame                   |
| **Script blocks**  | One block per Striga script with player settings                       |
| **Share codes**    | Make a code of your look, or apply a code from a friend                |
| **Refresh rate**   | How often the HUD updates (high = faster, low = slower)                |

***

## Script blocks

Every Striga script with player settings shows its own block in the menu, for example **Chat**, **Notifications**, **Text UI**, **Inventory** and **Multicharacter**. The blocks show by themselves when the scripts run. Nothing to set up.

* The block and the script's own panel change the **same** settings. A change in one shows in the other at once.
* While the menu is open, the script shows sample content (for example sample notifications), so players see the result live.
* Each block has a **Reset** button when the script supports it.
* Settings are saved by each script for each player.

{% hint style="info" %}
**Locked blocks.** If a server owner locks a script's settings (for example `Config.Ui.Settings = false` in that script), its block is read only and shows a short note. Share codes and `/hud reset` skip locked scripts.
{% endhint %}

***

## Theme color

The theme color the player picks in `/hud` is sent through **striga-core** to every Striga script:

* Chat, Notify, Text UI and the other scripts use it as their main color.
* A script follows the theme **unless the player picked a color in that script**. Players can switch a script back to the theme in its block.
* When the HUD stops, the scripts go back to their own config color.

***

## Edit HUD

* **Drag** a part to move it.
* **Select two or more** (click, or drag a box around them) and press **Group** in the small popover to join them. Groups close up nicely when one part hides itself.
* With several parts selected you can **restyle them all at once**.
* There are two layouts: **on foot** and **in vehicle**. The vehicle one starts as a copy of the on foot one.
* The info panel and the compass can be restyled, not moved.
* Everything saves by itself. There is no save button.

When striga-chat runs, the editor also shows the chat as a box (label "Chat"): drag it to move the chat, click it to change the chat look.

***

## Share codes

Players can copy a full look to a friend:

1. In the menu, make a code. It looks like `strg-7K2QX9`.
2. The friend pastes the code and applies it.

A code carries the HUD look, positions and minimap, **plus the settings of the Striga script blocks**. It does not carry the refresh rate.

| Rule                      | Value                                                  |
| ------------------------- | ------------------------------------------------------ |
| Works on                  | The same server only                                   |
| Time between new codes    | `Config.Storage.ShareCooldown` seconds (default `300`) |
| Codes kept per player     | 20 (older ones are deleted)                            |
| Locked or missing scripts | Skipped when the code is applied                       |
| Needs                     | oxmysql and `Config.Storage.Share = true`              |

Sharing the same layout again gives back the last code. That does not count for the wait time.

{% hint style="info" %}
Codes made before the settings hub still work. They just carry no script settings.
{% endhint %}

***

## /hud reset

`/hud reset` starts the player fresh, like a first join:

* Deletes the saved HUD layout, on the PC and on the server.
* Resets every Striga script block to its defaults (locked scripts and scripts without reset are skipped).

***

## Key bindings

Players change keys in *Settings > Key Bindings > FiveM*.

| Action                                   | Default     |
| ---------------------------------------- | ----------- |
| Open the HUD menu                        | F9          |
| Toggle seatbelt (built in seatbelt only) | B           |
| Turn signal left                         | Left arrow  |
| Turn signal right                        | Right arrow |
| Hazard lights                            | Up arrow    |

{% hint style="warning" %}
FiveM remembers keys per player. If you change a default key in the config later, players who already joined keep their old key. New players get the new default.
{% endhint %}

***

## For developers

The menu shows any script that registers its settings with striga-core:

* Register with `exports['striga-core']:RegisterSettings(schema, handlers)`. The block, live updates, share codes and `/hud reset` then work for your script.
* Follow the theme with `exports['striga-core']:GetTheme()` and the `striga-core:client:theme` event.
* Share codes accept at most 64 scripts, 32 settings per script and 64 KB in total.

Schema, field types and handlers: [Settings Hub & Theme](/docs/striga-core/settings-hub-and-theme.md).

{% content-ref url="/pages/BCfHuOQYdIHd70Sq5WFo" %}
[Exports & Events](/docs/striga-tokyo-hud/exports-and-events.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-tokyo-hud/settings-menu.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.