Contracts, grounding, and clearer test tools
Once the map was usable, the next challenge was making the voyage loop playable: find work, sail to the right place, avoid shallow water, and understand the result.
Challenge: contracts had to support actual voyages
Contracts are central to Portbound Seas. They give players a reason to cross the bay, choose routes, and care about cargo capacity, timing, and docking. Early versions had problems with availability and readability.
The first solution was to simplify contract cards and fix availability blockers so jobs could appear across ports. The cargo workflow was then separated more clearly: accepting a job is not the same thing as loading cargo. That distinction matters because the player may view jobs from a port, but still needs to reach the correct dock to load or unload.
Challenge: shallow water needed consistent rules
Shallow water is one of the defining constraints of a Great South Bay sailing game. The game needed a clearer relationship between visible land, depth, grounding, and what the boat actually experiences.
Work focused on making grounding edits persist, centralizing depth and grounding resolution, and aligning debug tools with gameplay behavior. When a tool says an area is safe or unsafe, it needs to match what the boat will actually do there.
Challenge: testing scenarios took too long
As systems became more connected, repeating the same test setup by hand slowed development. Presets were added for boat condition, captain experience, and money states so different gameplay situations can be recreated quickly.
That turned the debug menu into more than a developer convenience. It became a way to repeatedly validate whether the simulation still behaves correctly across common edge cases.