In a number connecting puzzle that verifies every segment, the eight points are anchored and the only valid route from 1 to 8 collects exactly 1,000 points when each new line clears a collision check against the path already drawn. That sentence defines the contract behind Connect the Numbers: instead of accepting any chain that happens to visit the numbers in order, the puzzle inspects each proposed segment against every nonadjacent line already on the canvas, treats endpoint contacts and collinear overlap as collisions, and rejects an out-of-sequence pick before any score change happens. Point 1 is connected automatically on load, and your task is to send the line onward to 2, then 3, all the way to 8, watching the ledger after each accepted step. With seven segments to draw and a clear geometry audit on every press, you are not just connecting dots; you are documenting a path under audit. That audit, paired with the fixed opening layout, is what makes the score reproducible, and reproducibility is what lets the seven-segment run finish at exactly 1,000 every time.

What a Verified Number Connecting Puzzle Tests For
Most dot-to-dot games treat the path as a list of pairs in numeric order: 1-2, 2-3, 3-4, and so on. Connect the Numbers tightens that contract by auditing every proposed segment against the segments already drawn. A proposed line that crosses an earlier nonadjacent segment, that touches an earlier segment at anything other than the shared endpoint, or that overlaps a prior segment collinearly is rejected before the score changes.
That check transforms a casual dot-to-dot into a small geometry puzzle. You are not just ordering numbers; you are choosing a route that the validator will accept, and the only authoritative route on the fixed opening layout is a known seven-segment path. When the canvas keeps that fixed geometry, you can reproduce the run exactly: the same starting anchor, the same seven segments, the same final score of 1,000.
Two design choices make the contract auditable. First, point 1 is anchored automatically when the board opens, so the user never picks the first endpoint. Second, every accepted segment becomes visible on the canvas and is also recorded in an on-screen ledger, which means the audit trail is double-checked: you see the line, and you see the line listed with its endpoints.
Playing Connect the Numbers on the Fixed Layout
- Open the board. Point 1 appears anchored on the canvas; the score reads 0 and the mistakes counter reads 0. The next required number, 2, is shown in the interface.
- Select point 2 with a mouse click, a tap, or the number key 2. The validator confirms the segment 1 to 2 is clear, the canvas draws the line, and your score advances by 125.
- Select 3, then 4, then 5, then 6, then 7. Each accepted segment awards 125 points and updates the on-screen ledger with the chosen endpoints.
- Select 8 last. This seventh segment adds 250 points, moving the score from 750 to exactly 1,000. The board enters its terminal completion state and locks further input.
- Use New layout before you start if you want a different arrangement. Picking a new layout only changes geometry, never the rules or the score target.
If you ever propose a crossing or an out-of-order number, the board rejects the move, the score does not advance, and the same invalid attempt cannot be charged twice. A second distinct invalid attempt closes the run and freezes the terminal state.
How the Crossing Check Rejects a Bad Move
The geometry check combines three signals so the validator can tell a real collision from a normal joint. Orientation signs tell whether two segments wind around each other at a proper crossing or simply miss each other in space. On-segment bounds restrict any reported intersection to the interior of both candidates. Collinear overlap is detected separately so that a long shared stretch is not mistaken for an honest crossing.
The endpoint of the immediately previous segment is shared with the proposed new segment by construction, since 2-3 must start where 1-2 ended, and that allowed joint is excluded from the audit. Any other endpoint contact, including a 1-3 link if 1 and 3 happen to touch an earlier segment, is treated as a collision. The same rule covers a propose-and-replace attempt: pressing an already-connected point is treated as a no-op rather than as a scoring event.
Because the check runs against nonadjacent segments, ordering still matters. You cannot skip ahead to 7 and then back-fill 4, because the validator will reject any out-of-sequence pick on signature alone. A candidate that would otherwise be valid but crosses an earlier nonadjacent segment loses on geometry, which is the central reason an inspection-driven puzzle behaves differently from a free dot-to-dot.
Score Breakdown for the Seven-Segment Run
| Segment | Connection | Points Awarded | Running Total |
|---|---|---|---|
| 1 | 1 to 2 | 125 | 125 |
| 2 | 2 to 3 | 125 | 250 |
| 3 | 3 to 4 | 125 | 375 |
| 4 | 4 to 5 | 125 | 500 |
| 5 | 5 to 6 | 125 | 625 |
| 6 | 6 to 7 | 125 | 750 |
| 7 | 7 to 8 | 250 | 1,000 |
The seventh segment is the completion bonus. Six 125-point steps total 750, then add the final 250 and the arithmetic lands on 1,000. The total is exact on the opened layout because each award is fixed and the only accepted run is the full seven-segment path. Readers who want an order-focused walkthrough for the same final score can compare with the seven-segment 1,000-point route guide, which treats the same run as a route plan rather than an audit.
Controls: Keyboard, Pointer, and Touch
You can solve the board with mouse, finger, or keys because the interface exposes the same eight numbered point controls regardless of how you intend to act. Pointer users click a numbered button. Touch users tap the same target on a phone or tablet. Keyboard players tab to a point and confirm with Enter or Space.
The keyboard shortcut layer adds a disclosed numeric path: pressing 2 selects point 2, pressing 3 selects point 3, and the pattern continues through pressing 8 for the final point. The keys match the numbers on the board so the route can be played eyes-down once you memorize it. The numbered buttons remain visible for accessibility during the run.
A Boss Key in the standard game shell can hide the canvas if you need to step away, and the keyboard layer is documented in the interface rather than hidden. All processing and canvas drawing stay in the browser, with no account, no remote puzzle feed, and no analytics-driven opponent influencing your run.
Reproducible Layouts and Mistake Handling
The opening layout is fixed so its geometry and winning route can be reproduced exactly. If you want a different board, the New layout control picks another in-bounds arrangement through a deterministic seeded generator. The chosen seed is passed into a pure layout function, so the same seed always produces the same unique in-bounds coordinates and the same completable ordered route. Randomness never runs silently during render, which keeps every layout testable.
Mistakes are tracked rather than silently swallowed. The signature for a mistake includes the active layout, the expected next number, the chosen number, and the collision result. Identical invalid attempts are deduplicated and cannot consume the second chance. A second distinct invalid attempt closes the run and freezes the board. Selecting an already-connected point, an unknown point, or any other invalid internal action is an atomic no-op, which keeps the audit ledger clean for review.
Restart restores point 1, the initial fixed layout, a score of 0, and a mistakes count of 0. Completion and a two-error deadlock both freeze path actions and layout replacement, preserving the audited terminal result. Because every route and candidate set is authored for this product, the puzzle makes no claim about real-world navigation, drafting, or cognitive measurement; the 1,000-point score describes completion of the authored board only.
For a deeper look, see Count the Cubes Game: Include Hidden Blocks for 1,000.