Skip to content

1.8.5-beta.1

Choose a tag to compare

@rizer001 rizer001 released this 04 Nov 11:38
· 1150 commits to main since this release
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.