Clear auto-construction orders on teardown and planet changes without
overwriting manual orders, and reject auto-cruise startup while native
autopilot is active. Reduce AGENTS.md to durable project guidance.
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.
Select the closest eligible ghost in the approach corridor before flying to a selected site, and use spherical cross-track checks to avoid bypassing nearer construction work.
Top up the warp heading toward the requested direction after game rotation so the actual heading achieves the 1.6-degree-per-tick turn step. Reduce warp speed control during large heading errors while preserving manual warp speed input.
Only avoid an orbiting parent when the direct target segment intersects it. Constrain its avoidance radius to stay outside the target and follow a heading-selected tangent before resuming direct approach.
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.
Dispatch shortcut polling from VFInput.OnUpdate's postfix so key-down events use fresh modifier and typing state. Keep regular feature updates in the plugin Update loop.
ModFeatureRegistry is a static class with shared collections accumulating
features from all mods. Dependent mods (CheatEnabler, UniverseGenTweaks)
each independently called InitAll/StartAll/OnInputUpdateAll/OnUpdateAll/
UninitAll, re-running lifecycle for ALL accumulated features including
other mods' — per-frame Update ran 2-3x (breaking CheatEnabler key toggles
to net no-ops), Init/Start/Uninit ran 2-3x (double RegisterExporter causing
save corruption, double SettingChanged subscriptions, double keybind
registration).
Fix:
- Init now runs eagerly at Discover/Register time (Awake-phase), preserving
the original timing that keybind registration depends on (game's
UIOptionWindow._OnCreate copies keybinds only after all plugins load)
- InitAll removed entirely
- StartAll/UninitAll/OnInputUpdateAll/OnUpdateAll made internal so only
UXAssist (host, same assembly, no InternalsVisibleTo) can drive them
- Start deferred to UXAssist.Start (after all dependents' Awake complete;
BepInEx runs all Awakes before any Start)
- Per-feature Started idempotency + per-frame Time.frameCount guards as
defense-in-depth
- Dependent mods reduced to Discover-only in Awake
Document the Init/Start timing contract on IModFeature and
ModFeatureAttribute so future mods can rely on it.