> 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/gangs/cuxial-gang-app/commands.md).

# Commands & permissions

Staff commands and in-game keys of Cuxial Gang App.

Cuxial Gang App has no player commands: everything is done from the phone. The two commands it adds are for staff and play a scene between two players.

## Commands

| Command                               | Who           | What it does                                                   |
| ------------------------------------- | ------------- | -------------------------------------------------------------- |
| `/kokkaduo <scene> <escort> [client]` | `group.admin` | Starts a scene between two players seated in the same vehicle. |
| `/kokkaduostop <id1> [id2]`           | `group.admin` | Stops the scene of one or two players.                         |

### /kokkaduo

| Parameter | Value                              | Description                                                                  |
| --------- | ---------------------------------- | ---------------------------------------------------------------------------- |
| `scene`   | `company`, `oral`, `full` or `gfe` | Scene to play. `full` and `gfe` play the same animation.                     |
| `escort`  | server id                          | Player in the front passenger seat.                                          |
| `client`  | server id, optional                | Player in the driver seat. The staff member who runs the command if omitted. |

Both players must already be in the vehicle, each in their seat. A player in the wrong seat, or on foot, gets a notice and their side of the scene does not start. The escort and the client cannot be the same player.

```
/kokkaduo full 12 7
```

## Permissions

Both commands are restricted to the `group.admin` principal. Add your staff to it in `server.cfg`:

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

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

{% endcode %}

What each player sees inside the app does not depend on permissions. It depends on their role in Cuxial Gang: member, boss, mule, police or none.

## Keys

Used during a booking of the escort service.

| Key                 | What it does                                                                |
| ------------------- | --------------------------------------------------------------------------- |
| Vehicle horn (hold) | Invites the companion into the front passenger seat.                        |
| <kbd>Enter</kbd>    | Starts the booked services once the vehicle is stopped in a discreet place. |

Both are game controls set in `data/kokka.lua` (`HornControl` and `StartKey`).


---

# 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/gangs/cuxial-gang-app/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.