Let a symbol repeat when it owns an internal feature - #43
Merged
Conversation
The deck builder made every card's symbol unique, which left one deck unbuildable: three fried eggs telling each other apart by yolk count. The yolks feature only unlocks once every card is an egg, and the uniqueness rule made that unreachable. A shape that owns a `requiresShapeSupport` feature now stands in for the symbol feature, so it can be worn by more than one card. Picking it a second time collapses the deck onto that one symbol — the symbol stops varying and its internal feature switches on with a value per card — which also keeps the generated deck from holding cards that render identically. Shapes owning no such feature are still one to a deck. The card count follows from the same data: a deck can hold no more cards than the smallest option pool it varies, so three yolk counts cap an egg deck at three cards. That also closes a latent hole where adding a card past a feature's option count wrote `undefined` into deck metadata. None of this names the fried egg — capacity, unlocking and the card cap all read the shape registry and the feature table, so the next shape with its own feature gets the same treatment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EA4U1xNbvJ3BwVKft8ECjh
✅ Deploy Preview for imaginative-dieffenbachia-3400e7 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
2 participants
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 deck builder made every card's symbol unique, which left one deck
unbuildable: three fried eggs telling each other apart by yolk count. The
yolks feature only unlocks once every card is an egg, and the uniqueness
rule made that unreachable.
A shape that owns a
requiresShapeSupportfeature now stands in for thesymbol feature, so it can be worn by more than one card. Picking it a
second time collapses the deck onto that one symbol — the symbol stops
varying and its internal feature switches on with a value per card —
which also keeps the generated deck from holding cards that render
identically. Shapes owning no such feature are still one to a deck.
The card count follows from the same data: a deck can hold no more cards
than the smallest option pool it varies, so three yolk counts cap an egg
deck at three cards. That also closes a latent hole where adding a card
past a feature's option count wrote
undefinedinto deck metadata.None of this names the fried egg — capacity, unlocking and the card cap
all read the shape registry and the feature table, so the next shape with
its own feature gets the same treatment.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01EA4U1xNbvJ3BwVKft8ECjh