01A race needs more than two unrelated timers
If players choose different scrambles or control their own starts, the result is difficult to interpret. SupaKewber gives both sides the same race phases and a visible endpoint for preparation.
The goal is practical synchronization in a browser. Small network delays can still exist, but neither competitor chooses the start after seeing the other player move.
02From room code to solved state
One player creates a room and shares its code. Both players complete the displayed scramble before the preparation window ends, take hands off during the countdown and begin when the arena starts the race.
A valid solved state ends a smart-cube run. Results lead to a rematch or lobby exit, making it possible to run several short races without rebuilding the room each time.
03Live cube progress makes the race readable
A conventional timer reveals almost nothing until a player stops. Mirrored smart-cube states show whether an opponent is still in F2L, has reached last layer or is recovering from a mistake.
The same arena pattern is used for Kewber Bot races, allowing a player to practice the preparation and start routine before waiting for a human opponent.
04Use 1v1 for pressure, tournaments for samples
A live battle tests composure, starts and recovery against an immediate rival. A daily or weekly tournament is better when you want a larger average and do not need both players online together.
Review the race after the emotion passes. A rushed Cross, rotation-heavy F2L or last-layer lockup under pressure is more actionable than the win or loss alone.