Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Browser-local issue worksheet · no save access

Food symptom and build report

Record the panel state before trying a workaround.

Build not recorded · rationing: unknown

Displayed stock: not recorded

No farm observation entered

No symptom recorded

Check whether this platform/build includes the developer's 1.1.6 food fixes before treating an old workaround as current.

Values stay in the current page and clear on reload. The worksheet cannot inspect villagers, stores, farms or saves, and it does not diagnose a bug or contact support.

A version-aware triage order

Two distinct causes can look like the same red hunger indicator. The 1.1.5 developer notes describe intentional rationing behavior; the 1.1.6 notes separately list bug fixes for hunger despite adequate food and farmers not harvesting decayed crops. The order matters: first check your current setting and patch, then follow the live UI. A report written before those patches may describe a resolved defect.

  1. Record the exact platform and build number shown by your game. Do not assume console rollout dates match the Steam patch history.
  2. Open the food-management display and read whether rationing is Auto, On or Off. Update 1.1.5 says active rationing consumes half the food while villagers go hungry and become very unhappy; if that is intentional, turn it off only if your current plan allows it.
  3. Compare the settlement's displayed food stock with the food types your villagers can actually access. A headline total alone does not prove every group has the needed resource available.
  4. Check the farmer/building panel for unharvested or decayed crops and whether the relevant farm is staffed and operating. The developer says the decayed-crop harvesting bug was fixed in 1.1.6; verify your installed branch before copying a workaround.
  5. If the game is older than 1.1.6, check the platform's official update channel and back up a valued save before changing branches. The notes do not promise that a branch switch repairs an existing save.
  6. If the symptoms continue on a build containing the fixes, record rationing state, available stock, crop state and one affected villager, then compare one possible cause at a time. The worksheet below organizes observations; it cannot diagnose your village.
ObservationFirst source-backed checkBoundary
Villagers hungry and mood dropsFood rationing settingOn is intentionally restrictive per 1.1.5 notes
Adequate food but hunger persistsInstalled build and actual accessible stock1.1.6 reports a fix; does not prove every shortage has that cause
Decayed crops remain on farmBuild and farmer panel1.1.6 reports a fix for this specific bug
Issue on console or another branchPlatform rollout and exact build labelSteam patch index may not reflect that platform's rollout

References: Stray Fawn Studio: The Wandering Village Steam announcements and patch notes · The Wandering Village on Steam

Make a reproducible player question

The report card stores only the values you type into this page. Keep observations separate from your theory: 'rationing is On; stock is X; crop is decayed' is more useful than claiming the farm AI is broken.

  1. Enter the platform/build and exact rationing state.
  2. Record the displayed food stock and one visible symptom.
  3. Note whether decayed crops remain and whether the related farm is staffed.
  4. Compare the report with the installed build's official patch note before sharing externally.

References: The Wandering Village Steam Community Discussions

Before you play

  • I recorded the platform and displayed build.
  • I checked rationing before changing farms or storage.
  • I compared the issue with the developer's 1.1.6 fixes.
  • I separated what I observed from the cause I suspect.

Frequently asked questions

Should I always turn rationing off?

Not necessarily. The 1.1.5 notes describe On as an intentional way to stretch reserves at the cost of hunger and unhappiness; decide using your own settlement goals.

Does 1.1.6 prove every food shortage is fixed?

No. It lists two particular bug fixes. It does not replace checking rationing, actual accessible stock or worker/building status.

Can the report card read my save?

No. It only summarizes the text and selections entered in this tab and clears when you reload.

Sources & revision notes

Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

  1. Stray Fawn Studio: The Wandering Village Steam announcements and patch notes (Official)

    Developer-published Steam patch history checked November 7, 2026. The 1.1.5 notes describe the Auto/On/Off food-rationing modes and intentional hunger/unhappiness behavior; 1.1.6 says two food bugs were fixed. Use the newest notes matching the installed branch; interface details can change. No village was tested.

  2. The Wandering Village on Steam (Official)

    Official product listing describes the village-on-Onbu management game and current Steam release information. It is not a full mechanics manual.

  3. The Wandering Village Steam Community Discussions (Community)

    External player-generated discussion posts, not official support or verified GamerWin experiences. Include platform, exact displayed build, rationing setting and observable resource/worker panels; do not post account or private save data.

What changed in this revision

November 7, 2026: first publication. Separated intentional 1.1.5 rationing behavior from two 1.1.6 bug fixes; no village or food shortage was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.