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