1.8.3-alpha.3

[rizer001]

UltimateImprovments 1.8.3-alpha.3

Delta release on top of 1.8.3-alpha.2. Alpha pre-release — back up your server before updating.
Replace all 12 JARs together (the family ships as one version) and restart the server.

🛠 Fixed

Custom enchantments never appeared in the enchanting table

All 17 datapack enchantments used min_cost = max_cost = 30, collapsing the level-1 availability
window to a single exact roll that the vanilla ±enchantability/±15% jitter practically never hits —
the charms showed up in the recipe book and anvils but never in the table. Fixed in the datapack
itself (no listeners, vanilla table behavior untouched): a Mending-style 25–75 cost window, so
level 1 is reliably offered on the third (level-30) button. Lower buttons stay vanilla.
All 17 charms verified present in the five minecraft/tags/enchantment tag files
(in_enchanting_table, tradeable, on_random_loot, on_traded_equipment, on_mob_spawn_equipment).

/ui reload crashed with "zip file closed" and left the server half-dead

The reload cycle disables every other UI-* plugin — including UI-Other, whose own code was
executing the reload. Disabling a plugin closes its JAR, so the next not-yet-loaded class threw
IllegalStateException: zip file closed and aborted the cycle mid-way, leaving the whole family
disabled. The synchronous phase now runs from a new core-side PluginReloadCoordinator
(ui-core is never disabled in the cycle, so its classloader cannot be closed mid-run), and on any
failure it re-enables every family plugin that is still off — a failed reload no longer leaves
listeners dead.

Anticheat NPE spam after a reload

Anticheat check listeners are registered under the never-disabled UI-Core, so disabling the
anticheat plugin left them firing against cleared singletons — an NPE on every PlayerMoveEvent.
shutdown() now unregisters all check listeners before clearing singletons, and the
exemption/flag lookups in AbstractCheck are null-safe as a defensive fallback.

Datapack auto-apply could loop forever

Replaced datapack.restart_to_apply with datapack.reload_to_apply (default false):
the server is /reload-ed instead of restarted, with a marker-file guard (10 min TTL) that makes
reload loops impossible. Also fixed the actual source of the loop: level-name is now read from
server.properties first (the Paper standard; the old code only checked server.toml and fell
back to a hardcoded world), so the "is the datapack enabled" check looks at the right world.

✨ Added — Datapack content

• New recipes: book, ender chest, Eye of Ender, mace, trident, nether star, shulker box,
  blaze powder, iron chain, amethyst (uncraft + budding amethyst), melon uncraft,
  netherite smithing template duplication, reinforced deepslate
• Advancements added/updated to cover the new recipes
• Reworked DatapackInstaller and updated loot tables

🔧 Changed

• Legacy monolithic config migration (config.toml/config.yml → per-addon files) removed —
  all servers are already on the configs/UI-<Addon>.toml layout, the one-time migration code
  had nothing left to do
• ui-core: new CommandOutcomeTracker, AddonsSubcommand, TomlCrashSalvage; updates to
  CommandErrors, SubCommandRegistry, ConfigRepairManager
• ui-shared/ui-other: crafting listener updates, space oxygen (SpaceOxygenListener), recipe registry
• ui-anticheat / ui-chat / ui-clans / ui-combat: routine module updates
• Repository cleanup: removed 263 stale bin/main/ build-output copies from git

⬆️ Version

• Family version bumped 1.8.3-alpha.2 → 1.8.3-alpha.3 across the core and all 11 addons
  (Gradle version, plugin.yml, plugin_version in config.yml + bundled UI-Core.toml,
  README badge). Existing servers keep their on-disk plugin_version.

Compatibility

No data-breaking changes: configs, the database and player items are unaffected.
Note for servers with datapack.mode: check-override: delete datapacks/UI-Datapack from the
world folder once (or switch to override) so the fixed enchantment data actually installs.

---

This discussion was created from the release 1.8.3-alpha.3.