Equivalent Legacy

v1.6.8 - The Red Katar was not recognised as a weapon by Better Combat

Bugfix release for Minecraft 26.2. Data-only change, no EMC or gameplay rebalance.

Fixed

• The Red Katar (equivalent_legacy:rm_katar) was never treated as a weapon by Better Combat. Every hit landed as a plain vanilla attack: no custom animation, no hitbox, no Better Combat swing sounds. Better Combat resolves an unknown item by matching regexes against its registry id, using the list in config/bettercombat/fallback_compatibility.json — and none of those patterns match rm_katar (katana is not katar, and the id contains no sword, blade, dagger or knife substring). The Red and Dark Matter Swords have always been detected (sword|blade), which is why only the Katar was affected. The item now ships its own weapon definition, which Better Combat loads directly by item id and which takes priority over the regex fallback.
• The Red Katar was missing from #minecraft:swords while both EL swords are in it, so any mod or data pack that classifies weapons by that tag instead of by class also treated the Katar as a generic tool. It is now listed there too.

Added

• data/bettercombat/weapon_attributes/rm_katar.json — the weapon definition Better Combat picks up. A katar is a short, one-handed thrusting blade, so it gets two horizontal cuts (0.9× damage) and a forward stab (1.3× damage) at a slightly reduced reach (range_bonus: -0.25), using the rapier slash and stab sounds. Damage multipliers apply on top of the item's own attack damage, so charge levels and the Katar's flat bonus are unchanged. No Java, no new item, no new registry entry.

Notes

Better Combat is a soft dependency: if it is not installed the new file is simply an unused data file. If you use a custom fallback_compatibility.json, keep it as it is — an item with its own weapon_attributes entry is skipped by the regex pass. In game you can confirm the fix by the Attack Range line that Better Combat adds to the tooltip.

Still not covered by Better Combat: equivalent_legacy:rm_morning_star. Its id matches none of the fallback patterns either, and it is deliberately not in #minecraft:swords because it mines like an axe/shovel rather than a sword.

Same fix shipped for 1.21.1 as 1.1.5.

JAR: equivalent_legacy-26.2-neoforge-26.2.0.57-1.6.8.jar