Skip to content

[#7269] Support Total Cover as an explicit attack outcome - #7270

Open
thatlonelybugbear wants to merge 2 commits into
foundryvtt:6.0.xfrom
thatlonelybugbear:feature/explicit-total-cover
Open

[#7269] Support Total Cover as an explicit attack outcome#7270
thatlonelybugbear wants to merge 2 commits into
foundryvtt:6.0.xfrom
thatlonelybugbear:feature/explicit-total-cover

Conversation

@thatlonelybugbear

@thatlonelybugbear thatlonelybugbear commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Closes #7269

Adds explicit Total Cover handling for attack targets.

  • Derived configurable cover levels from active cover statuses.
  • Preserves a target’s calculated AC while identifying Total Cover separately.
  • Treats Total Cover as an automatic miss, including for expanded critical-success ranges.
  • Adds ignoreTotalCover for module / macro overrides.
  • Expose ignoreTotalCover as a trait or item/activity Booleans
image
Hooks.on("dnd5e.preRollAttack", (config) => {
    config.ignoreTotalCover = true;
});
  
//or
await activity.rollAttack({ ignoreTotalCover: true });
image

@Fyorl Fyorl added bug Functionality which is not working as intended system: dice Dice rolling functionality strategic Requires sign-off from a core Foundry VTT developer before merge. labels Jul 21, 2026
@Kapuzenjoe

Kapuzenjoe commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Curious why the focus here is only on ignoreTotalCover rather than also covering Half and Three-Quarters Cover? Even though the system doesn't full automate cover in general yet, this might be a good spot to lay some groundwork for a model that could later be extended (e.g. spells like Sacred Flame ignore Half/Three-Quarters Cover but not Total Cover), so it might be worth considering a design where a single boolean isn't the only way to represent that distinction down the line.

#6369

@thatlonelybugbear

Copy link
Copy Markdown
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Functionality which is not working as intended strategic Requires sign-off from a core Foundry VTT developer before merge. system: dice Dice rolling functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Support Total Cover as an explicit attack outcome

3 participants