> For the complete documentation index, see [llms.txt](https://guide.crownicles.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.crownicles.com/en/notions-principale/alterations-detat.md).

# State alteration

The state alteration defines the current user's status. Some alterations might affect some of the games' actions.

### &#x20;List of the different alterations

| :smiley:              | No state alteration | **Ø**        |
| --------------------- | ------------------- | ------------ |
| :baby:                | Beginning status    | **Ø**        |
| :scream:              | Scared              | **15min**    |
| :confounded:          | Confused            | **40min**    |
| :drooling\_face:      | Starving            | **50m**      |
| :cold\_face:          | Frozen              | **1h**       |
| :foot:                | Hurting feet        | **1h50**     |
| :sleeping:            | Asleep              | **Variable** |
| :zany\_face:          | Drunk               | **4h**       |
| :face\_with\_monocle: | Lost                | **4h30**     |
| :head\_bandage:       | Injured             | **5h**       |
| :nauseated\_face:     | Sick                | **5h30**     |
| :dizzy\_face:         | Strongly injured    | **11h**      |
| :lock:                | Locked              | **24h**      |
| :clock2:              | Busy                | **Variable** |
| :skull:               | Dead                | **Ø**        |

{% hint style="warning" %}
The "Locked" state alteration is the only alteration that restrains access to the shop. Also, it cannot be removed with a guild reward.
{% endhint %}

{% hint style="danger" %}
The "Dead" status locks every bot's command, expect`/respawn.`
{% endhint %}

### Alteration state care

Except the "Dead" state, every alteration can be cured by themselves over time.

It is still possible to get rid of an alteration without waiting, though.

#### Get an "Heal state alterations"

You can purchase a status effect cure from the shop using the `/shop` command. This purchase will cost you 510 of money or less, depending on the time remaining. This purchase will cancel your status alteration and advance your journey by 10 minutes , allowing you to obtain a new report.

{% hint style="info" %}
The alteration state care is also one of the rewards of the guild daily command from a certain level.
{% endhint %}

{% hint style="warning" %}
Tokens are the only way to cure the ‘busy' status effect; you may need up to five for the longest ones.
{% endhint %}

#### Various way to make time go faster

Some objects and some potions can make the time go faster for some moment. When those are used, it is like if the time was going forward faster, but only for you.

You can also move forward 10 minutes on your journey by using tokens :coin:.


---

# 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://guide.crownicles.com/en/notions-principale/alterations-detat.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.
