Event 1 of 5

Count: how many dots?

The same set of dots moves and bounces during the flash. Count the objects, rather than every position they pass through.

Get a Count hint

Think in groups of five or ten. The total is between 70 and 80. Follow the same moving set; crossings do not add dots.

Reveal the Count answer

77 dotsThe exact target count for #14.

Grouped illustration of 77 dots. These are not the original dot positions; the rows make the answer easier to check.
  1. Look for rough groups of five or ten during the flash, then add the remaining dots.
  2. This answer is 7 groups of ten and 7 more.
  3. Crossings and wall bounces do not add new dots. The configured exposure is 2.6 seconds; the original introduction describes it as two and a half seconds.

A count error is relative to the true total: being one dot off means 1.3% error on this field.

Event 2 of 5

Track: where does the ball land?

Watch the early part of the flight, then select the landing point on the ground. Friday adds lower gravity and live side walls.

Get a Track hint

Account for one wall bounce. The landing is right of the field’s center. A bounce happens after the ball has disappeared.

Reveal the Track landing and trajectory

83.25% across the fieldLanding x ≈ 665.976 on the original 800-unit-wide field.

Solution trajectory for Perceptle #14: landing x 665.976, 1 wall bounce.Landing x 666
Solid teal: visible flight. Pale teal: 80 ms fade. Dashed: hidden continuation. Purple marks show wall bounces. This independent diagram uses the original logical coordinates, not physical screen pixels.
Launch x
105.87
Full flight
2.652 s
Fully hidden after
1.273 s
Wall bounces
1
  1. The ball launches from x ≈ 105.87 and begins to fade at 1.193 seconds.
  2. Continue through the right-wall rebound; at least one rebound happens after the ball is fully hidden.
  3. Choose the ground position 83.25% from the left edge of the full field, right of center. The exact generated x value is 665.976047731207.

Rebound timing: right wall at 2.278 s.

The field scales to your screen. Do not tap 666 CSS pixels from your phone’s edge. The visible ground line itself spans x=30–770; this target sits 85.94% along that shorter line.

Event 3 of 5

Angle: which direction and how many turns?

The original shows the requested counterclockwise angle before you drag. This solution explains how to reach it, including the full turns.

Get an Angle hint

Keep winding counterclockwise. This target contains 2 complete turns before its final partial turn.

Reveal the Angle target and turn guide

963° counterclockwise2 full turns + 243°

963 degrees counterclockwise: 2 complete turns and 243 additional degrees.0°90°270°
The spiral shows accumulated turns. The teal line shows the final direction.
  1. Start on the dashed line pointing right: that is 0°.
  2. Wind counterclockwise through 2 complete turns (720°).
  3. Continue counterclockwise for 243° more, then release to lock.
  4. Keep the whole 963° movement. Stopping at 243° alone leaves 720° missing.

Event 4 of 5

Tempo: what pulse should you keep?

Follow four warm-up beats, then make eight continuation taps. On Friday those eight taps belong in the gaps between the original loud beats.

Get a Tempo hint

Keep the same pulse after the four loud warm-up beats, but place eight taps in the gaps. The offset changes by half a beat; the tempo does not double.

Reveal the BPM and timing reference

100 BPM600 ms per beat · off-beat continuation

  1. Follow the four loud clicks at 100 beats per minute.
  2. After the last loud beat, the first ideal off-beat is half a period later: 300 ms.
  3. Keep all eight continuation taps 600 ms apart. Changing phase does not mean tapping twice as fast.

Ideal offsets after the last loud beat:

  1. Tap 1300 ms
  2. Tap 2900 ms
  3. Tap 31,500 ms
  4. Tap 42,100 ms
  5. Tap 52,700 ms
  6. Tap 63,300 ms
  7. Tap 73,900 ms
  8. Tap 84,500 ms

These offsets assume an ideal warm-up reference. The original adjusts its timing reference using your warm-up taps and separates overall timing offset from jitter. The BPM is fixed for this date; actual wall-clock tap times depend on when you start and how you followed the warm-up.

Event 5 of 5

Split: where does the fraction land?

Measure the requested fraction from the named endpoint. The prompt already gives that value; this solution places it on the line.

Get a Split hint

Start at the right endpoint. The fraction is more than one, so pass the opposite endpoint and keep going by the remaining fraction of the original line.

Reveal the Split position and calculation

9/7 from the right128.571% of the original line · target x ≈ 148.571

9/7 measured from the right endpoint, with target x 148.571.LeftRightTarget: 9/7Original line: 320 logical units
Teal marks the starting endpoint. Green marks the answer. The dashed extension beyond the original endpoint remains part of the same measurement.
  1. The original line runs from x=240 to x=560, so its length is 320.
  2. 9/7 corresponds to 1.285714 × the original line, or 411.429 logical units from the right endpoint.
  3. 560 − (9/7 × 320) = 148.571429.
  4. Go 28.571% of one original line length past the left endpoint. Do not change the denominator to the extended line.

The answer is 128.571% measured from the named endpoint along the original line. Its position on the whole 800-unit field is 18.571% from the left. Those are different measurements.

Use the answers without mixing up the modes

July 31, 2026 is a Friday variant. Moving dots, ricochets, accumulated turns, off-beats and extended fractions use the Friday rules and wider scoring tolerances. The overall grade comes from the rounded mean of the five event scores.

Target data reconstructed from the original game’s public date-seeded generator, source checked October 17, 2026. This describes the current inspected version’s archive replay; it is not a claim of a completed run on the historical date. How we obtain and explain the targets.