v0.3 Towing and dockside repair · shipped
Permalink ↗Homeward bound
Alex wanted crippled ships to make it home, with people patching the hull and pumping out the water. Homeward Bound starts with a damaged 128-metre Leviathan whose machinery is disabled. Select your ships, press T and click the ironclad. Five fully crewed cutters approach separate positions on the open-water side, send line handlers to stern winches, rig their ropes and begin the slow tow. The hull keeps its dimensions, damage and crew throughout the journey.
The pulling rules give a cutter one towing unit, a Sovereign three and a Leviathan eight. A cutter needs one unit, a Sovereign three and a Leviathan five. Selection uses enough eligible ships to do the job. Helm and propulsion still need their living crew, and handling a line takes someone away from the guns. Underpowered or crewless groups cannot move the target. The tow progresses at 0.8 metres per second for an ironclad in calm water. Flooding, rough seas and incoming fire continue to matter, so reaching safety takes preparation.
Each side now has a 160-by-four-metre repair pier, one berth, six named dockworkers and eight thousand repair supplies. Four shipwrights walk to lifting platforms beside the damaged hull; two pump operators reach their pumps and run hoses aboard. People retain the same 1.717-metre body dimensions as the sailors. Open Shipyard and click a worker’s name to watch closely. The repair camera looks down the gap between hull and pier so the hammer and work platform remain visible.
Shipwrights spend one supply for each hull point restored, while their patches reduce the leak. Pumps remove actual water, letting the unchanged hull rise in the sea. Empty stores stop repairs while staffed pumps continue. Machinery recovers once the hull is at least 50% of maximum hull health and its leaks are closed. Lost sailors stay lost. The berth holds one ship at a time; tugs release their lines on delivery, and the repaired vessel can cast off and sail under its own power. An intact ship can also return to the dock without a tow.
Towlines, rigging jobs, machinery, worker positions, hull work, water and supplies save together. Both co-op players can issue towing and cast-off orders. The multiplayer checks save during the tow, disconnect, load and invite again; then repeat that cycle during dock repair. Each stage resumes the same ships and people. Towing, pumping and dock work can finish after a battle result while cannon combat remains stopped.
Recordings includes Homeward bound: six minutes and thirty seconds in 5,542 bytes. Four legal tow, resume, cast-off and movement commands take the authored damaged ship through recovery, repair and departure. The starting damage belongs to scenario setup. Subsequent changes come from the real simulation, including finite stock consumption and the final sailing order. New recordings use .7. Frozen .1 through .6 recordings keep their earlier simulation paths, including resets and fleet reconfiguration; earlier fire, storm and rescue examples remain unchanged.
All 346 automated tests and the production build pass. Six public browser gates cover real click/keyboard orders, visible rigging and repairs, exact saves, WebGL/WebGPU, narrow controls, departure and complete Node-to-Chromium replay. Four real two-process co-op gates cover shared workers and stock, guest orders, named saves in both stages and cast-off. Existing replay and flooding browser checks pass, and public runtime files match the tested build. Fresh review corrected the repair camera and stale recording-version wording. A final geometry check caught a tug crossing the pier; the corrected formation keeps to open water, and collision tests cover the pier as well as other hulls. The rates and pulling-power rules are authored for play; there is no rope elasticity, force, torque or buoyancy solver. Dockworkers are a separate named roster and are not combat targets. Harbor economy docks keep their previous system. Physical older devices, sustained large-fleet performance and repeated family balance tests remain open; screenshot FPS is not a benchmark.








































































































