# Energy - Bet on losing

The [player](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/players) receives three *energy* unless her-his [robot](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors/robot)-[actor](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors) remained in the[ ](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field)[energy station](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field/energy-station) [location ](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field)after [conflict](https://metarchy.gitbook.io/welcome-to-metarcy/game-rules/game-turn/phase-4-conflict) resolution.

If in the [energy station](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field/energy-station) [location](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field), after the resolution of the [conflict](https://metarchy.gitbook.io/welcome-to-metarcy/game-rules/game-turn/phase-4-conflict), there are two or more [robots](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors/robot), then each [player](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/players) whose [robot ](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors/robot)remained in the [location](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field) [energy station](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field/energy-station) - receives one [material resource](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/material-resources) *energy*.

*Energy* can be used as **bet to lose in** [**conflict**](https://metarchy.gitbook.io/welcome-to-metarcy/game-rules/game-turn/phase-4-conflict) **resolution**.

When the [player](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/players) sends any [actor](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors) to [location](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/playing-field) with the [RSP-Token](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/rsp-tokens), she-he can also add one *energy* to her-his [actor](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors) as a **bet on losing the conflict resolution**. If her-his [actor](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors) lose the [conflict](https://metarchy.gitbook.io/welcome-to-metarcy/game-rules/game-turn/phase-4-conflict) the [conflict](https://metarchy.gitbook.io/welcome-to-metarcy/game-rules/game-turn/phase-4-conflict) is re-resolved with the [RSP-Tokens](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/rsp-tokens).&#x20;

Each [turn](https://metarchy.gitbook.io/welcome-to-metarcy/game-rules/game-turn),  [player](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/players) can place no more than one bet on each of her-his [actors](https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/actors).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://metarchy.gitbook.io/welcome-to-metarcy/game-review/constituents/material-resources/energy-bet-on-losing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
