Choose the water-disposal recipe first
Spaghetti has two starting variants. Traditional Recipe lets you drain pasta water into a sink. Extra Starch requires disposing of that water in a bin. A layout for one disposal method is not automatically a layout for the other.
The basic sequence is pot + water + spaghetti → cook → drain → portion onto a plate → add sauce. A pot provides two pasta portions. Basic tomato sauce needs two chopping stages. For water extraction from a sink, use the current Portioner rules: old Combiner-based water tutorials predate the 1.4.3 change.
Build one stage at a time
Start by serving manually while building blueprint supply through the Research Desk. Then reduce one repeated action at a time:
- Tomato preparation: feed a Mixer and only remove the required finished sauce state. Keep a place to collect it while the rest of the recipe is manual.
- Pot and water handling: check that the receiving item is an empty pot, that it gets water, and that spaghetti is added before cooking.
- Cooking and draining: use the disposal destination required by your starting card. Check the resulting pot still contains pasta before moving it onward.
- Portioning and assembly: keep a clean plate supply, portion cooked pasta, then add the right sauce. Train filters on the actual desired state.
- Return paths: provide space for emptied pots, dirty plates and waste. Block each output in Practice Mode and see whether the cooker remains safe.
Useful components include Mixers for sauce preparation, Grabbers for transfer, Smart Grabbers where intermediate states must be excluded, Combiners for valid ingredient assembly and Portioners for applicable extraction. Exact quantities depend on menu, map and how many steps remain manual; this is a staged workflow, not a universal tile layout.
Extra sauces are separate branches
Bolognese needs cooked mince and tomato sauce cooked together in a pot. Cheesy Spaghetti adds the roux, milk-processing and cheese work. Lasagne combines the two sauce branches with pasta sheets and a separate tray cooking and portioning cycle.
Add each branch only after its input and return paths work. A base tomato-spaghetti loop does not cover every additional recipe by changing a single filter.
Picky Eaters and waste need their own loop
Picky Eaters leaves food on dirty plates. Clear the remaining food before sending the plate into the ordinary washing loop. The 1.5 changes let Combiners bin items, Portioners empty full bins, and Dish Racks hold matching Picky Eater dishes. Check Bin handling and dirty plate return as well as food production.
HydraBurrito’s long-form demonstration shows both pasta-water and Picky Eater handling, including corrections to the plate line. It uses the large GLOBE Banquet Hall map. Its compact Extra Starch disposal timing is not a guarantee that a different map, card set or conveyor order will work.
Diagnose the first wrong item
| Symptom | Likely place to inspect |
|---|---|
| Empty pot reaches the next step | The disposal action removed more than the intended water, or an intermediate state was grabbed |
| Pasta never leaves the pot | The water has not been drained, a plate is missing, or the extraction destination is blocked |
| Plate-washing line stops with leftovers | The Picky Eater clearing step is missing or its bin is full |
| Cooker catches fire when demand stops | Downstream storage filled while burnable food stayed on a Danger Hob |
| Only one sauce order works | Another menu branch or final-state filter is incomplete |
The video is a process example, not evidence that every restaurant can be fully automated by ordinary Day 14. Keep manual access until your own full cook–serve–clear–return cycle works.
References
- PlateUp! spaghettiPlateUp! spaghetti
- PlateUp! release15PlateUp! release15
- PlateUp! release14PlateUp! release14
- PlateUp! researchPlateUp! research
- Spaghetti and Picky Eaters automation — HydraBurrito1:14:44–1:15:59, 2:21:55–2:30:48
- PlateUp! cardsPlateUp! cards