> For the complete documentation index, see [llms.txt](https://xerickerspigot.gitbook.io/arenalegends/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xerickerspigot.gitbook.io/arenalegends/menus/event-triggers.md). # Event Triggers Event triggers decide which menu item appears for a specific menu state. ## Trigger Key ArenaLegends menus render items based on: ``` item-settings.trigger ``` Example: ```yaml item-settings: trigger: NEXT_PAGE ``` ## Common Triggers ``` PREVIOUS_PAGE NEXT_PAGE CLOSE_MENU GO_BACK IGNORE_BUILD IGNORE_EVENT FILTER_ALL FILTER_OWNED FILTER_UNOWNED ``` ## Screen Triggers Generated menu files also contain triggers specific to a screen. ``` 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 MYTHIC_CLICK_TO_ROLL MYTHIC_NOT_ENOUGH_GOLD REWARD_CLAIMABLE REWARD_CLAIMED REWARD_LOCKED REWARD_NO_PREMIUM TIER_PASSED TIER_CURRENT TIER_LOCKED ``` {% hint style="info" %} Triggers are not one universal list for every menu. When editing a menu, inspect existing entries in the same YAML file first. {% endhint %} ## Example Item ```yaml item-bought: item-settings: trigger: ITEM_BOUGHT meta-builder: name: "&a{ITEM_NAME}" ``` --- # 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: ``` GET https://xerickerspigot.gitbook.io/arenalegends/menus/event-triggers.md?ask= ``` 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.