# End Conditions

Games end when certain conditions are fulfilled: a player reaches a certain goal, time runs out or all players but one are eliminated. 

{% hint style="success" %}
Set End Conditions to end a game when a condition is fulfilled.
{% endhint %}

Machinations diagrams use End Conditions to specify end states. End Conditions are square Nodes with a smaller, filled square inside (the same symbol that is used to indicate the stop button on most audio and video players).

{% hint style="warning" %}
Machinations checks the End Conditions in a diagram at each time step and stops running immediately when *any* End Condition is fulfilled. In other words, if you have multiple End Conditions in a diagram, it will **stop running as soon as *****any one***** of the End Conditions is met.** For such an example, watch the video below.
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=MB2HlB-DWVo>" %}

End Conditions must be activated by an Activator. In this case, Activators are used to specify the end state of the game.

{% content-ref url="/pages/-LHXjVlUNuLgQW43Qv6W" %}
[Activators](/docs/connections/state-connections/activators.md)
{% endcontent-ref %}


---

# 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://machinations.gitbook.io/docs/end-conditions.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.