When the station stops producing new families, the empty house is usually the least useful clue. Arrivals depend on a town-wide happiness gate, while the happiness behind that gate depends on local coverage, staffed services, warehouse transport, class-appropriate jobs, and family placement. Adding more homes can increase demand without fixing any of those systems.
Freeze expansion and take one snapshot: current build, average happiness, weakest happiness category, unassigned families at the station, empty labour slots, warehouse warnings, and the last district you added. This recovery tree is current to Town to City v1.0.4 on August 23, 2026. It favors what the current UI can prove over old fixed capacities or bonus percentages.
Start at the station, then move one layer upstream
Use the first matching row. Do not perform every fix at once.
| Station or housing state | First inspection | Do not do yet |
|---|---|---|
| A family is waiting with a house icon | Open the family card, read its class and preference, then assign a suitable empty home | Build another random house |
| No family is waiting and average happiness is below the arrival line | Open the happiness breakdown and select the weakest category | Add population or a duplicate service |
| Average looks healthy but arrivals do not resume | Check the current objective, unassigned households, residence class, and whether the average is stable after a service cycle | Assume the station is permanently bugged |
| Houses complain despite a nearby shop | Open the shop: worker, warehouse link, service coverage, and active connection | Move every building together |
| Warnings appeared after a save was loaded | Check the game build and one customized house/shop connection | Recreate the entire road network |
The supplied campaign and troubleshooting references consistently use 60% as the arrival boundary. Treat the number displayed by your current happiness panel as the final authority, but use the same logic: the station resumes only after the town-wide condition is actually restored, not when you place a building that might restore it later.
If happiness is red, repair the named category
Happiness is not one interchangeable resource. Food, apparel, leisure, housewares, Public Service, home decoration, work decoration, density, luxury, and tax pressure require different actions. Read the lowest category and click into the class or household that is pulling it down.
- Food: verify an appropriate food building, its worker, warehouse or crop supply, and actual household coverage.
- Apparel: provide the apparel service unlocked for the stage; more food cannot substitute.
- Leisure: add or repair leisure coverage in the affected district, not in the visually central plaza by habit.
- Housewares or Public Service: use the category-specific buildings available to the current class and stage.
- Home decoration: decorate the residential influence area shown by the selected home.
- Work decoration: decorate the worker’s actual workplace area; a garden around the house is the wrong location.
- Density: stop inserting housing into the same small block; create breathing room or a supported second cluster.
- Luxury or class pressure: inspect the Artisan or Bourgeoisie panel rather than averaging it together with normal residents.
- Taxes: lower or rebalance the policy before buying a service that does not address the penalty.
After one targeted change, wait for the affected household and the town average to update. If the named category improves but the average stays below the line, move to the next weakest category. If the category does not move at all, the new building is probably unstaffed, unsupplied, outside coverage, or the wrong type.
A stage upgrade can expose a need that the old block never covered
A district that was healthy before an upgrade can turn yellow without any road being broken. Later stages introduce apparel, leisure, housewares, Public Service, higher-class luxury, and tourism requirements. Compare the happiness categories visible before and after the upgrade. The newest red line is often the missing system.
This is why you should not upgrade with every worker already committed. Keep enough labour or a safe reassignment ready for the next service. The campaign stage roadmap identifies the class and system transitions without treating Early Access numbers as permanent.
A service is real only when four readbacks agree
Physical proximity is not proof of service. A stall beside a home can still do nothing. Check four readbacks in order:
- Worker: the service has an eligible resident assigned and is not showing an empty-labour state.
- Supply: the warehouse or crop chain can deliver the good the service uses.
- Connection: the road and configured link reach the intended shop or home.
- Coverage: the selected household panel actually recognizes the service.
Stop at the first failed readback. If there is no worker, moving the building is noise. If there is a worker but no supply, another decorative plaza is noise. If supply reaches the shop but the household does not recognize it, then inspect coverage, building type, and connection preference.
Duplicate buildings are useful when a second district needs its own local service. They do not automatically stack benefit for the same homes. Before placing a duplicate, select the underserved household and confirm that it lacks this building type. If the first building already covers the household, fix staffing or capacity instead.
Recover workers without creating another demand loop
“Not enough workers” describes a result, not a cause. The worker may be assigned to research, a low-priority duplicate, an underused service, or a job reserved for another class. A new house can add labour, but it also adds another family with needs. Reassign first.
Use this temporary rescue order:
- Keep the food service that supports the affected residents staffed.
- Keep the warehouse or granary route that supplies that service staffed.
- Staff the building that repairs the current red happiness category.
- Maintain only the research worker needed for an immediate blocking unlock.
- Pause or empty decorative duplicates and future-stage services that are not serving an active need.
Run one service cycle. If happiness and arrivals recover, the town was labour-starved rather than housing-starved. Add new residents in a small, supported cluster only after the recovered services have spare capacity. If no worker can take the job, check the required class; an apparently large normal-worker pool may not staff an Artisan, Bourgeoisie, or other class-specific position.
Research is the safest first place to borrow labour
Research produces future options. Food and transport preserve the people who will use those options. When an early town is stuck, temporarily move labour out of the Research Center, repair the operating chain, and return the worker after the happiness average is stable. Do not cancel a nearly completed critical unlock without checking its progress; the aim is a controlled reassignment, not a permanent research freeze.
Trace a warehouse warning from the shop backward
When a shop cannot sell or a warehouse cannot transport, begin with the failing shop. Identify the good or service it needs, the warehouse intended to supply it, and the road between them. Then open the warehouse and inspect its worker slots, configured connections, and current workload.
| Warehouse symptom | Discriminating check | Targeted response |
|---|---|---|
| No path or station connection | Follow the road continuously from station through warehouse to shop | Repair the broken or nonconnecting segment |
| Warehouse has no transport labour | Open its worker panel | Reassign an eligible worker before changing layout |
| One distant district is underserved | Compare connection lines and travel area for near versus far shops | Build a local warehouse only after the distance edge is proven |
| One warehouse is saturated | Observe active connections and a persistent queue while routes remain valid | Add workers, an applicable upgrade, or split the zone |
| A crop-powered building lacks input | Check the crop, granary, and consumer recipe | Use the farming chain; an ordinary warehouse may not own the missing step |
Do not place a large warehouse over a broken road and call the warning fixed. Scale solves a capacity ceiling; it cannot create a valid path or worker. The success signal is the failing shop receiving supply and the affected household recognizing service, not the warning disappearing from a different building.
For Fontebrac shortages, follow the crop, granary, and Farm Point guide. It keeps agricultural transport separate from the normal town warehouse network.
Family traits turn “nearby” into a placement test
A family preference can raise or lower its happiness independently of general service coverage. The supplied community trait reference describes homes that prefer water, cliffs, trees, flowers, light, nearby services, particular residence classes, farm features, pets, solitude, crowds, or a number of floors. It was last updated before 1.0, so do not copy its numerical bonus ranges into a current plan.
Use the family panel as an instrument:
- Select the family before assigning a home.
- Read the exact current trait and required object or condition.
- Reveal the placement or influence radius when the UI provides it.
- Move the family to a matching empty home, or move/add the matching feature.
- Wait for the trait readback to change before placing more copies.
Some conditions conflict. A family that wants solitude should not be placed inside the dense block created for a crowd-loving household. A single-floor preference can conflict with a plan to solve land pressure by upgrading every home. Class residences are not cosmetic: place Artisans and Bourgeoisie in the housing intended for them when their current card requires it.
Match difficult families before expanding. One poorly placed household may be cheap to move; a whole district built around the wrong assumption is expensive to untangle.
Use a controlled district test before changing the whole city
If the cause remains unclear, choose one affected home and make it the test case. Record its needs, recognized services, trait, work location, and current happiness. Then perform one change only:
- assign one missing worker;
- repair one road segment;
- connect one warehouse to one shop;
- move one service inside real coverage;
- add the exact decoration category around the relevant home or workplace;
- move the household to a home that fits its trait.
If the household readback improves, repeat the proven change where the same failure exists. If it does not, reverse it and move to the next checkpoint. This preserves evidence. Rebuilding the district, moving three shops, changing taxes, and adding workers in one action may recover the average, but it will not tell you which condition was responsible.
Save/load problems have a current patch boundary
The official v1.0.4 notes fixed customized connection preferences for houses and shops being reset when a game was loaded. If the visible links change after loading:
- record the version shown by the client;
- update to v1.0.4 or newer before applying an old workaround;
- make a separate save;
- customize one house or shop connection;
- reload and verify that exact preference;
- only then rebuild broader connection preferences.
If the preference still resets on the current build, capture the save, building names, the connection before and after load, and a minimal reproduction. Do not label every warehouse failure as this bug. A zero-worker building, disconnected road, unsupported shop, or out-of-range district can produce a similar symptom without any save fault.
Do not declare recovery until arrivals and services both hold
The station producing one family is an early success signal, not the end of the test. Assign that family to a suitable home, then watch another service cycle. The recovered town should meet four conditions:
- average happiness remains above the current arrival boundary;
- the newly occupied home recognizes its intended services;
- essential shops, warehouses, or granaries retain workers and supply;
- no older class or district falls red because labour was borrowed for the rescue.
Only then add another housing cluster or resume research staffing. If the town relapses immediately, the rescue moved the shortage rather than removing it. Compare the new weakest category and repeat the tree from that signal.
Evidence used for this recovery tree
The official Steam listing confirms the current class, citizen-management, worker-assignment, research, connected-town, farming, and tourism systems. The official v1.0.4 announcement supplies the saved-connection fix. The official publisher page independently describes the worker, Artisan, Bourgeoisie, amenity, request, farming, and tourism scope.
The supplied beginner, happiness, workers, warehouse, farming, stage, and citizen-trait references were readable and used to build the diagnostic branches. Community bonus percentages, old capacities, fixed prices, and unverified post-1.0 behavior were not adopted. Success is always defined by a live household, building, warehouse, happiness, and station readback in the current client.