Best opened when
Use this when smoother loops, prep, or comfort would clearly save more time across repeated sessions.
Efficiency
Cook one usable batch, inspect its effects, and reserve ingredients for the next trip.
Loop answer
Craft a Cooking Pot at a Basic Workbench with 2 Wood and 4 Copper Bars , place it, and put a valid food ingredient into each of its two input slots . Collect the finished dish from the output.
Best opened when
Use this when smoother loops, prep, or comfort would clearly save more time across repeated sessions.
Use another page when
Comfort upgrades matter more after the save already knows where it is going.
What to loop or open next
How to Get Scarlet Ore in Core Keeper. Go here when better comfort now lets you chase one targeted material cleanly.
Craft a Cooking Pot at a Basic Workbench with 2 Wood and 4 Copper Bars, place it, and put a valid food ingredient into each of its two input slots. Collect the finished dish from the output. The Cooking Pot recipe and Cooking instructions document this process; the latter lists ten seconds per ingredient pair.
For an accessible first meal, try Mushroom + Heart Berry for recovery and temporary maximum health, or Heart Berry + Bomb Pepper when movement matters. Cook a few meals before committing the full pantry, then inspect the finished tooltip. Ingredient effects can change when cooked.
Place the pot near your ingredient storage and open its interface. Put one ingredient in the first input and one in the second; reversing the order does not change the recipe. Both slots need an ingredient. These operating rules come from the Cooking reference.
For your first batch, my recommendation is three pairs. Collect the first dish and read it before adding more. This small batch is a convenience choice: it catches a mistaken ingredient selection without consuming everything you meant to save.
If nothing happens, inspect the two inputs before rebuilding the station. If a dish already exists in the output, collect it and check that both inputs still have valid supplies for another pair. Do not extend a power circuit to this pot simply because nearby incubators and drills need electricity; the documented cooking workflow starts with ingredients in the pot.
These are practical starting choices, not a ranking of every food in the game. The effects below refer to ordinary ingredients and regular-quality cooked results before talent adjustments.
| Pair | What the documented ingredients contribute | When I would choose it |
|---|---|---|
| Mushroom + Heart Berry | Mushroom contributes 4.2 health per second for 20 seconds; Heart Berry adds temporary maximum health | An everyday mining or exploration meal |
| Heart Berry + Bomb Pepper | Heart Berry contributes 25 maximum health for 10 minutes; Pepper contributes 21% movement speed for 1 minute | A trip where retreat and travel matter |
| Mushroom + Blue Cave Guppy | Mushroom recovery plus the Guppy's listed 16 magic barrier for 10 minutes | Trying a fish meal when you already have this catch |
Ingredient references: Mushroom, temporary maximum-health foods, Bomb Pepper, and Blue Cave Guppy.
Choose based on what you can replace. If mushrooms are scarce but your Berry and Pepper supply is healthy, the second pair may be easier to sustain. If fish are already waiting in storage, use them deliberately instead of treating every catch as a rare ingredient that must never be spent.
The fish example needs a source caution: the Cooking overview still shows an older Blue Cave Guppy dodge effect, while the current item entry lists magic barrier. This guide follows the item-specific entry for the table, but your finished in-game tooltip should decide what that meal does in your installed version. Do not farm the fish specifically for the old dodge example.
Bomb Pepper is the clearest early warning. Its item entry lists a health loss when eaten raw and movement speed when used as a cooking ingredient. Eating it directly is not equivalent to eating a Pepper dish.
Before packing a meal, inspect three things on the finished item:
Do not read only the dish name. Two meals can sound useful while solving different problems, and a buff icon by itself does not tell you that every effect from the meal is still running.
The Cooking reference says normal overlapping ingredient effects use the higher value when forming a dish; they are not added together.
For example, Mushroom and Heart Berry both contribute health regeneration, but this does not mean their two regeneration numbers should be summed. The point of the pair is to combine the Mushroom's recovery role with the Berry's temporary health bonus.
That rule describes creating a dish. Be careful about extending it into a universal rule for eating several dishes. The Max health reference specifically warns that a later same-type food buff can overwrite an earlier one even if the earlier buff was stronger. Do not assume the game will always preserve your best meal.
For a simple early loadout, carry one dependable everyday dish and add a specialist meal only for a named missing effect. If you use several foods, check their effects and the order you consume them before spending rare ingredients.
A regular Heart Berry and Bomb Pepper meal illustrates the problem: the documented Berry maximum-health bonus lasts ten minutes, while the Pepper movement effect lasts one minute. The health benefit still being active does not prove the speed benefit survived the walk to the boss.
My preparation order is to travel first, reach the safe staging area, and check the short effect immediately before the dangerous section. Bring a small refresh supply if the trip requires it. Do not eat every specialist meal at the front door of your base and assume all effects will last until combat.
Talents and food quality can alter displayed results, so use the durations on your own meal. If you need a full combat food plan, continue to boss-fight food; for repeated travel, use the travel food guide.
| Kitchen problem | Change for the next session |
|---|---|
| Ingredients exist but no meals get packed | Keep the everyday pair beside the pot and collect the batch before departure |
| Meals occupy too many inventory slots | Repeat the same pair instead of cooking every leftover combination |
| Fish never get used | Assign one catch to a planned meal rather than leaving all fish in reserve |
| Cooking consumes emergency supplies | Keep a separate reserve before loading large stacks into the pot |
| Meals seem ineffective | Check the finished tooltip and effect duration at the moment you need the bonus |
The Cooking reference notes that stack compatibility depends on identical ingredients, with quality creating further divisions. Repeating one pair is therefore a useful storage habit, not just a recipe preference.
For the next trip, I would put one ready meal stack beside the exit supplies and leave experimental dishes in the kitchen. After returning, restock the pair that was actually used. Expand the crop or fishing supply only when that meal runs short; the food loop planner handles that supply decision.
Choose the meal purpose first, reserve ingredients for replanting or another needed use, and cook one small batch. Inspect the result and place it in the output chest used for the next expedition. If ingredients exist but the batch is slow to prepare, correct the input and output storage before increasing the crop area. Use the Meal Purpose Guide when the meal job is still undecided.
I recommend three pairs while you are choosing a repeatable meal. That is enough to pack a small stack without committing the entire ingredient supply; it is a planning suggestion, not a recipe requirement.
Keep a reserve for a planned attempt, but give the rest a purpose. If a common catch makes an everyday meal easier to replace, using it now may help more than keeping an unsorted fish chest indefinitely.
Treat them as different supplies. The Consumables reference lists Healing Potion as an immediate percentage-health restoration, whereas the Mushroom cooking effect is recovery over time. A short recovery meal is not the same emergency response.
The accessible overview and item entry disagree. The current item entry lists magic barrier. Read your cooked result rather than relying on an older recipe example.
Reviewed November 10, 2026 using the linked community-maintained station, cooking, ingredient, and consumable entries. Recipes and example values are reference-backed; batch size, meal selection, and pantry organization are editorial advice. This review did not include an in-game cooking test. Values may differ with food quality, talents, mods, or installed version, and the Blue Cave Guppy discrepancy remains a source limitation.
The wiki checks used accessible search-index excerpts because direct page requests were blocked during this review.
The retained image is an editorial kitchen schematic, not a gameplay capture or evidence of testing.
Source review. Updated by Core Keeper Editorial Desk.
These notes describe source review or editorial analysis. No documented gameplay test is attached to this page.
November 10, 2026: Merged the separate cooking recheck into a concrete one-batch preparation and storage comparison. This pass reorganized editorial workflow advice, not a new mechanic benchmark or gameplay test. Previous review context: Reviewed November 10, 2026 against Cooking Pot, Cooking, Mushroom, Bomb Pepper, Blue Cave Guppy, Max health, and Consumables community wiki entries. The Cooking overview's old Blue Cave Guppy dodge example conflicts with the current item entry's magic barrier; this guide flags that conflict and avoids carrying the old value forward. Meal selection and kitchen organization are editorial advice, not a fresh gameplay test. The linked facts come from a player-maintained reference for this evergreen page; the route order, stop rules, and recommendations remain independent editorial guidance.
These are editing and source-review notes. A revision entry alone is not a gameplay test record.
Merged the separate cooking recheck into a concrete one-batch preparation and storage comparison.
Repeat-loop reviews / Merged the separate cooking recheck into a concrete one-batch preparation and storage comparison; use the direct steps for the named task.Merged the separate cooking recheck into a concrete one-batch preparation and storage comparison.
Editorial consolidation; no gameplay testAdded Cooking Pot cost, input and output steps, early meal choices, duplicate-effect cautions, timer differences, and the Blue Cave Guppy reference discrepancy.
Source review; no timed cooking or combat testEarlier revision organized food by session goal; this revision supplies the missing recipes and operating details.
Editorial historyCooking, Farming Loop, Fishing, and Money update pages now include small-batch tests, harvest-payoff audits, first-catch value checks, and clearer rules for when readers should leave for a direct support guide.
Cooking, farming, fishing, and money pages received tighter support-loop checksAncient Gemstone, Cooking, Money, and Galaxite pages now include route audits, storage habits, small-batch tests, and upgrade planning so players can judge whether a loop actually solved the current problem.
Material, cooking, and money pages received route-quality checksSession steps
Before you start
Open storage space
Keep the loop repeatable
Cut down return time
Expected outcome
Cook one usable batch, inspect its effects, and reserve ingredients for the next trip.
Cooking system visual
Cooking pages feel more trustworthy when they show the routine clearly: sort ingredients, batch cook before a route, and carry food that answers the next need.
Reference image: Official gameplay screenshot with a separate editor note
What the editor note helps you verify: In your own save, verify the key moment you should recognize before acting on the guide.
What this visual section is backing up: Merged the separate cooking recheck into a concrete one-batch preparation and storage comparison; use the direct steps for the named task.
The lead image is an official Core Keeper screenshot from Fireshine Games. The supporting route notes and decision sketches stay labeled as editor-made reference notes in the gallery so the page does not present them as raw in-game captures.
Helpful route cue
Use one short example that proves the guide route or decision rather than a long unedited session.
Screenshot to include
Show the one image that helps the player recognize the right moment or location immediately.
Why this matters
Clear screenshots make a guide feel confirmed in practice, not just described.
The strongest cooking panel shows ingredient sorting, one clean batch-cook sequence, and the route-ready loadout that follows from it.
| Step | Do this | Why it helps |
|---|---|---|
| Ingredient order | Makes cooking faster to repeat | Fish and crops already have predictable storage spots |
| Batch timing | Protects session flow | Food gets cooked before bosses or long routes, not after a failure |
| Food purpose | Keeps meals relevant | You know whether the next food needs healing, armor, speed, or boss support |