Horus Swarm Console
GTNH 2.8.4 · Dyson Swarm × Lapotronic Supercapacitor

Horus Swarm Console

Cannot explode — TecTech explosions removed in 2024

Sizing a Dyson Swarm on Horus (power factor 3.37) against the wireless throughput of a single UHV lapotronic capacitor — including the laser hatch pair that carries the power, and what the quest's explosion warning is actually worth today.

Match point 297 modules 10.009 G EU/t — first count ≥ 1× UHV nominal
UHV wireless rate 10 G EU/t 60 T EU pushed every 5 min rebalance
Per module · Horus 33.7 M EU/t 10 M EU/t base × 3.37 dim factor
Laser pair UHV 16 384A source + target, dial to 4 773A
Swarm ceiling 10 000 modules 337 G EU/t on Horus ≈ 34 UHV caps

Swarm sizing

Drag to size the swarm; readouts show Horus output against the nominal wireless throughput of the chosen capacitor bank. Nominal is not a hard cap — every rebalance pushes the full excess — so slight overshoot is harmless.

Load vs nominal100.1 %
Within nominal throughput
Swarm output (Horus)10.009 G EU/t
Bank nominal throughput10.000 G EU/t
EU per 5 min rebalance60.05 T EU
EU per 1 h recipe cycle720.6 T EU
Modules for this bank297
Coolant (fixed)3.6 M L/h

Laser link — swarm to LSC

A laser source hatch counts as a dynamo hatch, so the ground unit takes one directly. Both ends must be the same voltage tier — a source above the target detonates the target hatch — and each hatch carries amps × tier voltage per tick. Amps are adjustable down with a screwdriver, so buy the smallest variant that covers the load and dial it to the amps you actually need.

Required throughput10.009 G EU/t
Minimum amps at this tier4 773 A
Hatch capacity as bought34.36 G EU/t
Transfer burst (every 20 t)200.2 G EU
Source hatch buffer240.2 G EU
Laser loss (both hatches)477 EU/t

Throughput per hatch — tier × amps

covers current load recommended pair below load — = no assembly recipe in 2.8.4

Output vs capacitor thresholds

Swarm output on Horus is linear in module count. Dashed rungs mark whole-capacitor nominal throughput; the marked points are the first module counts clearing each rung (297 / 594 / 891).

Data table
ModulesEU/tUHV caps (nominal)
1003 370 000 0000.34
29710 008 900 0001.00
59420 017 800 0002.00
89130 026 700 0003.00
10 000337 000 000 00033.70

Failure mechanics

What the quest warning is actually worth in 2.8.4, from source and git history.

The warning is obsolete

Saturating the dynamo still calls explodeMultiblock() — but TecTech emptied that method in Sept 2024 ("yeet explosions", PR #3207). It and doExplosion() are no-ops, and explodeMultiblock() is final, so no subclass can restore it. The quest text and wiki are stale.

Tier mismatch detonates

The source hatch compares itself to the target: a higher-tier source calls doExplosion() on the target hatch, a lower-tier source transfers nothing at all and backs the swarm up into its own explosion. Only an exact tier match moves power.

Disable latency

Work-enable state (mallet, machine controller cover) is checked only when the current recipe finishes — a 72 000-tick, one-hour cycle. Mid-cycle the swarm keeps pushing EU regardless, so redstone shutoff cannot outrun a buffer that fills in seconds.

Bursty, not continuous

Laser hatches move power once every 20 ticks, up to amps × 20 × tier voltage per burst. The source buffer holds 24 ticks' worth (V × 24 × A), which is why amps × tier voltage ≥ swarm EU/t keeps the buffer from ever topping out.

What saturation costs you

EU that will not fit in the hatch buffers is silently voided. The method returns false, but energyFlowOnRunningTick ignores the return and reports success, so the swarm keeps running — burning cryotheum and modules to make power that goes nowhere. Wasteful, not fatal.

What can still break blocks

Hatches are plain MTEHatches with no TecTech protection: an exposed dynamo hatch can still explode from rain, thunder or adjacent fire like any GT machine (BaseMetaTileEntity.java:406–479). Roof the hatches. A laser tier mismatch also detonates the target hatch for real.