This creature enters with three oil
countersTo 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) on it.
At the beginning of combat on your turn, you may remove an oil
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) from this creature. When you do, target creature you control gains your choice of
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),
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),
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), or
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) until end of turn.