Chris Ward

@djurnamn Right. So. Here's my alternative suggestion: I've been thinking about the multi-language support for the API a little bit more. And I think the design of one set of...

You can find the original post in Discord [here.](https://discord.com/channels/656547667601653787/664902912014680068/931827044550078464) And if you haven't joined the Discord server yet. [Here's the invite.](https://discord.com/invite/TQuYTv7)

Excellent! Yeah might thoughts are you would basically build two scripts. One is a throwaway script that just coerces the data into this new shape. The second is a helper/tool...

@djurnamn Sorry for taking so long to respond. However, we now have semantic versioning for the docker images that get built for the DB, so I feel way more comfortable...

I see your 100% reasonable suggestion and raise you Erinyes: ``` "damage_resistances": [ "cold", "bludgeoning, piercing, and slashing from nonmagical weapons that aren't silvered" ], ``` There's a bunch of...

> Perhaps other field(s) could be useful for information about the conditions necessary for the resistance/vulnerabilities? We might be able to take a similar approach with what I suggested for...

> Really, damage types are nothing but an enumeration type since in DND5e the individual damage type themselves don't actually have a any game rules associated with them. Though they...

I think that looks good if you want to go forward with the rest.

I mean this would lead towards more standardized Schemas, which would also make life easier to document them in the API as well. (I could definitely use help with documenting...

I assume that `subsections` is a more useful field since I can see it more often looking at a rule and wanting know it's subsections, then looking at a rule...