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)
Align the runtime and package minimum with the official release that provides the shared production API. Keep official UXAssist 1.6.3 supported and document the dependency in both languages.
Assisted-by: Cindy (https://cindy.app)
Patch the native mecha damage and shield consumers so an inlined Player.invincible getter cannot bypass protection. Replace the fleet damage matcher with target-type prefixes to cover both space paths.
Synchronize the English and Chinese documentation without changing version 2.4.8.
The game-constant centralization attached wrong names to many item IDs, such
as Steel for Titanium Alloy (1107) and HydrogenFuelRod for the Electromagnetic
Matrix (6001). Every remaining usage relies on the IDs, which match the items
in the belt-signal proliferation tips, the matrix metadata types, and the Dark
Fog buy-out definitions. Rename the constants after their actual items and
current Dark Fog item names, and remove the mislabeled constants that only the
retired proliferator source table used. Item groups and compiled values are
unchanged.
The belt hooks keyed signal belts by the local planet's factory index. Battlefield
Analysis Base drones can finish belts on other planets and Dark Fog attacks can
destroy them there, so such changes started or stopped generation on a belt of
the current planet, or were dropped while in space, and a destroyed remote belt
kept its signal entry for any belt later built in its place. Use the factory that
owns the CargoTraffic instead.
The planner migration switched belt-signal upstream statistics to each item's
standard recipe. Capture the native RecipeProto.Explicit flag in the production
catalog and let the belt preset prefer explicit recipes again, which include the
rare-resource alternatives such as Graphene from Fire Ice and Diamond from
Kimberlite Ore. As before, explicit recipes that consume their own product
(X-ray Cracking and Reforming Refine) never supply an item, and natural items
stay raw. Proliferation modes now follow the selected recipe.
Signals can change inside the logic tick when drones finish a blueprint, so a
cache miss now queues the belt and the production planner runs from the next
frame update; the tick only applies cached rates. Document the recipe-based
upstream statistics in the unreleased changelog.
Add Proto-backed planning, fixed-building analysis, blueprint capture, and facility-specific material and power calculations.
Migrate belt-signal upstream statistics, include review fixes, and document the architecture and manual validation workflow.
Use productive veins for mining-rate estimates, resource analysis and hover counts without mutating miners or reserves. Keep zero-cost mining productive, including CheatEnabler infinite resources.
Refs #95
Attach the development action when enabling on an existing player, reuse it on re-enable, and dispatch input once per native input frame instead of every simulation tick.
Refs #66, #5
Validate the full dependency cascade and capacity reductions before applying tech downgrades. Preserve shared recipes, restore native bonus values and station limits, and clamp stored energy to the remaining capacity.
Fix warning integration and tech-tree help button ownership, cleanup and localization. Use the shared patch lifecycle and guarded transpilers.
Refresh bilingual feature and usage documentation, and consolidate the 2.4.7 changelog around the final user-visible behavior.
Rework `Unlock Tech with Key-Modifiers` into a full upgrade/downgrade feature,
ported from the standalone TechTweaks plugin.
- Holding Shift / Ctrl / Ctrl+Shift / Alt while clicking a tech adds 1 / 10 /
100 / all levels and unlocks the direct prerequisites, as before.
- `Caps Lock` toggles a session downgrade mode; the same modifiers then
subtract 1 / 10 / 100 levels or revert the tech to locked. Downgrading walks
the dependent techs so no "prerequisite locked, dependent unlocked" state is
left behind, and it reverts the upgrade values the tech had applied
(`TechFuncRevert`), including the multiplicative, assignment and boolean
`UnlockTechFunction` cases, so repeated up/down cycles do not drift.
- Toggling downgrade mode reports itself like the other toggles: a realtime tip
popup plus the critical warning banner. The banner now shows on its own
instead of requiring `Build without condition` or `No collision` to be on,
and outranks both in the shared priority chains.
- The `?` button in the tech tree shows the full key reference, using the same
title and text as the config panel's tip button. While the option is off, the
button is absent and `Caps Lock` is inert, so the key cannot collide with
other bindings.
- The option keeps its original `General/UnlockTech` config entry, so existing
configurations carry over.
The old unlock-only handler in `Patches/GamePatch.cs` is replaced by
`Patches/TechTweaksPatch.cs`, which follows the repository's mod feature
lifecycle (per-frame input through the registry's `OnInputUpdate`).
Restore architect inventory handling and use 999 virtual items,
including logistics bots, drones, and vessels.
Recycle removed station panels and refresh overlays independently
of typing guards.
Bump CheatEnabler to 2.4.6 and UXAssist to 1.6.1, with release
notes and synchronized package manifests.
Defer wind coverage changes until prefab data is ready and preserve retryable activation state.
Replace fixed raycast local slots with semantic entity-field matching and guard fallback paths.
Adapt UXAssist and CheatEnabler to the new terrain workflows, view modes, receiver inventory, and mineral-depletion API. Preserve crafting shortcuts, batch buyout visibility, soil progression, and saved brush safety.
Refresh game references and document compatibility changes. Release builds, static compatibility checks, behavior assertions, and diff checks pass; user testing is also confirmed.
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.