This repository was archived by the owner on Sep 9, 2026. It is now read-only.
Add shipcombat interference tactics - #349
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The existing space-combat engine omitted the p.201 clustering and interference options. These helpers expose the exact tactical choices the rule defines while leaving cluster membership and defense expenditure with encounter state.
Impact
Existing combat resolution is unchanged. Callers can now determine whether a nearby craft may protect or substitute for a target without inventing an additional roll or formation limit that the source does not provide.
The R=7 limit uses the world-range ladder (50 km), not Space Range S=7.
Validation
task checkCloses #194