Bad, Toxic, or Killer Soup: diagnose and prevent failed cooking

What this troubleshooting guide covers

The current game does not use one generic name for every failed recipe. An invalid pot can finish as Bad Soup, Toxic Soup, or Killer Soup. Those outcomes have different causes, so the useful response is to identify the result, quarantine it, and correct the kitchen process before starting another batch. There is also a named special case: a pot using Bag of Feces as its sole ingredient produces Poop Soup rather than the mixed-input Toxic Soup. It is not a recommended route meal and should be kept out of food storage too.

This page covers failed soup only. For a first successful recipe and kitchen setup, use the beginner cooking workflow. For task-specific buffs, use the buff meal planner. Keeping those jobs separate prevents this page from becoming an unverified recipe dump.

Failure table: identify the result before recovery

The table is a diagnosis tool, not an invitation to test the outcomes. A named failed soup means the batch did not meet the intended recipe. Even if a failed item has hunger or thirst values in a data table, it should not become part of the route-food plan.

The pot-name checkpoint

When a valid recipe is recognized, the pot name changes to the appropriate uncooked dish. If the ingredients do not match a recipe, it remains Unknown Soup until cooking finishes. That is the best moment to stop: remove the pot from heat, check the current recipe, and avoid converting uncertainty into a failed finished item.

Do not add more ingredients simply because the name has not changed. Extra items can move the result from an ordinary failure into the toxic or lethal category.

The prerequisite: solve water first

Cooking level 3 is required for soup. A Cooking Pot or Makeshift Cooking Pot can use clean Water or Antejuice as the liquid base. Tainted Water can be boiled into clean Water, but the current Cooking reference records a four-to-one conversion: 1,000 mL of Tainted Water produces 250 mL of Water.

That loss matters when diagnosing a failed batch. If the group is short on water, repeated attempts can create a second survival problem even when no one drinks the failed soup.

Use this water gate before cooking:

1. Keep the team's drinking reserve outside the recipe area.
2. Purify enough water before beginning the batch.
3. Confirm that the recipe pot contains clean Water or Antejuice.
4. Delay experimentation when the only available liquid is needed for travel.

Water discipline does not make a wrong ingredient set valid, but it prevents a recipe mistake from exhausting the base supply.

Recovery plan after a failed soup

Step 1: stop interaction

Do not consume the result to learn what it does. Read the finished name and use the failure table. In co-op, say the name aloud so another player does not take a portion while the cook is checking storage.

Step 2: move the failed pot out of the serving lane

Place it on a separate surface that is not used for finished route food. Do not leave it beside verified pots or empty bowls. A visible quarantine location is safer than relying on everyone to remember which identical container failed.

Step 3: audit the additions in order

Check four questions:

• Was the exact recipe current for the installed game version?
• Did every ingredient name match, including variants of fish, meat, produce, and processed food?
• Was the total number of additions correct?
• Could a player have selected an adjacent scrap, ammunition, rotten item, or chemical from mixed storage?

If the output was Toxic, Killer, or the single-ingredient Poop Soup, inspect storage placement before checking subtle recipe details. Those outcomes point to waste or another hazardous input, not merely an ordinary near miss.

Step 4: reset the work area

Clear loose items from the stove and adjacent surface. Bring only the exact ingredients for one known recipe into the cooking lane. Refill a clean pot with the correct liquid base. Keep the current Compendium entry or individual item page open while adding items.

Step 5: require recognition before completion

Add ingredients one at a time and watch the pot name. Proceed only after it shows the expected uncooked dish. If it remains Unknown Soup, stop and repeat the audit instead of spending another full cooking cycle.

Step 6: verify one portion, then label the batch

After the named soup finishes, collect a portion with a Soup Bowl and place the remaining pot in the verified-food zone. Store the next recipe set together so the group can reproduce the successful result.

Prevention layout for a shared kitchen

The safest layout makes the wrong action inconvenient.

In co-op, assign one cook for each active pot. Other players can deliver ingredients to the verified container without interacting with the stove. This reduces accidental additions and gives the group one person who can confirm the pot name before the timer completes.

Inventory rules that prevent lethal input

• Never place Metal Scrap, Glass Scrap, Tech Scrap, ammunition, or Leyak Essence in the verified-food container.
• Do not use the kitchen surface as a temporary inventory dump.
• Move Rotten Food and Rotten Fish to a disposal or non-food area immediately.
• Keep similarly shaped items in separate labeled containers.
• Return unused ingredients after one recipe instead of leaving them beside the next pot.

These rules are derived from the documented harmful-input lists. They solve the cause rather than telling players merely to "be careful."

Near-miss recipe discovery is not a production method

The Cooking page notes that some one-ingredient mistakes can reveal a proper recipe in the Compendium when the total ingredient count matches a valid dish. That mechanic can explain why a failed batch added new information. It should not become the normal kitchen strategy.

A production kitchen and an experimentation kitchen have different goals. The production area protects water and route supplies. If a group chooses to test unknown combinations, do so only after survival reserves are secure, away from the serving lane, and with no lethal materials in reach. Never present a failed result as a recommended meal.

Common misdiagnoses

"The stove is broken." If the pot finished with a failed name, the process ran; the ingredient set was the issue. Check recognition before replacing the stove.

"Any food item should produce food." Rotten items and some biological materials appear on the Toxic Soup list. Item category alone does not prove a safe recipe.

"Adding salt will rescue the pot." Salt belongs to several valid recipes, but an extra ingredient does not automatically correct an unknown mixture. Stop and follow the exact current recipe.

"The result is safe because it has portions." Killer Soup can be placed and portioned, yet its current page explicitly says consumption kills the player. Serving mechanics do not establish safety.

"One successful batch proves every variant works." Exact item names matter. Record the successful set and do not substitute a different fish, meat, or produce variant without a verified recipe.

Completion check

The recovery is complete only when:

• The failed output was identified as Bad, Toxic, or Killer Soup, or the single-ingredient Poop Soup special case was recognized separately.
• No one consumed the failed batch to test it.
• Hazardous materials and rotten items were removed from food storage.
• Clean water remains available for drinking and the next controlled attempt.
• The next pot displayed the expected uncooked recipe name before completion.
• Finished route food and failed output occupy different visible zones.
• The successful ingredient set is recorded for repeat use.

If the pot remains Unknown Soup, the correct action is still to stop. Preserving water and ingredients is a successful troubleshooting result; guessing until a named failure appears is not.