Go-Go Town Fishing Automation Reference

Crab and Lobster Pots belong to a low-attention catch route. They make sense when the town needs a dependable input and you want the first test to stay readable while you work on another district. The Fishing Zone Time Clock answers a different problem: the zone already exists, but worker timing or a repeating shift is the part that needs observation. Treating both as interchangeable makes it difficult to tell whether the failure is a missing node, an unreachable worker, or a badly timed handoff.

Rice Paddy is an ingredient-chain choice, not simply a larger fishing option. Name the recipe, shop, or service that needs the ingredient before placing it, then keep the source-to-next-stage path short enough to inspect. Seafood Converter belongs at the end of a proven raw-catch route. It is valuable when the town has a destination for the finished good, not when the raw input is still intermittent or the output crate is already full.

This separation gives each prop a useful first question: can a passive source complete one catch, can a worker reach and return from a valid zone, can the ingredient reach its next recipe stage, or can a processor turn one batch into a destination the town actually uses? Answer that question before comparing tiers or adding capacity.

• PassiveUse Pots when attention is the scarce resource.
• WorkerUse the Time Clock only after zone and output access are proven.
• ChainUse Rice Paddy or Converter when the next stage has a named destination.

For a passive pot, leave the output handoff in view and wait for one complete catch rather than judging the prop from its placement animation. For a Time Clock, watch the worker enter the zone, interact with a valid node, and return to an open crate. If any link is missing, record that exact link; do not use a higher-tier prop to hide it. A full crate is an endpoint condition, not evidence that the catch rate is wrong.

For an ingredient route, begin at the recipe or service that created the demand and walk backward to the paddy. This avoids placing supply in a remote corner that technically produces stock but never reaches the place that needs it. For the Converter, trace raw seafood into the input, then follow the finished output to a sale, export, or recipe. One complete batch is enough to prove the route; scaling before that only multiplies an unknown.

Keep the baseline visible while testing. A short source-to-handoff line makes it possible to compare a timing change, worker assignment, or output adjustment without also changing roads, staffing, and destination demand. The page should help the player identify the first broken link, not encourage a wholesale rebuild.

• InputConfirm a valid node or raw catch exists.
• HandoffKeep the worker, crate, and processor reachable.
• DestinationName the sale, export, recipe, or service before scaling.

If no passive catch appears, check the placement area and the intended output before adding a second pot. If the zone is valid but the worker is idle, check assignment, path access, node validity, and crate space in that order. A timing control is only the right correction after the worker has a real route to run. This order keeps a blocked road or full storage from becoming a false balance conclusion.

If Rice Paddy output exists but the recipe remains short, inspect the next stage rather than expanding the source. The ingredient may be waiting in the wrong crate, outside a worker route, or attached to a demand that is not active. If Converter output is missing, separate raw input starvation from processor access and finished-good demand. Each condition asks for a different correction, so a single “add more fishing” answer is too broad to be safe.

After the first correction, run one complete cycle under the same town conditions. Keep the original prop count, worker, road, and destination stable until the route proves itself twice. Only then decide whether another prop removes a real capacity limit. This produces a maintainable fishing district and a clearer update path when a later patch changes timers, tiers, or storage behavior.

• Walk backwardStart at the empty destination and inspect the previous handoff.
• Change one linkDo not alter source, worker, road, and demand together.
• Prove twiceScale only after a compatible second cycle succeeds.