Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As noted in #3 there were a few bad records I've identified so far in the Monster JSON
I dsecided to add a subtype field so that e,g, Wereboar which in SRD is listed as "Medium humanoid (human, shapechanger), neutral evil" is now...
`
I've also fixed a few small other issues
NOT in this PR but in test I've also converted hit_hpoints a-la #2 so Wereboar (at least here) looks like this...
"hitPoints": { "avg": 78, "diceCount": 12, "diceType": 8, "bonus": 24 },When I've done some more of the conversion I'll make the program that does this public. At the moment the export is starting to diverge from the initial JSON (but the prog will read either when done)