Every game needs an obstacle. The usual choice is something physical: an enemy, a wall, a pit. Cooking games make a different one — the obstacle is a clock — and the consequences of that choice run through the entire genre.
This guide is about why a deadline is a better obstacle than a hazard for this kind of game, and how to design one that creates pressure without creating unfairness.
What a deadline does that a hazard cannot
A physical hazard makes a player more careful. That is its nature: something can hurt you, so you slow down and pay attention. In a game about executing a sequence quickly, making the player more careful is directly counterproductive.
A deadline makes a player faster. It is the only common obstacle with that property. And speed, unlike caution, compounds with skill in an interesting way: a better player does not simply survive longer, they finish more work per minute, which means the game gives them more to do.
The test
Ask what a player does when your obstacle appears. If the answer is 'slows down and watches it', you have a hazard. If the answer is 'moves faster', you have a deadline.
For a game about sequencing under pressure, only the second is useful.
Making pressure visible
Pressure a player cannot see is just an unpleasant surprise. The display of a deadline matters as much as its length.
Bars beat numbers
This is not a stylistic preference. A number requires foveal vision — you must look directly at it and read it, which takes a deliberate glance and costs you whatever you were looking at.
A bar can be read peripherally. You do not need to look at it to know roughly how full it is, which means a player executing a ticket can track their remaining time without taking their eyes off the stations.
That is why every timer on this site is a bar: the ticket timer in the cooking games, the delivery window in Pizza Dash, the shift timer in Food Factory, the round timer in the challenge gauntlets.
Colour as a second channel
The timer bars on this site change colour at thresholds: green above 40%, amber between 20% and 40%, red below 20%. That gives a second, coarser signal that is even easier to read peripherally than the bar's length.
Colour alone is never sufficient — the bar's length carries the same information for players who cannot distinguish the hues — but as a redundant channel it is genuinely useful.
Audio as a third channel
Below three or four seconds, the games play a short tick twice per second. It is the only warning that works when you are looking at something else entirely, and it is deliberately quiet enough not to be stressful on its own.
How long is the right length?
The honest answer is that it depends on the number of actions required, and the useful version is that the time allowance should scale sub-linearly with the work.
In Kitchen Dash a two-ingredient ticket gets about 1.11 times the base allowance and a six-ingredient ticket about 1.83 times. Three times the work, 65% more time. That gap is what makes long tickets feel like a genuine escalation rather than just more of the same.
Two constraints keep it fair:
- A floor. Timers never go below 7.5 seconds in Kitchen Dash or 8 in Conveyor Kitchen. Without a floor the formula eventually demands inputs faster than a human can produce.
- A ceiling on ticket length. Six ingredients, because beyond that a player stops holding the sequence in memory and starts re-reading, which turns execution into lookup.
Escalating without cheating
There are honest and dishonest ways to make a timed game harder, and the difference is whether the player can perceive the change.
| Honest escalation | Dishonest escalation |
|---|---|
| Tickets get longer | The timer secretly drains faster |
| Timers get shorter, visibly | Inputs are silently dropped |
| The belt speeds up, visibly | The required ingredient stops appearing |
| More orders arrive at once | The hit box for a station shrinks |
Everything in the left column is observable. The player can see that tickets are longer, that the bar is shorter, that the belt is faster. They can adapt, and improvement is possible.
Everything in the right column is invisible. The player experiences the game getting harder without being able to identify what changed, which produces the specific frustration of feeling cheated.
Conveyor Kitchen is a good example of honest escalation. Its belt speed multiplier is displayed on screen — "Belt speed ×1.48" — so the escalation is not only observable, it is stated numerically. There is no ambiguity about what changed.
Failure has to be recoverable
A timed game where failure ends the run teaches the player that the timer is an enemy. A timed game where failure costs something bounded teaches them that the timer is a resource.
The second framing is much better, and it is achieved by grading the failure states:
- A wrong input costs seconds and the combo chain. Small, immediate, recoverable within the same ticket.
- An expired ticket costs a life and the chain. Significant, but a new ticket arrives immediately with a full timer.
- Running out of lives ends the run. The only terminal state.
Three tiers, with the cheapest failure being the most common. A player who makes two wrong inputs per ticket still completes tickets; they just score less. That means bad play is visible in the score long before it is visible in the run ending, which is exactly the feedback a player needs to improve.
Try it yourself: Conveyor Kitchen
Pull the right ingredient off an accelerating belt before the ticket times out.
Rewarding speed without punishing care
If a deadline only threatens, it produces anxiety. If it also pays, it produces urgency — a much better feeling.
That is what the time bonus does. Serving a ticket with time to spare pays roughly 12 points per remaining second at the current multiplier. It converts the timer from a threat into a currency: the seconds you did not need are worth something.
The balance is delicate. Too generous a time bonus and careful play becomes worthless; too stingy and there is no reason to hurry. The ratio this site uses means a four-second saving on a ticket is worth roughly a quarter of the serve bonus itself — noticeable, worth chasing, not decisive.
Pizza Dash takes this further, paying about 40 points per remaining second on its delivery window. There, speed is the primary scoring mechanism rather than a bonus on top of one.
The queue dimension
Everything above concerns a single deadline. The genre's other pressure source is what happens when deadlines overlap.
This site's cooking games use a strictly sequential queue — one ticket at a time — which is a deliberate simplification. Parallel tickets add a scheduling problem on top of the execution problem, and on a phone screen that combination becomes unreadable quickly.
What replaces the parallel pressure is the rush structure: every four or five services, tickets get longer and timers get shorter. The pressure escalates without the display having to hold more information.
That trade — depth of simulation against readability — is one that browser games face constantly, and readability usually wins. A brilliant scheduling system that cannot be read on a 375-pixel screen is not a feature.
Time pressure outside the kitchen
The same principles apply wherever a deadline appears on this site, and comparing them shows how versatile the mechanism is.
| Game | Deadline | What happens when it expires |
|---|---|---|
| Kitchen Dash | Per-ticket timer | Lose a life; a new ticket arrives |
| Pizza Dash | Delivery window | Lose 120 points and the chain; run continues |
| Food Factory | Shift bell | Run ends |
| Ultimate Food Challenge | Round timer | Lose a life; the gauntlet continues |
Pizza Dash is the gentlest: a missed deadline costs points only, which makes every delivery a bet the player can afford to lose. Food Factory is the harshest: the shift bell ends the run outright, which is why its timer is displayed most prominently.
Both are valid, and the choice tells the player what kind of game they are in. A deadline that ends the run demands caution; one that costs points invites ambition.
Key takeaways
- A deadline is the only common obstacle that makes players faster rather than more careful, which is exactly what a sequencing game needs.
- Display deadlines as bars, not numbers — a bar can be read peripherally while looking elsewhere.
- Use colour and a quiet audio tick as redundant channels, never as the only channel.
- Time allowance should scale sub-linearly with the work required, with a hard floor so late tickets stay possible.
- Escalate only in ways the player can observe. Invisible escalation produces the feeling of being cheated.
- Grade failure into three tiers so the cheapest failure is the most common, and bad play shows in the score before it ends the run.
- Pay for unused time. It converts the timer from a threat into a currency, and urgency is a better feeling than anxiety.
Frequently Asked Questions
Why do cooking games use timers instead of enemies?
Because a hazard makes a player more careful and a deadline makes them faster. In a game about executing sequences quickly, more careful is directly counterproductive.
Why are timers shown as bars rather than numbers?
A number requires you to look directly at it, which costs you whatever you were watching. A bar can be read peripherally, so you can track your remaining time without taking your eyes off the stations.
What is dishonest difficulty escalation?
Any change the player cannot perceive — a timer that secretly drains faster, inputs silently dropped, a required ingredient that stops appearing. It produces the feeling of being cheated, because the player cannot identify what changed.
Should running out of time end the run?
It depends on what you want from the player. A deadline that ends the run demands caution; one that costs points invites ambition. Pizza Dash costs points, Food Factory ends the run — both are valid and both are stated clearly.
Why do these games handle one order at a time?
Parallel tickets add a scheduling problem on top of an execution problem, and that combination becomes unreadable on a phone screen. The rush structure supplies the escalating pressure instead.
Is it worth serving fast if I could serve safely?
Yes. Unused seconds pay roughly 12 points each at your multiplier, which makes a four-second saving worth about a quarter of the serve bonus itself — noticeable and worth chasing.