Multiple Triggered abilities stack order is not chose by player
Wherever I play any ability which triggers in "Whenever you attach" and/or "Whenever this creature attacks" I can't chose the order I want to put them on the stack and so I can't use the correct combination of effects.
It should be possibile to decide triggered abilities order as written in the rule book by APNAP:
Give us the steps to reproduce the bug: 1.1 - play anything with mobilize and something that triggers whenevber a creature attacks or a player attacks 1.2 - attackNote which platform you’re using (PC, Steam, Mac, Android, or iOS): - PC -> Steam Ramo Steam beta: Client stabileVersion Steam: 1751405894
Date build client Steam: sab 28 giu 4:07 UTC -08:00
Date build Web Steam: mar 1 lug 23:19 UTC -08:00
Version API Steam: SteamClient022->Windows 11 10.0.26100 buld 26100Enter the actual results you’re experiencing: I lose games because of it. My mechacs and combinations would be much stronger. It results in hitting 2/3 damages and not gaining 2/3 life points per time so for any type of deck, especially aggro decks.I could be mythic right know with a non meta constructed deck. TY
Enter the expected results of the feature:To be FINALLY able to chose the order of multiple triggered abilities with APNAP rule
Add any relevant screenshots/videosIf you found a workaround, please add workaround steps:
not to activate triggered abilities using a stack data structure constructed as permanents are put into the field (which I found is not the case), or do not push items in the stack using the cards coordinate (it seems to be the case - at least possible but not verified). Instead you should keep a stack data structured empty only for triggerd abilities - for each opponent - and when activating multiple triggered abilities, make the player choose the order with they want to push them into the stack.
-
Rezzahan#77802
commented
First, you CAN disable the autoordering feature. That has been possible for YEARS. Check the settings menu under gameplay (during a game).
Second, if targeting is involved, then order of triggers may not matter, especially if you want to target a token that will be created by one of those triggers. YOU CAN'T DO THAT, no matter the order of the triggers. You have to target something that already exists, you cannot target something that may or may not exist sometime later. Because all targets have to be chosen when the triggers are put on the stack. And they are put on the stack AT THE SAME TIME. None of them can resolve to create a possible target for others.