Mass Removal Effects

[Kabuki]

When an effect (Supernova, Tidal Wave, Lightning Strike, etc.) removes multiple allies from play at the same time, what determines the order in which the allies are sent to the graveyard?

And on a related note, if an effect is used which kills multiple allies, and you have an Earthen Protector in play which is not killed by that effect, which ally will the Protector save?

[Maldazar]

Really good questions, specialy the first one I would like to know the answer, because I play lots of Shadow Knights in one of my deck and then this makes a huge diference..

I always thought it was 'last ally played on top', but I have already seen that this is not true, but it's also not always first ally played first. Actualy I think its random.

[Kabuki]

I thought it was left to right (first in, last out) for a while, but quickly realized that wasn't the case. I've been trying to figure it out in game, without any success, so thought it would be easier just to ask.

[Warr Byrd]

Originally, mass removal operated on a FIFO (First In, First Out) system, but this was changed to random order in a later update (1.27 if I remember correctly).

If multiple allies are killed at once, then Earthen Protector returns the first one to die. Since the order of death is random, Earthen Protector returns a random ally.

[BlanketEffect]

The order of elimination is completely random. There is no pattern or order to detect.

[Dai]

I think this could be a problem for the physical card game, if there is a rule how to put the allies dead to the graveyard this should be more clear how to do it, otherwise, randomizing it you have to shuffle the dead cards and put to the graveyard... it's not a very big problem but is easy to make it wrong and put allies in the order of the owner wants.

[razcrux]

I think this could be a problem for the physical card game, if there is a rule how to put the allies dead to the graveyard this should be more clear how to do it, otherwise, randomizing it you have to shuffle the dead cards and put to the graveyard... it's not a very big problem but is easy to make it wrong and put allies in the order of the owner wants.

Shuffling your allies and putting them in the grave shouldn't be that hard to do, though I agree it will need to be in a rules. Mojumbo is in charge of the rule book so he should make sure it has inclusion.

[glencocoe]

When an effect (Supernova, Tidal Wave, Lightning Strike, etc.) removes multiple allies from play at the same time, what determines the order in which the allies are sent to the graveyard?

And on a related note, if an effect is used which kills multiple allies, and you have an Earthen Protector in play which is not killed by that effect, which ally will the Protector save?

It's always the leftmost allies to rightmost allies, top to bottom respectively. So basically, if you have allies on the board like this:

1, 2, 3,

Then they get wiped, 3 is on the bottom of the graveyard, 2 in the middle, then 1 on top. This is also why it is very wise to put 5cc cards down first when playing wipe-happy players so your shadow knight can recurse them.

Edit: it's been like this since 1.29 sooo....this random thing idk what people are talking about unless you meant an update after 1.29...

[Warr Byrd]

No, I just confirmed that the order is random via a Custom AI match, weenie rush Jericho v weenie rush Jericho. My allies were played Kris, Puwen, Blake, Birgitte, Tainted Oracle, and killed Kris, Blake, Tainted Oracle, Puwen, Birgitte. The AI's allies were played Kris, Birgitte, Katrin, Puwen, and killed Puwen, Kris, Katrin, Birgitte. If that's not random, I'd like to know what it is.

[glencocoe]

No, I just confirmed that the order is random via a Custom AI match, weenie rush Jericho v weenie rush Jericho. My allies were played Kris, Puwen, Blake, Birgitte, Tainted Oracle, and killed Kris, Blake, Tainted Oracle, Puwen, Birgitte. The AI's allies were played Kris, Birgitte, Katrin, Puwen, and killed Puwen, Kris, Katrin, Birgitte. If that's not random, I'd like to know what it is.

Hmmm...