Logistic network - Revision history

Sorahn: Add Cargo landing pad icon to robot priority sources

2026-01-18T02:04:53Z

Add Cargo landing pad icon to robot priority sources

← Older revision		Revision as of 02:04, 18 January 2026
Line 196:		Line 196:
	{\| class="wikitable"		{\| class="wikitable"
	! Source Priority		! Source Priority
	\| {{icon\|Character logistic trash slots (research)\|\|logistic robotics (research)}}{{icon\|active provider chest}} > {{icon\|storage chest}}{{icon\|buffer chest}} > {{icon\|passive provider chest}}		\| {{icon\|Character logistic trash slots (research)\|\|logistic robotics (research)}}{{icon\|active provider chest}} > {{icon\|storage chest}}{{icon\|buffer chest}} > {{icon\|passive provider chest}} {{icon\|Cargo landing pad}}
	! Target Priority		! Target Priority
	\| {{icon\|Character logistic slots (research)\|\|logistic robotics (research)}}{{icon\|requester chest}}<sup>1</sup> > {{icon\|requester chest}} > {{icon\|buffer chest}}<sup>2</sup> > {{icon\|storage chest}}<sup>3</sup>		\| {{icon\|Character logistic slots (research)\|\|logistic robotics (research)}}{{icon\|requester chest}}<sup>1</sup> > {{icon\|requester chest}} > {{icon\|buffer chest}}<sup>2</sup> > {{icon\|storage chest}}<sup>3</sup>

Cardinal: Removed duplicate notes.

2025-12-06T10:22:10Z

Removed duplicate notes.

← Older revision		Revision as of 10:22, 6 December 2025
Line 44:		Line 44:

	<sup>(2)</sup> Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].		<sup>(2)</sup> Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

	~~<sup>(3)</sup> Tanks can only set logistics requests if [[Logistic system (research)\|logistic system]] has also been researched.~~

	== Usage ==		== Usage ==

Bilka: style edits to logi groups + space age requests

2025-11-24T15:05:03Z

style edits to logi groups + space age requests

Cuyama: /* Items */

2025-11-09T03:14:15Z

Items

← Older revision		Revision as of 03:14, 9 November 2025
Line 34:		Line 34:
	\| {{Imagelink\|Rocket silo}} \|\| {{SA}} If "Automatic requests from space platforms" is set, requests items from the logistic network based on requests from space platforms.		\| {{Imagelink\|Rocket silo}} \|\| {{SA}} If "Automatic requests from space platforms" is set, requests items from the logistic network based on requests from space platforms.
	\|-		\|-
	\| {{Imagelink\|Player}} \|\| rowspan="3" \| Can set logistic requests to function as a requester chest.		\| {{Imagelink\|Player}} \|\| rowspan="3" \| Can set logistic requests to function as a requester chest.<sup>3</sup>
	\|-		\|-
	\| {{Imagelink\|Tank}}~~<sup>3</sup>~~		\| {{Imagelink\|Tank}}
	\|-		\|-
	\| {{Imagelink\|Spidertron}}		\| {{Imagelink\|Spidertron}}

Cuyama: /* Items */

2025-11-09T00:56:14Z

Items

← Older revision		Revision as of 00:56, 9 November 2025
Line 17:		Line 17:
	\| {{Imagelink\|Logistic robot}} \|\| Moves items between logistic chests.<sup>1</sup>		\| {{Imagelink\|Logistic robot}} \|\| Moves items between logistic chests.<sup>1</sup>
	\|-		\|-
	\| {{Imagelink\|Construction robot}} \|\| [[Repair pack\|Repairs]] broken or replaces destroyed entities. [[blueprint\|Builds]], [[deconstruction planner\|deconstructs]] and [[upgrade planner\|upgrades]] entities on command. Deliver item requests and execute item removal requests created in [[remote view]].		\| {{Imagelink\|Construction robot}} \|\| [[Repair pack\|Repairs]] broken or replaces destroyed entities. [[blueprint\|Builds]], [[deconstruction planner\|deconstructs]] and [[upgrade planner\|upgrades]] entities on command. Deliver item requests and execute item removal requests created in remote view.
	\|-		\|-
	\| {{Imagelink\|Active provider chest}} \|\| Logistic chest: Pushes stored items into the logistic network.<sup>2</sup>		\| {{Imagelink\|Active provider chest}} \|\| Logistic chest: Pushes stored items into the logistic network.<sup>2</sup>
Line 36:		Line 36:
	\| {{Imagelink\|Player}} \|\| rowspan="3" \| Can set logistic requests to function as a requester chest.		\| {{Imagelink\|Player}} \|\| rowspan="3" \| Can set logistic requests to function as a requester chest.
	\|-		\|-
	\| {{Imagelink\|Tank}}		\| {{Imagelink\|Tank}}<sup>3</sup>
	\|-		\|-
	\| {{Imagelink\|Spidertron}}		\| {{Imagelink\|Spidertron}}
	\|}		\|}

	<sup>(1)</sup> Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].		<sup>(1)</sup> Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)\|worker robot cargo size]].

	<sup>(2)</sup> Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].		<sup>(2)</sup> Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

			<sup>(3)</sup> Tanks can only set logistics requests if [[Logistic system (research)\|logistic system]] has also been researched.

	== Usage ==		== Usage ==

Tertius3: /* Items */ construction bots also execute item delivery and removal requests in remote view

2025-09-26T11:15:57Z

Items: construction bots also execute item delivery and removal requests in remote view

← Older revision		Revision as of 11:15, 26 September 2025
Line 17:		Line 17:
	\| {{Imagelink\|Logistic robot}} \|\| Moves items between logistic chests.<sup>1</sup>		\| {{Imagelink\|Logistic robot}} \|\| Moves items between logistic chests.<sup>1</sup>
	\|-		\|-
	\| {{Imagelink\|Construction robot}} \|\| [[Repair pack\|Repairs]] broken or replaces destroyed entities. [[blueprint\|Builds]], [[deconstruction planner\|deconstructs]] and [[upgrade planner\|upgrades]] entities on command.		\| {{Imagelink\|Construction robot}} \|\| [[Repair pack\|Repairs]] broken or replaces destroyed entities. [[blueprint\|Builds]], [[deconstruction planner\|deconstructs]] and [[upgrade planner\|upgrades]] entities on command. Deliver item requests and execute item removal requests created in [[remote view]].
	\|-		\|-
	\| {{Imagelink\|Active provider chest}} \|\| Logistic chest: Pushes stored items into the logistic network.<sup>2</sup>		\| {{Imagelink\|Active provider chest}} \|\| Logistic chest: Pushes stored items into the logistic network.<sup>2</sup>

Alfonse: /* Space platforms */ Typo

2025-09-02T00:39:12Z

Space platforms: Typo

← Older revision		Revision as of 00:39, 2 September 2025
Line 160:		Line 160:
	==== Space platforms ====		==== 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 logistic network. They are instead handled by [[rocket silo]]s.		When a space platform is in orbit around a planet, it can send logistic requests to the planet below. These requests are not directly handled by any particular logistic network. They are instead handled by [[rocket silo]]s.

	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 logistic network that the ~~platform~~ resides in. If a platform requests a rocket load of assemblers, and a rocket silo (with at least one rocket at the ready) using this setting is in a logistic network that contains at least the requested amount of assemblers, the rocket silo will act as a [[requester chest]] and request those assemblers. Once logistics robots load the silo, the rocket will launch.		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 logistic network that the silo resides in. If a platform requests a rocket load of assemblers, and a rocket silo (with at least one rocket at the ready) using this setting is in a logistic network that contains at least the requested amount of assemblers, the rocket silo will act as a [[requester chest]] and request those assemblers. Once logistics robots load the silo, the rocket will launch.

	Rocket silos can also be loaded via non-logistic network means. Rocket silos can store cargo loaded via inserters. If the silo has a rocket prepared and has a rocket load of an item in its cargo, and a space platform requests a rocket load of that item, the silo will automatically launch to that platform. Alternatively, the [[circuit network]] can be used to read requests from platforms through the rocket silo. Circuit network conditions and [[combinator]]s can be used to allow inserters to load the silo with requested materials.		Rocket silos can also be loaded via non-logistic network means. Rocket silos can store cargo loaded via inserters. If the silo has a rocket prepared and has a rocket load of a single kind of item is in its cargo, and a space platform requests a rocket load of that item, the silo will automatically launch to that platform. Alternatively, the [[circuit network]] can be used to read requests from platforms through the rocket silo. Circuit network conditions and [[combinator]]s can be used to allow inserters to load the silo with requested materials.

	Note that you cannot load [[processing unit]]s, [[low density structure]]s, or [[rocket fuel]] in this way, as the silo assumes those are meant to make [[rocket part]]s.		Note that you cannot load [[processing unit]]s, [[low density structure]]s, or [[rocket fuel]] in this way, as the silo assumes those are meant to make [[rocket part]]s.

	Individual ~~logistics~~ requests on a space platform have two pieces of extra information associated with them. This extra information can ''only'' be specified when accessing the request from a space platform. So if a named logistics group is shared between a platform and some other kind of entity, if you want to change these settings, you must do so through the platform itself. This information is stored in named logistics groups and blueprints.		Individual logistic requests on a space platform have two pieces of extra information associated with them. This extra information can ''only'' be specified when accessing the request from a space platform. So if a named logistics group is shared between a platform and some other kind of entity, if you want to change these settings, you must do so through the platform itself. This information is stored in named logistics groups and blueprints.

	The first platform-specific information is the target planet. 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.		The first platform-specific information is the target planet. Each individual item requested by space platforms targets a specific planet. This means that requests for an item are only 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.		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.

Alfonse: /* Logistics groups */ Removed redundant section.

2025-08-27T16:16:53Z

Logistics groups: Removed redundant section.

← Older revision		Revision as of 16:16, 27 August 2025
Line 116:		Line 116:
	[[File:player_logistic_gui.png\|thumb\|300px\|right\|The logistic GUI next to the player's inventory. There are two active logistics groups]]		[[File:player_logistic_gui.png\|thumb\|300px\|right\|The logistic GUI next to the player's inventory. There are two active logistics groups]]

	~~=== Logistics groups ===~~
	A set of logistic requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and typing a new name. This will create a new group if no group with that name already exists. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.		A set of logistic requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and typing a new name. This will create a new group if no group with that name already exists. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.

Alfonse: Moved entity list to the request section.

2025-08-26T14:15:57Z

Moved entity list to the request section.

← Older revision		Revision as of 14:15, 26 August 2025
Line 93:		Line 93:
	Logistic: <code>speed = 3.0 × (3.4 + 0.65 × (Level-5))</code>		Logistic: <code>speed = 3.0 × (3.4 + 0.65 × (Level-5))</code>

	== Setting ~~logistics~~ requests ==		== Setting logistic requests ==

	~~Each logistics request contains two pieces of information:~~ the minimum amount ~~desired in~~ the entity~~, and~~ the ~~maximum amount allowed~~ to be ~~stored in that entity~~. ~~The maximum number may be infinity. Logistics robots will deliver more items to~~ the entity ~~if the number~~ of ~~items in the~~ entity~~'s inventory is less than the minimum number~~.		Certain entities can make logistic requests. These are requests to an external system (usually [[logistic robot]]s taking from the current logistic network) to ensure that the entity has at least a given minimum amount of specific items. For requests to a logistic network, the entity must be within the logistic network for the request to be satisfied. If the entity moves out of that range, robots currently carrying cargo bound for that entity will place it back into that network.

	~~Any entity which~~ can ~~use logistics~~ requests has a number of trash slots for items which the logistics requests on that entity say are to be removed. Items beyond the maximum amount for that request will be trashed. Logistics robots will remove such items and take them to other chests in the network.		The following entities can make logistic requests.

	Items which are not named in any ~~logistics~~ request are permitted to be in the entity's inventory. However, most such entities have a checkbox in their request UI to trash any item in its inventory for which no ~~logistics~~ request is made. To force the trashing of certain specific items, a request with a maximum value of 0 may be made.		* The [[player]], once [[Logistic robotics (research)\|logistic robotics]] has been researched
			* [[Tank]], once [[logistic system (research)\|logistic system]] has been researched
			* [[Spidertron]]
			* [[Buffer chest]]
			* [[Requester chest]]
			* [[Space platform]]{{SA}} (requests go to [[rocket silo]]s on the planet being orbited)
			* [[Cargo landing pad]]{{SA}} (requests go to [[space platform]]s in orbit around the planet)

			Each logistic request contains two pieces of information: the minimum amount desired in the entity, and the maximum amount allowed to be stored in that entity. The maximum number may be infinity. Logistic robots will deliver more items to the entity if the number of items in the entity's inventory is less than the minimum number.

			Any entity which can use logistic requests has a number of trash slots for items which the logistic requests on that entity say are to be removed. Items beyond the maximum amount for that request will be trashed. Logistic robots will remove such items and take them to other chests in the network.

			Items which are not named in any logistic request are permitted to be in the entity's inventory. However, most such entities have a checkbox in their logistic request UI to trash any item in its inventory for which no logistic request is made. To force the trashing of certain specific items, a request with a maximum value of 0 may be made.

	== Logistics groups ==		== Logistics groups ==
Line 105:		Line 117:

	=== Logistics groups ===		=== Logistics groups ===
	A set of ~~logistics~~ requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and typing a new name. This will create a new group. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.		A set of logistic requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and typing a new name. This will create a new group if no group with that name already exists. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.

	Logistics groups, named or unnamed, can be enabled separately from one another, and each entity can have multiple groups assigned to it at once.		Logistics groups, named or unnamed, can be enabled separately from one another, and each entity can have multiple groups assigned to it at once.

	~~Named logistics groups~~ are global. This means that if you use the same name for two groups in two different entities, no matter where they are, they are using the same ~~logistics~~ requests. Updates to requests ~~in that group~~ from one entity will be shared among all entities using that named group.		Logistics group names are global. This means that if you use the same name for two groups in two different entities, no matter where they are, they are using the same logistic requests. Updates to requests from one entity will be shared among all entities using that named group.

	~~The following entities can use logistics groups.~~

	* The [[player]]
	* [[Tank]] (once [[logistic system (research)\|logistic system]] is researched)
	* [[Spidertron]]
	* [[Constant combinator]]
	* [[Buffer chest]]
	* [[Requester chest]]
	* [[Space platform]]{{SA}}
	* [[Cargo landing pad]]{{SA}}

	=== Blueprints ===		=== Blueprints ===
Line 130:		Line 131:
	=== Constant combinators ===		=== Constant combinators ===

	[[Constant combinator]]s can use named logistics groups, allowing signals to be sent to a [[circuit network]] that match 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 network]]s 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.		[[Constant combinator]]s can also use named logistics groups, allowing signals to be sent to a [[circuit network]] that match 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 network]]s 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 signal value of an existing signal which has a maximum request value, the maximum value will be unaltered.		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 signal value of an existing signal which has a maximum request value, the maximum value will be unaltered.

Alfonse: /* Mechanics */ Logistics groups are a pretty big topic and need more details. Also added space logistics section.

2025-08-25T23:44:52Z

Mechanics: Logistics groups are a pretty big topic and need more details. Also added space logistics section.

@@ Line 93: / Line 93: @@
 Logistic: <code>speed = 3.0 × (3.4 + 0.65 × (Level-5))</code>
-== Mechanics ==
+== Setting logistics requests ==
 [[File:player_logistic_gui.png|thumb|300px|right|The logistic GUI next to the player's inventory. There are two active logistics groups]]
 === Logistics groups ===
-Logistics requests can be separated into groups. By clicking the button next to "no group" one can select an existing group, or create a new one. Logistics groups are enabled separately from one another, and each entity can have multiple groups assigned to it at once.
+A set of logistics requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and typing a new name. This will create a new group. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.
-The following entities can use logistics groups. Editing a request in one entity will edit the request in all others which use that same group.
+The following entities can use logistics groups.
 * The [[player]]
@@ Line 109: / Line 121: @@
 * [[Space platform]]{{SA}}
 * [[Cargo landing pad]]{{SA}}
 === Negative numbers ===
@@ Line 127: / Line 153: @@
 The delivered number of items in the requester chest can be higher than requested. This depends on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.
 == Priorities of robots ==

← Older revision		Revision as of 15:05, 24 November 2025
Line 17:		Line 17:
	\| {{Imagelink\|Logistic robot}} \|\| Moves items between logistic chests.<sup>1</sup>		\| {{Imagelink\|Logistic robot}} \|\| Moves items between logistic chests.<sup>1</sup>
	\|-		\|-
	\| {{Imagelink\|Construction robot}} \|\| [[Repair pack\|Repairs]] broken or replaces destroyed entities. [[blueprint\|Builds]], [[deconstruction planner\|deconstructs]] and [[upgrade planner\|upgrades]] entities on command. ~~Deliver~~ item requests and ~~execute~~ item removal requests created in remote view.		\| {{Imagelink\|Construction robot}} \|\| [[Repair pack\|Repairs]] broken or replaces destroyed entities. [[blueprint\|Builds]], [[deconstruction planner\|deconstructs]] and [[upgrade planner\|upgrades]] entities on command. Delivers item requests and executes item removal requests created in remote view.
	\|-		\|-
	\| {{Imagelink\|Active provider chest}} \|\| Logistic chest: Pushes stored items into the logistic network.<sup>2</sup>		\| {{Imagelink\|Active provider chest}} \|\| Logistic chest: Pushes stored items into the logistic network.<sup>2</sup>
Line 34:		Line 34:
	\| {{Imagelink\|Rocket silo}} \|\| {{SA}} If "Automatic requests from space platforms" is set, requests items from the logistic network based on requests from space platforms.		\| {{Imagelink\|Rocket silo}} \|\| {{SA}} If "Automatic requests from space platforms" is set, requests items from the logistic network based on requests from space platforms.
	\|-		\|-
	\| {{Imagelink\|Player}} \|\| rowspan="3" \| Can set logistic requests to function as a requester chest.~~<sup>3</sup>~~		\| {{Imagelink\|Player}} \|\| rowspan="2" \| Can set logistic requests to function as a requester chest.
	\|-		\|-
	\| {{Imagelink\|~~Tank~~}}		\| {{Imagelink\|Spidertron}}
	\|-		\|-
	\| {{Imagelink\|~~Spidertron~~}}		\| {{Imagelink\|Tank}} \|\| Can set logistic requests to function as a requester chest after [[Logistic system (research)\|logistic system]] has been researched.
	\|}		\|}

Line 116:		Line 116:

	== Logistics groups ==		== Logistics groups ==
	[[File:player_logistic_gui.png\|thumb\|300px\|right\|The logistic GUI next to the player's inventory. There are two active logistics groups]]		[[File:player_logistic_gui.png\|thumb\|300px\|right\|The logistic GUI next to the player's inventory. There are two active logistics groups.]]

	A set of logistic requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and ~~typing~~ a new name. This will create a new group if no group with that name already exists. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.		A set of logistic requests can be grouped together. Groups with no name are denoted by the name "[No group assigned]". A name can be assigned to a group by pressing the edit button and entering a new name. This will create a new group if no group with that name already exists. To pick an existing group by name, press the edit button and select the desired name from the drop-down list.

	Logistics groups, named or unnamed, can be enabled separately from one another, and each entity can have multiple groups assigned to it at once.		Logistics groups, named or unnamed, can be enabled separately from one another, and each entity can have multiple groups assigned to it at once.

	Logistics group names are global. This means that if ~~you use~~ the same name for two groups in two different entities, no matter where they are, ~~they are using~~ the same logistic requests. Updates to requests from one entity will be shared among all entities using that named group.		Logistics group names are global. This means that if a player uses the same name for two groups in two different entities, no matter where they are, those groups will use the same logistic requests. Updates to requests from one entity will be shared among all entities using that named group.

	=== Blueprints ===		=== Blueprints ===

	If an entity which uses a logistics group is captured in a [[blueprint]], all of the requests in that group will be stored in the blueprint. Pasting the blueprint will ~~put~~ all of those values into the pasted entity.		If an entity which uses a logistics group is captured in a [[blueprint]], all of the requests in that group will be stored in the blueprint. Pasting the blueprint will transfer 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 to match what they were when the blueprint was captured. The entity will simply use the existing named group. This means that, 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 to that group. The new entity will see the updated group.		The above includes named logistics group. However, named groups are global. As such, if a group with that name already exists when the blueprint is pasted, the ''contents'' of that group will not be changed to match what they were when the blueprint was captured. The entity will simply use the existing named group. This means that, if a logistics group's contents have been changed in the world, pasting a new blueprint which uses that group will not undo the changes to that group. The new entity will see and use the updated group.

	=== Constant combinators ===		=== Constant combinators ===
Line 134:		Line 134:
	[[Constant combinator]]s can also use named logistics groups, allowing signals to be sent to a [[circuit network]] that match 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 network]]s 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.		[[Constant combinator]]s can also use named logistics groups, allowing signals to be sent to a [[circuit network]] that match 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 network]]s 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 signal value of an existing signal which has a maximum request value, the maximum value will be unaltered.		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 a new signal for a named logistics group is set through a constant combinator, the maximum value will default to infinity. If the signal value of an existing signal which has a maximum request value is modified, the maximum value will be unaltered.

	== Mechanics ==		== Mechanics ==
Line 164:		Line 164:
	When a space platform is in orbit around a planet, it can send logistic requests to the planet below. These requests are not directly handled by any particular logistic network. They are instead handled by [[rocket silo]]s.		When a space platform is in orbit around a planet, it can send logistic requests to the planet below. These requests are not directly handled by any particular logistic network. They are instead handled by [[rocket silo]]s.

	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 logistic network that the silo resides in. If a platform requests a rocket load of assemblers, and a rocket silo (with at least one rocket at the ready) using this setting is in a logistic network that contains at least the requested amount of assemblers, the rocket silo will act as a [[requester chest]] and request those assemblers. Once logistics robots load the silo, the rocket will launch.		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 logistic network that the silo resides in. If a platform requests a rocket load of assemblers, and a rocket silo (with at least one rocket at the ready) using this setting is in a logistic network that contains at least the requested amount of assemblers, the rocket silo will act as a [[requester chest]] and request those assemblers. Once logistics robots load the silo, the rocket will launch the cargo to the space platform.

	Rocket silos can also be loaded via non-logistic network means. Rocket silos can store cargo loaded via inserters. If the silo has a rocket prepared and has a rocket load of a single kind of item is in its cargo, and a space platform requests a rocket load of that item, the silo will automatically launch to that platform. Alternatively, the [[circuit network]] can be used to read requests from platforms through the rocket silo. Circuit network conditions and [[combinator]]s can be used to allow inserters to load the silo with requested materials.		Rocket silos can also be loaded via non-logistic network means. Rocket silos can store cargo loaded via inserters. If the silo has a rocket prepared and has a rocket load of a single kind of item in its cargo, and a space platform requests a rocket load of that item, the silo will automatically launch to that platform. Alternatively, the [[circuit network]] can be used to read requests from platforms through the rocket silo. Circuit network conditions and [[combinator]]s can be used to allow inserters to load the silo with requested materials.

	Note that ~~you cannot load~~ [[processing unit]]s, [[low density structure]]s, or [[rocket fuel]] in this way, as the silo assumes those are meant to make [[rocket part]]s.		Note that [[processing unit]]s, [[low density structure]]s, or [[rocket fuel]] cannot be loaded in this way, as the silo assumes those are meant to make [[rocket part]]s.

	Individual logistic requests on a space platform have two pieces of extra information associated with them. This extra information can ''only'' be specified when accessing the request from a space platform. So if a named logistics group is shared between a platform and some other kind of entity, if ~~you want to change these~~ settings~~, you~~ must ~~do so~~ through the platform itself. This information is stored in named logistics groups and blueprints.		Individual logistic requests on a space platform have two pieces of extra information associated with them. This extra information can ''only'' be specified when accessing the request from a space platform. So if a named logistics group is shared between a platform and some other kind of entity, if the settings must be changed through the platform itself. This information is stored in named logistics groups and blueprints.

	The first platform-specific information is the target planet. Each individual item requested by space platforms targets a specific planet. This means that requests for an item are only 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.		The first platform-specific information is the target planet. Each individual item requested by space platforms targets a specific planet. This means that requests for an item are only 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.		So if a logistics group is shared between a platform and the destination planet, any new requests will need to be set in the space platform's version of the logistics group.

	The other platform-specific information is the "Custom minimum payload". When this is checked, the player can specify that the space platform can receive less than the full [[rocket capacity]] of the requested item. By default, rockets will only automatically launch when full; this setting is a per-item override to this, allowing rockets to launch with a minimum of the specified amount. By default, this setting is unchecked.		The other platform-specific information is the "Custom minimum payload". When this is checked, the player can specify that the space platform can receive less than the full [[rocket capacity]] of the requested item. By default, rockets will only automatically launch when full; this setting is a per-item override to this, allowing rockets to launch with a minimum of the specified amount. By default, this setting is unchecked.

	Trashing items via requests works like any other entity. Instead of having logistics robots remove trash, they are dropped to a planet whenever the platform is in orbit (and has "unload" checked). Note that this can fill cargo landing pads with ~~unwanted~~ items, possibly filling them up completely.		Trashing items via requests works like any other entity. Instead of having logistics robots remove trash, they are dropped to a planet whenever the platform is in orbit (and has "unload" checked). Note that this can fill cargo landing pads with unrequested items, possibly filling them up completely.

	==== Cargo landing pad ====		==== Cargo landing pad ====
Line 184:		Line 184:
	The [[cargo landing pad]] on a planet can request items from the [[space platform hub]] of any [[space platform]] currently in orbit around that planet which is set to unload items to that planet. Such requests can be set by the [[circuit network]] as well.		The [[cargo landing pad]] on a planet can request items from the [[space platform hub]] of any [[space platform]] currently in orbit around that planet which is set to unload items to that planet. Such requests can be set by the [[circuit network]] as well.

	Cargo landing pad requests can include trashing items beyond the maximum amount in the request. Trashed items are exported to the logistic network the ~~landing pad appears within~~.		Cargo landing pad requests can include trashing items beyond the maximum amount in the request. Trashed items are exported to the landing pad's logistic network on the planet.

	== Priorities of robots ==		== Priorities of robots ==