# Event Triggers

## Overview

Menu items in ArenaLegends become active through `item-settings.trigger`.

Some triggers are generic navigation helpers, while others are menu-specific render states used by a particular screen such as the shopkeeper or battle pass.

***

## Generic Triggers

These generic trigger names are used broadly by the menu system:

* `PREVIOUS_PAGE`
* `NEXT_PAGE`
* `CLOSE_MENU`
* `GO_BACK`
* `IGNORE_BUILD`
* `IGNORE_EVENT`
* `FILTER_ALL`
* `FILTER_OWNED`
* `FILTER_UNOWNED`

***

## Menu-Specific Triggers

ArenaLegends also uses many screen-specific triggers directly in the generated YAML files.

Examples currently present in the menus include:

* `ITEM_BOUGHT`
* `ITEM_CLICK_TO_BUY`
* `ITEM_NOT_ENOUGH_GOLD`
* `ITEM_NO_PERMISSION`
* `ITEM_PREVIEW`
* `CATEGORY_SELECTED`
* `CATEGORY_CLICK_TO_SELECT`
* `ANVIL_CLICK_TO_ROLL`
* `ANVIL_NOT_ENOUGH_GOLD`
* `ANVIL_PREVIEW`
* `MYTHIC_CLICK_TO_ROLL`
* `MYTHIC_NOT_ENOUGH_GOLD`
* `MYTHIC_PREVIEW`
* `DISCARD_ITEM`
* `REWARD_CLAIMABLE`
* `REWARD_CLAIMED`
* `REWARD_LOCKED`
* `REWARD_NO_PREMIUM`
* `TIER_PASSED`
* `TIER_CURRENT`
* `TIER_LOCKED`

***

## Practical Rule

Do not treat trigger names as a universal global enum list for every feature.

Instead:

1. inspect the menu you are editing
2. reuse its existing trigger names
3. keep visual templates aligned with the logic that menu already expects

***

## Example

```yaml
item-bought:
  item-settings:
    trigger: ITEM_BOUGHT
  meta-builder:
    name: "&a{ITEM_NAME}"
```

If the trigger does not match what the menu executor expects, the item may never render in the state you want.

***

## Related Pages

* [Item Builders](/arenalegends/menus/item-builders.md)
* [Shopkeeper](/arenalegends/features/shopkeeper.md)
* [Battle Pass](/arenalegends/features/battle-pass.md)


---

# 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://xerickerspigot.gitbook.io/arenalegends/menus/event-triggers.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.