Equivalent Legacy

v1.1.7 - Better Combat still did not recognise the Red Katar

Bugfix release for Minecraft 1.21.1 / NeoForge 21.1.249. Data file only — no Java, no new item, no gameplay or EMC changes.

Fixed

• The 1.1.5 fix for Better Combat never actually loaded. The weapon definition was added at data/bettercombat/weapon_attributes/rm_katar.json, which is precisely the one place Better Combat does not read. Better Combat lists the files under <any namespace>/weapon_attributes/ and turns each path into an item id (equivalent_legacy:weapon_attributes/rm_katar.json becomes equivalent_legacy:rm_katar), then silently drops every id that is not in the item registry. Sitting in Better Combat's own folder, the resulting id was bettercombat:rm_katar — not an item — so the definition was discarded on every load and the Red Katar (equivalent_legacy:rm_katar) kept falling back to a flat vanilla attack: no custom animation, no hitbox, no Better Combat swing sounds. The file now lives at data/equivalent_legacy/weapon_attributes/rm_katar.json, where the id it produces is the item's own id.
• The definition itself is unchanged. Its hitbox, animation and swing_sound values were already valid — they are checked against Better Combat's own files (data/bettercombat/weapon_attributes/rapier.json and data/minecraft/weapon_attributes/wooden_sword.json) on both 2.4.0+1.21.1 and 3.2.2+26.2. Only the folder was wrong.

Notes

No balance or gameplay change: this is the same weapon definition as before, in the path Better Combat actually reads. Damage multipliers still apply on top of the item's own attack damage, so Katar charge levels and the flat Katar bonus are unaffected.

In game you can confirm the fix by the Attack Range line Better Combat adds to the tooltip — if it shows up, the item is registered as a weapon. To dump the whole registry to the console, set weapon_registry_logging = true in config/bettercombat/server.json5; it prints every loaded id on startup.

Nothing to change in your config if you are coming from 1.1.5 or 1.1.6. The old file sat in Better Combat's own folder, where it was not competing with anything, and your fallback_compatibility.json can stay as it is.

Same fix shipped for 26.2 as 1.7.1.

JAR: equivalent_legacy-1.21.1-neoforge-21.1.249-1.1.7.jar