Another thing I just discovered is that the item modifier does not work consistently. For example:
{
"function": "minecraft:set_components",
"components": {
"minecraft:max_damage": 1000,
"minecraft:custom_data": {tag:"datapack_example.elytra"}
}
}
Let's say that this is in a file called "set_durability.json". Then to use it, we we call the command:
/item modify entity @s armor.chest datapack_example:set_durability
This however throws an error because Minecraft failed to parse the file. But if instead of storing the item modifier in a file, we store it in the command, we get a different result:
/item modify entity @s armor.chest { "function": "minecraft:set_components", "components": { "minecraft:max_damage": 1000, "minecraft:custom_data": {tag:"datapack_example.elytra"} }}
This works, but for some reason, the file does not.
Above is a datapack that proves my point. Let me know if you guys have any more questions!
Is there a way I can delete this duplicate myself?
Looks like you have some things to update.
This also appears on version 1.19.1 Pre-release 4.
It also can be recreated using a datapack loop.
Yes
[Mod] tryashtar,
You are mistaken. This is not datapack help. Please read the report in full to grasp an understanding of the issue. This is an issue with the item modifier "set_damage", not an issue with the datapack. The datapack is valid and is only used for demonstration purposes.
Thank you.