-
Notifications
You must be signed in to change notification settings - Fork 7
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] Survival Override and "do as much as possible" #94
Comments
My opinion is that both should be No Reasoning:
Is a shorthand for
So the "destroy to destroy" clause is put under a "may", this means DAMAP rule, which requires a "must", doesn't apply anymore. And we can apply Guerric's reasoning about "X to Y" construct on the "destroy to destroy" clause
So both actions must be possible (and no DAMAP) |
You cannot. Broadly, the "X to Y" construct should be read as "To do Y, you must do X as a prerequisite." Do you feel this rises to the level of an FAQ entry? |
So how about the other way around, can you destroy 1 Loyal ship to destroy 0 rival ship? (This is what I referred to as Guerric's logic) |
Yes, I will bite this bullet. Thematically it's justified—normally you can't just make ships blow themselves up, but now they've got overrides installed. I'll add this as an FAQ. |
Ok, I am still hoping the "X to Y" constraint works both way (you cannot do X even if you cannot do Y). Because that provides answers for |
Adding retroactive logic like that is incredibly thorny. It would have to exclude cases like Gatekeepers—can I discard it even if I can't place all those ships? No, that would be silly and unintuitive. So at that point I would have to distinguish resolution of Y in cases of full, partial, and none. |
There has been discussion about Survival Overrides, whether it is possible to
Since destroy is defined with return, and return is governed by Do as much as Possible.
The text was updated successfully, but these errors were encountered: