FoundryVTT: Wild Shape Feature Handling Proposal
Hey guys! Let's dive into a crucial aspect of implementing Wild Shape in FoundryVTT, particularly how it interacts with species and background features. The current system offers a binary choice: keep all features or none. However, this doesn't align with the nuances of the rules, especially when comparing the 2014 and 2024 versions of D&D. So, let's break it down and propose a more flexible solution.
The Wild Shape Dilemma
Currently, within FoundryVTT, managing character features during transformations like Wild Shape presents a bit of a challenge. The existing options are pretty straightforward: either you retain all features or you retain none. This all-or-nothing approach, while simple, doesn't fully capture the rules as written, especially when considering the different iterations of Wild Shape across various D&D editions and supplemental materials. The core issue revolves around how features gained from different sources—class, race (or species), background, and feats—should be treated during a transformation.
For example, a character might have class-specific abilities that are essential to their identity and build, racial traits that define their inherent capabilities, background features that reflect their history and training, and feats that grant them unique advantages. Each of these feature types contributes to the overall character, and determining which should persist through a Wild Shape transformation requires a more granular approach than simply keeping everything or nothing. This becomes particularly relevant when the rules themselves vary on what should be retained, leading to inconsistencies if the implementation isn't adaptable.
The need for a more refined system is driven by the desire for accuracy and flexibility. Players and game masters alike want the ability to tailor the transformation process to match the specific rules they're using and the unique aspects of their characters. By allowing for selective retention of features based on their source, the game can better reflect the intended balance and flavor of Wild Shape, ensuring a more satisfying and authentic gameplay experience. This is why a detailed proposal to split the feature retention options becomes essential, paving the way for a more customizable and rules-compliant implementation within FoundryVTT.
Rules as Written: 2014 vs. 2024
2014 Wild Shape
The 2014 Player’s Handbook states:
You retain the benefit of any features from your class, race, or other source and can use them if the new form is physically capable of doing so.
This is pretty clear-cut. Under these rules, a Druid retains all features, provided their new form can physically accommodate them. The current transform activity in FoundryVTT handles this well when set to retain all features. However, the simplicity ends here when we consider the updated rules.
2024 Wild Shape
The updated ruleset (One D&D playtest material) changes things significantly:
Your game statistics are replaced by the Beast's stat block, but you retain your creature type; Hit Points; Hit Point Dice; Intelligence, Wisdom, and Charisma scores; class features; languages; and feats.
Here, the scope is much narrower. Druids retain only Class Features and Feats. This excludes species features but includes any Feats a character gains from their Background or Species. This distinction is crucial and highlights the need for a more granular control over feature retention in FoundryVTT.
Proposal: Granular Feature Control
To address the discrepancies between the 2014 and 2024 Wild Shape rules, I propose splitting the feature retention option into three distinct categories:
- Class Features: Only features granted by a character's class.
- Feats: Only feats gained through any source.
- All Features: Retain all features from class, species, background, etc. (mimicking the 2014 rules).
The Wildshape Preset should then respect the rules version selected, keeping Class Features and Feats in 2024, and All Features in 2014.
This approach allows for accurate implementation of both rulesets and provides flexibility for custom rules or homebrew content.
Defining Class Features
The most challenging aspect of this proposal is determining what qualifies as a "Class Feature." I suggest aligning this with the categories already present on the character sheet. Only features explicitly granted by a class should be considered "Class Features" for Wild Shape purposes.
For example, consider a character with the Alert feat from the Criminal background and the Healing Hands feature from being an Aasimar. When wildshaped, this character should retain the Alert feat (as it's a feat) but should not retain the Aasimar's Healing Hands, Celestial Revelation, and Light Bearer features because these are species-related, not class-related.
Example Scenario
Let's say we have a Druid character who is also an Aasimar with a Criminal background. This character has the following relevant features:
- Class Features: Wild Shape, spellcasting, etc.
- Species Features (Aasimar): Healing Hands, Celestial Revelation, Light Bearer
- Background Feature (Criminal): Alertness (grants the Alert feat)
Under the 2014 rules, when this character Wild Shapes, they would retain all of these features, assuming their new form can physically use them.
However, under the 2024 rules, they would only retain their class features (Wild Shape, spellcasting) and the Alert feat (granted by their background). The Aasimar species features would be suppressed during the transformation.
Implementation Considerations for FoundryVTT
Implementing this in FoundryVTT will require some adjustments to the character sheet and transformation mechanics. Here’s a breakdown of the key areas to consider:
Character Sheet Categorization
Ensuring that features are correctly categorized on the character sheet is the first step. There should be clear distinctions between class features, species features, background features, and feats. This might involve adding custom categories or utilizing existing ones more effectively.
Transformation Logic
The transformation activity needs to be updated to recognize these categories. When a character Wild Shapes, the system should check the selected rules version (2014 or 2024) and apply the appropriate feature retention rules. This means:
- 2014 Rules: Retain all features.
- 2024 Rules: Retain only class features and feats.
This logic could be implemented as a series of conditional checks that determine which features are suppressed or retained during the transformation.
User Interface Enhancements
To make this system user-friendly, consider adding options to the transformation dialog that allow users to specify which features should be retained. This could be as simple as a set of checkboxes for “Class Features,” “Feats,” and “All Features.” Additionally, providing clear visual cues on the character sheet to indicate which features are being retained during a transformation can help prevent confusion.
Module Compatibility
It’s also important to consider compatibility with other FoundryVTT modules. Ensure that the changes made to the transformation mechanics don’t conflict with other popular modules that modify character sheets or handle transformations. Thorough testing and collaboration with other module developers can help ensure a smooth and seamless experience for users.
Benefits of the Proposed System
Implementing this granular feature control offers several benefits:
- Rules Accuracy: Accurately reflects both the 2014 and 2024 Wild Shape rules.
- Flexibility: Allows for custom rules or homebrew content.
- Clarity: Provides clear distinctions between feature types.
- Improved Gameplay: Enhances the Wild Shape experience by ensuring features are handled correctly.
Conclusion
By splitting the feature retention option into Class Features, Feats, and All Features, we can create a more accurate and flexible Wild Shape implementation in FoundryVTT. This aligns with the rules as written and provides a better gameplay experience for Druids and players who utilize transformation mechanics. Let's make it happen!