Return feature-only helpers to their owners, remove inactive scaffolding and duplicate state, and reuse existing calculation and UI work without changing public contracts or gameplay.
Record repository-wide coverage, justified retentions, independent reviews and validation, including baseline dashboard fixture failures.
Assisted-by: Cindy (https://cindy.app)
visual_uvel subtracted the unblended planet velocity. PlayerMove_Sail and
PlayerNavigation.DetermineSailVelocity both fade that reference frame out with
altitude and drop it entirely above 600 m, and PlayerController.UpdateRotation
runs after the whole action loop and turns visual_uvel into the mecha heading
and the speed readout, so the mecha visibly misaimed while sailing near a
planet. Apply the same blend, and stop writing uRotation from the sail
postfix, which the game recomputes immediately afterwards anyway.
Fixed targets had no approach deceleration: the cruise always aimed at
maxSailSpeed and simply stopped at the arrival radius. PlayerMove_Sail only
hands over to PlayerMove_Fly below 75 m/s of planet-relative speed, so the
mecha could never land. Cap the speed from the remaining distance, apply the
brake directly as the original does instead of folding it into the turn
interpolation (which weakened it by up to 1/t), and release warp early enough
for that brake to settle, since the game's own warp guard only covers planets
and never stars.
Yield to the game's own autopilot: PlayerNavigation zeroes the movement input
inside PlayerMove_Sail and PlayerMove_Fly and drives uVelocity itself, so both
were fighting over the same state. AutoConstructPatch already did this.
Guard SpaceSector.dfHives, which Init never allocates and Import only
allocates when the save carries hive data; the game null-checks it everywhere
for that reason and this ran on every sailing tick.
Follow AutoCruiseEnabled with the Harmony patches so disabling the feature no
longer leaves a transpiler on the hot PlayerController.GameTick installed, and
require a resolvable target before starting so the feature cannot emit a
started and a stopped popup in the same frame.
Refresh the toggle button label wherever Checked is set directly, since
MyCheckButton.Checked only updates the colours and the label lives on the
OnChecked handlers; toggling by shortcut left it stale.
Rename the user-facing strings to auto-cruise so they stop colliding with the
game's own navigation feature, and clean up the region: fix the misspelled
safety-radius constants, invert and rename the precondition helper, drop the
unused Obstacle.Radius, raise the degenerate-vector epsilon, and convert the
file's mixed tab indentation to spaces.
Flight settling never ran its residual-speed check: the caller gated it on
the tick countdown, which always reached exactly zero, so the constant
thresholds were dead and the wait degraded into a fixed delay. Gate it on a
separate pending flag, bound it with a timeout, and re-issue the deferred
route with bypassBrake so a timeout cannot defer the same route again.
Arrival no longer keeps the detour altitude. The planner scores build-range
coverage at ConstructionFlightAltitude, so hovering at AvoidanceAltitude put
part of the counted ghosts out of drone reach.
Also fix four planning defects:
* the route corridor compared an angle against a sine, and could collapse
instead of widening past 90 degrees;
* candidate near/far separation compared a difference of squared distances
against a squared merge distance, so any slightly farther ghost claimed the
far slot, and a displaced near candidate was dropped instead of demoted;
* the angular fan axes mixed the universal player rotation with planet-local
positions;
* surface distances used chord length where great-circle length was meant.
Ghost eligibility now mirrors the material-delivery filter in
ConstructionModuleComponent.GameTick. A ghost rejected by constructableIdHash
or blocked by a nearby Dark Fog building can never clear itemRequired, so the
mecha would park on a site that makes no progress. The enemy probe is skipped
when the planet has no ground bases.
Drop the OrderNode.Stop in CancelAutoMotion: PlayerOrder.Clear() discards it
before PlayerOrder.GameTick can process it, and the actual braking comes from
PlayerMove_Fly decaying rtsVelocity. It only left a stray order gizmo at the
planet centre.
Untie the Harmony patch from AutoConstructButtonEnabled so hiding the button
cannot silently disable the feature, and throttle the enable diagnostics now
that enabling is an in-game action.
Extract the shared manual-movement input probe, name the obstacle layer mask,
reset a copied Localizer on the cloned count text, and drop the dead
representative-target guard.
Remove the legacy cruise implementation and expose the advanced navigator through the existing auto-cruise setting and UI. Match the game's 1.6-degree steering cap and handle antiparallel target directions with a stable turn plane.