Expanded ClassFeature "feature_type" options
#812
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
augustjohnson
approved these changes
Oct 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR expands the
ClassFeaturemodel so that the"feature_type"now includes the option"CLASS_FEATURE_OPTION_LIST". This is to facilitate easier seperationg of lists of class options that typically go after the features per level list (Warlock Eldritch Invocations, Sorcerer Metamagic options, etc.)The V2 was also updated so that the SRD-2014/2024 Invocation list and the SRD 2024 Sorcerer Metamagic list have their
"feature_type"field set to this new value.Related Issue
Closes #811
How was this tested
pytest(all tests passing)