Go-Go Town Expansion & Legacy Save Check

Open the Mayor phone and read the exact Rank Challenge, quest, or boundary requirement first. A generic feeling that the town is “big enough” is not a progression signal. The phone tells you which pressure is actually blocking the next step; the first district then becomes the comparison line for whatever changes after the purchase.

Before spending on a remote area, follow one item from a valid source through processing, storage, delivery, and the shop. Also follow one Townie from home to job and back. You do not need every route to be perfect, but you do need one complete loop whose failure point is visible when another district adds distance.

Keep a little room around the proven supply spine. A packed street can look efficient while leaving nowhere to move a Depot, shorten a Courier route, or add service coverage. The useful preparation is reversible space and a named owner for the next test, not decorative completion.

• Read the phoneUse the named Rank, quest, or boundary requirement instead of a town-size guess.
• Prove one loopSource → processor → storage → delivery → shop must be visible before scaling.
• Leave roomKeep the supply spine and one service lane adjustable after the boundary opens.

Decide what the new area is meant to solve: a visitor desire, a resource input, an expansion gate, or a shortcut. A district that simultaneously adds housing, a commercial street, a new recipe, and a remote service route produces too many new variables to diagnose when the original town slows down.

Name the first endpoint before placing buildings. If the purpose is supply, identify the output crate and its next processor or shop. If it is exploration, identify the return landmark and the service coverage the route will need. If it is tourism, connect one attraction or shop to the arrival path before spreading visitors across several empty streets.

Let one complete operating period pass with the new purpose active. A successful purchase screen is not proof that the district works; the proof is a stock handoff, visitor route, worker cycle, or return path that survives without constant manual rescue.

• One purposeChoose supply, tourism, exploration, or a named Rank response—not all four.
• One endpointName where the output, visitor, worker, or return route must finish.
• One cycleJudge the district after a complete handoff or busy period, not after placement.

Start at the symptom that changed in the original district. If the shop empties, inspect the source, pickup, travel, and counter in that order. If workers idle, check whether a zone still covers live nodes and whether the output crate has space. If streets become dirty or buildings need repeated rescue, look for the assets that moved outside practical Maintenance reach.

Compare the old and new districts by one shared link. A Courier may be driving correctly while the destination is now too far away; a worker may still be assigned while the new return leg consumes the work cycle; a remote service point may exist while the original street no longer has coverage. Correct the first broken link before adding a second vehicle, worker, or shop.

If the new area cannot operate without weakening the baseline, pause the expansion rather than deleting the working town. Move one endpoint back, keep the new parcel as a test area, and record the exact pressure that still needs its own supply or service route. That is a useful recovery state, not a failed save.

• Start at the symptomTrace the changed shop, worker, route, or service loop from its first handoff.
• Find the shared linkA correct assignment can still fail when distance, capacity, or coverage changed.
• Protect the baselineMove one endpoint or pause the new purpose before adding more capacity.

Back up the old save and keep the legacy handoff available before making a large conversion or rebuild. The first return session should answer three small questions: does the phone show the expected challenge, does the first shop still receive a complete route, and can the town survive one co-op or solo operating cycle without a new rescue pattern?

Use the current 1.0 patch checks to choose what to retest. Fishing timers, crafting prompts, Garbird pressure, imports, train routes, and co-op stability are better targets than a full-town rebuild because each one can be compared against the old baseline. If the behavior differs, record the changed link before deciding that the whole save is unusable.

Creative Mode is a separate experiment. It is useful for testing roads, layouts, and blueprints without normal economy pressure, but a layout that works there does not prove that workers, stock, maintenance, and expansion costs work in the economic save. Return to the baseline town before making the final expansion decision.

• Protect firstKeep the old copy untouched while the current phone and first shop are checked.
• Retest one signalChoose a patch-sensitive loop such as fishing, imports, cleanup, or co-op stability.
• Separate sandboxCreative Mode proves a layout idea, not the economic district.