File Details
MMOSkillTree-1.0.3.jar
- R
- May 2, 2026
- 2.42 MB
- 2.3K
- Early Access
File Name
MMOSkillTree-1.0.3.jar
Supported Versions
- Early Access
v1.0.3
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.
- Modded weapons can declare their combat skill via an item tag — previously, a new weapon shipped by a content mod only earned 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 anMMO_Weapon_Typeraw tag whose values name a registered skill (for example["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 - Creative-mode placements no longer poison the XP guard — Placements made in creative mode are now skipped at the placement step — 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 prefer the prior per-player behavior can set
strictPlacedBlockChecktofalseinmods/mmoskilltree/skill-config.json. Natural ores and trees are unaffected — only blocks players actually placed are gated

