v1.0.3 - May 2026 Patch Notes

Two follow-on hardening tweaks for the placed-block XP guard shipped in 1.0.2, plus a modder-friendly fallback for routing custom weapons to a combat skill.

Updates

• Modded weapons can declare their combat skill via an item tag. Previously, a new weapon shipped by a content mod would only earn XP for the right combat skill if its item ID happened to substring-match a key in xp-maps.json — so admins had to add an entry for every new sword, axe, or staff. Weapons can now carry an MMO_Weapon_Type raw tag whose values name a registered skill (e.g. ["POLEARMS"] or ["PoleArms", "Blunt"]). When the regular xp-map lookup misses, the first tag value that matches a registered skill wins — XP routes to that skill, weapon-gated damage rewards/lifesteal/crit fire under that skill, and the View XP buffs panel shows the correct skill name. Tag matching is case-insensitive. Existing weapons with xp-map entries are unaffected. The tag is read from the item's getRawTags() map at the moment you swing — no config reload needed when a mod adds a tagged weapon.
• Creative-mode placements no longer poison the XP guard. When a player in creative mode placed a block, the guard remembered that placement and denied gathering XP to anyone who later broke it — including the same player after switching back to survival, and other players who came along to mine. Builder admins setting up an ore wall for survival miners were silently breaking those miners' XP. Placements made in creative mode are now skipped at the placement step, so survival players who break those blocks earn XP normally.
• Placed-block XP gating now defaults to server-wide strict mode. Previously the guard only denied XP when the breaker was the same player who placed the block — so a friend could place blocks for you to mine and you'd still get full XP. Out of the box, breaking any player-placed block now denies XP, regardless of who placed it. Admins who want the prior per-player behavior can flip strictPlacedBlockCheck to false in mods/mmoskilltree/skill-config.json. The block must still actually be flagged as placed — natural ores and trees are unaffected.