MC-149759Cannot fully revert renaming of item
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
RepairCost: 0- {display: {Name: '{"text":"Renamed"}'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.
- Note: You will encounter
- It retains the RepairCost tag, preventing it from stacking with other Egg items.
For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron). Still it is a nuisance.
Created Issue:
Cannot fully revert renaming of item
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- display: {Name: ' {"text":"Renamed"}
'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- display: {Name: ' {"text":"Renamed"}
'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- display: {Name: ' {"text":"Renamed"}
'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- display: {Name: '
{"text":"Renamed"}'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- {{display: {Name: ' {"text":"Renamed"}
'}}}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
{{display: {Name: '{"text":"Renamed"}'}}}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- display: {Name: '{"text":"Renamed"}'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- display: {Name: '{"text":"Renamed"}
'}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- {{display: {Name: ' {"text":"Renamed"}
'}}}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- {{display:
{Name: ' {"text":"Renamed"}
'}}}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron).
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- {{display:
Unknown macro: {Name}}}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron). Still it is a nuisance.
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- {
{display:Unknown macro: {Name}}}
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron). Still it is a nuisance.
When you use an anvil to rename an item, the item receives a RepairCost tag even when it cannot be enchanted or repaired. Upon reverting the custom name on an anvil, the item retains the RepairCost tag, preventing otherwise stackable items from stacking with other non-renamed items of the same type.
How to reproduce:
- Rename a stackable item, e.g. an Egg, on an anvil, e.g. to "Renamed".
- It is now NBT tagged with:
- {display: {Name: '{"text":"Renamed"}' }
- Put the renamed item onto an anvil and delete its custom name, reverting its name to be "Egg".
- Note: You will encounter
MC-149761when doing this.For many items there exist workarounds: Blocks can be placed and destroyed, dropping a non-tagged item, and some items can be crafted into other forms from which the item can be re-crafted (e.g. iron -> iron block -> iron). Still it is a nuisance.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
testing discovered
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
testing discovered
testing discovered
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
is duplicated by
is duplicated by
duplicates
This report is well written, but it is a duplicate of
MC-125046.