Weapons enchanted with Sharpness no longer display the extra damage within their tooltips

Still present in 1.21-pre2 :/

Can confirm

can confirm in 1.21-pre2

Still present in 1.21-pre4. Starting to think this won't get fixed for 1.21.

Bug still present in 1.21-rc1

Would be a shame to see this not fixed in 1.21, alongside MC-272819 and MC-268913.

Still happens on 1.21 final release. Oddly enough it only seems to happen with newly enchanted weapons. If you enchant a weapon with sharpness or something that increases the damage and then update to 1.21 from an older version, it doesn't have the bug. While if you try to enchant a weapon with something that changes damage levels in 1.21, it doesn't change the damage level.

@Classy_Car

Do this with 1.20.6 (enable 1.21 testing) then update to 1.21. It doesn't work (with my survival world) and I'm not sure about this :/

can conform in 1.21 final release

still going on

the enchant also doesnt add the damage

@unknown It is just a visual glitch; weapons still do more damage with Sharpness.

Viradex, no it is not. my fully enchanted sword does the same as a vanilla sword. tested on mobs and players.

@unknown I did some testing and Sharpness does do more damage.

Viradex No at least not in my mc it doesnt add it it still only does 7 damage

@unknown I tested it by doing this. Feel free to follow these steps:

1. Get two diamond swords, and enchant one of them with Sharpness V.

2. Summon a creeper and hit it with the unenchanted sword.

3. Run the command and note the number: /data get entity @n[type=minecraft:creeper] Health

4. Kill the original creeper and summon a new one.

5. Hit it with the Sharpness-enchanted sword.

6. Run the command above and note the number.

My results were as follows:

Non-enchanted diamond sword: 13HP left (6.5 hearts)
Sharpness-enchanted diamond sword: 10HP left (5 hearts)

An unenchanted diamond sword does 7 attack damage, which is what happened in the first result.

In Java Edition, the formula for calculating the damage Sharpness does is: 0.5 * level + 0.5
Therefore, a Sharpness V diamond sword does 10 attack damage, which is what happened in the second result.

This was with a sweeping attack, not a critical hit.

Viradex,
I would like to say im sorry and you were right

All good! This was just to clear confusion with some people. 🙂

Oh my goodness I tried it. You are correct. But that doesn't make any sense to me because I tried it with my friend and they took the same amount of damage from one swing from both items. Also I killed a spider in same amount of hits when I tried it. I'm so confused

this is just visual guys

I can confirm this bug exists on 1.21. If you take, for example, a diamond sword enchanted with sharpness 5 and a netherite sword not enchanted with any enchantments, then the diamond one will show 7 attack damage and the netherite 8, this should not happen. It's strange that this bug is in the release.

This is just a display bug, sharpness will still increase the damage of the weapon.

I hope Mojang will reconsider the resolution of MC-93699 (Smite/BoA/Impaling tooltips) when fixing this.

This may clone (or relate to) MC-16259.

As of 1.21, killing a zombie with an unenchanted diamond sword takes the same amount of hits as a sharpness 5 diamond sword…

Edit 1:  While I haven’t run any tests, I’m pretty sure this is not just a visual bug like the other comments claim

Edit 2:  I have now run tests, and this is just a visual bug, but I had no idea sharpness was this useless  😞.  It only adds an extra 3 points of damage with sharpness 5. 

Can confirm in 1.21.2 release candidate 1

Can confirm this bug is still present in 1.21.3

Confirmed in 24w45a.

Confirmed in 24w46a.

Confirmed in 1.21.4 pre-1

Confirmed in 1.21.4 pre-2

Confirmed in 1.21.4 pre-3

Confirmed in 1.21.4 rc-1

Confirmed in 1.21.4 rc-2

Confirmed in 1.21.4 rc-3

Confirmed in 1.21.4.

Confirmed in 25w02a

confirmed in 25w03a

25w08a

Still exist in 1.21.4.Netherite sword sharpness 5 damage is only 8 when it should be like 11 or 12

Still exists in 1.21.5. Odd how they’ve still ignored this for a pretty noticeable bug.

Still exists in 25w15a

Still exists in 25w16a, omg why mojang does not fix the bug

Ridiculous that this isn’t fixed yet

Still in 25w19a

Still exists in 25w20a

Still exists in 1.21.6 pre1

Still in 1.21.6 pre3

Still in 1.21.6

Still in 1.21.7

Still in 1.21.7

Why mojang does not fix the bug?

I’m also having this problem in 1.21.7

Still in 1.21.8 just reported it and got flagged as duplicate

Same thing to me.

still in 1.21.10