> For the complete documentation index, see [llms.txt](https://puzzlesystem.gitbook.io/project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://puzzlesystem.gitbook.io/project/manual/standard-logics/simult.md).

# SimultPuzzleLogic

## Use Case

There are 3 platforms in the scene. All of them must be kept activated in order to open the gates. However, they are resetting each time the player comes off it. 

Nevertheless, player is provided with additional props in the scene; 2 heavy rocks. If he will put each rock on 2 of the platforms, and he himself will stand on the 3rd one, he will solve the system.

{% hint style="warning" %}
Note that it's impossible to solve this puzzle by the player only, unless the triggers are overlapping each other. Thus, make sure to specify correct tags if you use default Collider based triggers. More about in the *Triggers* section.
{% endhint %}

## Customisation

None

## Critical Events

### OnSolved

Happens when all triggers are being active at the same time.

### OnFailed

Is not invoked, but coming in the further updates.


---

# 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 dynamically by asking a question.

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

```
GET https://puzzlesystem.gitbook.io/project/manual/standard-logics/simult.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.