MC-15259Items with invalid enchantment IDs crash the client when placed in an anvil
If an item has an invalid enchantment ID (between 0-255, but not one that is in use), the item will cause the client to crash when placed into an anvil.
Any other actions involving the enchantment (such as using the item, or hovering over it) do not cause a crash, as the validity of the enchantment is checked ('if Enchantment != null'). This sanity check is not performed in the anvil GUI.
Steps to reproduce:
1. Put any kind of item in your inventory
2. Use an NBT editor to put an enchantment on the item using an ID not used by any existing enchantment (i.e 200)
3. Go back ingame, the item will have an enchanted glow, but not list any enchantments (as expected)
4. Place the item in an anvil
5. The game crashes
Linked Issues
Created Issue:
Items with invalid enchantment IDs crash the client when placed in an anvil
If an item has an invalid enchantment ID (between 0-255, but not one that is in use), the item will cause the client to crash when placed into an anvil.
Any other actions involving the enchantment (such as using the item, or hovering over it) do not cause a crash, as the validity of the enchantment is checked ('if Enchantment != null'). This sanity check is not performed in the anvil GUI.
If an item has an invalid enchantment ID (between 0-255, but not one that is in use), the item will cause the client to crash when placed into an anvil.
Any other actions involving the enchantment (such as using the item, or hovering over it) do not cause a crash, as the validity of the enchantment is checked ('if Enchantment != null'). This sanity check is not performed in the anvil GUI.
Steps to reproduce:
1. Put any kind of item in your inventory
2. Use an NBT editor to put an enchantment on the item using an ID not used by any existing enchantment (i.e 200)
3. Go back ingame, the item will have an enchanted glow, but not list any enchantments (as expected)
4. Place the item in an anvil
5. The game crashes
duplicates
duplicates
duplicates
Please provide steps to reproduce using the Bug Report Guidelines Here aswell as the crash report.
Based on a crash report provided in this issue, I believe with high certainty that this report may be a duplicate of
MC-13086. You can view all information known about this specific crash at MCX-441.Report updated with information requested.