The primary Steam source was reviewed on 2026-08-08. Exact values or steps that source does not confirm remain labeled unknown until reproduced in the current version.
Map areas and connections first
Begin by naming the cliff areas that the current game lets you use. Then record each bridge or zipline that connects them. Corsair Cove officially makes vertical construction and those connection types part of city building, but the supplied evidence does not establish which connection should always be built first or how many of each a successful city requires.
A simple sketch can separate physical placement from economic assumptions. Mark structures and links exactly as they appear, then note any observed movement through the connection. Do not write an assumed capacity, speed, range, or construction cost unless the current official interface provides it and the observation is dated. That keeps the map factual even before the player understands every system.
- Name each active cliff area
- Mark visible bridges and ziplines
- Record observed connections without invented capacity
- Avoid labeling one arrangement as the best layout
Trace one production relationship
Production chains and resource logistics are confirmed features. To learn them safely, choose one process shown by the current build and write down the visible source, the path or connection involved, the receiving step, and the observed result. If an ingredient or output is not explicitly shown, mark it unknown rather than importing a recipe from a third-party table.
Change only one part of the observed route before comparing the next result. That can reveal whether a placement or connection is relevant without claiming a universal throughput formula. The dedicated Production Chains page expands this method and explains why a complex production system needs source labels more than it needs an early 'perfect ratio' copied from another player's city.
- Choose one visible production process
- Record source, connection, receiver, and result
- Change one observed relationship at a time
- Leave unknown recipes and output rates blank
Add ships and crew without assuming priorities
The wider loop includes building ships, assigning crew and a captain, and sending the vessel on a sea expedition. Crew cohesion and needs also matter. These facts explain why a city eventually connects production with personnel and fleet preparation, but they do not prove that shipbuilding belongs at one fixed point in every player's technology sequence.
Use the Ships and Crew Guide when those systems become visible in the live game. It distinguishes confirmed relationships from missing crew values, captain rankings, routes, and rewards. For a beginner, the reliable takeaway is structural: cliff areas need readable connections, production needs traceable logistics, and expeditions involve ships plus managed crew. The optimal timing remains unconfirmed.
- Recognize ships, crew, captains, and expeditions as connected systems
- Watch cohesion and needs only as the current game displays them
- Do not assume an ideal crew size
- Do not invent a fixed early technology order