Last active
July 1, 2018 23:01
-
-
Save manpages/8e297799c8dbcd5e2cae9c5e305ab798 to your computer and use it in GitHub Desktop.
KCI Rules
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
601.2g. If the total cost includes a mana payment, the player then has a | |
chance to activate mana abilities (see rule 605, "Mana Abilities"). Mana | |
abilities must be activated before costs are paid. | |
601.2h. The player pays the total cost in any order. Partial payments | |
are not allowed. Unpayable costs can't be paid. | |
605.3. Activating an activated mana ability follows the rules for | |
activating any other activated ability (see rule 602.2), with the | |
following exceptions: | |
605.3a. A player may activate an activated mana ability whenever they | |
have priority, whenever they are casting a spell or activating an | |
ability that requires a mana payment, or whenever a rule or effect asks | |
for a mana payment, even if it's in the middle of casting or resolving a | |
spell or activating or resolving an ability. | |
605.3b. An activated mana ability doesn't go on the stack, so it can't | |
be targeted, countered, or otherwise responded to. Rather, it resolves | |
immediately after it is activated. (See rule 405.6c.) | |
605.3c. Once a player begins to activate a mana ability, that ability | |
can't be activated again until it has resolved. | |
603.2. Whenever a game event or game state matches a triggered ability's | |
trigger event, that ability automatically triggers. The ability doesn't | |
do anything at this point. | |
603.3. Once an ability has triggered, its controller puts it on the | |
stack as an object that's not a card the next time a player would | |
receive priority. See rule 116, "Timing and Priority." The ability | |
becomes the topmost object on the stack. It has the text of the ability | |
that created it, and no other characteristics. It remains on the stack | |
until it's countered, it resolves, a rule causes it to be removed from | |
the stack, or an effect moves it elsewhere. | |
603.3b. If multiple abilities have triggered since the last time a | |
player received priority, each player, in APNAP order, puts triggered | |
abilities they control on the stack in any order they choose. (See rule | |
101.4.) Then the game once again checks for and resolves state-based | |
actions until none are performed, then abilities that triggered during | |
this process go on the stack. This process repeats until no new | |
state-based actions are performed and no abilities trigger. Then the | |
appropriate player gets priority. | |
116.2a. Triggered abilities can trigger at any time, including while | |
a spell is being cast, an ability is being activated, or a spell or | |
ability is resolving. (See rule 603, "Handling Triggered Abilities.") | |
However, nothing actually happens at the time an ability triggers. | |
Each time a player would receive priority, each ability that has | |
triggered but hasn't yet been put on the stack is put on the stack. | |
See rule 116.5. | |
116.3b. The active player receives priority after a spell or ability | |
(other than a mana ability) resolves. | |
116.3c. If a player has priority when they cast a spell, activate an | |
ability, or take a special action, that player receives priority | |
afterward. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment