ConvokeConvoke is a static ability that functions while the spell with convoke is on the stack. “Convoke” means “For each colored mana in this spell’s total cost, you may tap an untapped creature of that color you control rather than pay that mana. For each generic mana in this spell’s total cost, you may tap an untapped creature you control rather than pay that mana.”
The convoke ability isn’t an additional or alternative cost and applies only after the total cost of the spell with convoke is determined.
A creature tapped to pay for mana in a spell’s total cost this way is said to have “convoked” that spell.
Multiple instances of convoke on the same spell are redundant. (CR 702.51) (Your creatures can help
castTo cast a spell is to take it from the zone it’s in (usually the hand), put it on the stack, and pay its costs, so that it will eventually resolve and have its effect. A player may cast a spell if they have priority. See rule 601, “Casting Spells.”
To cast a card is to cast it as a spell. (CR 701.5) this spell. Each creature you
tapTo tap a permanent, turn it sideways from an upright position. Only untapped permanents can be tapped. (CR 701.26) while casting this spell pays for
or one mana of that creature's color.)
Target creature gets +1/+0 and gains
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) until end of turn. (It deals combat damage before creatures without
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).)