Server Crash Caused by Automated Crafting Using the Packager

[ZMDriedFish]

Context

Note: Please note that I am not proficient in English, so this entire issue report has been translated by AI.

Description:
I cultivated a large number of Mystical Agriculture crops, used Storage Drawers to collect them, and then utilized the Packager and Mechanical Crafters from the Create mod to automate resource production. After setting everything up, I left an AFK (Away From Keyboard) bot running and disconnected from the server. Shortly afterward, the server crashed. I am unsure what caused the issue.

Attachments:
Attached below are partial logs from before the crash and the full crash report.

log.log

Crash Report

https://mclo.gs/DyD6QfU

[ZMDriedFish]

Description:
I encountered a critical issue when attempting to remove my machinery setup. Here are the details:

Packager Duplication Bug:
When trying to break a Packager (even with a wrench), it respawns immediately at the same position without dropping any items.
If removed with a wrench, the Packager reappears, and an extra one is added to my inventory.

Console Errors and World Freeze:
Failed removal attempts trigger a java.util.NoSuchElementException: No value present error in the console.
After this error, the world stops updating (e.g., boilers halt, blocks like doors cease animations).

Temporary Fix:
The issue sometimes resolves after multiple attempts or waiting, allowing normal removal and item drops.

Possible Trigger:
This bug might relate to my autocrafting setup. The Factory Gauge spammed endless requests due to insufficient materials, which could have overloaded the system.

[BlueCrafter6]

Possible Trigger:
This bug might relate to my autocrafting setup. The Factory Gauge spammed endless requests due to insufficient materials, which could have overloaded the system.

If your Factory Gauge is in fact spamming, you can adjust the expiry of the promises in its UI. There's an option for how long the Factory Gauge should wait before placing a new order to fulfil its target.

[ZMDriedFish]

Possible Trigger:
This bug might relate to my autocrafting setup. The Factory Gauge spammed endless requests due to insufficient materials, which could have overloaded the system.

If your Factory Gauge is in fact spamming, you can adjust the expiry of the promises in its UI. There's an option for how long the Factory Gauge should wait before placing a new order to fulfil its target.

Thank you very much. I already know.

I have stopped using the packager for automatic crafting, but the following error message still appears in the server logs every ten seconds consistently:

[Server thread/ERROR] [minecraft/LevelChunk]: A BlockEntity type com.simibubi.create.content.logistics.packager.PackagerBlockEntity has thrown an exception trying to write state. It will not persist, Report this to the mod author
java.util.NoSuchElementException: No value present
at java.base/java.util.Optional.orElseThrow(Optional.java:377) ~[?:?]
at TRANSFORMER/create@6.0.2/com.simibubi.create.content.logistics.packager.PackagerBlockEntity.write(PackagerBlockEntity.java:569) ~[create-1.21.1-6.0.2.jar%23234!/:6.0.2]

I would like to know why this is happening despite no longer using the packager?

[BlueCrafter6]

at java.base/java.util.Optional.orElseThrow(Optional.java:377) ~[?:?]
at TRANSFORMER/create@6.0.2/com.simibubi.create.content.logistics.packager.PackagerBlockEntity.write(PackagerBlockEntity.java:569) ~[create-1.21.1-6.0.2.jar%23234!/:6.0.2]

The latest release of the Create Mod is 6.0.4. I'm not sure if your version (6.0.2; judging by the error line) is causing the issue. Try upgrading and see if there's a difference.

[ZMDriedFish]

The latest release of the Create Mod is 6.0.4. I'm not sure if your version (6.0.2; judging by the error line) is causing the issue. Try upgrading and see if there's a difference.

Thank you very much for your suggestions. However, my current server is running a lower version of NeoForge, which cannot support Create 6.0.4. Upgrading the version would be complicated for my setup, so I'll keep things as they are for now. If similar issues occur after I migrate to a newer version of Create in the future, I'll reach out again.