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.
Describe a chain from visible evidence
Start with one process that the current build identifies. Record the name shown for the source or producer, any displayed input, the connection between areas, the receiving step, and the output only when the interface makes those facts visible. Production may span cliff areas connected by bridges or ziplines, so location and connection belong in the same note as the process itself.
Use 'unknown' for any missing ingredient, quantity, cycle time, capacity, or yield. A partial record with clear evidence is more useful than a complete-looking recipe assembled from memory. The official Steam description supports complex chains and logistics, but it does not supply the detailed formula sheet needed to claim exact ratios on this page.
- Copy current names exactly as displayed
- Record only visible inputs and outputs
- Include the bridge or zipline when it connects the chain
- Mark every unstated quantity as unknown
Test a logistics question without declaring an optimum
When a resource does not reach the next confirmed step, compare the current path before changing the whole district. Note the sending area, receiving area, relevant connection, and observed resource state. Then change one visible relationship and observe again. This is a controlled troubleshooting method, not proof of a hidden transport rule or a guaranteed fix.
Avoid converting a single successful arrangement into a best layout. A cliffside city's connections, available technology, and production context may differ. The source used here does not establish throughput thresholds, building ratios, connection capacities, or one ideal vertical design. Any future numeric guide needs a dated current-build test and a traceable source.
- State the logistics question precisely
- Capture the current sending and receiving areas
- Change one connection or placement relationship
- Report the observed result without inventing causation
Keep production claims separate from expedition claims
Corsair Cove also includes ships, crew, captains, and sea expeditions. Production may support the larger city, but this page does not assume a particular recipe is required for a ship or an expedition unless the live game explicitly shows that relationship. The Ships and Crew Guide covers the confirmed fleet loop without adding unverified resource costs.
Exact recipes, yields, cycle times, storage or transfer limits, best ratios, and technology order remain unknown here. Existing wikis and planning tools can suggest what to inspect, but their data is not copied as official. Use the Beginner Guide to place a documented chain back into the wider cliff-area and connection map.
- Do not infer a ship recipe from the existence of production
- Do not infer expedition costs or rewards
- Treat third-party tools as leads, not proof
- Return to the beginner map when location is the real issue