Tag and recipe suggestions

[PegasDoggeAM]

Based on currently used tags and recipes for 1.21.1 (1.3.0-rc1).

Tags

1. Refrain from using c: tags inside of c: tags (e.g. #c:crops/tomato in #c:crops or #c:foods/raw_fish in #c:foods/safe_raw_fish); rather include items individually in both.
2. Include Tomato Seeds in #c:seeds/tomato. Same applies to other seeds.
3. Include Rotten Tomato in #minecraft:impact_projectiles.
4. Use more material tags like #c:rods/wooden or #c:gems/diamond in crafting recipes (e.g. knife recipes).
5. That's a bold one, include Straw in #c:strings.

Recipe changes

1. Add a "group": for fried egg recipes, so that others can add their own fried egg recipes to the same group.
2. I'm not sure if this originates from here, but don't use #c:crops/tomato tag in Immersive Engineering fermenter recipe.

Cutting recipe additions

I'll leave them here just so that I don't think about them anymore :b

1. Nether wart block to 1 nether wart (50% or lower chance).
2. Ladder to 2 sticks.
3. Other quartz blocks (pillar and bricks) to quartz.
4. Wool to strings.
5. Bowl to sticks.
6. Flower pot to bricks.
7. Glowstone to dust.

[TelepathicGrunt]

Refrain from using c: tags inside of c: tags

I am only reading this part and comment here to say this is nonsense. Nested tags are proper convention and encouraged for making sub categories.

see neoforge and fabric already shipping subtags and referencing those subtags in the parent tag. It’s the whole point of them. c:crops is parent. All tags under c:crops/ folder are subtags and all are referenced in parent tag

https://github.com/neoforged/NeoForge/tree/1.21.11/src/generated/resources/data/c/tags/item/crops

https://github.com/FabricMC/fabric-api/tree/26.1.2/fabric-convention-tags-v2/src/generated/resources/data/c/tags/item

May I ask where you got the idea of subtags being discouraged?

[PegasDoggeAM]

Well, I don't remember. I might've came up with it while overthinking the possible disadvantages it may produce when done incorrectly, so I restrained from doing that entirely, as I'm not the one who should decide the conventions. The tomato example might be a bit too extreme tho. It's mainly the #c:safe_raw_fish that bothers me, cause it basically forces you to remove any poisonous fish included in #c:raw_fish from it, instead of just including whatever fits. It's a nonexistant problem really, just a mere suggestion. And now that I think about it, you are totally right and I shouldn't be worried about that whatsoever. Thank you!

[vectorwing]

safe_raw_fish exists because Forge adds Pufferfish to what's essentially a food tag, and using this fish on food is very much wrong without proper precautions. In most situations, it will only really need to exclude Pufferfish; I can't imagine there are many others.