MC-271173Helmet slot glitched, deletes any helmet equipped
After logging into an existing 1.20.4 world on 1.20.5, helmet slot was cleared and upon equipping any helmet in that slot, said item would be deleted. Copied the world, launched it up from a 1.20.4 client made the helmet slot work again (but breaking other aspects of the game, which was expected). After launching it in 1.20.5 again, the bug came back again
Created Issue:
Helmet slot glitched, deletes any helmet equipped
After logging into an existing 1.20.4 world on 1.20.5, helmet slot was cleared and upon equipping any helmet in that slot, said item would be deleted
After logging into an existing 1.20.4 world on 1.20.5, helmet slot was cleared and upon equipping any helmet in that slot, said item would be deleted. Copied the world, launched it up from a 1.20.4 client made the helmet slot work again (but breaking other aspects of the game, which was expected). After launching it in 1.20.5 again, the bug came back again
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
r.-1.-1.mca
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
Can you please provide more information to the report, you can do that by adding the reproduction steps and if possible attach a video and screenshot showcasing the bug.
Would it be possible to upload the world with the issue?
I don't have much knowledge in this, so I'm unsure how I can copy the world in one file. A zip is too big (even with a few deleted folders [like advancements]).
Is there a link that could help explain the process to it, so I don't accidentally mess something up in the files and make them unusable?
(I tried to upload as you can see, but that turned into a mess, with many files not being uploaded)
If you like, you can upload the zipped world folder to an external site (e.g. Google Drive, OneDrive, Dropbox) and then provide a link here.
I'll try to get to that as soon as I can, although I'm unsure how soon.
In the meanwhile:
I decided to try and mess around, I created a world with the exact same seed in 1.20.5 (so, up to date), and one by one I copied the folders from the old world and replaced the ones in this new one. I went through every folder plus file that was in the save file (%appdata% - minecraft - saves) and the bug no longer exists. But if I copied the world (the one that was changed from 1.20.4 to 1.20.5) by duplicating the whole save file, it was there.