Demo Updates: What Changed Through 0.9.18

Which update should your instructions match?

Use Demo 0.9.18 for the latest verified interface in this November 6 review. Older patches still establish particular mechanics, but their menus or problem reports may no longer match your installed build. A patch summary is not proof that every earlier bug is present, or that an unmentioned mechanic has been redesigned.

The November 3 announcement refreshes People, Work, Research and several other screens. Build combines Orders, Buildings, Blocks and Objects; individual construction, mining and farming orders can be inspected and canceled. Supported blocks and objects can be cloned with their settings. Start with the controls reference when an older screenshot is misleading.

Which changes most affect an existing settlement?

Food age, worker choices and storage handling deserve separate checks because older advice can produce the wrong diagnosis. The table records dated official announcements rather than a full untested changelog. Dates are publication dates in UTC; a Steam display using another timezone can show a different local day for late-night updates.

The 0.9.17.2 notes also release automatic plant-clearing work when a project is canceled. That is narrower than promising a refund for every previously installed building material. Keep deconstruction and order cancellation distinct.

Why is the food update particularly important?

The 0.9.17.1 batch system makes remaining age different from the amount of food you own. A single fresh cooked meal and seventy equally fresh meals share the same six-game-day maximum in ideal storage. Moving, splitting, merging or saving does not restart that age, and other foods have their own lifetimes.

The 0.9.17.1 announcement is explicit: cool storage and the Quartermaster help prevent accelerated aging, but do not extend a food beyond its maximum shelf life. Use food storage and spoilage for a practical check instead of multiplying six days by stack size.

What should you record if a problem survives an update?

Record the game version, operating system, reproducible steps and a screenshot or short video when possible. The developer requested those details in 0.9.15. Include what you expected and what actually happened; an older community symptom alone does not establish the cause of a current failure.

For example, the older farming discussion reports a retained one-cell selection, followed by developer acknowledgement. The newer interface announcement does not prove that symptom is still present. Follow the farming diagnosis with its version boundary. For current release and demo limits, use Demo versus full game; no later patch or launch date is invented here.