Skip to content
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

Closed
turmoilbyrd opened this issue Dec 10, 2024 · 6 comments
Closed

[Arcs] Survival Override and "do as much as possible" #94

turmoilbyrd opened this issue Dec 10, 2024 · 6 comments
Labels
arcs Issue for Arcs faq-ready Ready to be entered as library FAQ

Comments

@turmoilbyrd
Copy link
Contributor

turmoilbyrd commented Dec 10, 2024

There has been discussion about Survival Overrides, whether it is possible to

  1. destroy 1 Loyal ship to destroy 0 rival ship. Or
  2. (!) destroy 0 Loyal ship to destroy 1 rival ship

Since destroy is defined with return, and return is governed by Do as much as Possible.

@turmoilbyrd
Copy link
Contributor Author

turmoilbyrd commented Dec 10, 2024

My opinion is that both should be No

Reasoning:

Martyr (Move): Destroy... to destroy...

Is a shorthand for

When you spend a pip or a resource to move, you may instead (destroy... to destroy...)

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

"To" is a load-bearing word as the community has understood up to this point. If an action initiates with an "X to Y" structure you must be able to do Y to initiate the action and perform X

So both actions must be possible (and no DAMAP)

@jdyearsley
Copy link
Contributor

jdyearsley commented Dec 19, 2024

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?

@jdyearsley jdyearsley added the wontfix This will not be worked on label Dec 19, 2024
@turmoilbyrd
Copy link
Contributor Author

turmoilbyrd commented Dec 19, 2024

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)

@jdyearsley
Copy link
Contributor

jdyearsley commented Dec 19, 2024

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.

@jdyearsley jdyearsley added faq-ready Ready to be entered as library FAQ and removed wontfix This will not be worked on labels Dec 19, 2024
@turmoilbyrd
Copy link
Contributor Author

turmoilbyrd commented Dec 19, 2024

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

@jdyearsley
Copy link
Contributor

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.

@jdyearsley jdyearsley added the arcs Issue for Arcs label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arcs Issue for Arcs faq-ready Ready to be entered as library FAQ
Projects
None yet
Development

No branches or pull requests

2 participants