User:Alfonse/Personal logistics

Logistics requests

Logistics groups

A series of logistics requests can be grouped together. These groups can be named or unnamed.

Named logistics groups are a shared global

Blueprints

If an entity which uses a logistics group is captured in a blueprint, all of the settings in that group will be stored in the blueprint. Pasting the blueprint will put all of those values into the pasted entity.

The above includes named logistics group. However, named groups are global. As such, if a group with that name already exists when you paste the blueprint, the contents of that group will not be changed by pasting the blueprint. That is, if you have changed a logistics group's contents in the world, pasting a new blueprint which uses that group will not undo your changes.

Constant combinators

Constant combinators can use named logistics groups, allowing signals to be sent to a circuit network that matches the request values in a logistics group. However, logistics requests for a particular item have 2 numbers attached to them: the minimum amount to request desired and the maximum amount to retain before trashing the rest. Circuit networks can only assign a single value to a signal. When a constant combinator uses a logistics group, the value it sends is the minimum requested amount, not the amount to retain.

Note also that the UI for setting a constant in a combinator does not provide a way to specify the maximum retention amount. So if you set a new signal into a named logistics group through a constant combinator, the maximum value will default to infinity. If you modify the value of an existing signal which has a maximum value, it will be unaltered.

Roboport requests

Roboports have a system similar to logistics requests for requesting construction robots and logistics robots. However, they do not request from a logistics network in the same way as a standard logistics request. Instead, these represent requests for some number of robots of that type to return to this roboport. If you request 50 construction bots, then idle construction bots will make their way to that roboport until at least 50 are there. This is useful for ensuring the locality of requests.

Roboport requests differ from logistics requests in several ways. They have no trashing/maximum functionality, so you cannot provide a maximum number of robots to have at the roboport. Furthermore, while roboport requests can be named like logistics groups (thus allowing requests to be shared), they are not in the same space of names as proper logistics groups. That is, a roboport request and a logistics group can have the same name, but they will have different requests.

Space Age

In the Space Age expansion, cargo landing pads gain the ability to make logistics requests. Space platforms also have the ability to make logistics requests. In both cases, these requests are not (directly) made to a logistics network; they are instead made to specific entities on other surfaces. Though they do not request from a logistics network, the user-interface for them is (almost) identical to any other logistics

Space platforms

When a space platform is in orbit around a planet, it can send logistics requests to the planet below. These requests are not directly handled by any particular logistics network. They are instead handled by rocket silos.

Every rocket silo on the planet will receive all requests from space platforms. Rocket silos can be set to automatically forward any platform requests to the local logistics network that the platform resides in. If a platform requests a rocket load of assemblers, and a rocket silo using this setting is in a logistics network that contains at least the requested amount of assemblers,

Rocket silos can also be loaded via non-logistics network means. If a rocket silo that is not using logistics has a rocket load of an item that is being requested by a platform, the silo will automatically launch it to that platform. Alternatively, the circuit network can be used to read requests from platforms through the rocket silo. Circuit network conditions and combinators can be used to allow inserters to load the silo with requested materials.

Each individual item requested by space platforms targets a specific planet. This means that requests for an item are sent to a specific planet. The UI to specify which planet to request from can only be access from a space platform. If you create a new request in a named logistics group that is shared with a platform from outside of the space platform's UI, it will use the default planet for that item. The default planet is usually Nauvis unless the main recipe for that item is restricted to a specific planet, in which case it defaults to that planet.

So if you share a logistics group between a platform and the destination planet, you will need to set any new requests in the space platform's version of the logistics group.

See also

• Player
• Tank
• Spidertron
• Requester chest and Buffer chest
• Space platform
• Cargo landing pad (only has logistics requests in Space Age).