-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Arcs] Secure Timing #138
Comments
I'm not sure this problem, if it is one, is solvable without extreme rewrites and issues. I would want a case where this looseness in order actually causes a problem before I targeted a solution. Planet-Eater Loose also, for example, is a case where the When Secured effect specifies a case where the card remains in the Court, while the base rule for Secure says to take the card. Broadly, the When Secured action can modify the base Secure logic. Technically, it makes the most sense to structure the Secure order as:
However, this really buries the lede on the Secure action and I would never want to write it this way in the core rules for the sake of a few cases in the campaign. Is there evidence of wide-scale confusion on this point, or is this confected? |
I don't believe there were any actual issues. This was just turmoilbyrd digging deep. But I would note that it's just kind of related to these attachment cards being looked at more closely (Armistice, etc) I'll poke around a bit more and check in with turmoilbyrd |
from turmilbyrd:
|
For Diplomatic Fiasco, the agents should be returned first—which favors the current logic order. (So Dealmakers would also return the captured agents first.) At this point, I'm content just to let the loose, clashing order of those few Vox cards stand above and clarify that point for Diplomatic Fiasco. If some real issues come up, we can revisit. |
That being said, I think it's fine to clarify the Diplomatic Fiasco order, since that could really affect things. Feel free to put in an FAQ. |
Added to faq240820 branch |
A few Vox cards
Planet-Eater Loose
Council Intrigue
Armistice
their When Secured effects refers to the agents on it. This implies the When Secured effect must be resolved before agents are returned/captured. This contradicts with base rule for Secure action which sequences them the other way. Which way is correct?
The text was updated successfully, but these errors were encountered: