Skip to content

Releases

1.8.5-release.1

Choose a tag to compare

@rizer001 rizer001 released this 15 Nov 12:50
v1.8.5-release.1
38c01da

UltimateImprovments 1.8.5-release.1

Changes from 1.8.5-beta.22 through 1.8.5-release.1.

[1.8.5-release.1] — since 1.8.5-beta.22 (2026-11-15)

Release channel — the first stable release of the 1.8.5 line: everything
published after the 1.8.5-beta.21 release, from the external authentication
audit up to the final reactor and configuration work. Every per-beta entry
below is part of this release.

Highlights of the line:

  • Authentication is hardened end to end (beta.22, beta.23): 2FA cannot be
    skipped by reconnecting, the login gate fails closed, wrong-password attempts
    and exponential lockouts are persisted, parallel dialog submits are
    serialised, and the pre-login freeze covers chat, entities and inventory.
  • The OP subsystem agrees with ops.json (beta.25-beta.28): /ui op and
    /ui deop accept offline players, deop all revokes real OPs, list/flag
    drift is repaired instead of blocking the command, and every message of the
    group is configurable in both languages.
  • Items: air-fired vanilla Fire Charge (beta.29-beta.32), air-only Remote
    Detonator (beta.33, beta.34), Portable Workbench (beta.36-beta.39),
    exact-amount experience bottles (beta.37), and the Structure Indicator turned
    into a real structure tool (beta.35, beta.51).
  • Photon Cannon physics and balance (beta.40-beta.44): hardness-based block
    piercing, no speed loss per ricochet, entity probes, claim-aware blocks and a
    much higher DPS.
  • Datapack, advancements and enchantments are configured, not compiled in
    (beta.45-beta.49): UI-Advancements.toml (43 achievements),
    UI-Enchantments.toml (18 enchantments), independently gated pack parts, and
    a single deterministic datapack zip with a hash cache.
  • Reactor safety and presentation (beta.52-beta.55): scooping the CER lava
    core no longer detonates the reactor, both reactors run 20-second countdowns
    with staged T-20/15/10/5 alerts, and the core check interval is configurable
    in real ticks.
  • Console and validation texts (beta.48, beta.50): repeating startup scan
    lines are behind [debug] startup_scans, and config validation output is a
    bilingual config section.

[1.8.5-beta.55] - 2026-11-15

Changed

  • Both reactor countdowns are 20 seconds now. CER
    nuclear_reactor.meltdown_seconds and DFC
    reactor.shield_failure_countdown default to 20 (existing configs
    still carrying the old 10 default are migrated once by
    AddonConfigManager). The DFC's meltdown particle ramp and rising ambient
    pitch were hardcoded to a 10-second window (meltdownTimer / 200); they now
    scale with the configured countdown, so the whole finale stretches correctly.
  • CER countdown presentation. Once per second the core plays
    BLOCK_FIRE_AMBIENT (crackling fire) to players within 10 blocks; the pitch
    starts at the normal 1.0 and falls toward zero as the countdown expires.
  • Countdown alerts at T-20 / T-15 / T-10 / T-5 for both reactors, in their
    existing styles ([UI][CER] and [UI][DFC] prefixes):
    • CER: initial meltdown_detected at T-20, then the new
      structures.nuclear_reactor.meltdown_countdown at 15/10/5;
    • DFC: initial shield_failure now carries %sec% (T-20), then the new
      structures.reactor.shield_countdown at 15/10/5.
      New keys are added to both language sections of UI-Other.toml and are
      filled into existing configs by the standard repair pass. The stale
      meltdown_fail_total "T-10s" text was replaced with "imminent".

[1.8.5-beta.54] - 2026-11-15

Changed

  • The CER meltdown core check is configured in real ticks:
    nuclear_reactor.meltdown_core_check_ticks (default 20 = once per
    second), replacing meltdown_core_check_seconds.
    The check now runs in its
    own small task (NuclearMeltdownCoreTask) scheduled with that exact period,
    so values such as 10 or 30 are honored precisely instead of being
    rounded to the 1-second countdown cadence. The countdown itself is unchanged,
    and its final second is still checked so a removed core can never explode.
    Validated in ConfigRules (1..72000) and documented in UI-MBS.toml /
    GUIDE.md.

[1.8.5-beta.53] - 2026-11-15

Changed

  • New nuclear_reactor.meltdown_core_check_seconds (default 1). The
    CER task already runs once per second, not per tick, but the meltdown core
    read can now be spread over several seconds to lower the per-second cost
    further. The countdown itself keeps ticking every second; only the center
    block lookup is gated. The last countdown second is always checked, so a
    removed core can never be missed on a skipped pass. Validated in
    ConfigRules and documented in UI-MBS.toml / GUIDE.md.

[1.8.5-beta.52] - 2026-11-15

Fixed

  • CER: removing the lava core no longer detonates the reactor. During the
    10-second countdown the meltdown branch only ran the clock, so a core that
    stopped being lava without a player block event (scooped with a bucket,
    broken, changed by another plugin) still exploded when the timer expired.
    The tick now checks the center every second: reinforced deepslate restored in
    time prevents the detonation as before, while air / any other block seals the
    blast and dismantles the reactor — the same outcome as placing a wrong block
    into the core. Breaking the center block during the countdown follows the
    same rule instead of detonating.
  • SHIFT+RMB readouts only claim the click when the clicking hand is empty or
    holds the Multimeter.
    The CER readout, the DFC data-panel sign and the coal
    generator readout cancelled every SHIFT+RMB on their blocks and answered "a
    multimeter is required" regardless of the held item, so a lever or any other
    block could not be placed on top of them (and the generic empty-off-hand
    event could not be told apart from the real click). MultimeterApi now
    resolves the click from the item of the hand that performed it: a multimeter
    gives the readout, an empty hand gets the hint, and any other item leaves the
    event untouched so vanilla placement/interaction still runs.

[1.8.5-beta.51] - 2026-11-15

Changed

  • The Structure Indicator is a real tool now, not a half-finished
    ender-chest gadget.
    It works exactly like the Multimeter (SHIFT+RMB, chat
    readout, shared per-click state, standard "can't measure" error) but has its
    own measurement list — structures:
    • ender chest — the existing stress / degradation / integrity report;
    • DFC reactor — core and case integrity, core/case temperatures, meltdown
      countdown, damaged/breached state;
    • compact nuclear reactor (CER) — status, structure damage, temperature,
      cooling, detonation countdown;
    • coal generator — assembly state, redstone gate, structure id;
    • battery multiblock — block count, shared capacity, mode;
    • particle accelerator — component (engine / sensor / ring / injector),
      engine buffer and readiness, sensor last speed;
    • magnet — cluster size, power tier, radius, centre;
    • lightning rod — structure state and centre;
    • light structure — lamps, junctions, lit state, consumption;
    • chunk loader — the kept-loaded chunk;
    • any other structure-registry row — type, id and block count.
      Blocks that are not structures answer with
      <plugin prefix> [STRUCT] Can't measure the structure of this block. The
      tag word and the body are configurable in the new
      [messages.structures.structure_indicator] / messages_en sections of
      UI-Other.toml, and StructureIndicatorMessagesTest guards both languages.
  • The item is no longer a block. The calibrated sculk sensor is replaced by
    a recovery compass, so the indicator cannot be placed. The PDC tag stays
    is_structure_integrity_indicator:1b, so already crafted items keep working.
  • Its craft is in the Multimeter's cost class but its own shape —
    DID / IRI / DID (4 diamonds, 4 iron ingots, a recovery compass). The recipe
    moved from UI-Other into UI-Items together with the other tool recipes, and
    the admin-menu entry now comes from the same factory instead of a hand-built
    copy.
  • The structure readouts now route the tool correctly. The generator furnace,
    CER block and DFC data-panel sign readouts leave the click to the Structure
    Indicator when it is in hand instead of cancelling it with "a multimeter is
    required"; the Multimeter still answers for energy. The ender-chest report is
    handled at LOWEST because EnderChestManager cancels the interaction at
    NORMAL for its custom GUI.

[1.8.5-beta.50] - 2026-11-15

Changed

  • The structure/energy scan lines are silent by default. [Generator] Auto-detected N generators ..., [ParticleAccelerator] Scanned existing accelerators — N engine buffer(s) in cache. and [StructureChunkTracker] Loaded N structure chunks. repeated after startup (the +5 s / +30 s / +120 s
    delayed rebuild passes) and on every world load, spamming the console with
    the same numbers.
  • New [debug] section in UI-Core.toml with startup_scans (default
    false). Turning it on prints those three lines as [debug] messages;
    ConsoleLogger.debug(...) is the shared gate, so other diagnostics can join
    it later. The switch is re-read on /ui reload.

[1.8.5-beta.49] - 2026-11-15

Changed

  • The bundled datapack is a single zip now, not a 243-file folder.
    plugins/UltimateImprovments/datapack/ holds UI-Datapack-<lang>.zip (Paper
    discovers a zip exactly like a folder via FilePackResources) instead of
    UI-Datapack-<lang>/ with the whole tree. The archive is assembled in memory
    from the addon JAR — part toggles (datapack.modules.*) and per-achievement
    switches (UI-Advancements.toml) are still applied, inclu...
Read more

1.8.5-beta.21

1.8.5-beta.21 Pre-release
Pre-release

Choose a tag to compare

@rizer001 rizer001 released this 11 Nov 15:16
v1.8.5-beta.21
1888ea2

UltimateImprovments 1.8.5-beta.21

Changes from 1.8.5-beta.1 through 1.8.5-beta.21.

[1.8.5-beta.21] - 2026-11-11

The authentication flow is fully configurable and bilingual, with the latest
dialog-state fixes, current Paper API calls, and a reproducible Java 26 build.

Fixed

  • Submitting a password no longer reopens the login dialog mid-verification.
    The prompt tracks an in-flight submission, restores itself after failed
    attempts, and avoids misleading blocked-action hints during the check.
  • Authentication dialogs recover when a frozen player has no visible screen.
    Closed or missing prompts are re-opened with throttling, including after a
    password lock expires; the player is told when reconnecting is the fallback.
  • Logout, self-service password changes, admin password resets and 2FA cancel
    actions now match their dialog identifiers correctly.
    The logout flow closes
    the confirmation screen and uses a plugin-styled kick reason.
  • Paper API calls updated across the plugin modules for the current Paper
    API, replacing deprecated calls used by the project.
  • Password-submission logs no longer include password length, for either normal
    authentication or sudo confirmation.

Changed

  • Authentication text is configuration-driven in both languages. The
    remaining English and Russian strings were moved out of Java code; the
    messages and messages_en auth sections now contain matching sets of
    143 keys, including 2FA, login/registration, logout and admin commands.
  • Authenticator success and challenge messages share the configured message
    keys, and player/account names are inserted through placeholders rather than
    concatenated between MiniMessage colour tags.
  • The login dialog's submitted state is tracked separately from its open state,
    so the client closing the custom screen on submit is not mistaken for a
    missing authentication prompt.

Build

  • Removed the machine-specific Windows JDK path from gradle.properties.
  • Enabled automatic Java toolchain provisioning and added a Java 26 Gradle
    build-and-test workflow for all modules.
  • Corrected the executable bit on gradlew, so Linux CI can invoke the wrapper.

[1.8.5-beta.20] - 2026-11-05

Authentication messages can now be translated and edited without recompiling.

Changed

  • Moved the remaining hardcoded Russian authentication messages into
    UI-Auth.toml, including password-change validation, admin password reset,
    logout and dialog cancellation messages.
  • Added matching Russian and English keys for the authentication dialog and
    admin feedback, including player-name placeholders.
  • Fixed English kick messages that contained escaped \\n sequences and
    displayed literal backslash-n text instead of line breaks.
  • Removed Russian fallback literals from the authentication classes; the
    configuration's language fallback supplies the displayed text.

[1.8.5-beta.19] - 2026-11-05

Authentication dialog actions and logout handling are reliable.

Fixed

  • Dialog action identifiers are compared by namespace and path. This fixes
    logout confirmation, self password change, admin password reset and 2FA
    cancellation actions that were silently ignored because Paper's Adventure
    Key and the stored Minecraft Identifier are different types.
  • Logout closes its confirmation dialog before disconnecting the player and
    shows a multi-line, plugin-styled reason.

Changed

  • Added the missing Russian admin authentication messages and aligned the
    English logout message with the same layout.

[1.8.5-beta.18] - 2026-11-05

Authentication commands and dialogs gained proper access rules and 2FA UI.

Added

  • Sender-aware tab completion for /ui auth: pre-login players only receive
    login suggestions; authenticated players receive the available 2FA, logout,
    password-change and permitted admin subcommands.
  • A login subcommand and bare /ui auth shortcut reopen the login dialog for
    players awaiting authentication.
  • A bilingual GitHub 2FA challenge dialog with an open-URL action and a cancel
    action that returns the player to the password screen.

Changed

  • Before authentication, only /ui auth and /ui auth login pass the command
    gate. Other authentication and admin actions remain unavailable.
  • Authentication dialogs use the RU/EN message configuration instead of
    hardcoded Russian text.

[1.8.5-beta.17] - 2026-11-05

The login prompt now recovers automatically when the client closes or fails to
display the custom authentication screen.

Fixed

  • Track whether the authentication dialog is open and throttle re-opening when
    the client has closed it or failed to render it.
  • Reopen the prompt after rate-limit rejection, failed authentication and when
    a password lock expires.
  • Route blocked pre-login actions through one prompt-and-hint path, with a
    reconnect hint when no dialog can be shown.

[1.8.5-beta.16] - 2026-11-03

Protection points are fractional now, and the built JARs leave git altogether.

Changed

  • Protection points are doubles, not ints. The 1.1 price curve is smooth
    (1, 1.1, 1.21, 1.331 ...), so whole points would round it away — every price and
    every fuel reward is now fractional. ProtectionBlock.points is a double, the
    protection_blocks.points column is declared REAL
    (SQLite keeps reals in the legacy INTEGER-affinity column, so existing databases
    need no migration) and is written/read via setDouble/getDouble.
  • Prices are no longer rounded. ProtectionBlock.scaledCost returns
    baseCost × growth^n as-is (was ceil(...)), clamped to MAX_COST; the repair and
    radius buttons in the GUI now show 1.21 instead of a stair-stepped integer.
  • Fuel rewards are fractional too (computePointsFromFuel → double, rounded to two
    decimals so 0.1 × 300 shows 30, not 30.000000000000004).
  • New ProtectionFormat.points(double) — the single formatter used by the GUI, the
    chat messages, /ui protection list|info and the hologram: at most two decimals,
    trailing zeros stripped, ∞ for non-finite input.

Added

  • ProtectionFormatTest (whole values, two decimals, float-noise rounding, NaN/∞),
    and ProtectionBlockCostTest rewritten for the fractional curve.

Removed

  • Built JARs are no longer tracked in git (build/libs/** purged from the whole
    history, !/build/libs/*.jar exceptions removed from .gitignore). Distributables
    come from GitHub releases; a local gradlew build still produces them in
    build/libs/.

[1.8.5-beta.15] - 2026-11-03

Protection block prices no longer double: a repair or radius upgrade now grows by a
configurable factor (1.1 by default).

Changed

  • Protection block price curve: cost = ceil(base_cost × growth_multiplier^n)
    instead of base_cost × 2^n. n is the per-block counter of previous purchases
    of that kind (repair_count / radius_upgrade_count, still stored in the DB and
    still cumulative forever). The doubled price made the second purchase of a 1-point
    upgrade cost 2, the fifth 16, the tenth 512 — for a repair that only restores
    1 % integrity that was a dead end. With the default 1.1 the first ten repairs
    cost 1, 2, 2, 2, 2, 2, 2, 2, 3, 3 points.
  • New TOML key protection.points.growth_multiplier in
    configs/UI-Protection.toml (default 1.1, guarded by ConfigRules to the
    range 1..1000). 2.0 reproduces the old behaviour, values <= 1 mean a flat
    price. A missing key in an existing config falls back to 1.1, so no migration
    is needed.
  • ProtectionConfig.getPointsGrowthMultiplier() clamps NaN/negative/< 1 input to
    1.0, and the cost helper (ProtectionBlock.scaledCost) clamps the result to
    Integer.MAX_VALUE instead of overflowing.
  • GUI lore of the radius and repair buttons shows the actual factor
    (Стоимость в очках × 1.1 каждый раз) instead of the hard-coded × 2.

Added

  • ProtectionBlockCostTest — pure-math tests for the curve: base price, ceil
    rounding, the legacy 2.0 factor, flat/degenerate factors, overflow clamping and
    monotonicity.

[1.8.5-beta.7] - 2026-11-03

Elytra wear tuning from the first review of beta.6.

Changed

  • The wear check now runs every 80 ticks (4 seconds) instead of 20, and
    chance_percent is the chance PER ROLL, so the default 0.1% is rolled once per
    4 seconds of gliding. Both the code default and
    elytra_wear.interval_ticks in configs/UI-Player.toml use 80; the config
    comment states the tick/second equivalent.
  • Durability semantics made explicit in the code, the config and the startup log:
    the item tooltip X/N gets X = min_durability (2 by default) independent of
    N
    — a vanilla elytra shows 2/432, an item with a different maximum shows
    2/<its max>. Implementation detail documented: vanilla stores the lost
    points, so the manager writes damage = N - 2 and the remaining value is 2.

[1.8.5-beta.6] - 2026-11-03

The elytra boost on jump is gone; the elytra can now tear during flight instead.

Removed

  • /ui elytraboost and the whole ElytraBoost module. Deleted
    ElytraBoostManager (SPACE-while-gliding boost, /ui togglefly state and its
    elytra_boost_disabled table), the CoreHooks elytra hooks
    (setElytraBoost/isElytraBoostEnabled/toggleElytraBoost), the
    ui.command.elytraboost permission, the subcommand registration in
    PluginReloadCommand, the MiscSubcommand.elytraBoost handler, the help line,
    the misc.fly_enabled/misc.fly_disabled messages and the
    anticheat.movement.elytra.boost_check_window_ms key.
  • The anti-cheat ElytraCheck no longer tries to whitelist a plugin boost (its
    reflection into ElytraBoostManager was the only reason that class was loaded
    sof...
Read more

1.8.5-beta.1

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:38
v1.8.5-beta.1

UltimateImprovments 1.8.5-beta.1

The whole 1.8.5 line since the last published build (1.8.5-alpha.44). Two bugs
made this the release that had to ship: an infinite redstone-block duplication
through wirelessly activated pistons, and a false fly-hack kick from the
levitation charm. Both are fixed below, together with the wireless-redstone
binding/ghost-link family that made the feature look broken, a chat-limits false
positive that rejected decorated messages, the concrete-bucket lifecycle fixes, the
Remote Detonator and the turret line-of-sight whitelist. In-game verification of the
whole line is still pending — hence beta.

Critical fixes in this build

  • Exploit: infinite redstone blocks from a wirelessly activated piston. A
    wireless piston was powered by placing a real redstone block next to it and taking
    it back on retract. The block stayed in the world as long as the piston was
    extended, so any player could mine it and keep it — and breaking it left the piston
    stuck extended. Pistons are now triggered through the vanilla piston block event
    (PistonBaseBlock.TRIGGER_EXTEND / TRIGGER_CONTRACT via ServerLevel#blockEvent):
    real movement, real sounds, BlockPistonExtendEvent/BlockPistonRetractEvent still
    fire, and nothing is ever written into the world.
  • Levitation charm no longer gets players kicked for flying. The chestplate
    jetpack wrote raw velocity every 2 ticks, which the client never simulates, so the
    movement anticheat punished the ascent as fly-hacking. It now grants the real
    vanilla Levitation effect (amplifier 5 = 0.05 × (5 + 1) = 0.30 blocks/tick ≈ 6
    blocks/s — exactly the old lift), invisible and removed with the leftover momentum
    the moment the key is released.
  • Wireless redstone could be bound only once. After the first Shift + RMB link
    the first device stayed selected, so every later click silently chained onto that
    OLD source and a second, unrelated pair could not be bound at all; a destroyed
    source produced ghost links to air and an endless “already bound” prompt. Binding
    now ends with the second click, prompts the next step explicitly, expires after
    60 s and reports already linked instead of silently re-adding.

Changelog since 1.8.5-alpha.44

Security

  • Wireless piston duplication (see Critical fixes) — the fake power block is gone.

Added

  • Remote Detonator (UI-Items) — flint-and-steel base, 128 uses. Shift + RMB on
    TNT binds it (one binding per item, stored in the item's persistent data, so it
    survives restarts and travels between inventories), an empty Shift + RMB clears
    it, RMB detonates: the block is consumed and a primed TNT with the configured
    fuse takes its place. Never usable as a lighter. Crafter-only recipe,
    [remote_detonator] config (fuse_ticks, cooldown_ms, max_distance,
    cross_world, max_uses, sounds), bilingual name/lore/messages, also available
    in /ui menu.
  • turret.ignore_blocks (UI-Combat) — turret line-of-sight whitelist. The default
    covers every glass block and pane (34 materials), so a turret behind glass targets
    and fires; unknown names are skipped with a warning, /ui reload applies changes.
  • Concrete bucket (UI-Items) — new Crafter recipe (clay/smooth basalt/tuff,
    blackstone/water bucket/red sand, dripstone block/soul sand/packed mud), crit
    particles that mark the liquid cement instead of the hardened block, and a whole
    [concrete_bucket] config section (delay, block, tint biome, particle with its
    count/offset/interval, refusal sound) instead of hardcoded values.

Fixed

  • Wireless links outlived their devices. Explosions, pistons, world edits and
    block replacement never fire BlockBreakEvent, so stored links kept pointing at air
    and were reported (and re-saved) forever. Dead links are pruned — memory, chunk
    ticket and DB row — the moment a player interacts with the device.
  • /ui reload registered a second wireless listener — every event ran twice
    (double cascade activation, duplicated action-bar messages). The old instance is
    unregistered now.
  • Wireless-driven devices stayed frozen after /ui reload or disable — a lit
    lamp, an extended piston, a stuck observer pulse, dust at power 15. They are
    released to their vanilla state now (direct block writes, no cascade), and devices
    still fed by real redstone are left untouched.
  • A wireless lamp no longer flickers the dust next to it — turning one off drove
    every adjacent wire to 0 even when another source powered it, adding a false
    falling/rising edge for repeaters and comparators downstream. A wire is cleared only
    when nothing else feeds it.
  • A runaway link network can no longer stall the tick — cascades are bounded by
    depth (24) and devices touched (512), with one console warning per cascade.
  • Duplicate rows in wireless_links are gone — links are stored in a canonical
    order and mirrored rows from older builds are collapsed once at startup.
  • Linked devices moved by a piston keep their runtime state — the re-entrancy
    guard and cached observer flag now follow the block instead of being dropped.
  • Chat abuse limits no longer reject decorated messages — the CAPS and
    random-soup metrics ran on raw MiniMessage, so tags such as
    <gradient:#e1ff00:#00ff55> were read as machine-made text and a valid message was
    blocked as “random text 100%”. Metrics now run on the visible text.
  • Concrete bucket: the whole poured puddle hardens — only the source block was
    converted, because the flow event fires while the destination is still air; flow
    tracking is group-based now.
  • Concrete bucket: the original biome is restored on hardening — the tint biome
    under the liquid no longer leaks into the world save.
  • Concrete bucket: pours survive a restart — tracked water lives in the
    concrete_bucket_water table with its original start time, so a restart no longer
    leaves gray water that never hardens.
  • Concrete bucket: the liquid cannot be taken away — bucket filling, glass
    bottles, sponges and dispensers are blocked (a dispenser bypassed every player
    event), each blocked attempt plays a dull refusal sound.

Changed

  • Custom enchantments moved from the datapack into RegistryEvents — the 18
    enchantments are registered in the bootstrap phase, so a typo invalidates the build
    instead of silently dropping an entry while plugin code keeps referencing ui:<id>.
    Keys are unchanged, so no item migration is needed. Fifteen of the eighteen item
    tags are gone (twelve inlined, three now use the built-in
    #minecraft:enchantable/durability); the three that are unions of vanilla tags keep
    their tag files — a union cannot be materialised before the registry freezes, which
    the live server confirmed.
  • Wireless signals respect real redstone — piston retraction and dust clearing
    skip anything a real source still powers, so the wireless line never fights vanilla.

Compare: v1.8.5-alpha.44...v1.8.5-beta.1

Install

  1. Download UltimateImprovments-1.8.5-beta.1-jars.tar (21 JARs).
  2. Unpack into plugins/, replace the old UI-*.jar files.
  3. Restart the server. Requires Paper/Purpur 26.3+, Java 26+.

SHA256 of the archive:
7720fac07447da20abfd1d07d3596a679c06551de43c3b64746d01f1fec1a4f5

Notes for existing installations

  • Wireless links are re-normalised on first start: mirrored rows left by older builds
    are collapsed (logged as Collapsed N mirrored link row(s)). No manual DB work.
  • Devices driven by wireless power are released on /ui reload and on disable, so a
    lamp/piston/dust that was active during the restart returns to its vanilla state.
  • New config keys come from the bundled TOML templates ([concrete_bucket],
    [remote_detonator], turret.ignore_blocks); values you already changed are never
    overwritten.
  • Custom enchantments are registered through RegistryEvents now; keys stay ui:*,
    so existing items need no migration. With datapack.enabled = false the three
    union-based enchantments (blunting, self_destruct, vulnerability) are skipped with a
    warning.

1.8.5-alpha.44

1.8.5-alpha.44 Pre-release
Pre-release

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:38
v1.8.5-alpha.44

UltimateImprovments 1.8.5-alpha.44

The whole 1.8.5 alpha line since 1.8.5-alpha.1. Fortress-grade chat
hardening (the forged-line exploit is gone, plus configurable abuse limits,
cooldown, duplicate guard, Cyrillic/Unicode modes and an anti-forgery hex
prefix), the punishment rework (persistent block dialog, unified pardon,
full punishment logs), the kit system with per-kit and global cooldowns,
scoreboard nicknames, infinitely growing sculk with contact hazards, meteor
and multimeter fixes, and a batch of structure-assembly and config/messages
polish. In-game verification of the newest features is still pending — hence
alpha.

Changelog since 1.8.5-alpha.1

Added

  • Chat abuse limits — [chat.limits] (UI-Chat) — every player message is
    checked independently of chat.enabled (these are protections, not
    formatting); CONSOLE/TERMINAL channels are exempt because they run trusted
    staff commands. Keys: max_lines (3), max_chars (512, counted across all
    rendered lines, ellipsis included), max_caps_percent (50 — the share is
    checked whatever the message length, only messages of at most
    caps_ignore_max_chars = 8 characters skip it), max_entropy_percent (50 —
    share of characters inside random-looking tokens), cooldown_ms (1000),
    duplicate_window_ms (2000), duplicate_percent (95),
    block_cyrillic (false), block_unicode (false) and
    bypass_permission (ui.chat.limits.bypass). Length/line limits truncate
    with …; CAPS, random-soup, Cyrillic, Unicode and duplicate violations
    cancel the message and reply with a configurable RU/EN warning.
  • Chat cooldown, Cyrillic and Unicode modes (UI-Chat) — the cooldown stores
    the timestamp only for a message that passes every check, so a rejected
    message does not eat the slot, and its "slow down" notice is throttled to one
    per second per player. block_cyrillic matches by UnicodeScript.CYRILLIC;
    block_unicode is the stricter "ASCII only" mode that rejects any code point
    above U+007F (Cyrillic, emoji, exotic symbols, invisible spaces).
  • Duplicate message guard (UI-Chat) — a message similar enough to the last
    ACCEPTED message inside the window is dropped. Similarity is normalized
    (trim, collapsed whitespace, case-folded) Levenshtein on code points:
    100 * (1 - distance / maxLength), so one changed letter in 20 characters
    scores 95% and unrelated text scores 0%. Blocked attempts never become the
    reference, so a spammer cannot shift it; the notice and its console log are
    throttled together.
  • /ui punish block — persistent modal-dialog account lock (UI-Punish) —
    a new soft punishment next to ban/mute/kick/warn: the player is never
    kicked, stays online behind a native Minecraft dialog and cannot move,
    interact, chat or run commands until the block expires or an admin lifts it.
    Reuses the punishments table (type = 'block'), survives restarts and
    reconnects, re-opens on join and on close (period punish.block. reopen_interval_ticks), supports -time/-permanent/-ip/-hw, and its
    Close/ESC path re-reads the record server-side (ESC is disabled, the
    duplicated Close button is gone).
  • /ui punish logs + purge (UI-Punish) — actionlist became logs (no
    alias): a clickable type filter and pagination (view [-p <page>] [-t <type>], 8 rows per page), plus purge -a [-confirm] and purge -t <1h|30m|7d|2w>. Events live in the new append-only punishment_log table:
    issuing writes punish, a moderator lifting writes pardon, automatic
    expiry writes expire with actor SYSTEM — and a purge never touches the
    rows that actually enforce anything.
  • Unified /ui punish pardon (UI-Punish) — the old unban / unblock / unmute / unwarn handlers are gone (~600 lines of duplicated logic). One
    PardonManager resolves the target (nick, offline:<nick> or all),
    collects every active record, checks warn ownership, applies a confirmation
    policy and invalidates the mute cache / open block dialog by record id
    (so alts punished through -ip/-hw scopes are freed too).
    pardon <ban|mute|block|warn|all> <player|all> takes -r:<reason>,
    -id:<N>, -s (silent), -dry (preview) and -confirm. -r ("reason") is
    now mandatory for issuing and lifting a punishment.
  • Audit columns for punishments (UI-Punish) — punishments and warns
    gained removed_at / removed_by / remove_reason (with per-column ALTER
    TABLE migration); automatic expiry writes SYSTEM / expired.
  • Kit system — /ui kit (UI-Other) — named 27-slot item sets stored in a
    dedicated kits table (shulker-box layout, ItemStack.serializeAsBytes +
    Base64), dialog-driven management for players and console forms for every
    action (give [-f], create/edit/delete, list, preview).
  • Kit cooldowns (UI-Other) — per-kit kits.cooldown_seconds with the
    kit_cooldowns table (survives restarts), the server-wide
    kits.global_cooldown_seconds with kit_global_cooldowns, /ui kit cooldown, /ui kit globalcd, /ui kit resetcd and the new /ui kit resetglobalcd (stops a running global timer while keeping the configured
    value; permission ui.command.kit.resetglobalcd).
  • Scoreboard nicknames (UI-Core/UI-Other) — /ui scoreboardnick "<text>"
    (MiniMessage) shows through the new %player_scoreboard_nick% placeholder
    (per-player resolution, falls back to the real name), off disables it, and
    a forbidden-syntax filter protects the scoreboard from broken tags.
  • GSit /spin guard (UI-Guard) — opt-in interception of /spin (and the
    /gspin alias) before GSit runs, against the version-mismatch invisibility
    bug: either it requires ui.gsit.spin, or it reports the mismatch instead of
    running.
  • Infinitely growing sculk (UI-World) — catalysts pulse the vanilla bloom
    once per second through Paper's SculkCatalyst#bloom, bloom origins are
    limited to the six face-adjacent blocks (random face each pulse), and
    [sculk.worlds] adds independent whitelist/blacklist filters (blacklist
    always wins) with /ui sculk control commands.
  • Sculk contact hazards (UI-World) — standing on grown sculk applies the
    debuff configured per block (sculk.vein, sculk.block, sculk.catalyst,
    shrieker/ sensor …), refreshed while the player stays; wither durations are
    tick-aligned so the effect actually damages, and the bypass requires an
    explicit grant (wildcards and OP no longer grant immunity).
  • Shared MultimeterApi (UI-Scoreboard/UI-Shared) — the generic multimeter
    readout now needs SHIFT+RMB (plain RMB keeps the vanilla block interaction),
    the "can't measure" error is composed in one place, and both the readout and
    the error are covered by tests.
  • Adaptive light structures (UI-MBS/UI-Energy) — a one-shot item frame on a
    waxed copper bulb assembles the whole connected bulb/junction component into
    one light structure (replacing the unfinished multiblock lamp).
  • CER output buffer on the copper port (UI-Energy) — the compact reactor
    feeds consumers directly through its copper port, so a battery-less
    reactor → cables → consumer network works.

Changed

  • Every rendered chat line carries the prefix (UI-Chat) — the message is
    never inserted as one blob: it is split into single lines (real Unicode line
    separators AND <newline>/<br> tags) and every line is rendered through
    the full channel format, pings are processed per line and de-duplicated.
    ChatText.escapeMiniMessage also doubles backslashes (a player backslash can
    no longer cancel the escape of a following <) and strips legacy § codes
    together with their letter.
  • Hex brand colour for the stock chat prefix (UI-Chat) — the stock
    ᴄʜᴀᴛ / ᴄᴜᴄᴇ prefix is now <#32c800> instead of <green>: a forged line
    written in plain green is visibly a different shade. Existing installations
    are migrated only when the format still starts with the stock
    <green>ᴄ prefix (manual recolours are left alone).
  • Punishment presentation (UI-Punish) — the remaining time is shown
    everywhere (Time remaining » %duration%) and permanent punishments render
    as a red "Permanent" label (PunishmentMessages#durationLabel).
  • Config salvage reports are colour-coded (UI-Core) — ✔ healthy is green,
    ✗ failed is red, ⚠ is yellow, everything else is plain info, instead of
    painting every line as a warning.
  • Guard texts moved into the RU/EN messages config (UI-Guard) — redstone
    guard alerts, the packet-guard kick message, proxy no-permission message,
    emergency entity cleanup, server-overload alerts and the /ui redstone /
    /ui codepane output now come from UI-Guard.toml messages sections with
    placeholders, instead of hardcoded Russian strings.
  • DFC reactor tick cost cut (UI-Energy) — live barrel states, a cached fuel
    check and a flat audit index replace repeated Block#getState() snapshots
    (ReactorManager.tick dropped from ~7.7 ms to a fraction of the server tick).
  • Structure assembly priority (UI-MBS/UI-Energy) — the full NBT template
    check runs before adaptive single-block structures, so a frame on a partly
    built reactor shows the reactor's fix list instead of assembling a lamp, and
    a nearby build no longer counts as "already assembled" (the clicked frame's
    own template center is resolved and volume-intersecting matches are skipped).
  • Batteries are one shared pool per cluster (UI-Energy) — an assembled
    battery cluster owns a single BatteryPool instead of per-block charge, so
    the multimeter shows the same value on every block and the far side discharges
    correctly.
  • Generators consume their item frame (UI-Energy) — the blast-furnace
    generator now breaks and drops its trigger frame like every other structure.

Fixed

  • Forged chat lines via <newline> (UI-Chat) — a player could send
    <newline>[Server] Restart in 5s and the second line rend...
Read more

1.8.5-alpha.1

1.8.5-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:39
v1.8.5-alpha.1

UltimateImprovments 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: capacity energy.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 new battery_modes table.
    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_reactors table, 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_radius on 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 fire BlockBreakEvent — explosions,
    pistons, plugin setType — 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 — StructureTemplate now
    accepts a palette id key as a fallback for the vanilla Name, 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-en and UI-Datapack-ru. The content is identical
    (enchantments, advancements, recipes, structures, worldgen); only the display
    names and descriptions are translated. The new datapack.lang key in
    UI-Datapack.toml ("en", "ru" or "auto" — follows messages.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 list and 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_ticks 100 → 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 reports OUTPUT_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 from Block#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 real BlockRedstoneEvent of 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) from structure_markers and,
    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 under config.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 as UI-<Addon>-broken-<N>.toml and 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): push charges
    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 har...
Read more

1.8.3-release.1

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:39
v1.8.3-release.1

UltimateImprovments 1.8.3-release.1

The first full (non-pre-release) family release. Everything in 1.8.3 —
the DFC cinematic startup / stall & manual shutdowns / self-destruct protocol,
Unbreaking on plugin durability wear, multi-reactor support and the rest —
passed the full in-game test checklist on the test server.

Highlights

  • Multi-reactor support (D.F.C) — assemble as many reactors as you want,
    each with its own ID, independent ticking, damage reports and persistence.
  • Soft /ui reload — real onDisable/onEnable for all 20 addons on
    Paper 26.3+ (runtime JAR loading is blocked there), without unloading.
  • New update flow — /ui update [tag] downloads release JARs into
    UltimateImprovments/update/, /ui swapjar moves them into plugins/
    (applied on restart; manual instructions when JARs are locked on Windows).
  • Unbreaking works everywhere — plugin durability wear (AoE, veinminer,
    treecapitator, degradation, levitation, flight, item stealing, sunburn)
    rolls the vanilla chance tables.
  • Self-destruct owns the reactor — the normal startup cannot run
    alongside the protocol anymore.

Fixed since 1.8.3-alpha.8

  • Chat filter word patterns (*word) failed to compile — invalid Unicode
    property escape; the words were silently dropped from the filter.
  • Custom-enchant wear ignored the Unbreaking enchantment (stale registry
    constant on Paper 26.3 — getEnchantmentLevel always returned 0).
  • /ui reload reloaded 0 of 20 addons — runtime plugin loading is blocked
    on Paper 26.3+; replaced with the soft lifecycle cycle.
  • The startup sequence could run alongside the self-destruct protocol.
  • Duplicate ui.enchant.itemstealing.steal permission declaration
    (UI-Enchant + UI-Other) — "already registered" warning at startup.
  • Removed the legacy updater (/ui checkver, /ui updatejar) — it targeted
    the old repository layout and matched nothing. Module count 98 → 97.

Full changelog: see CHANGELOG.md in the repository.

Compare: v1.8.3-alpha.8...v1.8.3-release.1

Install

  1. Download UltimateImprovments-1.8.3-release.1-jars.tar (21 JARs).
  2. Unpack into plugins/, replace the old UI-*.jar files.
  3. Restart the server. Requires Paper/Purpur 26.3+, Java 26+.

SHA256 of the archive:
92e56f075af9656bde9877733504ad6b1d42824db5cd5755c937b69db30cbebe

1.8.3-beta.4

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:39
v1.8.3-beta.4

Paper plugin family, api-version 26.3 (Paper/Purpur). Beta channel — feature-complete; verified by build + unit tests, in-game verification on the test server is pending.

Changes since 1.8.3-alpha.7

Added

  • Custom enchantments in random loot — all 18 ui:* enchantments joined the minecraft:enchantment/on_random_loot tag (it previously contained only wind_burst/mending), so loot rolls (enchant_randomly, e.g. end village towers) can now produce them, matching the other four spawn tags (enchanting table, mob equipment, villager trades).
  • /ui enchant confirm / /ui enchant cancel — the 255 level ceiling is gone; a give above enchant.max_level (default 10) is parked per-sender and must be confirmed within 60 seconds. The warning message has clickable confirm/cancel hints. take is not gated.
  • Namespaced enchantment ids — arguments, tab-complete, the success message and /ui enchant check use namespace:name form (minecraft:mending, ui:aoe); bare names still resolve.
  • Error 019 — ambiguous enchantment name (/ui enchant): a bare name registered in several namespaces (e.g. ui:aoe + test:aoe) is rejected with the list of ids — specify one explicitly. The text is configurable in both languages: [messages.enchant] / [messages_en.enchant], key ambiguous_enchant.

Changed

  • All custom enchantment levels capped at 10 — the datapack max_level and the Java MAX_LEVEL constants are in sync now (six charms were 255, magnet/lava_walker were 16, AoE raised 8 → 10 with a 21×21×21 scan cube). This fixes mobs/villagers/loot spawning absurd levels; existing higher items keep working (mechanics clamp at read).
  • enchant.max_level is the confirm threshold, not a cap (rule bound widened; template updated).
  • Curse of Disappearance ×10 stronger — 0.01% vanish chance per second per level (level 10 = 0.1%/s), so the curse is actually noticeable.
  • /ui enchant check reworked — full enchantment ids, fixed a broken skip that duplicated custom rows, and five previously invisible charms (repairing, lava_walker, blunting, vulnerability, disappearance) now show.

Installation

  1. Drop all 21 UI-*-all.jar from the attached archive into the server's plugins/ folder.
  2. Restart the server (Paper/Purpur 26.3). The UI-Datapack is installed automatically (override mode by default — delete datapacks/UI-Datapack from the world when upgrading from check-override setups).

Archive: UltimateImprovments-1.8.3-beta.4-jars.tar — 21 JARs, 18.7 MB (uncompressed tar, JARs are already ZIP).
SHA256: 26b2f7a9dd808b8190a2f8e6ef8ae08682d78ee98c4852e457856202ff865d07

Full changelog: CHANGELOG.md

1.8.3-beta.3

1.8.3-beta.3 Pre-release
Pre-release

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:39
v1.8.3-beta.3

Changelog

All notable changes to the UltimateImprovments plugin family are documented
in this file. The format is based on Keep a Changelog.

[1.8.3-beta.3] — since 1.8.3-beta.2 (2026-09-27)

Added

  • lava_walker charm (Lava Walker) — Frost Walker for LAVA, levels 1-255,
    boots only. Lava under the wearer's feet temporarily turns into obsidian:
    radius = level (1 → 1×1, 2 → 3×3, ... hard-capped at 16 → 31×31); created
    blocks melt back to lava after a random 20–45 s (frosted-ice style) and the
    block the player stands on never melts first. Both crust layers (below the
    feet and at the feet — for wading) are converted. Offered in the third
    enchanting-table slot (same min-cost gate as the other charms), available in
    villager trades and mob equipment, NOT in random loot. Sneaking disables the
    conversion; no fire protection is granted — the first step into fresh lava
    can still ignite you. The melt registry persists across restarts in the
    shared family SQLite database (lava_walker_melts table: position + exact
    original lava data + wall-clock deadline; autosave every 5 min + save on
    shutdown), so a melting plate comes back to lava even after a restart — and
    the melt restores the captured lava state verbatim (a source stays a source,
    a flow keeps its level) with a forced physics update, so the restored lava
    starts flowing immediately. Every created block costs the boots 1 integrity
    use (a max-radius sweep can cost 961 uses).
  • armor_trim_effects feature — configurable potion effects based on the
    armor TRIM MATERIAL (the smithing-table ingot/crystal, i.e. the trim color),
    not the trim pattern. Units under armor_trim_effects name one or more trim
    materials (amethyst/copper/diamond/emerald/gold/iron/lapis/netherite/quartz/
    redstone/resin — registry-resolved, datapack materials work), a count rule
    (EXACT: effect level = number of matching pieces; MIN: activates at count
    pieces with a fixed level), the effect, amplifier base, duration/interval
    and particles/ambient/icon flags (all default off). The default set covers
    ALL 11 trim materials with themed effects (netherite → fire_resistance,
    iron → resistance, diamond → absorption, gold → haste, emerald →
    hero_of_the_village, amethyst → regeneration, copper → water_breathing,
    lapis → night_vision, quartz → speed, redstone → strength, resin →
    slow_falling) under the MIN rule with count 1: the level never grows with
    more pieces. Multiple units work in parallel; effects expire naturally when
    pieces are removed.
  • Armor charms on the elytra — Flight, Levitation, Igniting and the Curse
    of Vulnerability accept the elytra in addition to their armor pieces: the
    enchanting table / anvil / /ui enchant take it (datapack item tags), the
    PDC failsafe syncs the elytra (chest) slot, and Igniting / Vulnerability
    effects read the elytra there. Flight / Levitation already read the chest
    slot, so they work on a worn elytra as-is.

Changed

  • Flight is incompatible with Repairing on the chest slot — if the worn
    chestplate (or chest-slot elytra) carries the Repairing charm, the flight is
    revoked and not granted while it stays on: that is the piece paying the
    flight engine's own drain. Repairing on other armor pieces is fine — the
    chestplate itself still visibly wears down.
  • Attack AoE has no damage falloff and caps at radius 10 — every cleaved
    target takes the same force as the original hit; the radius equals the
    charm level capped at 10 (the level where the old falloff formula would
    have reached zero anyway).
  • Container Stealing: levels 1-10 and a steal roll — level N = N×10%
    chance the charm works (level 10 = always). On a failed roll the break is
    fully vanilla: the container drops empty and its contents spill out —
    nothing is ever destroyed. Shulker boxes are excluded (vanilla already
    keeps their contents; stealing them would double-preserve the loot).
  • Lava Walker costs boots durability — every created obsidian block costs
    the boots 1 integrity use (a max-radius 31×31 sweep can cost 961 uses).
  • Flight now strains the whole armor set — while actively flying, every
    worn armor piece loses 1 use of integrity per second (previously only the
    charming chestplate paid, the rest of the set flew for free).
  • Flight now costs integrity while gliding too — planning with a
    charmed elytra drains 1 chestplate use per second, same rate as flying:
    the glide is the same engine and no longer travels for free.
  • Levitation now has an integrity cost — actively boosting (jump key
    held) drains 1 use per second from the charming chestplate; releasing the
    key is free. Cheaper than Flight, fitting its lower value. Previously
    the jetpack was entirely free.
  • /ui enchant gains lava_walker in the custom-enchantments config list.

Fixed

  • Lava Walker could suffocate the player it helped — the conversion swept
    the player's own feet and head layers, placing solid obsidian INSIDE the
    player (vanilla suffocation damage + trapped until the melt). The feet and
    head blocks of the converting player are now skipped; only the block they
    stand ON is converted.

  • Lava Walker melt could trap or lag behind the player — the "don't melt
    under a player" check used a stale cache of the last conversion center: a
    player could walk off and the block stayed un-melted forever, or a plate
    melted under a player who walked onto it from the side. The sweep now does
    a live bounding-box occupancy check of all players in the world.

  • Lava Walker doubled its own conversion — the move listener was
    registered twice in the module init (manually and inside register()),
    running the conversion pass twice per event. Removed the manual one.

  • Container Stealing bypassed protection plugins — the listener ran at
    NORMAL priority and wiped the container contents immediately: a protection
    plugin (WorldGuard, etc.) running later could cancel the break, leaving a
    LOOTED container in place. The listener now runs at MONITOR (after all
    protection checks) and performs the snapshot/wipe/drop on the next tick,
    when the break decision is final — a cancelled break keeps the container
    fully intact.

  • ConcurrentModificationException in the unbreakable breaker sweep —
    the per-tick maintenance task called cleanup() (which mutates the map)
    while iterating activeBreaks with its iterator open; the first session
    reset inside the sweep (player looked away / died / went offline) threw a
    CME and spammed the console. The sweep now removes entries via
    iterator.remove() and cleans the reverse map directly.

  • Container Stealing emptied the container it stole — breaking a container
    with the charm dropped a plain empty container item while the contents were
    stored in a plugin-only PDC blob that was never read back (breaking it again
    spilled nothing, placing the stolen container gave an empty chest: the items
    vanished). The dropped container now carries its contents in vanilla
    block-state NBT (BlockStateMeta snapshot of the broken block — same format
    as ctrl+pick-block), so the item tooltip preview shows the stored items and
    placing the container restores them natively, surviving restarts and
    datapack outages. Containers stolen before the fix still restore their
    contents from the legacy PDC blob when placed.

    Jars in the tar archive no more be gzipped.

1.8.3-beta.2

1.8.3-beta.2 Pre-release
Pre-release

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:39
v1.8.3-beta.2

[1.8.3-beta.2] — since 1.8.3-alpha.4 (2026-09-27)

Fixed

  • ConcurrentModificationException in the unbreakable breaker sweep —
    the per-tick maintenance task called cleanup() (which mutates the map)
    while iterating activeBreaks with its iterator open; the first session
    reset inside the sweep (player looked away / died / went offline) threw a
    CME and spammed the console. The sweep now removes entries via
    iterator.remove() and cleans the reverse map directly.

Changed

  • Unbreakable breaker sessions reset on death, gamemode change, quit and
    shutdown
    — accumulated damage no longer survives dying, switching
    gamemode (any source: client command, /gamemode, plugin API) or a
    plugin disable / /ui reload / server stop. The new
    UnbreakableBreakerManager.shutdown() cancels the tick task, unregisters
    listeners and clears all in-memory sessions (sessions were never
    persisted — this just makes it explicit).

1.8.3-beta.1

1.8.3-beta.1 Pre-release
Pre-release

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:39
v1.8.3-beta.1

Major architectural overhaul. (Will be incompatible with the previous release.)
You can download the archive below, which contains the core and the official plugin extensions.