Managed to get 2 creatures counted and then it stopped.
Didn't count any further creatures added to the board.
Second round seemed to count fine... Confused what's going on...
It also doesn’t count creatures put into play with Killer Instinct at all
That node is a train wreck
So has anybody figured out what actually counts for the summon objective? I managed to cast 6-7 creatures plus two Karn tokens, but only got 3 counted.
It has nothing to with actually "summoning creatures" Some count, most don't. It has a lot more interactions with dealing with the graveyard but there is really no method to its madness, some cards count twice. I had one match that i had could count for every card counted, but there rest i still have no idea.
You have to summon rare or lower cards. The objective doesn't care about card type, just rarity.
Oh yeah, that totally is clear with "Summon"... 🙄
Except that I've had cards NOT count and then some count three times and my deck has three Mythical creatures in it, so not sure it's that.
I have them coming in via:
Deadbridge Chant
Finale of Eternity and
Cauldron's Gift.
Still randomly counting or not counting them.
Still, I hope everyone in Brazil at Oktagon is enjoying the Festival... 😑
Having had the benefit of team mates exploring the hiccup in the objective I am ensuring that I CAST 4 common- rare cards to make sure the objective gets hit while this version of the event is running.
Its not how it should be but it is the way it is running and it will be over soon enough. Then the devs can go about creating a new mystery objective for the next outing.
It's none of all this. It counts spells. Can't believe they messed up this objective, which has been used for ages.
Edit: I've tried casting creatures, summoning creatures, summoning tokens, casting Vanguards and I noticed it only counts spells 100% of the times.
@Avahad that sounds like a mad fun idea! Objective: Guess what?
After recording several videos and watching other videos and counting each card being played over the last couple days running in this event I firmly believe that @Opperstamper is correct about summoning/casting rare cards or lower. No mythic or MP is counting toward objective that we have been able to count for. Is it possible you are only running mythic creatures in your deck? It definitely is a mind blowing objective that really got messed up.
I believe it's also spells.
The evidence I've observed also seems to coincide with the functionality @Opperstamper and @DerekRogers mentioned. Thus far, I haven't been able to reproduce any suggestions from others about mythic and masterpiece cards believed to count towards the Commander objective, and I haven't independently observed any instances of that in the games I've tracked carefully on that node during this event.
As a summary of the hypotheses I've attempted to test thus far and evidence consistent with the conclusion that the objective is most likely based on rarity of cast or summoned cards up to this point:
Hypothesis 1: Enemy creatures count towards the objective
Contradictory evidence: Opposing Gaea's Revenge did not count
Hypothesis 2: All spells count towards the objective
Contradictory evidence: Stitch in Time, Finale of Revelation, and Electrodominance did not count
Hypothesis 3: All spells without stored mana count towards the objective
Contradictory evidence: Stitch in Time did not count
Hypothesis 4: Cards that put other cards in the graveyard count towards the objective
Contradictory evidence: Talent of the Telepath and Beacon Bolt counted, while Glimpse the Unthinkable did not count
Hypothesis 5: Spells that deal damage or destroy enemy creatures count towards the objective
Contradictory evidence: Destroying an enemy creature with Electrodominance did not count
Hypothesis 6: Nissa 4's tokens count towards the objective
Contradictory evidence: They appeared not to count in a recorded test game.
Current hypothesis: The objective functions as though the text were "Cast or summon 4 or more common, uncommon, or rare cards" (cards summoned without being cast appear to count based on the behavior of Blood Operative and Cauldron's Gift, while tokens appear not to count based on the behavior of Bolas 1's second ability, Nissa 4's first and third abilities, and Turn to Frog)
Contradictory evidence: None observed thus far
Consistent evidence:
Edit: Removed video links to comply with forum rules; if anyone in the forum community is interested in examining those, message me privately or on other platforms for them
That's some pretty extensive testing @Dodecapod, thanks! We had it by first charge, tested thoroughly with a lot of players in our group before posting here at 99.9% certainty. I'd say this proves it to 100%.
[MOD MIC ON] Due to the forum rule not allowing videos with player names in them, please feel free to send video links to me directly. I will collect and send them to @Oktagon_Support upon her return from the Carnival holiday, so she can get them to the devs quickly. Please only send YouTube links. Google Drive permissions have proven problematic in the past.
Also thank you! To everyone who is working hard to make sense of this extremely frustrating bug! You are an amazing community! [//MOD MIC]
I checked the cards in my current deck. I do NOT use any mythic or MP spells, so assuming your observation is correct, the objective reads:
Commander: cast 4 or more COMMON, UNCOMMON, or RARE SPELLS.
From my experience it’s « cast anything that isn’t mythic ». I don’t have any MP in my deck to test those though.
I'd like to say I'm shocked that nobody at Oktagon QC noticed that one of their objectives worked in no way like it was written, but honestly I would have been more shocked if all 4 of the objectives worked properly.
Nice job testing everyone, these are some pretty detailed analysis that Oktagon should be paying you for (especially @Dodecapod , great job man)
Oktagon_Support said: Hello guys,This issue with Commander objective is already confirmed and will be correct on the next time this event runs.Thank you for the feedback and for your patience.
Mburn7 said: Oktagon_Support said: Hello guys,This issue with Commander objective is already confirmed and will be correct on the next time this event runs.Thank you for the feedback and for your patience. Just curious, did you guys figure out what the objective was actually checking?