Static tags stand in the way of fluidity. I propose a solution: a command for local, world-specific resource edits. Its usage will create a new datapack with top priority.
Format:
/resource data tag <type> <target> [add/remove/replace/reset] [resource_location]
Data is for datapack, leaving room for future expansion.
Type is the tag's category, like entity_types, blocks, items, etc.
Target is the resource location you intend to modify. Any time a tag exists in multiple datapacks, the highest priority one is targeted.
Examples:
/resource data tag blocks #minecraft:climbable add #custom:climbable
Blocks listed in #custom:climbable are added to #minecraft:climbable while preserving the existing values.
... blocks #minecraft:enderman_holdable remove minecraft:soul_sand
Removes block from #minecraft:enderman_holdable.
... items #custom:swords reset
Resets #custom:swords to the value(s) as specified in the installed datapack(s).
... entity_types #custom:scary
Returns a list of values stored in #custom:scary.
... blocks #custom:rare replace minecraft:gold_ore, minecraft:diamond_ore
Sets the #custom:rare tag to {minecraft:gold_ore, minecraft:diamond_ore}. It'll ignore lower versions of the tag because the replace value in the JSON file is always set to true.
Please sign in to leave a comment.
0 Comments