Repository navigation
1.8.5-alpha.1
Pre-releaseUltimateImprovments 1.8.5-alpha.1
First 1.8.5 build. It wraps up everything that landed after
1.8.3-release.1 (the whole 1.8.4 dev line): batteries became real
multi-block structures, the compact nuclear reactor got its thermal model,
coolant, meltdown and lazy structure audit, and the bundled datapack now
ships in English and Russian variants. In-game verification of the newest
features is still pending — hence alpha.
Changelog since 1.8.3-release.1
Added
- Batteries are real multi-block structures (UI-Energy + UI-Other) — a
waxed copper grate is now inert on its own: placing one creates no network
node, no storage and no marker. A battery is assembled like the magnet — put
a one-shot item frame on any grate and every copper grate connected to it
becomes one adaptive battery: capacityenergy.battery.max_energy × blocks(100 000 ⚡ per block), the blocks share one charge pool and one
operating mode. A redstone pulse on any block of the cluster cycles
Charge → Charge & Discharge → Discharge (rising edge, so a lever held on does
not keep flipping); the mode is persisted in the newbattery_modestable.
The multimeter reads the cluster's energy/capacity, block count and mode. - Compact nuclear reactor (UI-MBS + UI-Energy) — a 3×3×3 multi-block
energy generator (nuclearreactor.nbt). Assemble it with an item frame on a
top corner (so the top-center barrel stays reachable), put emeralds and ice
into that barrel, power the reinforced deepslate center with redstone (a
lever on the barrel top powers the adjacent center — glass cannot hold a
lever), and connect a cable under the bottom waxed chiseled copper port. It
burns 1 emerald per 10 seconds and pushes 1000 ⚡/s into the network; fuel is
spent only while the structure is intact, the center is powered, a cable is
connected and the network actually accepts the energy (partial acceptance
burns proportionally less). - CER thermal model, coolant and meltdown (UI-Energy + UI-MBS) — the
reactor now has a temperature in[biome floor .. 1024]. The floor is rolled
at assembly from the build-site biome temperature (same formula as the DFC)
and the passive cooling is scaled by the biome humidity. A running reactor
heats to 512° at 20°/s with passive cooling disabled, then holds the point
and drains the cooling buffer (1% per 8s); without coolant it keeps heating
to 1024°, the center block turns into lava and a 10-second detonation
countdown starts. Putting reinforced deepslate back into the center in time
cancels the blast and resets the reactor to 512°; otherwise a charged
creeper with explosion radius 5 detonates instantly. The barrel now also
accepts ice — consumed automatically 1 block/s while the buffer is below
100%, plain ice 1%, packed ice 2%, blue ice 3%. A stopped reactor passively
cools at 1°/s × humidity down to its biome floor, and a restored coolant
buffer pulls a running reactor back to 512°. Threshold particles (signal
smoke above 640°, large smoke above 860°, lava sparks above 960°) and
structure alerts (damage / restored / failure / meltdown / detonation
prevented) are broadcast within 30 blocks. Breaking the redstone center
detonates the reactor; breaking every template block dismantles it; any
other break flips the structure into the damaged state until it is fully
repaired. All state (temperature, limits, cooling, drain progress, meltdown
timer, fuel, damage flag) persists per anchor in the new
nuclear_reactorstable, so a world can host any number of reactors.
Configured in UI-MBS.toml[nuclear_reactor](heat_rate,work_temp,
max_temp,passive_cool_*,temp_limit_*,cooling_*,meltdown_seconds,
explosion_power,alert_radiuson top of the previous keys). The trigger
item frame is consumed on assembly and dropped back (glow frames keep their
type); SHIFT+RMB with the multimeter on any reactor block shows the[CER]
data readout (temperature, cooling, meltdown countdown), and without a
multimeter the player is asked to get one. - CER structure audit and meltdown escape hatch (UI-Energy) — the reactor
is now watched by a DFC-style rotating audit: 9 of the 27 template cells are
re-read per second (nuclear_reactor.audit_cells_per_second, 27 = full check
each pass), so bypasses that never fireBlockBreakEvent— explosions,
pistons, pluginsetType— flip the reactor into the damaged state, restore
it, or dismantle it with the failure alert once every block is gone; player
breaks/places still update the cache instantly. Sealing the meltdown lava
with any block other than reinforced deepslate cancels the blast (the
same "detonation prevented" alert) and dismantles the reactor, which can be
rebuilt afterwards once the reinforced deepslate is back in the center. - NBT templates in the newer palette format —
StructureTemplatenow
accepts a paletteidkey as a fallback for the vanillaName, so
structure files exported by recent game versions load without a manual
conversion step.
Changed
- Datapack ships in two languages (UI-Datapack) — the bundled pack is now
built twice:UI-Datapack-enandUI-Datapack-ru. The content is identical
(enchantments, advancements, recipes, structures, worldgen); only the display
names and descriptions are translated. The newdatapack.langkey in
UI-Datapack.toml("en","ru"or"auto"— followsmessages.lang)
selects which variant the bootstrapper extracts into
plugins/UltimateImprovments/datapack/and registers before the worlds load;
stale variants are deleted, so the pack is never registered twice. Switching
the language requires a restart (pack discovery happens at startup), and the
active variant is visible in/datapack listand the startup log. - CER balance and heat visuals (UI-Energy + UI-MBS) — the compact reactor
now pushes 100 ⚡/s instead of 1000 (UI-MBS.toml
nuclear_reactor.energy_per_second, fallback updated) and the coal
generator runs at 10 ⚡/s (energy.generator.fuel_burn_ticks100 → 200:
one fuel item still yields 100 ⚡ but burns for 10 s). Overheat particles
emit 8 particles per stage instead of 4/4/2 and use an explicit
0.1 speed, so the plume no longer looks like a fast jet. - CER network gate moved before the redstone gate (UI-Energy) — the
reactor checks the network for free storage first
(EnergyFlow.hasSpace) and reportsOUTPUT_BLOCKED("network is full —
the reactor is switched off") without touching fuel or the redstone state;
the redstone gate on the center block is now the second check. A saturated
network therefore stops the reactor (no fuel burn, passive cooldown) and it
restarts automatically once a battery has room again.
Fixed
- Battery modes no longer flip on their own while charging — the mode was
polled fromBlock#isBlockPowered()/isBlockIndirectlyPowered()with a
rotating per-tick scan, so indirect/weak power from neighbouring circuits
looked like a new rising edge and the cluster cycled Charge → Both →
Discharge on every charge cycle (with a chat message each time). Mode
cycling is now driven by the realBlockRedstoneEventof the redstone
component next to the battery (lever, button, dust, torch, plate): only a
genuine 0 → >0 edge counts, and a 10-tick per-cluster debounce collapses
the many events of one dust line into a single cycle. Nothing else can
change the mode. - Structures vanished from the DB after every restart —
purgeOrphaned
was called by the battery, lamp and magnet managers with only their own
UUID set, so each startup deleted the markers of every other structure type
(cables, generators, reactors, magnets, lamps) fromstructure_markersand,
through the chunk-tracker rewrite, dropped their force-loaded chunks. The
purge is now scoped to one marker type (purgeOrphaned(type, uuids)), so a
battery rebuild no longer wipes the cables or the reactor. - A bloated config file stalled the whole server startup — a runaway
writer could grow a TOML (observed: 9 MB) and toml4j ground through it on
the main thread for minutes. Every config read (salvage health check +
per-addon load) now runs underconfig.read_timeout_sec(new key in
UI-Core.toml[config], default 5s, clamp 1..300): a read that exceeds
the budget is abandoned on a daemon worker, the file is treated as
broken — backed up asUI-<Addon>-broken-<N>.tomland regenerated from
the bundled template — and startup proceeds. The first read of
UI-Core.toml itself always uses the built-in 5s default (the configured
value applies from that file onwards, including/ui reload). - Energy never flowed in a generator → wires → consumer network without
a battery — cables are pure routers, the generator pushed into
batteries only and consumers (the reactor's case junctions included)
pulled from batteries only: with no battery in the network nothing
worked end to end (the generator "produced nothing", the reactor
"did not accept energy"). The generator's furnace is now a
GENERATOR-typed network node with a small leftover buffer
(energy.generator.buffer_capacity, default 2000):pushcharges
batteries first, the rest lands in the buffer, and any consumer pulling
through the network drains it — a direct generator → wires → reactor
setup works without a battery. The node is RAM-only and rebuilt lazily;
the multimeter/blink show the transfer even when energy lands in the
buffer. - Generator placement required a cable in place — a generator placed
before its cable stayed inactive forever (until a restart re-scan).
Registration no longer requires a nearby cable: generation itself skips
generators without a connected node, and a cable placed later connects
the node automatically. - The generator dismantled message was hardcoded Russian — routed
throughStructuresMessageswith an English default
(generator.dismantled, configurable in both language tabs). - The generator ignored redstone — it burned fuel and produced energy
around the clock. Now the generator works ONLY while its blast furnace
block is powered by redstone: unpowered means no fuel consumption and no
energy output, the burn timer freezes (the burning fuel resumes where it
stopped when power returns) and the furnace shows the state visually
(lit/unlit). No on/off chat messages, by design. The SHIFT+RMB info now
shows the power state as a separate line. - Generator messages were hardcoded Russian — every player-facing
string (item name/lore, SHIFT+RMB info, assembly) now goes through
StructuresMessageswith hardcoded ENGLISH defaults and is configurable
in the composite config under
messages.structures.generator.*/messages_en.structures.generator.*
(UI-Other.toml: RU and EN tabs). - Every reactor sign demanded the multimeter —
onSignClickintercepted
ANY wall sign inside the reactor footprint (including the roof lamp
labels like "Trigger Action") and demanded a multimeter. Per the design:
at assembly the reactor now registers exactly the 8 control-panel DATA
signs (ReactorDisplay offsets, DB tablereactor_panel_signs, RAM cache)
and clears the registration at disassembly (setReactorLocation(null));
the registry is rebuilt from the live reactors at startup (stale rows of
reactors removed while the server was down are wiped, reactors built
before the registry self-heal on load). Only registered signs cancel the
click and demand the multimeter now; all other signs keep their normal
vanilla behavior. - DFC went mute after one rejected startup pulse — the laser latch
(started) was set inReactorLasers.tick()BEFORE calling
onTriggerPulse(), unconditionally. With the startup energy gate, a
rejected pulse (empty buffer) leftstarted = truewith no startup and
no shutdown running, so every following Trigger Action pulse was routed
totryManualShutdownTrigger()— which silently ignores a non-WORKING
shield. The reactor stopped reacting entirely: no gate message, no
startup. The latch now moves intoonTriggerPulse()and is set only
when the startup is actually accepted; a rejected pulse keeps
started = false, so every retry reaches the gate and its message. - DFC broadcasts had no anti-spam — identical messages are now
throttled per reactor with a 3-second cooldown (keyed by the final
message text, so a changing value like the buffer charge readout still
updates). The cooldown map is cleared on reset. - Multimeter was silent on every energy block —
MultimeterListener
(reading cables, junctions, batteries, generators and the accelerator
engine by right-clicking them with the multimeter) existed but was never
registered by any plugin: dead code, the item did nothing outside the
reactor sign check (which has its own hand check and worked). Registered
in SimpleModules next to the other general listeners, and the item check
is now hand-aware (e.getItem()— the multimeter works from the off
hand too;PlayerInteractEventfires per hand).
Added
- DFC case passive cooling — the case no longer traps heat forever: it
shedscase_cool_rateC*/sec (new key in UI-MBS.toml[reactor], default
3.0) scaled by the build-site humidity multiplier — the same roll as the
core's natural cooling (legacy reactors multiply by 1.0; plains 0.5 →
1.5 C*/sec, jungle 0.9 → 2.7). The cooling runs even with the reactor
off: a hot case now coasts down to the lower temperature limit instead of
freezing above the decay threshold until the next fusion run. The base
rate is auto-clamped in the config loader so that even at the max
humidity multiplier the cooling stays below the working-point (100%)
fusion heat (case_heat_rate× ⅔): a running reactor at ≥100% speed
always nets heating and the decay/maintenance loop stays reachable
(breakeven with the defaults: fusion below ~30% speed loses to max-
humidity cooling). Breach venting is unchanged — broken panes still vent
far faster than passive cooling. - DFC post-maintenance cooldown — saving a critical pane now starts a
cooldown before a new pane can be marked critical:
case_maintain_cooldown_sec(new key in UI-MBS.toml[reactor], default
10, 0 = off). Decay waves arriving while the cooldown runs wait it out —
held exactly like the one-window-at-a-time rule: no new marks and no
breaks until it expires, then the next wave starts a fresh window. The
cooldown restarts on every successful save and is transient (not
persisted, cleared on reset). - DFC case maintenance windows — integrity decay no longer snaps panes
blindly: a decay wave marks ONE random intact pane critical for
case_maintain_window_sec(new key, default 10) — CRIT particles ramp
at the block (radius 0.25, the count grows 1..10 with each elapsed
second) and the reactor broadcasts "DFC Case requires maintenance."
(case_maintenance_required, both language tabs) within the normal
30-block audience. Exactly one window runs at a time — while a pane is
pending its verdict, further decay is held (no new marks, no breaks).
Saving the pane: right-click it with an iron ingot (main hand) — 1
ingot is consumed, the pane stays, no integrity loss. A pane whose
window expires snaps (degradation-style, no drop) and the case
ESCALATES: while it is not fully repaired again, further decay points
snap random panes instantly, without maintenance windows. Full repair
resets the escalation and any pending crits. - DFC case breach bleeds fusion particles — a breached case lets the
accumulated fusion particles (P) escape through the broken glass:
case_breach_leak_per_pctparticles/sec per 1% of broken case glass
(new key, default 10 — a 1% breach leaks 10 P/sec, a fully broken case
drains the core in moments), with a small END_ROD burst streaming out
of a random breach cell. A core drained dry gets its fusion throttled
instead: fusion speed losescase_breach_speed_penaltypoints per 1%
broken glass (new key, default 1 — e.g. a 1% breach runs fusion at
−1%), floor 0; a fully broken case grinds fusion to a stop. The
effective speed replaces the raw one everywhere — case heating, spawn
rate and the signs/stats simply show the reduced values. - DFC case repair costs an iron ingot — a pane placed into a cold case
is only counted when the player holds an iron ingot in the OFF hand
(the main hand holds the glass): one ingot per pane is consumed on
placement (reactor.case_repair_iron_cost, new key, default 1; 0 =
free repairs). Without the ingot the pane lands but does NOT count —
after 1 second it pops off naturally (datapack loot table drops the
glass back), unless the ingot appears in the off hand within the grace
window, then it is consumed and the repair counts. The heat gate keeps
priority: a hot case reports the heat first and never consumes ingots.
The former hot-repair gate is generalized into the repair-failure gate
(ReactorCase.onPaneRepairFailed, verdict re-checks heat first, then
the ingot); only player placements are gated — event-blind placements
(plugins/commands) remain plain audit-tracked repairs. - DFC case hot-repair gate — a glass pane placed into the case while it
is hotter thanreactor.case_repair_max_temp(new key, default 1000 C*)
no longer counts as a repair: the cell is ignored by the damage tracker
(no integrity gain, no breach-message flicker) and its verdict runs after
1 second — still hot → the pane pops off naturally
(breakNaturally, datapack loot table → the glass item drops back out);
cooled below the threshold in time → the pane holds and is counted as a
real repair. The player is told on placement
(case_repair_too_hot, both language tabs). Repairs into a cold case are
unaffected; the admin/DBrepair()path bypasses the gate as before. - DFC startup energy buffer — the reactor now has its own internal
energy buffer (reactor.startup_energy, default 5000 ⚡) charged through
the case junctions: everyWAXED_CHISELED_COPPERcase cell connected to
the cable network (the block itself registers as a network junction when
placed; verified againstdarkfusionreactor.nbt— the whole case wall is
waxed chiseled copper, the copper bars are not) pulls energy into the
buffer at 250 ⚡/s via the unifiedEnergyFlow. A startup (Trigger Action
lamp pulse on a fresh core) requires a FULL buffer: otherwise the startup
is blocked with a "Not enough energy to start the reactor! Buffer:
%have%/%need% ⚡" broadcast (newstartup_no_energymessage key). A
successful startup consumes the whole buffer. The buffer persists in the
newenergy_bufferreactorsDB column (auto-migration; flushed every
5s while charging, immediately on startup/disassemble, restored on load).
One pulse per second drives the charging (ReactorTaskENERGY_BUFFER_INTERVAL). - DFC humidity-scaled natural cooling — the passive core decay (previously
a hardcoded 1 C*/tick = 20 C*/sec) is now configurable and scales with the
build-site biome humidity: at assembly the reactor rolls a cooling
multiplier = biome humidity (Block#getHumidity, live from the climate —
datapack/custom biomes work; a biome without a humidity value falls back
to the configured default) + offset, clamped to [min .. max]. The
multiplier is frozen at build time (a disassemble + rebuild rolls a fresh
one) and scales the live-tunable base rate: plains (humidity 0.5) →
20 × 0.5 = 10 C*/sec, jungle (0.9) → 18, desert (0.0) → 0. Legacy reactors
(built before the mechanic) keep the plain rate until rebuilt. The rolled
multiplier persists in the newnatural_cool_multreactorsDB column
(auto-migration; −1 = legacy). New config keys (UI-MBS.toml[reactor]):
natural_cool_rate(20.0 C*/sec),natural_cool_multiplier_offset(0.0),
natural_cool_biome_fallback(0.5),natural_cool_multiplier_min(0.0),
natural_cool_multiplier_max(1.0).
Changed
- DFC case vent: temperature drains 10× slower on a partial breach —
only the pressure should drop hard when a pane pops: while ANY pane
remains, the case temperature vents at a tenth of the former rate
(0.05 × case_temp_max per second at a 100% breach fraction, down from
0.5), so the fusion heat rise now outpaces a small breach's drain — a
lightly holed case keeps heating instead of free-cooling to ambient
(that free cooling was the exploit). A COMPLETELY broken case has no
containment at all: its temperature drains at the former full rate and
trends back to the lower limit within a second or two. - Energy network rework (ui-energy) — the wires/electricity system is
normalized around a single traversal service:EnergyFlow(transfer/cable) is now the one and only BFS of the
cable network. Producers (generator, reactor), consumers (lamp, electric
furnace, MBS bridge, particle accelerator) and the balancer all go
through itspush/pull/hasEnergy— instead of five copy-pasted
traversals with conflicting rules. Unified rules: cables are pure
routers, the BFS always traverses THROUGH batteries (a full or
mode-blocked battery no longer dead-ends the path), battery modes are
respected on both ends, traversals are node-capped, and moved energy
marks the cables (blink + multimeter readings).- Battery energy now persists — new
energy_storageSQLite table,
flushed every 10s and on shutdown/soft-reload, restored at startup.
Previously every restart or/ui reloadsilently emptied all batteries. - The reactor can actually output energy again — its generation block
pushed energy into CABLE nodes, whereCableNode.addEnergyis a no-op
(cables don't store), and the leftover went into a GENERATOR buffer
nothing consumed. Output now goes throughEnergyFlow.pushinto the
network; unaccepted energy is lost visibly instead of vanishing into a
dead-end buffer. - One balancer instead of two —
BatteryDrainTask(a second balancer
that pushed energy into the first battery with free space, ignoring
charge modes, and fought the real balancer) is removed; its job is
merged intoEnergyBalancerTask, which now walks connected components
viaEnergyFlow.collectBalanceGroup.
- Battery capacity is consistent — cluster capacity is
blocks × energy.battery.max_energy(the same per-block limit the nodes
enforce) instead of the contradictoryblocks × 1000hardcode, so the
charge percentage display is correct. New battery nodes get their
capacity at creation (previously up to 2s of silently swallowed energy
after placement). - Cable blink uses real ticks —
energy.cable.blink.off_ticks/
on_ticksare actual ticks now (the visual pass runs every 5 ticks;
before they counted 40-tick task runs). Flow marks auto-expire (50t
hold) instead of being force-cleared each visual pass.
Added
- Structure forbidden blocks — a general mechanic for ALL NBT structures:
a material from the forbidden list fails the check no matter where in the
structure's full footprint it stands (a solid or an air cell, inside or
outside the air-enforcement zones — a chest parked far from the core
chamber is still rejected). Reported as a distinct "forbidden at
[coords]" fix (newfix_forbiddenmessage key) in a separate
MatchResult.forbidden()list; the match percentage counts them as
mismatches. Global list: water, lava, TNT, pistons (they destroy any
multi-block). Per-structure developer overrides
(StructureTemplate.FORBIDDEN_OVERRIDES, not a user config):
darkfusionreactor additionally forbids containers (chest/trapped/ender,
hopper, dropper, dispenser, furnace family, brewing stand, all shulker
boxes — they clash with the fuel/debris barrel systems and hide items
inside the case) and the observer (wired against the roof bulbs it could
auto-pulse the Trigger Action lamp — the reactor is player-operated). - DFC dynamic lower temperature limits — every reactor rolls its own
lower temperature limit at build time from the build-site biome:
limit = biome temperature × reactor.temp_limit_biome_multiplier + reactor.temp_limit_offset, rounded to whole C* (desert 2.0 × 10 = 20).
The value is read live from the biome holder (Block#getTemperature),
so datapack/custom biomes work; a biome without a temperature value
falls back toreactor.temp_limit_biome_fallback(default 1.0). The
limit is per-reactor and persists in the newtemp_minDB column;
a disassemble + rebuild rolls a fresh one (legacy reactors keep −273
until rebuilt). Every lower-limit check uses it: the core cooling
floor, the stall point (the automatic shutdown now starts at the limit
instead of absolute zero), the shutdown heat dump target and the case
venting ambient floor. New config keys (UI-MBS.toml[reactor]):
temp_limit_offset(0.0),temp_limit_biome_multiplier(10.0),
temp_limit_biome_fallback(1.0).
Removed
- Dead energy config keys —
energy.cable.enabled,energy.cable.max_energy,
energy.cable.log(cables no longer store energy;CableLossTaskdeleted),
energy.battery.discharge_per_tick,energy.battery.smooth_charge.*,
energy.battery.visual.particles_enabled,energy.battery_drain.*(the
drain task is gone) andenergy.balancer.include_batteries(never read).
Removed from the code, ConfigRules and the UI-Energy.toml template; keys
left in live server configs are simply ignored. - Dead config keys
reactor.core_temp_minandreactor.case_temp_min
(default −273) — they have never affected anything: the floors were
hardcoded and are now the dynamic per-reactor lower temperature limit.
Removed from the code, ConfigRules and the UI-MBS.toml template; keys
left in live server configs are simply ignored. - DFC meltdown restabilization — a depleted shield no longer detonates
instantly. The emergency systems deploy an auxiliary shield (100%
integrity draining linearly to 0% over the T-3m window — the drain is
visible on the Shield Stats sign; at 0% the detonation becomes
unavoidable): explosion and fire in the core, the systems
analyze, smoke vents and the multi-line WARNING block announces the
"Emergency Termination Sequence". The stabilizers crank to 200% and the
control locks (the lamps still click, nothing responds). The operators'
second chance: netherite items in the content barrel (the floor barrel
the fusion debris lands in) — the success chance is summed per item
(ancient debris / netherite scrap +1%, netherite ingot +2%, netherite
block +3%; other items are ignored, stacks count fully) and capped by
the newreactor.restab_chance_maxconfig key (default 99, range 0–100)
— the best possible attempt is never certain. A long reactor run
naturally accumulates debris in the barrel, so a no-cargo attempt can
work. The attempt is the Trigger Action lamp pulse: the netherite items
are consumed, the systems run their calibration sequence and roll the
captured chance. Success →
the automatic shutdown procedure runs and the reactor powers
down. Failure (its own three-report sequence) or an expired aux shield →
the detonation becomes unavoidable (the shield FAILED T-10s countdown).
The whole phase machine persists across restarts. - DFC restabilization sequence extension — two more reports between the
shield re-creation attempt and the roll: "Estimating chance of successful
shutdown..." (5s after the re-creation attempt) and "Awaiting reactor
systems to respond..." (5s after the estimated chance) — the roll now
happens 30 seconds after the attempt starts instead of 20. - DFC explicit manual/automatic final shutdown procedures — the final
shutdown phase (power lasers → heat dump → stabilization lasers →
absorber valve → shield ramp → offline) is one shared chain entered
through two explicit trigger kinds. Only the announcement differs:
"due to manual trigger" (the operator lamp pulse on a running reactor)
vs "due to automatic trigger" (the −273 C* reaction-failure stall and
the restabilization success — previously announced as "due to reaction
failure"). The restabilization success shutdown switched from the manual
to the automatic procedure. The heat dump now runs for every trigger
(behaviorally identical: the −273 C* stall passes through instantly).
The trigger kind persists in the newstall_triggercolumn (legacy rows
fall back to the oldstall_manualflag), so the "Saved from extinction"
advancement still counts only the genuine −273 C* emergency stall.
Changed
- DFC stall: the reaction-failure warning precedes the shutdown — the
"Core reaction failure due to critically low temperatures, reaction stall
imminent!" warning moved from the 0 C* crossing to the lower-limit
crossing (so it fires on every reactor, whatever its dynamic limit is),
and the automatic shutdown now starts 5 seconds after it, together with
the "Operator Incompetence" advancement (previously both fired instantly
at the 0 C* crossing, one shutdown-length before the stall itself). - DFC assembly ignores foreign blocks outside the core chamber — the
NBT template check no longer fails on blocks standing in template air
cells (interior decor space, the space above the roof): outside the
functional core they cannot interfere. The core chamber is still
enforced — a sphere of 3 blocks around the core center (the same
(0.5, −4.5, 0.5) point the particle systems use): a foreign block
inside it fails the assembly with the usual break instruction.
Implemented as per-template air-enforcement zones in
StructureTemplate.checkAt(templates without zones keep the full
air matching); the zones also apply to the SHIFT+RMB structure scan
and the closest-match hints. - DFC aux shield integrity warnings — the draining auxiliary shield
broadcasts once per downward threshold crossing at 75 / 50 / 25 / 10%:
"Warning! Auxiliary shield integrity at N%!". - DFC advancement "Critical overload" — granted when the meltdown
restabilization phase starts (the shield just died, the T-3m window is
open). Goal frame, heart of the sea icon, 75 XP, parent
ui:datapack/dfc_unstable. - DFC advancement "Operator Incompetence" — granted when the stall
shutdown starts: the core reached the reactor's dynamic lower temperature
limit, the "reaction failure, stall imminent" warning fired first and the
automatic cooling shutdown follows 5 seconds later (together with the
advancement). Goal frame, ice icon, 50 XP, parent
ui:datapack/start_dfc. - DFC advancement "Self-destruct protocol" (rework of "Fading signals",
samedfc_self_destructfile) — granted at the T-60s announcement, after
the reactor systems finish rebooting (sensors down → controls down →
"Internal Dark Fusion Reactor Systems initiated a self-destruct protocol").
Challenge frame, red terracotta icon, 150 XP. - DFC advancement "Senior ReactorOps" — keep the shield integrity
within 0–10% for one minute straight. Entry requires deliberately
overdriving the core past ~22M C* (shield stress above 100%); hold the
band by balancing stress around the limit — a step to 0% is the
detonation, to 11% resets the progress. Challenge frame, spectral arrow
icon, 300 XP, parentui:datapack/dfc_unstable. - DFC advancement "Is it really that simple?" (hidden) — pulsing the
startup lamp during the self-destruct timed countdown gives a 0.5% chance
per rising edge that the systems malfunction the protocol away: it
disarms, the reactor powers down (controlled shield ramp, lasers off)
and can be started again later. The protocol is not gone for good: it
can roll again on subsequent startups at a halved chance (0.5% instead
of 1% on the default config) until the reactor is disassembled. Too late
once the detonation procedure is announced. Challenge frame, redstone
torch icon, 200 XP, parentui:datapack/dfc_self_destruct. - DFC advancement "Saved from extinction" — granted when the emergency
(stall) shutdown procedure completes successfully: the core coasts down,
the systems step off one by one and the reactor is marked offline,
awaiting a new startup. Covers both the automatic shutdown (reaction
failure at −273 C*) and the manual trigger shutdown. Challenge frame,
totem of undying icon, 250 XP, parentui:datapack/operator_incompetence.
Changed
- The reactor lamp is officially the "Trigger Action" lamp — one lamp,
context actions: startup, manual shutdown, meltdown restabilization
attempt, self-destruct cancel. Renamed across the code (LAMP_STARTUP→
LAMP_TRIGGER,onStartupPulse→onTriggerPulse, comments and the
WARNING hint line). - Roof lamp signs are now static white labels — the aqua live-power
readouts on the nine lamp signs are gone (the values live on the Power
Stats / Shield Stats panels). Every 10 seconds the plugin rewrites the
full label text taken from the NBT template (titles + "+5% Power" etc.),
with the "Core Startup" label renamed to "Trigger Action / Startup /
Shutdown / Restab. / Cancel" — a broken, replaced or wiped sign heals
itself on the next pass. - DFC case messaging consolidated to exactly three events — "DFC case
breach detected!" (the first pane breaks), "DFC case failure detected!"
(the case breaks completely — the integrity shatter or every glass cell
destroyed by any cause; a full physical destruction now actually breaks
the case instead of leaving it officially intact with zero glass) and
"DFC case breach restored." (fully repaired). The 30-second broken-case
reminder and the 10-second "Case glass is broken!" warning are gone, as
are the per-pane "(left/total)" glass damage/repair reports. - A breached DFC case now vents — every missing glass cell drains the
case pressure at (broken/total) × 100% of the max pressure per second and
the case temperature at half that rate (floor −273 C*): a holed case can
no longer hold its pressure and temperature indefinitely while the glass
is partially broken. Any breach outruns the fusion heat rise, so a vented
case trends toward ambient until repaired. - Advancement tree regrouped into clear lines — the "Research" branch
(People of the Past → High Temperatures) no longer trails into tech
crafts: the Photon Cannon ("Light Attack") and reinforced deepslate moved
to the "Technology" branch, which is now one continuous craft progression
ending in the two warp-fungus weapons (Photon Cannon → shoker). - Advancement icons reworked to match their content — Critical overload
(heart of the sea → netherite ingot, the restabilization currency), The
power of fusion (emerald → ancient debris), Senior ReactorOps (spectral
arrow → shield), Destructive Consequences (redstone → creeper head, the
meltdown literally detonates a creeper), Vaporised in the plasma
(redstone block → blaze powder), In the Depths of Hell (nether wart →
lava bucket), Ah, where the oxyden? (redstone → bubble coral), The space
(ender pearl → firework star, the rocket theme), Where is the Earth's
core here? (firework star → magma block), OutOfMemoryError (structure
void → shulker box, "memory full"). This also removes the stray
redstone/redstone_block duplicates in the tree. - Advancement XP rebalance (fairness pass) — rewards now match the
actual effort: "Kaboom!" 100 → 200 (a 1000+ damage single mace hit is a
real challenge), "Suicide" 100 → 25 (one command), "java.lang.
OutOfMemoryError" 100 → 150 and "The server has not responding!" 100 →
150 (the rarer server incidents outscale the common ones), "Saved from
extinction" 200 → 250 (a full emergency shutdown procedure, level with
"Vaporised in the plasma"). - DFC advancement "One-time heating" renamed to "Vaporised in the plasma"
(one_time_heater→vaporised_in_plasma, datapack file and code) — the
trigger is unchanged (be inside the DFC core when it explodes); new title
and description. - Emergency core shutdown no longer rescues a deliberately overloaded
shield — the integrity-below-threshold safety only fires while the
shield stress is within limits (≤100%): an operator-driven overheat is
the operators' responsibility. This opens the 0–10% integrity window the
"Senior ReactorOps" advancement requires; cooling down below the
threshold integrity brings the safety back. - All DFC advancements now require proximity — grants go only to players
within 30 blocks of the DFC structure center (previously a mixed bag of
everyone-online and a 20-block radius). The now-unused
reactor.selfdestruct_adv_radiusconfig key was removed. - DFC advancement XP rebalance — every advancement got its own reward
instead of flat 1 XP: dfc_unstable 10, inside_dfc 20, start_dfc 25,
burn_inside_dfc 40, explode_dfc 75, detonation_irreversible 60,
power_of_fusion 100, dfc_self_destruct 150, one_time_heater 250.
Changed
- The "linux" chat channel is renamed to "terminal" —
/ui chatchnl terminal,
enumChatChannel.TERMINAL, permissionui.chat.channel.terminal, config
sectionchat.channels.terminal.*and log prefix[TerminalChat]. The name
never matched reality (the channel runs PowerShell on Windows), so it now
says what it does. The config loader falls back to the legacy
chat.channels.linuxsection when the new one is absent, so existing
configs keep working until renamed manually.
Removed
- The "Detonation irreversible" advancement — granted at the start of the
T-10s detonation countdown, which duplicated "Destructive Consequences"
(the same meltdown, just 10 seconds apart). Removed along with its grant
hook (onShieldFailureCountdown); the blast itself is still the moment
that counts. Its TNT icon moved to "Destructive Consequences". - The dead "High-Tech Alloys" advancement (
craft_nethered_block) — its
criterion wasminecraft:impossibleand nothing in the code ever granted
it, which also made the whole subtree under it unobtainable (children are
not tracked until the parent completes). "Discharge!" (craft_shoker) now
hangs directly under "The force of decay" (react_with_antimatter).
Fixed
-
The reactor warning ping no longer loops on a breached idle case — the
0.5s integrity ping inReactorDisplay.tickSoundfired for a case
integrity below 100% regardless of the shield state, so any breach pinged
forever even on an offline reactor. The case-integrity condition is gated
on a WORKING shield, same as the shield-integrity one. -
"Saved from extinction" is no longer granted for every shutdown — the
grant infinishStallShutdown()fired for the manual trigger shutdown
and the restabilization success shutdown too. Only the EMERGENCY shutdown
counts now: the automatic stall procedure started by the reaction failure
(core coasting down to −273 C*). The manual/restab paths leave the
advancement untouched. The manual-vs-emergency flag is now persisted
(newstall_manualreactors column): previously a restart during a
manual shutdown that had already passed its heat-dump phase lost the
flag and the shutdown completed as a phantom "emergency" one. -
The
dfc_unstableadvancement is now obtainable — its grant check
(ReactorManager.checkDfcUnstable) was defined but never called, so the
parent of the whole DFC advancement branch could never fire. It is now
checked every tick with the running core: the first shield or case
integrity drop below 100% while the core is active grants it (once per
reactor). -
Reactor broadcasts reach the advancement grant radius — event
messages were sent only within 15 blocks of the anchor while all DFC
advancements grant within 30, so a player could earn an advancement
without ever seeing the warning that caused it (e.g. the T-10s
detonation "run" message). Broadcasts now use the same 30-block radius
(newBROADCAST_RADIUSconstant). -
The legacy
core_case_temp/press/intDB columns are no longer
written — the persistence DTO carried a dead inner-case stat trio that
was always saved as 0/0/100 and ignored on load (the live case lives in
case_broken/temp/press/int). The columns remain in existing databases,
just unused. -
Dead code cleanup in the reactor package —
ReactorStatetrimmed to
the fields persistence actually uses (the unused smoothed-display
values, tick counters and the inner-case trio are gone), a stray;
after a method inReactorCase, stale spin comments fixed (the core
spin target is 95 000 RPS at the working point, not "0.95 RPS"). -
Host terminal channel on Windows — commands ran through
cmd.exe /c
(nolsand no PowerShell aliases → exit 1) and the output was read as
UTF-8 while cmd writes the OEM codepage (CP866 on a Russian locale),
garbling non-ASCII output. Commands now run through
powershell.exe -NoProfile -NonInteractive -Commandwith the output
encoding forced to UTF-8.
Full changelog: see CHANGELOG.md in the repository.
Compare: v1.8.3-release.1...v1.8.5-alpha.1
Install
- Download
UltimateImprovments-1.8.5-alpha.1-jars.tar(21 JARs). - Unpack into
plugins/, replace the oldUI-*.jarfiles. - Restart the server. Requires Paper/Purpur 26.3+, Java 26+.
SHA256 of the archive:
f3bf1c9be075039f7577328461d897ff71515873d9b82bd341c56cd89fa53995