Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turn rituals into data-driven recipes #87

Closed
wants to merge 2 commits into from

Conversation

PssbleTrngle
Copy link
Contributor

Implementation for #84

  • Added new rootsclassic:ritual recipe type
  • 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.

@Mrbysco
Copy link
Collaborator

Mrbysco commented Nov 16, 2022

1 thing at a time please, The more added the more there's to review.

@PssbleTrngle
Copy link
Contributor Author

Sorry, I did not mean to interrupt your workflow

@@ -80,19 +102,31 @@ public void load(CompoundTag tag) {
public void saveAdditional(CompoundTag tag) {
super.saveAdditional(tag);
tag.put("InventoryHandler", inventory.serializeNBT());
if (getIncenses().size() > 0) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, I get that a lot of the changes you have made are likely nice ones but just a tip for the future, try to keep your PR's as close to only the changes needed rather than nice to have changes, especially if they are of this scale. It makes the pr a lot harder to review and more likely to have clashes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am sorry, I realize now that I have probably made a lot of these unnecessary changes automatically, without thinking about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants