Dedicated server disconnect/crash when inserting sieveable items into Ex Compressum Auto Sieve (regression after partial fix) #401

Minecraft Version

1.21.1

Mod Loader

NeoForge

Describe the Issue

The previous fix resolved the issue in singleplayer/integrated servers, however the problem still occurs on dedicated NeoForge servers.

Environment
Minecraft: 1.21.1
Loader: NeoForge 21.1.241
Ex Deorum: 3.12
Ex Compressum: 21.1.14.0

Steps to Reproduce
Start a dedicated NeoForge server.
Join the server.
Place an Ex Compressum Auto Sieve.
Insert any valid mesh.
Insert any valid sieveable item (e.g. Gravel, Sand, Dust).

Expected Behaviour
The Auto Sieve accepts the item and begins processing it normally.

Actual Behaviour
As soon as a valid sieveable item is inserted into the Auto Sieve:
Every connected player is disconnected/crashes.
The dedicated server remains running.
The issue is 100% reproducible.
The exact same setup works correctly in singleplayer.

Additional Information
This appears to be a regression or an incomplete fix of the previously reported issue.

The previous update fixed the problem for integrated (singleplayer) servers, but dedicated servers still reproduce it consistently.

Based on the attached crash logs, the crash still occurs during the interaction between Ex Compressum and Ex Deorum when checking whether an item is valid for the Auto Sieve. The stack trace still ends in RecipeCaches.getSieveRecipes() because sieveRecipeCache is null.

Logs

crash-2026-07-25_15.49.34-client.txt