Implemented adversary and environment statblocks #10
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
Also fixed missing GM questions in the environmnts json
|
Hi @Batres3, just to let you know that your multi-stage tier 4 adversaries (fallen warlord, volcanic dragon) have a colon in their filename - which isn't valid for filenames on windows. Thank you otherwise for porting these along with the environment blocks |
Author
|
Very true, I forgot since I don't really use windows. I'll switch to a dash soon. Thanks for the heads up |
HandsomeStrife
added a commit
to HandsomeStrife/daggerheart-srd
that referenced
this pull request
Sep 9, 2025
…statblocks from seansbox/daggerheart-srd
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.
I am aware that pull request #7 is very similar to this one, however, I have multiple reasons to believe this is a better option, first is the fact that the yaml content in the
statblockswithin the markdown files is one-to-one with the json file.The second obvious reason is that this implements both adversaries and environments.
Finally, the content within the statblocks is not only for use with the Fantasy Statblocks plugin, but also (optionally) with my own Daggerheart Combat Tracker
So overall I believe this is the better option.