Repository navigation
Make scoring predictable and explain each game's rules - #9
Merged
Merged
Conversation
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
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.
New practice rounds and Daily Fives from October 16, 2026 use linear closeness with explicit game-specific allowances. Time and When? use contextual bounds; 3D view uses 90°, Perspective uses the inner-box diagonal, How long? reaches zero at a 50% miss, and Line memory scores equal-width stroke intersection over union. Size it up averages independent width/height closeness. Color retains wheel distance, with American spelling throughout the interface.
Rebuild How it works with a scoring visual, controls and examples for all eleven games, and an explanation of historical scoring. Historical questions, saved scores, trivia assignments, and shared challenge identifiers remain compatible; no trivia data changes.
Validation: all Node verification suites and 21 Python tests; mobile browser coverage for all eleven games, real touch and keyboard controls, both themes, resize persistence, scoring/reveal layouts, and accessible instructions. Compared 45 daily rounds through October 15 byte-for-byte with the shipped build and checked 72 legacy year-score cases. Published-data guard and build checks pass.