6.0.0 FVTT v10.284 Compatibility || Damage Console

[Jagusti]

Release Summary

This release confirms Foundry v10 compatibility, building on changes introduced in Release Candidate v0.9.5, and as defined in issue #156 .

Requires at least Foundry v10.284 and WFRP 6.1.2.

Feature Updates

In addition to v10 compatibility, this release:

• Adds the Damage Console, from which GMs can quickly set and apply damage to one or more actors without starting a combat, opposed or other test. See below for key features. [Feature Request] Deal Damage to Targeted Tokens #158
• Fixes an issue where a combatant could gain Advantage from an Opposed Test they won but did not initiate when Group Advantage is being used. Group advantage - Winning entry - Not applying to defense  #159
• Changes Group Test behaviour to clear or restore the custom skill field if a skill is chosen from the skill list dropdown. Customize Skill in Group Tests #160

Repository Management

Module management and repository changes have also been made:

• Version numbering is overhauled, essentially to keep in step with WFRP4e system versioning.
  • This is marked by a jump from v0.* to 6.*.
  • There is no v1-v5 of GM Toolkit.
• Templates are provided for bug reports, feature suggestions and pull requests.
• Discussions are enabled on the repository. I intend to use these to solicit input and feedback on new features, enhancements and potential bugs.

Damage Console

Issue: #158. Pull Request: #168.

• Access from the Launch Damage Console macro or the GM Toolbox.
• Target tokens before launching to change the pre-selected characters.
• Set damage as a roll formula or fixed amount.
• Optionally randomise damage and hit location for each target.
• Choose whether to ignore Armour Points and/or Toughness Bonus, and whether to apply a minimum of 1 damage.
• Check tooltips to find randomisation details.

What's Changed

• Add compatibility for Foundry VTT v10 and WFRP4e v6 Add compatibility for Foundry VTT v10 and WFRP4e v6 #162
• Add templates for issues and PRs Add issue templates #163 Add templates for issues and PRs #164 Add Discord contact to templates; Move PR template #171
• Clear or restore default Group Test skill Customize Skill in Group Tests #160 Clear or restore default Group Test skill #160 #166
• Prevent advantage gain if not initiating challenge Group advantage - Winning entry - Not applying to defense  #159 Prevent advantage gain if not initiating challenge #159 #167
• Add Damage Console [Feature Request] Deal Damage to Targeted Tokens #158 Add Damage Console #168
• Add release workflow Add release workflow #169
• 6.0.0 macro versioning 6.0.0 Release #173

Full Changelog: v0.9.4.4...6.0.0

---

This discussion was created from the release 6.0.0 FVTT v10.284 Compatibility || Damage Console.

[nyoung]

I really like the damage console, but its picking up every Actor that is assigned Owner permissions, which is including horses, loot, etc, which gives me a fairly lenghty list to go through to find the characters impacted. Is there a way to limit it to the characters in the current scene or to characters actually assigned to the player?

[Jagusti]

Thanks for the appreciation :)
By default the damage console builds the player's character list from the entourage group type. At the moment this is baked in and can't be customised without changing the source code.

If you want to change it to a different group type, you can adjust this line in /apps/damage.js::

      playerGroup: game.gmtoolkit.utility.getGroup("entourage"),

Change entourage to:

• pcTokens to limit to those PCs represented by tokens in the scene
• party for just the assigned PCs (regardless of whether they have a token in the scene)
• company for player-owned, non-vehicle actors (whether in the scene or not)

Let me know how that goes for you. Also, it would be great to understand the sort of numbers you're talking about, and how it renders. If you can share some more info and a screenshot I'd apprecaite that - it will help with understanding real use cases and inform the sort of options I might be able to offer in the future.

One likely future option will be to choose the default Damage group, similar to how you can choose party or company for Group Tests.