Autocrafting in a sub network

[jinkhya]

Hello guys,

I was wondering if it's possible to have machines with an interface containing the recipes in a subnetwork and then to request crafting on those machines from my main network.
I attached a storage bus on an interface and the opposite but no luck, none of them allow me to see the crafting options in my main network.
I've seen that it works fine with storage like my barrels but not with crafting. Is that intended or is there a solution to that problem?

Thanks
Jin

 

[jordsta95]

It should work, though I have no idea how sub-networks work.

Do you have all the pre-requisites for auto-crafting: crafting core (I forget the name), crafting co-processor (a good idea to have), and the molecular assembler receiving power?

 

[jinkhya]

yes, before I had my crafting in my main network and it was working perfectly but I'm moving it kinda far from my main network so I wanted to create a subnetwork.

 

[Zarkov]

Last time I tried, it wasn't possible to have auto-crafting set up in sub-networks. I assume you can use quantum bridges though.

In my current world I ended up moving the controller to my auto-crafting area, since most other stuff only needs a single channel (storage) or a handful of them (terminals).

 

[Ieldra]

Machines that do auto-crafting by request of an element of a network must be part of the same network. You can connect through quantum bridges across dimensions, but machines on subnetworks won't work. There must be a channel connection between the requesting interface, assembler or terminal and the processing machine.

For that reason, I always subnetwork my storage networks to my crafting networks and not the other way round.

 

[Dentvar]

I´m in the same mess. For now I just redesineg my base to have the "main network" my crafting one.
But for how far my theorie goes it should be possible.

Given you have a main network with a ME-Terminal. This Terminal is were you want to request the crafts. Now you have a subnetwork with all the autocraft stuff setup.

The conexion that does the sub network would be a interface on the Main Network side and a storagebus on the subnetwork one.
Now you have to put in all the crafting patterns into this interface. Reason is that the main network looks into all the atached interfaces and the patterns inside.
If you then request a craft this will tall the interface to craft the requested item in the next block you atached. In your case the storage Bus and the following subnetwork.
The subnetwork has to know how to get the requested item also. So you have to make a second pattern for the requested item and put it in the acctual interface that is atached to the assambler.

As I said, this is what is happening in my head for 2 days but I had no time to try it out in Minecraft. Also I was thinkin about putting a "process pattern" into the first interface so it just requests item "X" to the subnetwork.
Only problem here I see is that you will need a lot of interfaces that goes into the crafting subnetwork and you have to dublicate all of the patterns. But it should work.

 

[jinkhya]

alright, thanks guys for your quick answers, I'll do something else then. ks guys for your quick answers, I'll do something else then.

 

[Cpt_gloval]

Dentvar is correct. The interface on the main network as well as the interface in the sub network would need the crafting pattern.

Your best bet is a p2p directly off the cpu. On the other end put 3 dense cables then, using colored glass cable, you can string out 32 connections for interfaces and import /export busses.

 

[Dentvar]

Dentvar is correct. The interface on the main network as well as the interface in the sub network would need the crafting pattern.

Your best bet is a p2p directly off the cpu. On the other end put 3 dense cables then, using colored glass cable, you can string out 32 connections for interfaces and import /export busses.

Lets give you a coockie. You said I¨m right in something

I still have to learn about p2p conectors. But why do you have to put this onto the CPU directly? As long as the CPU is inside the subnetwork does it matter?

 

[Cpt_gloval]

I'm referring to the main AE cpu, controller. P2p directly on the cpu will allow you to send the entire 32 channels out without using a boat load of expensive dense cables.

 

[HSIkMy]

I´m in the same mess. For now I just redesineg my base to have the "main network" my crafting one.
But for how far my theorie goes it should be possible.

Given you have a main network with a ME-Terminal. This Terminal is were you want to request the crafts. Now you have a subnetwork with all the autocraft stuff setup.

The conexion that does the sub network would be a interface on the Main Network side and a storagebus on the subnetwork one.
Now you have to put in all the crafting patterns into this interface. Reason is that the main network looks into all the atached interfaces and the patterns inside.
If you then request a craft this will tall the interface to craft the requested item in the next block you atached. In your case the storage Bus and the following subnetwork.
The subnetwork has to know how to get the requested item also. So you have to make a second pattern for the requested item and put it in the acctual interface that is atached to the assambler.

As I said, this is what is happening in my head for 2 days but I had no time to try it out in Minecraft. Also I was thinkin about putting a "process pattern" into the first interface so it just requests item "X" to the subnetwork.
Only problem here I see is that you will need a lot of interfaces that goes into the crafting subnetwork and you have to dublicate all of the patterns. But it should work.

I prefer getting a hole for base early-game(As digging hole gives you cobbles which can be compressed and thrown into smeltery ._.) and build a network there. Once you get a more complex base use the old base's network entirely as a storage network and the new base would be the crafting network. It's pretty simple as you don't have any autocrafting in your old base only drives, and you don't need to even move the drives!