A conveyor belt changes the fundamental question a cooking game asks. With stations, the question is "where is the cheese and how do I get there?" With a belt, it is "the cheese will arrive — will I be ready?"
That is a timing and patience problem rather than a navigation and memory one, and it produces a noticeably different game from very similar parts.
The three tuning parameters
| Parameter | Value in Conveyor Kitchen | Effect |
|---|---|---|
| Belt speed | 165 units/sec base | How long an item is reachable |
| Spawn interval | 0.85 sec base, floor 0.35 | How crowded the belt is |
| Spawn bias | 45% toward the needed item | How often the right thing arrives |
Belt speed and spawn interval together determine density. At 165 units per second with items every 0.85 seconds, consecutive items are about 140 units apart — comfortably readable. At the late-run combination of 300 units per second and 0.35-second intervals, they are about 105 apart, which is close to continuous.
Why the belt must be biased
This is the fairness mechanism that makes belt games work, and it is invisible to the player.
With eight ingredients and uniform random spawning, the chance that any given item is the one you need is 12.5%. Over a ten-second ticket at one item per second, there is a real probability of the required ingredient simply not appearing — which means losing a ticket to randomness rather than to any mistake you made.
Biasing 45% of spawns toward the current requirement removes that failure mode entirely, while still leaving enough variety that the belt does not become a conveyor of exactly what you want.
The grabber
The player controls a vertical grabber that can move horizontally along the belt. Three input methods, all equivalent:
- Arrow keys or A/D move it at 480 units per second.
- Dragging positions it directly under the cursor or finger.
- Clicking or tapping an item moves the grabber there and fires in one action.
The third is the fastest and most players do not discover it immediately. On a belt moving at 300 units per second, the difference between direct tapping and moving-then-pressing is often a whole ingredient per ticket.
The empty-grab cost
Grabbing at nothing costs 0.4 seconds from the ticket timer.
That penalty exists for exactly one reason: without it, mashing the grab button continuously while moving the grabber would be strictly optimal, and the entire timing element would disappear.
0.4 seconds is calibrated to be noticeable without being punishing. Three failed grabs per ticket is 1.2 seconds — enough to cost you a ticket occasionally, not enough to end a run on its own.
Note that an empty grab does not break the combo chain, while a wrong ingredient does. That asymmetry is deliberate: mistiming is a lesser error than misreading.
Belt acceleration
The belt genuinely speeds up as you serve orders: base speed × (1 + orders × 0.04), capped at 1.8, multiplied again by the difficulty ramp.
By the fifteenth order the belt is roughly two and a half times its starting speed. That escalation is displayed numerically on screen — "Belt speed ×1.48" — which makes it honest escalation rather than an invisible change.
It also changes the optimal technique. At low speeds you can react to what is under the grabber. At high speeds you must position ahead of an item and wait for it to arrive, which is a different skill and is what makes late tickets genuinely demanding.
Belts elsewhere
The belt idea generalises beyond cooking. Any game where content arrives on a fixed path at a fixed rate is a belt in disguise — a runner's track is a belt you walk along, and a catcher's falling items are a vertical belt.
The shared property is that the player controls position while the content controls timing, which is the defining characteristic of the whole arcade format.
Try it yourself: Conveyor Kitchen
Pull the right ingredient off an accelerating belt before the ticket times out.
Key takeaways
- A belt converts a navigation problem into a timing problem: items come to you on their schedule.
- Belt speed and spawn interval together set density; the late-run combination is close to continuous.
- Spawn bias toward the required ingredient is essential — without it, players lose tickets to randomness.
- Tapping an item directly is faster than moving the grabber and pressing, and many players never discover it.
- An empty-grab cost is what stops mashing from being optimal; 0.4 seconds is noticeable without being punishing.
- Belt acceleration should be displayed, not hidden — invisible escalation feels like cheating.
Frequently Asked Questions
How fast does a conveyor belt game get?
In Conveyor Kitchen, base speed is multiplied by 1 + (orders served × 0.04) capped at 1.8, and again by the difficulty ramp — roughly two and a half times its starting speed by the fifteenth order.
Will the ingredient I need always show up?
Yes. About 45% of belt spawns are specifically the ingredient the current ticket wants. Without that bias, a player could genuinely be starved of a required item by bad luck.
What is the fastest way to grab items?
Tapping or clicking an item directly, which moves the grabber and fires in one action. On a fast belt that is often worth a whole extra ingredient per ticket.
Why does grabbing at nothing cost time?
Because without a penalty, mashing the grab button while sweeping the grabber would be optimal and the timing element would disappear entirely. It costs 0.4 seconds and does not break your combo.
How is a belt different from a station layout?
Stations pose a navigation and memory problem — where is the cheese? A belt poses a timing and patience problem — the cheese will arrive, be ready. Belts support more ingredients because there is no travel cost.