LevelZ+ 2.1.1 — Public Release

Fabric · Minecraft 1.20.1 · Java 17+ · LevelZ 1.4.13

Fixed

• Fixed combat kills sometimes awarding no independent LevelZ progression XP.
• Improved player attribution for damage, including Minecraft's recorded last attacking player as a fallback.
• Corrected death-handler checks so invalid or rejected events do not prematurely mark combat XP as awarded.
• Preserved full configurable XP shares for each eligible multiplayer contributor, without awarding the same contributor twice.
• Kept mob-health scaling, spawner-mob restrictions, XP calculations, and the separation between LevelZ progression XP and vanilla XP.

Compatibility and configuration

• Custom combat XP now defaults to disabled on new installations. Native LevelZ already awards mob XP; enabling both systems can double progression rewards.
• When custom combat XP is enabled, a server-startup check warns if LevelZ's mobXPMultiplier is positive. The check reads the active LevelZ configuration, runs on the Fabric server-start lifecycle event, and never edits the configuration.
• Existing explicit levelz_xp.combat.enabled values and other configuration settings are preserved on upgrade. Missing keys are appended without replacing values.
• Cleaned the auto-generated 67-line configuration with generic descriptions, retaining all 34 option names and all other balance defaults.
• Preserved optional integrations for combat, spellcasting, crafting, harvesting, ships, attributes and other compatible mods.
• Removed experimental build labels and modpack-specific release branding.

When enabling shared combat XP

In config/levelz_plus.properties:

levelz_xp.combat.enabled=true
levelz_xp.combat.mob_xp_multiplier=1.0
levelz_xp.combat.max_health_fraction=0.10

In LevelZ's config/levelz.json5, use:

useIndependentExp: true
mobXPMultiplier: 0.0

Do not change these on an existing installation unless you intend to alter its XP setup. The mod never changes LevelZ's configuration automatically.

Testing status: Bytecode, archive, metadata, configuration, and isolated server-start warning checks passed. A full Minecraft/Fabric runtime retest of this final JAR has not been performed.