This would allow datapack makers to create custom items that craft other custom items, or custom items without fear of players crafting them in a recipe that shouldn't use them.
A data component for items called ingredient_id or something of that nature. It would be a string defaulting to the identifier ("minecraft:diamond", for example). Instead of data-driven recipes looking at item id's for input, they would look at ingredient id's. Output would still use an item id.
A practical example would be combining raw iron and coal to make raw steel scrap, and then smelting that to make steel, from which steel tools could be made. If raw iron or an iron ingot were to be used as a base item for the custom steel items, it would cause conflict with the steel recipes and iron recipes. If an item like poisonous potato was used, there would be no base conflict but now any poisonous potato acts like steel. This is why custom ingredient components are needed.
Please sign in to leave a comment.
1 Comments