Check the symptom before changing the city
Hotfix 4 was published on October 18. It adds cancellation of a building-move order and fixes a road-recognition case after free placement. A stuck move, a missing road and an incorrect power preview are different symptoms; record which one you actually see.
First allow the game’s normal update process to finish and note the installed build if displayed. Preserve your existing save. The checks below help narrow a report; they are not a guarantee that a patch repairs an already affected save.
Source: Developer · Hotfix 4
Which published fix matches your problem?
| Symptom | Published change |
|---|---|
| Move stalls after a Peep action is canceled | Hotfix 1, October 16: fixed a blocked resource-fetching case. Hotfix 2 covered an additional case. |
| Generator selection shows an unexpected radius | Hotfix 1: the displayed line now represents power range, rather than pollution range. |
| Power-consuming placement looks valid without a connected generator | Hotfix 3, October 17: corrected misleading green tiles. |
| Research Facility will not move during research | Hotfix 3 explicitly prevents that move while research is active. |
| Need to cancel a move; road not recognized after free placement | Hotfix 4, October 18: cancellation added and road-recognition case fixed. |
Source: Developer · Hotfix 1 · Developer · Hotfix 2 · Developer · Hotfix 3 · Developer · Hotfix 4
A short check without rebuilding everything
- Identify the exact building and current action. Capture the selected building, the destination and any visible requirement or warning.
- For power, compare the generator selection with the destination preview. A radius graphic and a connection requirement answer different questions; do not treat a green tile alone as proof.
- For a move, check whether the current interface offers cancellation. Read any confirmation before applying it, then observe the resulting order state.
- If the symptom remains, stop changing several variables at once. Keep the before-and-after evidence and report the smallest sequence that reproduces it.
One save limitation the developer calls out
Hotfix 3 prevents a Kewa conversation collision, but says saves already stuck in that state remain broken. Its diagnostic is an active Whale Communicator conversation with no choices and no way to leave. Do not describe that patch as a confirmed recovery method for those saves.
Source: Developer · Hotfix 3
Make the next report actionable
Include your platform, installed build, whether the save predates the patch, the building involved and the exact order of actions. State what you expected and what happened instead. Share screenshots through the developer’s linked support or community route, and keep a copy of your original save.
Continue with this game
Sources & scope
This article uses the official and individually identified community references linked below. It is not a hands-on review. Screenshots are credited to their original publishers; they are not evidence that we tested these steps. Game details can change after publication.
- Developer · Hotfix 1 (16 Oct 2026)
- Developer · Hotfix 2 (16 Oct 2026)
- Developer · Hotfix 3 (17 Oct 2026)
- Developer · Hotfix 4 (18 Oct 2026)
- Developer · announcements index
Sources checked: 21 Oct 2026. Read how we use sources and AI assistance.



