> 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/police-and-medical/cuxial-diseases/commands.md).

# Commands & permissions

Staff commands of Cuxial Diseases to assign, cure and test diseases and pregnancies, and who can use them.

Cuxial Diseases adds two commands, both for staff. Players have no commands and no keys: they interact with the system through items and, with `lb-phone`, the Health app.

## /disease

```
/disease <action> [id] [disease | symptom] [stage]
```

`id` is the server id of the player. `disease` is an `id` from `data/diseases.lua`.

| Command                                 | What it does                                                                                     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------ |
| `/disease list`                         | Lists the ids of every disease in the catalog.                                                   |
| `/disease status <id>`                  | Shows the active diseases of the player, with stage and status. Diagnosed cases are marked `dx`. |
| `/disease infect <id> <disease>`        | Gives the disease to the player, in its first stage. Ignores immunity. The player is notified.   |
| `/disease cure <id> <disease>`          | Cures the disease and applies the immunity set in the catalog. The player is notified.           |
| `/disease treat <id> <disease>`         | Applies one dose of the treatment, with the same rules as taking the item.                       |
| `/disease diagnose <id> <disease>`      | Marks the case as diagnosed.                                                                     |
| `/disease stage <id> <disease> <stage>` | Moves the case to that stage and restarts its timer.                                             |
| `/disease symptom <id> [symptom]`       | Plays a symptom on the player to test it. No disease is needed.                                  |
| `/disease onboarding <id>`              | Restarts the vaccination deadline of the player, with the hours of `onboarding.hours`.           |

### Testing symptoms

`/disease symptom` is the quick way to see each animation and effect without waiting for a real case.

| Value       | Effect                                                                   |
| ----------- | ------------------------------------------------------------------------ |
| `all`       | Plays the six symptoms one after another. Used when no symptom is given. |
| `cough`     | Cough.                                                                   |
| `dizziness` | Stumble and screen distortion.                                           |
| `vomit`     | Vomiting.                                                                |
| `fatigue`   | Out of breath.                                                           |
| `blur`      | Blurred vision.                                                          |
| `shake`     | Camera shake.                                                            |

```
/disease symptom 12 vomit
```

### A complete test

```
/disease infect 12 <disease>
/disease status 12
/disease stage 12 <disease> <stage>
/disease treat 12 <disease>
/disease cure 12 <disease>
```

When an action cannot be done, the command answers with the reason:

| Reason                | Meaning                                                                |
| --------------------- | ---------------------------------------------------------------------- |
| `already_infected`    | The player already has that disease.                                   |
| `not_infected`        | The player does not have that disease.                                 |
| `no_treatment`        | The disease has no `treatment` in the catalog.                         |
| `too_soon`            | The previous dose is still active.                                     |
| `onboarding_disabled` | The vaccination deadline is turned off, or its disease does not exist. |

## /pregnancy

```
/pregnancy <action> <id> [fatherId]
```

| Command                          | What it does                                                                                                  |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `/pregnancy set <id> [fatherId]` | Starts a pregnancy for the player and marks it as known. `fatherId` is the server id of the father; optional. |
| `/pregnancy status <id>`         | Shows week, whether it is known and the days left until birth.                                                |
| `/pregnancy reveal <id>`         | Marks the pregnancy as known, as a positive test would.                                                       |
| `/pregnancy birth <id>`          | Records the birth now.                                                                                        |
| `/pregnancy remove <id>`         | Ends the pregnancy.                                                                                           |

## Permissions

Both commands go through two checks. A player needs both.

| Check                                               | Default       | Where to change it                        |
| --------------------------------------------------- | ------------- | ----------------------------------------- |
| ACE group the command is limited to                 | `group.admin` | `admin.restricted` in `shared/config.lua` |
| Framework permission, asked through `cuxial_bridge` | `admin`       | `admin.permission` in `shared/config.lua` |

Add a staff member to the ACE group in `server.cfg`:

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

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

{% endcode %}

{% hint style="info" %}
Both commands can also be run from the server console, where no permission is checked.
{% endhint %}

## Keys

Cuxial Diseases registers no keys.


---

# 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/police-and-medical/cuxial-diseases/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.