| ▲ | deathanatos 2 hours ago | |
> The tokens are their own independent objects that act identical to the original, but are removed from the game if they change zones. This is still model-able with a qtx×type structure. Yes, a token Scute Swarm might be a different object vs. a Scute Swarm, but that's still pretty finite:
> Let's say I have 128 scute swarms, and play a land. That land triggers all 128 scute swarms, causing them to create copies of themselves.Sure, but we can represent this as "the 256× Scute Swarm stack has triggers on when lands are played", so, in effect, we have two trigger registrations, but representing here 257 separate firings of that trigger. E.g., our stack would be something like,
> Priority then goes to the next player, who can respond (which will add another thing to the stack), before passing back to me. The top trigger on the stack resolves putting a creature on the battlefield (which might cause more triggers to be added to the stack), and then that priority passing happens again until the stack is empty.Now, this is definitely more complicated, but I think we can still do it with reasonable resource consumption. At the moment we execute that a player can respond to the stack, we let them do so, or let them declare (probably secretly) where in the stack to interrupt (including not at all). E.g., a player's response could be summarized as "I'll permit all 256 Swarm landfall actions to resolve", and if all players do so, then we can batch resolve them. If any player chooses something different (such as "I'm doing this now", or "I'm permitting 20 to resolve, and then interrupting", then we can allow that (and cancel any other players' commands to permit the resolutions, as someone else doing something might cause them to reconsider, of course). It would be pretty hard to say if this'll hold over the entire game (there may be cases where batch consideration just does not work) but I think this is going to be "good enough" for most sane play. | ||