Official Factorio Wiki - User contributions [en]

Map structure

2025-10-28T08:39:43Z

Quchen: /* Chunk */ Clarification: not a 20×20 square around the player is generated, it’s 20 tiles in each direction (effectively a 41×41 square)

{{Languages}}
'''Map structure''' describes the division of the game world into standard [[Units|units]]: tiles and chunks. Tiles are the building blocks of the game, upon which all distance and area measurements are based. Chunks are blocks of 32×32 tiles used for various area-based calculations.

== Tile ==
[[File:MapStructure-GridExample.png|thumb|right|400px|The tile grid shown in-game; chunks (32×32 tiles) are indicated by the thicker black lines. Click to see at higher resolution.]]

A '''tile''' is a square which defines the smallest possible piece of the game world; the map is built on a grid of tiles. The tile is the basis for all area and distance measurement. Entity sizes are defined in terms of tiles; for example the [[rocket silo]] - the largest entity in the game - is 9 tiles wide and 9 tiles high, usually referred to as 9×9. The smallest possible entity size is therefore one tile, 1×1. Examples of 1×1 entities include [[transport belts]] and [[chests]].

The [[Map_generator#Maximum_map_size_and_used_memory|maximum size of the map]] is a square 2 million tiles on each side, a total of 4 trillion tiles. In practice the map in an average game is likely to be in the range of hundreds of thousands of tiles up to a few million at most.

=== Tile grid alignment ===

Almost all placeable entities are aligned to the tile grid when placed in the game. Exceptions include the [[land mine]] and vehicles such as the [[car]], [[tank]], [[locomotive]] and [[wagon]]s. Non-placeable entities that do not align to the grid include [[enemies]], [[tree]]s and decoratives.

[[File:MapStructure-PlaceableOffGridExample.png|thumb|none|300px|A few entities can be placed without aligning to the tile grid; this example shows cars, tanks and landmines.]]

=== Example distances ===

* Area covered by [[Radar]]: about 200 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]).
* It takes about 1 minutes and 52 seconds for a player to run 1000 tiles without being given a speed boost (such as via an [[exoskeleton]]).

=== Real world size analogy ===

One tile is generally assumed to be one square meter in size. This measurement is proven to be technically true, and can be verified in-game. A test conducted via car will reveal that covering 250 tiles at 208.0 km/h (57.777 m/s) will take 260 game ticks (4.333 s). Using this data, it can be proven that <code>57.777 m/s ÷ (250 tiles / 4.333 s) ≈ 1 m/tile</code>.


== Chunk ==

[[File:radar_revealing_sectors.gif|thumb|220px|Animation of radars revealing chunks.]]

The map is divided into a grid of '''chunks''', each 32x32 tiles (1024 tiles total).

Several mechanics work on a chunk-by-chunk basis:
* The map is generated chunk-by-chunk during play. 20 chunks distance in each direction around each player is slowly generated over time, or immediately if revealed directly and not yet generated.
* [[Player|Players]], [[Radar|radars]], [[Roboport|roboports]], [[Spidertron|spidertrons]], and fired [[Artillery|artillery shells]] reveal chunks and provide [[Radar#Coverage|live coverage]] in remote view on a chunk basis.
* [[Pollution]] and [[Spores|spores]]{{SA}} are calculated and spread on a chunk basis. (This can generate chunks without revealing them.)
* [[Enemies#Expansions|Enemy expansion]] is calculated on a chunk basis.
* [[Demolisher]]{{SA}} territories are chunk-aligned.
* Enemy pathfinding works in multiple stages, and the first stage is chunk-based. [https://factorio.com/blog/post/fff-317] An unintended result is enemies tend to walk along chunk borders. Also biters and spitters will sometimes attack obstacles at chunk borders that they would normally navigate around.
* To reduce computation, entire chunks are set inactive when nothing important is happening in them. E.g.: Chunks with only fish or idling enemies may be set inactive, halting their idle movement.

== Visualizing tiles and chunks in-game ==

A tile grid overlay is available which shows the grid upon which the map is built:

* The grid can be shown whenever the player pauses the game (by default with {{Keybinding|shift|space}}).
** This is configured under Settings->Interface->'''Show grid when game is paused'''.
* To see the grid while the game is still running, [[Debug mode|debug settings]] can be used:
** Pressing {{Keybinding|F4}} will show the '''Debug settings''' window.
** Ticking '''show-tile-grid''' under '''always''' will show the grid at all times; ticking it under '''debug''' will show it only when debug mode is activated.
** If '''debug''' is chosen the grid will become visible whenever {{Keybinding|F5}} is used to enable debug display. Configuring debug mode in this way allows {{Keybinding|F5}} to be used as a convenient toggle for turning the grid on and off, which can be useful when attempting to place entities according to a neat and/or symmetrical design.

{{C|Main}}

Infobox:Supercapacitor

2025-10-22T21:56:51Z

Quchen: Add recycling results

{{Infobox
|total-raw = Time, 15 + Battery, 1 + Copper plate, 6 + Electrolyte, 10 + Holmium plate, 2 + Iron plate, 4 + Superconductor, 2
|prototype-type = item
|internal-name = supercapacitor
|category = Intermediate products
|space-age = yes
|stack-size = 100
|rocket-capacity = 500 (5 {{Translation|stacks}})
|recipe = Time, 10 + Battery, 1 + Electrolyte, 10 + Electronic circuit, 4 + Holmium plate, 2 + Superconductor, 2
|producers = Electromagnetic plant
|required-technologies = Electromagnetic plant
|consumers = Personal battery MK3 + Electromagnetic science pack + Portable fusion reactor + Lightning collector + Mech armor + Tesla ammo + Tesla turret
|recycling-results = Battery, 0-1 + Electronic circuit, 1 + Holmium plate, 0-1 + Superconductor, 0-1
}}<noinclude>[[Category:Infobox page]]</noinclude>

Refinery

2024-09-18T09:54:15Z

Quchen: Changed redirect target from Oil Refinery to Oil refinery

#REDIRECT [[Oil refinery]]

Refinery

2024-09-18T09:53:52Z

Quchen: Redirect: Refinery -> Oil Refinery

#REDIRECT [[Oil Refinery]]

Blueprint string format

2024-05-14T09:38:52Z

Quchen: Syntax highlighting

[[File:blueprint_string_preview.png|thumb|340px|right|Preview of a blueprint string.]]This is a technical description of the blueprint string format, used to share blueprints with other users.

A blueprint string is a JSON representation of the blueprint, compressed with zlib deflate using compression level 9 and then encoded using base64 with a version byte in front of the encoded string. The version byte is currently 0 (for all Factorio versions through 1.1).
So to get the JSON representation of a blueprint from a blueprint string, skip the first byte, base64 decode the string, and finally decompress using zlib inflate.

== Json representation of a blueprint/blueprint book ==

The json representation of a blueprint or blueprint book is one large object inside another "wrapping" object, its key inside that object is either blueprint or blueprint-book.

=== Blueprint book object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| item
| String, the name of the item that was saved ("blueprint-book" in vanilla).
| String
|-
| label
| String, the name of the blueprint set by the user.
| String
|-
| label_color
| The color of the label of this blueprint. Optional. [[#Color object]].
| Object
|-
| blueprints
| The actual content of the blueprint book, array of objects containing an "index" key and 0-based value and a "blueprint" key with a [[#Blueprint object]] as the value.
| Array
|-
| active_index
| Index of the currently selected blueprint, 0-based.
| Integer
|-
| icons
| The icons of the blueprint book set by the user, array of [[#Icon object]]s.
| Array
|-
| description
| The description of the blueprint book. Optional.
| String
|-
| version
| The map version of the map the blueprint was created in, see [[Version string format]].
| Integer (long)
|}

=== Blueprint object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| item
| String, the name of the item that was saved ("blueprint" in vanilla).
| String
|-
| label
| String, the name of the blueprint set by the user.
| String
|-
| label_color
| The color of the label of this blueprint. Optional. [[#Color object]].
| Object
|-
| entities
| The actual content of the blueprint, array of [[#Entity object]]s.
| Array
|-
| tiles
| The tiles included in the blueprint, array of [[#Tile object]]s.
| Array
|-
| icons
| The icons of the blueprint set by the user, array of [[#Icon object]]s.
| Array
|-
| schedules
| The schedules for trains in this blueprint, array of [[#Schedule object]]s.
| Array
|-
| description
| The description of the blueprint. Optional.
| String
|-
| snap-to-grid
| The dimensions of the grid to use for snapping. Optional. [[#Position object]].
| Object
|-
| absolute-snapping
| Whether the blueprint uses absolute or relative snapping. Optional.
| Boolean
|-
| position-relative-to-grid
| Offset relative to the global absolute snapping grid. Optional. [[#Position object]].
| Object
|-
| version
| The map version of the map the blueprint was created in.
| Integer (long)
|}

=== Icon object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| index
| Index of the icon, 1-based.
| Integer
|-
| signal
| The icon that is displayed, [[#SignalID object]].
| Object
|}

=== SignalID object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the signal prototype this signal is set to.
| String
|-
| type
| Type of the signal. Either "item", "fluid" or "virtual".
| String
|}

=== Entity object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| entity_number
| Index of the entity, 1-based.
| Integer
|-
| name
| Prototype name of the entity (e.g. "offshore-pump").
| String
|-
| position
| [[#Position object]], position of the entity within the blueprint.
| Object
|-
| direction
| Direction of the entity, uint (optional).
| Integer
|-
| orientation
| Orientation of cargo wagon or locomotive, value 0 to 1 (optional).
| Floating Point
|-
| connections
| Circuit connection, object with keys starting from 1, values are [[#Connection object]]s (optional).
| Object
|-
| neighbours
| Copper wire connections, array of entity_numbers (optional).
| Array
|-
| control_behavior
| [[#Control behavior object]] of this entity (optional).
| Object
|-
| items
| Item requests by this entity, this is what defines the item-request-proxy when the blueprint is placed, optional. [[#Item request object]]
| Object
|-
| recipe
| Name of the recipe prototype this assembling machine is set to, optional, string.
| String
|-
| bar
| Used by [[Prototype/Container]], optional. The index of the first inaccessible item slot due to limiting with the red "bar". 0-based [[Types/ItemStackIndex]].
| Integer
|-
| inventory
| Cargo wagon inventory configuration, optional. [[#Inventory object]]
| Object
|-
| infinity_settings
| Used by [[Prototype/InfinityContainer]], optional. [[#Infinity settings object]]
| Object
|-
| type
| Type of the underground belt or loader, optional. Either "input" or "output".
| String
|-
| input_priority
| Input priority of the splitter, optional. Either "right" or "left", "none" is omitted.
| String
|-
| output_priority
| Output priority of the splitter, optional. Either "right" or "left", "none" is omitted.
| String
|-
| filter
| Filter of the splitter, optional. Name of the item prototype the filter is set to, string.
| String
|-
| filters
| Filters of the filter inserter or loader, optional. Array of [[#Item filter object]]s.
| Array
|-
| filter_mode
| Filter mode of the filter inserter, optional. Either "whitelist" or "blacklist".
| String
|-
| override_stack_size
| The stack size the inserter is set to, optional. [[Types/uint8]].
| Integer
|-
| drop_position
| The drop position the inserter is set to, optional. [[#Position object]].
| Object
|-
| pickup_position
| The pickup position the inserter is set to, optional. [[#Position object]].
| Object
|-
| request_filters
| Used by [[Prototype/LogisticContainer]], optional. [[#Logistic filter object]].
| Array
|-
| request_from_buffers
| Boolean. Whether this requester chest can request from buffer chests.
| Boolean
|-
| parameters
| Used by [[Programmable speaker]], optional. [[#Speaker parameter object]].
| Object
|-
| alert_parameters
| Used by [[Programmable speaker]], optional. [[#Speaker alert parameter object]]
| Object
|-
| auto_launch
| Used by the rocket silo, optional. Boolean, whether auto launch is enabled.
| Boolean
|-
| variation
| Used by [[Prototype/SimpleEntityWithForce]] or [[Prototype/SimpleEntityWithOwner]], optional. [[Types/GraphicsVariation]]
|
|-
| color
| Color of the [[Prototype/SimpleEntityWithForce]], [[Prototype/SimpleEntityWithOwner]], or train station, optional. [[#Color object]].
| Object
|-
| station
| The name of the train station, optional.
| String
|-
| manual_trains_limit
| The manually set train limit of the train station, optional.
| Integer
|-
| switch_state
| The current state of the power switch, optional.
| Boolean
|-
| tags
| Dictionary of arbitrary data, optional. [https://lua-api.factorio.com/latest/concepts.html#Tags Tags].
| Object
|}

=== Inventory object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| filters
| Array of [[#Item filter object]]s.
| Array
|-
| bar
| The index of the first inaccessible item slot due to limiting with the red "bar". 0-based, optional. [[Types/ItemStackIndex]].
| Integer
|}

=== Schedule object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| schedule
| Array of [[#Schedule Record object]]s.
| Array
|-
| locomotives
| Array of entity numbers of locomotives using this schedule.
| Array
|}

=== Schedule Record object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| station
| The name of the stop for this schedule record.
| String
|-
| wait_conditions
| Array of [[#Wait Condition object]]s.
| Array
|}

=== Wait Condition object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| type
| One of "time", "inactivity", "full", "empty", "item_count", "circuit", "robots_inactive", "fluid_count", "passenger_present", "passenger_not_present".
| String
|-
| compare_type
| Either "and", or "or". Tells how this condition is to be compared with the preceding conditions in the corresponding wait_conditions array.
| String
|-
| ticks
| Number of ticks to wait or of inactivity. Only present when type is "time" or "inactivity". Optional.
| uint
|-
| condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition object], only present when type is "item_count", "circuit" or "fluid_count".
| Object
|}

=== Tile object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Prototype name of the tile (e.g. "concrete")
| String
|-
| position
| [[#Position object]], position of the entity within the blueprint.
| Object
|}

=== Position object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| x
| X position within the blueprint, 0 is the center.
| Floating point
|-
| y
| Y position within the blueprint, 0 is the center.
| Floating point
|}

=== Connection object ===
Object containing information about the connections to other entities formed by red or green wires.

{| class="wikitable"
! Key !! Description !! Data type
|-
| 1
| First connection point. The default for everything that doesn't have multiple connection points.[[#Connection point object]]
| Object
|-
| 2
| Second connection point. For example, the "output" part of an arithmetic combinator.[[#Connection point object]]
| Object
|}

=== Connection point object ===
The actual point where a wire is connected to. Contains information about where it is connected to.

{| class="wikitable"
! Key !! Description !! Data type
|-
| red
| An array of [[#Connection data object]] containing all the connections from this point created by red wire.
| Array
|-
| green
| An array of [[#Connection data object]] containing all the connections from this point created by green wire.
| Array
|}

=== Connection data object ===
Information about a single connection between two connection points.

{| class="wikitable"
! Key !! Description !! Data type
|-
| entity_id
| ID of the entity this connection is connected with.
| Integer
|-
| circuit_id
| The circuit connector id of the entity this connection is connected to, see [https://lua-api.factorio.com/latest/defines.html#defines.circuit_connector_id defines.circuit_connector_id].
| Integer
|}

=== Item request object ===
1 or more instances of key/value pairs.
Key is the name of the item, string.
Value is the amount of items to be requested, [[Types/ItemCountType]].

=== Item filter object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype this filter is set to.
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|}

=== Infinity settings object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| remove_unfiltered_items
| Boolean. Whether the "remove unfiltered items" checkbox is checked.
| Boolean
|-
| filters
| Filters of the infinity container, optional. Array of [[#Infinity filter object]]s.
| Array
|}

=== Infinity filter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype the filter is set to, string.
| String
|-
| count
| Number the filter is set to, [[Types/ItemCountType]].
| Integer
|-
| mode
| Mode of the filter. Either "at-least", "at-most", or "exactly".
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|}

=== Logistic filter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype this filter is set to.
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|-
| count
| Number the filter is set to, [[Types/ItemCountType]]. Is 0 for storage chests.
| Integer
|}

=== Speaker parameter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| playback_volume
| [[Types/double]]. Volume of the speaker.
| Floating point
|-
| playback_globally
| Boolean, whether global playback is enabled.
| Boolean
|-
| allow_polyphony
| Boolean, whether polyphony is allowed.
| Boolean
|}

=== Speaker alert parameter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| show_alert
| Boolean, whether an alert is shown.
| Boolean
|-
| show_on_map
| Boolean, whether an alert icon is shown on the map.
| Boolean
|-
| icon_signal_id
| The icon that is displayed with the alert, [[#SignalID object]].
| Object
|-
| alert_message
| String, message of the alert.
| String
|}

=== Color object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| r
| red, number from 0 to 1.
| Floating point
|-
| g
| green, number from 0 to 1.
| Floating point
|-
| b
| blue, number from 0 to 1.
| Floating point
|-
| a
| transparency, number from 0 to 1.
| Floating point
|}

=== Control behavior object ===

'''ALL fields are optional''' and depend on the type of the entity.

{| class="wikitable"
|-
! Key !! Description !! Data type
|-
| logistic_condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition]
| Object
|-
| connect_to_logistic_network
| Whether this entity is connected to the logistic network and enables/disables based on logistic_condition.
| Boolean
|-
| circuit_close_signal
| Whether this rail signal can be closed by circuit_condition.
| Boolean
|-
| circuit_read_signal
| Whether or not to read the state of this rail/chain signal.
| Boolean
|-
| red_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently red.
| Object
|-
| orange_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently orange.
| Object
|-
| green_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently green.
| Object
|-
| blue_output_signal
| [[#SignalID]] to use if the chain signal is currently blue.
| Object
|-
| circuit_condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition]
| Object
|-
| circuit_enable_disable
| Enable or disable based on circuit_condition.
| Boolean
|-
| send_to_train
| Send circuit values to the train to use in schedule conditions.
| Boolean
|-
| read_from_train
| Get the currently stopped trains cargo.
| Boolean
|-
| read_stopped_train
| Get the currently stopped trains ID.
| Boolean
|-
| train_stopped_signal
| [[#SignalID]] to output the train ID on.
| Object
|-
| set_trains_limit
| Whether this stations trains limit will be set through circuit values.
| Boolean
|-
| trains_limit_signal
| [[#SignalID]] to use to set the trains limit.
| Object
|-
| read_trains_count
| Whether to read this stations currently on route trains count.
| Boolean
|-
| trains_count_signal
| [[#SignalID]] to output the on route trains count on.
| Object
|-
| read_logistics
| Whether this roboport should output the contents of its network.
| Boolean
|-
| read_robot_stats
| Whether this roboport should output the robot stats of its network.
| Boolean
|-
| available_logistic_output_signal
| [[#SignalID]] to output available logistic robots on.
| Object
|-
| total_logistic_output_signal
| [[#SignalID]] to output the total count of logistic robots on.
| Object
|-
| available_construction_output_signal
| [[#SignalID]] to output available construction robots on.
| Object
|-
| total_construction_output_signal
| [[#SignalID]] to output the total count of construction robots on.
| Object
|-
| circuit_open_gate
| Whether to limit the gate opening with circuit_condition.
| Boolean
|-
| circuit_read_sensor
| Whether to send the wall-gate proximity sensor to the circuit network.
| Boolean
|-
| output_signal
| [[#SignalID]] to output the wall-gate sensor / accumulator charge on.
| Object
|-
| circuit_read_hand_contents
| Whether to read this belts content or inserters hand.
| Boolean
|-
| circuit_contents_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.transport_belt.content_read_mode defines.control_behavior.transport_belt.content_read_mode]
| Integer
|-
| circuit_mode_of_operation
|
| Integer
|-
| circuit_hand_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.inserter.hand_read_mode defines.control_behavior.inserter.hand_read_mode]
| Integer
|-
| circuit_set_stack_size
| Whether to set the inserters stack size from a circuit signal.
| Boolean
|-
| stack_control_input_signal
| [[#SignalID]] to use to set the inserters stack size.
| Object
|-
| circuit_read_resources
| Whether this miner should output its remaining resource amounts to the circuit network.
| Boolean
|-
| circuit_resource_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.mining_drill.resource_read_mode defines.control_behavior.mining_drill.resource_read_mode]
| Integer
|-
| is_on
| Whether this constant combinator is currently on or off.
| Boolean
|-
| filters
| Array of [https://lua-api.factorio.com/latest/concepts.html#ConstantCombinatorParameters ConstantCombinatorParameters].
| Array
|-
| arithmetic_conditions
| [https://lua-api.factorio.com/latest/concepts.html#ArithmeticCombinatorParameters ArithmeticCombinatorParameters]
| Object
|-
| decider_conditions
| [https://lua-api.factorio.com/latest/concepts.html#DeciderCombinatorParameters DeciderCombinatorParameters]
| Object
|-
| circuit_parameters
| [https://lua-api.factorio.com/latest/concepts.html#ProgrammableSpeakerCircuitParameters ProgrammableSpeakerCircuitParameters]
| Object
|-
| use_colors
| Whether this lamp should use colors or not.
| Boolean
|}

[[Category:Technical]]

== Example code ==

On a typical Bash command line, the blueprint can be decoded like so:

<syntaxhighlight lang="bash">echo "$blueprint_string" | cut -c2- | base64 -d | pigz -d</syntaxhighlight>

Blueprint string format

2024-05-14T09:38:20Z

Quchen: Add decode one-liner for Bash

[[File:blueprint_string_preview.png|thumb|340px|right|Preview of a blueprint string.]]This is a technical description of the blueprint string format, used to share blueprints with other users.

A blueprint string is a JSON representation of the blueprint, compressed with zlib deflate using compression level 9 and then encoded using base64 with a version byte in front of the encoded string. The version byte is currently 0 (for all Factorio versions through 1.1).
So to get the JSON representation of a blueprint from a blueprint string, skip the first byte, base64 decode the string, and finally decompress using zlib inflate.

== Json representation of a blueprint/blueprint book ==

The json representation of a blueprint or blueprint book is one large object inside another "wrapping" object, its key inside that object is either blueprint or blueprint-book.

=== Blueprint book object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| item
| String, the name of the item that was saved ("blueprint-book" in vanilla).
| String
|-
| label
| String, the name of the blueprint set by the user.
| String
|-
| label_color
| The color of the label of this blueprint. Optional. [[#Color object]].
| Object
|-
| blueprints
| The actual content of the blueprint book, array of objects containing an "index" key and 0-based value and a "blueprint" key with a [[#Blueprint object]] as the value.
| Array
|-
| active_index
| Index of the currently selected blueprint, 0-based.
| Integer
|-
| icons
| The icons of the blueprint book set by the user, array of [[#Icon object]]s.
| Array
|-
| description
| The description of the blueprint book. Optional.
| String
|-
| version
| The map version of the map the blueprint was created in, see [[Version string format]].
| Integer (long)
|}

=== Blueprint object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| item
| String, the name of the item that was saved ("blueprint" in vanilla).
| String
|-
| label
| String, the name of the blueprint set by the user.
| String
|-
| label_color
| The color of the label of this blueprint. Optional. [[#Color object]].
| Object
|-
| entities
| The actual content of the blueprint, array of [[#Entity object]]s.
| Array
|-
| tiles
| The tiles included in the blueprint, array of [[#Tile object]]s.
| Array
|-
| icons
| The icons of the blueprint set by the user, array of [[#Icon object]]s.
| Array
|-
| schedules
| The schedules for trains in this blueprint, array of [[#Schedule object]]s.
| Array
|-
| description
| The description of the blueprint. Optional.
| String
|-
| snap-to-grid
| The dimensions of the grid to use for snapping. Optional. [[#Position object]].
| Object
|-
| absolute-snapping
| Whether the blueprint uses absolute or relative snapping. Optional.
| Boolean
|-
| position-relative-to-grid
| Offset relative to the global absolute snapping grid. Optional. [[#Position object]].
| Object
|-
| version
| The map version of the map the blueprint was created in.
| Integer (long)
|}

=== Icon object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| index
| Index of the icon, 1-based.
| Integer
|-
| signal
| The icon that is displayed, [[#SignalID object]].
| Object
|}

=== SignalID object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the signal prototype this signal is set to.
| String
|-
| type
| Type of the signal. Either "item", "fluid" or "virtual".
| String
|}

=== Entity object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| entity_number
| Index of the entity, 1-based.
| Integer
|-
| name
| Prototype name of the entity (e.g. "offshore-pump").
| String
|-
| position
| [[#Position object]], position of the entity within the blueprint.
| Object
|-
| direction
| Direction of the entity, uint (optional).
| Integer
|-
| orientation
| Orientation of cargo wagon or locomotive, value 0 to 1 (optional).
| Floating Point
|-
| connections
| Circuit connection, object with keys starting from 1, values are [[#Connection object]]s (optional).
| Object
|-
| neighbours
| Copper wire connections, array of entity_numbers (optional).
| Array
|-
| control_behavior
| [[#Control behavior object]] of this entity (optional).
| Object
|-
| items
| Item requests by this entity, this is what defines the item-request-proxy when the blueprint is placed, optional. [[#Item request object]]
| Object
|-
| recipe
| Name of the recipe prototype this assembling machine is set to, optional, string.
| String
|-
| bar
| Used by [[Prototype/Container]], optional. The index of the first inaccessible item slot due to limiting with the red "bar". 0-based [[Types/ItemStackIndex]].
| Integer
|-
| inventory
| Cargo wagon inventory configuration, optional. [[#Inventory object]]
| Object
|-
| infinity_settings
| Used by [[Prototype/InfinityContainer]], optional. [[#Infinity settings object]]
| Object
|-
| type
| Type of the underground belt or loader, optional. Either "input" or "output".
| String
|-
| input_priority
| Input priority of the splitter, optional. Either "right" or "left", "none" is omitted.
| String
|-
| output_priority
| Output priority of the splitter, optional. Either "right" or "left", "none" is omitted.
| String
|-
| filter
| Filter of the splitter, optional. Name of the item prototype the filter is set to, string.
| String
|-
| filters
| Filters of the filter inserter or loader, optional. Array of [[#Item filter object]]s.
| Array
|-
| filter_mode
| Filter mode of the filter inserter, optional. Either "whitelist" or "blacklist".
| String
|-
| override_stack_size
| The stack size the inserter is set to, optional. [[Types/uint8]].
| Integer
|-
| drop_position
| The drop position the inserter is set to, optional. [[#Position object]].
| Object
|-
| pickup_position
| The pickup position the inserter is set to, optional. [[#Position object]].
| Object
|-
| request_filters
| Used by [[Prototype/LogisticContainer]], optional. [[#Logistic filter object]].
| Array
|-
| request_from_buffers
| Boolean. Whether this requester chest can request from buffer chests.
| Boolean
|-
| parameters
| Used by [[Programmable speaker]], optional. [[#Speaker parameter object]].
| Object
|-
| alert_parameters
| Used by [[Programmable speaker]], optional. [[#Speaker alert parameter object]]
| Object
|-
| auto_launch
| Used by the rocket silo, optional. Boolean, whether auto launch is enabled.
| Boolean
|-
| variation
| Used by [[Prototype/SimpleEntityWithForce]] or [[Prototype/SimpleEntityWithOwner]], optional. [[Types/GraphicsVariation]]
|
|-
| color
| Color of the [[Prototype/SimpleEntityWithForce]], [[Prototype/SimpleEntityWithOwner]], or train station, optional. [[#Color object]].
| Object
|-
| station
| The name of the train station, optional.
| String
|-
| manual_trains_limit
| The manually set train limit of the train station, optional.
| Integer
|-
| switch_state
| The current state of the power switch, optional.
| Boolean
|-
| tags
| Dictionary of arbitrary data, optional. [https://lua-api.factorio.com/latest/concepts.html#Tags Tags].
| Object
|}

=== Inventory object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| filters
| Array of [[#Item filter object]]s.
| Array
|-
| bar
| The index of the first inaccessible item slot due to limiting with the red "bar". 0-based, optional. [[Types/ItemStackIndex]].
| Integer
|}

=== Schedule object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| schedule
| Array of [[#Schedule Record object]]s.
| Array
|-
| locomotives
| Array of entity numbers of locomotives using this schedule.
| Array
|}

=== Schedule Record object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| station
| The name of the stop for this schedule record.
| String
|-
| wait_conditions
| Array of [[#Wait Condition object]]s.
| Array
|}

=== Wait Condition object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| type
| One of "time", "inactivity", "full", "empty", "item_count", "circuit", "robots_inactive", "fluid_count", "passenger_present", "passenger_not_present".
| String
|-
| compare_type
| Either "and", or "or". Tells how this condition is to be compared with the preceding conditions in the corresponding wait_conditions array.
| String
|-
| ticks
| Number of ticks to wait or of inactivity. Only present when type is "time" or "inactivity". Optional.
| uint
|-
| condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition object], only present when type is "item_count", "circuit" or "fluid_count".
| Object
|}

=== Tile object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Prototype name of the tile (e.g. "concrete")
| String
|-
| position
| [[#Position object]], position of the entity within the blueprint.
| Object
|}

=== Position object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| x
| X position within the blueprint, 0 is the center.
| Floating point
|-
| y
| Y position within the blueprint, 0 is the center.
| Floating point
|}

=== Connection object ===
Object containing information about the connections to other entities formed by red or green wires.

{| class="wikitable"
! Key !! Description !! Data type
|-
| 1
| First connection point. The default for everything that doesn't have multiple connection points.[[#Connection point object]]
| Object
|-
| 2
| Second connection point. For example, the "output" part of an arithmetic combinator.[[#Connection point object]]
| Object
|}

=== Connection point object ===
The actual point where a wire is connected to. Contains information about where it is connected to.

{| class="wikitable"
! Key !! Description !! Data type
|-
| red
| An array of [[#Connection data object]] containing all the connections from this point created by red wire.
| Array
|-
| green
| An array of [[#Connection data object]] containing all the connections from this point created by green wire.
| Array
|}

=== Connection data object ===
Information about a single connection between two connection points.

{| class="wikitable"
! Key !! Description !! Data type
|-
| entity_id
| ID of the entity this connection is connected with.
| Integer
|-
| circuit_id
| The circuit connector id of the entity this connection is connected to, see [https://lua-api.factorio.com/latest/defines.html#defines.circuit_connector_id defines.circuit_connector_id].
| Integer
|}

=== Item request object ===
1 or more instances of key/value pairs.
Key is the name of the item, string.
Value is the amount of items to be requested, [[Types/ItemCountType]].

=== Item filter object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype this filter is set to.
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|}

=== Infinity settings object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| remove_unfiltered_items
| Boolean. Whether the "remove unfiltered items" checkbox is checked.
| Boolean
|-
| filters
| Filters of the infinity container, optional. Array of [[#Infinity filter object]]s.
| Array
|}

=== Infinity filter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype the filter is set to, string.
| String
|-
| count
| Number the filter is set to, [[Types/ItemCountType]].
| Integer
|-
| mode
| Mode of the filter. Either "at-least", "at-most", or "exactly".
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|}

=== Logistic filter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype this filter is set to.
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|-
| count
| Number the filter is set to, [[Types/ItemCountType]]. Is 0 for storage chests.
| Integer
|}

=== Speaker parameter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| playback_volume
| [[Types/double]]. Volume of the speaker.
| Floating point
|-
| playback_globally
| Boolean, whether global playback is enabled.
| Boolean
|-
| allow_polyphony
| Boolean, whether polyphony is allowed.
| Boolean
|}

=== Speaker alert parameter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| show_alert
| Boolean, whether an alert is shown.
| Boolean
|-
| show_on_map
| Boolean, whether an alert icon is shown on the map.
| Boolean
|-
| icon_signal_id
| The icon that is displayed with the alert, [[#SignalID object]].
| Object
|-
| alert_message
| String, message of the alert.
| String
|}

=== Color object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| r
| red, number from 0 to 1.
| Floating point
|-
| g
| green, number from 0 to 1.
| Floating point
|-
| b
| blue, number from 0 to 1.
| Floating point
|-
| a
| transparency, number from 0 to 1.
| Floating point
|}

=== Control behavior object ===

'''ALL fields are optional''' and depend on the type of the entity.

{| class="wikitable"
|-
! Key !! Description !! Data type
|-
| logistic_condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition]
| Object
|-
| connect_to_logistic_network
| Whether this entity is connected to the logistic network and enables/disables based on logistic_condition.
| Boolean
|-
| circuit_close_signal
| Whether this rail signal can be closed by circuit_condition.
| Boolean
|-
| circuit_read_signal
| Whether or not to read the state of this rail/chain signal.
| Boolean
|-
| red_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently red.
| Object
|-
| orange_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently orange.
| Object
|-
| green_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently green.
| Object
|-
| blue_output_signal
| [[#SignalID]] to use if the chain signal is currently blue.
| Object
|-
| circuit_condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition]
| Object
|-
| circuit_enable_disable
| Enable or disable based on circuit_condition.
| Boolean
|-
| send_to_train
| Send circuit values to the train to use in schedule conditions.
| Boolean
|-
| read_from_train
| Get the currently stopped trains cargo.
| Boolean
|-
| read_stopped_train
| Get the currently stopped trains ID.
| Boolean
|-
| train_stopped_signal
| [[#SignalID]] to output the train ID on.
| Object
|-
| set_trains_limit
| Whether this stations trains limit will be set through circuit values.
| Boolean
|-
| trains_limit_signal
| [[#SignalID]] to use to set the trains limit.
| Object
|-
| read_trains_count
| Whether to read this stations currently on route trains count.
| Boolean
|-
| trains_count_signal
| [[#SignalID]] to output the on route trains count on.
| Object
|-
| read_logistics
| Whether this roboport should output the contents of its network.
| Boolean
|-
| read_robot_stats
| Whether this roboport should output the robot stats of its network.
| Boolean
|-
| available_logistic_output_signal
| [[#SignalID]] to output available logistic robots on.
| Object
|-
| total_logistic_output_signal
| [[#SignalID]] to output the total count of logistic robots on.
| Object
|-
| available_construction_output_signal
| [[#SignalID]] to output available construction robots on.
| Object
|-
| total_construction_output_signal
| [[#SignalID]] to output the total count of construction robots on.
| Object
|-
| circuit_open_gate
| Whether to limit the gate opening with circuit_condition.
| Boolean
|-
| circuit_read_sensor
| Whether to send the wall-gate proximity sensor to the circuit network.
| Boolean
|-
| output_signal
| [[#SignalID]] to output the wall-gate sensor / accumulator charge on.
| Object
|-
| circuit_read_hand_contents
| Whether to read this belts content or inserters hand.
| Boolean
|-
| circuit_contents_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.transport_belt.content_read_mode defines.control_behavior.transport_belt.content_read_mode]
| Integer
|-
| circuit_mode_of_operation
|
| Integer
|-
| circuit_hand_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.inserter.hand_read_mode defines.control_behavior.inserter.hand_read_mode]
| Integer
|-
| circuit_set_stack_size
| Whether to set the inserters stack size from a circuit signal.
| Boolean
|-
| stack_control_input_signal
| [[#SignalID]] to use to set the inserters stack size.
| Object
|-
| circuit_read_resources
| Whether this miner should output its remaining resource amounts to the circuit network.
| Boolean
|-
| circuit_resource_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.mining_drill.resource_read_mode defines.control_behavior.mining_drill.resource_read_mode]
| Integer
|-
| is_on
| Whether this constant combinator is currently on or off.
| Boolean
|-
| filters
| Array of [https://lua-api.factorio.com/latest/concepts.html#ConstantCombinatorParameters ConstantCombinatorParameters].
| Array
|-
| arithmetic_conditions
| [https://lua-api.factorio.com/latest/concepts.html#ArithmeticCombinatorParameters ArithmeticCombinatorParameters]
| Object
|-
| decider_conditions
| [https://lua-api.factorio.com/latest/concepts.html#DeciderCombinatorParameters DeciderCombinatorParameters]
| Object
|-
| circuit_parameters
| [https://lua-api.factorio.com/latest/concepts.html#ProgrammableSpeakerCircuitParameters ProgrammableSpeakerCircuitParameters]
| Object
|-
| use_colors
| Whether this lamp should use colors or not.
| Boolean
|}

[[Category:Technical]]

== Example code ==

On a typical Bash command line, the blueprint can be decoded like so:

<syntaxhighlight>echo "$blueprint_string" | cut -c2- | base64 -d | pigz -d</syntaxhighlight>

Upcoming features

2024-05-05T19:25:12Z

Quchen: Add a couple of FFF links: Fulgora, Vulcanus, and the new buildings

{{Languages}}
This is a list of known information about the upcoming expansion pack '''Factorio: Space Age''' and the upcoming 2.0 version.

* As of August 2023, development is at the end of step 5 "First pass of tweaking" out of 7 total steps until release. [https://factorio.com/blog/post/fff-373]
* The planned price is $30.00 because it is "as big an addition as the whole vanilla game.". [https://factorio.com/blog/post/fff-367]
* The expected release date is around August 2024 [https://factorio.com/blog/post/fff-373], with it being October 2024 at the latest [https://www.reddit.com/r/factorio/comments/1c4qov8/main_points_from_new_interview_with_kovarex/]

== Space Age expansion ==
[https://factorio.com/blog/post/fff-367 Friday Facts #367] shows some concept art for the expansion. [https://factorio.com/blog/post/fff-372 Friday Facts #372] shows some item icons from the expansion.

"Factorio: Space Age continues the player's journey after launching rockets into space. Discover new worlds with unique challenges, exploit their novel resources for advanced technological gains, and manage your fleet of interplanetary space platforms." [https://factorio.com/blog/post/fff-373]

Consists of 3 major mods which can be enabled and disabled at will: Space Age, Quality, and Elevated Rails.

=== Space Age ===

Relevant FFFs: [https://www.factorio.com/blog/post/fff-373 FFF 373 - Factorio: Space Age], [https://www.factorio.com/blog/post/fff-381 FFF 381 - Space Platforms], [https://www.factorio.com/blog/post/fff-386 FFF 386 - Vulcanus], [https://www.factorio.com/blog/post/fff-387 FFF 387 - Swimming in lava], [https://factorio.com/blog/post/fff-398 FFF 398 - Fulgora], [https://factorio.com/blog/post/fff-399 FFF 399 - Trash to Treasure]

* Space Age features 4 new planets (Vulcanus and Fulgora are the only ones to have been officially revealed, the others are thought to be named Bacchus and Aquilo) with their own "unique theme, resource, challenges, and gameplay mechanics", as well as new enemies to deal with.

* [[Rocket silo | Rockets]] will be significantly cheaper. [[Chemical science pack | Chemical science]] unlocks rocket silo and access to space. [[Space science pack | Space science]] unlocks access to other planets. Some technologies have been moved to one of these planets; artillery, cliff explosives, spidertron, tier 3 modules, and some personal equipment are in this list.

* Playthroughs of Space Age are expected to take approximately 60-100 hours, compared to 150-500+ hours for Space Exploration.

'''New Music:'''

* The expansion will come with five hours of new music, some of it recorded using a live orchestra. [https://www.factorio.com/blog/post/fff-406] There will be around one hour of new music for each new surface (space, plus the four new planets).

* It will also feature a new "variable music tracks" system [https://www.factorio.com/blog/post/fff-407], which seeks to "provide some variety in the music after tens or hundreds of hours spent in game". But, the developers note: "regular music is still the main focus and large majority of the soundtrack".

* The Space Age soundtrack will be available as a separate digital purchase. [https://factorio.com/blog/post/fff-407]

'''New Buildings:'''

* Crusher, assembler-like building for breaking down asteroids [https://www.factorio.com/blog/post/fff-381]
* Asteroid Collector, sends out tentacle-like grabbers to collect asteroids [https://www.factorio.com/blog/post/fff-381]
* Space Platform Hub, central unit for space platforms
* Foundry, processes molten materials [https://factorio.com/blog/post/fff-387]
* Electromagnetic Plant, builds electricity-based items [https://factorio.com/blog/post/fff-399]
* Big mining drill, upgraded electric mining drill [https://factorio.com/blog/post/fff-387]

'''Space Platforms:'''

* Space platforms are player-created surfaces that function both as factories and as transport to other planets.

* Platforms are created by launching a "starter pack" on a rocket, which creates the surface with a hub on it with a small amount of flooring. More flooring can be placed, but can't contain any holes. The entire platform is lost if the hub is destroyed.

* The hub counts as a construction and logistics handler (as the player is confined to the hub) as well as a train-like entity (for moving between planets).

* Rocket silos now act as a requester chest and can request all items needed by a connected hub in orbit, including ghost entities. Silos can also be manually filled.

* A number of buildings can't be built on platforms, including construction and logistics robots, chests, vehicles, and burner entities.

* Storage within the hub can be expanded with cargo bays, which is important as you can't place chests on platforms. Cargo bays can also attach to other cargo bays.

* Platforms act as a power transmitter, removing the need for power poles entirely.

* Asteroids appear around space platforms and act as a renewable way to obtain iron, ice, and carbon. All three are required to produce fuel and oxidiser to move between planets. Moving causes larger, hazardous asteroids to appear that can be shot down into the smaller, collectible form. All asteroid types are collected and then crushed.
** Metallic asteroids are crushed into iron ore
** Carbonic asteroids are crushed into carbon
** Oxide asteroids are crushed into ice, which can be melted into water

* Excess items can be dumped by "inserting" them into a space with no flooring.

* All three asteroid types are also required to produce space science efficiently, as the satellite method now only produces 10 science packs, as well as needing some enriched uranium. Enrichment was moved to space science to compensate for enriched uranium being a required resource. Tier 2 modules were also moved to space science.

'''Vulcanus:'''

Relevant FFFs: [https://factorio.com/blog/post/fff-386 386 - Vulcanus], [https://factorio.com/blog/post/fff-387 387 - Swimming in lava]

* Vulcanus is a new volcanic planet. Its surface is divided between three distinct biomes: mountains, ashlands and lava basins.

* Mountains are large volcanoes, covered in cliffs and with a large lava pool at their center. They are home to sulfuric acid vents where sulfuric acid can be directly obtained, and a new material, calcite, which is used as a cleansing agent in recipes.

* Ashlands are plateaus speckled with sparse vegetation and deposits of coal. They are home to leafless alien trees, presumably a source of wood. They are relatively free of cliffs and lava, making them ideal for building.

* Lava basins are filled with winding lava rivers. Within them are deposits of a new material, tungsten, which can only be mined using the new big mining drill.

* The foundry, a new building for crafting with molten materials, can be researched here. It is used to process lava and calcite into molten iron and molten copper, with a byproduct of stone. It can also be used to melt iron and copper and cast molten metals into items such as iron gear wheels, copper wire, steel, and low density structures more quickly than other methods.

* Lava can be used to destroy items by placing items over it with an inserter.

* Big mining drills have a range of 13x13 tiles, harvest materials at 2.5/s, have 4 module slots, and have a 50% chance not to reduce resource richness, which can be further decreased at higher qualities.

* Sulfuric acid and calcite can be obtained to create water, which is the only local source of water on the planet.

* Coal liquefaction is now only obtainable on Vulcanus. A simplified liquefaction process is also available, wherein coal can be processed into oil without the need for heavy oil.

* Tungsten is used in a foundry to create the Metallurgic science pack.

'''Fulgora:'''

Relevant FFFs: [https://factorio.com/blog/post/fff-398 398 - Fulgora], [https://factorio.com/blog/post/fff-399 399 - Trash to Treasure]

* Fulgora is a new barren desert planet. Its surface is split between island-like plateaus, and deep oilsands.

* Oilsands can be walked through, but only elevated rail supports and offshore pumps can be built in them. Offshore pumps will produce an unlimited supply of Heavy Oil.

* Factory buildings can only be built on plateaus. The only way to bridge the gaps will be with elevated rails, but you will be able to landfill the oilsands in the late game.

* Fulgora is prone to lightning storms at night. Lightning will damage buildings not protected by the new lightning rods.

* Lightning rods will also take energy from lightning and turn it into electricity for the power network. A bank of accumulators is needed to store it through the daytime.

* The plateaus are far enough apart for power poles, so each island will need its own electric network.

* The Electromagnetic Plant, Fulgora's equivalent to the Foundry, is found here. It is used for crafting electrical-based items such as lightning rods, supercapacitors, and modules. It has an inherent productivity bonus of 50%, which, unlike modules, is not restricted to just intermediate items.

* The main resource on Fulgora is Scrap, which can be processed in the Recycler to create 12 different basic and intermediate products.

* These products include the new Holmium Ore, which can be used to create the Electromagnetic Science Pack.

=== Quality ===
Relevant FFFs: [https://www.factorio.com/blog/post/fff-375 FFF 375 - Quality], [https://www.factorio.com/blog/post/fff-376 FFF 376 - Research and Technology]

* Quality offers "vertical" growth for factories and influences a variety of building and item stats.

* Quality tiers are Normal (0), Uncommon (1), Rare (2), Epic (3), and Legendary (5). Note that legendary quality has a doubled level increase to 5 instead of 4.

* Known effects per level increase:
** +30% health
** +30% energy output
** +30% crafting speed
** +10% turret range
** +30% robot limit (rounded down)
** +30% robot recharge rate (both number and speed, rounded down)
** +1 tile reach for power poles
** +30% positive module effects
** +1 equipment grid size (both dimensions)
** Larger inventory (unknown boost size)
** Increased ammo damage (30%?)
** Faster inserters
** Reduced resource depletion on miners
** Larger capacity on accumulators
** Increased output rate on nuclear reactors, boilers, and steam engines/turbines
** Increased transmission power and decreased power consumption of beacons
** Larger scan range on radars
** +100% durability on consumable items (repair packs, science packs)

* Quality items above Normal are created via quality modules. Quality modules have a strength of 10%/15%/25% in line with the 2/3/5 system other modules use, as well as a speed penalty.

* When crafting an item, each step up applies a 10% (moddable per quality) multiplier to the quality strength to the chance of receiving at least that quality. With four tier 3 quality modules providing a 100% quality strength, this results in 10% odds of at least +1 quality, 1% of at least +2, and so on. The base quality of a craft is the lowest input quality, ignoring fluids; it's impossible to get a Normal iron gear from two Uncommon iron plates.

* Quality modules can be used on any recipe, unlike productivity modules which can only be used on intermediates. Quality is also random, whereas productivity is a cumulative effect.

* New building: [[Recycler]], gives a 25% chance of returning items created from recipes.

* There is a new achievement for having best legendary armor full of legendary equipment [https://www.factorio.com/blog/post/fff-375] .

=== Elevated Rails ===
Relevant FFF: [https://www.factorio.com/blog/post/fff-378 FFF 378 - Trains on another level]

New buildings:

* Rail ramp, to change layers
* Rail support, to support elevated rails

Elevated rails offer a second layer of rail planning, including curved rails and signals. Elevated rails require periodic supports which can be placed on water.

== Known free changes for 2.0 ==

* [[Crafting#Recipe_difficulties|Expensive mode]] gets turned into a mod. [https://forums.factorio.com/viewtopic.php?p=577191#p577191]
* Better [[Blueprint]] building. [https://www.factorio.com/blog/post/fff-380], [https://www.factorio.com/blog/post/fff-403], [https://www.factorio.com/blog/post/fff-404]
** "Super Force Building": Will place [[Landfill]] underneath blueprints when building on water, or delete any other buildings in the way. Underground belts will be placed automatically, if possible.
** Quick adjustment of [[Blueprint]] grid offsets: SHIFT + Arrow keys adjusts the Grid position, CONTROL + Arrow keys adjusts the Absolute grid offset
** [[Rail planner]] now works in map mode (and works especially well with the new "Super-force building" feature).
* Improvements to control of [[train]] systems. [https://factorio.com/blog/post/fff-377],[https://factorio.com/blog/post/fff-389], [https://factorio.com/blog/post/fff-395], [https://www.factorio.com/blog/post/fff-403]
** Any Item: A new wildcard signal that will replace itself with the first item in the train, allowing for generic trains
** Disabling: Disabled stations will now act as if their Station Limit=0.
*** A train en route to a station that is disabled will now continue to the station regardless, instead of skipping it and re-pathing.
*** A train told to go to a disabled station will enter the "destination full" state and wait until it is enabled again.
** Locomotive Colours: Locomotives can update their colour based on the destination station's colour.
** Manual Push: Push trains with your feet. Very slow.
** New Rails: [[Rail]]s have a new texture. The geometry behind rail curves has been redone, allowing for 2 and 4-tile S-bends.
** Reservations: Trains will give up their reservation in a station when they leave the block the station is in, opposed to immediately.
** Remote Control: It's now possible to remote drive trains, which is convenient for controlling a Train on another surface without travelling to it
** Station Interrupts: Trains can be directed to a different station when a condition is met, such as when [[Fuel]] is low.
** Station Priority: A new slider on Station GUI. Stations have a priority of 0 to 255, with a default of 50.
*** When deciding between multiple destinations, trains will prefer stations with a higher priority.
*** Trains at stations with higher priority will be dispatched first.
** Train Groups: Trains can be assigned a group, and have their schedules changed en masse.
** [[Train stop]] GUI Improvements:
*** The GUI now has a 'Trains on the way' tab.
*** When you set the name of a stop, it will copy the limit and colour from an existing stop with that name.
*** A station's name is now shown when hovered over on the map.
*** Train stop now shows path of incoming trains.
*** Ability to copy-paste Train stops from the map.
*** Mass stop rename: holding CTRL when confirming a change will rename all stops with that name to the new name.
*** When you set the name of a stop, it will copy the limit and colour from an existing stop with that name.
* Factoriopedia: A new GUI which shows every item in the game, how they are crafted, what recipes they're used in, and what technologies unlock them. Can also be built upon for Expansion and Modded content. [https://factorio.com/blog/post/fff-397]
* [[Circuit network]] Changes [https://factorio.com/blog/post/fff-384], [https://factorio.com/blog/post/fff-388], [https://factorio.com/blog/post/fff-394], [https://factorio.com/blog/post/fff-402], [https://factorio.com/blog/post/fff-405]
** [[Assembling machine]]s can now be connected to the circuit network. Functions include setting recipes via signal, reading active ingredients, and outputting a signal when a recipe is finished.
** [[Lamp]] can now use colours without the need for a circuit connection.
** The UI for [[Arithmetic combinator]]s and [[Decider combinator]]s are redone. [[Decider combinator]]s can now handle multiple conditions at once.
** Connecting to the [[Belt transport system]] has the option to read the contents of all belts in the same 'transport line', survives going through underground belts; also has "less visual clutter"
** Wireless circuit transmission using [[Radar]] with a single radar channel for each surface.
** Heavily reworked [[Logistic network]] GUI, with remote view panel and table of inventory icons.
** [[Pump]] now has a filter, which can be set with signals.
** When using the cut tool, the game remembers outside circuit wire connections, tries to reconnect if possible. This cannot be transferred to a blueprint export string.
* Small changes [https://factorio.com/blog/post/fff-388]
** Logistic Requests are re-enabled upon retrieving one's corpse.
** Mathematical expressions can be typed in text fields, such as 4k, 4*5k, etc.
** Save games can now be sorted by last time modified.
* [[Filter inserter]] and [[Stack filter inserter]] will be removed. All remaining inserters will have the ability to filter 5 items. [https://factorio.com/blog/post/fff-393]
* [[Stack inserter]]s will be renamed to "Bulk Inserter". This will be due to a new inserter in the paid Expansion with the ability to stack items on belts, which will take the more appropriate name of Stack Inserter. [https://factorio.com/blog/post/fff-394].
* [[Ghost]] [[Pipe|pipes]] will visually connect to each other. [https://forums.factorio.com/viewtopic.php?p=578549#p578549]
* Improved [[Robots | flying robot]] behaviour. [https://www.factorio.com/blog/post/fff-374]
* Mods can create more than 255 tiles. [https://forums.factorio.com/viewtopic.php?p=589483#p589483]
* An overhaul to the sound engine, allowing for more dynamic and layered sounds. [https://factorio.com/blog/post/fff-396]
* Improved world generation of Nauvis, the starting planet. [https://factorio.com/blog/post/fff-401]
* [[Crafting]] now loops if it needs to run faster than 1 craft per tick [https://www.factorio.com/blog/post/fff-402]
* The [[Spidertron remote]] is renamed to the "RTS Tool", which can group Spidertrons, and remembers the last selection of Spidertrons per-surface [https://www.factorio.com/blog/post/fff-404]
* The Pipette tool now works in more places: recipe slots, logistic slots, inventory slots; placeable tiles like concrete, landfill, platform foundation, etc.; Water, Lava, Oil Ocean (to get offshore pump) [https://www.factorio.com/blog/post/fff-404]
* [[Rocket silo]] changes [https://www.factorio.com/blog/post/fff-405] [https://discord.com/channels/139677590393716737/603392474458882065/1179442159628341318]
** Faster subsequent launches: the Silo can craft and buffer an extra rocket inside. These buffered rockets will be launched without the silo going through its normal animation of closing and reopening its doors.
** [[Rocket control unit]]s are removed. [[Rocket part]] now takes [[Processing unit]] instead.
* [[Production statistics]] and [[Electric system]] Changes [https://factorio.com/blog/post/fff-408]
** The Electric Network Info Screen now has a third graph which displays [[Accumulator]] charge over time.
** Production statistics now has a special selectable item which shows the total of all [[Science pack]]s being produced.
** If using Space Age from the Paid Expansion, production statistics can show any or all Planets.
** If using Quality from the Paid Expansion, production statistics can show any or all Quality grades.
* [[Beacon]] Rebalance [https://factorio.com/blog/post/fff-409]
** Beacons now transmit at a base strength of 1.5, instead of 0.5.
** A beacon's effect on a building now scales based on the square root of the number of beacons effecting the building. Buildings with 8 or fewer beacons receive a buff, 9 or more receive a nerf.
** If using Quality from the Paid Expansion, higher quality beacons have a greater transmission power.

== See also ==
* [https://factorio.com/blog/post/fff-365 Friday Facts #365 - Future plans]
* [https://factorio.com/blog/post/fff-367 Friday Facts #367 - Expansion news]
* [https://factorio.com/blog/post/fff-370 Friday Facts #370 - The journey to Nintendo Switch]
* [https://factorio.com/blog/post/fff-373 Friday Facts #373 - Factorio: Space Age]
* [https://factorio.com/blog/post/fff-374 Friday Facts #374 - Smarter Robots]
* [https://factorio.com/blog/post/fff-375 Friday Facts #375 - Quality]
* [[Roadmap|Planned releases]]

{{C|News}}

Virtual signals

2017-02-07T07:23:00Z

Quchen: Rearrange each/output section

{{Languages}}

[[File:virtual_signals.png|thumb|300px]][[File:logic_signals.png|300px|thumb|There are three types of logic signals]]
'''Virtual signals''' can used as signals in [[Circuit network]]s. They are signals that are not associated with a certain item type, and therefore are immune to non-player based changes. If a circuit network contains virtual signals, they act like a normal item signal, so one can perform comparisons and arithmetical operations.

== Containing signals ==
Currently Factorio has 45 virtual signals:
* Numbers 0-9
* Letters A-Z
* Colors (red, green, blue, yellow, magenta, cyan, white, gray, black)

Each signal has:
* A ''name'' (for example "N") and
* A ''value'' (for example "19").

This is similar to a map in programming, where a key holds a value, and the value can be accessed by that key.

== Logic signals ==

There are also some logic signals in Factorio which are accessible by clicking certain signal slots on devices. They have special functions to control information with multiple signals. These three signals are:
* Everything
* Anything
* Each

=== Everything ===
==== As input ====
{| class="wikitable"
| {{imagelink|basic-transport-belt|Transport belts}} | {{imagelink|basic-inserter|Inserters}} | {{imagelink|gate|Gate}} | {{imagelink|rail-signal|Rail signal}} | {{imagelink|lamp|Lamp}} | {{imagelink|offshore-pump|Offshore Pump}} | {{imagelink|small-pump|Small pump}} | {{imagelink|decider-combinator|Decider Combinator}} | {{imagelink|power-switch|Power switch}} |-
|}
The "Everything" signal works like a logical AND. It can only be used as the left term of the circuit condition. The condition will only be true if the condition is true for all signals the device receives. Be careful with signals with amount 0, because these signals will not considered by "Everything", as they are considered 'inactive'.

If the decider combinator output is set as "Input count" and not "Everything", there will be no output even if the condition is true.
==== As output ====
{| class="wikitable"
| {{imagelink|decider-combinator|Decider Combinator}} |-
|}
If the condition is true, ''all input signals are outputted'', either with amount 1 or with their input amount.
=== Anything ===
==== As input ====
{| class="wikitable"
| {{imagelink|basic-transport-belt|Transport belts}} | {{imagelink|basic-inserter|Inserters}} | {{imagelink|gate|Gate}} | {{imagelink|rail-signal|Rail signal}} | {{imagelink|lamp|Lamp}} | {{imagelink|offshore-pump|Offshore Pump}} | {{imagelink|small-pump|Small pump}} | {{imagelink|decider-combinator|Decider Combinator}} | {{imagelink|power-switch|Power switch}} |-
|}
It works similar as "Everything", but the condition is true if the condition for at least one input signal is true. (logical OR)

==== As output ====

''Anything cannot be used as output, will output nothing.''

=== Each ===
==== As input ====
{| class="wikitable"
| {{imagelink|arithmetic-combinator|Arithmetic Combinator}} | {{imagelink|decider-combinator|Decider Combinator}} |-
|}
The "Each" signal also performs the operation for all input signals, but the condition is not true or false once, but true or false for each input signal individually.

If the output is "1" and not "Each" (decider combinators only), the signal will only be outputted if at least one condition is true. If the output is "Input count" and not "Each", all amounts of input signals whose condition is true or (for arithmetic combinators) the results of mathematical operations for each input signal are summed and outputted.
==== As output ====
{| class="wikitable"
| {{imagelink|arithmetic-combinator|Arithmetic Combinator}} | {{imagelink|decider-combinator|Decider Combinator}} |-
|}
The "Each" signal can only be set as output if the left input signal is also "Each".

* Decider combinators output only the input signals for which the input condition is true.
* Arithmetic combinators apply the operation to each input signal, and output the results alongside each other.

Roboport

2017-01-18T13:49:03Z

Quchen: Mention orange is smaller/green is bigger in introduction

{{Languages}}
{{:Roboport/infobox}}

The Roboport is the resting place for all [[Robots]]. It also emits an area of 50x50 tiles, in which logistic robots can interact with logistic network entities, such as [[Storage chest]]s, or [[Requester chest]]s. Additionally, a 100x100 tile area is created for construction robots to function. This can be seen by hovering the mouse on a roboport, or logistics chest.

* The smaller orange square represents the reach of the logistics network where logistics robots can move.
* The larger green square represents the extent of the construction network where construction robots can repair, construct or remove structures. Note that construction robots can function inside of the logistics square, it is not exclusive to logistics robots.

Robots placed into the air from the player's inventory inside of a roboport's coverage will seek out the nearest roboport to charge and rest.

Two or more roboports can connect to form a [[Robotic network|robotic network]], if the borders of the orange logistic areas touch. This is shown by a dotted line running between the two ports. An example of this can be seen on the bottom-right. Non-connected roboports will not share robots.

[[File:roboport_connection.jpg|300x300px|thumb|Two roboports connecting to form a logistic network. Notice the yellow dotted line indicating a successful bond.]]

== Storage ==
A Roboport contains 7 [[Storages/Stack|slots]] reserved for [[robots]], and another 7 for [[repair pack]]s. Robots and repair packs can be inserted into the roboport with an [[inserter]]. While seemingly useful, a repair pack inside a roboport is reserved for the construction robots inside the roboport only. Repair packs are better stored inside a [[Storage Chest|logistics storage chest]] or a [[passive provider chest]] where they can be used by all robots in the logistics network. Construction bots, when provided with repair packs, will automatically repair all damaged structures inside of a roboport's coverage area.

If a roboport is full of robots, robots attempting to rest will find a different roboport.

== Power usage ==
The Roboport needs ~50 kW of energy when idle, but can use up to 4 x ~1 MW when charging bots. Ensure the power grid can meet the demand when making large requests of the robot system.

Roboports have 4 chargers, which are used to recharge the flying bots. More roboports in a small area will allow for greater charging throughput, if a lot of robots need charging. Robots waiting to be charged will float in place near the roboport and wait their turn.

Robots will not enter a roboport to rest unless they have full charge. Robots with low/no charge can still fly, but will move extremely slowly.

== History ==

{{history|0.13.0|
* Roboport is connectible to the circuit network, it sends the logistic network contents or the robot statistics of the network.
* Roboports have decreased transmission power consumption (200 kW to 50 kW) while the robots and their recharging have increased power consumption (200 kW per recharge slot to 1MW per slot)
* Reduced number of drawn connections between roboports again.
* Optimized roboport radius rendering.
}}

{{history|0.12.5|
* Robots can charge from a closer roboport on their way to a more distant one.}}

{{history|0.12.0|
* Reduced number of rendered roboport connections.
* Inserters can now extract from roboports.
* Optimized adding and removing roboports, robots keep their tasks if possible.
}}

{{history|0.10.7|
* Roboport gui labels updated to state "Roboport"
* Roboport is no longer categorized as a military structure.
}}

{{history|0.10.0|
* Backer names are used to name roboports.}}

{{history|0.9.0|
* Roboports have a separate logistic radius (now 25) and construction radius (now 50)
* Area visualizations for roboports are displayed under their entities.
}}

{{history|0.8.5|
* Only repair packs may be placed into the roboport slots.}}

{{history|0.8.2|
* Roboport supply area increased from 40x40 to 50x50.
* Lowered transmission energy consumption of roboport from 200 W to 100 W
}}

{{history|0.8.0|
* Introduced}}

== See also ==
* [[Robotic network]]
* [[Logistic network]]
* [[Repair pack]]
* [[Robots]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=6005 How exactly do Roboports work with each other?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7993 Splitting up roboport functions]:
** Recharge bots
** Store unused bots
** Create a construction network
** Create a logistics network

{{LogisticsNav}}

[[Category:Items]]
{{C|Logistic network}}
{{C|Repair}}
{{C|Robots}}