Mikkel Paulson

This is doable with the existing implementation, if you take advantage of constant scopes: ``` class MyEnum extends Enum { protected const FOO = 'FOO'; } MyEnum::FOO(); // works MyEnum::FOO;...

> 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...

Okay, so if I understand correctly, it sounds like we're converging on: ```javascript [ { "name": "The Order of Combat", "index": "the-order-of-combat", "desc": "...", // optional, body text only (no...

> As for human-readability, we've talked a lot in the past about choosing a Markdown standard and sticking to it, applying it across the whole database. This could be a...

My preference would be to converge behind a single Markdown string for all fields including `desc` project-wide, for all that the readability at a JSON level suffers as a result....

Okay, I'll add this to my to-do list, unless someone else is feeling bored.

I'll get there at some point if you (or someone else) doesn't beat me to it. I'm not working on integrating SRD data sets right now, so further data cleanups...

 First attempted set of character portraits. Looks good, ship it!

@alfonsomartinezs Sure thing! If you want a guide, you can find the sole existing generator at [core/src/world/place/building/business/inn.rs](https://github.com/initiative-sh/initiative.sh/blob/main/core/src/world/place/building/business/inn.rs), although it's pretty rudimentary (not much more sophisticated than the d20 table in...

Spitballing re: #298: Even with two generators roughed in, there's starting to be some overlap in vocabulary (right now, animals and I guess technically numbers). I'd like to start bubbling...