> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/interface/cuxial-pausemenu/troubleshooting.md).

# Troubleshooting

Common Cuxial Pause Menu problems, with their cause and fix.

The most frequent problems after installing Cuxial Pause Menu, with the cause and the fix for each one.

<details>

<summary>The resource does not start</summary>

**Cause.** A dependency is missing or starts later than the menu. Cuxial Pause Menu needs OneSync, `ox_lib` and `cuxial_bridge`.

**Fix.** Enable OneSync and start the dependencies first:

{% code title="server.cfg" %}

```cfg
ensure ox_lib
ensure cuxial_bridge
ensure cuxial_pausemenu
```

{% endcode %}

</details>

<details>

<summary>Two menus appear, or the screen flickers when pressing Esc</summary>

**Cause.** Another pause menu resource is still running. Both react to <kbd>Esc</kbd>, and Cuxial Pause Menu closes the GTA pause screen each time the other one opens it.

**Fix.** Remove the other pause menu from `server.cfg` and restart the server.

</details>

<details>

<summary>Pressing Esc does nothing</summary>

**Cause.** One of these:

* Another interface has the cursor (inventory, phone, another menu). The pause menu waits until it is closed.
* The player changed the key binding in the GTA settings.
* The interface is not loading. The folder `web/dist` is missing or incomplete, usually after a partial upload.

**Fix.** Close the other interface, or check the binding "Open the pause menu" in the GTA key settings. If the menu never shows for anyone, make sure `web/dist/index.html` and the folder `web/dist/assets` exist inside the resource; if they do not, copy the resource again from the original package and restart the server.

</details>

<details>

<summary>I changed keys.menu or keys.map but the old key still works</summary>

**Cause.** Both are only defaults. Once a player has joined, FiveM remembers their key binding.

**Fix.** Each player changes it in the GTA settings, under key bindings for FiveM. New players get the new default.

</details>

<details>

<summary>Police and medics on duty always show 0</summary>

**Cause.** The values in `duty` do not match your jobs. On QBox and QBCore they are compared with the job type and the job name. On ESX only with the job name, so the default `'leo'` and `'ems'` match nothing.

**Fix.** Set your own values in `shared/config.lua`:

{% code title="shared/config.lua" %}

```lua
duty = { police = 'police', medical = 'ambulance' },
```

{% endcode %}

Only players on duty are counted.

</details>

<details>

<summary>The extra currency shows 0, or I do not use one</summary>

**Cause.** `coins.enabled` is `true` and the account in `coins.account` does not exist in your framework.

**Fix.** Write the name of your account in `coins.account`, or set `coins.enabled = false` to hide it.

</details>

<details>

<summary>Cash and bank show 0, or the name is the FiveM name instead of the character</summary>

**Cause.** The menu could not read the character. `cuxial_bridge` is not connected to the framework, or it started before it.

**Fix.** Start your framework before `cuxial_bridge`, and `cuxial_bridge` before `cuxial_pausemenu`.

</details>

<details>

<summary>The number of slots is wrong</summary>

**Cause.** With `server.maxPlayers = 0` the menu shows the value of `sv_maxclients`.

**Fix.** Write the number you want to show in `server.maxPlayers`.

</details>

<details>

<summary>No icons appear above players with the menu open</summary>

**Cause.** One of these:

* `aura.enabled` is `false`.
* The player is further than `aura.distance`, or behind a wall with `aura.requireLos = true`.
* The player is dead or downed with `aura.clearOnDeath = true`.
* You are looking for your own icons in first person, or `aura.showSelf` is `false`.
* The player opened and closed the menu more than `aura.rate.limit` times in a few seconds. The icons come back on their own.

**Fix.** Review the `aura` block in `shared/config.lua`.

</details>

<details>

<summary>The menu closes by itself</summary>

**Cause.** Another resource took the cursor away while the menu was open. After `aura.healMs` without focus, the menu closes.

**Fix.** Raise `aura.healMs` if a resource of yours takes the focus for a moment on purpose.

</details>

<details>

<summary>The GTA pause screen never opens, even from another resource</summary>

**Cause.** It is intended. Every `native.watchdogMs` the menu checks for a GTA pause screen it did not open, closes it and opens itself.

**Fix.** Set `native.watchdogMs = 0` to stop that check. <kbd>Esc</kbd> still opens Cuxial Pause Menu.

</details>

<details>

<summary>A shortcut has no picture</summary>

**Cause.** The file named in `image` is not inside `web/dist/img/tiles/`.

**Fix.** Copy the picture into that folder and write its exact file name in the `tiles` entry.

</details>

<details>

<summary>Texts appear in the wrong language</summary>

**Cause.** The menu follows the `ox:locale` convar. The rules, the social networks and the server name are not translated: they are shown as written in `shared/config.lua`.

**Fix.** Set the convar in `server.cfg` and restart. `en` and `es` are included:

{% code title="server.cfg" %}

```cfg
setr ox:locale "en"
```

{% endcode %}

</details>


---

# 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://docs.cuxial.com/scripts/interface/cuxial-pausemenu/troubleshooting.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.