> 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/vehicles/cuxial-gasstations/commands.md).

# Commands & permissions

Commands, default keys, admin access and staff roles of Cuxial Gas Stations.

Players use one command; the rest are for staff and for tuning. Most of the script is used through interaction points, not commands.

## Commands

| Command                  | Who                    | What it does                                                                                                                                                                          |
| ------------------------ | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/detailing`             | Everyone               | Opens the mobile detailing menu to request a wash where you are. Name set in `mobile.command`; `false` removes it.                                                                    |
| `/gasadmin`              | Admins                 | Opens the admin panel. Name set in `admin.command`.                                                                                                                                   |
| `/washerlivery [index]`  | `group.admin`          | Changes the livery of the nearby detailing van. Without a number it moves to the next one. Name and restriction set in `wash.commands.livery`; `name = false` removes it.             |
| `/washdebug`             | Admins                 | Toggles a diagnostics overlay for the water jet, with the detail of each wash stage. Registered with `wash.debugCommand.enabled = true` or with debug on.                             |
| `/gas_fill [model]`      | ACE `command.gas_fill` | Tuning tool. Spawns the vehicle and lets you place the point where the loading hose connects, then prints the values for `loading.fillPoints` to the F8 console. `tanker` if omitted. |
| `/gasaudio <wash\|hose>` | Debug mode             | Plays the sounds of a sound bank. Only registered with debug on. Name set in `wash.audioDebugCommand`.                                                                                |
| `/washjet`               | Debug mode             | Tuning tool for the position of the water jet particle. Only registered with debug on.                                                                                                |

{% hint style="info" %}
Debug mode is `debug = true` in `shared/config.lua` or `setr cuxial_gasstations_debug 1`. `/washdebug` checks the same admin access as the panel.
{% endhint %}

## Keys

Every key can be rebound by each player in the GTA key settings.

| Key           | What it does                                             | Default from             |
| ------------- | -------------------------------------------------------- | ------------------------ |
| <kbd>F7</kbd> | Collapses or expands the mission overlay during a run.   | `ui.mission.toggleKey`   |
| <kbd>G</kbd>  | Switches the pressure gun between water and soap.        | `wash.keys.switchMode`   |
| <kbd>E</kbd>  | Drops the gun after the hose breaks.                     | `wash.keys.dropGun`      |
| <kbd>Y</kbd>  | Accepts a wash offer (NPC customer or mobile detailing). | `wash.offers.acceptKey`  |
| <kbd>X</kbd>  | Declines a wash offer.                                   | `wash.offers.declineKey` |

The keys of the point editor are listed in the [Features guide](/scripts/vehicles/cuxial-gasstations/features.md#point-editor).

## Admin access

The admin panel and every admin action are checked on the server. A player gets in with either of these:

* the ACE in `admin.ace`, `cuxial_gasstations.admin` by default;
* the framework permission in `admin.permission`, `admin` by default.

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

```cfg
add_ace group.admin cuxial_gasstations.admin allow
add_ace group.admin command.gas_fill allow
```

{% endcode %}

## Staff roles

Station staff have a role from 1 to 3. An employee can do an action when their role is equal to or higher than the value in `roles.actions`. The owner can do everything. A value of 4 means owner only.

| Role  | Name     | With the default config                                                                                                                      |
| ----- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| 1     | Basic    | Drive contracts, use fleet vans, clean spills, see the summary and the contracts.                                                            |
| 2     | Advanced | Also: set prices, post and delete jobs, buy upgrades, unlock chargers, configure washes, NPC customers and mobile detailing.                 |
| 3     | Full     | Also: rename, deposit and withdraw, manage staff and commissions, buy and sell fleet vehicles, promotions, rental settings and read notices. |
| Owner | Owner    | Also: sell the station and change the notice settings.                                                                                       |

The full list of actions and pages is in [Configuration](/scripts/vehicles/cuxial-gasstations/configuration.md#roles).


---

# 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/vehicles/cuxial-gasstations/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.
