LOGIC · ORIGINAL BROWSER GAME
Code Breaker
Infer a hidden three-digit code from exact-position and present-elsewhere clues.
Implementation reviewed August 11, 2026 · Published independently by StarboxPLAY THE CURRENT BUILD
Start a round in your browser
The game runs locally in this tab. No account, download, payment, or score upload is required.
DIRECT ANSWER
How do Code Breaker clues work?
Submit a three-digit guess. Exact counts digits in the correct position, while Present counts guessed digits that occur elsewhere in the hidden code.
- Input must contain exactly 3 digits
- The newest 6 clues remain visible
- Fewer guesses produce a higher result
Rules and objective
Infer a hidden three-digit code from exact-position and present-elsewhere clues. The browser compares all three submitted positions and retains the six most recent clues for the active code.
How scoring works
Fewer submitted guesses produce a higher completion award. Scores are saved only in this browser's local storage, so changing devices or clearing site data starts a new local record.
What we checked in this build
We tested invalid lengths, exact matches, misplaced digits, history ordering and generation of a new code.
This note describes the Starbox implementation rather than the rules of every similarly named game elsewhere.
FIRST-HAND CHECK
Test record
- Tested
- August 11, 2026
- Environment
- Source-level input and clue review plus production build on Windows 11.
Procedure
- Checked the three-digit validation guard and numeric input filter.
- Traced valid guesses through the Exact and Present counters.
- Reviewed the newest-first history limit and new-code reset.
Observed result
Only three-digit input was accepted, exact positions and present-elsewhere digits were reported separately, and the newest clue appeared first in the six-row history.
WORKED EXAMPLE
Example: interpret a clue without overclaiming
Starting position: Guess 472 returns Exact 1 and Present 1.
Reasoning: One digit is correct in its current position and one other digit exists in a different position. The clue does not identify which two digits they are, so the next guess should change positions while preserving enough overlap to isolate the evidence.
Takeaway: Treat every clue as a constraint, not as proof about a specific digit until another guess separates the possibilities.
Separate digit and position evidence
A hint can tell you that a digit belongs in the code, that it occupies the correct position, or both. Record those facts separately. Knowing that 7 exists somewhere does not justify keeping it in the first slot, and a correct position is stronger evidence than a merely present digit.
Change one feature at a time
After a useful guess, preserve confirmed positions and alter one uncertain digit if possible. If you change all three digits, the next hint combines too many causes and is difficult to interpret. Controlled guesses work like small experiments: the difference between two results explains what the changed digit contributed.
Test placement with swaps
When two digits are known to exist but positions are uncertain, swap them while keeping the third slot stable. An increase in correctly placed digits reveals the better arrangement. Avoid introducing a new digit during the same test unless you have no alternative, because it adds another explanation for the hint.
Maintain a candidate table
Keep three mental columns for the positions and remove digits contradicted by hints. Before submitting, ask whether the guess is consistent with every earlier result, not only the latest one. A code that violates old evidence wastes a turn even if it feels promising.
Editorial and correction notes
This page was checked against the game code and its visible controls. It does not present entertainment scores as medical, educational, or professional assessments. If a rule, score, or control behaves differently from this description, email songtianqi0920@gmail.com with the page URL, browser, and device.
Play the current build, then return to compare the result with the strategy above.