Most hazard collisions are not reaction failures. They are recognition failures — the player saw the hazard, but too late to have a plan, because they were identifying it rather than recognising it.
Learn the silhouettes
Every hazard on this site has a distinct outline, and shape is processed considerably faster than colour.
| Hazard | Shape | Behaviour |
|---|---|---|
| Supply crate | Square with a cross brace | Static |
| Wet-floor cone | Triangle with a white band | Static |
| Burner flame | Flickering peak | Static, animated |
| Spinning whisk | Four radial spokes | Moves on a visible vertical path |
| Falling rock | Irregular polygon | Falls, rotating |
| Steam vent | Rising circles above a bar | Fires on a cycle |
| Boiling pot | Wide body with bubbles | Overhead — requires a duck |
| Sauce spill | Flat ellipse | Low and wide |
Spending one run deliberately watching only the hazard entry point — the left edge in a runner, the top in a catcher — until the silhouettes are automatic is the single most effective drill available.
Know how long you have
Hazards enter from the edge of the screen and are never spawned inside the visible area. That gives you a known window, and knowing roughly how long it is changes what you can attempt.
At Sushi Sprint's 390 units per second, a hazard entering the right edge of a 960-unit-wide field reaches the player at about x=190 in roughly two seconds. At Ice Cream Run's 285, it is nearly three.
Two seconds is enough to finish collecting an arc and still clear the obstacle. One second is not. Calibrating that is most of what separates a confident player from a cautious one.
Distinguish patrol from chase
Arena hazards use two behaviours and they demand opposite responses.
- Patrol hazards move on a sine path. Their position is predictable about a second ahead, so you can wait one cycle and cross behind them. Ignoring them is often correct.
- Chase hazards steer toward you with gentle acceleration. They cannot be waited out, but their acceleration means they turn slowly — cutting across their turning arc leaves them behind.
The tell is simple: watch one for two seconds. A patrol hazard's path repeats; a chase hazard's does not.
Collect around hazards, not away from them
The instinctive response to a hazard is to move away from it, which usually means abandoning whatever you were collecting.
The better response is to curve around it while continuing your route. A hazard occupies a small area; going around it costs a fraction of a second, while reversing costs your position and often your chain.
In maze games this is more explicit: the generator knocks out an extra 2% of walls specifically so you can loop around a block rather than being forced into a dead end.
When taking a hit is correct
This is counter-intuitive but it follows directly from the scoring arithmetic.
A hit costs a life and your chain. At ×1, the chain is worth nothing, so the hit costs only the life. If a 240-point risk placement sits behind a hazard and you are at ×5, the points arrive before the collision does — 1,200 points for one life is frequently a good trade, especially on Easy with four lives.
Conversely at ×8 with one life on Expert, almost nothing is worth a deliberate hit.
Use the shield as a licence
The Kitchen Shield absorbs one collision. A player who treats it as insurance and plays identically has wasted it; a player who treats it as permission to take the route they were declining has used it properly.
It is worth most in games where a hit costs more than a life: Donut Run's sugar meter, Food Monster Escape's pursuer surge, Sandwich Stack's two lost layers.
Try it yourself: Food Factory
Clear every ingredient token from a generated factory floor before the shift bell rings.
Key takeaways
- Most collisions are recognition failures, not reaction failures. Learn the silhouettes.
- Hazards always enter from the screen edge, which gives you a known and calculable window.
- Patrol hazards repeat and can be waited out; chase hazards turn slowly and can be outmanoeuvred.
- Curve around hazards rather than reversing — reversing costs position and chain.
- A deliberate hit is correct when your multiplier is low and the reward is high.
- A shield should change your routing, not just your safety margin.
Frequently Asked Questions
Why do I keep hitting hazards I saw coming?
Usually because you were identifying them rather than recognising them. Learning each hazard's silhouette converts a slow identification into a fast recognition with a pre-built response.
How long do I have to react to a hazard?
It depends on the game's speed. At Sushi Sprint's 390 units per second a hazard crosses the screen in about two seconds; at Ice Cream Run's 285 it is nearly three.
How do I tell a patrolling hazard from a chasing one?
Watch it for two seconds. A patrol hazard's path repeats on a sine cycle; a chase hazard steers toward you and does not repeat.
Is it ever right to take a hit deliberately?
Yes, when your multiplier is low and the reward is high. At ×1 a hit costs only a life; a 240-point risk placement at ×5 pays 1,200 before the collision registers.
What is the best way to use a Kitchen Shield?
As permission to take a route you were declining, not as insurance on the route you were already taking. It is worth most in games where a hit costs more than a life.