Key: Each point is one saved flight, ordered oldest → newest by its exact saved date and time. The x-axis shows both date and time, always increasing left → right from the oldest saved flight to the newest; higher points mean a higher final score. Hover for full run telemetry, or click a point to pin the popup.
Landing success
OUTCOME MIX
Key: Cyan = runs with a scored landing (Pad/Mat, Cube, or Bullseye). Dark = runs with no scored landing. The center percentage is successful landings ÷ total runs. Hover or click the ring for exact counts.
Average score by pilot
INDIVIDUAL PERFORMANCE
Key: Each bar is a pilot’s average final score across the currently filtered runs. Taller bars indicate a higher average. Hover or click a bar for average, personal best, and run count.
Scoring composition
WHERE POINTS COME FROM
Key: Breaks all points earned into Field objectives, Balls, and Landing points. Bar length shows total points contributed; the percentage shows that source’s share of all points.
Objective completion
TEAM CONSISTENCY
Key: Each bar shows how often the team completed that objective. 100% means it was completed in every filtered run; 0% means it was never completed.
Pilot leaderboard
COMPLETE SUMMARY
#
Pilot
Runs
Average
PB
Recent avg
Landing %
Avg balls
PRACTICE MODE
Solo Flight
One pilot. One field. Full telemetry.
PAIR MODE
Doubles Flight
Two pilots. One shared score.
✓ Run saved
Data & Cloud
Runs are always saved in this browser first. Optional Supabase sync gives you a cloud copy while keeping this app as one HTML file. Create a table named time_warp_runs with columns: id (text primary key), created_at (timestamptz), mode (text), pilot1 (text), pilot2 (text), drop_zone/loading_station/pillar/flight_path (bool), inner_balls/outer_balls/score (int), landing (text), notes (text).