fix(5e-SRD-Monsters.json): small inconsistencies #598
Merged
Conversation
This file contains 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
Fixes various small inconsistencies (probably introduced by character recognition).
breni-tiber
changed the title
|
The patch contains a single comma in the Lamia's entry for Intoxicating Touch. I've verified it can be parsed. |
bagelbits
approved these changes
Mar 15, 2024
|
🎉 This PR is included in version 3.3.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
markpol
pushed a commit
to markpol/5e-database
that referenced
this pull request
May 19, 2024
* Fix (5e-SRD-Monsters.json) Fixes various small inconsistencies (probably introduced by character recognition). * Update 5e-SRD-Monsters.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes various small inconsistencies (some probably introduced by character recognition).
What does this do?
Fixes various small inconsistencies.
How was it tested?
Manually.
Is there a Github issue this is resolving?
No.
Did you update the docs in the API? Please link an associated PR if applicable.
No.
Here's a fun image for your troubles