• Configure item use in recipe (ingredient)
• Configure sacrifice in recipe (by entity tag)
• Configure ritual id in recipe -> we then only provide general ritual types like "summon spirit with job", "create item", ...
  • recipe then has instance of said ritual
  • sacrificial bowl then identifies recipe instead of ritual (but recipe simply calls ritual.identify to keep refactor to a minimum)
• Configure entitytype to spawn in recipe - by id
• for spirits - configure max age in recipe
• Show item use in JEI
• Show sacrifice in JEI
  • recipe holds translation key to show name
• Show entity to spawn in JEI (at least name / job)
• Handle ritual dummies
  • -> provide a "Custom Ritual" dummy, other dummies would have to be created via e.g. kubejs
• Handle ritual messages -> just need to be added to datapack file
• Test
  • Pentacle matching
  • Summon with job
  • Craft
  • Familiar
  • Dedicated server
• Warning for packmakers
  • moved/removed config
  • new recipe style
  • datapackable pentacles

See source issues:

• #118
• #318
• #317

See also #346