Missed-checkpoint help — 2026-09-16

Einstellungen → VERPASSTE CHECKPOINTS → TROTZDEM WERTEN lets riders continue after missing intermediate checkpoints. The default remains ZURÜCKFAHREN, including for older saved profiles. The choice saves immediately and also applies when changed during a paused race.

With help enabled, a rider can take a gradual roadside detour, return to the route and continue toward the finish. Start and finish still require actual forward crossings on the road; simply placing the bike at the finish, standing there or crossing backwards cannot finish a race. The helper tracks continuous forward/backward route travel within the nearby roadside corridor, rather than treating an arbitrary nearby projection as a completed race. Its roadside allowance extends 40 m beyond the road half-width. Recovery still uses an already reached safe gate and does not teleport the rider forward.

Finished races retain normal classification, Cup points, campaign completion and unlocks. Assisted best times are stored separately and displayed as BESTZEIT MIT HILFE. Turning help off again during the same race cannot relabel an assisted run as strict. A new strict restart clears that run history. Resumed stages still cannot earn a continuous best time.

Campaign checkpoints retain the run's assist history and reconstruct their safe position from validated gate progress. Continuing respects the current saved setting. Existing checkpoint JSON defaults to strict behavior; route ID, revision, length and gate-ordinal validation remain in place.

CheckpointAssistVerification.Run() is included in the consolidated native editor verification/build entry. It exercises production route sampling and progress rules with explicit continuous position paths, strict regressions, assisted detours, missed gates, invalid placement, real start/finish crossings, recovery, resumed flags, best-time separation, profile migration, story unlocks and classic lap counts. The report is Docs/QA/checkpoint-assist-verification.json. No physical driving, controller hardware or rendered UI claim is implied by that fixture; execution evidence comes from the consolidated run.