Factorio Forums

About

• Items are moved directly between connected nodes(chests), expending power in the process. Transportation is not limited by distance, however larger distances require increasing power.
• Network Power requires conditioning and is not pulled directly from the electricity grid. Energy buffers must be placed and connected to the circuit network to provide the required power.
• Item transfers are coordinated and controlled by a Network Controller. A minimum of one controller is required per network. Additional controllers provide no inherit benefits but can be used to share power between distinct networks.
• Devices can be connected to both a red and green network. This allows that device to share its contents with, or request items from, either network.
• Items can be provided to, or requested from, the logistics network via purpose-made chests.

Mod Portal

Example Setups

Basic Network

• Inputs: Copper and Iron plates
• Intermediate: Gears
• Results: Belts and Red Science

Setup


Alt Mode

FAQ

• Is this intended to be a bot network replacement?
  Not exactly, while it can largely replace the logistics network, it can not fully replace it, and is designed to work with it.
• How can I see all the items in the network?
  The easiest way is to press N(default) to open the overview window. You can also mouse over a power pole that is carrying the network to see the signal counts.
• Where did the name come from?
  The name is inspired from a minecraft mod I used to work closely with, Applied Energistics, (shameless plug) as I am also the author of Thaumic Energistics

History

Beta Notes

• Naming and color scheme is inverted compared to base factorio, "Provider Interface" has "Energistic Requests" GUI. (Probably due to minecraft naming being inverted?)
• Energy Buffer does not charge when a (default configured) electric-energy-interface is on the same network.
• Constant blinking of "not in logistic range" icon when not near roboports for provider/requester. (there might be a prototype flag against this...)
• Can't dupe items with constant combinators, my hopes are shattered ;(.

/c
 script.on_event(defines.events.on_built_entity,function(e)
  if e.created_entity.ghost_name then
   local _
   _,e.created_entity = e.created_entity.revive()
   script.raise_event(defines.events.on_built_entity,e) --[[will error "Player attempted to open unregistered entity" when not raising, as expected]]
   end
  end)

Attal wrote:Hi Nividica!

very nice job!

I've tryed it a bit ypur mod:
+ Great new idea with transportation
+ In can easily replace bots!
+ In can replace rails when you set ~zero energy consumption
+ configurable power consumption can be changed to infinite research "Low energy transportation"
+ what about game performance?
+ A bit strange decision to use accumulator for energy:
with solar+accu energy setup it charges only when solar panels are active (and don't when accumulators supply factory)

• Push 100 Iron Plates
• Find next target
• Calculate max power requirements ((100 * power-per-item) + (distance * power-per-chunk))
• Does network have enough power?
• No, only enough for 50 plates, reduce send count
• Push 50 plates
• Chest only accepted 30
• Add (30 * power-per-item) + (distance * power-per-chunk)
• Find next target

thaelina wrote:The wiki states for network interface chests that "If an item is added to the chest which does not match any filter, or causes the amount stored to exceed the request amount, that item is pushed to the network."
However in the attached setup, the interface chest only has 400 iron plates as a filter but the other items in the chest aren't being pushed to connected chests.

EDIT: After a little experiementing and turning off all the other mods, Im pretty sure it has to do with the stack sizes. It doesn't appear to play nice with larger stack sizes. Also on that same note, the filters don;t take into account much larger stack sizes.

eradicator wrote:Hah, more former minecraft modders turning to factorio. Thy be welcome! (Though i have do admit i think i never got around playing with thaumic logistics even though i had it in my custom pack, shame on me.) And to be honest i never expected anyone do actually port AE to factorio, though it has been suggested a few times. Mostly performance concerns from my side.

Here's some stuff i noticed after fiddling for 10 mins (mod portal version 0.9.0):

• Naming and color scheme is inverted compared to base factorio, "Provider Interface" has "Energistic Requests" GUI. (Probably due to minecraft naming being inverted?)
• Energy Buffer does not charge when a (default configured) electric-energy-interface is on the same network.
• Constant blinking of "not in logistic range" icon when not near roboports for provider/requester. (there might be a prototype flag against this...)
• Can't dupe items with constant combinators, my hopes are shattered ;(.

Wanted to do some perf testing but your event handling breaks when trying to insta-revive ghosts. Build a blueprint after using the following:

Code: Select all

/c
 script.on_event(defines.events.on_built_entity,function(e)
  if e.created_entity.ghost_name then
   local _
   _,e.created_entity = e.created_entity.revive()
   script.raise_event(defines.events.on_built_entity,e) --[[will error "Player attempted to open unregistered entity" when not raising, as expected]]
   end
  end)

silentz0r wrote:Hey, this looks awesome, can i use it along side bob's/angel's?

Nividica wrote: I decided to name the provider and requester chests after their logistics counterpart, as those two chests are designed to interact with the logistics network.
Does the storage and network interface(green) chests complain about not being in range of a bot net? Only the provider and requester chests should.
The energy buffer still needs some work, and may be replaced entirely if I can find a way around it.
And I have no idea about the script, I will have to dig into what ghost entites do/dont

eradicator wrote:

Nividica wrote: I decided to name the provider and requester chests after their logistics counterpart, as those two chests are designed to interact with the logistics network.
Does the storage and network interface(green) chests complain about not being in range of a bot net? Only the provider and requester chests should.
The energy buffer still needs some work, and may be replaced entirely if I can find a way around it.
And I have no idea about the script, I will have to dig into what ghost entites do/dont

1) The GUI title does not match the chest name is what i meant.
2) Yes, only those two. BlinkBlink to insanity
3) Around might be difficult.
4) For the most part they "don't", they're just placeholders that wait to be revived. The problem is that if i revive them in script instead of building them with robots/hands then on_built_entity is not raised and the chests aren't registered. So i tried to work around that by raising the event manually. (Reason: I wanted to spam a few hundret chests to see how the performance is)

account_on_factorio wrote:if manually fill network.interface.chest ( ctrl_left click) with 1.6k items, the transfer stops , stuck

account_on_factorio wrote:a message like "running out of power"

account_on_factorio wrote:and with a filter you see the amount

account_on_factorio wrote:a possibility to move all the contens of the storage chests , like storage.cells of applied.energistice in MINECRAFT

account_on_factorio wrote:where will be the main discussion

account_on_factorio wrote:(netwoks ticks are set to 1)...allways 60 FPS/UPS

eradicator wrote: Wanted to do some perf testing but your event handling breaks when trying to insta-revive ghosts. Build a blueprint after using the following:

Code: Select all

/c
 script.on_event(defines.events.on_built_entity,function(e)
  if e.created_entity.ghost_name then
   local _
   _,e.created_entity = e.created_entity.revive()
   script.raise_event(defines.events.on_built_entity,e) --[[will error "Player attempted to open unregistered entity" when not raising, as expected]]
   end
  end)

/c
 script.on_event(defines.events.on_built_entity,function(e)
  if e.created_entity.type == "entity-ghost" then
   local _
   _,e.created_entity = e.created_entity.revive()
   script.raise_event(defines.events.on_built_entity,e)
   end
  end)

eradicator wrote:Also found something else: My test setup is just a single interface+storage chest. If the interface is filled up completely while the energy buffer is empty it doesn't restart transport even when energy becomes available again.

My test setup still won't work though, only one storage chests is ever used. Here's the blueprint (repeated about 100 times):

I played around with your blueprint, and had quite a bit of fun setting up various tests.

account_on_factorio wrote: - if i try to put more items in interface.chests, ore use more interface chests , the transfer stucks,
if reduce to < 1000 ( maybe <1024 ) transfer is about 300 / sec