Physical supply and vessel model
Mod version shipped with FlammiCraft: 0.556.0
Overview · Instruments and log · Deutsch
The direct-steam path below applies to RBMK only. Every normal reactor runs as a two-circuit plant with a Steam Generator. Power, emergency cooling, containment and spray below apply to both.
This describes the physical plant under development. Offline checks do not establish gameplay acceptance; complete plant runs and manual multiplayer/load acceptance remain open.
New normal controllers are two-circuit plants right away; new RBMK uses the physical direct-steam path described here. The Reactor Creator builds a cold two-circuit reactor without a Steam Generator and with empty fuel/coolant buffers; sneaking no longer starts a hot plant. Build and link the Steam Generator, connect power, then add coolant and fuel and adjust the rods. After building an RBMK, the Creator directs you to route steam straight from the reactor to the turbine.
The Creator needs a clear, loaded and permitted 13 × 11 × 7 area. If a block prevents construction, the action bar shows its position. The job saves its progress and waits for the owner to return to the same dimension. After the last build step, the controller has 400 server ticks to validate the structure. Blocks already placed stay in the world if validation fails. The job sets its own Creative Motors to 256 RPM as it places them.
Simple mode uses a simplified core and power limits. In realistic mode the simulation couples the spatial core model to the vessel and stores mass and heat.
Supply
Set a Reactor Nozzle to Main Power or Reserve Power and connect an FE cable
to it. Each power nozzle stores 100,000 FE by default (inputBufferFe) and never
exports FE. A reactor can have several of each and their stored FE adds up.
Connect your existing FE generators.
Instead of an FE cable, the power nozzle can also spin directly inside a Create
network: it applies stress for whatever the plant is drawing, so a network with a
single source is enough. If the plant exceeds what the network can carry, the
drive stalls and the supply falls back to reserve power or blackout. The amount
follows the mechanical load model (KJ_PER_SU_RPM_SECOND), not a config value.
Careful: While in a power mode the nozzle takes rotation on every side and passes it on 1:1, like an invisible gearbox. Keep neighbouring kinetic lines away or use a gearbox in front of it, so stray connections stay under control.
Controls default to 16 FE/t. On a two-circuit reactor, connect shaft power or FE to the primary pumps themselves. On an RBMK, internal circulation draws a further 256 FE/t from the power nozzles. Main has priority; a sufficient reserve takes over if main cannot meet demand. An undersized feed may run controls while circulation is unavailable. Circuits are not summed. Spare input energy charges the 19,200 FE control reserve at up to 128 FE/t. At 16 FE/t, it provides 60 loaded seconds. It never powers pumps. The Plant tab shows source, control power, reserve time, coolant temperature, actual emergency flow and damage/waiting state. Empty reserve refuses normal commands with feedback; emergency SCRAM remains available. Digital alarms/sounds/recording report control power loss; the mechanical wall gauge remains readable.
Coolant makeup and emergency cooling
The control reserve briefly keeps the controls powered during an outage. An Emergency Coolant nozzle adds coolant. The separate Emergency Cooling Station temporarily circulates coolant in a two-circuit reactor when the main pumps fail.
Pipes or buckets on an Emergency Coolant nozzle fill the controller's 16,000 mB reserve. Use water for an RBMK or cold primary coolant for a two-circuit reactor.
- RBMK with the physical vessel model. The controller adds water from the reserve when the vessel drops below 80% full.
- Two-circuit reactor. The controller adds cold primary coolant once the circuit is sealed and holds less than 90% of its fill target.
Injection needs fluid in the reserve and FE from the power nozzles. Higher circuit pressure slows injection. The default pressure limit is 160 bar. The default rate is 400 mB/s per nozzle at 2 FE per injected mB. PLANT shows the actual flow.
Vessel mass/heat, chart pages, emergency tanks and control reserve persist.
Known reactor/nozzle boundaries must be loaded; the controller does not load
chunks and reports waiting. Physics/consumption pause without wall-clock catch-up.
The outer-containment scan reads loaded blocks only. An unknown boundary reports
waiting and is never treated as a confirmed open envelope. Supply settings are under
plantSupply in nucleus-server.toml.
Containment and hydrogen
Containment stores water, heat, hydrogen and used oxygen. Vessel discharge carries actual mass/enthalpy into it. Reclosing the envelope resets neither pressure nor damage. Spray uses Emergency Spray nozzles, the controller's 16,000 mB spray water tank and FE from the power nozzles. Above 0.2 bar gauge in a geometrically closed envelope, it defaults to 80 mB/s and 2 FE/mB. Cold water redistributes existing heat and condenses steam; full containment water storage stops it. The menu also shows sump amount/temperature. Pipes or buckets fill water into an Emergency Spray nozzle; below 80 °C, pumping or an empty bucket takes water out of the sump through it. The complete plant must be loaded. Simulation drains nothing; actual drainage removes water and carried heat. Ordinary Minecraft water has no separate temperature/contamination component; drainage is not radiation cleanup. An open/failed envelope exchanges dry air too and retains its new air inventory when reclosed, so a flooded sump does not remain artificially trapped under old air pressure.
Hot cladding forms hydrogen only against available water. Physical readings use vol%, with a default 4 vol% alarm. Ignition needs a 4–75 vol% mixture, oxygen and a hot core. Burning consumes hydrogen/oxygen, produces water and retains heat with a relaxing pressure wave. The envelope can fail above the default 6 bar gauge. Open/failed containment vents actual steam/hydrogen; passive wall heat loss is accounted for separately. With damaged fuel, vented water produces bounded spills and a quantity-dependent fallout release. Small releases accumulate up to 1,000 mB of damage-weighted coolant and persist across reload; new venting while fallout is disabled is not queued.
Physical breaches, melts and ignitions have bounded world consequences, with no later
forced-explosion timer or heat reset. accidentsEnabled prevents new pressure failures
and ignition. Existing meltdownTemperature sets the physical melt temperature too:
the realistic model progresses its spatial melt fraction above it; Simple uses the
temperature or fully damaged fuel directly. meltdownEnabled disables physical melt
world consequences. Heat and existing core damage remain.
Recovery
In direct-steam plants with the physical model, randomIncidents=true can trip
circulation or open relief valves. Messages, switches and history identify the
event. Check the supply or pressure, then restore the pump or valve at the desk.
Protection and ARGUS use actual flow and supply availability.
In a two-circuit plant, a primary pump recovers from a random trip after 20 seconds.
An emergency cooling station can take over during that time.
For two-circuit plants, see Failure and repair for the materials and conditions. An RBMK breach in the physical vessel model uses one Reactor Casing in Survival. Load the entire plant, check the structure and latch SCRAM. Wait for less than 1% power, less than 80 °C at the reactor and vessel, and less than 2 bar vessel pressure.
For a failed outer shell, close the wall first. Repair requires less than 80 °C, less than 0.2 bar above outside pressure and less than 1% hydrogen by volume. Under PLANT, click Repair plant twice. SCRAM stays latched. Check cooling, supply and outlets before restarting. A melted core blocks repair. Placing a new controller does not transfer the old fuel and water.
World-damage settings
worldDamage in nucleus-server.toml covers old/new accidents, ruins, corium,
debris and fallout vegetation damage. NONE prevents block damage; REACTOR_ONLY
also restricts it to saved reactor bounds; RADIUS permits the radius. Defaults are
32 blocks, 128 direct block changes and 4,096 work/explosion probes per dimension/tick,
with explosion power capped at 8. Simultaneous accidents share budgets. Excess one-shot
changes are skipped rather than queued for a later burst.
Block entities are protected by default. Unbreakable blocks, TNT and the extensible
nucleus:accident_protected block tag stay protected. Native explosion/block
callbacks remain; existing world physics and other mods are not generally suspended.
New accident fire blocks are omitted because native fire could spread beyond bounds;
visual flame effects remain.
Separate switches control fallingDebris, fallout, resonanceEffects and entityEffects.
Entity damage/movement obeys the radius and a shared 64-effects/tick budget independently
of block mode. New debris retains its origin/bounds until landing; corium retains them
for later melt ticks. Hot corium pauses under NONE and resumes when permitted.
It cools in place above protected ground or at the edge of its allowed area.
Spreading and cooling together need two available changes in the same tick.
If the configured limit is one change per tick, it cools in place. Legacy
corium uses a conservative origin inferred from age/height. Unmarked debris created
before this build cannot safely be attributed against other mods and is not retrofitted.
Fallout belongs to the dimension of its release: it spreads, decays and acts there,
including the Nether and the End. Disabling fallout retains its spreading/decaying saved cells but stops new releases,
vegetation damage and fallout exposure. Existing player doses remain. Exposure and
vegetation changes require a saved release source within the radius. REACTOR_ONLY
prevents later airborne vegetation changes without known reactor bounds. Disabled
resonance jobs pause and may resume when reenabled; tagged visitors are removed when
disabled. These switches do not repair existing world damage.
Existing radioactive materials retain their normal radiation behavior; accident
switches do not globally disable the radiation system.
Stationary RTG
Craft an empty source capsule from lead/glass, then fill it in a Create Spout with 1,000 mB High-Level Waste from reprocessing. The recipe produces a sealed source. Craft/place the RTG separately, right-click and insert one source. Item pipes can use the same single slot. Connect FE consumers/cables on any side: the RTG exports and pushes energy to loaded neighbors and accepts no external FE.
Defaults are 64 FE/t without ongoing source consumption and a 64,000 FE buffer. Its menu shows actual generation, stored FE, missing source, disabled generation and full-buffer states. Removing the source or disabling generation preserves exportable buffered FE. Normal block drops retain source, FE and switch. Reducing configured capacity preserves stored energy and waits for it to be drawn down.
The RTG runs only while loaded and stationary. Sable ships stop generation and FE
output. It has no Create contraption generator and cannot be pushed by pistons;
no mobile SMR is added. The sealed source adds no separate radiation emitter; its
permanent output is a deliberate gameplay approximation. Output/buffer settings
are under rtg in nucleus-server.toml. Ponder on the RTG and the Reactor Nozzle
explains production and connections. Scene presentation and real cable/ship
interaction still require gameplay acceptance.