Issue type:
Short description:
I'm playing ATM10, which has a very large number of recipes for the crafting table. When I place an Attuned Crafting Interface on a Crafting Table, the game very quickly becomes laggy; I was never able to see the interface get rendered, and when I opened my storage terminal, none of the items or recipes displayed and the game became unresponsive. I assume this is because of the large number of recipes, because the interface handles machines like Mekanism's Metallurgic Infuser without issue.
Because I've updated the Integrated mods beyond what the pack offers, I thought it'd be more prudent to report the bug here, instead of to the ATM devs. I'll make my report there if it is the right procedure in this case.
Steps to reproduce the problem:
- Boot up All The Mods 10-4.10 with the specified versions of the Integrated Mods.
- Place a crafting table next to an Integrated Dynamics network.
- Connect the crafting table to the network with an Attuned Crafting Interface.
- (Optional) Open a storage terminal on that network.
Expected behaviour:
The recipes are exposed to the network, viewable in the storage terminal without framerate or tickrate issues, like they are for machines with fewer recipes.
Versions:
- This mod: 1.3.1
- Minecraft: 1.21.1
- Mod loader version: Neoforge 21.1.203
Log file:
Issue type:
Short description:
I'm playing ATM10, which has a very large number of recipes for the crafting table. When I place an Attuned Crafting Interface on a Crafting Table, the game very quickly becomes laggy; I was never able to see the interface get rendered, and when I opened my storage terminal, none of the items or recipes displayed and the game became unresponsive. I assume this is because of the large number of recipes, because the interface handles machines like Mekanism's Metallurgic Infuser without issue.
Because I've updated the Integrated mods beyond what the pack offers, I thought it'd be more prudent to report the bug here, instead of to the ATM devs. I'll make my report there if it is the right procedure in this case.
Steps to reproduce the problem:
Expected behaviour:
The recipes are exposed to the network, viewable in the storage terminal without framerate or tickrate issues, like they are for machines with fewer recipes.
Versions:
Log file: