You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Auto Sieve crashes when inserting sieveable items (NeoForge 1.21.1 + Ex Deorum 3.12) #400
Environment
Minecraft: 1.21.1
Loader: NeoForge
NeoForge Version: 21.1.43
Ex Compressum: 21.1.13.0
Ex Deorum: 3.12
Balm: Latest compatible version
Description
The Auto Sieve crashes the game whenever a sieveable item is inserted.
The Auto Sieve GUI opens normally, and meshes can be inserted without any issues. However, inserting a valid sieveable item (such as gravel) immediately crashes the client.
Manual sieves from Ex Deorum work correctly.
Steps to Reproduce
Create a new NeoForge 1.21.1 instance.
Install only:
Balm
Ex Deorum 3.12
Ex Compressum 21.1.13.0
Start a new world.
Place an Auto Sieve.
Insert any mesh.
Attempt to insert a valid sieveable item (e.g. Gravel).
Expected Behavior
The Auto Sieve should accept the item and begin processing it.
Actual Behavior
The client immediately crashes when the item is inserted.
Crash
The crash is a java.lang.NoSuchMethodError originating from Ex Compressum's Ex Deorum compatibility layer.
java.lang.NoSuchMethodError:
'the darkcolour.exdeorum.recipe.RecipeUtil.getSieveRecipes(...)'
at net.blay09.mods.excompressum.neoforge.compat.exdeorum.ExDeorumAddon.isSiftableWithMesh(...)
The crash occurs while the Auto Sieve checks whether the inserted item has a valid Ex Deorum sieve recipe.
Troubleshooting Performed
Reproduced in a completely fresh instance.
Only the following mods were installed:
Balm
Ex Deorum
Ex Compressum
No additional mods, resource packs, or datapacks.
Manual sieves work correctly.
Auto Sieve accepts meshes.
Crash only occurs when inserting a sieveable item.
Additional Information
This appears to be an incompatibility between Ex Compressum's Auto Sieve integration and the current Ex Deorum API, as the crash is caused by a NoSuchMethodError inside ExDeorumAddon.
Activity
fix: Update to newer versions of Ex Deorum #400