Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Custom Crafting does not save NBT properly

Open
  • Is something wrong?
#1,260 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
game-dev

Research direction

Start by reproducing the custom crafting flow with a custom-NBT item, using /cb about and /version to confirm the reported CraftBook and Bukkit versions. Inspect how the recipe result is persisted across a server restart. Done means custom model data and other NBT attributes remain available when the item is crafted after restarting.

Written by the indexing model from the issue text.

Description

status:pending type:bug version:five

Versions

CraftBook version: 3.10.3;4680-f1ee2df AND 5.0.0;4696-73809ea
Bukkit version: PurPur-1022

Describe the bug
Item NBT data is not being saved properly when using custom crafting. It CAN store that information before the server restarts, however after restarting, it only saves name and lore. This prevents items from retaining custommodeldata, and custom NBT attributes on items.

To Reproduce

  1. Create recipe with the resulting item having custom NBT flags
  2. Restart the server
  3. Attempt to craft that custom item and the data is gone.

Expected behavior
I would expect that this information would continue to be applicable for items - this makes Craftbook much more integral and compatible with other resources and custom items, so its a very important feature (at least, to me)

Screenshots
image
This is the item as it should be:
image
And this is the resulting item after restarting the server:
image

Additional context
The custom item in the example is using MMOItems - however all of that item data is attached to the item itself, which shouldn't cause issues like this. There was an issue with this before back in 2014 - however with ProtocolLib and many other updates and resources coming to fruition since that last report - I feel that this should really be revisited.

Dominant language
Java
Stars
320
Forks
165
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EngineHub/CraftBook

All issues in EngineHub/CraftBook

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.