Cocktail Mixing Game scores each accepted round with the disclosed formula 200 minus the rounded total percentage-point deviation times 10, capped at zero, and it awards exactly 1,000 points when you clear five rounds at zero deviation. The browser challenge presents five zero-proof ratio briefs, each showing a target expressed in three invented interface streams called Lumen Drop, Cloud Ribbon, and Comet Fizz, none of which are real beverages. You set each stream to an integer from 0 through 10 with native slider controls, submit through the Shake button, and watch the live reduced ratio, the component gap, the total deviation, the projected round score, and the running miss counter update immediately. A mix passes when total proportional deviation is no more than 6.00 percentage points, anything above that threshold produces a miss and awards no points. These three facts, the formula, the 6.00 threshold, and the five-round ceiling, define the entire scoring economy of the Cocktail Mixing Game.
The Cocktail Making Game as a Ratio Challenge
The keyword "cocktail making game" pulls readers toward a wide range of products, from mobile bartender simulators to time-attack serving games. The Cocktail Mixing Game answers a different question. It is a fictional zero-proof ratio challenge, and the activity contains no alcoholic ingredient, serving advice, preparation guidance, health claim, or safety recommendation. Every round name is an original game fixture rather than a beverage recipe, and the three streams on the interface are invented tokens that exist only inside the panel.
Each round displays one visible three-part target while the page reveals only the active brief and its current proportions. Later brief names and target values are not listed in surrounding copy or rendered ahead of play, so every round begins with a fresh read of a single target. The work is purely proportional: set three integer amounts between 0 and 10, submit, and compare shares. There is no second hidden solution field, so the submitted values are the actual values judged by the reducer, and what the panel shows after Shake is the full truth of the outcome.
Because the three streams are completely fictional, the activity does not pull from any recipe database, random service, or external data feed. The whole panel runs on text, CSS, React state, and the existing GameShell, so every value the player sees is generated locally. That reproducibility is the reason the score formula and threshold are so explicit: there is nothing to hide behind, no random card draw or animated timing window, just one comparison step between the chosen sliders and the visible target.
The Score Formula and the 6.00-Point Threshold
Scoring happens through a single disclosed rule. For each round, the game divides each actual amount by the total actual amount and each target part by the total target parts. It then sums the absolute percentage-point gap between those shares for all three streams. The result is the total proportional deviation. The round score is max(0, 200 − round(totalDeviation × 10)), with one extra rule layered on top: total proportional deviation must be 6.00 percentage points or less, otherwise the attempt counts as a miss and awards no points regardless of what the formula would otherwise return.
| Round outcome | Total deviation | Round score |
|---|---|---|
| Perfect match | 0.00 percentage points | 200 |
| Near match example (4:6:9 vs 2:3:5) | ~5.263 percentage points | 147 |
| Boundary pass | 6.00 percentage points | 140 (formula gives 200 − 60) |
| Above threshold | More than 6.00 percentage points | 0 (miss) |
Because every brief awards at most 200 points, the only way to reach the disclosed maximum of 1,000 is to score a perfect 0.00 deviation on all five rounds, which means 200 points × 5 rounds = 1,000 points. Accepted near matches reduce the total in a fully reproducible way; the panel lists the exact round-by-round figures, and the projected score on the Shake result mirrors what the formula computes before any score lock-in.
How to Play the Cocktail Making Game
The cockpit has three sliders, one Shake button, a Restart control, and a Boss toggle. The procedure below covers a single round from the first visible target through score lock-in.
- Read the current three-stream target shown at the top of the round panel.
- Set Lumen Drop, Cloud Ribbon, and Comet Fizz to integer amounts from 0 through 10 using the native range controls. Arrow keys still work natively, and pointer or touch input feeds the same controlled values.
- Confirm that not every stream is at zero, because a zero-only input is invalid; adjust at least one slider above zero before submitting.
- Watch the live reduced ratio, the three component percentage-point gaps, and the projected round score before committing to the Shake.
- Choose Shake ratio by clicking the button, pressing Enter, or pressing Space; the same pure judgment function runs in every case.
- If the total deviation is 6.00 or less, the round passes and adds the projected score to your total. If the total is above 6.00, the round produces a miss and adds nothing.
The native range controls retain their native Arrow-key behavior, so a keyboard player can step each slider with the arrow keys and submit with Enter or Space without ever leaving the keyboard. Touch users on mobile browsers reach the same controlled values through the standard slider tap and drag affordance, and the touch targets stay large enough for comfortable use on small screens. The Shake button uses the same pure judgment function whether activated by click, Enter, or Space, so the score is identical regardless of the input method. After the fifth brief, the panel displays the locked final total; if the run has not been deadlocked by two distinct misses, you can either restart from the first target or step through the totals round by round.
Why 2:3:5 and 4:6:10 Are the Same Attempt
The game divides submitted integers by their greatest common divisor before creating the miss signature, which means scalar equivalents collapse into a single attempt. The pair 2:3:5 and 4:6:10 reduce to the same normalized form 2:3:5 after GCD normalization, since GCD(2,3,5)=1 leaves 2:3:5 unchanged while GCD(4,6,10)=2 divides 4:6:10 down to 2:3:5; both produce 0.00 percentage-point deviation against any matching target, and both register as one miss signature if they were to fail above the threshold. This is the same logic that prevents losing two repairable chances to one mathematical repeat.
To see the deviation arithmetic in action, work through the verified near-match example. Suppose the visible target is 2:3:5 and the submitted mix is 4:6:9. The actual sum is 19, so actual shares are 4/19 ≈ 0.2105, 6/19 ≈ 0.3158, and 9/19 ≈ 0.4737. The target sum is 10, so target shares are 0.2000, 0.3000, and 0.5000. The absolute gaps per stream are about 0.0105, 0.0158, and 0.0263. Summed, they give total proportional deviation ≈ 0.0526, which equals 5.263 percentage points. The round then awards 200 − round(5.263 × 10) = 200 − 53 = 147 points. Every figure on the panel reproduces this calculation, and the projection that appears before Shake is identical to the value locked in after.
Misses, Repair, Boss Key, and Restart
The panel tracks more than just score. Each interface includes the live reduced ratio, the component gaps, the total deviation, the projected round score, the previous accepted score, and the running miss count, so every outcome is reproducible from what the page shows at the moment of judgment. One distinct above-threshold ratio is repairable: the game stores only normalized miss signatures, so a second scalar-equivalent above-threshold attempt does not consume another chance. A second different above-threshold ratio, however, closes the run until Restart.
| Game state | Trigger | Effect |
|---|---|---|
| Round pass | Total deviation ≤ 6.00 percentage points | Round score added, miss history cleared |
| Round miss | Total deviation > 6.00 percentage points | No score added, normalized signature stored |
| Run deadlock | Second distinct above-threshold miss | Run closes, judging frozen |
| Run complete | Fifth brief accepted | Run closes, judging frozen |
| Restart | User action | First target, zero score, no misses |
Accepted mixes clear the current miss history and open the next round. Completed and deadlocked states freeze judging, so the sliders and the Shake button stop producing new scores while the lock remains. Once the run deadlocks on a second distinct miss, the sliders and the Shake button freeze their judging behavior; the panel still shows the previous round's deviation numbers and the running totals, but new Shake submissions no longer register until Restart is pressed. A completed run that reaches the fifth brief and locks the score behaves the same way: the totals are visible, but no further submissions are accepted. Restart restores the first visible target, zero inputs, no misses, and zero score, giving a clean run from the opening brief.
The shared Boss control covers the interface after a double Escape. While the Boss screen is up, the page explicitly blocks slider updates, Shake, and Restart, because a visual overlay alone would not disable focused native controls. The page stays responsive, keeps touch-size controls, and uses only text, CSS, React state, and the existing GameShell, so no account, upload, API, or random service participates in the outcome. Knowing the formula and the threshold is enough to plan every brief: pick a mix whose shares match the target within roughly one and a half percentage points per stream, accept the projected score, and clear all five rounds at 0.00 deviation to record the disclosed maximum of 1,000 points on the Cocktail Mixing Game.