(As this Saga enters and after your draw step, add a lore
counterTo counter a spell or ability is to cancel it: remove it from the stack without resolving it. A counter on an object or player is instead a marker that changes characteristics or interacts with rules or abilities; for example, a +1/+1 counter modifies a creature’s power and toughness. (CR 701.6; 122.1).)
I —
ScryTo “scry N” means to look at the top N cards of your library, then put any number of them on the bottom of your library in any order and the rest on top of your library in any order.
If a player is instructed to scry 0, no scry event occurs. Abilities that trigger whenever a player scries won’t trigger.
If multiple players scry at once, each of those players looks at the top cards of their library at the same time. Those players decide in APNAP order (see rule 101.4) where to put those cards, then those cards move at the same time.
An ability that triggers whenever a player scries triggers after the process described in rule 701.22a is complete, even if some or all of those actions were impossible. (CR 701.22) 2.
II — You gain 2 life.
III —
ExileTo exile an object, move it to the exile zone from wherever it is. See rule 406, “Exile.” (CR 701.13) this Saga, then return it to the battlefield transformed under your control. //
First strikeFirst strike is a static ability that modifies the rules for the combat damage step. (See rule 510, “Combat Damage Step.”)
If at least one attacking or blocking creature has first strike or double strike (see rule 702.4) as the combat damage step begins, the only creatures that assign combat damage in that step are those with first strike or double strike. After that step, instead of proceeding to the end of combat step, the phase gets a second combat damage step. The only creatures that assign combat damage in that step are the remaining attackers and blockers that had neither first strike nor double strike as the first combat damage step began, as well as the remaining attackers and blockers that currently have double strike. After that step, the phase proceeds to the end of combat step.
Giving first strike to a creature without it after combat damage has already been dealt in the first combat damage step won’t preclude that creature from assigning combat damage in the second combat damage step. Removing first strike from a creature after it has already dealt combat damage in the first combat damage step won’t allow it to also assign combat damage in the second combat damage step (unless the creature has double strike).
Multiple instances of first strike on the same creature are redundant. (CR 702.7)