TotenKnopfandClaude Opus 5
014e45aa2b
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
67 lines
1.9 KiB
Plaintext
67 lines
1.9 KiB
Plaintext
// ABOUT ME
|
|
// Components merged into base_part_overclock, the shared base for every
|
|
// overclockable part. They form the mod's safety net.
|
|
//
|
|
// Why it exists: the threshold band on the thermal battery is a prediction. It
|
|
// can be wrong -- if the ship generates heat faster than its radiators can
|
|
// clear it, or if heat pipe topology cannot deliver to the batteries quickly
|
|
// enough, heat overflows regardless of what percentage the band is set to.
|
|
//
|
|
// OverflowHeatStorage is the engine's own ground truth for that: heat only ever
|
|
// reaches it when the network has already refused the heat, which is the exact
|
|
// moment the part starts cooking itself. Any part in that state forces every
|
|
// radiator on the network to vent, ignoring the band entirely.
|
|
//
|
|
// The timer holds the signal for a few seconds so a stream of per-tick overflow
|
|
// events becomes one steady "vent now" rather than a flicker.
|
|
//
|
|
// Carried as a NetworkValue rather than a NetworkToggle: vanilla marks every
|
|
// NetworkToggle IncludeInPhysical = false, so they do not carry a signal on a
|
|
// real ship.
|
|
|
|
AutoRad_OverflowTimer
|
|
{
|
|
Type = Timer
|
|
Duration = 3
|
|
StartExpired = true
|
|
StartTrigger = OverflowHeatStorage
|
|
ResetTrigger = OverflowHeatStorage
|
|
}
|
|
|
|
AutoRad_One { Type = StaticValue; Value = 1 }
|
|
AutoRad_Zero { Type = StaticValue; Value = 0 }
|
|
|
|
AutoRad_OverflowValue
|
|
{
|
|
Type = ToggleValueSelector
|
|
Toggle = AutoRad_OverflowTimer
|
|
ToggleOnValue = AutoRad_One
|
|
ToggleOffValue = AutoRad_Zero
|
|
}
|
|
|
|
AutoRad_NetworkedForceVent
|
|
{
|
|
Type = NetworkValue
|
|
ValueSource = AutoRad_OverflowValue
|
|
Categories = [ auto_radiator_force_vent ]
|
|
IncludeInBlueprints = false
|
|
}
|
|
|
|
// Routes the broadcast onto the heat network. NetworkHeatInput is what this
|
|
// base's thermal ports anchor on (BASE_THERMAL_PORT: RouteSource =
|
|
// &../HEAT_NETWORK_INPUT).
|
|
AutoRad_Router
|
|
{
|
|
Type = NetworkRouter
|
|
RouteGenerators
|
|
[
|
|
{
|
|
Type = Bidirectional
|
|
Routes
|
|
[
|
|
[NetworkHeatInput, AutoRad_NetworkedForceVent, 0]
|
|
]
|
|
}
|
|
]
|
|
}
|