Level up and Start a character: another class's feats are shown disabled, with the reason (Q133 / L19) #1008

New issue

Closed

opened 2026-10-01 20:37:55 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-10-01 20:37:55 +00:00

Collaborator

The owner's answer to Q133 (L19), 2026-10-01: (b), as recommended. To be recorded as D261.

Today: the class feat step lists every class feat in the loaded content. A Fighter is offered a rogue's feat as if they could take it, because feats carry their class as a trait, not as a prerequisite. Start a character behaves the same way.

What changes: a class feat that belongs to another class is shown disabled with its reason ("A rogue feat."), the way a feat with an unmet prerequisite already is ("Needs trained in Acrobatics."). The character's own class's feats are unaffected. A GM can still type any feat by name (D250).

The rule belongs on the server too: a level-up or creation that names another class's feat from content is refused, the same way an unmet prerequisite is.

Tests, changelog fragment, catalogue row if a new state is drawn. Part of #737's follow-ups.

**The owner's answer to Q133 (L19), 2026-10-01: (b)**, as recommended. To be recorded as D261. **Today:** the class feat step lists every class feat in the loaded content. A Fighter is offered a rogue's feat as if they could take it, because feats carry their class as a trait, not as a prerequisite. Start a character behaves the same way. **What changes:** a class feat that belongs to another class is shown disabled with its reason ("A rogue feat."), the way a feat with an unmet prerequisite already is ("Needs trained in Acrobatics."). The character's own class's feats are unaffected. A GM can still type any feat by name (D250). The rule belongs on the server too: a level-up or creation that names another class's feat from content is refused, the same way an unmet prerequisite is. Tests, changelog fragment, catalogue row if a new state is drawn. Part of #737's follow-ups.

claude-bot referenced this issue

2026-10-01 20:48:26 +00:00

Record D254–D269, the owner's answers of 1 October (#737) #1012

claude-bot referenced this issue

2026-10-01 21:11:10 +00:00

Build lane 11: stat blocks and character sheets (WIKI-19) #737

rbrooks referenced this issue from a commit

2026-10-01 21:36:17 +00:00

Level up: another class's feat is shown disabled with why (#1008, D261)

rbrooks referenced this issue from a commit

2026-10-01 22:19:17 +00:00

Another class's feat reads "another class" in the list, not "not yet" (#1008)

rbrooks referenced this issue from a commit

2026-10-01 22:19:17 +00:00

The list's note for another class's feat is tested as it renders (#1008)

claude-bot referenced this issue from a pull request that will close it,

2026-10-01 22:39:07 +00:00

Level up shows another class's feat disabled, with why (#1008) #1015

claude-bot referenced this issue

2026-10-01 23:46:17 +00:00

In a milestone campaign the GM marks a level as waiting, and the player levels up (#1007) #1019

claude-bot referenced this issue from a commit

2026-10-02 00:40:11 +00:00

Merge PR #1019: in a milestone campaign the GM marks a level as waiting, and the player levels up (#1007); another class's feat is shown disabled (#1008)

claude-bot commented

2026-10-02 00:40:31 +00:00

Author

Collaborator

Done: on main 13f16533, through PR #1019 (which carried #1015's commits; head ac5e4ea8 is an ancestor of main; CI green on e3d80423).

At a class feat step in Level up, a content feat whose traits name classes but not the character's is shown disabled with the reason ("A rogue feat."), the list reads "another class" beside it, and applying a level with it is refused; a feat typed by name still passes (D250). The rule is the server's, in sheet_levelup.feat_why, worked out from the loaded content.

Start a character is unchanged, and the question to the owner was wrong on this point: creation has no class feat step (PF2e's offers only the ancestry feat through the plain content picker, which has no disabled-with-why state). 5e has none either. The owner has been told.

Recorded as D261. Not on dev until the next deploy.

**Done: on main `13f16533`**, through PR #1019 (which carried #1015's commits; head `ac5e4ea8` is an ancestor of main; CI green on `e3d80423`). At a class feat step in Level up, a content feat whose traits name classes but not the character's is shown disabled with the reason ("A rogue feat."), the list reads "another class" beside it, and applying a level with it is refused; a feat typed by name still passes (D250). The rule is the server's, in `sheet_levelup.feat_why`, worked out from the loaded content. **Start a character is unchanged**, and the question to the owner was wrong on this point: creation has no class feat step (PF2e's offers only the ancestry feat through the plain content picker, which has no disabled-with-why state). 5e has none either. The owner has been told. Recorded as D261. Not on dev until the next deploy.

claude-bot closed this issue

2026-10-02 00:40:41 +00:00