A cooking game's difficulty lives in three numbers — ticket length, timer allowance and mistake cost — plus two floors that stop escalation from crossing into impossibility. Everything else is presentation.
Number one: ticket length
The formula this site uses is clamp(2 + floor(intensity × 3 + ordersServed / 6), 2, 6).
Two inputs, deliberately. The intensity term makes tickets grow with elapsed time, which is standard escalation. The orders-served term makes them grow with success, which is self-balancing: a skilled player is given a harder game without a struggling player being punished.
The cap of six is a working-memory limit rather than a taste judgement. Beyond about six items in arbitrary order, a player stops holding the sequence in their head and starts re-reading the ticket for every step — which changes the game from execution to lookup, and lookup is not fun.
Number two: the timer allowance
time = max(floor, (baseTime − intensity × 5) × (0.75 + length × 0.18)).
The structure matters more than the constants. A two-ingredient ticket gets about 1.11 × base; a six-ingredient ticket gets about 1.83 × base. Three times the work for 65% more time.
That sub-linear scaling is precisely what makes long tickets feel like an escalation rather than just more of the same. If time scaled linearly with length, a six-ingredient ticket would be exactly as easy as a two-ingredient one and the length lever would do nothing.
Number three: the mistake cost
The most consequential balance decision in the genre, and the intuitive answer is wrong.
A mistake should cost time, not a life. Two seconds in Kitchen Dash, 1.6 in Conveyor Kitchen, plus the combo chain in both.
Life-cost mistakes make players verify every input before committing, which makes them slow, which makes the timer feel like an enemy. Time-cost mistakes keep the downside bounded, so committing is always worth attempting — which produces the fast, slightly messy play that a dinner rush should feel like.
There is a third cost worth including: failed empty actions. Grabbing at nothing in a belt game costs 0.4 seconds. Without that, mashing the grab button through a busy belt would be optimal and the timing element would evaporate.
Floor one: the minimum timer
7.5 seconds in Kitchen Dash, 8 in Conveyor Kitchen.
A six-step ticket in 7.5 seconds is 1.25 seconds per ingredient. That is fast but achievable with direct clicks or taps. Without the floor, the formula would eventually produce tickets demanding inputs faster than a human can make them — a difficulty curve that has crossed into impossibility is broken rather than hard.
Floor two: ingredient availability
Specific to belt games and easy to overlook.
If ingredients arrive at random, a player can genuinely be starved of a required item by bad luck. Losing a ticket to randomness rather than to error is the worst feeling a cooking game can produce.
The fix is spawn bias: about 45% of belt spawns are specifically the ingredient the current ticket wants. It is invisible to the player and it removes an entire category of unfairness.
The ingredient count
Six stations in Kitchen Dash, eight on the belt in Conveyor Kitchen.
The difference reflects what each model costs. In a station game, more ingredients means more navigation — the row gets wider and the average travel distance grows. In a belt game there is no travel, so extra ingredients add reading difficulty only, which is cheaper.
Six is also the practical touch-target limit: six buttons fit comfortably across a phone screen at 44+ pixels each.
Balancing the reward side
Escalating difficulty without escalating reward reads as punishment. Three rewards scale alongside:
- Ingredient value is flat (45 or 50) but multiplied by the combo, which grows with a clean run.
- The serve bonus is flat (200 or 230) but also multiplied.
- The time bonus rewards speed directly at about 12 points per remaining second.
The time bonus is where the delicate balance sits. Too generous and careful play becomes worthless; too stingy and there is no reason to hurry. At 12 points per second, saving four seconds on a ticket is worth roughly a quarter of the serve bonus — noticeable, worth chasing, not decisive.
Try it yourself: Conveyor Kitchen
Pull the right ingredient off an accelerating belt before the ticket times out.
Key takeaways
- Ticket length should scale with both elapsed time and orders served, capped at six for working-memory reasons.
- Timer allowance must scale sub-linearly with length, or the length lever does nothing.
- Mistakes should cost time, not lives — bounded downside produces fast committed play.
- Failed empty actions need a small cost, or mashing becomes optimal.
- A minimum timer floor stops escalation from crossing into impossibility.
- Belt games need spawn bias toward the required ingredient, or players lose tickets to luck rather than error.
- Reward must escalate alongside difficulty, and the time bonus is where that balance is finest.
Frequently Asked Questions
How long should a cooking game ticket be?
Two to six ingredients, growing with both elapsed time and the number of orders served. Six is a working-memory cap — beyond it players stop holding the sequence and start re-reading.
Why does a longer ticket not get proportionally more time?
Because sub-linear scaling is what makes long tickets an escalation. If time scaled linearly with length, a six-ingredient ticket would be exactly as easy as a two-ingredient one.
What should a wrong ingredient cost?
Time, not a life. Around two seconds plus the combo chain. Life-cost mistakes make players verify before committing, which makes them slow and makes the timer feel unfair.
Why do belt games bias what appears?
Because purely random arrival can genuinely starve a player of a required ingredient. Biasing about 45% of spawns toward the needed item removes an entire category of unfair loss.
How many ingredients should a cooking game have?
Six for a station layout, which is also the practical touch-target limit on a phone. Eight works on a belt, where there is no travel cost and extra ingredients only add reading difficulty.