Hexalia: Incompatible with Transmutation ritual recipes + Verdant Grimoire loading error

[NovaLynxie]

Minecraft Version

1.20.1

Mod Version

1.20.1-0.9.4

Describe the bug!

Hi there! I have discovered a strange bug with Hexalia and transmutation recipes, which causes a cascading error in their mod's guide book not to load properly. More details here: AstralyaStudios/Hexalia#16

When installing your mod to handle unification between items to reduce duplicate resources being mined or gathered in my modpack, Wilderwoods, I discovered that one of Hexalia's recipes was not loading correctly, and because of this, as of v1.2.3 of their mod, the "Verdant Grimoire" throws an error reverting to an empty contents state as a failsafe.
Digging deeper by looking into the game's logs, I noticed the affected ritual recipe for the Sage Pendant had failed to load. Disabling your mod allowed the affected recipe to load again.
I have been able to workaround by ignoring this recipe type hexalia:transmutation, specifically ignoring hexalia:sage_pendant_transmutation recipe, which was causing it to not be craftable and breaking the Verdant Grimoire as a result of recipe unification done by your mod.

Steps to reproduce:

1. Install Minecraft Forge for 1.20.1, Hexalia and Almost Unified. (EMI/JEI if you want to check recipes directly)
2. Enter any world, or create a new one.
3. Obtain the Verdant Grimoire or use EMI/JEI to view the Sage Pendant recipe and see that the ritual recipe is missing. Verdant Grimoire will also error out, showing the same recipe is missing as well.

Crash Report

No response

Log

https://gist.github.com/NovaLynxie/649c45a8796a23f6ac815c1104a8cd66

Additions and Modifications

Yes

Additions and Modifications Description

Added additional mods:

• Hexalia v1.2.4
• Patchouli v84.1-FORGE (for mod's guide book)
• EMI / JEI for viewing recipe (optional)

Did the issue happen in singleplayer or on a server?

Both

[rlnt]

Could you enable all options inside the debug config, reload the game, and upload the debug logs inside the logs folder? A zip archive of your configs and the debug logs would be nice.

[NovaLynxie]

Sure thing, here's the configs and relevant log files from testing: hexalia_unified_test_10-04-2025.zip
I did notice something peculiar though when I inspected the debug output, which I may have to let the hexalia dev know may be a problem. The affected recipe for the Sage Pendant here had one of it's recipe's items changed to a tag. "item:"minecraft:diamond" was changed to "tag":"forge:gems/diamond", so I am wondering if it is a recipe handling issue on Hexalia's side.

// recipes_before_unification.txt
hexalia:sage_pendant_transmutation [JSON]:{"type":"hexalia:transmutation","input":{"item":"minecraft:diamond"},"output":{"item":"hexalia:sage_pendant"},"salt_items":[{"item":"hexalia:spirit_powder"},{"item":"minecraft:gold_nugget"},{"item":"minecraft:book"},{"item":"minecraft:experience_bottle"}]}

// recipes_after_unification.txt
hexalia:sage_pendant_transmutation [JSON]:{"type":"hexalia:transmutation","input":{"tag":"forge:gems/diamond"},"output":{"item":"hexalia:sage_pendant"},"salt_items":[{"item":"hexalia:spirit_powder"},{"item":"minecraft:gold_nugget"},{"item":"minecraft:book"},{"item":"minecraft:experience_bottle"}]}

[NovaLynxie]

Issue has been resolved on the mod developer's side as of v1.2.5 of Hexalia to no longer use diamonds in the affected recipe, though it seems they use strictly item names rather than item tags which was causing the bug in the first place. Will continue to use config options to ignore the transmutation recipes in case AU tries to change other items in "hexalia:transmutation" recipes going forward.