Multiplicative Enchantment Damage

Changes Sharpness, Smite, Bane of Arthropods and Impaling damage calculations to be percentage based. This mod aims to lessen the gap between enchanted heavy vs light weapons.

Mods often add “fast and weak” vs “slow and powerful” and even 2-handed weapons. When the additional damage from enchantments is all linear, the balance falls apart and fast weapons almost always win out in DPS in lategame. Because of the flat additions, the % DPS increase for 1 handed is much greater than 2 handed due to faster attack rate.

Fully Configurable!

So you can fine tune the balance:

1. Whether to run the multiplier logic at all for this enchant.
2. Whether to override the default enchantment behavior (undo flat additions)
3. What the first level multiplier is.
4. What each additional level adds to that multiplier.

Default Settings

This mod changes the following enchantments by default (Based on Vanilla scaling at 6 damage from a lighter weapon, Knives, + vanilla enchants scaled to percentage instead):

1. Sharpness changed from, +1 first level, +0.5 per additional: +16.8% level 1, + 8.3% per additional. (x1.5 at level 5)
2. Bane of Arthropods, Smite, Impaling changed from 2.5 per level: +41.6% per level. (x3.08 base damage at level 5 vs specific mobs)

Keep in mind this stacks on top of crits (e.g. 1.5x from crit times 3.08x)

Note: For modded enchantments from my experience (Illager’s Bane and Sculk’s Smite, will vary per mod), they don’t have hardcoded damage scaling logic and will work through a Data Pack.
Replace their damage minecraft:add effect(s) with the following:

"type": "minecraft:multiply",
"factor": {
"type": "minecraft:linear",
"base": 1.416,
"per_level_above_first": 0.416
}

I recommend unzipping the given mod jar(s) to find the data folder path to their “enchantments” folder. Until I find a mod that doesn’t work with a datapack, I don’t see the need to make config support for modded enchantments specifically. If you find a modded enchantment that doesn’t work through a Datapack, feel free to bring up an issue on the GitHub!