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.)
CreateTo create one or more tokens with certain characteristics, put the specified number of tokens with the specified characteristics onto the battlefield.
If a replacement effect applies to a token being created, that effect applies before considering any continuous effects that will modify the characteristics of that token. If a replacement effect applies to a token entering the battlefield, that effect applies after considering any continuous effects that will modify the characteristics of that token.
Previously, an effect that created tokens instructed a player to “put [those tokens] onto the battlefield.” Cards that were printed with that text have received errata in the Oracle card reference so they now “create” those tokens. (CR 701.7) X 1/1 white Soldier creature tokens with
lifelinkLifelink is a static ability.
Damage dealt by a source with lifelink causes that source’s controller, or its owner if it has no controller, to gain that much life (in addition to any other results that damage causes). See rule 120.3.
If an object is no longer in the zone it’s expected to be in as an effect causes it to deal damage, its last known information is used to determine whether it had lifelink.
The lifelink rules function no matter what zone an object with lifelink deals damage from.
If multiple sources with lifelink deal damage at the same time, they cause separate life gain events (see rules 119.9–10).
Multiple instances of lifelink on the same object are redundant. (CR 702.15).