Chrome Rally steering: gates, boost and recovering BODY

Set a line before the gate, then correct the exit

Chrome Rally rewards staying near the road centre while steering velocity takes time to change. Start correcting before a coral gate reaches the car. Release or reverse the steering input early enough to avoid carrying the same sideways movement into the next bend.

There is no separate accelerate or boost button. Distance advances automatically. A clean central line builds boost, and a successful gate adds a boost pulse. Repeatedly pressing Space cannot spend that boost or make the car jump.

This guide applies to the current native Chrome Rally 2.0.0 runtime. Open Chrome Rally to use the controls below.

Read these three counters together

Counter	What it measures	What ends or changes the attempt
LAP and distance	A total of 1,200 distance units, divided into three 400-unit laps	Reaching 1,200 completes the race
TIME	Starts at 72 seconds after the startup countdown	Zero before the finish ends the attempt
BODY	Starts at 100%; leaving the road drains it	Zero ends the attempt even if time remains

Score and gate combo are rewards, not alternative completion conditions. A high score with BODY exhausted is still a failed race. A missed gate resets combo but does not itself end the run.

The score screen distinguishes Challenge complete from Run over. Read that result as well as the number. The S/A/B/C grade is a score summary, not a guarantee that the run was mistake-free.

Choose keyboard or pointer steering

Input	What to do	Important limit
Keyboard	Hold Left/Right or lowercase a/d, then release or correct the other way	The car has steering velocity; release does not instantly stop drift
Mouse or touch	Move or drag horizontally on the canvas to set a steering target	The pointer target remains after movement stops
Mixed inputs	A held horizontal key takes priority over pointer assistance	After key release, steering can return toward the last pointer target

Keep the pointer outside the canvas when practising a purely keyboard-driven line. A new run clears the old pointer target. Up/Down, Space and repeated clicks on a gate are not accelerator, brake or boost controls in this runtime.

Use Pause, P or Escape before reading instructions during a run. Resume continues the attempt. Restarting or reloading initializes a new race; a stored personal best does not save your position.

A first attempt with a clear stopping check

1. Use Play and wait until the startup countdown ends. The 72-second race clock starts with the active run.
2. Try a short Left or Right input and release it. Watch the car continue easing sideways; this is the movement you must allow for before a gate.
3. Read the approaching road bend and coral posts. Move toward the required central line before the posts reach the car.
4. After the gate, read the next bend instead of adding another correction automatically. A late correction can solve the gate entry while putting the car off the road on exit.
5. If BODY starts falling, return to the road before chasing another combo. Continue until 1,200 distance or the result screen, then identify which condition ended the run.

Later laps add speed. They do not add another accelerator control. A correction that was early enough on the first lap can become late as the next bend approaches faster.

Understand what boost and gates actually reward

The first gate check occurs at 115 distance units; further checks are 120 units apart. The game evaluates how close your racing line is to the road centre when a gate is crossed. You do not need to click the drawn posts.

A successful gate increments combo. Its score bonus is 120 plus 45 times the new combo, so the first three consecutive gate bonuses are 165, 210 and 255. A missed gate resets combo; the next accepted gate begins again at 165. These are gate bonuses, not the full final score, which also includes running score and completion bonuses.

Successful gates add 28 boost points, capped at 100. A very central line also builds boost over time. Boost otherwise decays, and off-road running burns it faster. Do not look for a button to trigger it: the game uses the current boost automatically in its speed calculation.

Recover from the failure you can see

What you see	Likely cause in the current rules	Next action
The car leaves the road after a good gate	Steering velocity carried the entry correction into the exit	Correct earlier and read the next bend after the gate
BODY drops while the clock still looks safe	The car is outside the permitted road band	Return toward the road centre before chasing gate score
GATE MISSED but the race continues	The racing line was not close enough to centre at the gate check	Reset your line for the next gate; combo has restarted
The car steers again after key release	A previous canvas movement left a pointer target	Keep the pointer clear during keyboard practice, or restart for a clean input comparison
Space does not produce a boost	This game has no boost activation key	Build boost through clean lines and successful gates
The run ends before three laps	TIME or BODY reached zero	Check both counters in the next attempt; score alone does not explain the failure

Practise one observable change at a time

For steering practice, compare a late correction at the gate with an earlier correction before it. Watch whether the car exits on the road and whether BODY stops falling. Do not assume the earlier input helped solely because the final score was higher.

For pointer practice, use one steady target and observe how assistance follows it. Then compare that with a keyboard-only attempt. This separates control behaviour from the changing road and avoids treating mixed input as random drift.

For gate practice, count consecutive accepted gates and note where combo resets. You can use the 165/210/255 gate bonuses to understand why a clean sequence earns more; it is not a promise of a maximum score.

Rule checks and the next step

Checked on 13 October 2026 against the effective native rally definition, including its later runtime override. An ordinary keyboard/mouse run completed the current race with Challenge complete, score 2,331 and grade S during this review. That confirms a playable completion path; it is not a best-score benchmark or proof of every device combination.

This page explains the current rules and recovery steps. It does not measure average completion time, frame latency or every browser's performance. If a future active runtime changes the clock, gate spacing or input model, the affected sections need to be checked again.

Play Chrome Rally to practise the line and exit correction. To choose a different task, use the racing comparison or keyboard controls comparison. Those pages distinguish this road-steering game from distance-and-fuel rides and discrete lane changes.