DefenderDefender is a static ability.
A creature with defender can’t attack.
Multiple instances of defender on the same creature are redundant. (CR 702.3) (This creature can't attack.)
Whenever this creature is dealt damage,
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) that many 1/1 green Insect creature tokens 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
deathtouchDeathtouch is a static ability.
A creature with toughness greater than 0 that’s been dealt damage by a source with deathtouch since the last time state-based actions were checked is destroyed as a state-based action. See rule 704.
Any nonzero amount of combat damage assigned to a creature by a source with deathtouch is considered to be lethal damage for the purposes of determining if excess damage is being dealt.
The deathtouch rules function no matter what zone an object with deathtouch deals damage from.
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 deathtouch.
Multiple instances of deathtouch on the same object are redundant. (CR 702.2). (Any amount of damage a creature with
deathtouchDeathtouch is a static ability.
A creature with toughness greater than 0 that’s been dealt damage by a source with deathtouch since the last time state-based actions were checked is destroyed as a state-based action. See rule 704.
Any nonzero amount of combat damage assigned to a creature by a source with deathtouch is considered to be lethal damage for the purposes of determining if excess damage is being dealt.
The deathtouch rules function no matter what zone an object with deathtouch deals damage from.
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 deathtouch.
Multiple instances of deathtouch on the same object are redundant. (CR 702.2) deals to a creature is enough to
destroyThe only ways a permanent can be destroyed are as a result of an effect that uses the word “destroy” or as a result of the state-based actions that check for lethal damage (see rule 704.5g) or damage from a source with deathtouch (see rule 704.5h). If a permanent is put into its owner’s graveyard for any other reason, it hasn’t been “destroyed.”
A regeneration effect replaces a destruction event. See rule 701.19, “Regenerate.” (CR 701.8) it.)