fix(monsters): Change burrow speed for young-blue-dragon to 20 ft. (from 40 ft.) #632
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
As compared to 5E Monster Manual; also Ancient and Adult Blue Dragon burrow speed is 40ft and 30ft respectively
bagelbits
changed the title
bagelbits
approved these changes
Apr 29, 2024
markpol
pushed a commit
to markpol/5e-database
that referenced
this pull request
May 19, 2024
…rom 40 ft.) (5e-bits#632) Change burrow speed for young-blue-dragon to 20 ft. (from 40 ft.) As compared to 5E Monster Manual; also Ancient and Adult Blue Dragon burrow speed is 40ft and 30ft respectively
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.
As compared to 5E Monster Manual; also Ancient and Adult Blue Dragon burrow speed is 40ft and 30ft respectively
What does this do?
Simple change of JSON data in 5e-SRD-Monsters.json
How was it tested?
Using diff
Is there a Github issue this is resolving?
No
Did you update the docs in the API? Please link an associated PR if applicable.
N/A
Here's a fun image for your troubles