Skip to content

Fix srd-2024 Fighter and Monk saving_throws to match their Core Traits tables#962

Closed
half-ogre wants to merge 1 commit into
open5e:stagingfrom
half-ogre:fix/srd-2024-fighter-monk-saving-throws
Closed

Fix srd-2024 Fighter and Monk saving_throws to match their Core Traits tables#962
half-ogre wants to merge 1 commit into
open5e:stagingfrom
half-ogre:fix/srd-2024-fighter-monk-saving-throws

Conversation

@half-ogre

Copy link
Copy Markdown

The structured saving_throws fields for two srd-2024 classes contradict the classes' own core-traits feature tables (and the SRD 5.2 Core Traits tables in the CC document):

Class saving_throws field Core Traits table
Fighter ["dex", "str"] "Strength and Constitution"
Monk ["dex", "wis"] "Strength and Dexterity"

This PR corrects both fields (["con", "str"] and ["dex", "str"], keeping the existing array ordering style). I swept all twelve srd-2024 classes against their own core-traits prose — the other ten fields already match.

Found while using the srd-2024 document as the verification source for a downstream 5e engine — thanks for maintaining this dataset; the verbatim rules text has been flawless in our audits.

…s tables

The structured saving_throws fields for the 2024 Fighter and Monk
contradict the classes' own core-traits feature tables (and the SRD 5.2
Core Traits tables):

- Fighter: [dex, str] -> [con, str] ("Saving Throw Proficiencies:
  Strength and Constitution")
- Monk: [dex, wis] -> [dex, str] ("Saving Throw Proficiencies:
  Strength and Dexterity")

The other ten srd-2024 classes' fields already match their prose.
@half-ogre

Copy link
Copy Markdown
Author

Sorry for the noise here, I was exploring your data with Claude and it over-eagerly opened a PR before I was ready.

@half-ogre half-ogre closed this Jul 5, 2026
@half-ogre half-ogre deleted the fix/srd-2024-fighter-monk-saving-throws branch July 5, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant