INDEPENDENT CHECKLIST · REVIEWED 28 OCT 2026 · CHECKED AGAINST THE LIVE CLIENT BUNDLE
This is the short version of a hop earth car not spawning report: the world loaded, you are on foot, the prompt is on screen, and no car appears. The public client handles that flow in a fixed order — detect the input device, print one of two prompt wordings, require a hold of one to two seconds, then place a vehicle on the nearest road through an event the bundle names vehicleSummonToRoad. Each stage can fail on its own, and each one leaves a different trace on your screen, which is why “the car will not spawn” covers at least five separate faults.
Everything below was read out of bundle10280058.js, the script the official hop.earth homepage loaded on 28 October 2026, plus the same-day live UI wording. It is not a substitute for your own session: this guide cannot see your screen, your input device or the server's response, so treat each section as a test you can run rather than a diagnosis we can make for you.
The prompt tells you which input model the client chose.
Before any car can appear, the client decides whether it is dealing with a touch session. The check is small and exact: it tests for ontouchstart in the window, or onmsgesturechange for older gesture hardware. Nothing else. The current bundle contains no user-agent parsing at all, so the phone-or-desktop question is never answered by your device string — only by whether touch events exist on the page.
That single boolean decides the prompt text. The same function returns Hold the car icon to summon a vehicle when touch is detected and Hold X to summon a vehicle when it is not. So the prompt is a free diagnostic: if your phone shows the X wording, the game is treating you as a keyboard player, the car icon you were told to hold does not exist yet, and no amount of holding the screen will summon anything. An in-app browser, a webview that suppresses touch events, or a page that lost focus after a tab switch are the usual causes. The mobile controls page covers the touch layout in full, and the mobile access guide explains why the two input models diverge.
A tap is not a summon: X has three release behaviours.
This is the most common real cause of a missing car. X is not a button that summons; it is a button whose meaning depends on how long you hold it. The key-release handler measures the press and branches three ways. Under 1,000 milliseconds, it calls the player reset. Between 1,000 and 2,000 milliseconds, it performs the vehicle action for your current state. At the 2,000 millisecond mark the action is sent for you even if you never let go, because the hold timer reaches its threshold first.
In practice: a quick tap of X respawns your character and never asks for a car. That is the failure mode behind a large share of “summoning does not work” reports, and it is invisible unless you know the timing. If you are on foot and the live prompt offers a vehicle, hold X once and keep it down for about a second and a half, watching the hold ring described below. The dedicated X key guide documents the same three tiers from the player's side.
In a car, the same key resets instead of summoning.
The client sends two different requests depending on whether you occupy a vehicle. With no vehicle, a completed hold asks for a summon. With a vehicle, the identical hold asks to reset that vehicle to the last road. Both live in the same handler, one branch apart, which explains the confusing report where “holding X” moves a car that was already there and never produces a new one. If you are trying to summon, confirm you are actually on foot first — occupying a seat is enough to make the key stop summoning.
The hold ring is the only honest feedback you get.
While a hold is in progress the client draws a small progress indicator near the bottom centre of the screen: a red fill over a blue track, sized to the fraction of the threshold you have held. Summon and vehicle reset complete at two seconds; entering or exiting a vehicle completes at one second. Nothing else tells you whether your press is being counted.
Use it as an instrument. If the ring never appears, the press is not reaching the input handler at all and the threshold is irrelevant — check focus and the chat box first. If the ring appears but stalls, you are releasing early. If it fills and the car still does not arrive, the input stage worked and the problem is downstream, in placement or session state. That single observation splits the whole diagnosis in two, and it is the reason this page asks you to watch the ring before touching anything else.
A focused chat box swallows the key.
The keyboard handler returns early while the chat or typing state is active, with one exception for the key that toggles chat itself. In that state X is received by the text field, not the game, so holding it types nothing, summons nothing, and leaves no ring on screen. If a summon attempt produced no visible feedback at all, press M or Escape once to leave the text field, click back into the game canvas, and repeat the hold. This is also why a “broken” summon key can start working again after an unrelated keystroke: the key was never broken, the focus was elsewhere.
The summon icon hides itself when it thinks you are already served.
On touch layouts the car icon is not permanently on screen. The HUD logic hides it when you already occupy a vehicle, or when the vehicle it would summon is already close — the comparison is a squared horizontal distance against 2,500, which is about 50 metres. A missing icon is therefore frequently correct behaviour rather than a bug, and the car you are looking for may be the one parked behind you. Walk away from the road you arrived on, or end the session cleanly, and the icon reappears when summoning is genuinely the useful action.
The car arrives on the road, not at your feet.
The client's own vocabulary is the clearest evidence here: the event is named summon-to-road, and the two reset events are named reset-to-last-road and reset-to-nearest-road. Vehicle placement is tied to the road network that the world generator produced for your location, so a summon from a field, a beach or the middle of a building can legitimately put the car some distance away, on the nearest carriageway. Look along the road in front of you before concluding nothing spawned.
The same three event names also explain a quieter failure: a car that seems to vanish may have been reset rather than lost. If you held the summon key while seated, or used the reset control by accident, the vehicle was moved back to a road you have already driven. The respawn guide covers recovering from that state without repeating the mistake, and the race mode guide explains why a race session supplies its own vehicle and behaves differently from free driving.
The FLIP button has two paths and a timeout.
The reset control is labelled FLIP with the caption HOLD RESET, and it is only visible while you have a vehicle the client considers unoccupied. It carries two behaviours that look identical on screen. Releasing it between 80 milliseconds and two seconds triggers the player reset. Holding it to two seconds hands the action to the reset-to-last-road path instead. A deliberate long press is therefore not a stronger version of a short one; it is a different instruction, and a press held well past the threshold can leave you convinced the button did nothing.
Order of checks for a car that will not appear.
- 01
Read the prompt before you press anything
If it names X on a touch device, the client has not detected touch and the car icon does not exist yet. Reload in a normal browser tab, then re-read the prompt.
- 02
Leave the chat box, then hold X once
If you are on foot and the live prompt offers a vehicle, hold X once and keep it down for roughly a second and a half. A tap is a reset, not a summon, so leave the chat field with M or Escape and click into the game canvas first.
- 03
Watch the ring and read what it tells you
No ring means the press never arrived. A ring that stalls means you released early. A filled ring means the request was sent, so the remaining questions are placement and session state rather than input.
- 04
Look down the road, not at your feet
Summoning places the vehicle on the road network. Sweep the nearest carriageway and any road behind you before deciding the request failed, and check whether a car you already owned was moved instead.
- 05
Restart the session once, and change one variable
Reload the official launch page, choose a location with clearly connected roads, and record what changed. If sessions never join at all, use the not-working checklist and check server status before blaming the summon key.
Frequently asked questions
How long do I have to hold X to summon a car in Hop Earth?
Between one and two seconds. In the current client (bundle10280058.js) a key release after less than one second is treated as a reset, a release between one and two seconds performs the vehicle action, and if you keep holding past two seconds the action fires automatically at that mark. A quick tap therefore does something different from a hold.
Why does tapping X respawn me instead of spawning a car?
Because that is what a short press does. The key-release handler checks how long X was held: under 1,000 milliseconds it calls the player reset, between 1,000 and 2,000 milliseconds it sends the vehicle action, and at 2,000 milliseconds the action is sent for you. If you see your character respawn, the press was too short.
There is no car icon on my phone — what happened?
The client picks its prompt wording from touch detection alone: it tests for ontouchstart or onmsgesturechange on the window and shows “Hold the car icon to summon a vehicle” when that is true, otherwise “Hold X to summon a vehicle”. If your phone shows the X wording, the touch session was not detected, and an in-app browser or a page that hides touch events is the usual reason.
The car icon is missing on desktop too. Should I reinstall something?
No. The summon button hides itself when the client thinks you already have a vehicle, or when the vehicle it would summon is within roughly 50 metres of your character — the bundle compares a squared distance against 2,500. Look around for a car you already own before assuming the button is broken, and remember that Hop Earth is a browser game with nothing to install.
I held X for two seconds and the car still did not appear next to me.
Summoning places the vehicle on the road network, not at your feet: the client event is literally named vehicleSummonToRoad. Look along the nearest road rather than at the ground you are standing on, and if the session is still loading or you are off-road in a field or on a beach, give the world time and try a location with a connected road.
Does holding reset too long cancel it?
On the FLIP / HOLD RESET control, yes. Releasing it between 80 milliseconds and two seconds triggers the reset; holding it past two seconds hands the action to the separate reset-to-last-road path instead. If nothing happened after a long press, repeat it as a deliberate short hold-and-release.