v2.3.0

Changes

• Pick armour models per recipe and metal, including infantry and mage by @XxFran10xX in #36
  • A model scheme entry named after a recipe (e.g. heavy_helmet) wins over the shared type (helmet), so light, medium and heavy armour of each metal get their own look. Infantry and mage armour take the main metal's look when its scheme has one.
  • The bundled basic.yml maps all five base metals to the ServerAssets tfmc_armor items. Install that ItemsAdder content before this version.
• Tag crafted items with their metal, move old armour to the new looks, keep item data through refreshes by @XxFran10xX in #37
  • Crafted items carry advancedcrafting:ac_craft_model_scheme (alloys carry their base metal), which ArmourShop's metal skin lines read.
  • New armour-look-migration config (off by default). When enabled, crafted armour that still wears its old default look gets its recipe's current model on join, in opened chests, on click and on equip. The change keeps stats, gems, sockets, lore, durability and name, and skinned pieces keep their skin. legacy-models lists old looks that came from another ingredient (infantry paper, mage dust).
  • The stat refresh no longer repairs items, drops ArmourShop names or skins, or loses other plugins' data such as gem socket rarities.
  • Crafted pieces with an ItemsAdder look are opted out of ItemsAdder's auto_update, which could rebuild them without their MMOItems data. NBTAPI is now a soft dependency.
  • One broken item no longer stops a join or chest refresh.

Full Changelog: v2.2.9...v2.3.0

Downloads

• advancedcrafting-2.3.0.jar
• SHA256SUMS — SHA-256 checksums.
• build.json — Build metadata.