fix: route the network components so they actually attach
The diagnostic icons answered it. The wrench was present, so AddBase and the Overrides had applied correctly all along -- but the thermal-missile and resource icons were both showing, meaning both NetworkValues read zero. With both signals absent, VentAllowed collapses to true and AutoPowerToggle degenerates to plain PowerToggle: on means permanently on, exactly as reported. A network component is only attached to the network if a route reaches it. The part's NetworkPort anchors on one component and a NetworkRouter bridges that anchor to the rest -- which is how vanilla connects the radiator's own NetworkedThermalDissipationLoadValue, and how the thermal amplification pump reaches the resonance beam turret. Add routes from each part's anchor: NetworkedHeatBuffer on the radiator via its existing Router, and a new NetworkRouter on the thermal battery, the missile launcher and base_part_overclock, none of which ships one. Unrouted network components are not an error -- they simply never connect and read as absent forever, which is why three versions loaded cleanly and did nothing. The new test fails on any network component the mod adds that no route names. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011oLWY1G6S8U35bi2FxVWni
This commit is contained in:
@@ -16,7 +16,7 @@
|
||||
|
||||
ID = ganter.auto_radiator
|
||||
Name = "Auto Radiator"
|
||||
Version = 1.2.0
|
||||
Version = 1.3.0
|
||||
CompatibleGameVersions = ["0.30.4c", "0.30.4"]
|
||||
ModifiesGameplay = true
|
||||
Author = "Tobias Ganter"
|
||||
@@ -69,6 +69,25 @@ Actions
|
||||
BaseToAdd = &<components/radiator_auto.rules>
|
||||
}
|
||||
|
||||
// --- Attach the radiator's receivers to the network -------------------
|
||||
//
|
||||
// A network component only reaches the network if a route leads to it. The
|
||||
// radiator's ports anchor on NetworkedHeatBuffer, and its existing Router
|
||||
// bridges that anchor to the other network components -- which is how
|
||||
// vanilla's own NetworkedThermalDissipationLoadValue gets connected.
|
||||
// Without these three entries the receivers are inert and read nothing,
|
||||
// which makes the vent gate permanently open.
|
||||
{
|
||||
Action = AddMany
|
||||
AddTo = "<ships/terran/radiator/radiator.rules>/Part/Components/Router/RouteGenerators/0/Routes"
|
||||
ManyToAdd
|
||||
[
|
||||
[NetworkedHeatBuffer, AutoRad_HoldSignal, 0]
|
||||
[NetworkedHeatBuffer, AutoRad_ThermalAmmoSignal, 0]
|
||||
[NetworkedHeatBuffer, AutoRad_ForceVentSignal, 0]
|
||||
]
|
||||
}
|
||||
|
||||
// --- Rewire the radiator ---------------------------------------------
|
||||
//
|
||||
// The radiator's dissipation is gated on PowerToggle directly, not on its
|
||||
|
||||
Reference in New Issue
Block a user