Normalize invalid -1 spell limit to 0 in generated monsters - #359
Merged
Conversation
The AI generator occasionally returns innate_spells with limit -1, which isn't handled by the app's "0 = at will" display convention. Co-Authored-By: Claude Sonnet 5 <[email protected]>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
innate_spellsentries withlimit: -1(often for cantrip-like spells).limit === 0as "at will" but doesn't handle-1, so these spells rendered with a bogus limit.GenerateMonster.vue, alongside the existing post-generation sanitization, to coercelimit === -1to0.Test plan
limit: -1and confirm it renders as "at will" (limit 0) after generation.limitfield) are unaffected.🤖 Generated with Claude Code