Issue description
If the added material has ore and gem and is a gem material type, the ore drop always becomes the gem processtype item, even if the oreDrop Module in the JSON File is supplied and references another item.
If later changed thru KubeJS for example, the JEI Addon which displays the ore drop info from EE is not updated and still shows the old drop.
Both is behavior which is unintended i think, or atleast logically the "oreDrop" Module should always outweight the processtype auto drop.
Steps to reproduce
Add material with type gem
add ore and gem as processtype
specify soem other drop in the oreDrop Module
Load game and observe that the oreDrop Module is ignored
Minecraft version
1.19.2 (Latest)
Forge version
1.19.2
Emendatus Enigmatica version
2.1.x (Latest)
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response
Issue description
If the added material has ore and gem and is a gem material type, the ore drop always becomes the gem processtype item, even if the oreDrop Module in the JSON File is supplied and references another item.
If later changed thru KubeJS for example, the JEI Addon which displays the ore drop info from EE is not updated and still shows the old drop.
Both is behavior which is unintended i think, or atleast logically the "oreDrop" Module should always outweight the processtype auto drop.
Steps to reproduce
Add material with type gem
add ore and gem as processtype
specify soem other drop in the oreDrop Module
Load game and observe that the oreDrop Module is ignored
Minecraft version
1.19.2 (Latest)
Forge version
1.19.2
Emendatus Enigmatica version
2.1.x (Latest)
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response