You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I promise this is the last time I will bring up this topic. I am making this for future reference)
After a lot of thoughts, I still think, by default, when you secure a card, you take it into your play area. (https://arcs.seiyria.com/#7.6.1.1-step-1). If a card is not taken into your play area it needs to explicitly override it.
If the intention for Passage Storm is that it remains in the Court when secured, I think strictly speaking this errata is necessary:
"The text 'Don't remove this card!' should be in body text, not in italics and parentheses."
The text was updated successfully, but these errors were encountered:
turmoilbyrd
changed the title
Passage Storm
Passage Storm to remain in court after secure
Dec 22, 2024
turmoilbyrd
changed the title
Passage Storm to remain in court after secure
Passage Storm remains in court When secured
Dec 22, 2024
And again, I personally think it is fine for Passage Storm to be taken into a player's play area. It won't break anything since crisis will still trigger its Crisis box, hits everything and puts it back into the deck. And there is no way for a player to lose a Vox card in their play area.
turmoilbyrd
changed the title
Passage Storm remains in court When secured
Passage Storm remains in court When secured? Or is taken into play area?
Dec 22, 2024
(I promise this is the last time I will bring up this topic. I am making this for future reference)
After a lot of thoughts, I still think, by default, when you secure a card, you take it into your play area. (https://arcs.seiyria.com/#7.6.1.1-step-1). If a card is not taken into your play area it needs to explicitly override it.
If the intention for Passage Storm is that it remains in the Court when secured, I think strictly speaking this errata is necessary:
The text was updated successfully, but these errors were encountered: