> 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/cores/trigger.md).
# CorePuzzleTrigger
{% hint style="info" %}
This is the core class for the **Trigger** elements. This means that the subclasses of this component also have all properties and methods that are present in here. Make use of it.
{% endhint %}
## Default
The default trigger component should be used when you want to activate it manually within your own script/event.
The component has public methods that you can use for this purpose:
```
///
/// The method that triggers the puzzle step. Active iff the type of the trigger is 'OnMessage'.
///
public virtual void Trigger();
///
/// Deactivates the triggering state manually.
///
public virtual void UnTrigger();
```
{% hint style="info" %}
Note that now we are not talking about the inheritance now, but rather about the completely different script that handles an event that will activate the trigger. In this case, the only thing that this script would need to do is just call out the provided public methods (*Trigger* or *UnTrigger*).
{% endhint %}
The inspector view interface provides you with 3 fields:
* **Allow Multiple Triggering** -- is it allowed to trigger it multiple times? If set to 'true', it will be possible to trigger the object multiple times regardless of its state.
* **OnTriggerEvent** -- callback that happens whenever the trigger is activated.
* **OnUnTriggerEvent** -- callback that happens whenever the trigger is deactivated.
## Inheritance
---
# 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/cores/trigger.md?ask=&goal=
```
`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.