> 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/jobs/cuxial-electrician/commands.md).

# Commands & permissions

Commands, keys and permissions of Cuxial Electrician, and who can use each one.

Cuxial Electrician adds two commands for players and three for staff. The job itself is driven from the NPC panel and the interaction options, not from commands.

## Commands

| Command             | Who               | What it does                                                                                                           |
| ------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `/elecreset`        | Crew owner        | Cancels the job in progress. Trucks, ladders and platforms are removed and nobody is paid.                             |
| `/elecleave`        | Crew members      | Leaves the crew. The owner cannot leave while a job is running; they must reset it first.                              |
| `/eleclist`         | Staff             | Lists the crews: number, members, region and phase. Also works from the server console.                                |
| `/elecclose <crew>` | Staff             | Closes the crew with that number and cancels its job. The action is written to the audit table and to the Discord log. |
| `/elecfast [count]` | Staff, debug only | Marks `count` pending repairs of your own job as done; all of them if omitted. For testing.                            |

{% hint style="info" %}
`<crew>` is required and `[count]` is optional. Every name can be changed in `commands` inside `shared/config.lua`; set `name = false` to disable a command.
{% endhint %}

{% hint style="warning" %}
`/elecfast` only works when debug is on at the moment the resource starts: `debug = true` in the config or `setr cuxial_electrician_debug "1"`. Keep debug off on a live server.
{% endhint %}

## Keys

| Key                  | What it does                                                                                                |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| <kbd>E</kbd>         | Delivers the trucks at the drop-off, repairs from the platform or the ladder, and closes the final summary. |
| <kbd>↑</kbd>         | Raises the platform.                                                                                        |
| <kbd>↓</kbd>         | Lowers the platform.                                                                                        |
| <kbd>G</kbd>         | Climbs down the ladder.                                                                                     |
| <kbd>Y</kbd>         | Accepts a crew invite.                                                                                      |
| <kbd>N</kbd>         | Declines a crew invite.                                                                                     |
| <kbd>Backspace</kbd> | Hides the tip on screen.                                                                                    |

These are the defaults from `keys` in `shared/config.lua`. Each player can rebind them in the GTA key settings.

{% hint style="info" %}
Changing `keys` only affects players who have never joined with the script running. FiveM remembers the binding of everyone else.
{% endhint %}

## Permissions

### Staff commands

`/eleclist`, `/elecclose` and `/elecfast` are limited to the group written in their `restricted` field, `group.admin` by default. Add your staff to that group, or change the field to the group you use:

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

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

{% endcode %}

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

```lua
commands = {
    list = { name = 'eleclist', restricted = 'group.mod' },
    -- ...
},
```

{% endcode %}

### Who can work

| Action                                               | Requirement                                                                                                                                          |
| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Open the panel                                       | Be within `npc.menuDistance` of the NPC and have a job allowed by `job`                                                                              |
| Be invited to a crew                                 | Be within `crew.inviteDistance` of the owner, have an allowed job and not be in another crew that is working or has more members                     |
| Pick the region, start, reset, kick, split the money | Crew owner                                                                                                                                           |
| Start a region                                       | Every member connected, with an allowed job, at the region's `minLevel` or above and out of cooldown; region free when `run.exclusiveRegions = true` |
| Deliver the trucks                                   | Any crew member, at the wheel of a job truck                                                                                                         |


---

# 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/jobs/cuxial-electrician/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.