Closed cheeezburga closed 8 months ago
This isnt a big issue or anything, as doing set (tag "custom" of {copy}) to (tag "custom" of {original})
is a valid workaround.
another workaround is:
set {_copy} to nbt from "%nbt of player%"
Im working on a fix though, so the next update will have it.
re-opening. I close when I actually release a build
What happened?
I was using an inventory serializer type thing to backup a group of items to a player's nbt compound, and when trying to retrieve and modify it, the nbt on the player was being modified (which, to my knowledge, is intentional). I wanted the nbt on the player to remain the same (i.e. I was wanting to use and modify a copy of the nbt), so I did the following:
With the above attempts, I also tried getting a copy of the full nbt of the player (I just replaced
nbt copy
withfull nbt copy
).Anyway, I noticed that the
custom;
tag of the player's nbt wasnt included in the nbt copy. I'm not sure if this is intentional behaviour or not. Broadcasting both tags would only broadcast anything when referencing the actual player's nbt, not the copy.Steps to reproduce
Expected behavior
Expected to see the same custom tag that the player had.
SkBee Version
3.0.0
Server Version
Paper 1.20.2
SkBee Info
Additional Information
No response