fix: carry signals as NetworkValue, not NetworkToggle

v1.0.0 loaded cleanly and did nothing in game. Every vanilla use of
NetworkToggle and NetworkToggleReceiver -- all three of them -- sets
IncludeInPhysical = false. They are blueprint stat-display plumbing and
carry no signal on a real ship, so the receivers always read off, the
vent gate stayed open, and radiators behaved exactly as in vanilla.

Broadcast 1/0 through NetworkValue and threshold it back into a toggle
on the receiving side. That is what the thermal amplification pump uses
to drive physical behaviour, and vanilla never sets IncludeInPhysical on
it anywhere.

Also repoint the radiator's power indicator at the gate, so an auto-idled
radiator is visibly idle instead of looking identical to a working one.

Tests grow a guard against the blueprint-only types, plus a check that
re-verifies that premise against the installed game data so the guard
cannot go stale, and a name-collision check against vanilla components.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011oLWY1G6S8U35bi2FxVWni
This commit is contained in:
2026-08-28 23:37:21 +02:00
co-authored by Claude Opus 5
parent 831a628b53
commit 3ad03d7964
7 changed files with 250 additions and 73 deletions
+29 -6
View File
@@ -124,14 +124,37 @@ so a broken parser fails loudly instead of passing everything.
Set `COSMOTEER_DATA` to point at a different install.
## How to tell it is working
There is no separate "auto" mode and nothing to reset. The radiator's on/off
switch is an AND gate:
- switch **off** → radiator is off, and stays off. The mod never turns it back on.
- switch **on** → the automation decides, moment to moment.
An auto-idled radiator shows the same "powered off" indicator icon as a manually
switched-off one, and stops emitting its steam plume. That icon appearing on a
radiator you did *not* switch off is the mod working.
## Status
Validated against game data version 0.30.4c. The logic is verified statically —
every patch target, component reference and component type is checked against
the shipped `.rules` files — but it has not yet been run in-game. Worth watching
on the first run: whether `NetworkToggleReceiver` with `AllowUncategorized =
false` reads *off* on a ship with no broadcaster, which is the assumption the
vanilla-fallback behaviour rests on.
Validated against game data version 0.30.4c, and confirmed to load cleanly
(`Enabled mods: [User Folder] - ganter.auto_radiator`).
**v1.0.0 loaded without error and did nothing in game.** It broadcast its
signals with `NetworkToggle` / `NetworkToggleReceiver`. All three vanilla uses of
those types set `IncludeInPhysical = false` — they are blueprint stat-display
plumbing and carry no signal on a real ship, so every receiver read off, the
vent gate was permanently open, and radiators behaved exactly as in vanilla.
**v1.1.0** carries the signals as `NetworkValue` / `NetworkValueReceiver`
instead, which is what vanilla's thermal amplification pump uses to drive actual
physical behaviour, and which never sets `IncludeInPhysical` anywhere in the
shipped data. `tests/test_mod.py` now fails on any use of the blueprint-only
types, and separately re-checks that premise against the installed game so the
guard cannot quietly go stale.
The v1.1.0 logic is verified statically but has not yet been confirmed in-game.
## Possible additions