> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/playcanvas-toolkit/building-with-playcanvas-toolkit/conditions.md).
# Conditions
Learn how use Conditions in your VIVERSE Worlds, and how to link them to Triggers
***
## About
Conditions is additional convenience layer on top of Triggers, allowing creators to string multiple Triggers together, either in parallel or in sequential mode. Conditions can be used with Triggers interchangeably, for example when linking them to Actions.
## Usage
Conditions support 2 types of configuration:
* **Sequential (AND)** — creates an activation only when **both** input Triggers were activated within a given **Time Window**
* **Parallel (OR)** — creates an activation when at **any** input Trigger is activated. The **Time Window** here helps to prevent or control **double activation** when both inputs are triggered one after another
For practical usage examples, please refer to [Triggers](/playcanvas-toolkit/building-with-playcanvas-toolkit/triggers.md#usage) or [Actions](/playcanvas-toolkit/building-with-playcanvas-toolkit/actions.md#usage) respectively!
## Reference
***
{% columns %}
{% column width="25%" %}
`And`
{% endcolumn %}
{% column width="50%" %}
Activates when both **Trigger A** and **Trigger B** are activated within a given `Time Window`. Leaving time window at 0 (default) means no time restriction is applied
{% endcolumn %}
{% column width="24.999999999999986%" %}
{% endcolumn %}
{% endcolumns %}
***
{% columns %}
{% column width="25%" %}
`Or`
{% endcolumn %}
{% column width="50%" %}
Activates when either **Trigger A** or **Trigger B** is activated within a given `Time Window`. Leaving time window at 0 (default) means no time restriction is applied
{% endcolumn %}
{% column width="24.999999999999986%" %}
{% endcolumn %}
{% endcolumns %}
***
---
# 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.viverse.com/playcanvas-toolkit/building-with-playcanvas-toolkit/conditions.md?ask=&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.
