Feature set 173. - #88
Merged
Merged
Conversation
The Limit belongs to the player. Opponents are served without one. Jack: "It's hard enough getting through their attacks." The gauge fills on damage taken, which was built as the way back into a fight going badly — it survives a switch, so a battered sphere on the bench is worth keeping. Given to the opponent it inverts: the sphere winning a fight hands its opponent the means to end it, and a run going well is punished for going well. Stripped on the server rather than hidden in the client, so the payload is honest about what an opponent can do. It costs the vetting nothing, since TurnsToKill already ignores Limits on the grounds that a hunt should not be rated winnable on a resource that may never arrive. The mark keeps its Limit. Sealing it puts it in the party and a sphere you play has one; it is only the fighting copy that goes without. The client stops filling a gauge for anything that cannot spend it, or a "Limit ready" badge lights over a move the opponent no longer has. Verified against the live catalogue: party 3 of 3 armed, opponents 0 of 33, marks 11 of 11. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The Limit belongs to the player. Opponents are served without one.
Why it was backwards
The gauge fills on damage taken. It was built as the way back into a fight that's going badly — it survives a switch, so a battered sphere on the bench is worth keeping. Given to the opponent that inverts: the sphere winning a fight hands its opponent the means to end it, and a run going well is punished for going well.
How
Stripped on the server, not hidden in the client, so the payload is honest about what an opponent can do. It costs the vetting nothing —
TurnsToKillalready ignores Limits, on the grounds that a hunt shouldn't be rated winnable on a resource that may never arrive.The mark keeps its Limit. Sealing it puts it in your party, and a sphere you play has one; only the fighting copy goes without. That's why
Capturereferences the un-stripped sphere whileOpponentsgets the disarmed copies.The client stops filling a gauge for anything that can't spend it — otherwise a "Limit ready" badge lights over a move the opponent no longer has.
Verified against the live catalogue
544 tests pass.
🤖 Generated with Claude Code