Nova triggers after mimik

[primal delta]

Expected order:

1. A unit in the same row as mimik attacks Nova.
2. Nova triggers.
3. Mimik triggers because of the first unit.

Actual Order:

1. A unit in the same row as mimik attacks Nova.
2. Mimik triggers because of the first unit.
3. Nova triggers.

I have no idea how this computer code is written, but if this were actual cards on a table, and an actual stack of cards to keep track of the order, it'd go in the order I described. Let's imagine a different scenario with one enemy row: frostinger with 99 , baby snowbo with 99 and mimik with 9 ; Nova has 99 , 99 , and 9 . When building up the stack of cards for enemy order, you have to start backwards. (It's a stack, but the expected initial order is like they were all just waiting in line to attack, aka a queue in England. If it were just Nom & Stompy instead of Nova, it's the simple case like it's a queue.)

The mimik has no attack of its own, so doesn't go onto the stack; Baby snowbo goes onto the stack, then frostinger. So the attack order without Nova's reaction is: Frostinger, baby snowbo. Frostinger is removed from the stack and attacks, which means mimik is added to the stack, then frostinger knocks off a from Nova, so her reaction is added to the top of the stack. No other reactions get triggered, so Nova attacks and comes off of the stack. Then mimik comes off the stack to attack, Nova loses another , she's added to the stack again, and attacks again. Then baby snowbo attacks, and everything is stacked the same as frostinger. This stack of cards is how I imagine other reactions, like smackback. 👍

[primal delta]

OK, here's the video showing the wrong order. (Had to crop and trim it.)

[tulip steeple]

This is the correct order

Mimik's reaction gets queued up the moment that Frostinger declares its attack, even before it hits anything

So Nova can't react until the reactions that are already triggered (Mimik's) are finished

The same thing would happen if you had e.g. a card with Smackback get hit instead, Mimik would take priority because it triggers on attack declaration, while Smackback triggers when hit

[wet pelican]

This is why bonescraper prevents infernoko from gaining attack while moko head still gives its allies spice

Since it’s an external trigger, it’s able to shove another effect in before other handles are called, leading to a delay (or in the bonescraper case, complete removal) of the effect.

[primal delta]

I totally disagree with this. A hidden queue of actions means you need to memorize which queues have priority over which other ones. Smackback adds to the stack instantly, which means you don't need to memorize anything or guess. The rest of the game is built around explaining you exactly what actions will happen, based on the text of cards, charms, or abilities attached to cards, without anything hidden.

[tulip steeple]

Well they can't have Mimik's reaction trigger before the card that triggers it attacked

[onyx palm]

That doesn’t sound correct. There are two types of reaction triggers: those that stack and those that queue. Both Mimik and Nova are stack triggers.

I’d have to check the code later to verify (checked and updated!), but I think the order goes

1. Frostinger declares the attack. All prehit effects activate. Notably, Block and Mimik's effect activate.
2. Block has the higher priority (-1 vs. -99), so it resolves first. 1 Block is removed. All EntityDisplayUpdated effects activates (Nova's).
   2*. Nova's effect resolves and her trigger is placed on the top of the stack.
3. Mimik's effect resolves. Its trigger is placed on top of the stack.
4. Frostinger attacks.

[stone yew]

I mean, to me at least this order makes sense when reading the effects. Mimik (and puffball)'s triggers occurs when the unit attacks, then things like TriggerWhenHit/Smackback/Nova happen when they're hit, so at least wording wise this order makes more sense (although I can see the other way of thinking and why it could be confusing)