One More Run Guides

Starter guides

Chef Knight Guides

Chef Knight is a cozy fantasy incremental game about pushing into dungeons, turning monster drops into ingredients, cooking meals, selling dishes, and reinvesting profit into upgrades. Start here if your run feels busy but your kitchen, sales, and upgrade timing are not actually moving the next dungeon push forward.

Beginner guide Route reference Common mistakes Ingredient flow Customer flow Version watch
Official Steam page

Start here

Start with these Chef Knight guides

Beginner

Beginner Guide

Learn the dungeon, ingredient, kitchen, selling, and upgrade loop without wasting early money on the wrong bottleneck.

 Reference

Route Reference

Use one table to decide whether the next fix belongs to dungeon supply, ingredient flow, cooking output, customer flow, selling speed, money timing, or upgrades.

 Kitchen

Ingredients and Cooking Flow Guide

Turn monster drops into meals without creating ingredient backlogs, selling delays, or upgrades that miss the real clog.

 Customers

Customer Flow and Selling Speed Guide

Fix cooked dish backlogs, slow sales, customer-side delays, and upgrade timing when the shop is the real money gate.

 Routes

Dungeon Route Guide

Decide when to farm safely, when to push deeper, and when the kitchen or selling side needs to catch up first.

 Upgrades

Upgrade Priority Guide

Decide whether the next spend should improve fighting, cooking throughput, selling speed, or the next dungeon push.

 Money

Money and Selling Guide

Find the income bottleneck between dungeon drops, cooking conversion, dish value, customer flow, and upgrade timing.

 Mistakes

Common Mistakes Guide

Diagnose slow loops, ingredient backlogs, weak sales, wrong upgrades, and depth pushes that look better than they are.

 Launch week

Launch Week Impact Guide

Check dungeon routes, ingredient flow, cooking output, customer selling speed, money timing, upgrades, and localization issues after launch.

 Updates

Version Watch

Use a patch-impact checklist to decide which Chef Knight guide needs retesting after future dungeon, kitchen, counter, money, or upgrade changes.

Core loop

Start with the loop, not one stat

Chef Knight is not only about fighting faster. The run improves when dungeon depth, ingredient supply, cooking output, selling income, and upgrades reinforce each other. If one layer races ahead while another layer stalls, the next loop usually feels worse than it should.

  1. Push only as deep as your current damage, route safety, and kitchen conversion can support.
  2. Turn drops into meals before judging whether the dungeon route was worth it.
  3. Spend upgrades on the layer that is blocking the next full loop.
  4. Watch customer flow, selling speed, and cooking throughput before assuming combat is the only bottleneck.
  5. Use the Common Mistakes Guide when a loop feels busy but the next upgrade still arrives too late.

Which Chef Knight guide should you read first?

Pick the page by the loop that actually failed

Player situationOpen this firstWhy it helps
You clear the dungeon but the kitchen still waits.Ingredients and Cooking FlowIt checks whether the route is bringing repeatable ingredients the kitchen can use.
Meals exist, but money arrives too slowly.Customer Flow and Selling SpeedIt moves the diagnosis from cooking output to counter throughput and sales timing.
You can buy something, but every upgrade feels only partly useful.Upgrade Priority GuideIt forces the next spend to name one bottleneck instead of spreading money everywhere.
A deeper route is available, but the current loop is not clean.Dungeon Route GuideIt separates safe farming, useful pushing, and greedy depth that only creates kitchen debt.
The whole loop feels busy but progress is slow.Route ReferenceIt reads the full chain from dungeon drops to sold meals before you buy another fix.

Spend Gate

Do not buy the next upgrade until the loop names the bottleneck

A Chef Knight upgrade is only good if it moves the slowest part of the current loop. After one familiar dungeon run, ask what waited longest: useful drops, cooking output, counter movement, actual money, or the next route push. Buy for that layer first.

If the answer changes every loop, do not chase a bigger plan yet. Repeat a comparable run, watch where the jam moves, then spend once the same failure appears twice.

  1. Dungeon waits: improve route safety or ingredient targeting.
  2. Kitchen waits: fix ingredient conversion before pushing deeper.
  3. Counter waits: improve customer flow or selling speed before cooking more.
  4. Money waits: check dish value and upgrade timing, not just raw speed.

Reader route

Recommended reading order

Open first: Beginner Guide. Start with Beginner Guide, then Dungeon Route, then Ingredients and Cooking Flow once the kitchen starts lagging behind your dungeon push.

Common first mistake: pushing deeper for ingredients before sales speed and upgrades can turn them into progress.

Patch caution: Early builds can change prices, recipes, and dungeon rewards; read current official context before treating one loop as solved forever.

Source context: Use the official links on this page for store or developer context; the guides here turn that public context into safer route decisions for Chef Knight players.