INDEPENDENT CHECKLIST · REVIEWED 27 AUG 2026 · LIVE GAME UI PREVAILS
Check one layer at a time.
Public guides consistently describe a shared race flow built around a link generated by the live game. That makes the newest link and each player's ability to load Hop.Earth separately the useful starting points—not guessed URL edits or repeated refreshes.
- 01
Test a normal solo session first
Open the official game directly, sign in through its current flow and load one simple location. If this fails, resolve the browser, graphics, account or connection issue before testing a shared race.
- 02
Use the link generated in the live race flow
Create a fresh, short route and copy the share link the current interface provides. Do not hand-edit parameters, substitute an old bookmark, or assume that a normal place link contains shared-session state.
- 03
Compare the visible destination
Ask every driver to confirm the same start and finish after the world loads. If someone sees a different place or no race details, stop the attempt and resend the latest complete link rather than driving mismatched sessions.
- 04
Retry once with a compact new route
If solo play works for everyone but the shared attempt fails, wait briefly and create one new route on connected, recognisable roads. Keep the participants and route simple so the result is useful evidence instead of a moving target.
- 05
Capture a safe report if it keeps failing
Record the approximate time and timezone, desktop or mobile, the stage where it stopped, whether solo play worked and whether a new link changed anything. Do not post an active session link or account information publicly.