Instead of using .minecraft/itemsfromtext/<namespace>/<ITEM_ID.txt / ITEM_ID_name.png / ITEM_ID_recipe.json>, make a more datapack format for :
adding an item => .minecraft/itempacks/<datapack name>/data/<namespace>/items/<ITEM_ID>.json (use json for more datapack-like experience)
adding the texture => .minecraft/itempacks/<datapack name>/assets/<namespace>/item/<ITEM_ID>.png (and also load the pack as a resourcepack to allow further customization for appearance)
adding the recipe => .minecraft/itempacks/<datapack name>/data/<namespace>/recipes/<ITEM_ID>.json (and also load the pack as a global datapack to allow further customization for mechanics, etc.)
And obviously use a pack.mcmeta in the pack root folder :)
I think thats a good idea since it could allow global resourcepacks/datapacks that can be easily expanded for other additions (imagine making data-driven blocks next)
Instead of using
.minecraft/itemsfromtext/<namespace>/<ITEM_ID.txt / ITEM_ID_name.png / ITEM_ID_recipe.json>
, make a more datapack format for :.minecraft/itempacks/<datapack name>/data/<namespace>/items/<ITEM_ID>.json
(use json for more datapack-like experience).minecraft/itempacks/<datapack name>/assets/<namespace>/item/<ITEM_ID>.png
(and also load the pack as a resourcepack to allow further customization for appearance).minecraft/itempacks/<datapack name>/data/<namespace>/recipes/<ITEM_ID>.json
(and also load the pack as a global datapack to allow further customization for mechanics, etc.)And obviously use a
pack.mcmeta
in the pack root folder :)