Lors du spawn après avoir chargé une sauvegarde existante il faut que tu sponnes au niveau du Motherhip #227
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Done in
62acb00.Worse than described, as it turned out. A loaded save fell through to the brand-new-game branch in
PlanetAtmosphereController._ready(), which spawnsSTARTING_SHIP_COUNTinterceptors at the world origin. So resuming stranded the player in empty space with the wrong ships, while their base sat wherever they had left it — thousands of units away on a charted map.fleet_positionwas in the save all along, but nothing ever read it: onlyFleetwrites it, as a mirror for payment-range checks.A resumed run now spawns at
get_mothership_position(). That is already the canonical home —BuildController._check_fleet_wipe()rebuilds a wiped fleet there — so this reuses the existing answer to "where does the fleet belong" rather than inventing one. It falls back to the position the save was written at, and only then to the origin, because a run can have no mothership standing. The crew comes from the savedfleet_vessel_types. New games are untouched.resumed_from_saveis a one-shot handoff likehas_return_position, and is deliberately not saved: it describes this launch, not the run.Verified by reverting the branch:
resumed at (0.0, -48.0), but the mothership is at (7400.0, -3100.0).One note for whoever writes the next fleet test: asserting a three-ship crew proves nothing without capacity. Since #219 the fleet holds
BASE_FLEET_SIZE(1) plus one berth per supplied fleet office, sospawn_shipsclamps to 1 and the assertion passes against the wrong number.test_resume_spawn.gdgives the save two offices and checksmax_fleet_size()first.177/177.