Fully automation of Assembling Line based on OpenComputers and AE, without renaming tricks.

[tribal smelt]

• **Applicable Tiers: **IV +
• Version: Tested on GTNH 2.6.1
• Features:
• • 1. Automation for all assembling line recipes. There's no need to manually build a database. You can just make an ME template and then request to craft it.
• • 2. Do not require a renaming trick to solve stacking conflict. Some recipe, for example, heavy alloy Ingot T4, or Fusion Reactor Computers, the have unfully stacked input items, which makes it hard to precisely dispatch the materials to the assembling line. This issue was sovled by renaming trick. (See pure AE automation on assebling line) But my system does not require renaming. You can just directly send the original materials.
• • 3. Fast scheduling: Previous automation work for assembling line by OC use transposers or robots to transfer the items from the input chest to the input buses. They bring high latency. My system make use of a local AE system, it uses OC to control the ME output bus to send the materials. What's more, The items without stacking issues could be parallelly sent to the assembling line, only those with stacking issues will be sent sequentially. And when the assembling line starts to craft, the OC system could immediately accept the next crafting request and dispatch the materials. of the next recipe, making a pipelined work. This accelerates the system further.
• • 4. Data Sticks could be automated. You can add the data stick of the output item, in the last slot of its ME template. If a recipe is sent with a encoded data stick, the OC system could insert the data stick into the data access hatch and remove it after finished.
• • 5. One computer could manage many assembling lines, as long as the computer could connect the component.
• Disadvantages: It requires to configure many address and directions in configuration file. Some understanding of oc and basic lua syntax is required

The codes are here: https://github.com/sxysxy/GTNH-AssemblingLine-Automation

So is anyone interested in it?

[sinful delta]

Some comments:

• You don't mention if this works with AALs, does it work with them? Specifically, is it able to hold in cache multiple stacks for each slot and push them as needed?
• Have you measured the delay between the recipe packet being pushed and the AL starting a craft?
• In the mid-late game you need hundreds of AALs, they are very time consuming to build even with ring of loki. Have you tested scaling it in terms of how performance is affected?
• Renaming items using a multiblock forming press is very fast, and can be configured quickly. It seems like you need to manually copy-paste 20 opencomputers component addresses per AL.
• It's impractical to encode the data stick as an input to a pattern because you will need hundreds of duplicate data sticks when only one could work in principle. Do you have any workaround for this?

[tribal smelt]

Well, thank you for the comments! About your questions, the current answers are:

• 1. No, I have not tested it on AAL, I just finished IV and went into LuV times, I will test it on AAL later
• 2. It's usually no more than 10 seconds. (usually more faster) And I optimize it with pipelined work. For example, the AL requires 10 seconds to process the recipe, and the OC needs 10 seconds to dispatch the material. When the AL is processing the recipe, the input buses are empty so OC could dispatch the materials at the same time. So the additional latency only appears for the first time.
• 3. The program is designed to deal with multiple ALs. When the OC computer is waiting for an AL(Even if it's only 1-tick time), it could switch to control another AL. So the performance limitation is just due to the game itself.
• 4. Renaming is fast but not elegant, right? You have to manully build some renaming automations. I think it's ugly.
• 5. My system could also accept recipe without a data stick. The data stick is optional. If you send a recipe with a data stick, my system will send it into data access hatch and later fetch it. If you don't send with a data stick, it also works!

Appreciate for your valuable comments!

[sinful delta]

No problem. Good luck in LuV

[tribal smelt]

Hmm, I'm not good at oral English to make a video explaining how to use and how it works. Only static pictures and texts are not so clear....If anyone would like to try it, I can offer help... An open-world game embraces all possibilities, maybe just try something interesting for fun😁