Control room
one desk runs the whole reactor · click a numberDesk, front view (studs)
Where: the south-west room
STABLE
Heat0
Change / s0
Output0
Demand0
Day 1 · server
- Close the south-west room: wall on x 536 with a steel door at z 996.
ReactorCoreserver module: the loop below, attributes onWorkspace.Reactor.- Prompts on controls 1 to 5 (tagged parts, found once with CollectionService).
- Breakers drive the city: FENCE = ReactorGates, LIGHTS = CityBlackout, SCREENS = PropNet power, PRISON = cell doors.
Day 2 · client and test
- One client script: lever, switch and button tweens, lamps, board needles, all from attributes.
- Plant board SurfaceGui (control 6).
- Hook the existing furnaces (7) and charge (8) to the same attributes.
- Test against Play it: solo near 500, crew near 560, sabotage melts in about 45 s.
Reuse
ReactorOLD/ReactorRoomsManager: coal feed, cooler break and repair, switches.ReactorOLD/ExplosiveManager: the charge.Reactor/CityBlackout, existing door system, destroyed-plant swap.- Nothing else in the plant changes.
The whole algorithm
every 1 s: heatIn = Σ furnaces with coal: 6.7 × (3 if its booster is on) × ROD[rods] k = 0.030 + 0.010 × (coolers running) heat += heatIn − k × heat (+ surge ±20..60 every 40-70 s) coal per furnace −= (0.75 if booster else 0.25) × (0.5 + 0.5 × ROD[rods]) output = heat ≥ 200 ? clamp((heat − 200) / 4.5, 0, 180) : 0 every 30 s each running cooler faults with 3% + 12% × hot ROD = 0.2, 0.4, 0.6, 0.8, 1.0 loads 30, 25, 20, 25 BLACKOUT < 200 · LOW < 450 · STABLE < 650 · HOT < 1000 · CRITICAL MELTDOWN = heat ≥ 1500 for 12 s
Settles at heatIn / k. Solo 500, crew 560, everything on 1000. Boosters alone never melt it; Raiders must kill the coolers too.