Skip to content

[#1581] fix: Barbarian Rages scale value increases to 6 at level 17, not 16#7010

Merged
Fyorl merged 1 commit into
foundryvtt:6.0.xfrom
vfez1:fix/barbarian-rage-uses-level
Jun 2, 2026
Merged

[#1581] fix: Barbarian Rages scale value increases to 6 at level 17, not 16#7010
Fyorl merged 1 commit into
foundryvtt:6.0.xfrom
vfez1:fix/barbarian-rage-uses-level

Conversation

@vfez1
Copy link
Copy Markdown
Contributor

@vfez1 vfez1 commented May 20, 2026

Description: Corrects the 2024 Barbarian class advancement table where the Rages ScaleValue incorrectly granted 6 uses at level 16. Per the 2024 PHB, this upgrade should occur at level 17.

D&D Beyond reference: https://www.dndbeyond.com/classes/2190875-barbarian

Corrects the 2024 Barbarian class advancement table where the Rages
ScaleValue incorrectly granted 6 uses at level 16. Per the 2024 PHB,
this upgrade should occur at level 17.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vfez1 vfez1 force-pushed the fix/barbarian-rage-uses-level branch from 10d6aa0 to 4f375db Compare May 20, 2026 12:33
@vfez1 vfez1 changed the title fix: Barbarian Rages scale value increases to 6 at level 17, not 16 [#1581] fix: Barbarian Rages scale value increases to 6 at level 17, not 16 May 20, 2026
@Fyorl Fyorl added compendium content: 2024 bug Functionality which is not working as intended labels May 21, 2026
@Fyorl Fyorl added this to the D&D5E 6.0.0 milestone Jun 2, 2026
@Fyorl Fyorl changed the base branch from 5.3.x to 6.0.x June 2, 2026 17:18
@Fyorl
Copy link
Copy Markdown
Contributor

Fyorl commented Jun 2, 2026

Note that changes to the PHB are made separately to the SRD 5.2 included in the game system, so I have removed the 'closes' from the description.

@Fyorl Fyorl merged commit c5da12e into foundryvtt:6.0.x Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Functionality which is not working as intended compendium content: 2024

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants