quaero#14276
My feedback
2 results found
-
5 votes
An error occurred while saving the comment
quaero#14276
supported this idea
·
-
6 votes
An error occurred while saving the comment
quaero#14276
commented
Same issue as of February. As I see it, there are two ways to fix this. You could highlight the attack trigger's source on the board when highlighting a given Firebender Ascension trigger instead of just highlighting the Firebender Ascension (or any other way to identify where the triggers originally came from).
Another idea is to make the Firebender Ascension triggers to match the order you arranged your attack triggers as the default. This doesn't fix the underlying issue of unidentifiable triggers from a single funneled source, but it does cover like 95% of use cases.
quaero#14276
supported this idea
·
Same issue as of February. As I see it, there are two ways to fix this. You could highlight the attack trigger's source on the board when highlighting a given Firebender Ascension trigger instead of just highlighting the Firebender Ascension (or any other way to identify where the triggers originally came from).
Another idea is to make the Firebender Ascension triggers to match the order you arranged your attack triggers as the default. This doesn't fix the underlying issue of unidentifiable triggers from a single funneled source, but it does cover like 95% of use cases.