Hurry Curry!

Overview

Orders pile onto the rail the moment a customer walks in, and the whole kitchen leans on how fast a crew can turn each ticket into a plated meal. Hurry Curry! is a free, open-source cooperative cooking game built in Godot 4.5 with a Rust WebSocket server, licensed under the AGPL-3.0 and developed on Codeberg by the metamuffin project and contributors. Players run a restaurant together: one chef approaches a customer to take the order, then the team chops, cooks, bakes, sears and combines ingredients at the kitchen stations until the requested dish is ready to serve. The pressure is the patience timer, because leave a meal on the stove too long and it burns, or drag your feet and the customer walks out. What sets it apart from a generic cooking loop is the variety underneath: 26 recipes, more than 20 restaurant layouts, some split by counters that block your path and some linked by conveyor belts that carry dishes for you, and the fastest complete runs recorded per map. Bot teammates fill empty slots so a solo player is never stuck, which makes the same Overcooked-style chaos work whether you bring a group or play alone.

How to Play

Install the client, connect to a public server or host your own, then pick a map, with the in-game list recommending Sophomore for solo play. Movement is WASD and you aim the camera with the mouse; the left and right mouse buttons, with J, K and L as keyboard alternates, are the interact keys that pick up ingredients, chop at a cutting board, set a pan on a stove, or hand over a finished plate. Hold Shift to boost between stations, limited by a stamina bar, and tap Ctrl to slow to a precise walk. A round runs from the first customer arriving to the last ticket cleared: read the order on the rail, fetch and process each component, plate the meal, and deliver it before the patience meter empties.

Tips & Strategy

Split the kitchen before tickets stack up. With two or more chefs, station one near the cutting boards and another at the stoves so chopping and cooking run in parallel instead of one cook walking the whole loop every single order. Watch the patience meters, not just the current ticket: a customer almost out of patience should leapfrog the queue, because a walk-out costs more than a slightly late fresh dish. Never leave a pan on the heat while you run an errand, since burned food wastes both the ingredients and the time you already spent. On conveyor-belt layouts, drop a finished plate on the belt and let it travel while you start the next order instead of carrying everything by hand. Save the boost for long crossings such as fetching ingredients from crates or reaching an isolated oven, because stamina regenerates slowly and wasted sprints leave you walking. For solo runs, hand the repetitive prep work to the bots and keep the plating and serving for yourself, where timing matters most.