Skip to content

2024 Collections: Schema guidance for Classes, Levels, and Spells contributions? #1057

@t11z

Description

@t11z

I'm building an open source, self-hosted RPG engine targeting SRD 5.2.1, I use 5e-database as my SRD data source (currently pinned to v4.6.3) and am very happy with the quality of what's there.

My game design is built around the 2024 SRD mechanics, the existing 2024-* data (Backgrounds with ability scores and Origin Feats, Species, Subclasses, Feats, etc.) is exactly what I need and works great.

I've noticed that several collections don't have 2024 equivalents yet:

  • Classes (referenced via nyi field in Subclass docs)
  • Levels (spell slots, class features per level, proficiency bonus)
  • Spells
  • Monsters
  • Features (class features as standalone collection)

I'd like to contribute this data from the SRD 5.2.1 PDF (CC-BY-4.0) and submit it as PRs.

Questions

  1. Is there ongoing work on these collections? I don't want to duplicate effort or step on anyone's toes. If there are branches or draft schemas I should build on, I'd love to know.

  2. Schema guidance for Classes and Levels? The nyi field in Subclass class references suggests you've thought about how Classes will look. Is there a target schema, or should I propose one based on the existing 2014 structure adapted for 2024 mechanics (unified level-3 subclass selection, etc.)?

  3. Spells schema? The 2024 SRD changes some spell properties compared to 2014 (e.g., spell lists are now per-class-group rather than per-class). Should I follow the 2014 spell schema as closely as possible, or is there a 2024-specific schema in mind?

  4. Preferred contribution format? I'd submit JSON data files + Zod schemas + tests, matching the existing pattern in src/2024/. Just want to confirm that's the right approach.

My plan

I've forked the repo to unblock my own development, but my goal is upstream contribution — not permanent divergence. I'd rather align on schemas before producing hundreds of documents than submit PRs that don't fit your vision for the 2024 dataset.

Happy to coordinate however works best for you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions