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

# Commands & permissions

Commands, default keys and staff permissions of Cuxial Emotes.

Players play emotes with `/e`, the menu and a handful of keys. Staff get one more command to manage zones.

## Commands

Names shown here are the defaults. All of them can be renamed in `shared/config.lua` under `commands`.

| Command                        | Who                                                          | What it does                                                                                                                                                                                                                          |
| ------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/e <emote> [variant]`         | Everyone                                                     | Plays an emote, scenario, walk style or expression by its command. The optional number picks a prop variant when the emote has several.                                                                                               |
| `/e c`                         | Everyone                                                     | Cancels the current emote.                                                                                                                                                                                                            |
| `/c`                           | Everyone                                                     | Cancels the current emote. Exists only if `commands.cancel.enabled` is `true`.                                                                                                                                                        |
| `/emoteset <1-6>`              | Everyone                                                     | Switches the active quick set. Exists only if `emotes.quickAnims` is `true`.                                                                                                                                                          |
| `/animedit`                    | Everyone                                                     | Moves and rotates your character while an emote is playing. Exists only if `commands.animEdit.enabled` is `true`.                                                                                                                     |
| `/syncpos <sender> [receiver]` | Everyone, or staff if `commands.syncPos.adminOnly` is `true` | Development tool: adjusts the relative position of a paired emote and copies the result to the clipboard. `[receiver]` is only needed when the sender emote has no `OtherEmote`. Exists only if `commands.syncPos.enabled` is `true`. |
| `/emotezones`                  | Staff                                                        | Opens the emote zone panel: list, create, enable, disable and delete zones. Needs the `cuxial_emotes_dlc` add-on.                                                                                                                     |

{% hint style="info" %}
Synchronized dances are generated from the dance category. Play them with `/e s<command>`, for example `/e sdance` for an emote whose command is `dance`.
{% endhint %}

## Default keys

Each player can rebind these in the GTA settings, under key bindings for FiveM. Defaults come from `keys` in `shared/config.lua`.

| Key                  | Action                                    |
| -------------------- | ----------------------------------------- |
| `F3`                 | Open the emote menu                       |
| `X`                  | Cancel the current emote                  |
| `Shift` + `1` to `5` | Play quick emote 1 to 5 of the active set |
| `Y`                  | Accept a paired emote or a suggestion     |
| `X`                  | Reject a paired emote or a suggestion     |
| `B`                  | Point with the finger                     |
| `H`                  | Hands up                                  |
| `G`                  | Cross arms                                |
| `,`                  | Ragdoll                                   |
| `Left Ctrl`          | Crouch                                    |
| `Right Ctrl`         | Prone                                     |
| `H`                  | Photo mode: hide or show the panel        |
| `Left Alt`           | Photo mode: release or capture the cursor |
| Unbound              | Photo mode: exit                          |

Photo mode keys only act while photo mode is open. It is started from the Settings tab of the menu.

## Paired emotes

1. A player picks a synchronized emote from the menu, or types its command with `/e`.
2. The request goes to the chosen player or, with `/e`, to the closest one within `sync.distance`.
3. The other player sees the request and answers with **Y** or **X**.
4. If it is accepted, both characters are positioned and play their half of the emote.

A request expires after `sync.pendingMs`. A player with a pending request cannot receive another one until it is answered or expires.

## Staff permissions

| Action                                                     | Requirement                                                                                                                                                   |
| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Run `/emotezones`                                          | ACE group set in `commands.zones.restricted` (`group.admin` by default) **and** the `cuxial_bridge` permission set in `admin.permission` (`admin` by default) |
| Create, enable, disable or delete zones                    | The `cuxial_bridge` permission set in `admin.permission`                                                                                                      |
| Use `/syncpos` when `commands.syncPos.adminOnly` is `true` | The `cuxial_bridge` permission set in `admin.permission`                                                                                                      |

{% hint style="warning" %}
The zone panel only opens when the `cuxial_emotes_dlc` add-on is running, because the emotes a zone offers come from it.
{% endhint %}

To let a player run the zone command with the default settings, add them to the admin group:

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

```cfg
add_principal identifier.license:xxxxxxxxxxxxxxxx group.admin
```

{% endcode %}


---

# 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-emotes/commands.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.
