Discover tags

This is a simple automation I've come up with while playing ATM10. It takes the recipe materials from the barrel/chest and outputs the finished processors to the same chest (you may change that by modifying the code). There are probably easier and more efficient ways to do so, but this one just works, and it's easy to set up. PS: I think that more inscribers making Silicon Circuits would make this setup way more efficient if you plan on bulk crafting. Note: You can use this setup to automate the craftings using an AE2 Pattern Provider, but I would advise using Slicers and Crystal Assemblers for that, as this build is intended for the early game. We already have a build including code and explanation on how to do that on the SFMHub.

The main goal of this build is to automate the crafting of the Applied Flux Redstone Crystal, just because this is a build I made in survival, and I found no other reason to automate other Crystal Assembler recipes other than this one, but feel free to automate anything using the same code pattern shown here. The recipe is doubled, so if you're automating using a pattern provider, be sure to multiply the resource amount by how many times you think it is reasonable. We're using a strategy where if we split the total amount we want to craft into multiple machines (still following the minimal resources needed for each recipe), we'll finish the crafting faster than one single machine with a bunch of resources. Just know that there is probably a sweet spot where you may send more than one recipe resource to a single machine to make it still busy until the next input feeding cycle starts, and that an amount over that will make the crafting less efficient by not utilizing as many machines as possible.

The code includes recipes for 3 Reaction Chamber types of craftings, they are: Lava, Water, and Quantum. This means you need a tank (any tank) with those resources, as shown in pictures 3, 4, and 5, and preferably a way to keep them full. If you're going to use any more item recipes that aren't in these codes, just modify the code to include them, following the same existing pattern. There are 3 distinct codes for each Reaction Chamber recipe type. Be sure to correctly split it into the 3 Factory Manager "Computers" and push the labels correctly and separately, just like shown in the images. You may actually completely remove the energy transfer part from the code if you're connecting at least one of the Reaction Chambers to an online AE2 cable, as they already provide energy to the machines. PS: Yes, the redundant part of excessive filtering is necessary, for some reason it wasn't behaving properly without it and wasn't correctly delivering the output to the system, God knows why, but it just works this way, so I wouldn't remove it. NOTE: Some recipes have been multiplied, this will matter if you don't set the recipe amount correctly for the crafting pattern and order a craft that uses less than the minimum amount of materials set to be distributed to each machine, otherwise it works fine, but be sure to set your crafting patterns to use the right amount of materials (and products, for that matter) used in the codes.

You may or may not use Applied Energistics to automate this; it works as is. The goal of this automation is to make an expandable factory for any Crusher or Enrichment Chamber recipe. The code is plain simple, you take energy from the accessor (can be a Cube, but will require side specification) and insert on the machines and retain a low amount of items from the input chest (can be connected to an AE2 provider) to each crusher/chamber. This will optimize craftings that take too long because the number of items to process is too high for a single machine, now spread across multiple machines. I've set the retain amount to 9 (a mekanism machine at the Ultimate tier have 9 slots), but you can use something higher or lower, just know that if a higher value than the total slots is set it will use less machines at a time, it will output items to each machine until it reaches that amount and move on to the next machine, it would be wiser to increase the amount of machines rather than this number. I have used 25 machines for this example, but that's just for symmetry; you can definitely use fewer than that, and it would be enough to handle basically any amount of items you may need to process. NOTE: You MUST specify sides for Mekanism machines input and output or else the SFM won't be able to take or insert from that machine. PS: This post includes two codes of two builds for two different types of machines that behave the same way, the code is literally the same, because of this I will rename the machines to just "machine" instead of the specific name, but feel free to modify it as you wish.