Processing pattern LMA crash loop

[Tiketika]

Your GTNH Discord Username

tiketika

Your Pack Version

daily 369

Your Server

private server

Java Version

Java 25

Type of Server

None

Your Actions

I accidentally put a processing/ultimate pattern in the Large Molecular Assembler. When i requested this item the server crashed and got stuck in a crash loop after restarting, forcing me to load a backup.

Crash Report

Description: Exception in server tick loop

java.lang.IllegalStateException: Not a crafting recipe!
at appeng.helpers.UltimatePatternHelper.getOutput(UltimatePatternHelper.java:203)
at gregtech.common.tileentities.machines.multi.MTELargeMolecularAssembler.lambda$pushPattern$7(MTELargeMolecularAssembler.java:629)
at gregtech.common.tileentities.machines.multi.MTELargeMolecularAssembler.withAeJobs(MTELargeMolecularAssembler.java:404)
at gregtech.common.tileentities.machines.multi.MTELargeMolecularAssembler.pushPattern(MTELargeMolecularAssembler.java:627)
at appeng.me.cluster.implementations.CraftingCPUCluster.executeCrafting(CraftingCPUCluster.java:835)
at appeng.me.cluster.implementations.CraftingCPUCluster.updateCraftingLogic(CraftingCPUCluster.java:701)
at appeng.me.cache.CraftingGridCache.onUpdateTick(CraftingGridCache.java:155)
at appeng.me.Grid.update(Grid.java:270)
at appeng.hooks.TickHandler.onTick(TickHandler.java:192)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_1238_TickHandler_onTick_TickEvent.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:140)
at cpw.mods.fml.common.FMLCommonHandler.onPostServerTick(FMLCommonHandler.java:247)
at net.minecraft.server.MinecraftServer.tick(MinecraftServer.java:590)
at net.minecraft.server.integrated.IntegratedServer.tick(IntegratedServer.java:111)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)

Final Checklist

• I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the crash still exists will prompt us to investigate and reopen it once we confirm your report.
• I can reproduce this crash consistently by following the exact steps I described above.
• I have asked other people and they confirm they also crash by following the exact steps I described above.