I've noticed this why trying to enchant a diamond sword.
Whenever I use the grindstone to disenchant an item, it does not drop experience orbs or add the experience automatically.
I.e. the amount of experience I have remains the same.
While this is a minor issue, I do find this annoying and would appreciate if this got fixed.
Linked issues
duplicates 1
Comments 10
Sorry I misread the ticket! 😛 With that being said, did you happen to be using any data packs when experiencing this issue?
Are you sure that the experience did not drop at all? Sometimes it gets stuck behind the grindstone.
@Avoma: I was not using any data packs.
@Violine1101: The grindstone is on the ceiling of the enchanting area. Before 1.17, the orbs would always drop to the ground.
I'm certain that it does not drop.
I'm on a realm, if that helps at all.
I've just discovered that orbs do drop when disenchanting a book.
So it seems that the bug occurs with tools like swords, bows etc.
In that case, please provide some screenshots and/or videos demonstrating this behavior whilst the F3 debug screen is enabled.
Just wanted to confirm that I have also experienced this with disenchanting some fishing rods, two pieces of gold armor, and a pair of leather boots. I'll try to capture some video with F3 debug visible the next time I have something to disenchant.
I did some more testing, and it looks like the issue is that the experience orbs are in fact getting trapped above the grindstone when it is attached to the ceiling. In the linked video, I was able to draw the orbs to me by jumping beside the grindstone, but if the grindstone was in a recessed hole in the roof, or surrounded by half slabs, this hasn't worked, and the grindstone would need to be mined to get the experience.
It looks like the real issue is the the orbs are spawning on the surface of the grindstone with the largest Y-coordinate, when ideally they should always spawn on the "top" of the grindstone (which is at the lowest Y-coordinate when it is attached to a ceiling). Is there an existing issue elsewhere for this?
Resolving as a duplicate of MC-58862.
Would MC-152526 happen to describe your issue?