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.
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.