502.9c If all the creatures blocking an attacking creature with trample are removed from combat before the combat damage step, all its damage is assigned to the defending player.

502.9d Assigning damage from a creature with trample considers only the actual toughness of a blocking creature, not any abilities or effects that might change the final amount of damage dealt.

Example: A 6/6 green creature with trample is blocked by a 2/2 creature with protection from green. The attacking creature’s controller must assign at least 2 damage to the blocker, even though that damage will be prevented by the blocker’s protection ability. The attacking creature’s controller can then choose to assign the rest of the damage to the defending player.

502.9e When there are several attacking creatures, it’s legal to assign damage from those without trample so as to maximize the damage of those with trample.

Example: A 2/2 creature with an ability that enables it to block multiple attackers blocks two attackers: a 1/1 with no special abilities a 3/3 with trample. The attacking player could assign 1 damage from the first attacker and 1 damage from the second to the blocking creature, and 2 damage to the defending player from the creature with trample.

502.9f Multiple instances of trample on the same creature are redundant.

502.10. Banding

502.10a Banding is a static ability that modifies the rules for declaring attackers and assigning combat damage.

502.10b As a player declares attackers, he or she may declare that any number of those creatures with banding, and up to one of those creatures without banding, are all in a “band.” (Defending players can’t declare bands but may use banding in a different way; see rule 502.10h.)

502.10c A player may declare as many attacking bands as he or she wants, but each creature may be a member of only one of them.

502.10d Once an attacking band has been announced, it lasts for the rest of combat, even if something later removes the banding ability from one or more creatures. However, creatures in a band that are removed from combat are also removed from the band.

502.10e If an attacking creature becomes blocked by a creature, each other creature in the same band as the attacking creature becomes blocked by that same blocking creature.

Example: A player attacks with a band consisting of a creature with flying and a creature with swampwalk. The defending player, who controls a Swamp, can block the flying creature if able. If he or she does, then the creature with swampwalk will also become blocked by the blocking creature(s).

502.10f Banding doesn’t cause attacking creatures to share abilities, nor does it remove any abilities. The attacking creatures in a band are separate permanents.

502.10g If one member of a band would become blocked due to an effect, the entire band becomes blocked.

502.10h A player who controls an attacking creature with banding chooses how combat damage is assigned by creatures blocking that creature. A player who controls a blocking creature with banding chooses how combat damage is assigned by creatures it blocks. If the creature had banding when it attacked or blocked but the ability was removed before the combat damage step, damage is assigned normally.

502.10i Multiple instances of banding on the same creature are redundant.

502.11. Bands with Other

502.11a Bands with other is a special form of banding. If an effect causes a permanent to lose banding, the permanent loses all bands with other abilities as well.

502.11b An attacking creature with “bands with other [creature type]” can form an attacking band with other creatures that have the same “bands with other [creature type]” ability. Creatures with banding can also join this band, but creatures without banding can’t. The creatures in this band don’t have to have the creature type specified in the “bands with other [creature type]” ability. Blocking this band follows the same general rules as for banding.

502.11c If an attacking creature is blocked by at least two creatures with the same “bands with other [creature type]” ability, the defending player chooses how the attacking creature’s damage is assigned. Similarly, if a blocking creature blocks at least two attacking creatures with the same “bands with other [creature type]” ability, the attacking player chooses how the blocking creature’s damage is assigned.

502.11d Multiple instances of bands with other of the same type on the same creature are redundant.

502.12. Rampage

502.12a Rampage is a triggered ability. “Rampage N” means “Whenever this creature becomes blocked, it gets +N/+N until end of turn for each creature blocking it beyond the first.” (See rule 309, “Declare Blockers Step.”)

502.12b The rampage bonus is calculated only once per combat, when the triggered ability resolves. Adding or removing blockers later in combat won’t change the bonus.

502.12c If a creature has multiple instances of rampage, each triggers separately.

502.13. Cumulative Upkeep

502.13a Cumulative upkeep is a triggered ability that imposes an increasing cost on a permanent. “Cumulative upkeep [cost]” means “At the beginning of your upkeep, put an age counter on this permanent, then sacrifice this permanent unless you pay [cost] for each age counter on it.” If [cost] has choices associated with it, each choice is made separately for each age counter, then either the entire set of costs is paid, or none of them is paid. Partial payments aren’t allowed.

Example: A creature has “Cumulative upkeep {W} or {U}” and two age counters on it. When its ability next triggers and resolves, the creature’s controller puts an age counter on it and then may pay {W}{W}{W}, {W}{W}{U}, {W}{U}{U}, or {U}{U}{U} to keep the creature in play.

Example: A creature has “Cumulative upkeep-Sacrifice a creature” and one age counter on it. When its ability next triggers and resolves, its controller can’t choose the same creature to sacrifice twice. Either two different creatures must be sacrificed, or the creature with cumulative upkeep must be sacrificed.

502.13b If a permanent has multiple instances of cumulative upkeep, each triggers separately. However, the age counters are not linked to any particular ability; each cumulative upkeep ability will count the total number of age counters on the permanent at the time that ability resolves.

Example: A creature has two instances of “Cumulative upkeep-Pay 1 life.” The creature currently has no counters but both cumulative upkeep abilities trigger. When the first ability resolves, the controller adds a counter and then chooses to pay 1 life. When the second ability resolves, the controller adds another counter and then chooses to pay an additional 2 life.