Rule evolution
Rule 509.3
Earliest archived Rules release: 2009-10-01 · 1 wording revision · 0 renumberings
Earliest archived Rules release509.3Details
Third, for each creature that's blocking multiple creatures (because some effect allows it to), the defending player announces its damage assignment order among the attacking creatures. This turn-based action doesn't use the stack. (During the combat damage step, a blocking creature can't assign combat damage to a creature it's blocking unless each creature ahead of that blocked creature in its order is assigned lethal damage.)
Wording changed509.3Details
Third, for each blocking creature,
that'stheblockingdefendingmultipleplayercreaturesannounces(becausethatsomecreature'seffectdamageallowsassignmentit to)order,thewhichdefendingconsistsplayerofannouncestheitscreaturesdamageit'sassignmentblocking in an orderamongofthethatattackingplayer'screatureschoice. (During the combat damage step, a blocking creature can't assign combat damage to a creature it's blocking unless each creature ahead of that blocked creature in its order is assigned lethal damage.) This turn-based action doesn't use the stack.(During the combat damage step, a blocking creature can't assign combat damage to a creature it's blocking unless each creature ahead of that blocked creature in its order is assigned lethal damage.)Removed509.3Details
Third, for each blocking creature, the defending player announces that creature’s damage assignment order, which consists of the creatures it’s blocking in an order of that player’s choice. (During the combat damage step, a blocking creature can’t assign combat damage to a creature it’s blocking unless each creature ahead of that blocked creature in its order is assigned lethal damage.) This turn-based action doesn’t use the stack.