XP Multiplier 2.1.4

New: an optional [difficulty] multiplier, keyed by Easy/Normal/Hard - plus another round of NeoForge patch bumps, a /xpmultiplier reload fix, reload gets color, and two config misconfigurations that used to fail silently now speak up.

[difficulty]
    enabled = true
    hard = 1.25   # reward playing on Hard, stacked on top of whatever a source's own multiplier is

The optional [difficulty] layer works exactly like [dimension]/[biome]: off by default, stacks multiplicatively on top of a source's own multiplier once turned on, and for now covers the same two events [dimension] does (block-break and mob-kill XP). Peaceful has no entry of its own - it uses the normal value, since mining, fishing and every other non-combat source still fires on it, so penalising Peaceful the same way as a real difficulty step would be wrong.

Another round of NeoForge patch bumps:

The other four versions (1.21.2, 1.21.4, 1.21.5, 1.21.9) were already on the newest available patch and are unchanged. All eight jars were rebuilt and re-tested against their new NeoForge patch - every mixin still loads cleanly, nothing shifted underneath the mod.

/xpmultiplier reload now counts [dimension]/[biome]/[difficulty] entries. The "N value(s) differ from vanilla" line used to undercount: turning on [dimension] or [difficulty] with real entries reported 0 for them, even though they were live. The count now includes all three lists and both section's enabled switches.

Two mistakes that used to fail silently now get flagged. Setting minXpPerEvent above maxXpPerEvent (e.g. min = 100, max = 50) used to let the ceiling win with no explanation anywhere - it now logs a debugLog warning on every scaled event, and shows as a red line the next time you run /xpmultiplier reload. A duplicate entry in [custom] or [dimension] (the same id or #tag listed twice) always let the later value quietly win; the server log now warns about it the moment the config is read, whether or not debugLog is on.

The reload chat line finally has color. Green when your config differs from vanilla, yellow when it's still all default, red if the mod is off or if the min/max mistake above is present - a glance instead of squinting at plain white text.

Updating from 2.0: drop in the new jar, existing config keeps working, [difficulty] appears with its default (off) values the next time the server writes the file. Still server-side only.