Dungeon Settlers Food, Hunger, Mood, and Energy

When food, hunger, mood, energy, or stress blocks progress, inspect the affected member's current tooltip, then fix the single support loop it identifies—food supply, a room, a work station, or expedition preparation. Do not rely on a fixed food ranking from an older build.

Evidence boundary: Steam confirms food, bedrooms, dining areas, fields, rations, and camping supplies. A community thread contains player observations about specific foods and crops, but those observations are not official values or independently tested site data.

Diagnose the state before changing the base

Read the current interface for the affected member and write down the state, its stated cause, and the last event before it became a problem. This separates a food shortage from an energy, mood, or expedition-duration issue. Fixing the wrong system can consume scarce materials without making the next run safer.

Then test one change at a time. Improve the food or room loop, take a cautious comparable expedition, and record whether the condition changed. If it did not, return to the current tooltip instead of stacking more unrelated upgrades.

Build the support loop in order

Steam describes a settlement with fields, bedrooms, dining areas, food, rations, and camping supplies. Treat these as a connected loop:

1. Secure the basic food or supply source currently shown as missing.
2. Check whether the appropriate room and station are functional.
3. Pack only the expedition supplies that address the next run's stated risk.
4. Set a return threshold before leaving, then compare actual use after returning.

The Dining Room and other room effects should be checked in the in-game Game Guide rather than assumed from a guide table. See Room Upgrades for that verification routine.

Community observations need a retest

Players discussing food and farming have reported finding apples, blueberries, turnips, oats, and jerky in their own runs, with differing accounts of what can be farmed and how it affects mood. Those reports demonstrate a real player question, but they do not establish universal farming rules, recipes, or effects.

If you test one of these reports, capture the build, item tooltip, source, member state before use, and observed result. Add the result to a versioned note only after it can be repeated. This is more useful to players than turning one forum post into a false certainty.

Use Resources & Camping for run supplies and Base Expansion only when space—not an unmet member need—is the actual constraint.

Use a before-and-after log

State problems are especially easy to misread because several systems can worsen during the same expedition. Before changing a meal, room, or supply plan, record the member's visible condition, the current build and difficulty, what they consumed or did, and the point in the run where the state changed. Repeat the same kind of run after one controlled change. The comparison is more valuable than a memory of a successful or unsuccessful attempt.

Record	Why it matters
Member and visible state	Keeps one recruit's trait or condition from being generalized to everyone
Build and difficulty	Lets a future update be recognized as a possible cause
Food, room, or supply change	Shows what was actually tested
Expedition length and return point	Distinguishes an endurance issue from a food issue
Result	Records what changed, what did not, and what needs another test

This log is also useful when reporting a possible bug or a misleading tooltip. A statement such as “food does not work” is difficult to investigate. A record of the current item description, member state before and after, and the build lets another player or the developer reproduce the situation.

Separate settlement needs from expedition insurance

Food produced or stored at the settlement and supplies brought underground answer related but different questions. Settlement support is about keeping the people and work loop functional between runs. Expedition insurance is about the risks of a particular departure: expected duration, damage, uncertainty, and the team's chosen retreat threshold. Do not drain the settlement's support loop merely to make every run longer, and do not assume a full settlement stockpile makes an underprepared party safe underground.

Set a conservative return point before leaving. When the party reaches it, compare the supplies used with the reason for turning back. If a state worsened before the threshold, inspect the relevant tooltip and support loop. If supplies stayed unused, decide whether they were useful insurance or an unnecessary burden. This lets the player adjust one assumption at a time rather than oscillating between hoarding and overextending.

What to publish later

A future food database should be built from current tooltips and repeatable tests, not a single forum claim. Each entry needs its source, current build, stated effect, observed result, and a link to the room or production condition that makes it relevant. Until then, this page is designed to solve the first problem: identify which loop is failing and verify the next action without pretending one meal is always best.

Keep the language of the interface intact

When an effect is unclear, copy its current tooltip wording into the note before translating it into a strategy decision. “Mood,” “stress,” “hunger,” and “energy” may be related in play but are not automatically interchangeable. Preserving the displayed term prevents a guide from recommending the wrong fix and makes it easier to identify a localization or tooltip change after a patch.

Sources and review boundary

• Dungeon Settlers on Steam — official food, room, field, ration, and camping-supply systems; reviewed September 8, 2026.
• Food and farming discussion — player observations used to identify questions for testing, not as confirmed values.
• Room Upgrades — current in-game verification process for room requirements.