Books still have an NBT tag (RepairCost of 0) after removal of enchantments using Grindstone
After using a Grindstone to remove an unwanted enchantment from a book and get some experience back, I noticed that the plain book left behind wouldn't stack with my other books in my chest. I then noticed that it still had an NBT tag, shown in screenshot 1.
Looking in my inventory using NBTExplorer showed that this tag is a RepairCost value of 0.
Further testing in creative had the same thing happen every time, also revealing that the NBT-tagged books stack with each other, but not regular crafted books (which is expected since the minecraft:book item can stack).
Simply having the grindstone remove this tag as well if a book is used should be simple enough with no negative effects, since the RepairCost tag is useless on a regular unenchanted book. These de-enchanted books can be re-enchanted without issue, so the issue is mainly with item stacking.
This issue wasn't present before Pre-Release 3 because enchanted books weren't able to be de-enchanted with a grindstone due to a now-fixed bug.
Environment
Windows 10 Pro x64, Java 1.8.0_51 (supplied with MC Launcher)
Linked Issues
is duplicated by28
MC-148514Disenchanted books keep NBT tag DuplicateMC-148575Books disenchanted with a grindstone won't stack with books that were never enchanted.DuplicateMC-148628In pre-rlease 4, books that are disenchanted have an extra tag, seperating them from regural booksDuplicateMC-148686Books obtained from grindstone have NBTDuplicateMC-148784Disenchanted books not stacking with regular books.DuplicateMC-148954Disenchanted books do not stack with normal booksDuplicateMC-149140Enchanted Books used in Grindstone won't be stackable with other books.DuplicateMC-149175un-enchanted book bugDuplicateMC-149313Disenchanted books not stacking with othersDuplicateMC-149326enchantment-stripped items do not stack with the same itemDuplicateMC-149554Disenchanted books not stacking with normal booksDuplicateMC-149575Enchanted books keeps nbt dataDuplicateMC-149633Incorrect StackingDuplicateMC-149638Disenchanted books cannot stack with other normal booksDuplicateMC-149687Vanilla book stacking issueDuplicateMC-149717Unenchanted books do not stack with regular booksDuplicateMC-149738Enchanted book cant be stacked with normal books after being used in grindstone to remove enchantDuplicateMC-149845disenchanted books from grindstone cant be stacked with normal booksDuplicateMC-149946Books become a new stack when disenchanting on a grindstone.DuplicateMC-149998Disenchanted books (grindstone) can't be stacked with normal booksDuplicateMC-150038Books dont stackDuplicateMC-150362disenchanted books do not splice with the other books, they have another tag.DuplicateMC-150428Enchanted books disenchanted using the Grindstone do not stack with regular booksDuplicateMC-150570Can't stack booksDuplicateMC-150590Books won't stack after disenchantmentDuplicateMC-150622Зачарованные книгиDuplicateMC-151048Book De-enchanting DuplicateMC-151507Disenchanted books can´t be stacked with normal booksDuplicaterelates to5
MC-125880Recipe book rejects bows with Damage:0 tag when crafting dispensersFixedMC-140236Using the Grindstone on an item to remove enchants doesn't reset the XP price to add enchants to it in an anvilFixedMC-148000Enchanted books cannot be disenchanted with the grindstoneFixedMC-181109Grindstone adds RepairCost: 0FixedMC-268824Disenchanted books from grindstone don't stack with books that were in the inventoryFixed
Created Issue:
Books still have an NBT tag (RepairCost of 0) after removal of enchantments using Grindstone
After using a Grindstone to remove an unwanted enchantment from a book and get some experience back, I noticed that the plain book left behind wouldn't stack with my other books in my chest. I then noticed that it still had an NBT tag, shown in screenshot 1.
Looking in my inventory using NBTExplorer showed that this tag is a RepairCost value of 0.
Further testing in creative had the same thing happen every time, also revealing that the NBT-tagged books stack with each other, but not regular crafted books (which is expected since the minecraft:book item can stack).
Simply having the grindstone remove this tag as well if a book is used should be simple enough with no negative effects, since the RepairCost tag is useless on a regular unenchanted book. These de-enchanted books can be re-enchanted without issue, so the issue is mainly with item stacking.
This issue wasn't present before Pre-Release 3 because enchanted books weren't able to be de-enchanted with a grindstone due to a now-fixed bug.
Environment
Windows 10 Pro x64, Java 1.8.0_51 (supplied with MC Launcher)
Attachments3
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
is duplicated by
Maria Lemónis duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
This is still an issue in 1.14.2.
relates to
relates to
Duplicate of MC-148476.
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
This should probably be marked as duplicate, I had done some research before without finding it, but just found MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
This is because there is a bug where when you disenchant an item, it keeps an NBT tag when its supposed to remove it, therefore causing the disenchanted book to not be able to stack with books that have never been enchanted. There is already an open bug report MC-148476 that shows this.
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
Duplicate of MC-148476
![[Helper] pine1needle](../../../data/avatars/users/41329.png){kind=small}
This is a duplicate of MC-129057. After you unenchanted the fishing rod using the grindstone, it still had an NBT tag (RepairCost of 0). (This NBT tag is left for any item except books - see MC-148476.) The recipe book doesn't automatically move items that have NBT tags into the crafting grid (see MC-129057). You can still craft a warped fungus on a stick by manually moving your fishing rod into the crafting table, but the recipe book will not move it for you.
The bug
When using a grindstone it always sets RepairCost:0 in the NBT of the item (except for books, see MC-148476), even though that is redundant because 0 is the default if no value is present.
Due to MC-129057, this prevents the recipe book from using such items (e.g. bow for dispenser recipe or fishing rod for carrot / fungus on a stick) because it does not ignore RepairCost:0 and therefore considers it custom NBT data, which should prevent using the item for recipes.
Reproduction steps
- Put a bow in your mainhand and enchant it
/enchant @s minecraft:unbreaking
- Put the bow in a grindstone and remove its enchantments
- Try using the bow as part of the dispenser recipe by clicking on it in the recipe book
It refuses to use the bow - Inspect the NBT data of the bow by putting it in your mainhand and running
/data get entity @s SelectedItem
The NBT data of the bow contains RepairCost:0
This is still happening in 1.14
This error can cause the Crafting Manual in your inventory to not use items that were previously enchanted (such as bows for dispensers). I recommend that a mod link
MC-149881to this thread because it not only effects books.This is still an issue in 1.14
Franke van Zuilen, this bug is marked as fixed for the next version (probably 1.14.1 Pre-Release 1).
Issue is still in 1.14.1 (latest Release)
Chris Brooks, your issue is
MC-151062.