Dragonborn Breath Weapon
See original GitHub issueUnder races/dragonborn there’s the attribute trait options which stores an array of all the dragon ancestry options however it only stores the name of the ancestry type. it doesn’t hold the damage type nor the saving throw, now the distance which I believe is relevant data. Here’s my suggestion on formatting (sorry idk how to format json on here):
{
"index": "black",
"name": "Black",
"damage_type": "Acid",
"saving": "dex",
"range": "5 by 30 ft. line"
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Dragonborn | D&D 5th Edition on Roll20 Compendium
Breath Weapon : You can use your Action to exhale destructive energy. Your Draconic ancestry determines the size, shape, and damage type of...
Read more >The Dragonborn Race for Dungeons & Dragons (D&D) Fifth ...
Breath Weapon. You can use your action to exhale destructive energy. Your draconic ancestry determines the size, shape, and damage type of the...
Read more >Dragonborn - DND 5th Edition - Wikidot
Breath Weapon. You can use your action to exhale destructive energy. It deals damage in an area according to your ancestry. When you...
Read more >Dragonborn – 5th Edition SRD
Breath Weapon : You can use your action to exhale destructive energy. Your draconic ancestry determines the size, shape, and damage type of...
Read more >D&D 5e: Dragonborn Breath Weapon - YouTube
This video explains and demonstrates the dragonborn breath weapon for dungeons & dragons 5e. Breath weapons work differently depending ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah I think we’re mostly on the same page but explaining things is hard. I’ll put together an example a little later of what I’m thinking.
I like @GeraldTo’s idea of simply utilizing the existing trait_options, which right now are essentially redundant. After all picking an ancestry sets both your resistance type and breath details so in this regard it would make sense to go this way. On the other hand splitting the data as @bagelbits suggests might have its benefits in the long run but it might take a bit more planning.