FlyingFlying is an evasion ability.
A creature with flying can’t be blocked except by creatures with flying and/or reach. A creature with flying can block a creature with or without flying. (See rule 509, “Declare Blockers Step,” and rule 702.17, “Reach.”)
Multiple instances of flying on the same creature are redundant. (CR 702.9)
At the beginning of each end step, if you gained 5 or more life this turn,
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) a 4/4 white Angel creature token with
flyingFlying is an evasion ability.
A creature with flying can’t be blocked except by creatures with flying and/or reach. A creature with flying can block a creature with or without flying. (See rule 509, “Declare Blockers Step,” and rule 702.17, “Reach.”)
Multiple instances of flying on the same creature are redundant. (CR 702.9) and
vigilanceVigilance is a static ability that modifies the rules for the declare attackers step.
Attacking doesn’t cause creatures with vigilance to tap. (See rule 508, “Declare Attackers Step.”)
Multiple instances of vigilance on the same creature are redundant. (CR 702.20).
: Until end of turn, this creature gets +2/+2 and gains
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).