> For the complete documentation index, see [llms.txt](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/abilities-and-game-state/11-abilities-trigger-queue-and-continuous-effects/11-1-ability-types-and-sources.md). # 11.1 Ability Types and Sources 11.1.1 Monsnatch recognizes Triggered Abilities and Continuous Abilities. A Momon 'with an ability' must have actual rules text defining an Ability; flavor text or reminder text alone does not qualify. 11.1.2 A Triggered Ability begins with a triggering condition, including At, When, Whenever, or a Timing Header. 11.1.3 A Continuous Ability applies for as long as its stated condition and duration are true. It does not enter the Trigger Queue. 11.1.4 The Source of an Ability is the card or rule that created it. A Snatch directly instructed by an Ability is caused by that Ability. A Snatch Check created by Incite or another Ability, including the Check associated with an Effect-Based Summon it creates, retains that Ability as its cause for Snatch-prohibition purposes. Ordinary On Summon processing before a normal Turn-Based Snatch Check does not make that normal Check Ability-caused. Record the causal Momon Game Object. Use its current Controller when the Snatch is evaluated if it remains on the Arena; otherwise use its last known Controller. Control of the queued Ability itself remains fixed under rule 11.1.6. 11.1.5 A card Ability normally functions only while its Source is face-up on the Arena unless its text identifies another zone or necessarily triggers from a zone change. While a card Ability functions from a Source in a Hand or Void, that Source's Owner controls the Ability unless its text states otherwise. 11.1.6 When a Triggered Ability triggers, fix its Controller at that moment. If its Source is face-up on the Arena, use that Source's Controller. If its Source is in a Hand or Void, use its Owner under [Section 11.1.5](/comprehensive-rules-1.0.0/abilities-and-game-state/11-abilities-trigger-queue-and-continuous-effects/11-1-ability-types-and-sources.md). If the Source leaves the Arena as part of the triggering event, use its Controller immediately before it left the Arena. That Ability Controller does not change later, even if the Source changes Controller or zones before the Ability enters or resolves from the Trigger Queue. 11.1.7 A queued Ability exists independently of its Source. Removing, moving, turning face-down, or changing control of the Source does not remove the queued Ability. 11.1.8 If a queued Ability needs information about a Source that is no longer in the expected zone, use the Source’s last known information immediately before it left that zone. --- # 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://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/abilities-and-game-state/11-abilities-trigger-queue-and-continuous-effects/11-1-ability-types-and-sources.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.