Jewel Match is a free match-three browser puzzle that needs no download, no sign-up, and no installation. The level runs on a fixed 4×4 board holding exactly 16 gems — four rubies, four sapphires, four emeralds, and four topazes — with no pre-existing match line. You clear 12 gems to score exactly 1,000 points and the entire game runs locally in the browser tab, so nothing is uploaded. Every legal swap follows one rule: pick one gem, then pick a second gem that shares an edge with it, and the board only accepts the exchange if it immediately creates a horizontal or vertical line of at least three identical gems. Diamonds, time pressure, paid boosters, and cascading random levels are deliberately not part of this version. This guide walks through the two-click swap rule, the cascade refill loop, the keyboard and touch controls, and the unique three-swap minimum route that an independent breadth-first oracle confirms is the only way to finish the level.
The Match-Three Genre and This Specific Level
The match-three genre asks one question: can you arrange three identical pieces in a straight line by swapping two of them? Jewel Match keeps that core but compresses it into a single deterministic level instead of an endless random score chase. The board is exactly 4 columns wide and 4 rows tall, with 16 cells total. Each cell holds one gem drawn from a fixed set of four types: Ruby (R), Sapphire (S), Emerald (E), and Topaz (T). At the start, every type appears four times, so the opening board has exactly four rubies, four sapphires, four emeralds, and four topazes, and no row or column already contains a line of three or more. That last fact is what makes the puzzle solvable by swap rather than by click-to-collect.
If you have played match-three games before, you may expect random refill, animated cascades, and special pieces. This level is none of those. There is exactly one refill queue, exactly one refill order, and exactly one route that clears the 12-gem target in the minimum number of swaps. The PySolFC maintained documentation describes adjacent match-forming exchanges, clear, gravity, refill, and repeated cascades as the canonical match-three rules (PySolFC match three rules), and PuzzleBento independently confirms neighboring selection, horizontal or vertical 3-plus lines, rejected swaps, falling columns, new pieces, and chain reactions (PuzzleBento match pop rules). Jewel Match uses those same rules in their strictest form so the cascade outcome is fully predictable from the swap that triggered it.
The Two-Click Swap Rule and How Adjacency Works
The interaction model is intentionally simple. Click or tap the first gem you want to move; that cell receives a visible ring and an accessible pressed state. Then click or tap a second gem. The second gem must share an edge — top, bottom, left, or right — with the first. Diagonal cells are not adjacent, no matter how close they look on screen. If the second gem is not a neighbor, the swap is rejected and the original board is restored without changing any counter.
Even when the two gems are neighbors, the swap is only accepted if the resulting board immediately contains at least three identical gems in a straight horizontal or vertical line. A swap that creates no qualifying line is also rejected, and again the board returns to its previous state. This is the same legal-swap rollback described in the canonical match-three rules: you cannot move two pieces "just to see what happens." Every accepted swap must produce a real match on the resulting board.
Touch and mouse controls follow this same two-click model. Picking the same cell twice cancels the selection with no penalty. The on-screen feedback explains whether the rejection came from non-adjacency or from the missing match, so you always know which rule you tripped. For a closer look at how this no-download browser level differs from installed match-three apps, see Play Jewel Match Without Downloading.
How Cascades Resolve After a Legal Swap
After a legal swap, the game does not wait for your next move before continuing. Instead, it runs a fully disclosed cascade loop. First, the engine collects every horizontal and vertical line of three or more identical gems on the current board. Overlapping lines clear their union once, so an intersection cell never counts twice. Second, those gems are removed and surviving gems in each affected column keep their relative order and fall straight down toward the bottom — there is no diagonal slide and no sideways drift. Third, every empty top position in that column refills from one fixed queue. The queue contains 64 gems in a repeating Sapphire, Ruby, Topaz, Emerald cycle, giving 16 of each gem type across the queue. Columns are processed left to right; within a column, the earliest queue item falls into the lowest vacancy, followed by later items above it. Fourth, if the freshly refilled board contains another line of three or more, the entire loop runs again before the game returns control to you. Each loop is one cascade wave.
Because the refill queue is fixed rather than random, the cascade result is completely determined by the swap that triggered it. There is no seed, no network call, and no time-of-day effect on what falls next. The full objective of 12 cleared gems consumes only the first 12 entries of the queue, which leaves a defensive reserve that prevents any edge-case depletion error from exposing a half-cleared board. Refill exhaustion is handled atomically: a resolver given an empty queue returns failure instead of exposing a partially cleared board.
How to Play Jewel Match Step by Step
- Open the Jewel Match level in your browser. The starting board, read row by row from the top, is R S R S, E T R T, E S E R, and T T E S. Letters stand for Ruby, Sapphire, Emerald, and Topaz. No sign-up, account, or download is required.
- Inspect the lower-right corner of the board before moving. The only opening exchange must move one emerald away so that three rubies align vertically. The two cells to swap are at row 3 column 3 and row 3 column 4.
- Make that first swap. The accepted exchange forms a vertical ruby line at indexes 2, 6, and 10 and clears exactly 3 gems.
- Without delay, perform the second swap at indexes 11 and 15. The accepted exchange forms a horizontal sapphire line at indexes 9, 10, and 11 and clears 3 more gems.
- Make the third swap at indexes 5 and 6. A vertical line clears indexes 5, 9, and 13; gravity and the fixed refill then form a second line at indexes 13, 14, and 15 in a second cascade wave. That cascade clears 6 gems.
- Total cleared: 3 + 3 + 6 = 12 gems. The board freezes and awards exactly 1,000 points. To retry, press R.
Keyboard, Mouse, and Touch Controls Compared
The control scheme is identical in behavior across input methods, but each path suits a different setting. Mouse and touch both use the same two-click model; keyboard covers every action so the level can be played without a pointer. Holding a key cannot make two selections or spend two errors because repeated keydown events are ignored, and the grid uses native buttons with touch-friendly dimensions, visible focus treatment, English labels, and compact responsive spacing for a 390-pixel viewport.
| Input | Action |
|---|---|
| Click or tap | Select the gem under the cursor or finger; tap a neighbor to attempt a swap |
| Tap the same cell twice | Cancel selection without penalty |
| Arrow keys or W, A, S, D | Move the logical cursor around the 4×4 grid; wrap at each edge |
| Enter or Space | Select the cursor gem, then attempt the swap with the chosen neighbor |
| R | Restart the level from the opening board |
| Esc Esc (double-tap) | Replace the board with a neutral spreadsheet view; repeat to return |
Why Jewel Match Has Only One Solution
Most match-three games welcome multiple paths and reward faster solutions with bonus points. Jewel Match does neither. The level is a small deterministic logic puzzle, and a separate letter-token oracle — coded independently from the production matcher — proves the minimum route is unique.
The oracle represents the four gem types as A, B, C, and D, scans rows and columns with its own loops, implements its own gravity and refill routine, enumerates every orthogonally adjacent pair, and searches legal states by depth. It finds exactly one legal opening exchange and exactly one shortest path to 12 cleared gems at depth three. The production solver is then compared against that independently authored route, and golden tests isolate every rule boundary: an edge neighbor is accepted while a diagonal is rejected, concrete horizontal and vertical triples are identified, a no-match rollback is verified, and the first resolved board plus its gem inventory is checked. The tests also confirm that the three moves clear 3, 3, and 6 gems in cascade waves of 1, 1, and 2, and that the refill index equals the total number cleared.
The result is the three-swap route already listed above: indexes 10–11, then 11–15, then 5–6, with per-swap clear totals of 3, 3, and 6. Anyone who memorizes the route will replay the level trivially; anyone who does not can rediscover it by starting in the lower-right corner, because only an emerald move there produces the required vertical ruby line.
Why a Swap Rolls Back and What Restart Does
If a swap you attempted was rolled back, the cause is always one of two things. Either the two cells were not orthogonally adjacent, so the engine never considered the exchange, or the two cells were neighbors but the exchanged board did not contain an immediate horizontal or vertical line of at least three identical gems. Diagonal-only taps cannot match in Jewel Match, and neither of those failure modes changes any gem, refill cursor, clear total, move count, or selection. The on-screen explanation names which rule you tripped so the next attempt is informed.
Mistakes are counted by the two-error rule. The first illegal swap is repairable: you can immediately choose the unique valid opening exchange and continue from the same board. A second illegal swap deadlocks the run until you press Restart. Restart restores all 16 initial gems, refill cursor zero, clear total zero, move count zero, cursor position zero, no selection, no mistakes, and no terminal state. The score never changes during a rollback, and the 1,000-point award appears only after 12 gems have actually been cleared. Because the terminal result is frozen, a delayed keyboard event cannot alter a captured completion state, and the entire finish is auditable from start to finish.
Finally, the 1,000-point finish is fixed game behavior, not an intelligence test. The score, the disclosed board, the refill queue, and the two-error stop are all product choices. Knowing the route makes later runs trivial, and a single key slip can count as an error. For an honest look at what the score does and does not measure, see Does the 1,000-Point Jewel Match Score Measure Ability?.