Skip to content

Barba.cba#44929

My feedback

1 result found

  1. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Barba.cba#44929 commented  · 

    Exactly as the other player described! It happens to me on PC when I play with a mono-white deck that uses the “Soul Sisters” strategy — it’s full of low-cost creatures that gain life and add +1/+1 counters. I play in the Historic Ranked format, and I’m wondering: does the handling of events that trigger other events — making the current stack longer than in the previous step — overload the RAM? VRAM? Idk...

    It happens specifically with a combo I use when I fill the graveyard somehow (either with Day of Judgment or something similar, or when I’m up against a mill deck), and then I cast Raise the Past. A bunch of creatures enter the battlefield all at once, and as the triggers resolve, it automatically builds a stack that grows like branching nodes, since resolving one event triggers many others (in my case, life gain and +1/+1 counter effects).

    There should be a process that measures the stack length and stores part of it on disk when it gets too large, or maybe assigns the total outcome based on the sum of all +1/+1 counters through another interface — and the opponent could see the node tree only if they remotely choose to respond.

    Barba.cba#44929 supported this idea  · 

Feedback and Knowledge Base