The Multitasking Game runs five fixed rounds in which two parallel desk tasks, Aqua and Copper, share a single start timestamp, keep independent visible deadlines, and award exactly 200 points only when both tasks are secured before either clock exits its window, capping a perfect run at exactly 1,000 points.
What that means in plain terms: every time you press Start both tasks, two countdowns begin from the same instant and tick down in parallel. Each card prints its own due time and an authored acceptance window, and a live countdown updates from a requestAnimationFrame loop while scoring is decided by the event timestamp. You can only score by acting on Aqua while its card shows NOW and on Copper while its card shows NOW, and finishing both before either clock leaves its inclusive boundary. A single secured task never scores on its own. The five rounds, the per-round timing values, and the 1,000-point ceiling are fixed game fixtures, not measurements of any real-world multitasking ability.
Why Multitasking Game Is Built Around Two Live Deadlines
Most "do two things at once" browser games cheat. They switch between two prompts in sequence, accept input on whichever lane happens to be showing NOW, and treat each lane as an independent mini-round you can win on its own. The Multitasking Game takes the harder path: Aqua and Copper are truly parallel, rendered and active together from the same round-start timestamp, each with its own due time and acceptance window, and neither one pauses while you work on the other. Securing Aqua does not stop Copper's clock, and securing Copper does not stop Aqua's clock.
The point of that design is to make the timing contract visible at all times. Both cards print an explicit due offset in seconds, both show a live countdown that ticks every animation frame, and both change to NOW during their respective windows. After a valid action a card reports Secured, after an early action it reports an early failure, and after an expired window it reports a missed failure. Because the score depends on both lanes finishing in the same round, you cannot grind one lane and ignore the other, which is what separates this from a pair of back-to-back reaction tests.
If you want a deeper answer about the parallel implementation, the walkthrough Are Aqua and Copper Actually Active at the Same Time? covers the shared timestamp, the live visibility of both deadlines, and the atomic acceptance check in more detail.
How to Play the Do Two Things at Once Game to 1,000 Points
Each of the five rounds follows the same control flow. The only thing that changes between rounds is the order of the two deadlines and how close together they land. Treat every round as one shared problem with two clocks, not as two problems you can solve one after the other.
- Start the round. Choose Start both tasks. Aqua and Copper appear together and begin counting down from one shared round-start timestamp, so neither lane gets a head start.
- Read the cards before pressing anything. Each card prints its own due offset. The first round, for example, gives Aqua a due time of 1.20 seconds and Copper a due time of 2.20 seconds, which means Copper's clock has more headroom than Aqua's on Round 1.
- Handle Aqua only while it shows NOW. Use the Aqua button or press the A key when the Aqua card reads NOW. Pressing before the opening boundary fails the round as early; pressing after the closing boundary fails the round as missed.
- Handle Copper only while it shows NOW. Use the Copper button or press the L key when the Copper card reads NOW. The Copper clock keeps running while you wait, so do not get stuck on Aqua.
- Finish both tasks in the same round. A successful action on both lanes in a single round awards exactly 200 points and prepares the next authored pair. A single secured task awards zero points and the round does not advance.
- Repeat for all five rounds. Complete all five fixed rounds for the maximum score of 1,000 points, or choose Restart to return the score, round, errors, task state, and feedback to their exact initial values for a clean run.
What Changes From Round to Round
The five rounds are not random and not adaptive. Round 1 always starts with Aqua's deadline inside Copper's, which gives you a longer runway on the right lane. Later rounds reverse the order, draw the two deadlines closer together, or narrow the authored acceptance windows, so the same control flow gets progressively tighter as the run continues. Treating later rounds as harder is fair; treating any specific number as a personal benchmark is not, because every value is an authored game fixture rather than a measurement of speed or attention.
| Action | Pointer or touch | Keyboard |
|---|---|---|
| Handle Aqua task | Aqua button | A key |
| Handle Copper task | Copper button | L key |
| Confirm a focused button | Tap or click | Enter or Space |
| Start a round | Start both tasks button | Enter or Space when focused |
| Restart the run | Restart button | Enter or Space when focused |
| Hide an active round | Switch tab or hide page | Same |
The arithmetic that ties the run together is straightforward: five rounds times 200 points per clean pair equals the fixed maximum of 1,000 points. There are no random rounds, hidden shortcuts, score multipliers, or adaptive difficulty values, and independent logic tests verify that each round ships two distinct deadlines, that one lane cannot score alone, and that both lanes can independently cause a missed-round failure.
What Counts as Early, Missed, or Restart
The acceptance window is inclusive on both ends. A press is valid from the printed due time minus its authored window through the due time plus that window, so acting at the exact boundary still counts. Acting one millisecond before the opening boundary fails the round as early, and leaving either lane one millisecond past the closing boundary fails the round as missed. Both task clocks reset together when either failure fires, because the two lanes are scored as one round rather than two independent attempts.
| Outcome | Trigger | Effect on the run |
|---|---|---|
| Early failure | Press before the opening boundary | Round fails, both clocks reset, error logged |
| Missed failure | Window expires without a valid press | Round fails, both clocks reset, error logged |
| Same-failure repeat | Identical early or missed signature | Deduplicated, no extra error recorded |
| Second distinct failure | Different lane or different kind | Run closes in deadlock (terminal) |
| Visibility cancellation | Tab switch or page hidden | Attempt cancelled, no error logged |
| Restart | Restart button at any time | Score, round, errors, and state return to initial values |
Failure handling is deterministic. The game records a failure signature from the round, the lane, and the early-or-missed kind, so repeating the exact same failure on the same lane in the same round does not stack up against you. A valid completion clears the repairable error history, and a second genuinely different failure closes the run in deadlock. Once the run reaches a terminal state, later clock ticks, task presses, starts, or visibility events cannot change the result, which makes Restart the only way back to a fresh run.
Changing tabs or hiding the page is handled separately on purpose. Visibility loss cancels an active attempt without recording an error, which prevents background-tab timer throttling from turning a visibility change into an artificial miss. When you return to the tab, the same round is ready to start again with both clocks reset, and no penalty has been logged against your run.
Controls, Focus, and What the Score Does Not Measure
The interface supports pointer, touch, and keyboard input through the same pure timing reducer, so the rules do not change with the input method. Native buttons also accept Enter and Space when focused, and the task buttons exceed a 44-pixel target so they remain comfortable on touch devices. Focus management is part of the control contract: starting a round moves focus to the task with the earliest deadline, after one task is secured focus moves to the pending task, success or failure returns focus to Start, and a terminal result receives programmatic focus so a keyboard or screen-reader user is notified of the outcome. Initial page load does not steal focus.
Color supports the status display, but readable labels such as Waiting, NOW, Secured, error messages, and explicit due times carry the meaning on their own. The Multitasking Game is recreational entertainment. It does not measure or diagnose productivity, attention, cognition, reaction time, coordination, employability, learning ability, or any medical or psychological condition. A score reflects only completion of these five fictional authored timing rounds under the stated game rules.
Everything runs locally in the browser. The game uploads no actions, calls no paid service, contacts no game API, and adds no external dependency. The only thing that persists between sessions is an optional best score stored in your browser's local storage, and the live five-round scoring continues unchanged even when storage is unavailable. Try the Multitasking Game in your browser to put both clocks to the test.