March of the Multitudes doesn't spawn all tokens from stored mana... [Investigating]

Brakkis
Brakkis Posts: 777 Critical Contributor
edited November 2018 in MtGPQ Bugs & Technical Issues
As the title says, after you've put out 12 soldiers with March of the Multitudes, any repeated casting of the spell only spawns the +3 tokens and ignores the stored mana.

I drew and filled 4 March of the Multitudes with Blue Sun's Zenith. With all 4 at fully stored mana (it only costs 11), the first one cast and spawned 12 soldiers. The subsequent 3 each only spawned 3 tokens. As in, the +3 you're supposed to get on top of the number of stored mana.

I thought it might be a buggy interaction with BSZ so I manually filled 3 of them in a subsequent match and it had the same behavior.

Comments

  • Brakkis
    Brakkis Posts: 777 Critical Contributor
    edited November 2018
    It also has a bugged interaction with Divine Visitation.

    Thus far, each time I have cast it while Visitation is on the field, only 6 tokens are spawned the first time rather than 12.
  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    Wait, there's a Mythic that does not function properly when cast multiple times?  Never seen that before!

    Seriously, you'd think by now those issues would be resolved.
  • Tombstone
    Tombstone ADMINISTRATORS Posts: 1,208 Chairperson of the Boards
    @Brakkis
    Thanks for reporting this. I'd recommend sending a ticket to Customer Support with all the relevant information so they can investigate further. 
  • Matthew
    Matthew Posts: 605 Critical Contributor
    Came here to post this. Thanks for tipping it @Brakkis
  • Tilwin90
    Tilwin90 Posts: 662 Critical Contributor
    edited November 2018
    I can confirm that March of the Multitudes does not work properly!
    No fancy reproduction steps, just cast multiple marches (Without losing your soldiers stack), and notice how only the first grants the X tokens (out of the total of X+3). Subsequent marches will always generate exactly 3 tokens.
    What I still have to test with respect to this is whether convoke can influence this in any way. I'll return with an answer on that.

    @Tombstone
    Is bug reporting via a customer support ticket recommended to actually posting them on the forums here? Just wondering what's more effective for everyone.
  • BenRamaPhoenix
    BenRamaPhoenix Posts: 14 Just Dropped In
    I can also confirm that this card is bugged. 3 tokens max here. 
  • Brigby
    Brigby ADMINISTRATORS Posts: 7,757 Site Admin
    Tilwin90 said:
    -snip-

    Tombstone
    Is bug reporting via a customer support ticket recommended to actually posting them on the forums here? Just wondering what's more effective for everyone.
    I think it depends on the bug. If it's something like "this card isn't behaving correctly" then I don't think submitting a support ticket is 100% necessary, but it certainly doesn't hurt. (They work closely with the QA team when it comes to bug reports)

    If it's an issue that may require information about your account or device though, then submitting a support ticket would definitely be the route to take.
  • Matthew
    Matthew Posts: 605 Critical Contributor
    Brigby said:

    If it's an issue that may require information about your account or device though, then submitting a support ticket would definitely be the route to take.
    It's definitely not an account issue. This is specific to the card, because the same thing is happening to me.
  • DumasAG
    DumasAG Posts: 719 Critical Contributor
    Matthew said:
    Brigby said:

    If it's an issue that may require information about your account or device though, then submitting a support ticket would definitely be the route to take.
    It's definitely not an account issue. This is specific to the card, because the same thing is happening to me.
    Also having this happen.
  • stikxs
    stikxs Posts: 534 Critical Contributor
    edited November 2018
    It might be just the fact that the soldier stack is already on the board that is causing the issue. I just cast March in a match that only gave me the 3 tokens the first time I cast it, and I had a token stack already on the board building from Haazda Marshal.

    edit: After wiping the stack out and recasting March again you get the full 12, and any recasts while the stack is present only give 3.

    edit2: Also noticed when you cast March with a stack already present the 'do you want to cast now?' prompt comes up twice for some reason.
  • Elektrophorus
    Elektrophorus Posts: 150 Tile Toppler
    Really surprised this hasn’t been realized yet.

    Obviously the problem here isn’t casting multiple copies of this card. The problem is with Convoke. If you have any number of creatures, whether they’re tokens or not, it decreases the cap on the Stored Mana portion.

    So, if you have a Stored Mana of 3, but you already have 3 creatures out, it will only spawn 3 tokens instead of 6.

    This is why the card will only spawn 3 tokens with each successive cast, since 9 minus 12 is <0. So it views Stored Mana as 0, then adds 3 due to the card effect.
  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    Elektrophorus said:
    Really surprised this hasn’t been realized yet.

    Obviously the problem here isn’t casting multiple copies of this card. The problem is with Convoke. If you have any number of creatures, whether they’re tokens or not, it decreases the cap on the Stored Mana portion.

    So, if you have a Stored Mana of 3, but you already have 3 creatures out, it will only spawn 3 tokens instead of 6.

    This is why the card will only spawn 3 tokens with each successive cast, since 9 minus 12 is <0. So it views Stored Mana as 0, then adds 3 due to the card effect.
    I did not think of that.  Nor I think did most of the rest of us.  That does make perfect sense, though.

    @Tombstone please alert the devs to look into this
  • stikxs
    stikxs Posts: 534 Critical Contributor
    edited November 2018
    Elektrophorus said:
    Really surprised this hasn’t been realized yet.

    Obviously the problem here isn’t casting multiple copies of this card. The problem is with Convoke. If you have any number of creatures, whether they’re tokens or not, it decreases the cap on the Stored Mana portion.

    So, if you have a Stored Mana of 3, but you already have 3 creatures out, it will only spawn 3 tokens instead of 6.

    This is why the card will only spawn 3 tokens with each successive cast, since 9 minus 12 is <0. So it views Stored Mana as 0, then adds 3 due to the card effect.
    Convoke wouldn't reduce by 12, it has a cap of 6 on this card (unless bugged as well).

    But it does look like convoke is doing it, just did a TG and put down 14 tokens before casting March and only got the 3 guaranteed tokens.
  • Brakkis
    Brakkis Posts: 777 Critical Contributor
    I assumed it had something to do with Convoke interfering with Stored Mana because even on it's first cast it's finicky.

    Thanks for clearing that up.
  • Tombstone
    Tombstone ADMINISTRATORS Posts: 1,208 Chairperson of the Boards
    According to my information, this appears to be an issue with Convoke on this card, and the team is currently aware of this issue. I'll go ahead and add this to bug list.  
  • Tremayne
    Tremayne Posts: 1,710 Chairperson of the Boards
    Assume - Fully charged MotM, first time casting in match.

    question: how many soldiers do you get?


    If your answer is 3, then guess again.



    if 12 then guess again.



    if some multiplier of 3 then guess again.








    and the answer is...






    8, yes you guessed it!!!

    Any math-geniuses who can figure that one out? And yes it is not a trick question. MotM was fully charged.
  • Elektrophorus
    Elektrophorus Posts: 150 Tile Toppler
    Tremayne said:
    Assume - Fully charged MotM, first time casting in match.

    question: how many soldiers do you get?


    If your answer is 3, then guess again.



    if 12 then guess again.



    if some multiplier of 3 then guess again.








    and the answer is...






    8, yes you guessed it!!!

    Any math-geniuses who can figure that one out? And yes it is not a trick question. MotM was fully charged.

    stikxs said:
    Elektrophorus said:
    Really surprised this hasn’t been realized yet.

    Obviously the problem here isn’t casting multiple copies of this card. The problem is with Convoke. If you have any number of creatures, whether they’re tokens or not, it decreases the cap on the Stored Mana portion.

    So, if you have a Stored Mana of 3, but you already have 3 creatures out, it will only spawn 3 tokens instead of 6.

    This is why the card will only spawn 3 tokens with each successive cast, since 9 minus 12 is <0. So it views Stored Mana as 0, then adds 3 due to the card effect.
    Convoke wouldn't reduce by 12, it has a cap of 6 on this card (unless bugged as well).

    But it does look like convoke is doing it, just did a TG and put down 14 tokens before casting March and only got the 3 guaranteed tokens.
    Well, it’s not that Convoke is reducing the mana cost by more than 6. It’s doing exactly that.

    However, when the card checks to see how much Stored Mana was spent to cast it, I bet it’s doing something with checking the total mana spent to cast it

    @Tremayne How many creatures and reinforcements did you have out? You probably had 4 other reinforcements, reducing your Stored Mana from 9 to 5, summoning 5+3 tokens, right?
  • arNero
    arNero Posts: 358 Mover and Shaker
    Yes, Convoke is the source of the bug here.

    I can confirm that using Chord of Calling which I just got, once I have a creature out, the next creature I fetch with Chord can NEVER gain 18 mana, always less.

    So basically, there is a problem with the combination of Convoke and Stored Mana.
  • jayabalard
    jayabalard Posts: 16 Just Dropped In
    If I already have a hunchnof other soldier tokens out from another source or a reinforced leader, I see the same behavior... 

Categories