[#7269] Support Total Cover as an explicit attack outcome - #7270
Open
thatlonelybugbear wants to merge 2 commits into
Open
[#7269] Support Total Cover as an explicit attack outcome#7270thatlonelybugbear wants to merge 2 commits into
thatlonelybugbear wants to merge 2 commits into
Conversation
Contributor
|
Curious why the focus here is only on |
Contributor
Author
|
I was mainly waiting on some feedback on how to proceed in general and what kind of automation the system wants to support. I agree that there should be a more complete solution |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #7269
Adds explicit Total Cover handling for attack targets.
ignoreTotalCoverfor module / macro overrides.ignoreTotalCoveras a trait or item/activity Booleans