A virtual race, not a physical distance claim
The race turns valid same-direction wheel events into capped virtual progress under a public versioned protocol. Its meters are game units used to make repeated attempts easy to read; they never claim that a mouse wheel or finger traveled that physical distance.
How the 100 Meter Scroll Test Works
Select 25m, 50m, or 100m and start the three-second countdown. Once the track becomes active, keep the pointer over it and scroll consistently in one vertical direction. The first three eligible events establish the sign used for this attempt. Matching events add normalized virtual distance; opposite input adds a direction error without advancing the runner.
The track shows distance, percentage, elapsed active time, current virtual speed, average virtual speed, peak virtual speed, valid events, and quality. Pause stops input and timing until Resume. Restart clears the unfinished attempt. When progress reaches the selected finish, the run stops automatically and unlocks a local save control and PNG score card.
Why the Distance Is Virtual
A browser receives delta values rather than a physical tape measurement. `deltaMode` may identify pixels, lines, or pages, and operating-system acceleration can alter magnitude. Treating raw deltaY as real meters would be misleading. This mouse scroll game therefore calls its track a virtual browser-based challenge everywhere a result is shown.
Protocol 1.0 applies a mode-specific display weight and limits one event to 2.5 virtual meters. The cap prevents an extreme event from instantly finishing the 25m mode. Pixel, line, and page units are never mixed as though they were identical physical quantities, and the protocol version remains attached to every saved result.
25m, 50m, and 100m Modes
The 25m mode is a short practice run and a convenient way to learn the countdown and direction calibration. The 50m mode requires a longer sustained gesture while remaining quick to repeat. The full 100 meter scroll test emphasizes continuity and pacing across a longer virtual track.
Personal bests are separated by selected distance and protocol version. A fast 25m finish cannot replace a 100m record, and a future protocol cannot silently overwrite a 1.0 best. Keep the distance, browser, input method, and scroll settings unchanged when comparing your own attempts.
How Speed and Progress Are Calculated
For each valid event, the model multiplies absolute vertical delta by the explicit weight for its deltaMode and caps the result. Progress is the sum of these virtual contributions, limited at the selected finish. Current virtual speed uses contributions in a recent half-second window; peak speed retains the highest such window; average speed divides completed virtual distance by active finish time.
Those figures are deliberately called virtual speeds. They are useful within this game protocol and a controlled browser setup, not for estimating surface travel, encoder resolution, device polling rate, or a universal advantage. A reverse event contributes zero progress and increments Direction errors so a run's consistency stays visible.
How to Run a Consistent Challenge
Use one mouse wheel mode or one touchpad technique for the whole run. Place the pointer over the track before the countdown ends, avoid pinch zoom, keep the window focused, and repeat the same distance several times. Warm up separately if necessary rather than mixing exploratory gestures into the formal attempt.
Page hiding and focus loss pause the run and add a quality flag. Synthetic WheelEvent objects are rejected from formal progress. These client-side boundaries do not prove that a score is genuine; they simply prevent obvious non-user input and disclose interruptions. Read the flags before treating one local time as a useful personal comparison.
Personal Bests and Local Storage
After finishing, enable Save results on this device and explicitly save the versioned summary. The Test Results page can show, compare, export, and delete challenge records. The tool finds the fastest compatible local record for the selected distance and displays the difference from that best.
Nothing is synchronized across devices or accounts. Clearing site data removes the history. Other users of the same browser profile may access saved labels and results, so labels are optional and should not contain sensitive information. Protocol-version separation protects older results from being presented as if they used new rules.
Local PNG Score Cards
A finished challenge can be drawn to a high-density canvas using only shapes, text, and system fonts. The browser encodes that canvas as PNG after you request a preview. The card includes the site name, mode, finish time, average virtual speed, direction errors, date, virtual-challenge wording, and canonical page URL.
The optional local label is excluded by default and enters the image only after you check the setting. Download uses a temporary local object URL; supported browsers may also offer a user-triggered clipboard write. There are no remote images to taint the canvas, no server image endpoint, and no badge, certification, global rank, fingerprint, or invented percentile.
Why There Is No Unverified Global Leaderboard
A trustworthy public leaderboard needs server-side identity, protocol enforcement, abuse controls, and a verification model. This site intentionally provides none of those in Phase B: it is a static, account-free browser tool. A localStorage time can be changed by its device owner and is never labeled verified.
Keeping comparison personal avoids a fictional world record, fabricated average, or meaningless global percentile. The challenge remains useful as an enjoyable repeatable exercise and a way to compare your own sessions under known conditions, without collecting identity or constructing a browser fingerprint.
Mouse Wheel and Touchpad Differences
A notched wheel often produces larger separated events, while a free-spin wheel can create a burst and a touchpad may create many small inertial events. The normalization cap and deltaMode weights make the track playable, but they do not make every device equivalent. Input hardware, drivers, operating-system settings, and browsers still affect results.
Choose one input type for a comparison set. If your goal is to inspect two-finger inertia or horizontal behavior rather than play a challenge, use the touchpad scroll test. For fixed-time event rate use the speed test; for stopping precision use the accuracy test; for cumulative directions use the counter.
Continue with a focused test
Use a diagnostic or measurement page when you want evidence beyond a game result.
100 Meter Scroll Test questions
Did my wheel physically travel 100 meters?
No. Meter is a virtual game unit produced by protocol 1.0. The browser does not provide physical wheel travel to this page.
How is the direction selected?
The first three eligible vertical events establish the dominant sign for that attempt. Later opposite events add errors and no progress.
Can one huge event finish the race?
No. Each event is capped at 2.5 virtual meters, including page-mode input.
Is my personal best verified?
No. It is a local browser record for personal comparison, separated by mode and protocol version. There is no public leaderboard.
Is the PNG generated on a server?
No. A browser canvas draws and encodes it locally after a completed run. Your optional label is excluded unless you explicitly include it.