Recipes of that type specify the ritual level, color, ingredients and incenses
The also provide the actual effect as an ID.
Ritual effects are registered to a registry, just as rituals previously were
Ritual effects can define a custom config which is also read from the network/json
Examples of this is the crafting ritual, which requires an additional result ItemStack, or the Summoning Ritual
Altar TileEntities no longer store their ritual when saved. This can be re-implemented using a recipe lookup instead, but as rituals are all more or less instantaneous, it did not feel like they needed to be saved when closing the world.
They now only sync the ritual level & color to the client instead, since these are needed for client-side effects.
The research pages for rituals now only get added when the actual recipe behind them is defined, enabling data-pack authors to disable specific rituals and removing them from the tablet.
Implementation for #84
rootsclassic:ritualrecipe typeresultItemStack, or the Summoning RitualAltar TileEntities no longer store their ritual when saved. This can be re-implemented using a recipe lookup instead, but as rituals are all more or less instantaneous, it did not feel like they needed to be saved when closing the world. They now only sync the ritual level & color to the client instead, since these are needed for client-side effects.
The research pages for rituals now only get added when the actual recipe behind them is defined, enabling data-pack authors to disable specific rituals and removing them from the tablet.