Even more summon bugs

EC red/green thread.
Summon 2 werewolves
Summon 2 or less ceeatues

Using Eldest Reborn to get a werewolf from my opponents graveyard.
It counted as one of my 2 or less creature summons but it didn’t count as one of my 2 werewolves.

A coalition-mate of mine said that casting Deploy had the same issue, he got +3 to creature summons but no werewolf summons.

@Oktagon_Daiane I like that you guys are finally clarifying the Summon/Cast issue, but please check that it is working properly in all events.

They’ve a lot to change, and I expect they’re glad that we’re being helpful spotting anomalies!

Can we just get the second objective on that node rewritten instead?

It’s basically ‘summon EXACTLY two wolves or werewolves’

Really frustrating when you draw an Angrath deck with six kill spells.

it’s even worse… summon EXACTLY two WEREWOLVES. In EC, Wolves don’t counts. That’s Terror in the Shadows :wink:

Also, a team mate pointed out that stealing a Werewolf with Exert Influence also counted towards the last objective, but the first objective didn’t count it. Still some things left to fix for you…

I mean, we could go back to the original version of this event now that tokens count again, if you prefer
(summon 6 or more werewolves, summon 6 or more eldrazi)

The other solution is to just make sure you include a non-creature based win condition. That way if your wolves get killed you don’t have to summon more. But yeah, this is a very difficult event again

I don’t think the problem is too few to count for the objectives, but rather that they are deliberately contradictory and too close together. If it was summon 3 or more werewolves and 6 or less creatures overall, that at least allows a modicum of flexibility.

Avacyn’s madness, for example, has deliberately contradictory objectives that are impossible to both fulfill, so you’re left making a choice between them, with the middle ground getting you zero bonus points.

Across Ixalan node 1’s ‘Veteran’ objective says ‘Cast’ but it accepts ‘Summon’.

And that is in English, imagine the chaos playing in Spanish where sometimes Summon and Cast are translated to the same word ‘Lanzar’.

This is a small one: creatures which are stolen from your opponents count as “summoned” (at least, dinosaurs do in the latest Bo4t1 event level 2.3)

I don’t think there’s a necessarily a problem here. Conceptually, “summoning” could well include stealing. However, this distinction is not made clear in the definition of summoning in the MTGPQ Abilities Gallery FAQ page, so I think the definition should be expanded to clearly indicate this (stolen creatures are not, after all, “placed on the battlefield”, they are simply moved around it).

Rising Tensions today (Golgari), Selesnya node counted me stealing a Verdant Force via In Bolas’ Clutches as “casting” a creature with mana cost 15+.

ToA Black node says “Summon Zombies”, but is acting like “Cast Zombies”

This actually makes sense, in a way.

It appears that for some reason each objective in each event must be programmed individually (why that is the case is beyond my expertise). This event was programmed with the “old” rules, and has not been run since the update. So it stands to reason that it would still be the old way.

Don’t make it right, though

I’m bored so I’ll throw out another theory. My guess it’s every named objective that has to be programmed. e.g. in this event it’s:

  • Reanimator
  • Summon 3 or more Zombies in a single fight.
    and they haven’t changed Reanimator yet. But they have done whatever the generic objective name for summon > / < X creatures and some of the other ones.

I know they use some objectives across events so hopefully they aren’t all programmed individually, but who knows.

It does! These are simple changes, but, it can be hard for Oktagon to find all the places they apply on their own, so if we crowdsource all that and find them for them, they can fix them all the faster.