Skip to content

1.8.5-release.1

Latest

Choose a tag to compare

@rizer001 rizer001 released this 15 Nov 12:50
· 109 commits to main since this release
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, including the
    advancement-parent rewrite — and then written atomically.
  • datapack/hash.txt caches the build. It stores
    <sha256> <zip name>; the archive is built deterministically (entries sorted by
    name, fixed 2000-01-01 entry timestamp, fixed deflate level), so an unchanged
    pack produces the same bytes and is not rewritten at all. A missing hash file, a
    different hash, a damaged/edited zip or a switched language rebuilds it and
    rewrites both files.
  • Old extracted folders are removed automatically on the first start after the
    update, together with the other language variant and any .tmp leftovers — two
    copies of the same pack id can never be discovered at once.
  • datapack.position no longer influences the archive: it only affects the
    discovery call, so moving the pack in the stack does not rebuild it.

Fixed

  • DatapackInstaller matched the pack by a fallback only. Paper registers
    plugin packs as UI-Datapack/UI-Datapack-<lang>, while the exact-name lookup
    used UI-Datapack-<lang>; the contains fallback hid it. Both the bare id and
    the namespaced form are accepted now.

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

Changed

  • Config validation console texts are configurable in both languages.
    Every message emitted by ConfigValidator — the per-rule
    [ConfigValidator] ⚠ [ERROR]/[WARN] lines, the type/range/regex/list
    diagnostics, the summary banner and the "all values passed" line — moved out
    of the code into [messages.config_validation] (RU) and
    [messages_en.config_validation] (EN) in UI-Core.toml. The active section
    follows messages.lang, with a fallback to the other language. The legacy
    monolithic-config notice uses the same mechanism.
    Placeholders: %key%, %message%, %type%, %value%, %min%, %max%,
    %description%, %length%, %regex%, %index%, %chars%, %error%,
    %errors%, %warnings%, %dir%.

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

Added

  • configs/UI-Enchantments.toml — the custom enchantments get their own config.
    Master switch (enchantments.enabled), one enabled flag per enchantment (all
    18), and per-enchantment values that used to be constants in
    EnchantmentDefinition: name_en / name_ru (display names, so a restart can
    translate the registry tooltip), max_level, anvil_cost, active_slots
    (MAINHAND/ARMOR/ANY/...).
  • [enchantments.defaults] carries the values shared by all of them: weight
    and the enchanting-table cost curve (min_cost_base, min_cost_per_level,
    max_cost_base, max_cost_per_level).
  • Config validation for the whole section (master, defaults, 18 × 6 keys), so a
    typo — including an unknown active_slots name — is reported instead of being
    silently ignored.

Changed

  • Enchantments are no longer a datapack part. datapack.modules.enchantments
    and datapack.disabled_enchantments are gone; the pack always copies the
    enchantment item tags (ui/tags/item/, minecraft/tags/enchantment/) because
    the registry needs them. Both legacy keys are still honoured as a fallback for
    installs that have not migrated yet.
  • enchant.custom_enchantments removed from UI-Enchant.toml. The list only
    fed tab-complete and had already drifted from the registry (15 entries instead
    of 18 — the three curses were missing). Tab-complete and /ui enchant now read
    the real list from EnchantmentDefinition through Enchantments.IDS, showing
    only the enabled ids.
  • datapack.enabled=false no longer switches custom enchantments off — they are
    registry entries, not pack content. enchantments.enabled is their switch. A
    warning is logged when the pack is off while tag-based enchantments are on.

Runtime

  • New com.ultimateimprovments.enchant.Enchantments (ui-core): master/per-id
    checks, per-enchantment typed getters and the active_slots parser used by the
    bootstrap; the module gate now prunes the effect engine of a disabled
    enchantment from the same source.

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

Added

  • configs/UI-Advancements.toml — the achievement system gets its own config.
    43 custom achievements, each with its own enabled switch plus the tunables
    that were compile-time constants: kaboom.required_damage (1000 HP),
    woodcutter_at_full_throttle.goal/duration_seconds (7200 / 1 h),
    let_me_teleport.goal/duration_seconds (60 / 1 min),
    out_of_memory.threshold_percent (95), server_not_responding.freeze_seconds
    (10). advancements.enabled is the master switch.
  • datapack.position — top (default) or bottom, i.e. whether the bundled
    pack wins or loses conflicts against the world's own datapacks.

Changed

  • Achievements are no longer a datapack part. datapack.modules.advancements
    is gone: the pack always copies ui/advancement/ and the new per-achievement
    filter decides what stays. The legacy key is still honoured as a fallback for
    advancements.enabled so existing installs keep their intent.
  • A disabled achievement disappears from the tree instead of leaving a hole.
    The extraction drops its JSON and re-attaches every descendant to the nearest
    enabled ancestor by rewriting the parent field, so children never fail to
    load. The module that implements a disabled achievement's trigger is not
    registered either.
  • Challenge messages show the configured numbers instead of the hardcoded
    60 / 7200 / 1 minute / 1 hour.

Fixed

  • The achievement module list still named BeyondSpace and ServerOverload,
    modules that no longer exist — they were silently dead entries.

Notes

  • Advancements are not a Minecraft registry: Paper exposes no
    RegistryEvents.ADVANCEMENT (verified against paper-api-26.3.build.249), so
    there is no runtime registration API to migrate to. They stay datapack JSON and
    are filtered at bootstrap, which is why every achievement toggle needs a restart.
  • Config validation covers the whole new section (43 booleans plus the ranges of
    every tunable), so a typo is reported at startup.

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

Fixed

  • Structures and the airdrop loot table ignored the datapack toggles.
    ui/structure/* and ui/loot_table/* matched no part prefix, and files that
    match no prefix are always extracted — so worldgen: false and
    loot_tables: false still shipped the airdrop chest, the enchanted room, the
    end village and their loot. They now belong to the new structures part.
  • Vanilla tag overrides were ungated too. minecraft/tags/item/* and
    minecraft/tags/mineable/* had the same hole and now have the vanilla_tags
    part.
  • datapack.enabled: false still registered 12 custom enchantments. Their
    modules were gated off, so the enchanting table handed out entries with no
    effect behind them. The registry is now skipped entirely when the master
    toggle is off.
  • The pack was looked up by substring. DatapackInstaller accepted any pack
    whose name contained UI-Datapack; it now matches the registered id first and
    keeps the substring search only as a fallback.

Added

  • datapack.disabled_enchantments — a list of custom enchantment ids to
    leave out (["flight", "veinminer"]). An entry removes both the registry
    entry and the plugin module implementing it, so an unwanted charm costs
    nothing at runtime. Unknown ids are reported with the list of valid ones.
  • datapack.modules.structures and datapack.modules.vanilla_tags — the
    two parts above can now be switched independently of worldgen,
    loot_tables and enchantments.
  • Config validation for datapack.* — booleans, the lang enum
    (en/ru/auto) and the disabled-enchantment list are checked at startup
    instead of a typo silently falling back to the default.

Changed

  • One part registry instead of three copies. DatapackParts is now the
    single table of parts and path prefixes, shared by the bootstrapper (copies
    the subset out of the JAR) and DatapackModules (gates the code modules).
    A new part is a one-line change and the two sides cannot drift apart.
  • Readable comments in UI-Datapack.toml. worldgen was documented as
    "World name." and dimension_limits as "Limit."; every part now says what it
    covers and whether a restart is needed.

[1.8.5-beta.44] - 2026-11-14

Fixed

  • The bolt bounces off water and lava as if it were a wall. Anything that
    was not isAir() counted as solid, and water has hardness 100. New
    PlasmaPhysics.isPassable treats air and fluids alike for the raycast,
    escape and ricochet placement.
  • Block piercing ignored claims. block.breakNaturally() never asked
    CoreHooks.isBlockProtected, so a shot dug through a protected region.
    Protected blocks now ricochet the bolt.
  • Grazing hits could park or kill the bolt. When Block.getFace returned
    null (diagonal neighbour) the face was guessed from the dominant axis; the
    ricochet position could land inside the next block, so escapeToAir shoved
    the bolt up to two blocks forward or it silently fizzled. Positions are now
    validated and recovered along the face normal, and every substep escapes an
    embedded start before casting.
  • Entity ricochets bypassed the bounce budget and accelerated without
    limit.
    They now share MAX_BOUNCES (colour darkens accordingly), and the
    ×1.1 boost is capped at MAX_SPEED_CAP = 2.4 so a mob pile cannot drive the
    bolt into MAX_SAFE_SPEED and the explosion path.
  • Fast bolts flew through entities. The hit box was only checked at the end
    of the whole step; the segment is now sampled every 0.75 blocks (up to
    MAX_ENTITY_PROBES). The bolt also continues from the real contact point
    instead of snapping back to the tick start.
  • The shooter could hit themselves with their own ricochet after the 2 s
    immunity. The owner is now never damaged by their bolt.

Changed

  • Photon Cannon damage 6 → 8 HP (4 hearts) and cooldown 80 → 60 ticks.
    At 6 HP / 4 s the DPS was 1.5 (bow ~20), so the cannon read as weak next to
    the Shoker (6 HP + Slowness 255 on the same cooldown).
  • The trail is drawn along the travelled segment (one dust every 0.6
    blocks, max 12) instead of a single particle per tick, which left ~1.2-block
    gaps at 24 blocks/s and was invisible once the colour went nearly black.

[1.8.5-beta.43] - 2026-11-14

Changed

  • Piercing a block now costs half of that block's hardness instead of a flat
    0.25.
    The bolt breaks any block it has enough speed for (speed >= hardness) and pays hardness * 0.5 (PENETRATION_COST_FACTOR); a bolt that
    is too slow bounces off. Dirt, sand and gravel (hardness 0.4–0.6) therefore
    give way for ~0.2–0.3 speed each, while stone (1.5) still needs an
    entity-boosted bolt to break. Speed is floored at MIN_SPEED (0.35).
  • The old MAX_PENETRABLE_HARDNESS whitelist and RICOCHET_SPEED_RETENTION
    (already 1.0) are gone; entity piercing has its own ENTITY_PENETRATION_COST
    (0.25).

[1.8.5-beta.42] - 2026-11-14

Changed

  • A block ricochet no longer costs the Photon Cannon bolt any speed.
    RICOCHET_SPEED_RETENTION was 0.88, so the bolt slowed down with every
    bounce (1.2 → 0.49 over seven bounces, floored at MIN_SPEED = 0.35) and
    a short step per tick made it look sluggish. It is now 1.0: only pierced
    blocks (plants, hardness ≤ 0.3) spend energy, and the bolt's lifetime is
    limited by MAX_BOUNCES instead. Entity ricochets still add the ×1.1 bonus.

[1.8.5-beta.41] - 2026-11-14

Changed

  • The Photon Cannon trail fades from blue to black as the bolt runs out of
    charge.
    Dust colour and size interpolate from the familiar electric blue
    (0, 220, 255, size 2.0) to near-black (6, 4, 16, size 1.0), and the
    spark count drops to one. Charge is min(remaining lifetime, remaining bounces), so the colour also dims after every ricochet instead of staying
    bright until the bolt suddenly fizzles.

[1.8.5-beta.40] - 2026-11-14

Fixed

  • The Photon Cannon bolt no longer freezes on a block. A ricochet used to
    teleport it into the neighbouring air-cell centre (up to 4 blocks back) and
    ensureMovingAwayFromWall could re-reflect a direction that was already
    leaving the wall, sending the bolt straight back into it — the bolt then
    alternated against the same face and looked stuck. The ricochet now places
    the bolt just outside the hit face (2 cm), the outward component is topped
    up instead of flipped, and one tick may resolve up to 8 blocks along the
    flight path, so a fast bolt never hovers in front of a wall.
  • Photon Cannon damage is no longer tied to the leftover speed. It deals a
    flat 6 HP (3 hearts) per hit instead of 0.5 HP at spawn and less after
    every bounce; the bolt also pierces plants (hardness ≤ 0.3) instead of
    stopping on them.

Changed

  • Photon Cannon starts at 1.2 blocks/tick (was 0.5), keeps 88% of its speed per
    ricochet and fizzles after 8 bounces instead of orbiting inside a cave for a
    full minute. All tuning values live in PlasmaConstants.

[1.8.5-beta.39] - 2026-11-14

Changed

  • Portable Workbench texts are fully localised through the standard message
    routing (MessagesManager, RU + EN sections, English by default when
    messages.lang is not ru). Name and lore use the same fallback chain as
    every other addon message instead of reading the config directly.
  • Durability-style charge readout: lore and actionbar now include
    %percent% (Charges: 63/64 (98%)). Below portable_workbench.low_warning_percent
    (default 10%) the actionbar switches from opened to the low warning.

[1.8.5-beta.38] - 2026-11-14

Changed

  • Portable Workbench: 64 charges instead of 128, and it breaks when the last
    one is spent.
    A crafting-table item has no durability component, so the
    break is simulated in code: the stack is removed, the break sound plays and a
    particle burst (the item itself) appears; an actionbar message reports it.
    Legacy items that already have 0 charges break on the first use and items
    above the new maximum are clamped to it.
  • Every Portable Workbench setting is configurable in UI-Items.toml:
    [portable_workbench] (enabled, max_charges, cooldown_ms,
    open_sound, break_sound, break_particle, break_particle_count) and
    [messages.portable_workbench] / [messages_en.portable_workbench]
    (name, lore with %charges% / %max%, opened, broken). The item is
    reloaded by /ui reload.

[1.8.5-beta.37] - 2026-11-14

Changed

  • Experience bottles now share one model: the exact stored amount. The
    /ui expsplit bottle is the canonical charged bottle — it keeps the precise
    number of experience points the player had (PDC ui:exp_split_amount).
    The vanilla random 3–11 XP roll is irrelevant to it.
  • Anvil merge for bank bottles: two exp-split bottles in the anvil now
    produce one bottle holding the exact sum (CoreHooks.ExpBottleUser gained
    storedXp / createBottle). Mixed pairs (bank + multiplier) stay rejected,
    so banked experience can never be silently converted into a multiplier tier.
  • The legacy multiplier bottles (EXP_BOTTLE_MULTIPLIER, xN) keep working
    exactly as before — no migration, no lost items.

[1.8.5-beta.36] - 2026-11-14

Added

  • Portable Workbench — right-click opens a real crafting-table GUI and
    spends one of 128 charges, shown in the lore. Block placement is suppressed
    (the click is cancelled), an empty table refuses to open and cannot be
    recharged. The recipe (iron + leather + crafting table) is a custom recipe,
    so it can only be crafted in a Crafter block, like the other custom items.
    Name and lore are explicitly non-italic.

[1.8.5-beta.35] - 2026-11-14

Changed

  • Structure Indicator (formerly Structure Integrity Indicator) now uses a
    calibrated sculk sensor instead of a spyglass and is renamed accordingly.
    The item is the single structure-inspection tool: the branch that read
    ender-chest integrity from the Multimeter was removed, so the Multimeter
    reports cables, batteries, generators, reactors and accelerator blocks only.
    The admin menu lists the new item.
  • Entity Locator no longer writes to the chat. It is now a passive locator:
    a note whose pitch rises with proximity plus a short dust trail toward the
    nearest entity. The tick only runs for players actually holding the item and
    the default interval is 10 ticks.
  • Ore Finder scans the chunk snapshot asynchronously; the report is sent on
    the main thread afterwards. The click used to read ~98 000 blocks in one tick.
  • Metal Detector sweeps its 33×33×33 volume with a 3 000-blocks-per-tick
    budget and abandons the scan when the player walks away. The result is
    announced with a beep series that gets faster and higher the closer the
    nearest find is.
  • Mob Finder also reports creature spawners found in the chunk and warns
    when the number of hostile mobs reaches features.mobfinder.danger_threshold
    (default 8).
  • Portable Radar gained filters: Shift+RMB cycles all → hostile → players,
    and the found target glows for 5 seconds.
  • Health Meter shows an extended card: armor, attack damage, knockback
    resistance, active effects and equipment.

Removed

  • The Waypoint module: it was an empty scheduler stub that did nothing.
    Its config section and rules were dropped.
  • Unused Keys.AUTH_GUI and Keys.CHUNK_LOADER declarations (the chunk loader
    keeps its own hardcoded key).

[1.8.5-beta.34] - 2026-11-12

Changed

  • Detonator reset is now air-only. Shift + RMB in the air clears the
    binding. Shift + RMB on a non-TNT block no longer resets it: the click is
    cancelled and the new remote_detonator.shift_air_only actionbar message is
    shown (RU: «Сбросить привязку можно только Shift+ПКМ по воздуху!», EN:
    "You have to click Shift+RMB to AIR to use detonator!").
  • RMB on a block keeps the air_only actionbar hint, and Shift + RMB on TNT
    still binds/rebinds. Interactive non-ignitable blocks keep their vanilla
    behaviour.
  • Rechecked the interaction-event handling for both the detonator and Fire
    Charge after the beta.32 air-click fix: both use ignoreCancelled = false and
    check only useItemInHand() == DENY, so RIGHT_CLICK_AIR is never dropped by
    the block-result quirk. Item lore and the [remote_detonator] config comment
    now describe the air-only reset.

[1.8.5-beta.33] - 2026-11-12

Changed

  • Remote Detonator now detonates only from an air click. RMB on a block no
    longer triggers the charge; it cancels the vanilla flint-and-steel use and
    shows the new remote_detonator.air_only message in the actionbar
    (no plugin prefix). Russian default: «Взрывать детонатором можно только по
    воздуху (ПКМ)!»; English: "You have to click RMB to AIR to use detonator!".
  • Reset moved to Shift + RMB in the air. A bound detonator clears its
    binding there; an unbound one reports nothing_bound. Shift + RMB on a
    non-TNT block also clears the binding (unchanged), Shift + RMB on TNT still
    binds/rebinds. Interactive non-ignitable blocks (chests, doors, buttons) keep
    their vanilla behaviour.
  • Air-click bug fixed for the detonator too. It used
    @EventHandler(ignoreCancelled = true), which Bukkit treats as always-cancelled
    for RIGHT_CLICK_AIR (see beta.32); it now uses ignoreCancelled = false and
    checks only useItemInHand() == DENY.
  • The detonator works from either hand; durability break clears the hand that
    was actually used. Item lore defaults and the Russian/English lore config
    entries describe the new bind/detonate/reset scheme.

[1.8.5-beta.32] - 2026-11-12

Fixed

  • Fire Charge air shots were skipped because of the Bukkit air-click quirk.
    For Action.RIGHT_CLICK_AIR there is no clicked block, so
    PlayerInteractEvent initialises useInteractedBlock() to DENY, and the
    legacy isCancelled() delegates to that value. With
    @EventHandler(ignoreCancelled = true) the event was therefore always
    filtered out for air clicks, and the later manual useInteractedBlock()
    check reproduced the same false positive (cancelled=true in the debug log).
    The listener now stays at LOW with ignoreCancelled = false and treats only
    useItemInHand() == DENY as a real cancellation.
  • Debug output now prints itemDenied and blockResult separately so the air
    quirk is explicit.

[1.8.5-beta.31] - 2026-11-12

Fixed

  • Fire Charge air shots did not fire in some setups. The handler now:
    • works with the charge in either hand (the previous main-hand-only check
      silently ignored an off-hand charge);
    • treats a null PlayerInteractEvent#getHand() as the main hand;
    • lets server operators through even when LuckPerms has not resolved the new
      node yet (isOp() || hasPermission);
    • registers at LOW with ignoreCancelled = false and logs the cancellation
      state instead of silently skipping an already-cancelled event.
  • Diagnostics: [fireball] debug = false in UI-Items.toml logs every
    Fire Charge air click to the console with hand, item, cancellation, enabled,
    OP and permission state. The module also prints a startup line
    ([FireCharge] Module enabled (...)) so a stale/missing first-shot jar is
    immediately visible.
  • Config routing: the fireball root is now routed to UI-Items in
    AddonCatalog, so config repair writes/reads [fireball] from
    UI-Items.toml instead of falling back to the core view. FireCharge is
    included in UI-Items' owned-module report.

[1.8.5-beta.30] - 2026-11-12

Changed

  • Fireball shots now require the ui.fireball.use permission (registered in
    UI-Core, default FALSE, so it must be granted via LuckPerms). The check runs
    before the item/cooldown logic; players without the permission get the normal
    vanilla right-click-in-air behaviour instead of a shot. Noted in the
    [fireball] comments in UI-Items.toml.

[1.8.5-beta.29] - 2026-11-12

Added

  • Vanilla minecraft:fire_charge now shoots a fireball when used in the
    air.
    Right-click in the air consumes one charge (creative mode is free) and
    spawns a LargeFireball from the player's eyes, flying straight along the
    view direction without gravity. Right-clicking a block keeps the vanilla
    fire-placement behaviour. New module FireCharge in UI-Items, settings under
    [fireball] in UI-Items.toml: enabled, cooldown_ms (default 1000),
    speed (1.5 blocks/tick), explosion_power (1..127, default 1),
    incendiary, block_damage, self_damage (default false) and
    shoot_sound (ENTITY_GHAST_SHOOT).
  • The spawned fireball is tagged with the ui-core:fireball PDC key, so the
    EntityExplodeEvent / self-damage handlers only affect shots from this
    feature and never vanilla fireballs. Cooldowns are cleared on quit.

[1.8.5-beta.28] - 2026-11-12

Changed

  • Every /ui op, /ui deop and /ui oplist message is configurable and
    bilingual.
    80 keys now live in UI-Admin.toml under [messages.op] (Russian)
    and [messages_en.op] (English): usage lines, player/unknown/offline notices,
    the offline warning, every confirmation dialog row and button, all
    grant/revoke results, deop all tags and counters, and the whole /ui oplist
    layout text (title, totals, drift line, entry tags, hover texts, pager).
    Placeholders: %player%, %count%, %players%, %action%, %command%,
    %page%, %pages%, %total%, %online%, %listed%, %op_only%,
    %offline%.
  • New helper OpMessages resolves op.* through MessagesManager with English
    fallbacks, so an older config that has not been regenerated still shows the
    previous texts. The new message group is routed to UI-Admin in AddonCatalog
    (routeMsg("UI-Admin", ..., "op")), so the keys are written to and repaired
    from UI-Admin.toml.
  • Literal command syntax inside messages (<player|all|confirm>, <page>,
    <player>) is escaped for MiniMessage (\<...\>), so the usage lines no
    longer lose their placeholders when rendered.

[1.8.5-beta.27] - 2026-11-12

Changed

  • /ui op <player> and /ui deop <player> now work for offline players.
    The name is resolved with Bukkit.getPlayerExact first and then
    Bukkit.getOfflinePlayerIfCached (no blocking profile lookup, so only names
    this server has seen are accepted). OfflinePlayer#setOp rewrites ops.json
    and the op_list entry is updated through OpManager.grant/revoke, exactly
    like the online path. A name the server has never seen is rejected with
    "is not online and is not known on this server".
  • Offline targets get a prefixed warning. Before the confirmation dialog and
    in the result the command prints a MessageUtil.PREFIX-styled line: the change
    will be written to ops.json and the OP list, and the player receives no
    notification. The confirmation dialog marks the target (offline).
  • Tab completion follows. /ui op suggests OP-list names (repair
    candidates); /ui deop suggests every list entry and every real operator,
    online or offline.

[1.8.5-beta.26] - 2026-11-12

Changed

  • /ui deop all now revokes every real OP, not just the OP list. Targets are
    the union of the op_list table and Bukkit.getOperators() (ops.json), so
    players who were granted OP outside /ui op — including offline players
    from ops.json — are deopped too. Stale list-only entries (listed, no real OP)
    are simply dropped. The confirmation dialog shows each target's source:
    [OP], [op-only], [list-only], plus an offline marker and counts
    (in list / real OP outside list / offline). The result message separates real
    revocations from removed stale entries and reports failures.
  • OpManager.revoke(OfflinePlayer) was added for the offline path
    (OfflinePlayer#setOp(false) rewrites ops.json without the player being
    online) and shares the list-removal logic with the online overload.

[1.8.5-beta.25] - 2026-11-12

Fixed

  • /ui op and /ui deop no longer deadlock on OP-state drift. The OP list
    (op_list in SQLite) and the real Bukkit OP flag could disagree — a player
    stayed in the list after their OP was removed (or had OP without a list
    entry) — and then both commands refused with contradictory messages:
    "is already in the OP list" / "does not have OP status" / "No eligible players
    found". Now the commands treat every mismatched state as work: /ui op
    restores the flag for a list-only player (or records an existing OP in the
    list), and /ui deop drops a stale entry instead of failing. Messages report
    both states instead of one of them.
  • OP changes go through one place. OpManager moved from UI-Admin to
    UI-Core and gained grant(Player, by) / revoke(Player) helpers that update
    the flag and the list together. The OP whitelist/blacklist gates (UI-Punish),
    /ui opself and the opt-in real grant of /forceop (UI-Other) now use them,
    so they no longer leave the list out of sync.
  • Join-time reconciliation. A player who already has real OP but no list
    entry (vanilla ops.json, a third-party plugin, an older build) is added to
    the list on join, so /ui deop can find them later. The opposite state is
    deliberately not auto-regranted — it may be the intended result of the OP
    whitelist/blacklist gates — and is repaired explicitly by /ui op.
  • Database errors are no longer mistaken for "not in the list".
    OpManager.lookup is tri-state (null = unreadable); the commands abort with
    "Could not read the OP list" instead of granting or refusing based on a broken
    query, and failed list writes are reported to the sender and the console.
  • /ui oplist shows drift. Entries are marked ⚠ list-only and the header
    counts both drift directions (list-only / op-only).

[1.8.5-beta.24] - 2026-11-12

Fixed

  • Area enchantments no longer break blocks through walls. AoE used to be a
    plain cube scan by material type, so a block sealed inside a solid shell was
    mined together with the one the player actually hit — placing magma on the
    outside of a bedrock box and breaking it also mined the magma locked inside.
    The sweep is now a 6-direction flood fill (BlockVisibility) that may only
    travel through blocks of the same type (they are mined anyway) and through
    see-through, non-solid blocks (air, water, plants, ...). Any solid block of
    another type (bedrock, stone, planks, glass, ...) stops the sweep, so only
    blocks with a real physical path from the broken one are affected. The cube
    radius limit (±level, capped at 10) is unchanged.
  • VeinMiner (same-ore 6-direction flood fill) and TreeCapitator (same-column
    scan that stops at the first non-log block) already could not cross walls;
    their behaviour is unchanged.

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

Follow-up hardening from the external authentication audit (on top of beta.22).

Security

  • Parallel dialog submits can no longer bypass the wrong-password limit. The
    cooldown is applied only after an error, so a burst of auth_submit clicks all
    passed it and started N parallel Argon2 checks. One verification is now reserved
    per account/IP before the async check and released afterwards.
  • Lockouts grow exponentially (auth.lockout.backoff_multiplier: 15 s → 30 s →
    60 s …) up to auth.lockout.max_seconds, and a new penalty never shortens an
    already active lock — a burst of errors used to reduce the lock to 15 s from
    the last one.
  • Pre-login freeze also cancels InventoryOpenEvent (entity/container GUIs that
    do not go through PlayerInteractEvent, e.g. chest minecarts).
  • A pending GitHub 2FA challenge is cleared on quit instead of lingering in
    stateToUuid until the 5-minute expiry.
  • /ui auth 2fa setup rejects blank GitHub usernames at the API level and refuses
    an account already linked to another player (auth.twofa.github_taken).
  • GUIDE documents that the GitHub callback server is plain HTTP on
    auth.twofa.github.port and must sit behind an HTTPS reverse proxy.
  • The password-change dialog verifies the old password through the same
    reservation/backoff path.

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

Authentication hardening: the login gate now fails closed, the GitHub second
factor can no longer be skipped, brute-force protection survives reconnects, and
the pre-login freeze covers chat and entity/inventory actions.

Security

  • 2FA can no longer be bypassed by reconnecting. last_login was written
    right after the password check, so a player could pass the password, leave and
    rejoin inside the session window and skip the GitHub challenge. The session is
    now stamped only after full authentication (password + 2FA).
  • The login gate fails closed. An unreadable auth table used to let players
    in unauthenticated; such joins are now refused with a clear kick message.
  • Account passwords can no longer be overwritten by a storage glitch. A failed
    registration read was treated as "not registered" and the registration path used
    INSERT OR REPLACE. Reads now return an explicit unknown state, and registration
    uses ON CONFLICT DO NOTHING and reports a conflict instead of replacing a hash.
  • 2FA never silently disables itself. A missing GitHub binding or an unreadable
    2FA row used to delete the protection and log the player in; both cases now
    refuse the login.
  • Wrong-password attempts are persisted in auth.failed_attempts, so
    max_wrong_attempts is actually reachable — reconnecting no longer resets it.
  • Pre-login freeze extended to chat, entity interaction, item pickup/consumption
    and inventory clicks.
    Previously a frozen player could talk in chat.
  • Password-change and admin-reset dialogs now require an authenticated sender
    (a crafted custom-click packet cannot reach them).
  • Logout/admin password resets keep the stored IP, so max_accounts_per_ip cannot
    be dodged by logging out; resetauth also removes the 2FA binding.
  • Offline forcelogin is refused (it used to leave a permanent authenticated entry
    in memory); PBKDF2 verification is constant-time.
  • The built-in GitHub callback server caps concurrent connections, request-line and
    header sizes, escapes rendered values, and sends no-store/nosniff headers.

Fixed

  • Registration is only certified after the row is actually written; a failed hash
    or insert now reports an error instead of a successful login.
  • AuthPlayerState uses concurrent sets — it is read from async chat/command threads.

SHA-256 of UltimateImprovments-1.8.5-release.1-jars.tar (21 JARs, 20 302 336 bytes):

2d74a45406543db1190c60f30e402a1639ec8acd0c433d3795f477ba57d987d4