Tried to load invalid item Not a boolean: 0, missed input
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
An itemstack serialized 1.20.4 should correctly load in 1.21 without errors.
Observed/Actual behavior
on 1.20.4:
Base64.getEncoder().encodeToString(Bukkit.getUnsafe().serializeItem(shulker))
the base64 string: https://0bin.net/paste/gCNq3q2J#fdoLN9dS1PAzhj8eBqeOrnp-xihURktdcDNq1nGLw4a
on 1.21
Bukkit.getUnsafe().deserializeItem(Base64.getDecoder().decode(string));
console error: https://0bin.net/paste/o2chIszJ#52v2olu-s1gmuI/T6IOWtt9OJp3CIgjIu7DgXVqxAyG
The item appears to deserialize correctly, but the console error is still printed, very odd.
Steps/models to reproduce
Encode an item using Bukkit.getUnsafe().serializeItem in 1.20.4
decode said item in 1.21
Plugin and Datapack List
N/A
Paper version
1.21 https://github.com/PaperMC/Paper/commit/34a2917dccd1a39888c85badd7cf7aad7c44ff61
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with Bukkit.getUnsafe().serializeItem and deserializeItem using the provided 1.20.4 Base64 data on Paper 1.21. Trace the deserialization path responsible for the “Not a boolean: 0” message, then verify that the item loads without logging an error while preserving its data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100