Remove the capture points from the game, to capture a planet you just need to kill all ennemies on it #211
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?
Implemented in commit
6e13b63onmain. This was the big one.The rule
A planet registers the garrison its setup authors, each defender's own
destroyedsignal counts against it, and the last kill takes the world and pays the research award. Capture points are gone entirely - the node, its scene, thecapture_pointsfield, the four authored maps' arrays, and the map editor's palette tile, markers, placement, drag and delete paths. The boss encounter is a garrison of one. The surface readout countsGARRISON n/mrather thanCAPTURED n/m.One semantic I had to decide, since the ticket does not say
Capture progress used to persist across landings. The garrison, though, is re-placed in full every time you land - so persisting kills would mean a planet left one-from-clear falls to a single kill against three fresh defenders. The count therefore restarts with the enemies it counts, and a planet already conquered is refused re-registration outright so it can never be handed back. Both cases are pinned by tests.
The kill is bound to the planet id captured when the enemy is spawned, not read at the moment of death: the player may have left the surface by the time a straggler dies, and the planet being fought over is the one they were standing on.
Verification
test_planet_garrison.gd: a realEnemy, destroyed the way anything destroys one, moves the planet toward being held - one kill is progress, the last is conquest, the signal fires exactly once carrying the authored award, and a late kill after the planet has fallen is absorbed without a second payment.test_conquered_planet_clear.gdrewritten for the new rule, including the re-landing case above.test_capture_points.gdwas deleted because it tested a mechanic that no longer exists.test_surface_feature_depth.gdfailed because the research lab's only drawing scenery WAS the capture rings. Its rule is about features that exist, so an empty profile is now skipped, with a run-wide check that at least one profile had features so it cannot quietly prove nothing.