The Bakso Malang shift runs on a small core control set — move, interact, serve, restock, and the order board — plus a five-step anomaly loop: pause and timestamp, capture the state, isolate the station, resolve with the matching control, then verify against the shift summary. Most “unusual events” are not random: they fire when the broth counter, the meatball tray count, and the order queue drift out of sync, so watching those three numbers catches the large majority of anomalies before they void a ticket. The guide below lists the controls, the default shift parameters, and the response steps in the order you actually need them.
Core controls and what each one is for
The default bindings are shown below. Every one is remappable in Settings → Controls, and the game’s own tutorial flags the order board as the single most under-used key — it is also the control that resolves more anomalies than any other.
| Action | Keyboard | Gamepad | When it matters |
|---|---|---|---|
| Move | W A S D | Left stick | Constant; slower while carrying a full tray |
| Interact / pick up | E | A / Cross | Bowls, trays, baskets, pot lid |
| Serve bowl | F | RT / R2 | Only registers when the customer’s ticket is active |
| Restock tray | R | X / Square | 1.5 s channel; interrupted if you move |
| Order board | Tab | Y / Triangle | Cancel, re-queue, and inspect stuck tickets |
| Sprint | Shift | LB / L1 | Drains stamina; spills a full bowl |
| Dash | Space | B / Circle | 2 s cooldown; the usual cause of bowl duplication |
| Drop held item | Q | LT / L2 | The fastest way to break a desync |
| Select topping | 1 – 4 | D-pad | Wrong topping fails the ticket silently |
| Pause / log | Esc | Start / Options | Freezes the shift clock — your anomaly timestamp tool |
Default shift parameters worth memorising
Anomalies are easier to spot when you know what “normal” looks like. The values below are the current build’s defaults on standard difficulty; hard mode shortens the clock and customer patience, and co-op scales the order queue upward.
| Parameter | Default | Notes |
|---|---|---|
| Shift length | 12:00 | Hard mode runs 9:00 |
| Broth pot capacity | 40 servings | Refill adds 40 and takes 6 s |
| Meatball tray | 24 slots | 3 meatballs per standard order |
| Noodle baskets | 6 in parallel | 20 s cook time each |
| Order queue cap | 8 tickets | A 9th ticket voids the oldest one |
| Anomaly scan interval | every 45 s | Checks broth, tray, and queue counters |
| Response window | 15 – 25 s | Varies by anomaly type; see table below |
| Customer patience | 90 s | Drops to 60 s on hard |
| Dash cooldown | 2 s | — |
| Restock channel | 1.5 s | Cancels on movement or interaction |
Why the scan interval is the key number
Because the anomaly scan runs on a fixed 45-second cycle, anything you break between scans has up to 45 seconds to compound. Two breaks in the same cycle — say a tray desync plus a stalled noodle basket — stack into a queue failure that costs the whole shift rather than one ticket. If you know you just triggered something, don’t wait for the scan: open the board and clear it yourself.
Anomaly classes, first signs, and fixes
Unusual events fall into a handful of recognisable classes. The first sign is what you will actually see on screen; the response window is how long you have before the affected ticket voids automatically.
| Anomaly | First sign | Typical trigger | Window | Fix |
|---|---|---|---|---|
| Broth drift | Steam stops while 12+ servings remain | Refilling the pot mid-cook | 20 s | Press R at the pot |
| Tray desync | Counter reads 25/24 | Restocking while a serve resolves | 15 s | Q to drop, then R |
| Queue stall | Ticket timer frozen at 0 | Opening the board during a serve | 20 s | Close and reopen the board |
| Phantom customer | Empty seat still holding a ticket | Customer leaves mid-order | 25 s | Cancel the ticket on the board |
| Bowl duplication | Two bowls in one hand | Serve and dash on the same frame | 10 s | Drop both, re-serve one |
| Noodle stall | Basket timer stops advancing | All 6 baskets in use simultaneously | 20 s | Pull one basket, re-add it |
The five-step anomaly response loop
Run these in order. Skipping step 1 is the most common reason players can’t tell whether a fix worked — without a timestamp, the shift summary won’t tell you which ticket was affected.
- Pause and timestamp. Hit Esc the moment something looks wrong. The pause menu freezes the shift clock, which converts a moving problem into a stationary one and gives you the exact second to check against the summary later.
- Capture the state. Note the three counters — broth servings, tray count, queue length. These are the only values the scan checks, and the combination tells you which class you’re in.
- Isolate the station. Stop interacting with the affected station. Repeated E presses on a desynced tray is the fastest way to turn a 15-second fix into a voided queue.
- Resolve with the matching control. Use the fix column above. The board (Tab) resolves more classes than any other single key because it’s the only control that can cancel a ticket outright.
- Verify. Resume, let one full 45-second scan pass, and confirm the counters read normal. If the same anomaly reappears within two scans, it’s a stuck state rather than a transient one — return to the board and cancel the affected ticket manually.
Worked example: the double-broth anomaly
You refill the pot at 3:10 while a bowl is mid-serve. At 3:12 the steam stops with 38 servings showing. Pause (Esc) at 3:12. Counters read broth 38, tray 22/24, queue 5 — one low on the tray but not desynced, so this is broth drift, not tray desync. Don’t touch the tray. Walk to the pot, press R once, and wait for the 6-second refill channel to finish. Resume. At the next 45-second scan the broth counter reads 40 and the queue clears normally. Total cost: about 25 seconds of shift time and one slightly impatient customer, versus a voided ticket and a lost queue slot if you had spammed interact instead.
Control combinations that prevent most anomalies
Prevention is mostly about not overlapping two channel actions. The triggers in the table above share a pattern: two state-changing actions resolving on the same frame.
- Never serve and dash together. The 2-second dash cooldown is longer than the serve animation, so you gain nothing and risk duplication.
- Restock before you serve, not after. The 1.5-second restock channel is interrupted by any interaction, and a partial restock is the direct cause of tray desync.
- Keep one noodle basket free. Running all six at once is the only way to trigger the noodle stall.
- Open the board between orders, never during one. This alone removes the queue stall class entirely.
- Refill broth only when the pot is idle. Broth drift has no other trigger.
Matching your setup to how you actually play
| Your situation | Recommended setup | Why |
|---|---|---|
| First run, solo | 12:00 shift, assist on, board on Tab | You need the full clock to learn the three counters |
| Solo, going for a clean shift | 12:00 shift, assist off, dash unbound | Removes the duplication class entirely |
| Two-player co-op | Split front/back; one player owns the board | Only one player should ever cancel tickets |
| Hard mode | 9:00 shift, 60 s patience, board on a shoulder button | Shorter windows mean you need board access without leaving the sticks |
| Controller only | Move serve off RT to a face button if your triggers are soft | A half-pressed trigger registers as a failed serve and looks like an anomaly |
| Keyboard only | Move restock from R to a key near your movement hand | Cuts the partial-restock desync rate noticeably |
When an anomaly won’t clear
If the same class reappears across two consecutive 45-second scans, you are dealing with a stuck state rather than a transient one. Work through this order: cancel the affected ticket on the board, then drop everything you’re holding (Q), then leave and re-enter the station’s interaction radius. Only if all three fail should you consider ending the shift — restarting resets your progress on the current order queue, and the shift summary will log the restart as a failed shift rather than a completed one.
Keep in mind that default values shift between builds. If a window feels shorter or a capacity feels larger than the numbers above, check the current build’s patch notes before assuming you misread a counter — the scan interval in particular has been adjusted more than once.
Frequently Asked Questions
What is the single most important control for anomaly response?
The order board (Tab by default). It is the only control that can cancel a ticket outright, and it resolves or reveals more anomaly classes than any other key. Players who never open it are effectively limited to four of the six fix paths in the anomaly table.
How long do I have to fix an anomaly before it costs me a ticket?
Response windows run from 10 seconds for bowl duplication up to 25 seconds for a phantom customer, with most classes sitting at 15 to 20 seconds. Because the anomaly scan only fires every 45 seconds, you should treat the window as starting when you first notice the problem, not when the scan reports it.
Can I just restart the shift when something goes wrong?
You can, but the shift summary logs a restart as an incomplete shift rather than a completed one, and your order-queue progress resets. For transient anomalies, working the five-step loop is almost always faster than a full restart, which costs you the entire elapsed shift time.
Does hard mode change the anomaly rules or just the numbers?
It changes the numbers, not the rules. The shift clock drops to 9:00 and customer patience falls to 60 seconds, which compresses every response window in practice even though the stated windows are unchanged. The anomaly classes and their triggers stay identical across difficulties.
Why does my tray counter read 25 out of 24?
That is tray desync, and it almost always comes from restocking while a serve is resolving. Drop whatever you are holding with Q, then run a clean restock with R and let the 1.5-second channel finish without moving. Do not press interact repeatedly — that extends the desync rather than clearing it.
Is the order board pause the same as the pause menu?
No. The board (Tab) shows and edits tickets while the shift clock keeps running, which is why opening it during a serve causes a queue stall. The pause menu (Esc) freezes the clock entirely and is the tool you want for timestamping an anomaly before you start fixing it.
Write Your Review
No reviews yet. Be the first to share your experience!