remove all upgrades that let the player increase the fleet size #219
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?
to increase the fleet size, player needs to build a new building type: "Fleet office"
Each office adds one more ship available in the fleet. Fleet offices consumes resources depending on the type of vessel that is being assigned in the fleet. The first default vessel in the fleet do not need office. When the fleet office do not have enough resources, it becomes disabled and the related vessel in the fleet is destroyed. A popup is showed to the player when this happens to let them know their ressource flow is not good enough to sustain their fleet.
Implemented in commit
1f5fecdonmain.The model
Fleet capacity is
1 + supplied Fleet Offices, capped by the 20 positions the formation defines. All eight fleet-size doctrines are gone from the skill tree. An office charges every 25 seconds for the vessel in its berth, from its own store - hub transporters keep it stocked exactly as they do a gas burner. When it cannot pay it goes dark, the vessel is destroyed, and the player is told.Upkeep is derived from the vessel's own BUILD price rather than a second authored table: an expensive hull is expensive to keep, and there is no second set of numbers to drift out of step with the first.
The warning goes through the queue quest lines already use, rather than a new popup path. That queue drains into the narration banner, which stops the game until it is acknowledged - and it works from a planet surface, where there is no banner to shout at directly.
Two decisions the ticket did not settle
take_damagewould have let a shielded vessel survive its own eviction.scuttle()shares the ending (wreck, sound, signal) without the absorb pass.And one I want to flag, because you may disagree
The Fleet Office is NOT gated behind research - it sits beside the mothership in the opening build menu at an ore-only price. Gating it would put fleet size back behind the research tree, which is what this ticket removes; and the only cheap gate available (
coordination) costs a research point, which comes solely from conquering a planet - so it would demand a planet be taken with a single vessel before the fleet could grow at all. Say the word if you want it gated anyway.Verification
test_fleet_growth.gdrewritten end to end: one vessel and one berth at the start, the whole tree researched moves nothing, each supplied office adds exactly one berth, and the starve -> destroy -> warn -> restock -> re-crew cycle.tests/_berths.gdhelper. Four were real findings rather than churn:test_skill_treeandtest_skill_menuboth asserted the tree SCROLLS - the doctrine lane was its deepest branch, so removing it made the tree fit its own view.test_input_after_dialogcompared a nested panel's child index against a UI-level index, two different sibling lists; it passed only by luck and broke as soon as the build menu gained nodes. It now walks up to the UI-level ancestor, which is what actually decides draw order.test_build_menu_hides_lockedassumed every menu row is full; with an odd count the last row holds one, which the layout centres.