Good Practices With AE: Difference between revisions

feedback from discord
(forgot one tip)
(feedback from discord)
Line 5:
* Always put the highest multiple of a recipe if you can, as it reduces queries for AE. Example: you want to automate the craft of 1 iron dust from 1 iron ingot. Automating it like that will make 64 queries if you want a stack of it. Automating 64 iron dusts from 64 iron ingots will only make 1 query if you want a stack of it.
* Always prefer recipes without reusable items if you can: it impacts server tps because it needs to calculate if it can reuse the items after each query. Example: you should aim for the assembler recipe of the machine casing instead of the crafting grid recipe.
* IfAvoid youusing can, avoid usingrecursive subnetworks for storage: This is a good way to trigger a lot of updates at once if you do it. (Famous example of a laggy storage subnetwork is the Super Soaryn Drive.) However, storage subnetworks can improve tps by reducing the number of IO operations on the main net if used properly.
* If you want to use crafting cards in export busses or interfaces or in general if you want to perform some form of stock keeping, reduce the queries as much as you can: Use the 1st point of this list and if it's still spamming the queries, consider making the needed items outside of AE and import them in AE once they are done.
* Always make subnetworks when you'll do something that will cause a big I/O to your item and/or fluids. This way you contain the update to the subnetwork, and lookups for item/fluids are instant. For instance ores and intermediate items from ore treatment don't need to go in the main network, you should only send the end items to the main network.