[fixed/closed]Emrakul, the Aeons Torn

[HarlequinCasts]

Describe the Bug:
Different from This Bug

Emrakul, the Aeons Torn occasionally does not trigger his annihilator ability when attacking. This has proven to be a bug that I encounter "in the wild" frequently but have trouble reproducing. It seems like it only happens when he has been cheated into play somehow, and usually due to Show and Tell.

In the attached save game, you can attack with Emrakul, the Aeons Torn and the annihilator ability will not trigger. In a completely clean game, I have not managed to reproduce this, but when it happens, the save game will still reproduce it.

In other cases, annihilator will trigger the first time he attacks, but not the second time.

Which card did behave improperly ?
Emrakul, the Aeons Torn

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
CIA v2 Jan 2014

What exactly should be the correct behavior/interaction ?
Annihilator every time.

Are any other cards possibly affected by this bug ?
Emrakul is the go to bomb card, but perhaps this happens when cheating other eldrazi into play? I will test.

[Korath]

My first reaction is to wonder if the defending player have six permanents he can sacrifice. Annihilator uses impose_sacrifice(), which is broken in CrIAv2; it doesn't make you sacrifice anything unless you can sacrifice the full number of permanents it's asking for.

[HarlequinCasts]

That's what I was wondering too, but here is a save file where the AI only has 3 Forest s in play and does sacrifice them all.

[Korath]

What in its hand, for the other sacrifice bug? (I can load CrIAv2 savegames, but it takes on the order of fifteen minutes.)

[HarlequinCasts]

Here's a screenshot. Basically just your average affinity deck. I was actually curious if perhaps the Arcbound Ravager 's sacrificing on previous turns had lead to the AI thinking it had zero permanents in play or something. But if I debug the AI some extra life and swing again and again it correctly annihilates the other turns...

Like I said, this happens fairly regularly when playing with Show and Tell decks, but in a clean game, simply Show and Tell ing an Emrakul into play does not cause it.

EDIT:
If I make sure the AI has exactly 6 permanents in this case then it seems to sacrifice correctly (just like the known bug you menitoned). What I don't understand is why in a clean game, the AI will sacrifice correctly with less than 6 permanents... Any possibility this is a Duel vs Gauntlet thing?

[Korath]

Won't trigger in that screenshot because there's a total of five permanents in play and in its hand. Well-understood and already fixed. Again, what's in its hand in the case where there's only three permanents in play and it does sacrifice?

[HarlequinCasts]

Aha I did not gather from your description before that it also counted permanents in hand (that's weird!). In the game where it does sacrifice, the AI has 3 Forest s in play and 7 Forest s in hand, so it satisfies the criteria. If I repeat it with 3 Forest s in play and 0 cards in hand the AI sacrifices nothing.

Thanks, this bug is definitely fixed then.