> For the complete documentation index, see [llms.txt](https://rules.gatcg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rules.gatcg.com/game-mechanics/game-mechanics-abilities/abilities-resolving-triggered-and-activated-abilities.md).

# Abilities - Resolving Triggered and Activated Abilities

#### General Rules:

1. Resolving activated or triggered abilities follow much of the same rules as [resolving cards](/game-mechanics/game-mechanics-playing-cards/playing-cards-resolution.md), except for how an ability's source is tracked. When an ability is activated or triggered, it resolves in a discrete, instanced timing, unlike static abilities that generate continuous effects.
   1. Rules largely follow and abide by the same as those described in [Resolution: General Rules #1 through 6](/game-mechanics/game-mechanics-playing-cards/playing-cards-resolution.md#general-rules), as well as for [Resolution: Checking Resolution](/game-mechanics/game-mechanics-playing-cards/playing-cards-resolution.md#checking-resolution) 1.b through 1.d. Mentions in these sections regarding card activations should be considered to apply to abilities within the context here.
   2. Activated and triggered abilities will reference a source, similar to how activations/materializations/bestowments reference their source card on the Effects Stack. This source is not moved to the Effects Stack, but it is separately tracked based on either the source card or, if it was an object, the source object from which the ability was triggered or activated.
      1. If the ability was activated or triggered from an object or card, the [last-known information](/game-mechanics/game-mechanics-card-and-object-information.md#last-known-information) of that card/object can be used (according to the rules therein).


---

# 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://rules.gatcg.com/game-mechanics/game-mechanics-abilities/abilities-resolving-triggered-and-activated-abilities.md?ask=<question>&goal=<endgoal>
```

`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.