(Initial description of component, usage and some use case examples) |
m (deployer shenanigans) |
||
| (16 intermediate revisions by 5 users not shown) | |||
| Line 2: | Line 2: | ||
|description = {{PAGENAME}} | |description = {{PAGENAME}} | ||
}} | }} | ||
This internal component can be used to store and place buildings and units. The stored frame will maintain all equipped components and register settings. | |||
The {{IL|Deployer}} is reusable. | |||
{{Recipe cargo|{{PAGENAME}}}} | |||
== | ===== Storing ===== | ||
After equipping a unit with a {{IL|Deployer}}, the GUI will offer a "Acquire" button next to it. Click on it and then click an entity that you want to store. The unit will move into range of the target and start packaging, which takes roughly 6 seconds. | |||
=== | ===== Deploying ===== | ||
When a frame is stored in the {{IL|Deployer}}, it can be unpacked and placed within the world. To do so, use the button "Deploy" next to the Deployer. After clicking you can choose a spot and click it. The unit will move to that spot and place the frame, which takes roughly 6 seconds. | |||
=== | ===== Limitations ===== | ||
* When picking up an entity with a {{IL|Deployer}}, that entity's inventory items will be dropped on the ground | |||
* A {{IL|Deployer}} can't pick up any entity with a {{IL|Deployer}} equipped on it (i.e. no recursion) | |||
* A {{IL|Deployer}} can't pick up any entity that has items in its components (e.g. {{IL|Drone}}s in a {{IL|Drone Port}} or {{IL|Blight Extraction}} in an {{IL|Internal Blight Container}}) | |||
* A {{IL|Deployer}} can't pick up any entity that can't be made into a blueprint (e.g. a {{IL|Re-simulator}}) | |||
== | ==== Common use cases ==== | ||
=== Moving buildings === | ===== Moving buildings ===== | ||
If you want to reorganize your base, you can move buildings using units equipped with Deployers instead of | If you want to reorganize your base, you can move buildings using units equipped with {{IL|Deployer|Deployers}} instead of deconstructing them with a {{IL|Deconstructor}} and rebuilding them. | ||
=== Deploy remote infrastructure === | ===== Deploy remote infrastructure ===== | ||
If you want to start a remote base, such as a mining outpost | If you want to start a remote base, such as a mining outpost, a wind farm on a plateau, you can prepare the necessary buildings in your base. Build a frame, equip the needed components, set a registers and then store it in a {{IL|Deployer}}. | ||
This is faster than hauling individual components and frame ingredients to the site. A {{IL|Scout}} for example, can carry up to 8 {{IL|Deployer|Deployers}} (1 small slot, 3 internal slots + 4 inventory spaces). | |||
===== Deploy a surprise army ===== | |||
You can use a {{IL|Deployer}} to "summon" units to help you in battle or transportation. | |||
{{Category | |||
|race = | |||
|item-type = Components | |||
|material-type = | |||
|entity-type = | |||
|unit-type = | |||
}} | |||
__NOTOC__ | |||
__NOEDITSECTION__ | |||
Latest revision as of 08:57, 8 November 2023
Deployer |
||||
|---|---|---|---|---|
|
||||
Unpacks into a completed unit
|
||||
This internal component can be used to store and place buildings and units. The stored frame will maintain all equipped components and register settings.
The 
Deployer is reusable.
| Circuit Board | Crystal Chunk | Deployer | |
|---|---|---|---|
 1 |
 5 |
 |
|
| Assembler | Time |
|---|---|
 |
6 seconds
|
 |
Advanced Logistics |
Storing
After equipping a unit with a Deployer, the GUI will offer a "Acquire" button next to it. Click on it and then click an entity that you want to store. The unit will move into range of the target and start packaging, which takes roughly 6 seconds.
Deploying
When a frame is stored in the Deployer, it can be unpacked and placed within the world. To do so, use the button "Deploy" next to the Deployer. After clicking you can choose a spot and click it. The unit will move to that spot and place the frame, which takes roughly 6 seconds.
Limitations
- When picking up an entity with a Deployer, that entity's inventory items will be dropped on the ground
- A Deployer can't pick up any entity with a Deployer equipped on it (i.e. no recursion)
- A Deployer can't pick up any entity that has items in its components (e.g.
Drones in a 
Drone Port or 
Blight Extraction in an 
Internal Blight Container) - A Deployer can't pick up any entity that can't be made into a blueprint (e.g. a
Re-simulator)
Common use cases
Moving buildings
If you want to reorganize your base, you can move buildings using units equipped with Deployers instead of deconstructing them with a 
Deconstructor and rebuilding them.
Deploy remote infrastructure
If you want to start a remote base, such as a mining outpost, a wind farm on a plateau, you can prepare the necessary buildings in your base. Build a frame, equip the needed components, set a registers and then store it in a Deployer.
This is faster than hauling individual components and frame ingredients to the site. A 
Scout for example, can carry up to 8 Deployers (1 small slot, 3 internal slots + 4 inventory spaces).
Deploy a surprise army
You can use a Deployer to "summon" units to help you in battle or transportation.
| Mining | |
| Production | |
| Energy | |
| Weaponry | |
| Logic | |
| Utility | |
| Storage | |
| Module | |
