AllItemsMini – Mini All Items Challenge

[2.3.1] - 2026-07-31

🐛 Fixes

• Fixed: Items that Mojang adds after a challenge has started are now picked up on server start. applyBlacklistAndRulesToOrder() could only ever remove entries, and loadState() only discards materials that became invalid — so a saved order stayed frozen at the item set the server had at /aic start. On a long-running challenge this silently omitted every item from later Minecraft updates.
  • Measured on a live 26.1.2 server: 114 survival-obtainable items missing, among them the complete copper family (tools, armour, chains, bars, chests, lanterns, statues incl. all oxidation stages and waxed variants), all 16 harnesses, all 12 shelves, the spears, the nautilus armour, DRIED_GHAST and IRON_CHAIN. The stored order matched the item set of Minecraft ~1.21.4.
  • New method addNewlyAvailableItems() appends anything missing to the pending part of the order. Positions 0..index — the finished items and the current target — are left untouched, so neither the counter jumps nor the running item timer resets. If the challenge was already complete, the new items extend it.
  • Verified against the official registry: item list generated with the vanilla data generator from mojang_26.1.2.jar, obtainability cross-checked against all 1515 recipes and 1326 loot tables.

🔧 Changes

• Added: Config option auto-add-new-items (default true). Set it to false to keep a running challenge at its original scope.
• Changed: Build pinned back to maven.compiler.release 21 against the Paper 1.21.10 API. Bytecode is forward-compatible, so one JAR runs on Java 21 (1.21.x) and Java 25 (26.x). Building against the 26.1.x artifact is not an option here: it ships as class file version 69 and cannot be read with release 21 — that path would produce a Java-25-only JAR and lock out every 1.21.x server. The plugin uses stable Bukkit API only, and Material.values() is resolved at runtime, so a 26.x server still exposes its own items.
• Changed: maven-shade-plugin 3.6.0 → 3.6.2.