Official Factorio Wiki - User contributions [en]

Military units and structures

2020-04-29T05:31:06Z

Jon8RFC: fix redirect

{{Languages}}
Some units and structures are marked as '''Military units''' or '''Military structures''' and are high priority targets for enemy forces. They will be attacked on sight by:

* [[Enemies#Biters|Biters]], [[Enemies#Spitters|spitters]], and [[Enemies#Worms|worms]].
* [[Gun_turret|Turrets]], [[Combat_robot_capsules|combat robots]], and [[personal laser defense]].
* The [[player]], when holding down "shoot enemy" (spacebar).

There are a few exceptions:
* [[Artillery turret]]s and [[Artillery wagon]]s will not attack units automatically, they only attack structures automatically.
* Biters and spitters do ''not'' prioritize [[construction robot]]s or [[logistic robot]]s over other targets.

__TOC__

== Modding ==
Military units and structures are identified by a hard coded flag on certain prototypes. This cannot be changed by [[modding]]. The military prototypes are listed in the table below.

== Military units ==
{| class="wikitable"
|-
! Icon !! Name !! Default force !! Prototype
|-
| [[File:Player.png|center]]
| [[Player]]
| player
| [[Prototype/Character|character]]
|-
| [[File:Defender_capsule.png|center|32px]]
| [[Defender capsule]]
| player
| [[Prototype/CombatRobot|combat-robot]]
|-
| [[File:Distractor_capsule.png|center|32px]]
| [[Distractor capsule]]
| player
| [[Prototype/CombatRobot|combat-robot]]
|-
| [[File:Destroyer_capsule.png|center|32px]]
| [[Destroyer capsule]]
| player
| [[Prototype/CombatRobot|combat-robot]]
|-
| [[File:Construction_robot.png|center|32px]]
| [[Construction robot]]
| player
| [[Prototype/ConstructionRobot|construction-robot]]
|-
| [[File:Logistic_robot.png|center|32px]]
| [[Logistic robot]]
| player
| [[Prototype/LogisticRobot|logistic-robot]]
|-
| [[File:Land_mine.png|center|32px]]
| [[Land mine]]
| player
| [[Prototype/LandMine|land-mine]]
|-
| [[File:small_biter.png|center|64px]]
| [[Enemies#Biters|Small biter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:small_spitter.png|center|72px]]
| [[Enemies#Spitters|Small spitter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:medium_biter.png|center|64px]]
| [[Enemies#Biters|Medium biter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:medium_spitter.png|center|72px]]
| [[Enemies#Spitters|Medium spitter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:big_biter.png|center|64px]]
| [[Enemies#Biters|Big biter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:big_spitter.png|center|72px]]
| [[Enemies#Spitters|Big spitter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:behemoth_biter.png|64px]]
| [[Enemies#Biters|Behemoth biter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:behemoth_spitter.png|center|72px]]
| [[Enemies#Spitters|Behemoth spitter]]
| enemy
| [[Prototype/Unit|unit]]
|-
| [[File:Compilatron.png|center]]
| Compilatron
| enemy
| [[Prototype/Unit|unit]]
|}

== Military structures ==
{| class="wikitable"
|-
! Icon !! Name !! Default force !! Prototype
|-
| [[File:Gun_turret.png|center|32px]]
| [[Gun turret]]
| player
| [[Prototype/AmmoTurret|ammo-turret]]
|-
| [[File:Flamethrower_turret.png|center|32px]]
| [[Flamethrower turret]]
| player
| [[Prototype/FluidTurret|fluid-turret]]
|-
| [[File:Laser_turret.png|center|32px]]
| [[Laser turret]]
| player
| [[Prototype/ElectricTurret|electric-turret]]
|-
| [[File:Artillery_turret.png|center|32px]]
| [[Artillery turret]]
| player
| [[Prototype/ArtilleryTurret|artillery-turret]]
|-
| [[File:Radar.png|center|32px]]
| [[Radar]]
| player
| [[Prototype/Radar|radar]]
|-
| [[File:Small_worm.png|center|50px]]
| [[Enemies#Worms|Small worm]]
| enemy
| [[Prototype/Turret|turret]]
|-
| [[File:Medium_worm.png|center|50px]]
| [[Enemies#Worms|Medium worm]]
| enemy
| [[Prototype/Turret|turret]]
|-
| [[File:Big_worm.png|center|50px]]
| [[Enemies#Worms|Big worm]]
| enemy
| [[Prototype/Turret|turret]]
|-
| [[File:Behemoth_worm.png|center|50px]]
| [[Enemies#Worms|Behemoth worm]]
| enemy
| [[Prototype/Turret|turret]]
|-
| [[File:Biter_nest.png|center|50px]]
| [[Enemies#Nests|Biter spawner]]
| enemy
| [[Prototype/EnemySpawner|enemy-spawner]]
|-
| [[File:Spitter_nest.png|center|50px]]
| [[Enemies#Nests|Spitter spawner]]
| enemy
| [[Prototype/EnemySpawner|enemy-spawner]]
|-
|
| [[Prototype/PlayerPort|Player port]]
|
| [[Prototype/PlayerPort|player-port]]
|-
|
| [[Prototype/SimpleEntityWithForce|SimpleEntityWithForce]]
|
| [[Prototype/SimpleEntityWithForce|simple-entity-with-force]]
|}

Power production

2020-04-29T05:19:27Z

Jon8RFC: /* Solar panels and accumulators */ fix redirect

{{Languages}}
Electricity has to be produced before it can be transferred to consumers over the [[electric system]]. There are multiple methods to produce electricity:

== Steam engine power ==
Each [[steam engine]] needs 0.5 [[boiler]]s when running at full capacity. One [[offshore pump]] can supply 20 boilers and 40 steam engines.

The above ratio can be calculated from information available in-game: One boiler consumes 1.8MW of fuel and produces energy stored in [[steam]] at 100% efficiency. One steam engine consumes 900kW of energy stored in steam, so each boiler can supply 2 steam engines: <code>1.8MW ÷ 0.9MW = 2</code>. One steam engine consumes 30 steam per second, and one offshore pump produces 1200 water per second, so each offshore pump produces enough water to supply 40 steam engines: <code>1200 unit/s ÷ 30 units/s = 40</code>. The number of boilers can be derived from the number of steam engines: <code>40 ÷ 2 = 20</code>. This produces the 1:20:40 ratio.

[[File:SteamSetupExample.png|center|600px|thumb|A possible setup]]

== Solar panels and accumulators ==

=== Optimal ratio ===

The optimal ratio is 0.84 (21:25) [[accumulator]]s per [[solar panel]], and 23.8 solar panels per megawatt required by your factory (this ratio accounts for solar panels needed to charge the accumulators). This means that you need 1.428 MW of production (of solar panels) and 100MJ of storage to provide 1 MW of power over one day-night cycle.

A "close enough" ratio is 20:24:1 accumulators to solar panels to megawatts required (for example, a factory requiring 10 MW can be approximately entirely powered, day and night, by 200 accumulators and 240 solar panels - this approximation differs from optimal only in that it calls for 20 extra solar panels, which is negligible but remember that the difference between the "close enough" ratio and the optimal ratio increases as you add more solar panels).

This is taken from [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=5594 Accumulator / Solar Panel Ratio] (which calculates this in an impressive mathematical way!) and [https://forums.factorio.com/viewtopic.php?p=143317#p143317 another post in that thread] (which calculates the solar panel to megawatt ratio in a different way).
[[File:9x9_accumulator_solar_panel_example.jpg|300px|thumb|top|A small 9x9 setup demonstrating the 20:24 "close enough" ratio above.]]
=== Calculations ===

The optimal ratio of accumulators per solar panel relies on many values in the game. These include the power generation of a solar panel, the energy storage of an accumulator, the length of a [[Time#Days|day]], and the length of a night. There are also times between day and night called dusk and dawn which complicate the calculations. In vanilla factorio, without mods which change any of these values, the optimal ratio will be the same. This ratio is
<pre>Accumulators / Solar_panels =
(day + dawn) × (night + dawn × (day + dawn) / game_day) / game_day
× Solar_power / Accumulator_energy</pre>

which, given the default time lengths of: day = 12500/60 s; dawn or dusk = 5000/60 s; night = 2500/60 s, and the default: Solar_power = 60 kW; Accumulator_energy = 5 MJ = 5000 kJ, gives the optimal ratio of 0.84 accumulators per solar panel. If the player uses mods which change the power generation of solar panels, or the energy storage of accumulators, but not the length of days, a simplified version of this equation can be used.
<pre>Accumulators / Solar_panels = 70 s × Solar_power / Accumulator_energy</pre>

This equation could also be used to remember the vanilla optimal ratio given its simplicity. If the only effect the mod has on the game is it changes the total length of one day, without changing the ratio of dusk : day : dawn : night, then the equation can be simplified as
<pre>Accumulators / Solar_panels = 0.002016 /s × game_day </pre>

where game_day is the number of seconds in the game day which is 25000/60 s by default.

=== See also ===

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=5168 Perfectly optimal solar network (Factorio forums)]
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5394 Solar ratios (Factorio forums)]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7619 1 solar panel produces 42KW after factoring in the night (Factorio forums)]

== Nuclear power ==
:''See also: [[Tutorial:Nuclear power]]''
In general, nuclear power is produced by the following production chain: [[Uranium ore]] is mined and [[Uranium processing|processed]] to [[uranium-235]] and [[uranium-238]], then [[uranium fuel cell]]s are created from the two. These fuel cells are then burned in a [[nuclear reactor]] to create heat. The heat can be used to convert [[water]] to [[steam]] using a [[heat exchanger]] and the steam can be consumed by [[steam turbine]]s to produce power.

A reactor without neighbor bonus needs 4 heat exchangers so that all its heat gets consumed. For each 100% neighbor bonus, the reactor needs 4 more heat exchangers.

{| class="wikitable"
|-
! Ideal Ratio !! Simple Ratio !! Building
|-
| 25 || 1 ||{{imagelink|Offshore pump}}
|-
| 291 || 12 || {{imagelink|Heat exchanger}}
|-
| 500 || 20 || {{imagelink|Steam turbine}}
|}

== Ensuring enough energy is produced ==

Try this checklist before you completely revamp your power source. You may also use this to rectify [[Glossary#B|brownouts/blackouts]].

* Did you connect the steam engine to the [[electric system]]? If not, a small yellow triangle will flash. To fix, Add some [[Small electric pole|power poles]] near the steam engines that go to machines needing that power. Any power pole will work.
* Is steam able to reach all steam engines?
* Do your pipes have water? Look at the windows in the pipes, hover over the pipes! Place some pipes or a tank at the end to see if there is really water coming through. If not, ensure all [[pipe]]s or [[Pipe to ground|underground pipes]] are connected together.
* Is the factory producing enough fuel (coal, solid fuel, uranium fuel cells)?
* Are there enough steam generators (boilers, heat exchangers)?
* Are there enough steam engines/turbines?

See also the [[Tutorial:Applied_power_math|applied power math tutorial]] to answer the question ''how much coal do I need?''

Steam engine

2020-04-29T05:17:26Z

Jon8RFC: /* History */ added to history

{{Languages}}
{{:Infobox:Steam engine}}

'''Steam engines''' are the most basic [[Electric system|electricity]] generator, available to the player at the start of the game. They produce electricity by consuming [[steam]], using [[water]] pumped from an [[offshore pump]] that was heated to 165°C steam with [[Boiler|boilers]] or to 500°C steam with [[heat exchanger]]s. Steam that has a higher temperature than the maximum temperature of the steam engine (165°C) is consumed at the normal rate (30 units/s), and does not yield more electricity. This means the energy that was put into the steam to heat it to a higher temperature is wasted.

Steam engines will automatically adjust their power production and steam usage based on the current demands of the electricity network. Hovering the mouse over a steam engine will display their current power production ('''Performance''') and their possible power production ('''Available Performance'''), in a display on the right.

Steam engines have two ports, allowing excess steam to flow through. This allows steam engines to be chained together. The current optimal ratio is 1 [[offshore pump]] to 20 [[boiler]]s to 40 steam engines.

Using steam engines for power does not produce [[pollution]], unless [[Boiler|boilers]] are used to heat up the water.

When producing power, the steam engine will display a working animation:

[[File:steam engine animation.gif]]

{{clear}}

== History ==
{{history|0.18.18|
* Adjusted steam engine and [[Steam_turbine|turbine]] collision boxes so player can walk between two steam engines.}}

{{history|0.15.0|
* [[Steam]] is now internally a separate fluid from hot [[water]].
* Added high graphics quality option for the steam engine.
* Increased the maximum [[power production]] of the steam engine from 510kW to 900kW.
* Doubled the heat capacity of water from 0.1kJ per degree per liter to 0.2kJ.
* Change fluidbox height and base level of boiler, steam engine and pump to improve fluid flow.
}}

{{history|0.10.7|
* Made bounding box smaller.}}

{{history|0.10.0|
* New graphics.
* New sounds.}}

{{history|0.5.1|
* New graphics}}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Electric system]]
** [[Power production]]
* [[Steam]]
* [[Pipe]]

{{ProductionNav}}
{{C|Energy}}

Steam turbine

2020-04-29T05:17:20Z

Jon8RFC: /* History */ added to history

{{Languages}}
{{:Infobox:Steam turbine}}
The '''steam turbine''' consumes [[steam]] to create electric energy. It is usually used together with [[heat exchanger]]s and a [[nuclear reactor]].

While designed for the 500°C steam of a nuclear reactor, turbines can still be connected to [[boiler]]s for use in conventional 165°C steam power. At this mode, the steam turbine acts equal to two separate [[Steam engine|steam engines]], producing 1800 kW and consuming 60 steam/sec. However, actual power production is based on the temperature of the steam, not the building itself. This means that using a steam turbine is no more fuel-efficient than using two steam engines. Unless saving space within a large build, it is not necessary to use the more costly turbines for boiler steam.

== Power output ==

Each Steam turbine takes a maximum input of 60 units of 500°C [[steam]] per second and outputs 5.82MW of electricity; the 5.8MW listed on the tooltip is rounded.

* [[Heat exchanger]] heats 15°C [[water]] to 500°C [[steam]];
* It takes 0.2 kJ of [[Fuel|burner]] energy to raise 1 water 1°C;
* Steam is consumed by steam turbines at a rate of 60 units of water per second;
* (500°C - 15°C) × 0.2 kJ × 60 units = 5820 kW, or 5.82 MW.
* On the other hand, the calculation for the Boiler-generated steam is: (165°C - 15°C) × 0.2 kJ × 60 units = 1800 kW, or 1.8 MW.

== History ==
{{history|0.18.18|
* Adjusted [[Steam_engine|steam engine]] and turbine collision boxes so player can walk between two steam engines.}}

{{History|0.15.0|
* Introduced}}

== See also ==
* [[Power production#Nuclear power|Power production]]
* [[Heat pipe]]
* [https://www.reddit.com/r/factorio/comments/67xgge/nuclear_ratios/ Nuclear ratios]

{{ProductionNav}}
{{C|Energy}}

Steam engine

2020-04-29T05:10:23Z

Jon8RFC: remove superfluous (and redirecting) link

{{Languages}}
{{:Infobox:Steam engine}}

'''Steam engines''' are the most basic [[Electric system|electricity]] generator, available to the player at the start of the game. They produce electricity by consuming [[steam]], using [[water]] pumped from an [[offshore pump]] that was heated to 165°C steam with [[Boiler|boilers]] or to 500°C steam with [[heat exchanger]]s. Steam that has a higher temperature than the maximum temperature of the steam engine (165°C) is consumed at the normal rate (30 units/s), and does not yield more electricity. This means the energy that was put into the steam to heat it to a higher temperature is wasted.

Steam engines will automatically adjust their power production and steam usage based on the current demands of the electricity network. Hovering the mouse over a steam engine will display their current power production ('''Performance''') and their possible power production ('''Available Performance'''), in a display on the right.

Steam engines have two ports, allowing excess steam to flow through. This allows steam engines to be chained together. The current optimal ratio is 1 [[offshore pump]] to 20 [[boiler]]s to 40 steam engines.

Using steam engines for power does not produce [[pollution]], unless [[Boiler|boilers]] are used to heat up the water.

When producing power, the steam engine will display a working animation:

[[File:steam engine animation.gif]]

{{clear}}

== History ==
{{history|0.15.0|
* [[Steam]] is now internally a separate fluid from hot [[water]].
* Added high graphics quality option for the steam engine.
* Increased the maximum [[power production]] of the steam engine from 510kW to 900kW.
* Doubled the heat capacity of water from 0.1kJ per degree per liter to 0.2kJ.
* Change fluidbox height and base level of boiler, steam engine and pump to improve fluid flow.
}}

{{history|0.10.7|
* Made bounding box smaller.}}

{{history|0.10.0|
* New graphics.
* New sounds.}}

{{history|0.5.1|
* New graphics}}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Electric system]]
** [[Power production]]
* [[Steam]]
* [[Pipe]]

{{ProductionNav}}
{{C|Energy}}

Tree

2020-04-29T05:07:59Z

Jon8RFC: added history section

{{Languages}}
{{:Infobox:Tree}}
'''Trees''' are plants in Factorio. They can be mined for [[wood]], and are the only source of it. Trees are obstacles to construction and must be cleared to provide building space, but they also reduce [[pollution]], so take care not to remove more than necessary. Currently, trees cannot be replanted.

== Achievements ==
{{Achievement|run-forrest-run}}
{{Achievement|pyromaniac}}

== Good methods to remove trees ==

* Mining by hand (*)
* Shooting swaths of trees with a [[shotgun]] or [[combat shotgun]]
* Using [[grenade]]s to blow them up
* Using [[Poison capsule|poison]] to kill them
* Having construction robots harvest them using a [[deconstruction planner]] (*)
* Knocking them down by driving a [[tank]] over them
* Burning them with a [[flamethrower]], causing a forest fire
* Burning them with a flamethrower while in a tank
* Using [[atomic bomb]]s to blow them up

(*) Usable to collect wood. Dead trees will give 2 wood and have a mining time of 0.5. Live trees will give 4 wood and have a mining time of 0.55. All other methods just destroy the tree and wood.

== Fires ==
[[File:ForestFireBegins.gif|frame|A forest fire spreads rapidly after a few moments.]]
Trees can be set on fire by [[flamethrower]]s and [[flamethrower turret]]s. The fire will spread from tree to tree, releasing high amounts of [[pollution]] and leaving stumps and charred trees behind.

Once on fire, trees cannot be extinguished, but the spread of the fire can be limited by creating a [[wikipedia:Firebreak|fire break]].

== Pollution removal ==

Every single tree absorbs a small amount of pollution in its chunk per second. If the total pollution in a chunk is above 60 units, once per second some of the trees in that chunk each have a chance to either lose one stage of leaves or have their leaves become one stage more gray. Regardless of whether the tree loses leaves or gets grayer, 10 pollution are absorbed by the tree. 
A tree stops losing leaves/becoming more gray once the sum of its gray percentage and its leaves lost percentage is above 120%. As the grayness and leave stage are then locked for that tree forever, it is possible for trees to keep some leaves in heavily polluted chunks but in turn be very gray, or the other way around. 
The less dense the leaves, the slower the tree absorbs pollution, however tree grayness does not affect pollution absorption.

{| class="wikitable"
! Object !! Stage !! Pollution per second
|-
| rowspan="4" | [[File:Green tree.png|120px]] Tree, red tree, brown tree || 0 (Max leaf density) || -0.001
|-
| 1 || -0.00067
|-
| 2 || -0.00033
|-
| 3 (Min leaf density) || 0
|-
| [[File:Dead dry hairy tree.png|120px]] Dead dry hairy tree || No stages || -0.0001
|-
| [[File:Dead grey trunk.png|120px]] Dead gray trunk || No stages || -0.0001
|-
| [[File:Dead tree desert.png|120px]] Dead tree - desert|| No stages || -0.0001
|-
| [[File:Dry hairy tree.png|120px]] Dry hairy tree || No stages || -0.0001
|-
| [[File:Dry tree.png|120px]] Dry tree || No stages || -0.0001
|-
|}

== History ==

{{history|0.18.0|
* Added animation to trees.}}

{{history|0.17.0|
* New graphics.}}

{{history|0.16.0|
* Tanks no longer take miniscule amounts of damage from hitting trees.}}

{{history|0.15.28|
* Damaging a tree with impact or physical damage generates some leaves.}}

{{history|0.13.0|
* Added fire. Fire will spread between trees and cause forest fires, causing a large amount of pollution to be released.}}

{{history|0.12.0|
* Trees degenerate slowly when there high pollution levels.
* Trees regenerate health slowly.
* Trees have generally smaller bounding boxes, so it is easier to walk through forest.
* New tree graphics. Trees have 4 levels of leaves and the leaves are colorable.
* Trees emit leaves (based on the tree color) when being mined and destroyed.
* Trees emit branches when mined or destroyed.}}

{{history|0.9.2|
* Changed the amount of wood in dry tree from 1 -> 4.}}

{{history|0.9.0|
* New graphics: 10 types of trees that replace the outdated 2 types.}}

{{history|0.3.0|
* New tree graphics (8 dry trees 12 big trees).}}

== See also ==

* [[Wood]]
* [[Pollution]]

Poison capsule

2020-04-29T04:10:45Z

Jon8RFC: /* History */ update history

{{languages}}
{{:Infobox:Poison capsule}}

A basic capsule that creates a large, long-lasting cloud of at the target area, dealing 320 [[Damage|poison damage]] over 20s, the damage from multiple poison capsules stacks. This is one of the most effective ways of removing [[tree]]s.

Poison capsules can be used to effectively kill [[Enemies|worms]] as they are stationary. This technique is a relatively safe and cheap way to eliminate clusters of worms - it takes 3 poison capsules to kill a big Worm and the capsules can be thrown from outside the big Worm's spitting range. Since [[Enemies#Nests|spawners]] are not affected by poison damage, poison capsules are useless against them.

Poison capsules do not harm the player's structures, robots or vehicles, but do harm players themselves unless they are in a vehicle. Poison capsules are particularly effective when deployed from the [[tank]], as the tank can park inside a cloud of poison to lure enemies to their death.

=== Damage ===

The poison cloud deals 8 poison damage twice a second and lasts for 20s, a maximum of 320 damage.

[[File:Poison-usage.gif|frame|none|Poison capsule being deployed against some trees. Note the size of the cloud created, and damage taken.]]

== History ==

{{history|0.18.7|
* New visuals for poison capsule effect.}}

{{history|0.11.17|
* Tooltips are now generated automatically for some items, including capsules.}}

{{history|0.11.9|
* Green coral is now affected by the poison capsule. This is controlled by the "breaths-air" entity flag.}}

{{history|0.9.2|
* Poison capsules can now damage [[Enemies|worms]].}}

{{history|0.9.1|
* Capsules can be used in god mode. ([[player]] without character)}}

{{history|0.7.1|
* Capsule is less expensive.}}

{{history|0.7.0|
* Introduced}}

== See also ==
* [[Defender capsule]]
* [[Slowdown capsule]]
* [[Distractor capsule]]
* [[Destroyer capsule]]

{{CombatNav}}
{{C|Capsules}}

Poison capsule

2020-04-29T04:09:15Z

Jon8RFC: fix redirect

{{languages}}
{{:Infobox:Poison capsule}}

A basic capsule that creates a large, long-lasting cloud of at the target area, dealing 320 [[Damage|poison damage]] over 20s, the damage from multiple poison capsules stacks. This is one of the most effective ways of removing [[tree]]s.

Poison capsules can be used to effectively kill [[Enemies|worms]] as they are stationary. This technique is a relatively safe and cheap way to eliminate clusters of worms - it takes 3 poison capsules to kill a big Worm and the capsules can be thrown from outside the big Worm's spitting range. Since [[Enemies#Nests|spawners]] are not affected by poison damage, poison capsules are useless against them.

Poison capsules do not harm the player's structures, robots or vehicles, but do harm players themselves unless they are in a vehicle. Poison capsules are particularly effective when deployed from the [[tank]], as the tank can park inside a cloud of poison to lure enemies to their death.

=== Damage ===

The poison cloud deals 8 poison damage twice a second and lasts for 20s, a maximum of 320 damage.

[[File:Poison-usage.gif|frame|none|Poison capsule being deployed against some trees. Note the size of the cloud created, and damage taken.]]

== History ==

{{history|0.11.17|
* Tooltips are now generated automatically for some items, including capsules.}}

{{history|0.11.9|
* Green coral is now affected by the poison capsule. This is controlled by the "breaths-air" entity flag.}}

{{history|0.9.2|
* Poison capsules can now damage [[Enemies|worms]].}}

{{history|0.9.1|
* Capsules can be used in god mode. ([[player]] without character)}}

{{history|0.7.1|
* Capsule is less expensive.}}

{{history|0.7.0|
* Introduced}}

== See also ==
* [[Defender capsule]]
* [[Slowdown capsule]]
* [[Distractor capsule]]
* [[Destroyer capsule]]

{{CombatNav}}
{{C|Capsules}}

Achievement file format

2020-04-29T04:08:09Z

Jon8RFC: /* File Format */ fix redirect

{{Languages}} [[Category:Technical]]
This is a technical description of the achievement file format, used by Factorio to store player's achievement progress in the files "achievements.dat" and "achievements-modded.dat".

Yes - this information can be used to "cheat" Factorio by simply writing to the achievement file(s) in such a way as if you had met all the achievement requirements, open up Factorio, and then suddenly have all achievements unlocked. The goal of this document is to share how to _read_ the achievement file(s) - so that third party applications can do new and interesting things with that information. Enjoy!

See the page on [[Data_Types|data types]] for an explanation of the different types of data used in this document.

== File Format ==

The overall file format is as follows. Note that in this file, [[Data_Types#array|array]] length is stored as a [[Data_Types#short|short]], not an [[Data_Types#int|int]]!

{| class="wikitable"
! Type !! Description
|-
| [[Data_Types#short|short]][4]
| The [[Version_string_format|version string]] of Factorio that generated this file.
|-
| [[Data_Types#array|array]]<[[#Achievement Header Info|bytes]]>
| [[#Achievement Header Info|Achievement header info]]. Variable length. See the section for more information.
|-
| [[Data_Types#array|array]]<[[#Achievement Content Info|bytes]]>
| [[#Achievement Content Info|Achievement content info]]. Variable length. See the section for more information.
|-
| [[Data_Types#short|short]][*]
| Currently tracked achievements, given as a series of [[Data_Types#short|shorts]] up until the end of the file, with each representing the index number of an achievement. The order of achievements in this series matches the order of which the player has them tracked in game.
|}
This format has been valid since at least version 0.14.x.

== Achievement Header Info ==

The header contains information about what type of data fields each achievement has.

{| class="wikitable"
! Type !! Description
|-
| [[Data_Types#string|string]]
| Achievement type. This determines what kind of data fields this achievement contains in the content array.
|-
| [[Data_Types#string|string]]
| Achievement string id - the one used internally by Factorio.
|-
| [[Data_Types#short|short]]
| Achievement index number. This number is used to map achievements between this header info array, the content info array, and the tracked achievements list in this file. These index numbers are non-normative, so they won't always match up with the same achievement. Note: the mapping of index numbers to achievement ids are continuous, but start at index 1 (there is no index 0) - because LUA tables start at 1.
|}

== Achievement Content Info ==

This contains the actual data of each achievement. It's important to note that not every achievement listed in the header has a matching content section here.

Also note that this array always ends with an index number of 0. When reading, either ignore this, or manually add in a blank achievement into your meta table at index zero with no fields.

{| class="wikitable"
! Type !! Description
|-
| [[Data_Types#short|short]]
| Achievement index number. This matches up with the index number in the [[#Achievement Header Info|Achievement header info]].
|-
| byte[*]
| The achievement's progress information. The structure and length of this is determined by the [[#Achievement Types|achievement's type]]. See the table below for a list of achievement types.
|}

== Achievement Types ==

If new achievement types are added in the future, the achievement files will be unparse-able. Please add any new types you find here, thanks!

See the [[Prototype/Achievement]] base prototype page for more information about achievement structure.

{| class="wikitable"
! Achievement Type !! Binary Fields(s) !! Field(s) Description
|-
| [[Prototype/BuildEntityAchievement|build-entity-achievement]]
|
* byte[4]
|
* Unknown format, 4 bytes long.
|-
| [[Prototype/CombatRobotCountAchievement|combat-robot-count]]
|
* [[Data_Types#int|int]]
|
* The greatest number of combat robots you've had following you.
|-
| [[Prototype/ConstructWithRobotsAchievement|construct-with-robots-achievement]]
|
* [[Data_Types#int|int]]
* byte[4]
|
* Total number of objects constructed using robots.
* Unknown format, 4 bytes long.
|-
| [[Prototype/DeconstructWithRobotsAchievement|deconstruct-with-robots-achievement]]
|
* [[Data_Types#int|int]]
|
* Total number of objects deconstructed using robots.
|-
| [[Prototype/DeliverByRobotsAchievement|deliver-by-robots-achievement]]
|
* byte[8]
|
* Unknown format, 8 bytes long.
|-
| [[Prototype/DontBuildEntityAchievement|dont-build-entity-achievement]]
|
''TODO''
|
''TODO''
|-
| [[Prototype/DontCraftManuallyAchievement|dont-craft-manually-achievement]]
|
''TODO''
|
''TODO''
|-
| [[Prototype/DontUseEntityInEnergyProductionAchievement|dont-use-entity-in-energy-production-achievement]]
|
* [[Data_Types#double|double]]
|
* Maximum number of Joules produced per hour, only including power produced from entities listed under "[[Prototype/DontUseEntityInEnergyProductionAchievement#included|included]]", and excluding those listed under "[[Prototype/DontUseEntityInEnergyProductionAchievement#excluded|excluded]]".
|-
| [[Prototype/FinishTheGameAchievement|finish-the-game-achievement]]
|
''TODO''
|
''TODO''
|-
| [[Prototype/GroupAttackAchievement|group-attack-achievement]]
|
* byte[4]
|
* Unknown format, 4 bytes long.
|-
| [[Prototype/KillAchievement|kill-achievement]]
|
* [[Data_Types#double|double]]
|
* The greatest number of an entity killed (e.g. trees, spawners).
|-
| [[Prototype/PlayerDamagedAchievement|player-damaged-achievement]]
|
* [[Data_Types#float|float]]
* [[Data_Types#bool|bool]]
|
* The maximum amount of damage you've taken in a single hit.
* True if the you survived that hit, False if you died.
|-
| [[Prototype/ProduceAchievement|produce-achievement]]
|
* [[Data_Types#double|double]]
|
* The total number of the item you've produced.
|-
| [[Prototype/ProducePerHourAchievement|produce-per-hour-achievement]]
|
* [[Data_Types#double|double]]
|
* The maximum amount of the item produced per hour.
|-
| [[Prototype/ResearchAchievement|research-achievement]]
|
* byte[4]
|
* Unknown format, 4 bytes long.
|-
| [[Prototype/TrainPathAchievement|train-path-achievement]]
|
* [[Data_Types#double|double]]
|
* The longest path (in tiles) planned by a train.
|}

"combat-robot-count" is currently the only achievement type that doesn't end in "-achievement". This is not an error.

Map exchange string format

2020-04-29T04:07:47Z

Jon8RFC: /* Factorio 0.14 and Beyond */ fix redirect

{{Languages}} [[Category:Technical]]
This is a technical description of the map exchange string format, used to share map generating configurations with other users. This format is also used to store these settings inside save files for future chunk generation.

Factorio line wraps the entire map exchange string after 57 characters during export (55 code characters + '\r\n', which is fairly standard), but ignores all whitespace during import. The outer layer of the map exchange string format includes three angle brackets on either side: ">>>" and "<<<", which must be present for Factorio to accept the string. Between those two tokens is the map exchange data, encoded using base 64 as defined by [https://tools.ietf.org/html/rfc4648#section-4 RFC 4648] (or [https://tools.ietf.org/html/rfc3548#section-3 3548], [https://tools.ietf.org/html/rfc2535#page-42 2535], [https://tools.ietf.org/html/rfc2045#section-6.8 2045], [https://tools.ietf.org/html/rfc1421#section-4.3.2.4 1421], et al).

See the page on [[Data types|data types]] for an explanation of the different types of data used in this document.

== Factorio 0.16 and Beyond ==

Beginning with Factorio 0.16.0, two important changes are made to the encoding of the map exchange string data:

# The map exchange data inside the Base 64 encoding is further encoded using the [https://en.wikipedia.org/wiki/Zlib zlib] compression algorithm. The best way to determine the encoding is to first attempt to parse the map exchange string using zlib, and if that fails, try again using the 0.14+ rules.
# All numeric data fields longer than 1 byte are encoding using a custom-built variable length integer format described by Factorio developer [[User:Rseding91|Rseding]] at [[Data_types#Space_Optimized]]. For appropriate Factorio versions, '''all''' such data types (int, short, dict, etc) used in this document represent values encoded using this approach, ''unless otherwise specifically noted''.

After taking these considerations into your codec, proceed using the 0.14+ rules below.

== Factorio 0.14 and Beyond ==

This is the base map exchange string format for all Factorio versions 0.14.x and greater.

{| class="wikitable"
! Type !! Description
|-
| [[Data types#short|short]][4]
| The [[Version_string_format|version string]] of Factorio that generated this string, used to determine encoding format. This field is never [[Data_types#Space_Optimized|space optimized]].
|-
| byte[*]
| [[#Map_Gen_Settings|Map Gen Settings]]. Variable length. See linked section for information on how to parse.
|-
| byte[*]
| [[#0.15 Map Settings|0.15.x Map Settings]]. If present, this chunk consists of the remainder of the data (minus the checksum).
|-
| [[Data types#uint|uint]]
| [https://en.wikipedia.org/wiki/Cyclic_redundancy_check CRC32 checksum] of all preceding data, as defined by ANSI X3.66 / FIPS 71 / ITU-T V.42 (the same one used by [https://en.wikipedia.org/wiki/Zlib zlib], ethernet, etc.)
|}

== Map Gen Settings ==

This format matches [http://lua-api.factorio.com/latest/Concepts.html#MapGenSettings MapGenSettings].

The "From" column denotes the earliest Factorio version in which that field is present. Most of them are currently labeled as "≤0.14", which means the field was present from ''at least'' 0.14. If you have more specific information, please edit this page!

{| class="wikitable"
! Type !! LUA key !! From !! Description
|-
| [[Data types#byte|byte]]
| terrain_segmentation
| ≤0.14
| [[Water]] [[#Map_Gen_Size|frequency]].
|-
| [[Data types#byte|byte]]
| water
| ≤0.14
| [[Water]] [[#Map_Gen_Size|size]].
|-
| [[Data types#dict|dict]]<[[Data types#string|string]], [[#Autoplace_Control|byte[3]]]>
| autoplace_controls
| ≤0.14
| An dictionary of [[#Autoplace_Control|Autoplace Controls]], with string keys, where the key represents the resource name. Factorio doesn’t care what order this dictionary is in, but it always alphabetizes during export. Vanilla has seven resources: [[Coal|coal]], [[Copper ore|copper-ore]], [[Crude oil|crude-oil]], [[Enemies|enemy-base]], [[Iron ore|iron-ore]], [[Stone|stone]], and [[Uranium ore|uranium-ore]]. Unknown ores are ignored and missing ores are set to their defaults.
Factorio 0.16.x adds addition terrain related autoplace features: desert, dirt, grass, sand, trees. With the exception of trees, these resources ignore their richness and as such are not configuration using the map gen GUI, and always have a richness value of 3 ("Regular").
|-
| [[Data types#byte|byte]][2]
| TODO
| 0.16.0
| TODO...
|-
| [[Data types#int|uint]]
| seed
| ≤0.14
| [[World generator#Map Seed|Map seed]]. This field is never [[Data_types#Space_Optimized|space optimized]].
|-
| ''none''
| shift
| ≤0.14
| This field isn't present in the binary format! But it is part of the LUA structure - by default it's derived from the map seed. I'll slap the algorithm here soon(tm).
|-
| [[Data types#int|uint]]
| width
| ≤0.14
| [[World generator#Map-width and -height|Map width]]. This field is never [[Data_types#Space_Optimized|space optimized]].
|-
| [[Data types#int|uint]]
| height
| ≤0.14
| [[World generator#Map-width and -height|Map height]]. This field is never [[Data_types#Space_Optimized|space optimized]].
|-
| [[Data types#byte|byte]]
| starting_area
| ≤0.14
| [[World generator#Starting area|Starting area]] [[#Map_Gen_Size|size]].
|-
| [[Data types#bool|boolean]]
| peaceful_mode
| ≤0.14
| [[World generator#Peaceful mode|Peaceful mode]]. Enabled if set to 1, disabled otherwise.
|}

== 0.15 Map Settings ==

All of the following data fields (until noted at the end) have a special encapsulation format. Preceding each value is a single byte that states whether or not the value is present. If the byte is equal to zero, then the field value is not present. Otherwise, then the field's value follows.

In the LUA structure, this information is stored in the "[http://lua-api.factorio.com/latest/LuaGameScript.html#LuaGameScript.map_settings game.map_settings]" table, which is created by the "[http://lua-api.factorio.com/latest/Concepts.html#MapSettings MapSettings]" prototype. Each section in the table below represents a nested sub-table in "map-settings", where the LUA key listed is the key of the table, and all subsequent fields are part of the sub-table. See data/base/prototypes/map-settings.lua for a description of all attributes (some of that information has now been copied to this page).

Fields marked with a check (✓) in the "GUI" column are configurable in the [[World_generator#How_it_works|new game map generator GUI]].

{| class="wikitable mw-collapsible mw-collapsed"
! Type !!+ style='writing-mode:vertical-lr;vertical-align:bottom;font-size:90%' | GUI !! LUA key !! Description
|-
! * !! ✓ !! pollution !! Pollution
|-
| [[Data types#bool|boolean]] || ✓ || enabled || Pollution enabled.
|-
| [[Data types#double|double]] || ✓ || diffusion_ratio || The amount of pollution that is diffused into neighboring chunk per second.
|-
| [[Data types#double|double]] || || min_to_diffuse || This many PUs must be on the chunk to start diffusing.
|-
| [[Data types#double|double]] || ✓ || ageing || [Modifier of] the pollution eaten by a chunks tiles.
|-
| [[Data types#double|double]] || || expected_max_per_chunk || Anything bigger than this is visualised as this value.
|-
| [[Data types#double|double]] || || min_to_show_per_chunk || Anything lower than this (but > 0) is visualised as this value.
|-
| [[Data types#double|double]] || ✓ || min_pollution_to_damage_trees || Any pollution above this amount starts to damage trees.
|-
| [[Data types#double|double]] || || pollution_with_max_forest_damage || ???
|-
| [[Data types#double|double]] || || pollution_per_tree_damage || ???
|-
| [[Data types#double|double]] || ✓ || pollution_restored_per_tree_damage || The amount of pollution absorbed by a tree when it is damaged by pollution.
|-
| [[Data types#double|double]] || || max_pollution_to_restore_trees || ???
|-
! * !! !! steering.default !! Steering (Default)
|-
| [[Data types#double|double]] || || ??? || ???
|-
| [[Data types#double|double]] || || ??? || ???
|-
| [[Data types#double|double]] || || separation_force || ???
|-
| [[Data types#bool|boolean]] || || force_unit_fuzzy_goto_behavior || ???
|-
! * !! !! steering.moving !! Steering (Moving)
|-
| [[Data types#double|double]] || || ??? || ???
|-
| [[Data types#double|double]] || || ??? || ???
|-
| [[Data types#double|double]] || || separation_force || ???
|-
| [[Data types#bool|boolean]] || || force_unit_fuzzy_goto_behavior || ???
|-
! * !! ✓ !! enemy_evolution !! Evolution
|-
| [[Data types#bool|boolean]] || ✓ || enabled || Evolution enabled.
|-
| [[Data types#double|double]] || ✓ || time_factor || Percent increase in the evolve factor for every second.
|-
| [[Data types#double|double]] || ✓ || destroy_factor || Percent increase in the evolve factor for every destroyed spawner.
|-
| [[Data types#double|double]] || ✓ || pollution_factor || Percent increase in the evolve factor for every 1000 PU [produced].
|-
! * !! ✓ !! enemy_expansion !! Enemy Expansion
|-
| [[Data types#bool|boolean]] || ✓ || enabled || Enemy expansion enabled.
|-
| [[Data types#int|int]] || ✓ || max_expansion_distance || Distance in chunks from the furthest base around.
|-
| [[Data types#int|int]] || || friendly_base_influence_radius || ???
|-
| [[Data types#int|int]] || || enemy_building_influence_radius || ???
|-
| [[Data types#double|double]] || || building_coefficient ||+ rowspan=4 | Expansion algorithm. See LUA file for details.
|-
| [[Data types#double|double]] || || other_base_coefficient
|-
| [[Data types#double|double]] || || neighbouring_chunk_coefficient
|-
| [[Data types#double|double]] || || neighbouring_base_chunk_coefficient
|-
| [[Data types#double|double]] || || max_colliding_tiles_coefficient || A chunk has to have at most this much percent unbuildable tiles for it to be considered a candidate.
|-
| [[Data types#int|int]] || ✓ || settler_group_min_size ||+ rowspan=2 | Size of the group that goes to build new base (in game this is multiplied by the evolution factor).
|-
| [[Data types#int|int]] || ✓ || settler_group_max_size
|-
| [[Data types#int|int]] || ✓ || min_expansion_cooldown || Minimum cooldown.
|-
| [[Data types#int|int]] || ✓ || max_expansion_cooldown || Maximum cooldown.
|-
! * !! !! unit_group !! Unit Group
|-
| [[Data types#int|int]] || || min_group_gathering_time ||+ rowspan=2 | A pollution triggered group's waiting time is a random time between min and max gathering time.
|-
| [[Data types#int|int]] || || max_group_gathering_time
|-
| [[Data types#int|int]] || || max_wait_time_for_late_members || After the gathering is finished the group can still wait for late members, but it doesn't accept new ones anymore.
|-
| [[Data types#double|double]] || || max_group_radius ||+ rowspan=2 | Limits for group radius.
|-
| [[Data types#double|double]] || || min_group_radius
|-
| [[Data types#double|double]] || || max_member_speedup_when_behind || When a member falls behind the group he can speedup up till this much of his regular speed.
|-
| [[Data types#double|double]] || || max_member_slowdown_when_ahead || When a member gets ahead of its group, it will slow down to at most this factor of its speed.
|-
| [[Data types#double|double]] || || max_group_slowdown_factor || When members of a group are behind, the entire group will slow down to at most this factor of its max speed.
|-
| [[Data types#double|double]] || || max_group_member_fallback_factor || If a member falls behind more than this times the group radius, the group will slow down to max_group_slowdown_factor.
|-
| [[Data types#double|double]] || || member_disown_distance || If a member falls behind more than this time the group radius, it will be removed from the group.
|-
| [[Data types#int|int]] || || tick_tolerance_when_member_arrives || ???
|-
| [[Data types#int|int]] || || max_gathering_unit_groups || Maximum number of automatically created unit groups gathering for attack at any time.
|-
| [[Data types#int|int]] || || max_unit_group_size || Maximum size of an attack unit group. This only affects automatically-created unit groups.
|-
! * !! !! path_finder !! Path Finder
|-
| [[Data types#int|int]] || || fwd2bwd_ratio || Defines whether we prefer forward (>1) or backward (<-1) or symmetrical (1) search.
|-
| [[Data types#double|double]] || || goal_pressure_ratio || When comparing nodes in open which one to check next, heuristic value is multiplied by this ratio. The higher the number the more is the search directed directly towards the goal.
|-
| [[Data types#bool|boolean]] || || use_path_cache || ???
|-
| [[Data types#double|double]] || || max_steps_worked_per_tick || When this is exhausted no more requests are allowed. At the moment the first path to exhaust this will be finished (even if it is hundreds of steps).
|-
| [[Data types#int|int]] || || short_cache_size ||+ rowspan=2 | Number of elements in the cache.
|-
| [[Data types#int|int]] || || long_cache_size
|-
| [[Data types#double|double]] || || short_cache_min_cacheable_distance || Minimal distance to goal for path to be searched in short path cache.
|-
| [[Data types#int|int]] || || short_cache_min_algo_steps_to_cache || Minimal number of algorithm steps for path to be inserted into the short path cache.
|-
| [[Data types#double|double]] || || long_cache_min_cacheable_distance || Minimal distance to goal for path to be searched in long path cache.
|-
| [[Data types#int|int]] || || cache_max_connect_to_cache_steps_multiplier || When searching for connection to path cache path, search at most for this number of steps times the initial estimate.
|-
| [[Data types#double|double]] || || cache_accept_path_start_distance_ratio || When looking for path from cache make sure it doesn't start too far from requested start in relative distance terms.
|-
| [[Data types#double|double]] || || cache_accept_path_end_distance_ratio || When looking for path from cache make sure it doesn't end too far from requested end. This is typically higher than accept value for the start because the end target can be moving.
|-
| [[Data types#double|double]] || || negative_cache_accept_path_start_distance_ratio || Same as cache_accept_path_start_distance_ratio, but used for negative cache queries.
|-
| [[Data types#double|double]] || || negative_cache_accept_path_end_distance_ratio || Same as cache_accept_path_end_distance_ratio, but used for negative cache queries.
|-
| [[Data types#double|double]] || || cache_path_start_distance_rating_multiplier || When assigning rating to the best path this * start distances is considered.
|-
| [[Data types#double|double]] || || cache_path_end_distance_rating_multiplier || When assigning rating to the best path this * end distances is considered. This is typically higher than value for the start to achieve better path end quality.
|-
| [[Data types#double|double]] || || stale_enemy_with_same_destination_collision_penalty || Somewhere along the path is stuck enemy we need to avoid. This is mainly to handle situations when units have arrived and are attacking the target, then units further in the back will use this and run around the target.
|-
| [[Data types#double|double]] || || ignore_moving_enemy_collision_distance || If there is a moving unit further than this we don't really care.
|-
| [[Data types#double|double]] || || enemy_with_different_destination_collision_penalty || Enemy is not moving/or is too close and has different destination.
|-
| [[Data types#double|double]] || || general_entity_collision_penalty || Simplification for now - collision with everything else is this.
|-
| [[Data types#double|double]] || || general_entity_subsequent_collision_penalty || Collision penalty for successors of positions that require destroy to reach.
|-
| [[Data types#int|int]] || || max_clients_to_accept_any_new_request || Uptil this amount any client will be served by the path finder (no estimate on the path length).
|-
| [[Data types#int|int]] || || max_clients_to_accept_short_new_request || From max_clients_to_accept_any_new_request till this one only those that have a short estimate will be served.
|-
| [[Data types#int|int]] || || direct_distance_to_consider_short_request || This is the "threshold" to decide what is short and what is not.
|-
| [[Data types#int|int]] || || short_request_max_steps || If a short request takes more than this many steps, it will be rescheduled as a long request.
|-
| [[Data types#double|double]] || || short_request_ratio || How many steps will be allocated to short requests each tick, as a ratio of all available steps per tick.
|-
| [[Data types#int|int]] || || min_steps_to_check_path_find_termination || Absolute minimum of steps that will be performed for every path find request no matter what.
|-
| [[Data types#double|double]] || || start_to_goal_cost_multiplier_to_terminate_path_find || If the amount of steps is higher than this times estimate of start to goal then path finding is terminated.
|-
| colspan = 4 | '''Note:''' The following fields do not use the special encapsulation method.
|-
! byte[4] !! !! . (root) !! Other
|-
| [[Data types#int|int]] || || max_failed_behavior_count || If a behavior fails this many times, the enemy (or enemy group) is destroyed. This solves biters stuck within their own base.
|-
! Type !!+ style='writing-mode:vertical-lr;vertical-align:bottom;font-size:90%' | GUI !! LUA key !! Description
|}

=== Difficulty Settings ===

This information is instead stored in the LUA structure at [http://lua-api.factorio.com/latest/LuaGameScript.html#LuaGameScript.difficulty_settings game.difficulty_settings], which is prototyped by [http://lua-api.factorio.com/latest/Concepts.html#DifficultySettings DifficultySettings]. These fields do not use the special encapsulation method noted above.

{| class="wikitable"
! Type !!+ style='writing-mode:vertical-lr;vertical-align:bottom;font-size:90%' | GUI !! LUA key !! Description
|-
! byte[10] !! ✓ !! difficulty_settings !! Difficulty Settings
|-
| [[Data types#byte|byte]] || ✓ || recipe_difficulty || Recipe difficulty. 0 for Normal, 1 for Expensive.
|-
| [[Data types#byte|byte]] || ✓ || technology_difficulty || Technology difficulty. 0 for Normal, 1 for Expensive.
|-
| [[Data types#double|double]] || ✓ || technology_price_multiplier || Technology price multiplier.
|-
|}

Note: these values are typically defined using the constants at [http://lua-api.factorio.com/latest/defines.html#defines.difficulty_settings defines.difficulty_settings].

== Autoplace Control ==
See the page on [[World generator#Settings on the top row|world generation]] for more information on frequency, size, and richness.
{| class="wikitable"
! Type !! LUA key !! Description
|-
| [[Data types#byte|byte]]
| frequency
| Ore [[#Map_Gen_Size|frequency]].
|-
| [[Data types#byte|byte]]
| size
| Ore [[#Map_Gen_Size|size]].
|-
| [[Data types#byte|byte]]
| richness
| Ore [[#Map_Gen_Size|richness]].
|}

== Map Gen Size ==
These are the values used for the frequencies, sizes, and richnesses of ores, water, and the starting area size. None is a valid value for all three options.
{| class="wikitable"
| 0
| None / None /None
|-
| 1
| Very Low / Small / Poor
|-
| 2
| Low / Small / Poor
|-
| 3
| Normal / Medium / Regular
|-
| 4
| High / Big / Good
|-
| 5
| Very High / Big / Good
|}

Each of the values in a triplet (such as "low", "small", and "poor") are synonymous.

Burner mining drill

2020-04-29T04:04:28Z

Jon8RFC: /* Method 1 */ fix redirect

{{Languages}}
{{:Infobox:Burner mining drill}}

The '''burner mining drill''' is the first type of drill accessible to the player. It burns [[fuel]] to [[mining|mine]] the ore underneath the 2×2 area it is placed on.

It mines about 7 items per single unit of coal used to fuel it, producing 0.25 items/s for [[copper ore]], [[coal]], [[iron ore]] or [[stone]]. Burner miners create a lot of [[pollution]] per item.

Burner drills are usually used until the player has built an [[electric system|electrical network]], at which point the larger and faster [[electric mining drill]] becomes more useful, though they can still provide some use as extra drills that take up less space.

==Interface==
[[File:Interface_of_Burner-Mining-Drill.png|upright=2]]
# Amount of [[fuel]] in the mining drill
# Depletion of 1 unit of [[fuel]]
# Progress of mining
# Product
==Self-Sustaining Coal Mines==
Both methods require no electricity.
=== Method 1 ===
Two burner mining drills can refuel each other when placed next to each other on a coal deposit as long as they're facing each other. Each drill fuels the other and coal gradually accumulates in their [[stack]]s, so you have effectively a storage of 100 coal (2 stacks, 50 coal, one in each burner miner, together 100). You can do this also for 4 or any other even number of miners.

[[File:Early_coal_mining_1.png‎|200px]]

Note that it takes slightly less than 3 minutes for the mining drills to completely fill each other's fuel inventory. Once full, the drills will sit idle until the accumulated coal is removed. It's possible to extend that time by having the drills output their coal into a buffer [[Chests|chest]] rather than directly into another drill's fuel stack.

[[File:Early_coal_mining_1b.png‎|250px]]

=== Method 2 ===
This method can be used for any number of burner mining drills in a coal deposit. Place a burner mining drill, then place at least three [[transport belt]]s from the output in a mirrored "L" like shape so that the third belt has a gap between it and the miner. Fill the gap with a [[burner inserter]] in a way that the inserter can insert coal to the miner. When placing this array of entities opposite of each other, ensure that no two burner inserters are trying to take coal from the same piece of belt or one of them might run out of fuel.

[[File:Early_coal_mining_3.png‎|400x400px|upright=2]]

== History ==

{{history|0.18.0|
* Updated sound effects.}}

{{history|0.17.0|
* Mining speed for all ores except uranium is now 0.25/s.}}

{{history|0.8.1|
* Mining drill now ignores resources that can't be mined because of the higher hardness.}}

{{history|0.8.0|
* Player starts with one burner mining drill and one furnace in the freeplay.
* Increased mining speed of burner mining drill.}}

{{history|0.7.3|
* Shows area of effect when highlighted.
* Mining drill evenly mines from every tile in it's area.}}

{{history|0.7.0|
* Added support for modules to Electric mining drills.
* Mining drills deactivate when out of resources.}}

{{history|0.5.1|
* Show output arrows when alt mode is on.}}

{{history|0.5.0|
* New Graphics.}}

{{history|0.2.0|
* Shows count of available resources.}}

{{history|0.1.0|
* Introduced}}

==See also==
* [[Mining]]
* [[Coal]]

{{ProductionNav}}
{{C|Resource extraction}}

Utility science pack

2020-04-29T04:03:34Z

Jon8RFC: /* History */ fix redirect

{{Languages}}{{:Infobox:Utility science pack}}
The '''Utility science pack''' is one of three late-game [[science pack]]s, the other two being the [[Production science pack]], and the [[Space science pack]].

== Ratio ==
The following shows the minimum ratio of assemblers/machines and items required to produce utility science packs such that all number of assemblers/machines are whole numbers. Items per min is calculated using [[assembling machine 3]] with no [[module]]s or [[beacon]]s and all assemblers running at full speed. The crafting of some intermediate products are not shown (due to the assumption that these items are available in large quantities within the factory). This table was produced using normal recipe difficulty.

{| class="wikitable"
! Items/min
|-
|
{|
|-
|colspan="10"| {{Icon|Utility science pack|225}} using {{Icon|Assembling machine 3|21}}
|-
| ||colspan="10"| {{Icon|Flying robot frame|75}} using {{Icon|Assembling machine 3|20}}
|-
| || ||colspan="10"| {{Icon|Battery|150}} using {{Icon|Chemical plant|10}}
|-
| || || ||colspan="10"| {{Icon|Iron plate|150}}
|-
| || || ||colspan="10"| {{Icon|Copper plate|150}}
|-
| || || ||colspan="10"| {{Icon|Sulfuric acid|3000}}
|-
| || ||colspan="10"| {{Icon|Electric engine unit|75}} using {{Icon|Assembling machine 3|10}}
|-
| || || ||colspan="10"| {{Icon|Engine unit|75}} using {{Icon|Assembling machine 3|10}}
|-
| || || || ||colspan="10"| {{Icon|Pipe|150}}
|-
| || || || ||colspan="10"| {{Icon|Iron gear wheel|75}}
|-
| || || || ||colspan="10"| {{Icon|Steel plate|75}}
|-
| || || ||colspan="10"| {{Icon|Electronic circuit|150}}
|-
| || || ||colspan="10"| {{Icon|Lubricant|1125}}
|-
| || ||colspan="10"| {{Icon|Electronic circuit|225}}
|-
| || ||colspan="10"| {{Icon|Steel plate|75}}
|-
| ||colspan="10"| {{Icon|Low density structure|225}} using {{Icon|Assembling machine 3|60}}
|-
| || ||colspan="10"| {{Icon|Steel plate|450}}
|-
| || ||colspan="10"| {{Icon|Copper plate|4500}}
|-
| || ||colspan="10"| {{Icon|Plastic bar|1125}}
|-
| ||colspan="10"| {{Icon|Processing unit|150}}
|-
|style="width:40px;"|
|style="width:40px;"|
|style="width:40px;"|
|style="width:40px;"|
|style="width:40px;"|
||
|}
|}

== Raw Components ==
The total raw section counts items that can't be crafted by hand as raw ingredients. The volume of '''raw''' materials per pack is as follows:
{{Icon|Iron plate|33.3}}
{{Icon|Copper plate|49.8}}
{{Icon|Coal|3.8}}
{{Icon|Crude oil|115.7}}
{{Icon|Water|178.1}}

== History ==
{{history|0.17.0|
* Changed name from "High tech science pack" to "Utility science pack".
* Changed recipe to 21 [[Time]] + 1 [[Flying robot frame]] + 3 [[Low density structure]] + 2 [[Processing unit]] → 3 [[Utility science pack]]. (Previously 14 [[Time]] + 1 [[Battery]] + 30 [[Copper_cable|Copper wire]] + 3 [[Processing unit]] + 1 [[Speed module]] → 2 [[Utility science pack]].)
}}

{{history|0.15.0|
* Introduced.
}}

== See also ==
* [[Research]]
* [[Science pack]]
* [[Technologies]]

{{IntermediateNav}}
{{C|Science packs}}

Gate/ru

2020-04-29T03:46:29Z

Jon8RFC: fix redirect

{{Languages}}
{{:Infobox:Gate}}

'''Ворота''' представляют собой вариант стен, добавленных в Alpha 0.11.0 версии. Для [[Vehicle/Train|поездов]] существует отдельный вариант графики, который перекрывает дорожную дорогу. Так же ворота можно ставить рядом с друг другом, и они будут объединяться в одни большие ворота.

== Механика ==
Ворота открываются только для тех, кто состоит в одной той же группировке. Враги же должны уничтожить ворота, чтобы пройти дальше. Ворота имеют такие же показатели Здоровья/[[Damage|Сопротивление урону], как и у [[Wall/ru|стен]]

Существует несколько режимов работы ворот:
* Ворота открываются почти перед игроком, который не путешествует на [[Vehicle/ru|транспорте]], при его приближении.
* Ворота открываются в зависимости от скорости передвижение игрока, который едет на [[Vehicle/ru|транспорте]].
* Ворота открываются сильно заранее, когда сквозь них проходит [[Railway|поезд]], который [[Railway/Automated_transport|функционирует в автоматическом режиме]].

== Смотрите также ==
* [[Wall/ru|Стены]]
* [[Enemies/ru|Враги]]
* [[Defense/ru|Оборона]]
* [[Vehicle/ru|Транспорт]]

{{CombatNav}}
{{C|Defense}}

Turret

2020-04-29T03:42:10Z

Jon8RFC: correct grammar

{{Languages}}
{{Disambiguation}}

''Turret'' may refer to:

* {{imagelink|Gun turret}}
* {{imagelink|Laser turret}}
* {{imagelink|Flamethrower turret}}
* {{imagelink|Artillery turret}}

Although not a turret in the standard sense, [[Enemies#Worms|worms]] act as turrets in their method of attacking.

Turret

2020-04-29T03:41:16Z

Jon8RFC: Fix redirect

Transport belts/Physics

2019-11-07T12:45:45Z

Jon8RFC: /* Belt properties */ fix redirect

{{Languages}}
The [[belt transport system]] in Factorio is among the most detailed simulations in the game. Items in chests and other containers are stored simply as summed totals, and items on uninterrupted stretches of belts are [https://www.factorio.com/blog/post/fff-176 moved in aggregate] as an optimization, but in the end items on belts are simulated individually, especially when they get picked up or put down by inserters. This leads to some intricate behaviors, in particular when it comes to [[Inserters#Inserter_Throughput|inserter throughput]].

== Belt properties ==

* '''Density'''. How many items fit onto a certain length of belt, measured in items per [[Map_structure#Tile|tile]] per belt lane. This is 4 on a straight belt, regardless of the type of item and type of belt. The item density on belts can be different from what they take up when just dropped on the ground (using the Z key).

* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles per second. Note that internally it is measured in positions (1/256 tile) per tick (1/60 sec). More on that below. The speed of a basic [[transport belt]] is 1.875 tiles per [[Time#Seconds|game-second]]. [[Fast transport belt]] is twice as fast, and [[express transport belt]] is three times as fast.

* '''Throughput'''. How many items per second that are moved from one tile to the next. That is density (items per tile) multiplied by speed (tiles per second), e.g. for a basic belt it is 4 * 1.875 = 7.5 items per second, for one belt lane. For both lanes it is doubled, i.e. 15 items per second.

* '''Compression'''. If there is no empty space between items on the belt it is called ''fully compressed'', otherwise its compression is only partial and it does not have optimal throughput. Entities that put items onto belts - [[inserters]], [[splitters]], other belts coming from the side, mining drills, etc - make room for their item by [https://forums.factorio.com/viewtopic.php?f=3&t=57993 enlarging a small gap] until it is exactly big enough for the item. That means belts naturally become fully compressed before items start to back up.

* '''Lanes'''. Belts have two parallel lanes, and the density and speed of each lane is constant and independent of the other one, regardless of twists and turns. So items in the inner lane of a turn exit it before those in the outer lane, since their speeds are equal and the inner lane is shorter than the outer one.

== Belt speeds ==

Given the values above we can calculate the speed and throughput of the three types of belts. Measurements confirm these values.

{| class="wikitable"
! rowspan=2 | Belt type || colspan=2 | Speed || colspan=4 | Throughput
|-
! Factor || Tiles/sec || Single lane, items/sec || Single lane, items/min || Both lanes, items/sec || Both lanes, items/min
|- align="center"
| align="left" | {{Imagelink|Transport belt|Transport belt}} || 1 || 1.875 || 7.5 || 450 || 15 || 900
|- align="center"
| align="left" | {{Imagelink|Fast transport belt|Fast transport belt}} || 2 || 3.75 || 15 || 900 || 30 || 1800
|- align="center"
| align="left" | {{Imagelink|Express transport belt|Express transport belt}} || 3 || 5.625 || 22.5 || 1350 || 45 || 2700
|}

== Items on belts ==

As mentioned earlier, items take space on belts in terms of density and compression. However, every item on a belt is logically ''on'' exactly one belt tile at any moment in time.

For example, even though in a screenshot it might look like an item is halfway out from one tile and halfway onto the next, it will be accounted to exactly one of the two tiles:
* If you stop the belt tile the item is on, it stops; else it continues moving - there are no in-between states.
* If you connect the two belt tiles to a circuit network and get them to [[Belt_transport_system#Circuit_network|report statistics]] about the items they carry, you will see the item being accounted to exactly one of them.
* An inserter can only pick up items that are logically on the tile in front of it, not items butting in from the neighboring tiles.

In this sense it is useful to think of items as points with a certain minimum distance between them, rather than things with an area lying next to each other. For belt calculations and circuit networks involving belts it doesn't really matter where those "center points" are within the graphic of the item, but they appear to be in the middle:

[[Image:Belts-with-one-tick-offsets.png|center]]

In the image above the belts have been started at 1 tick offsets, then all the top row tiles have been stopped at once, causing the front-most stopped items to poke out by varying amounts. The items on the leftmost belt are almost halfway into the next tile, which means their center points are the closest to the edge of the upper stopped tile.

Below is a schematic example showing some items moving over two straight [[fast transport belt]] tiles and what their read signals would be at each tick. Their center points are marked with <code>*</code>. (The space between belt tile 1 and 2 is only for visualisation - in the game there are no such gaps between tiles.)

<pre>
Tick Belt tile 1 Belt tile 2 Read belt tile 1 Read belt tile 2
|------------------------------| |------------------------------| Pulse Hold Pulse Hold
0 <---*--> <---*--> <---*-- ><---*--> <---*--> 0 3 0 2
1 <---*--> <---*--> <---* --><---*--> <---*--> 0 3 0 2
2 <---*--> <---*--> <-- -*--><---*--> <---*-- 0 2 1 3
3 <---*--> <---*--> < ---*--><---*--> <---* 0 2 0 3
4 -> <---*--> <---*--> <---*--><---*--> <-- 0 2 0 2
5 *--> <---*--> <---*- -> <---*--><---*--> < 1 3 0 2
6 --*--> <---*--> <--- *--> <---*--><---*--> 0 2 1 3
7 <---*--> <---*--> <- --*--> <---*--><---*--> 0 2 0 3
8 <---*--> <---*--> <---*--> <---*--><---*--> 0 2 0 3
</pre>

== Belt positions and lengths ==

[https://forums.factorio.com/viewtopic.php?f=5&t=70055 Careful measurement] shows that the outer lane of a turn is exactly 1.15234375 times longer than a straight belt, or 295/256 in fractional format. That means each straight belt tile has 256 ''positions'' an item can be in, even though measuring the position with that precision can only be done indirectly.

Here are the speeds and lengths of the various types of belt tiles in terms of these positions:

{| class="wikitable"
! colspan=2 | What || Number of positions
|-
| colspan=2 | Basic [[transport belt]] speed, per tick || align="center" | 8
|-
| colspan=2 | [[Fast transport belt]] speed, per tick || align="center" | 16
|-
| colspan=2 | [[Express transport belt]] speed, per tick || align="center" | 24
|-
| colspan=2 | Length of an item on a belt (of any speed) || align="center" | 64
|-
| colspan=2 | Length of one lane of a straight belt tile, underground belt, and splitter || align="center" | 256
|-
| colspan=2 | Length of the inner lane of a turn || align="center" | 106
|-
| colspan=2 | Length of the outer lane of a turn || align="center" | 295
|-
| style="border-right: 0px" | Length travelled by an item sideloaded late on a straight belt or underground exit
| style="border-left: 0px" | [[Image:Sideload-late.gif]] || align="center" | 68
|-
| style="border-right: 0px" | Length travelled by an item sideloaded early on a straight belt or underground entrance
| style="border-left: 0px" | [[Image:Sideload-early.gif]] || align="center" | 188
|}

For example, given the figures above, we can deduce the speed of a basic belt:

: 8 (positions per tick) / 256 (positions per straight belt tile) * 60 (ticks per second) = 1.875 tiles per second

Its throughput per belt lane is:

: 8 (positions per tick) / 64 (positions per item) * 60 (ticks per second) = 7.5 items per second

== See also ==
* [[Belt transport system]]
* Jan 04 FFF #276: [https://www.factorio.com/blog/post/fff-276 Belt item spacing & Script rendering]
* Feb 03 FFF #176: [https://www.factorio.com/blog/post/fff-176 Belts optimization for 0.15]
* [https://forums.factorio.com/viewtopic.php?f=5&t=70055 Accurate belt segment measurements] (discusses 0.17)

{{C|Belt transport system}}

Map generator

2019-11-07T12:44:32Z

Jon8RFC: fix redirect

{{Languages}}
[[File:Default_123456789.png|thumb|right|An example how the world generator might create a new map: Default settings with map seed 123456789]]
World generation is the procedure by which the in game landscape is generated. In short: a number of settings, editable at the start of a new world, define what that world will look like. This can dramatically alter gameplay — a new player is advised to start with the default settings before deciding to change their world.
__TOC__{{Clear}}
== Map generation presets ==
[[File:MapGeneratorOverview.png|thumb|right|400px|Overview of the map generation screen]]
A preset may be chosen in the top left dropdown instead of manually configuring the generation.
=== Default ===
Normal settings. The recommended way to play Factorio.

All sliders are set to the center position. Map height and width is unlimited, peaceful mode is disabled.

All other settings are set to their defaults:
{| class="wikitable"
|-
! Enemy expansion !! Default !! Evolution !! Default
|-
| Enabled || Yes || Enabled || Yes
|-
| Maximum expansion distance || 7 || Time factor || 40
|-
| Minimum group size || 5 || Destroy factor || 200
|-
| Maximum group size || 20 || Pollution factor || 9
|-
| Minimum cooldown (Minutes) || 4
|-
| Maximum cooldown (Minutes) || 60
|-
|}

{| class="wikitable"
|-
! Pollution !! Default !! Recipes/Technology !! Default
|-
| Enabled || Yes || Recipe difficulty || Normal
|-
| Absorption modifier || 100% || Technology difficulty || Normal
|-
| Attack cost modifier || 100% || Technology price multiplier || 1
|-
| Minimum damage to trees || 60 || Research queue availability || After the game is finished
|-
| Absorbed per damaged tree || 10 ||
|-
| Diffusion ratio || 2% ||
|-
|}

=== Rich resources ===
Resources patches have a larger richness, so you don't have to expand far.

Difference from default: Resources have 200% richness instead of 100%.

=== Marathon ===
Recipes and technologies are more expensive.

Difference from default: Expensive recipes and technology, technology price multiplier 4.

=== Death world ===
Biters are more dangerous and evolve faster.

Difference from default: 200% enemy base frequency and 200% enemy base size, 75% starting area size, enemy evolution time factor is set to 200, pollution factor is set to 12. The pollution absorption modifier is set to 50% instead of 100%, same goes for the attack cost modifier.

=== Death world marathon ===
Recipes and technologies are expensive and biters are dangerous and plentiful. Only select this if you are a Factorio veteran.

Combines "Marathon" and "Death world" with some additional changes: Enemy evolution time factor is set to 150, pollution factor is set to 10. Attack cost modifier is set to 80% instead of 100% (50% for death world).

=== Rail world ===
Resource patches are large and spread far apart, to encourage train systems. Biters won't create any new bases or re-expand into cleared territory.

Difference from default: All resources are set to 33% frequency and 300% size. Water is set to 200% scale and 150% coverage. The evolution time factor is set to 20 from 40 and enemy expansion is disabled.

=== Ribbon world ===
The map height is limited to only 128 tiles, which introduces a range of challenges and interesting situations.

Difference from default: Map height is limited to 128. All resources are set to 300% frequency, 50% size and 200% richness. Water is set to 25% coverage and size. Starting area size is increased to 300%.

=== Island ===
A large island in an endless ocean.

Difference from default: Terrain map type is set to island.

== Manual configuration ==
It is possible experiment with different settings by opening the map preview, changing the settings and observing their effects. This makes it possible to directly observe what exactly particular settings modify in the world, beyond the textual descriptions provided on this page.

The seed is the starting value for the random number generator that Factorio uses for generating the world based on the generation settings. This means that even with the same generation settings, the world can look very different depending on the seed.

All resources and terrain features can be disabled by unchecking the checkbox in front of them.

=== Resources ===
Frequency determines the number of resource patches in a given area. It does not affect resource patch size or richness. A setting of 200% frequency that means roughly double the patches can be found in a given area.

The size setting adjusts the size of the resource patches. Setting the slider to 200% means the surface area of the patch is doubled.

Richness defines the yield of every ore tile and every oil field. If richness is set to 200%, each ore tile and oil field contains about double the amount of ore/oil. Outside of this, resource patch richness increases by distance.

=== Terrain ===
Setting the map type to island generates a single island around the spawn point and endless ocean beyond that. The normal map type generates endless terrain.

Water scale changes how much space there is between lakes. The smaller the scale, the swampier the terrain. Higher scale leads to bigger oceans separated by bigger landmasses. Water coverage influences the overall amount of water. Reducing it generates small lakes, increasing it generates large oceans.

The settings for trees behave in the same way. Higher scale increases the distance between forests while lower scale reduces it. High tree coverage allows to completely cover the world in trees, and low coverage nearly removes them from the world.

Cliff frequency influences how many cliff lines there are in the world. Higher frequency means more cliffs, lower frequency reduces their number. The continuity setting changes how long and unbroken the cliff lines are. Low continuity leads to very short lines, high continuity to long, nearly unbroken lines of cliffs.

The moisture settings control the distribution of grass versus desert. Higher bias generates more grass, lower bias generates more desert. Higher scale increases the size of the grass/desert areas, low scale leads to small grass and desert patches.

The terrain type setting controls the distribution of red desert versus sand. Higher bias generates more red desert, lower bias generates more sand. Higher scale increases the size of the red desert/sand areas, low scale leads to small red desert and sand patches.

=== Enemy ===
[[File:MapGeneratorEnemy.png|thumb|right|400px|The enemy tab]]
Frequency determines the number of enemy bases in a given area. It does not affect enemy base size. A setting of 200% frequency that means roughly double the enemy bases can be found in a given area.

The size setting adjusts the size of enemy bases. Setting the slider to 200% means the surface area covered by the enemy bases is doubled.

When peaceful mode is turned on, the [[enemies]] don't begin fights, only responding if the player hits them. Additionally, when a map is in peaceful mode, the enemies will not [[Enemies#Expansions|expand]].

The starting area is the an almost circular radius around the spawn point that does not contain enemy bases. Increasing its size pushes the bases further out, decreasing its size generates enemy bases closer to the spawn point. The size setting does not have any other effects.

[[Enemies#Expansions|Enemy expansion]] can be enabled/disabled and further adjusted using the below settings.

{| class="wikitable"
|-
! Enemy expansion setting !! Description
|-
| Maximum expansion distance || The maximum distance enemies will look to expand from other enemy bases.
|-
| Minimum group size || The minimum size of an enemy expansion party modified by the current evolution level.
|-
| Maximum group size || The maximum size of an enemy expansion party modified by the current evolution level.
|-
| Minimum cooldown (Minutes) || The minimum time between enemy expansions being sent out.
|-
| Maximum cooldown (Minutes) || The maximum time between enemy expansions being sent out.
|-
|}

[[Enemies#Evolution|Evolution]] can be enabled/disabled and further adjusted using the below settings.

{| class="wikitable"
|-
! Evolution setting !! Description
|-
| Time factor || Controls how fast evolution increases over time.
|-
| Destroy factor || Controls how fast evolution increases due to destroying enemy spawners.
|-
| Pollution factor || Controls how fast evolution increases due to producing pollution.
|-
|}

=== Advanced ===

The [[Replay system|replay]] can record all the actions that the player(s) perform during the game, so that they can later be played back as essentially a timelapse of the save file.

The map width and height allows to generate maps with finite resources and area. It is possible to limit generation in only direction, alike the [[#Ribbon world|ribbon world]].

The difficulty settings allow to change the [[Crafting#Recipe difficulties|recipe]]/technology difficulty and multiply the [[research|technology cost]]. Currently, setting the technology difficulty does not have an effect in vanilla. Furthermore, it can be controlled when the research queue is available: From the start, after launching a [[rocket silo|rocket]] or never.

[[Pollution]] can be enabled/disabled and further adjusted using the below settings.

{| class="wikitable"
|-
! Pollution setting !! Description
|-
| Absorption modifier || Modifier of how much pollution is absorbed by trees and tiles.
|-
| Attack cost modifier || Modifier of how much pollution is absorbed by enemy attacks.
|-
| Minimum damage to trees || Trees have 4 different stages of the progression towards being destroyed by pollution. Any pollution above this amount starts the process of moving a tree towards a more damaged stage.
|-
| Absorbed per damaged tree || Trees have 4 different stages of the progression towards being destroyed by pollution. This value specifies how much pollution is absorbed when moving to a more damaged stage.
|-
| Diffusion ratio || The amount of pollution diffused into neighboring chunks per second.
|-
|}

=== Map exchange string ===

A map exchange string generally looks like this:

>>>eNp1UTGIE0EU/WMu3F4EUUjhgR4prrDZJTlFJRyZURAR0d7Oz
WYiA5udOLsLnhaX4kptxEaraz3hOgu7wIEoKBxa2UVsLFROBC0U4
p+dnWSNdw/+583/f97/fwbgGLhAADGgAEPqzAXSD/HI8JRZJZD9P
leuVNyGtC0EKu1wV4qwGK3wiPfW3LYfc6NozBFKRv8qMFaOExnlE
WDPtrZoOVGcx3igxgb0cKr8SKQ9c1eL5aOSGIcebCxlNl6H2nisD
dkIC0YAtpIQjOWYOx7IKFEydGOeJCK61fTTO8228OMFt+416hqn9
ivpKn475VGw1uylYSL6oeDKqXtnNc6dnL3RkyJOUsUzZccKuweW7
ave8E5nKAeh6HYBahfQLuotCJB71e3LH+8+osTs5bGc7OWRYdtGr
lhynR2YWrbkTEHHdP9RIKZpgi3yKodNiUlu6CQhD74+3/z1crdF/
jz9/u5a+yYljUvVb3sr2y1MzusVDk3ck8caL+wqYDVHNE99oOTtG
40vlJT1jap27Dy64dUSkKNHkG3eR1c7AXa0lpWpMtLN8NNu8smS9
3R2D3yIVS2+pN0r7bKGk8lITm8wk1icZvHqChTbd6bLvbYddwqtZ
2b4/w+KK8xElgsPX9F9OhP3uTQZAl9wd96e2DorwRT4wTu/vYd/A
dl73Kk=<<<

The map exchange string can be used to share all map generation settings between different players. The player can paste the string (using {{Keybinding|ctrl|V}}) into the map exchange string field and the game will set the generation settings to the settings saved in the string, resulting in a complete copy of the map when generated.

The map exchange string can be retrieved from save files by going into the load game screen, selecting the desired map, clicking the map exchange string button in the upper right corner and copying the string from the window that pops up.

For a technical description of the map exchange string, see [[map exchange string format]].

== Mechanics ==

=== Starting area ===

There is a second internal starting area that is completely separate from the starting area that can be changed in the enemy settings tab. This starting area always has a constant size and affects the spawning of resources, cliffs and water directly at the spawn. The map generation logic makes sure that there is always at least one path of [[coal]], [[iron ore]], [[copper ore]], and [[stone]] each. Furthermore, there is always a lake in the starting area, even when water is turned off, and there are never any cliffs there. [[Uranium ore]] and [[crude oil]] do not spawn in the starting area. The richness of the ore patches is slightly influenced by the frequency setting.[https://forums.factorio.com/viewtopic.php?p=432592#p432592]

=== Chunks ===

A map is endless by default, though its size can be limited by height and width — see above. Because it is technically endless, the whole map is not generated from the start. Instead, a new [[Map_structure#Chunk|chunk]] of the map is generated only when needed, similar to other procedurally generated world games.

==== Invisible chunks (fog of war) ====

Outside of the visible chunk area, an invisible area of about 3 chunks wide is generated as a preloading mechanism. Enemies may be located inside these invisible chunks and can attack the player from there, while [[artillery turret]]s and [[artillery wagon|wagon]]s may automatically shoot enemy bases in these chunks if they are within their automatic range. Invisible chunks are also generated if pollution is generated heavily; the game generates (invisible) chunks as it needs to spread the pollution into the area.

==== Charting (removing fog of war) ====

As long as a chunk is invisible, the part of the players map stays black. This changes when a chunk is [[Radar#Charting|charted]], which means when it is "touched" by a radar. This can be either the player's internal radar, which is always available and continually charts chunks around the player, or the [[radar]] entity. If a far-away and thus ungenerated chunk is charted, it will be generated, together with the above-mentioned invisible 3 chunk radius of map around it.

==== Maximum map size and used memory ====

The map size is limited to 2,000 x 2,000 kilometers; internally, this is a square 2,000,000 tiles on a side, with an area of 4,000,000,000,000 (4 trillion) square tiles (assuming 1 tile = 1 meter on a side yields 2,000 x 2,000 km = 4 million square km). In real-world terms, this is between the sizes of India and Australia (or about 40% the area of the United States, or over 10 times the area of Germany). It would take around 200 [[Time#Seconds|game-minutes]] (ca 3.3 hours real time) to reach that border from the center when riding a [[locomotive|train]] fueled with [[rocket fuel|rocket]] or [[nuclear fuel]]. This makes the world essentially endless for practical purposes. The generated chunks are fully mapped and stored in the player's RAM, which is the practical limiting factor of exploration.

Because chunks are only generated in and close around the area revealed by radar, it is possible to reach that border without overloading your computer, as the size of the map in computer memory is dependent only on chunks actually generated. If only a narrow stripe of land is explored to far away, this remains manageable.

== History ==

{{History|0.17.44|
* The resource frequency slider in the map generator settings has a smaller influence over the amount of ore in the starting area patches.
}}

{{History|0.17.0|
* Resource generation changed significantly:
** The starting area contains only iron, copper, coal and stone, in very predictable amounts. Uranium and oil are excluded from the starting area.
** Resource generation settings now have a much more dramatic effect. Increased the number of steps for each setting.
** Ore patches are slightly less frequent but richer.
** There will be a more balanced amount of resources within a large enough region.
** Many other small tweaks.
* Biter generation changed significantly:
** Biter richness slider removed, biter placement is only configured by size and frequency settings.
** Biter generation settings now have a much more dramatic effect. Increased the number of steps for each setting.
** Biter bases will increase in size, frequency and number of worms depending on the distance from player spawn.
** Worm size increases depending on the distance from player spawn.
** Small biter bases are now closer to the player spawn.
** At large distances from player spawn, biter base frequency is lower than before but biter bases are larger.
** Other small tweaks.
* Terrain generation changed significantly:
** Water is generated as large lakes instead of swamps.
** Tile generation improved. Tile placement respects biomes better.
** More predictable cliff placement.
** Better controls in the map generator GUI for water, tiles and cliffs.
* New map terrain type selectable: Island. Launch the rocket with only a limited amount of resources available on the map.
}}

{{History|0.16.0|
* Added cliffs.
* New terrains and new terrain generation.
* Trees can now be configured in the generate-map GUI.
* Terrain can be configured in the generate map GUI.
* Biters scale less with distance and there are generally less biters.
* No uranium as a starting resource also no uranium is ever generated near the starting area, you need to go look for it.
}}

{{History|0.15.0|
* Extended map generator settings to include an advanced section.
* Added map generator presets.
* The map seed is used to generate unique maps instead of just shifting the starting position.
}}

{{History|0.13.7|
* Map size is now limited to 2000 km by 2000 km with a black bar rather than crashing when reaching this distance.
}}

{{History|0.13.0|
* Map generator algorithm changed, further resource field now have greater richness.
}}

== See also ==

* [https://forums.factorio.com/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [https://forums.factorio.com/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)

Accumulator

2019-11-07T12:43:07Z

Jon8RFC: /* Notes */ fix redirect

{{Languages}}{{:Infobox:Accumulator}}
The '''Accumulator''' stores a limited amount of energy when available production exceeds demand, and releases it in the opposite case. The accumulator can store up to 5 MJ of energy. Its maximum charge/discharge rate is 300 kW. If connected to a [[circuit network]], an accumulator will output its level of charge, as an integer from 0 to 100, to a specified signal.

== Notes ==
* 5MJ of stored energy takes approximately 17s to fully charge/discharge at the maximum rate of 300kW. Read [[Time#Seconds]] for further time related calculations.
* It takes 20 accumulators (100MJ) to maintain 1MW through the night, because the accumulators don't immediately start discharging at the beginning of dusk, see the graph in [https://forums.factorio.com/viewtopic.php?f=5&t=5594 this post.]
* When discharged above maximum speed by multiple unconnected poles, energy will not be distributed equally (some loads may get 100% demand, others 0%)
* May be used to provide a limited amount of power (multiples of maximum charge rate) to a section of the grid.
* Produces light when charging and discharging.
* Can act as an emergency backup for the factory in case of blackout, until main power supply is restored.
* Can be used to power the base at night if it relies heavily on [[solar panel]]s.
* Can act to satisfy surging demands of certain loads. If the power usage of one device exceeds production for a few seconds or so, the accumulator can provide power to the grid until said device shuts down or requires a lesser power requirement.

== Other uses ==
Note that if throughput should not be limited, a [[power switch]] can be used instead.

=== Isolation of Power Networks ===

[[Electric system#Storage|Accumulator]]s can be used to isolate two separate power networks, which has a number of uses. Since accumulators have a lower delivery priority than any other entity, this guarantees that they only receive energy when you have enough left over after powering all other entities in a network. At the same time, accumulators can also be used to deliver energy in another electrical network, and can charge and discharge at the same time. Consider the following example:

[[File:Accumulator_Network_Isolation.png|thumb|left|550px|Example of accumulators sharing two separate networks. ''(Click to enlarge)'']]
{{clear}}
The two power networks A and B are not directly connected to each other: They are connected only through the accumulators, which are shared by both networks. This is accomplished by setting up electric poles for each network connected to the accumulators, then ensuring the sets of poles are not connected to each other (which can be done by crafting a copper wire then dragging it between two connected poles to sever the connection, exactly as is done for disconnecting circuit wires).

In the above example:

* The accumulators will only charge if extra power is being produced by network A or B.
* The accumulators will discharge as needed into either network if one is not producing enough power.
* Since the maximum input/output rate of an accumulator is 300 kW, power flow between the two networks will be limited to 300 kW times the number of accumulators (1.5 MW in the example).
* Note that this isolation is bidirectional: Either network can charge the accumulators, and the accumulators can discharge into either network.

This technique can be used whenever this type of isolation is desired.

==== Reduction of Energy Consumption in Critical Situations ====

In particular, one good use for the above technique is to limit electricity consumption in low power situations by isolating non-critical parts of your factory (such as [[Radar]], [[Lab]]s, [[Electric furnace]]s, [[Electric mining drill|electric miner]]s, [[Beacon]]s, etc.) from critical parts (such as lasers, ammo production, or whatever your priorities are).

To do this, place your main generators and critical components on one network and place your non-critical components on another network, isolating the two as above. Now, two things will happen:

* Power will ''only'' flow to the non-critical network when you are generating a surplus on the main network, and
* The rate will always be limited to 300 kW per accumulator.

Because the accumulators will only receive power if you have a surplus on the main network, this will in effect deactivate the low-priority network when electricity is in short supply. This will also limit power consumption of the low priority network if its usage becomes high, for example if you have two factories on a low priority network and usually only one of them runs at a time, if both happen to run they won't consume more than the total limit, they'll just slow down.

Essentially you are saying "only deliver power to these systems if I have enough to spare, and even then don't exceed this delivery rate".

In general this is a technique which works well when you've just researched accumulators and solar panels, but don't have enough resources to build big solar farms and accumulator farms yet.

== History ==

{{history|0.13.3|
* Reduced collision box of [[big electric pole]] to allow squeezing between it and an accumulator.}}

{{history|0.13.0|
* Now connectible to the [[circuit network]].}}

{{history|0.12.0|
* Heavy optimisations by merging them into groups.}}

{{history|0.11.0|
* Drastically slowed crafting to 10 secs.}}

{{history|0.7.1|
* Capacity doubled, increase I/O to 300 watts.}}

{{history|0.4.1|
* Added charging animation.}}

{{history|0.4.0|
* Introduced}}

== See also ==
* [[Electric system]]
* [[Solar panel]]
* [[Power production]]
* [[Game-day]]

{{ProductionNav}}
{{C|Energy}}

Enemies

2019-11-07T12:42:19Z

Jon8RFC: /* Methods of increasing */ fix redirect

{{Languages}}
'''Enemies''' (also commonly called '''biters''') are creatures that want to harm the [[player]]. They are the native inhabitants of the extraterrestrial world in the form of arthropods living in organic nests, coexisting with each other peacefully. They are encountered in three species: Biters, spitters and worms. The species are further distinguished in four stages of growth, and thus strength. Enemies and nests show up on the map as red dots. Much like the player, enemies can slowly regain lost health.

== Achievements ==
Enemies are directly connected to the following achievements:
{{Achievement|it-stinks-and-they-dont-like-it}}
{{Achievement|steamrolled}}

==Creatures==
===Biters===
Biters are one of two main antagonists in the game. They come in four sizes: small, medium, big and behemoth. In the beginning of a game, there will only be the small ones. With increasing [[pollution]], they will become bigger, related to the enemy's [[#Evolution|evolution]]. As common sense may suggest, their method of attack is a straightforward charge to "bite" things.

{| class="wikitable"
|-
! Picture !! Name !! Info
|-
| [[File:small_biter.png|center]] || Small Biter
| Weakest of biters, can be easily killed with a pistol.
* Health: 15
* Damage: 7 Physical
* Attack speed: 1.71/s
* Speed: 43.2km/h
* Range: 1
* Pollution to join attack: 4
|-
| [[File:medium_biter.png|center]] || Medium Biter
| Stronger and slightly faster than the small biter. Can pose a problem for and even kill weaker players.
* Health: 75
* Damage: 15 Physical
* Attack speed: 1.71/s
* Speed: 51.8km/h
* Range: 1
* Pollution to join attack: 20

[[Damage#Resistance|Resistances]]:
*Explosion: 0/10%
*Physical: 4/10%
|-
| [[File:big_biter.png|center]] || Big Biter
| Dangerous, resistant to small arms. Can attack through walls, hitting objects directly behind them.
* Health: 375
* Damage: 30 Physical
* Attack speed: 1.71/s
* Speed: 49.7km/h
* Range: 2
* Pollution to join attack: 80

Resistances:
*Explosion: 0/10%
*Physical: 8/10%
|-
| [[File:behemoth_biter.png|center]] || Behemoth Biter
| Extremely durable and nearly immune to small arms, except for the strongest ordnance. Can attack through walls, hitting objects directly behind them.
* Health: 3000
* Damage: 90 Physical
* Attack speed: 1.2/s
* Speed: 64.8km/h
* Range: 2
* Pollution to join attack: 400

Resistances:
*Explosion: 12/10%
*Physical: 12/10%

|}

===Spitters===
'''Spitters''' are much like [[Enemies#Biters|biters]] and only appear slightly later on in the game as the evolution factor increases. Their main difference from biters is their ranged attack. Using predictive aiming, they spit a stream of acid at enemies which leaves behind a puddle of acid where it hits the ground. Due to the spitters' predictive aiming, the acid stream can be dodged by suddenly changing walking directions or standing still.[https://factorio.com/blog/post/fff-279] Both the stream and the puddle of acid deal damage of time and slow down players and vehicles. Most entities of the game have a much lower resistance to acid than other damage types (including [[turret]]s and [[armor]]), so spitters are effectively more potent against the player and his factories. Their behaviour and size classification are the same as with biters, but their health is universally lower and they are resistant exclusively against explosives, with no physical resistance.

{| class="wikitable"
|-
! Picture !! Name !! Info
|-
| [[File:small_spitter.png|center]] || Small Spitter
| Weakest of spitters. Easy to kill with any weapon, but attacks at range.
* Health: 10
* Damage: 12 Acid
* Attack speed: 0.6/s
* Area of effect size: 1
* Speed: 40.0km/h
* Range: 13
* Pollution to join attack: 4
|-
| [[File:medium_spitter.png|center]] || Medium Spitter
| Stronger and slower than the smaller version. Can pose a problem for and even kill weaker players.
* Health: 50
* Damage: 24 Acid
* Attack speed: 0.6 /s
* Area of effect size: 1.25
* Speed: 35.6km/h
* Range: 14
* Pollution to join attack: 12

Resistances:
*Explosion: 0/10%
|-
| [[File:big_spitter.png|center]] || Big Spitter
| An even bulkier spitter and so can take more damage.
* Health: 200
* Damage: 36 Acid
* Attack speed: 0.6/s
* Area of effect size: 1.35
* Speed: 32.4km/h
* Range: 15
* Pollution to join attack: 30

Resistances:
*Explosion: 0/15%
|-
| [[File:behemoth_spitter.png|center]] || Behemoth Spitter
| The bulkiest of the spitters and so can take even more damage.
* Health: 1500
* Damage: 60 Acid
* Attack speed: 0.6/s
* Area of effect size: 1.75
* Speed: 32.4km/h
* Range: 16
* Pollution to join attack: 200

Resistances:
*Explosion: 0/30%
|}

===Worms===

The Worms are natural allies of biters and spitters and will attack the player if they get close enough with an attack similar to spitters'. They act like static [[turret]]s and will not follow attackers. They rely on high damage, great range and splash damage to keep the player away from the worms and the nests they protect, but either one of these advantages can be overcome. Unlike other enemies, they are also highly resistant to fire. They will spit acid at the player, which can also leave acidic puddles on the ground that can still damage players and vehicles, as well as slow them both down and leave a brief acidic, damaging effect for a few seconds. However, placed buildings and tiles are unaffected by the acid puddles, but still take damage normally by the acid projectile.

Worms come in 4 sizes, their power increasing with size. Like biters and spitters, behemoth, big and medium worms spawning is influenced by the evolution factor. Worms are only created during enemy expansion when a certain evolution factor requirement is fulfilled. This is 0.3 for the medium worm, 0.5 for the big worm and 0.9 for the behemoth worm. Below these evolution factors, worms can only be created by the map generation. In map generation, the game restricts higher tier worms behind the distance from the starting point. The further away the player goes from the starting area, the stronger the worms become.

{| class="wikitable"
|-
! Picture !! Name !! Description
|-
| [[File:Small worm.png|center]] || Small Worm
| A weak worm. It is still capable of killing the player unless it is targeted as priority.
* Health: 200
* Damage: 36 Acid
* Attack speed: 15/s
* Area of effect size: 1.4
* Range: 25
|-
| [[File:Medium worm.png|center]] || Medium Worm
| Medium worms are dangerous to even more advanced players. They should be handled with care.
* Health: 400
* Damage: 48 Acid
* Attack speed: 15/s
* Area of effect size: 1.55
* Range: 30

Resistances:
*Explosion: 5/15%
*Fire: 2/50%
*Physical: 5/0%
|-
| [[File:Big worm.png|center]] || Big Worm
| Big worms are not as much more dangerous as resilient. They are almost immune to common gunfire of any sort.
* Health: 750
* Damage: 72 Acid
* Attack speed: 15/s
* Area of effect size: 1.75
* Range: 38

Resistances:
*Explosion: 10/30%
*Fire: 3/70%
*Physical: 10/0%
|-
| [[File:Behemoth worm.png|center]] || Behemoth Worm
| Behemoth worms are the most dangerous of worms. They are just as resilient as Big worms, with much greater range.
* Health: 750
* Damage: 96 Acid
* Attack speed: 15/s
* Area of effect size: 2
* Range: 48

Resistances:
*Acid: 0/100%
*Explosion: 10/30%
*Fire: 3/70%
*Physical: 10/0%
|}

{| class="wikitable"
|-
! Picture !! Description
|-
| [[File:worm.gif]] || A worm's attack animation.
|-
|}

==Nests==

The spawn points of biters and spitters. While nests themselves are generally defenseless, the enemies they release over time effectively serve as a form of guards to distract the player and any nearby turrets, and are often accompanied by worms. Nests exposed to pollution will use it to send enemies to join attacks. Enemies not engaged in combat may seek out the nearest nest for protection.

The nests are highly resistant to fire and otherwise generally more resilient than a medium worm.

{| class="wikitable"
|-
! Picture !! Name !! Description
|-
| [[File:biter_nest.png]] || Biter's nest
|
* Health: 350

Resistances:
*Explosion: 5/15%
*Fire: 3/60%
*Physical: 2/15%
|-
| [[File:spitter_nest.png]] || Spitter's nest
|
* Health: 350

Resistances:
*Explosion: 5/15%
*Fire: 3/60%
*Physical: 2/15%
|}

=== Expansions ===
Every 4-60 minutes, a group of 5-20 biters/spitters will leave their base to create a new base which will consist of as many worms/nests as there are members in the group. This group will search for a suitable spot that's 3-7 chunks away from existing bases. The interval between enemy expansions is global, and the higher enemy evolution, the shorter the interval is on average. Furthermore, with higher evolution, the groups are bigger on average.

Once they have found a suitable spot, each biter/spitter in the group dies and forms a new nest or worm. There is a delay between each member sacrificing itself for to create a worm/nest, so creating the new base from the expansion group can take quite a long time, depending on the group size. Medium worms are only formed if the current evolution is higher than 0.3, big worms only if the current evolution is higher than 0.5 and behemoth worms are only formed if current evolution is higher than 0.9. The game randomly chooses whether to form a new biter nest, spitter nest, small worm, or bigger worm if the evolution factor is high enough. [https://gist.github.com/Bilka2/aa88490c23124a6f214c02c73a368aa7]

==Defense==
Nests spawn biters and spitters "for free". However, biters and spitters will only aggressively engage the player's factory if the pollution cloud of the factory reaches a nest because pollution is consumed to send biters or spitters to join the next attack. Every 1 to 10 minutes (random) the mustered biters launch an attack. If not all biters have arrived at the rendezvous point by that time, they will wait up to an additional 2 minutes for stragglers. The attack then proceeds to their target over the shortest path possible, accounting for terrain, but not for player entities that could pose an obstacle (like [[wall]]s).

If there is a clear path somewhere around those obstacles, the biters will attempt to go around. If there is no clear passage or a clear passage would mean deviating too far from the original course, the biters will attack whatever is in their way to go through. This can be exploited to an extent; creating mazes at regular intervals along a barrier can direct the biters through a gauntlet not dissimilar to tower defense.

However, if a biter comes in proximity of the player, [[turret]]s or [[radar]]s, it will prioritize these and attempt to immediately attack them instead, again trying to reach the new target over the shortest possible path with no too great detours, if possible.

==Evolution==
[[File:Evolution Biters.png|thumb|right|400px|Spawn chances of biters from biter spawners by evolution factor.]]
[[File:Evolution Spitters.png|thumb|right|400px|Spawn chances of spitters from spitter spawners by evolution factor.]]
[[File:Evolution Weights.png|thumb|right|400px|Weight graph of both spawners by evolution factor. The values shown are primarily for indicating when certain types start and stop spawning, for actual chances refer to the tables or other charts.]]
The evolution factor is a global variable that determines what kind of biters will be spawned. You can check the variable in the dev console via the following command (does not disable achievements):

/evolution

The evolution factor goes from 0 (not evolved at all) to 1 (maximal evolution). At the moment the evolution factor can only increase.

Besides choosing what kind of biter will be spawned, the evolution factor also influences the spawning interval. This interval (<code>spawning_cooldown</code> in the <code>enemy-spawner</code> definition) is interpolated between 360 (0 evolution) and 150 (1 evolution) game ticks (= 6 to 2.5 seconds).

=== Methods of increasing ===

The evolution factor is increased by three kinds of events:

* The passage of time very slightly increases the evolution factor.
* The global [[Pollution|pollution production]] increases the evolution factor.
* Destroying [[Enemies#Nests|nests]] significantly increases the evolution factor.

All these values are set in <code>game.map_settings.enemy_evolution</code>. From there they can be changed or modded.

The default settings are:

{| class="wikitable"
!Source per
!Variable in <code>enemy_evolution</code>
!Percent increase
|-
| [[Time#Seconds|Second]] || <code>time_factor</code> || 0.0004%
|-
| 1 Pollution unit || <code>pollution_factor</code> || 0.00009%
|-
| Destroyed enemy spawner || <code>destroy_factor</code> || 0.2%
|}

Pollution production is the total pollution produced by [[Pollution#Polluters|buildings]] per tick, not the pollution spreading on the map, so it is not reduced by trees or other absorbers.
e.g. : 10 boilers produce 300 pollution in one minute, raising the evolution factor by around 0.027%.

The percentages are applied on the base of <code>1 - current_evolution_factor</code>. So for instance destroying enemy spawners in the beginning of the game results in increase of evolution factor by 0.005 (half a percent) while doing this when the evolution factor is 0.5 the increase is only 0.0025 (quarter a percent).

This also means that the evolution factor approaches 1 asymptotically - generally, increases past 0.9 or so are ''very'' slow and the number never actually reaches 1.0.

=== Spawn chances by evolution factor ===

The probability charts show the chances of each type of biter/spitter for each spawner at all evolution levels.

<div id="evoChecker"></div>

=== Advanced: Evolution factor components and computation ===
<div class="toccolours mw-collapsible mw-collapsed" style="width:calc(100%-400px); overflow:auto;">
This section has charts plotting the individual evolution factor components and discusses possibilities for manually estimating the evolution factor.
<div class="mw-collapsible-content">

[[File:Evolution_factor_by_time.png|400px|thumb|right|1. Single-component evolution factor increase with time]]
[[File:Evolution_factor_by_pollution.png|400px|thumb|right|2. Single-component evolution factor increase with pollution]]
[[File:Evolution_factor_by_spawners.png|400px|thumb|right|3. Single-component evolution factor increase with destroyed spawners]]

'''Notes'''

* Data from version 0.16.51.

* All charts end at approximately an evolution factor of 0.99.

*To simplify calculation, the time and pollution charts are calculated using steps of 1,000 seconds / 1,000,000 pollution units - in both cases 1,000 times larger than the unit the game uses for the calculation. Because of the recursive nature of the calculation, this makes the values in the charts somewhat '''higher''' than those the game would obtain in the same calculation; however, the difference is fairly minimal (less than 1 percentage point). The spawners chart is calculated 1-to-1 and therefore accurate.

*While time passed is shown on save files and spawners destroyed can be retrieved from player statistics, the game does not currently report the total pollution released by the player. Also, none of the well-known Factorio calculators show pollution generated by a particular factory. Therefore, to make use of the pollution chart the player's pollution output would need to be manually estimated.

*Given that the game reports the actual evolution factor (console: <code>/evolution</code>) whenever the player wishes, these charts are intended primarily to help estimate the impact of planned base expansions and similar activities on the evolution factor's future development.

'''Comments'''

These charts (click to enlarge) represent the situation where each evolution factor component (time, pollution, destroyed spawners) is the ''only'' component contributing to the evolution factor in that entire game. They are therefore '''not realistic''', as in a typical game all three components will contribute, some at varying times and intensities.

Because of how contributions to the evolution factor (hereinafter, EF) are calculated (multiplied by <code>(1 - current EF)</code>), it is '''not''' possible to simply add the values indicated by these charts for a game's time passed, pollution generated, and / or spawners destroyed so far to retrieve the total evolution factor.

For example, if 20 hours have passed (single-component EF =~ 0.25), 10 million pollution units were released (single-component EF =~ 0.15), and 200 spawners were destroyed (single-component EF =~ 0.35), the actual evolution factor will '''not''' be (0.25 + 0.15 + 0.35 =) ~0.85.

However, the evolution factor will always be '''less''' than the sum of all individual components as indicated by these charts, and '''at least''' as high as the highest individual component. Thus, using the values from above, the EF will be ''at least'' 0.35 and ''less than'' 0.85. A smarter approach is required to compute the amount of pollution released.

'''Computation of actual evolution factor'''

The actual EF can be computed as follow :

<code> 1 - EF = (1 - E[t]) * (1 - E[p]) * (1 - E[s])</code>, where ''E[t]'', ''E[p]'', and ''E[s]'' are the single-component values from the pollution, time, and spawner charts, in that order.

A key observation in understanding where this formula comes from is that each increpmental change of the evolution factor is effectively a multiplication of <code>1 - EF</code> by a constant (depending on the nature of the change). For example, an other way of saying that killing a biter nest augment evolution by 0.2% of <code>1 - EF</code>, is to say that killing a biter nest multiplies <code>1 - EF</code> by 0.998.

So like multiplication, evolution is, barring rounding errors, associative and commutative. The commutativity means that the order in which you make actions increasing evolution do not matter, and along the assossiativity grounds the formula above.

That knowledge can also be applied to compute the above charts exactly, or to compute a component of evolution without having to refer to the chart at all. For example, pollution as a function of time only is <code>1 - 0.999996 ^ t</code> where t is the time in seconds.

For the values from above, we can deduce the evolution factor <code>1 - EF = (1 - 0.25) * (1 - 0.15) * (1 - 0.35) = 0.75 * 0.85 * 0.35 = 0.41</code>, which gives an evolution factor of <code>0.59</code>.

This formula can also be used to estimate impact of future player activities on the EF : a set of actions that is known to bring the evolution factor of a world from 0 to EF(2) (eg using the above chart and formula) will bring it from EF(1) to <code>1 - (1-EF(1)) * (1-EF(2))</code>

For example, if the player planned to spend the next 20 hours building up their base, releasing 10 million pollution and destroying 200 spawners in the meantime (i.e., the same numbers as in the example above), and the EF at the start of the project were, say, 0.55, then the estimated EF at project end will be <code>1 - (1 - 0.55) * (1 - 0.59) = 0.81</code>.
</div></div>

== Gallery ==
<gallery widths=270px heights=140px>
File:player_near_enemy_nests.png|The player near some enemy nests and worms.
File:player_worms_acid.png|The player among acid puddles created by attacking worms.
File:player_attacked_by_biters.png|Both the player and some buildings getting attacked by biters.
File:enemy_nests_mapgen.png|Enemy nests seen in a map generation preview (deathworld setting).
File:turret_wall_biters.png|Line of gun turrets defending against biters.
</gallery>

== History ==
{{history|0.17.0|
* Behemoth worm added.}}

{{history|0.15.0|
* Increased the damage, range, and health of worms.
* Decreased health and resist of Behemoth biters.}}

{{history|0.13.10|
* Biters and other units won't become aggressive as a result of friendly-fire.}}

{{history|0.13.0|
* Big and behemoth enemies now spawn 50% slower.}}

{{history|0.12.26|
* Running biters over with a vehicle will now anger them in peaceful mode.}}

{{history|0.12.0|
* Updated sounds for enemies.}}

{{history|0.11.17|
* Items dropped by enemies([[alien artifact|*]]) are now collected automatically and from longer distances.}}

{{history|0.11.6|
* Range of spitters is now 15, less than turrets.}}

{{history|0.11.0|
* Spitters added.
* Drawing of enemies optimised, so adding new colors does not impact VRAM.
* Blood splashes on death are now procedural.}}

{{history|0.9.0|
* Turrets no longer search for enemies when none are near.
* Biters can no longer destroy the shipwreck in the 3rd new hope campaign.}}

{{history|0.8.1|
* Further improvement to enemy AI.}}

{{history|0.8.0|
* Decreased the range of medium worm from 25 to 20.}}

{{history|0.7.2|
* Biter AI improved.}}

{{history|0.7.1|
* Peaceful mode added for freeplay.}}

{{history|0.7.0|
* Enemy creepers were replaced by small, medium and big biters.
* Enemy turrets were replaced by small, medium and big shooting worms.
* Enemies move and attack in groups.
* Enemies wander around their base when they have nothing to do.
* Enemies call for help when attacked.
* Enemies can create new bases.
* Enemies can now destroy all player creations they find.}}

{{history|0.1.0|
* Introduced, called 'creepers'}}

== See also ==
* [[Damage]]
* [[Pollution]]

Pollution

2019-11-07T12:41:33Z

Jon8RFC: fix redirects

{{languages}}
[[File:Pollution.png|300px|thumb|Example of in-game pollution (red squares) in the map]]
[[File:pollution_gui.png|300px|thumb|Pollution tab in the production GUI.]]

Pollution is represented as an abstract "cloud", updated [[Map_structure#Chunk|per chunk]] every game second (60 ticks) and visible on the map, when "alt-view" is on (default [[Keyboard bindings|Alt-Key]]). It appears as a red colored blocky cloud.

It is produced by many buildings involved in processing items and spreads outwards at a steady rate.

The [[Enemies#Evolution|evolution factor]] is not increased by the spreading/absorbed pollution, but by the pollution produced by all the player's [[Pollution#Polluters|machinery]] at every tick. This means that no matter how hard the player tries to contain the pollution, [[enemies]] will still evolve at the same rate. They just won't attack the player as frequently. The pollution cloud is used to trigger biter attacks and determines the size of the attacks.

Pollution settings can be changed via [[World_generator|map generation]] settings, or can be disabled entirely.

== Pollution spread ==

As soon as a chunk has reached 15.0 pollution it starts spreading in all four cardinal directions at a rate of 2% per [[Time#Seconds|game-second]] (60 ticks). Pollution can generate new chunks if it needs to spread to them.

For example, a chunk with 400.0 pollution and 4 adjacent chunks with 100.0 pollution each, raises the pollution in all adjacent chunks by 8.0 while reducing its own pollution by 32.0. But every one of the 4 surrounding spreads 2.0 pollution "back" to the center chunk, so it only loses 24.0 + [[Pollution#De-polluters|absorbed value]].

== Pollution dissipation==

* Every [[Map_structure#Chunk|chunk]] (32x32) of map slowly reduces the pollution it covers (See [[Pollution#Chunks]]). So the more the pollution spreads, the more is absorbed.
* [[Tree]]s also absorb some pollution (See [[Pollution#Trees]]).
* [[Enemies#Spawner|Spawners]] absorb a great amount of pollution, and use this to assign enemies to attacks.

== Native life ==
Pollution attracts [[Enemies#Biters|biters]] to the Player's factory. Biters who find themselves in a polluted area will attempt to reach the source of pollution and destroy it.

If a chunk's pollution is greater than 20, each enemy spawner absorbs 20 + 0.01 * [chunk's pollution] every game second (60 ticks), otherwise it absorbs 3 times the amount of pollution needed for the most expensive unit it can spawn for the current evolution factor.

Higher pollution values decrease the time it takes for biters to join the attack force. After a certain amount of pollution is absorbed the spawner sends one of its biters/spitters to a rendezvous point. Every 1 to 10 minutes (random) the mustered biters launch an attack. If not all biters have arrived at the rendezvous point by that time, they will wait up to an additional 2 minutes for stragglers.

Required pollution to add an additional biter/spitter to the attack wave:
{| class="wikitable" style="text-align:right;"
! style="width: 100px;" | Pollution 
! style="width: 130px;" | Type 
|-
| 4  || Small biter 
|-
| 20  || Medium biter 
|-
| 80  || Big biter 
|-
| 400  || Behemoth biter 
|-
| 4  || Small spitter 
|-
| 12  || Medium spitter 
|-
| 30  || Big spitter 
|-
| 200  || Behemoth spitter 
|-
|}

== Modules ==
[[Module]]s that list "+x% pollution" increase pollution multiplier, not a flat pollution rate. Final pollution value is (pollution multiplier * energy usage multiplier * base pollution), meaning heavily boosted buildings are likely to account for most of the pollution produced in a factory.

== Production/Absorption ==
These tables contain information about the levels of pollution produced/absorbed by items in the game.
=== Polluters ===
{| class="wikitable"
! Structure !! Pollution per minute at full power
|-
| {{Imagelink|Stone furnace}} || 2
|-
| {{Imagelink|Steel furnace}} || 4
|-
| {{Imagelink|Electric furnace}} || 1
|-
| {{Imagelink|Burner mining drill}} || 12
|-
| {{Imagelink|Electric mining drill}} || 10
|-
| {{imagelink|Pumpjack}} || 10
|-
| {{Imagelink|Assembling machine 1}} || 4
|-
| {{Imagelink|Assembling machine 2}} || 3
|-
| {{Imagelink|Assembling machine 3}} || 2
|-
| {{imagelink|Boiler}} || 30
|-
| {{Imagelink|Oil refinery}} || 6
|-
| {{Imagelink|Chemical plant}} || 4
|-
| {{Imagelink|Centrifuge}} || 4
|-
|}

Fire on the ground and burning trees produce 0.005 pollution per second.

=== De-polluters ===

==== Spawner ====
If a chunk's pollution is greater than 20, each enemy spawner absorbs 20 + 0.01 * [chunk's pollution] every game second (60 ticks), otherwise it absorbs 3 times the amount of pollution needed for the most expensive unit it can spawn for the current evolution factor.

==== Chunks ====
Every chunk has a natural absorption rate per second which is determined by the sum of the pollution absorption of its floor tiles.

Following numbers are the pollution reduction for a single tile per second.
{| class="wikitable"
! Tile !! Pollution per second
|-
| Grass 1-4 || -0.0000075
|-
| Dirt 1-7, dry dirt || -0.0000066
|-
| Sand 1-3 || -0.0000058
|-
| Red desert 0-3 || -0.0000066
|-
| Water, green water, deep water, deep green water, shallow water, mud water || -0.000005
|-
| Path tiles (Stone bricks, concrete etc), landfill || 0
|-
| Out of map || -0.00001
|-
| Special tiles (Lab tiles, tutorial grid) || 0
|-
|}

==== Trees ====
Every single tree absorbs a small amount of pollution in its chunk per second. If the total pollution in that chunk is above 60 units, trees lose their leaves for every 10 pollution absorbed. The less dense the leaves, the slower the tree absorbs pollution.

{| class="wikitable"
! Object !! Stage !! Pollution per second
|-
| rowspan="4" | [[File:Green tree.png|120px]] Tree, red tree, brown tree || 0 (Max leaf density) || -0.001
|-
| 1 || -0.00067
|-
| 2 || -0.00033
|-
| 3 (Min leaf density) || 0
|-
| [[File:Dead dry hairy tree.png|120px]] Dead dry hairy tree || No stages || -0.0001
|-
| [[File:Dead grey trunk.png|120px]] Dead grey trunk || No stages || -0.0001
|-
| [[File:Dead tree desert.png|120px]] Dead tree - desert|| No stages || -0.0001
|-
| [[File:Dry hairy tree.png|120px]] Dry hairy tree || No stages || -0.0001
|-
| [[File:Dry tree.png|120px]] Dry tree || No stages || -0.0001
|-
|}

== Achievements ==
Pollution is directly connected to the following achievement:
{{Achievement|it-stinks-and-they-dont-like-it}}

== History ==

{{history|0.17.12|
* Added pollution tab to the production statistics.
* Spawner tooltip (including the pollution statistics), shows distribution of biters spawn for the current evolution factor with the pollution costs.
* Pollution generation is now shown in the x/s format both on the entity and in the item/crafting slot.
* Internal pollution values have been normalized, and they are now roughly 60 times less compared to what they were.}}

{{history|0.17.0|
* Rebalanced assembling machine 1,2 and 3 power consumption and pollution - higher tiers eat more power, but produce less pollution.
* Changed spawner pollution absorption logic so that all the pollution on a chunk doesn't build up un-spent in a single spawner.}}

{{history|0.13.2|
* Optimized rendering of huge pollution clouds on the map.}}

{{history|0.13.0|
* Large amounts of pollution is created when burning fires.
* Pollution creation of the productivity module was reduced drastically.
* Optimized pollution rendering on map and minimap.
}}

{{history|0.12.0|
* [[Tree]]s degenerate slowly when exposed to pollution at high levels. }}

{{history|0.8.0|
* Added option to turn off pollution visibility even when detailed info is on. }}

{{history|0.7.1|
* Speed modules no longer produce extra pollution.
* Added missing pollution descriptions.
* Pollution is only shown on the minimap with alt mode on.
}}

{{history|0.7.0|
* Introduced concept of pollution.}}

== See also ==
* [[Crafting]]
* [[Module]]s
* [[Enemies]]

Upgrade planner

2019-11-07T12:38:33Z

Jon8RFC: fix redirect

{{Languages}}{{:Infobox:Upgrade planner}}
The '''upgrade planner''' is a tool for mass updating entities to alternative entities of the same size and type. It can be used on both placed structures and [[ghost]]s. It can also modify the contents of a [[blueprint]]. While most commonly used to upgrade entities to their higher tier equivalents - for example to replace [[transport belt]]s with [[fast transport belt]]s or [[fast inserter]]s with [[stack inserter]]s - the upgrade planner is able to change a wide range of entities including [[transport belts]], [[underground belts]], [[splitters]], [[inserters]], [[assembling machine]]s, [[chests]], [[electric system|power poles]], [[rail signal]]s, [[module]]s, [[furnace]]s and more.

Using an upgrade planner in the game world is similar to the operation of the [[deconstruction planner]] and blueprint, in that the player drags a rectangular area in which the upgrade planner will function and this results in orders being queued for [[construction robot]]s. Upgrade planners can be used blank (unfiltered) to automatically apply a limited set of common upgrades. Alternatively they can be configured (filtered) to make specific replacements. This can include downgrading higher tier, later-game entities to lower tier equivalents.

== Basic operation ==

=== Getting an upgrade planner ===

A blank planner can be obtained by:

* Clicking the green upgrade planner icon ( [[File:upgrade_planner_button.png|20px]] ) on the [[shortcut bar]] (available once [[Construction robotics (research)|construction robotics]] has been researched in at least one game.)
* Opening the blueprint library and clicking '''New Upgrade planner'''.

This will result in a blank upgrade planner appearing in the hand. It can be used immediately or placed in the inventory. It must be placed in the inventory before a filter can be applied and before it can be pinned to a [[quickbar]] slot.

=== Using a planner in the game world ===

With a planner held in the hand the player can click-drag it ({{Keybinding|lmb}} is held down while moving the mouse) over existing structures to mark them for upgrade. A tooltip appears indicating which entities will be changed and to what.

Once {{Keybinding|lmb}} is released yellow circles will appear over any existing structures that are now queued for update. These update operations will be performed by [[construction robot]]s.

Upgrade planners can also affect ghost entities. Any ghost eligible for update will immediately change to the new entity.

<gallery widths=280px heights=260px>
File:UpgradePlanner-DraggingAPlanner.png|thumb|none|250px|Dragging an upgrade planner.
File:UpgradePlanner-DraggingAPlannerTooltip.png|thumb|none|250px|The tooltip shows which upgrades will occur.
File:UpgradePlanner-PendingUpgradeOperationCircles.png|thumb|none|250px|Yellow circles indicate pending update operations.
File:UpgradePlanner-GhostsDemo.gif|Ghost entities update immediately.
</gallery>

=== Cancelling updates ===

Pending upgrade operations can be cancelled by holding {{Keybinding|Shift}} while click-dragging the upgrade planner over the affected area.

=== Updating blueprints ===

Upgrade planners can also be used to change the contents of a blueprint. This allows the player to keep using the same blueprints as they research progressively better entities. As upgrade planners can also downgrade entities this further provides a way for a player to adjust late-game blueprints to make them suitable for re-use in subsequent games.

* The blueprint to be updated must reside in an inventory. It is not currently possible to use an upgrade planner in the blueprint library.
* With a planner held in the hand, the edit window for a blueprint should be opened by clicking {{Keybinding|rmb}} on it.
* The upgrade planner can be applied by clicking {{Keybinding|lmb}} on the grey upgrade planner slot in the top right corner of the blueprint.
* The entities in the blueprint will immediately update according to the filters in the planner. If a blank planner is used an automatic set of common upgrades is applied, as described in the next section.
* The update is immediate and cannot be undone, except by applying another upgrade planner with filters set to change back the affected entities.
 
: [[File:UpgradePlanner-BlueprintExample.gif|border]]

== Upgrade planner filters ==

A new upgrade planner is blank, meaning it lacks any configuration and will operate on a pre-defined set of upgrade rules. The planner can optionally be edited to provide a custom list of update rules that control which entities will be updated and what to.

=== Using a blank upgrade planner (unfiltered) ===

When a blank upgrade planner is used it operates on a specific list of entities considered automatically upgradable to the next highest tier. The list of entity types that can be affected by a blank planner are as follows:

* [[Transport belts|Belts]]
* [[Underground belts]]
* [[Splitters]]
* [[Inserters]]
* [[Assembling machine]]s
* [[Furnace]]s

Entities of the above types will be upgraded to the next highest tier where one exists. A complete list of the entities eligible for upgrade by a blank planner is found in [[#Valid entities|Valid entities]].

=== Filtering an upgrade planner ===

The planner must be in an inventory in order for it to be editable. The filter window can be accessed by clicking {{Keybinding|rmb}} on an upgrade planner, either in the inventory or on a [[quickbar]] link.

==== The filter window ====

The filter window consists of 24 entity slot pairs.

In each pair the entity to be updated goes in the left slot and the entity it will be changed to goes in the right slot.

<gallery widths=300px heights=200px>
File:UpgradePlanner-Blank.png|300px|A blank planner.
File:UpgradePlanner-Example1.png|300px|A simple configuration example.
</gallery>

==== Editing the filters ====

A filter is applied by first clicking {{Keybinding|lmb}} on the left-hand slot of any slot pair. This brings up the '''Select upgrade''' window. This is similar to the [[Items|item selection]] window but is limited to displaying the entities an upgrade planner is able to change.

The right-hand slot is then selected in the same way, choosing the target entity. The select upgrade window for the right slot will only show entities that are a valid update target for the entity in the left slot.

When there is only one possible update target the right slot will be filled in automatically.

Filters can be removed by clicking {{Keybinding|rmb}} on the slot.

== Valid entities ==
[[File:UpgradePlanner-DowngradeExampleCropped.png|thumb|right|200px|An example of downgrading. This could be helpful to make a blueprint usable from the beginning of a game.]]
The upgrade planner can operate on the entities listed below. It can swap any entity in a given category to any other entity in the same category. For example a [[transport belt]] can be changed to a [[fast transport belt|fast]] or [[express transport belt]] and also to any kind of [[underground belt]], but not to a [[splitters|splitter]] or a [[chests|chest]].

The '''Blank upgrade planner''' column indicates which entities will be automatically upgraded when a blank (unfiltered) upgrade planner is used. These entities will upgrade to the entity following them in the table.

{| class="wikitable"
!style="width: 220px;" |Category
!Entity
!Blank upgrade planner
|-
| Belts and undergrounds || [[Transport belt]] || Yes
|-
| Belts and undergrounds || [[Fast transport belt]] || Yes
|-
| Belts and undergrounds || [[Express transport belt]] || No
|-
| Belts and undergrounds || [[Underground belt]] || Yes
|-
| Belts and undergrounds || [[Fast underground belt]] || Yes
|-
| Belts and undergrounds || [[Express underground belt]] || No
|-
| Splitters || [[Splitter]] || Yes
|-
| Splitters || [[Fast splitter]] || Yes
|-
| Splitters || [[Express splitter]] || No
|-
| Inserters || [[Burner inserter]] || No
|-
| Inserters || [[Inserter]] || Yes
|-
| Inserters || [[Fast inserter]] || Yes
|-
| Inserters || [[Stack inserter]] || No
|-
| Inserters || [[Filter inserter]] || No
|-
| Inserters || [[Stack filter inserter]] || No
|-
| Pipes || [[Pipe]] || No
|-
| Pipes || [[Pipe to ground]] || No
|-
| Chests || [[Wooden chest]] || No
|-
| Chests || [[Iron chest]] || No
|-
| Chests || [[Steel chest]] || No
|-
| Chests || [[Active provider chest]] || No
|-
| Chests || [[Passive provider chest]] || No
|-
| Chests || [[Storage chest]] || No
|-
| Chests || [[Buffer chest]] || No
|-
| Chests || [[Requester chest]] || No
|-
| Power poles || [[Small electric pole]] || No
|-
| Power poles || [[Medium electric pole]] || No
|-
| Rail signals || [[Rail signal]] || No
|-
| Rail signals || [[Rail chain signal]] || No
|-
| Steam Engine/Turbine || [[Steam engine]] || No
|-
| Steam Engine/Turbine || [[Steam turbine]] || No
|-
| Furnaces || [[Stone furnace]] || Yes
|-
| Furnaces || [[Steel furnace]] || No
|-
| Assembling machines || [[Assembling machine 1]] || Yes
|-
| Assembling machines || [[Assembling machine 2]] || Yes
|-
| Assembling machines || [[Assembling machine 3]] || No
|-
| Modules || [[Speed module]] || No
|-
| Modules || [[Speed module 2]] || No
|-
| Modules || [[Speed module 3]] || No
|-
| Modules || [[Productivity module]] || No
|-
| Modules || [[Productivity module 2]] || No
|-
| Modules || [[Productivity module 3]] || No
|-
| Modules || [[Efficiency module]] || No
|-
| Modules || [[Efficiency module 2]] || No
|-
| Modules || [[Efficiency module 3]] || No
|-
| Wall/Gate || [[Wall]] || No
|-
| Wall/Gate || [[Gate]] || No
|}

=== Modded entities ===

[[modding|Modded]] entities can also be valid entities for an upgrade planner. The filter selection window will expand to automatically include any modded entities compatible with the above categories.

This can also result in extra categories being available for update, beyond those listed above. For example if a mod is installed that adds new types of [[lamp]], it may become possible to update the vanilla lamp to one of the new modded lamps using an upgrade planner.

== History ==
{{history|0.17.10|
* "Make upgrade planner" function is now accessible via keyboard shortcut.}}

{{history|0.17.0|
* Introduced}}

== See also ==

* [[Construction robot]]

{{ProductionNav}}
{{C|Tools}}

Quickbar

2019-11-07T12:37:46Z

Jon8RFC: fix redirect

{{Languages}}
[[File:Quickbar-example.png|thumb|right|450px|An example of a quickbar layout. Two visible bars containing various items plus an [[upgrade planner]] and two [[blueprint book]]s.]]
The '''quickbar''' is a user interface component for creating shortcut links to items, [[blueprint]]s, [[blueprint book]]s, [[deconstruction planner]]s and [[upgrade planner]]s. Once created they can be quickly selected at any time without needing to open the inventory. The quickbar is always visible at the bottom of the screen. It shows between one and four bars from a set of ten available, each containing 10 slots. Clicking any filled slot will place the chosen item in the player's hand if available in the inventory. It can also be configured to provide a [[ghost]] of any item the player is not currently carrying. The quickbar also allows blueprints and books to be pinned directly from the blueprint library, providing quick access to these blueprints without cluttering the inventory.

== A shortcut to items, not an inventory ==

The quickbar replaces the toolbelt found in previous versions of the game. The toolbelt also functioned as inventory space; the quickbar does not. It contains links to items regardless of whether they are in the player's inventory.

== Ten quickbars available ==

In total the player has 10 different quickbars available for use, providing space to shortcut up to 100 different items. To see all the quickbars, the number against any visible bar can be clicked.

[[File:Quickbar-View10Bars.gif]]

== Basic Usage ==
[[File:Quickbar-ConfigureVisibleNumber.png|thumb|right|331x33px|Configuring the number of visible quickbars.]]
=== Setting the number of visible quickbars ===

The game defaults to showing two quickbars. This can be changed to between one and four visible at a time, configured with the '''Active quickbars''' option in '''Settings->Interface'''.

There is no research connected to the quickbar; the player can access all quickbars from the beginning of the game.

=== What can be placed on a quickbar ===

* Any type of item, including modded items. Items can be added regardless of whether they are currently being carried.
* Any [[blueprint]], [[blueprint book]], [[deconstruction planner]] or [[upgrade planner]] in the player's inventory.
* Blueprints and blueprint books directly from the blueprint library.

=== Adding and removing items ===

* Clicking {{Keybinding|lmb}} on an empty slot opens the [[Items|item selection]] window, allowing the selection of the item to be linked in that slot.
* With an item in the hand, clicking {{Keybinding|lmb}} or {{Keybinding|mmb}} on an empty slot creates a link to that item.
* Existing links can be removed by clicking {{Keybinding|mmb}} on the slot.
** On macOS the default binding is instead {{Keybinding|Command-Right-Click}}.
* A slot must be cleared before a new item can be placed in it.

=== Accessing items ===

* Clicking {{Keybinding|lmb}} on a filled slot will, when that item is carried in the inventory, place one [[stack]] in the hand.
[[File:Quickbar-InventoryItemvsGhostItem.png|frame|right|The player is carrying 300 [[Express transport belt|express belts]] but no [[Fast transport belt|fast belts]].]]
* Clicking {{Keybinding|rmb}} will place half a stack in the hand.
* If a slot is clicked while another item is in the hand, the held item will change to the newly clicked item.
* If a given item is not available in the inventory the game can optionally give an entity ghost. This feature can be enabled by selecting '''Pick ghost item if no items are available''' in '''Settings->Interface'''.

=== Inventory counts ===

Items that the player is carrying in their inventory will show a number underneath indicating the total amount carried. Items not present in the inventory will have no number and appear dimmed.

The exception to this rule is the [[artillery targeting remote]], which will show you how many artillery turrets, that have shells, are in range of your current position.

== Accessing multiple quickbars ==
[[File:Quickbar-SwapBarsExample.png|thumb|right|400px|The player has three visible quickbars and has changed the second bar to bar 5 and the third to bar 4.]]
=== With the mouse ===

Clicking on the number next to any visible quickbar will bring up a list of all 10 quickbars. Then clicking the number against any other bar will move it into the position originally selected.

=== With the keyboard ===

Three different methods are provided for manipulating the visible quickbars using the keyboard:

# '''Select quickbar''' shortcuts, defaulting to {{Keybinding|Shift-1}} through {{Keybinding|Shift-0}}.
## Changes the top visible quickbar to the bar selected by the shortcut.
# '''Next active quickbar''' and '''Previous active quickbar''' shortcuts. Not bound by default.
## '''Next active quickbar''' will change the top quickbar to the next highest number. For example if bar 3 is in the top position it will change to bar 4. Bar 10 will change to bar 1.
## '''Previous active quickbar''' does the opposite; bar 3 would change to bar 2. Bar 1 will change to bar 10.
# '''Rotate active quickbars''', defaulting to {{Keybinding|X}}.
## Rotates all the visible quickbars down to the next position. The bottom bar goes to the top. It does not change which quickbars are visible, only their relative positions.

== Selecting quickbar items with the keyboard ==

In addition to using the mouse to click on an item slot it is also possible to use keyboard shortcuts. Combined with the '''Select quickbar''' shortcuts for accessing specific bars, this provides the ability to select any one of up to 100 different items with at most two successive keyboard shortcuts.

Two sets of 10 hotkeys are available: one set for accessing items on the top visible bar, the second set for the second visible bar.

=== Shortcut 1-10 (top bar) ===

* The keyboard shortcuts named '''Shortcut 1''' to '''Shortcut 10''' access the items on the top bar currently visible.
* The default bindings are {{Keybinding|1}} through {{Keybinding|0}} for items 1 to 10 respectively.

=== Secondary Shortcut 1-10 (second bar) ===

* The keyboard shortcuts named '''Secondary Shortcut 1''' to '''Secondary Shortcut 10''' access the items on the second bar currently visible.
* These are not bound by default. An example binding could be {{Keybinding|Control-1}} through {{Keybinding|Control-0}}.

== Blueprints, blueprint books and planners on the quickbar ==

[[File:Quickbar-BlueprintsPlanners.png|thumb|right|240px|Planners, a blueprint and a blueprint book pinned from the inventory to the Quickbar.]]
It is possible to pin blueprints, blueprint books, deconstruction planners and upgrade planners to any quickbar slot.

=== From the inventory ===

Any blueprint, blueprint book or planner currently in the inventory can be pinned to a quickbar slot. If the item in question is deleted or destroyed, the quickbar link for it will be automatically removed. If the item is removed from the inventory, for example by being placed in a chest, the quickbar link will remain but will not function until the blueprint or planner returns to the player's inventory.

{{Keybinding|rmb}} on a quickbar slot containing a blueprint, blueprint book or planner will open that item's edit window.

=== Direct from the blueprint library ===

[[File:Quickbar-BlueprintsFromLibrary.png|thumb|right|180x80px|Two blueprint books and a blueprint pinned directly from the blueprint library to the quickbar.]]

It is also possible to pin blueprints and blueprint books directly from the blueprint library. These appear differently to blueprints pinned from the player's inventory - they have a darker background and no dotted border. There is no visual distinction between a blueprint book and a blueprint unless the tooltip is viewed.

The advantage of pinning from the library is that it provides permanent and quick access to the blueprints in question without the player needing to keep copies in their inventory. This saves inventory space for other purposes.

Clicking with {{Keybinding|rmb}} on the quickbar link for a library blueprint or book will directly access the library copy. This can usually be noticed as the blueprint library UI will also appear in the background, behind the UI for the blueprint or book itself. The player should be careful when accessing library blueprints in this way - clicking the delete button will permanently remove them from the library!

== History ==

{{history|0.17.0|
* Introduced}}

== See also ==

* [https://youtu.be/8VZ_TsXVv3U Quickbar Hotkey Demo (Video demonstration/tutorial)]
* [[Shortcut bar]]

{{C|GUI}}

Construction robot

2019-11-07T12:36:59Z

Jon8RFC: /* Mechanics */ fix redirect

{{Languages}}
{{:Infobox:Construction robot}}

'''Construction robots''' are autonomous floating devices capable of repairing or building the player's structures. They are one of two type of robotic floating devices, the other being the [[logistic robot]]s. They run on electricity from [[roboport]]s.

== Mechanics ==

Construction robots accomplish various tasks, including:

* They repair damaged entities using [[repair pack]]s.
* They replace destroyed entities as long as they are available in a [[provider chest]] or [[storage chest]].
* They remove entities marked with the [[deconstruction planner]]. Removed entities are transported into storage chests. As of 0.15, this includes [[raw fish|fish]].
* They add entities marked with a [[blueprint]] or placed as [[ghost]]s as long as these entities are available. Entities are fetched from the closest logistic chest.
* They can carry and place up to four [[tile]]s at once, as of 0.17.75.

Construction robots are priority targets of [[enemies]], meaning Biters/spitters will engage them even if there are [[pollution]]-producing buildings around. Construction robots have no means of defending themselves and do not run when they encounter enemies. Because they often operate at the "front", they are in high danger to be destroyed. Despite being a floating entity, ground units using melee are still capable of destroying them.

Researching [[Worker robot cargo size (research)|more cargo]] or [[Worker robot speed (research)|more speed]] for the logistic bots are also valid for the construction robots.

== Achievements ==
{{Achievement|automated-cleanup}}
{{Achievement|automated-construction}}
{{Achievement|you-are-doing-it-right}}

== History ==

{{history|0.17.75|
* Construction robots will attempt to batch build tiles.}}

{{history|0.17.0|
* Construction robots can blow up cliffs.
* Landfill can be built by construction robots and be included in blueprints.}}

{{history|0.15.0|
* Fish can be collected by construction robots.}}

{{history|0.12.4|
* Construction robots when used by the player will take primarily from the player's inventory, then the hotbar.
* Construction robots will check if their target is still in the network area when they return to personal roboport for charging.
}}

{{history|0.12.0|
* Construction robots can now be used by the player via a [[personal roboport]] embedded into a type of modular armor.}}

{{history|0.11.17|
* AI of the construction robots improved.}}

{{history|0.10.2|
* Construction robots take as many [[repair pack]]s as they can when going to repair.}}

{{history|0.10.0|
* Construction robots no longer die of lack of electricity, they just slow down to 20% of their normal speed.}}

{{history|0.9.0|
* The [[deconstruction planner]] can be used to order bots to destroy buildings/trees.}}

{{history|0.8.6|
* Robots can rebuild [[land mine]]s.}}

{{history|0.8.1|
* Construction robots now use the durability of the [[repair pack]]s when using them.}}

{{history|0.8.0|
* Introduced}}

== See also ==
* [[Robots]]
* [[Logistic robot]]
* [[Repair pack]]

{{LogisticsNav}}
{{C|Logistic network}}

Blueprint

2019-11-07T12:35:09Z

Jon8RFC: fix redirects

{{Languages}}
{{:Infobox:Blueprint}}

'''Blueprints''' are items that contain building layouts. Blueprints are used to 'copy & paste' parts of a factory. Built areas can be selected for inclusion in a blueprint. When a blueprint is placed, a [[ghost]] of the layout appears on the ground. This can be used as a guide for manually placing factory pieces, or, more commonly, handed over to [[construction robot]]s for automated completion.

Blueprints can be stored in a [[blueprint book]]. This can store an unlimited amount of blueprints while taking only one inventory spot.

== Achievements ==
{{Achievement|automated-construction}}
{{Achievement|you-are-doing-it-right}}

== Usage ==

Blank blueprints can be crafted by clicking the 'new blueprint' button in the blueprints dialog, or the ( [[File:Blueprint_button.png|20px]] ) button in the [[shortcut bar]].
This dialog is opened by pressing {{Key|B}} or clicking the blueprint icon above the mini-map.

The blank blueprint can now be used to 'copy' a set of buildings.

For example, copying this small laser defense setup:

[[File:Blueprint-example-01.png]]

=== Create a blueprint ===

To create a blueprint select the blueprint item out of the toolbar or the inventory.
With the blueprint icon shown next to the mouse cursor, click and hold the left mouse button and drag a box as large as needed.
All buildings which will be included in the blueprint will be highlighted with a green square.
Once everything to 'copy' is inside the drag box, release the mouse button, and the 'Blueprint icon setup' menu will open.

[[File:Blueprint-example-02.png‎]]

=== Blueprint icon setup ===

On the top left of the 'Blueprint icon setup" menu there are four icon slots.
The game chooses automatically the number of icons and which are pre-selected depending on the number of buildings that are included.
This can be changed by simply clicking on the icons to choose the desired ones.

On the top right there are two icons to 'create blueprint' and 'cancel blueprint'.
The 'create blueprint' icon will also show a preview of how the blueprint icon will look after creation.
The 'Blueprint preview' just shows the preview of the blueprint.

On the bottom the 'Total' number of buildings included in the blueprint is shown.

Finally, create the blueprint if everything is fine or cancel it.
Canceling does not consume the blueprint item.
The created blueprint will be in the tool belt or the inventory (or dropped to the ground if no tool belt/inventory slot is available).

[[File:Blueprint-example-03.png‎]]

=== Placing the blueprint ===

To use/place the created blueprint select it from the tool belt or inventory.
The whole building setup of the blueprint will be shown at your mouse cursor.
In this case the Blueprint was renamed to "Example blueprint".
It is possible to place it rotated, press the default key {{keybinding|r}} to rotate.
The blueprint can be placed anywhere inside the green (or orange) 110×110 tiles area of a [[roboport]], or within range of a [[personal roboport]] installed in [[modular armor]].

[[File:Blueprint-example-04.png‎]]

After the blueprint gets placed somewhere, the buildings are placed as ghost buildings.
[[Construction robot]]s will now start to pick up the needed items from the construction network/the player inventory (if using a personal roboport) and place them at the ghost buildings.
The required items need to be in the network in an [[active provider chest]], a [[passive provider chest]] or a [[storage chest]].

[[File:Blueprint-example-05.png‎]]

=== Viewing and clearing a blueprint ===

Right clicking on a blueprint allows you to can view, edit and clear it.
By clearing it, it will become blank so it can be set again.

== Importing/Exporting blueprints ==

It is possible to export blueprints as a text string and import said text string to create a new blueprint. This makes sharing blueprints between players very easy. 
Clicking the '''Export to string''' button ( [[File:ExportToString.png|25px]] ) in the top right of the blueprint edit window will pop up a window containing the '''Blueprint string'''. This string can be copied to the operating system clipboard, from where it could be saved to a text file or uploaded to a website.

To import a blueprint, the player can click the '''Import string''' icon on the [[shortcut bar]] ( [[File:ImportString.png|25px]] ) or choose the same option from the blueprint library. A dialogue box will appear into which the string can be pasted. This will result in a blueprint appearing on the hand with the same setup as the one that was exported.

The text string itself is a base64 encoded, compressed JSON string which contains all the information of the blueprint. It is therefore possible to decode/decompress the text string, change attributes of the blueprint in the JSON text and finally re-encode/compress it back to the known text string format. This basically allows blueprint editing outside of the game itself.

A complete explanation of the blueprint JSON can be found on the [[blueprint string format]] page.

== Additional information ==

* Once a blueprint is created it can be used unlimited times.
* To place a blueprint that is blocked by existing buildings you can hold shift to place the things that aren't blocked.
* The above trick will also mark rocks and trees for deconstruction.
* Buildings marked for destruction will not block placing a blueprint. The blueprinted building cannot be placed if there are any buildings in the way. This can cause an item outside the construction zone to block construction of a 2×2 building on the edge of the zone.
* The size limit of blueprints is 10k by 10k [[Map_structure#Tile|tiles]].

== History ==
{{history|0.17.10|
* "Make blueprint" function is now accessible via keyboard shortcut.}}

{{history|0.17.0|
* Trains can be blueprinted.}}

{{history|0.15.24|
* In multiplayer, admins are allowed to modify other players' blueprints in the library, including deleting them.}}

{{history|0.15.3|
* Blueprints can be destroyed by clicking the trash can icon in the GUI.}}

{{history|0.15.0|
* Blueprint library: Allows for keeping players blueprints between individual game saves and allows sharing blueprints in multiplayer games.
* The build rotation of each blueprint is remembered independently of the general item build rotation.
* Alternative select with blueprints (shift + select) skips the blueprint setup GUI.
* Added ability to export and import blueprints, blueprint books, and deconstruction planners as strings.
* Blueprints, blueprint books and deconstruction planners are obtainable from the library GUI with no crafting cost.}}

{{history|0.14.15|
* Changed the clear blueprint icon to the trashcan icon and moved it to the left of the cancel button, to make it less confusing for users.}}

{{history|0.13.13|
* Added [http://lua-api.factorio.com/latest/LuaEntityPrototype.html entity prototype flags] not-blueprintable and not-deconstructable, so these can be controlled by mod makers.}}

{{history|0.13.9|
* Added tips and tricks for pasting wagon slots and cycling in [[blueprint book]].}}

{{history|0.13.7|
* Rocks can be mined while holding blueprints.}}

{{history|0.13.5|
* Blueprints with labels will now show the label when holding them in the active hand.}}

{{history|0.13.0|
* Blueprints can now be edited.
* Added the [[blueprint book]] item, can hold multiple blueprints in one item.
* Modules are now supported by blueprints.
* Optimized drawing of connections between [[roboport]]s in blueprints.
* [[Circuit network#Virtual_signals|Virtual signals]] can be used in blueprint icons.
}}

{{history|0.12.2|
* Enabled swapping held blueprints with other blueprints directly.
* Force building blueprints will mark colliding trees for deconstruction.}}

{{history|0.12.0|
* Enabled mining trees/ghosts while holding blueprints to be built.
* Building blueprints over existing ghosts restores the ghost's life time.
* Proper blueprint centering.
}}

{{history|0.11.18|
* Blueprints can be built over things marked for deconstruction.
* Blueprints can be force built by shift clicking.
}}

{{history|0.11.10|
* Added [http://lua-api.factorio.com/latest/LuaItemStack.html Lua API] for reading/writing information from blueprints.}}

{{history|0.10.2|
* The rotation of turrets in blueprints no longer matters when testing for entity collision.}}

{{history|0.10.0|
* Blueprints can copy [[circuit network]] connections.
* Miners in blueprints are now ignored if they are non-functional.
* An [[inserter]]'s logistic conditions are copied when blueprinting.
}}

{{history|0.9.4|
* Limit the size of the blueprint preview, so it is usable for very large blueprints.}}

{{history|0.9.2|
* The [[train stop]] and [[lab]] built from blueprints are now given dedicated names.}}

{{history|0.9.0|
*Introduced}}

== See also ==
* [[Deconstruction planner]]
* [[Upgrade planner]]
* [[Blueprint book]]
* [[Logistic network]]
* [[Roboport]]
* [[Personal roboport]]
* [[Construction robot]]
* [[Blueprint string format]]

{{ProductionNav}}
{{C|Tools}}

Exoskeleton

2019-11-07T12:33:12Z

Jon8RFC: /* Movement speed increase */ fix redirects

{{Languages}}
{{:Infobox:Exoskeleton}}

'''Exoskeleton''' enhances the movement speed of the player by 30% when fully powered. It consumes 200kW (200kJ/s) of power when used. They can be toggled on and off in the [[shortcut bar]], assuming the player is wearing one.

Exoskeleton is a kind of [[Equipment modules|Equipment module]]. It can be used by placing it in the grid that opens by right clicking the armor.

Each exoskeleton occupies a 2×4 tall rectangle in the equipment grid. It is possible to use multiple exoskeletons in modular armor, and the speed bonus will stack additively. There is no speed limit; it is limited only by the amount of room available in the armor and by available power.

Exoskeletons have a 56kJ internal electricity storage, visible as a charging bar. With no power, this will sustain them for less than a second. As the available power approaches 200kW, the charging bar will both drain more slowly and have a larger minimum size. The exoskeleton will provide a full speed bonus until the charging bar hits the minimum size, at which point the exoskeleton's speed bonus drops to what it can maintain. At 200kW or greater, the charging bar does not shrink and the speed bonus remains at maximum.

Note, however, that exoskeletons are below shields in armor charging priority, and if the shields are damaged at all, exoskeletons will rapidly run dry and will not resume their full speed until the shields are fully charged. This makes them fairly useless for quick getaways.

== Movement speed increase ==

The base movement speed is '''8.902''' [[Map_structure#Tile|tiles]] per [[Time#Seconds|game-second]]. [[Talk:Exoskeleton#Movement%20speed%20experiments|1]] Each additional exoskeleton increases the speed by 30% of the base speed.

{| class="wikitable"
|-
! Number of exoskeletons
! Tiles/game-second
! % of base speed
|-
| 0
| 8.902
| 100 %
|-
| 1
| 11.483
| 129 %
|-
| 2
| 14.286
| 161 %
|-
| 3
| 16.866
| 190 %
|-
| 4
| 19.672
| 221 %
|-
| 5
| 22.472
| 252 %
|-
| 6
| 25.026
| 281 %
|}

== History ==
{{history|0.17.10|
* "Toggle exoskeleton" function is now accessible via keyboard shortcut.}}

{{history|0.17.0|
* Added shortcut bar that allows quick access to certain game features such as turning off exoskeleton.}}

{{history|0.13.0|
* Power consumption increased by a factor of 10.}}

{{history|0.12.0|
* Power consumption increased by a factor of 100.}}

{{history|0.7.0|
* Introduced}}

== See also ==
* [[Modular armor]]
* [[Equipment modules]]

{{CombatNav}}
{{C|Equipment}}

Transport belt

2019-11-07T12:31:05Z

Jon8RFC: match capitalization of fast and express transport belts

{{Languages}}{{:Infobox:Transport belt}}
The '''transport belt''' is the easiest and cheapest method of automatic item transportation. It is the first tier among the three [[belt transport system|transport belts]].

No prior [[research]] is required and it is available from the beginning of the game.

==Properties==

[[File:Basic_transport_belt_fulldensity.gif|right|frame|414px|3 [[fast inserter]]s per side will fill a basic transport belt to maximum density.]]

{| class="wikitable"
|-
! scope="col" | Type
! scope="col" | Max. throughput (Items per [[Time#Seconds|game-second]] for two lanes)1
! scope="col" | Speed ([[Map_structure#Tile|Tiles]] per game-second)1
! scope="col" | Max. density (Items per tile)1
! scope="col" | Required [[research|technologies]]
|-
| {{Imagelink|Transport belt|Transport belt}} || 15 || 1.875 || 8 || None
|}

(1) See [[transport belts/Physics|physics of transport belts]] for more detailed information.

== History ==

{{history|0.17.0|
* Increased throughput from 13.33 to 15.
* Consistently holds 8 items per tile.}}

{{history|0.15.0|
* Increased stack size from 50 to 100.}}

{{history|0.13.0|
* Transport belt is now connectible to the [[circuit network]].
* Transport belt connectible entities will now disconnect from incoming belts when marked for deconstruction.}}

{{history|0.12.0|
* Items on transport belts don't go off the belt at the end, so the transport belt has to go directly in front of the required inserter.
* Optimised the transport belt movement.}}

{{history|0.11.9|
* Items marked for deconstruction cannot be moved by belts anymore.
* Reduced the CPU load caused by big counts of [[inserters]] loading/unloading transport belts.}}

{{history|0.9.7|
* Belts to be deconstructed no longer accept items. }}

{{history|0.9.6|
* New transport belt graphics. }}

{{history|0.9.0|
* Small optimisation. }}

{{history|0.6.0|
* Transport belt doesn't pull player out of the edge of it (like items), so player won't be almost trapped on faster transport belts. }}

{{history|0.5.0|
* Better movement on transport belts in turns and crossings. }}

{{history|0.2.8|
* Cross connections of transport belt of the same type are disabled. }}

{{history|0.2.2|
* When transport belts are rotated (or replaced with different than opposite direction), items on transport belt are collected.}}

{{history|0.2.1|
* Small optimisation. }}

{{history|0.1.0|
* Introduced}}

== See also ==

* [[Belt transport system]]
* [[Fast transport belt]]
** [[Fast splitter]]
* [[Express transport belt]]
** [[Express splitter]]

{{LogisticsNav}}
{{C|Belt transport system}}

Express transport belt

2019-11-07T12:27:35Z

Jon8RFC: /* Properties */ fix redirects

{{Languages}}{{:Infobox:Express transport belt}}
'''Express transport belts''' are a faster variant of the [[transport belt]], operating at triple speed. They are the third and final tier among the [[Belt transport system|transport belts]].

Unlike previous tiers, express transport belts rely on [[oil processing]] for [[lubricant]]. Therefore, it is recommended to restrict their production in early-game until high throughput is needed.

== Properties ==

[[File:Express_transport_belt_fulldensity.gif|right|300px|thumb| 9 [[Fast inserter]] per side will fill an express belt to max. density.]]

{| class="wikitable"
|-
! scope="col" | Type
! scope="col" | Max. throughput (Items per [[Time#Seconds|game-second]])1
! scope="col" | Speed ([[Map_structure#Tile|Tiles]] per game-second)1
! scope="col" | Max. density (Items per tile)1
! scope="col" | Required [[Research|technologies]]
|-
| {{Imagelink|Express transport belt|Express transport belt}} || 45.0 || 5.625 || 8 || [[Logistics 3 (research)]]
|}

(1) See [[Transport belts/Physics|Physics of Transport Belts]] for more detailed information.

== History ==

{{history|0.17.0|
* Increased throughput from 40 to 45.
* Consistently holds 8 items per tile.}}

{{history|0.15.0|
* Increased stack size from 50 to 100.}}

{{history|0.13.0|
* Transport belt is now connectible to the [[circuit network]].
* Transport belt connectible entities will now disconnect from incoming belts when marked for deconstruction.}}

{{history|0.12.0|
* Items on transport belts don't go off the belt at the end, so the transport belt has to go directly in front of the required inserter.
* Optimised the transport belt movement.}}

{{history|0.11.9|
* Items marked for deconstruction cannot be moved by belts anymore.
* Reduced the CPU load caused by big counts of [[inserters]] loading/unloading transport belts.}}

{{history|0.11.0|
* Fast/express belts are now made from the slower variants.}}

{{history|0.9.7|
* Belts to be deconstructed no longer accept items. }}

{{history|0.9.6|
* New transport belt graphics. }}

{{history|0.9.2|
* Express belts require lubricant. }}

{{history|0.9.0|
* Small optimisation. }}

{{history|0.7.1|
* [[Express transport belt]] now takes 10 [[Iron gear wheel]]s to craft, down from 15. }}

{{history|0.6.0|
* Transport belt doesn't pull player out of the edge of it (like items), so player won't be almost trapped on faster transport belts. }}

{{history|0.5.0|
* Better movement on transport belts in turns and crossings. }}

{{history|0.2.8|
* Cross connections of transport belt of the same type are disabled. }}

{{history|0.2.2|
* When transport belts are rotated (or replaced with different than opposite direction), items on transport belt are collected.}}

{{history|0.2.1|
* Small optimisation. }}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Belt transport system]]
** [[Splitters]]
** [[Inserters]]
* [[Crafting]]

{{LogisticsNav}}
{{C|Belt transport system}}

Fast transport belt

2019-11-07T12:26:27Z

Jon8RFC: /* Properties */ fix redirects

{{Languages}}
{{:Infobox:Fast transport belt}}

'''Fast transport belts''' are a faster variant of the [[transport belt]], operating at double speed. They are the second tier among the three [[Belt transport system|transport belts]].

==Properties==

[[File:Fast_transport_belt_fulldensity.gif|right|300px|thumb|6 [[Fast inserter]]s per side will fill a fast transport belt to max. density]]

{| class="wikitable"
|-
! scope="col" | Type
! scope="col" | Max. throughput (Items per [[Time#Seconds|game-second]])1
! scope="col" | Speed ([[Time#Seconds|Tiles]] per game-second)1
! scope="col" | Max. density (Items per tile)1
! scope="col" | Required [[Research|technologies]]
|-
| {{Imagelink|Fast transport belt|Fast transport belt}} || 30 || 3.75 || 8 || [[Logistics 2 (research)]]
|}

(1) See [[Transport belts/Physics|Physics of Transport Belts]] for more detailed information.

== History ==

{{history|0.17.0|
* Increased throughput from 26.66 to 30 items/second.
* Consistently holds 8 items per tile.}}

{{history|0.15.0|
* Increased stack size from 50 to 100.}}

{{history|0.13.0|
* Transport belt is now connectible to the [[circuit network]].
* Transport belt connectible entities will now disconnect from incoming belts when marked for deconstruction.}}

{{history|0.12.0|
* Items on transport belts don't go off the belt at the end, so the transport belt has to go directly in front of the required inserter.
* Optimised the transport belt movement.}}

{{history|0.11.9|
* Items marked for deconstruction cannot be moved by belts anymore.
* Reduced the CPU load caused by big counts of [[inserters]] loading/unloading transport belts.}}

{{history|0.11.0|
* Fast/express belts are now made from the slower variants.}}

{{history|0.9.7|
* Belts to be deconstructed no longer accept items. }}

{{history|0.9.6|
* New transport belt graphics. }}

{{history|0.9.0|
* Small optimisation. }}

{{history|0.6.0|
* Transport belt doesn't pull player out of the edge of it (like items), so player won't be almost trapped on faster transport belts. }}

{{history|0.5.0|
* Better movement on transport belts in turns and crossings. }}

{{history|0.2.8|
* Cross connections of transport belt of the same type are disabled. }}

{{history|0.2.2|
* When transport belts are rotated (or replaced with different than opposite direction), items on transport belt are collected.}}

{{history|0.2.1|
* Small optimisation. }}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Belt transport system]]
** [[Splitters]]
** [[Inserters]]
* [[Crafting]]

{{LogisticsNav}}
{{C|Belt transport system}}

Belt transport system

2019-11-07T12:25:03Z

Jon8RFC: fix redirects

{{Languages}}
The belt transport system is the first system the [[player]] will use to transport items from place to place. It, along
with [[Railway|trains]], and [[Logistic network|Logistic robots]], makes up the systems of item transportation in
Factorio.

Belts specifically are used to transport items and run without using energy. Belts can also interact with other moving entities such as [[player]]s, [[vehicle]]s and [[enemies|biters]], also allowing for faster or slower movement speed.

== Belt tier overview ==
[[File:Transport_belts_speed.gif|300px|thumb|top|Animation showing the three types of belt and their speed (from top to bottom: regular belts, fast belts, and express belts).]]
There are 3 different tiers of belts available for use. The [[transport belt]] has a yellow color and is the slowest, as well as the cheapest to craft. The next tier up, the [[fast transport belt]] has a red color and is twice as fast as the standard transport belt. The [[express transport belt]] is the final tier. It is colored blue and is three times faster than normal belts, or 1.5× faster than red belts. 
{| class="wikitable"
! [[Transport belts]] !! [[Underground belts]] !! [[Splitters]] !! Max. throughput (Items/[[Time#Seconds|second]]) !! Needed research
|-
| {{Imagelink|Transport belt}}
| {{Imagelink|Underground belt}}
| {{Imagelink|Splitter|Splitter}}
| 15
| [[Logistics (research)]]1
|-
| {{Imagelink|Fast transport belt}}
| {{Imagelink|Fast underground belt}}
| {{Imagelink|Fast splitter}}
| 30
| [[Logistics 2 (research)]]
|-
| {{Imagelink|Express transport belt}}
| {{Imagelink|Express underground belt}}
| {{Imagelink|Express splitter}}
| 45
| [[Logistics 3 (research)]]
|-
|}
(1) Only for the underground belt and splitter. The basic transport belt is available at the start of the game.

Regardless of the belt tier, a fully filled transport belt holds 8 items in total. For more information on this, see [https://factorio.com/blog/post/fff-276 Friday Facts #276 - Belt item spacing].
{{clear}}

== Belt mechanics ==

=== Merging and un-merging belts ===

Belts of all tiers have 2 lanes for items to ride on. This allows for either a double flow of one material, or to transport two different materials on the same belt. Mixed belts can be beneficial for
smelting ore, or producing items with many different ingredients such as [[Utility science pack]]. The belt can be unmerged using a splitter filter. It is also possible to unmerge a mixed belt by using underground belts since an underground belt will block half of the belt.

[[File:Transport_belts_2_lanes.gif|top]]   [[File:Transport_belts_unmerge.gif|top]]

Commonly, merging and un-merging is done by using a [[splitter]]. The trick in the second gif is better described in the '''[[Belt_transport_system#Separating_belt_lanes|Underground Belt]]''' section.

=== Lane balance ===

Due to how items are placed onto belts by [[inserters]], their lanes can sometimes become unbalanced. In order to
maintain throughput, balancing the lanes may be necessary. The gifs below show two ways how to do this. The former only works if only one lane is in use initially. For further explanation of the mechanics, see [[Balancer mechanics#Lane_balancers|lane balancers]].

[[File:Transport_belts_balance1.gif|top]]   [[File:Transport_belts_balance2.gif|top]]

=== Belt throughput ===
[[File:Stack inserters fill express belt.gif|frame|230px|right|4 [[stack inserter]]s can compress an express belt at stack size 12 for the left inserters and stack size 8 for the right inserters.]]
Maximizing the throughput means ensuring that as many items as possible are transported. Therefore some definitions need to
be introduced:

; Speed
: How fast a belt moves in tiles per second. This is 1.875, 3.75 and 5.625 for basic, fast and express belts.
; Density
: How tight are the items put onto the belts; each straight belt piece can hold exactly 8 items.
; Throughput
: This is speed × density. It describes how many items pass by at a given time.

So, there are three opportunities to enhance the throughput:

; More density
:Sometimes items have small gaps in between each other that aren't big enough for other items to fit in. However, mining drills, inserters, and belt sideloading can still force an item into these gaps, temporarily squashing the items on the belt. The squashed gap is extended to normal size once the front of the belt starts to move again.
; More speed
:If the belts in the factory are already at maximum density, their speed can still be upgraded with better belts. Finding the bottleneck is the first thing that needs to be done, usually it can be discovered quite easily. There will be a part of the belt where the items don't move quickly (or at all) or stop at maximum density and suddenly they come to a point where this 'stop and go' effect releases itself, the bottleneck has been found. In most cases, this will be the place where belt optimization is needed.
; More belts
:Adding additional parallel belts can also increase the throughput. Simply place more belts carrying the item that needs throughput.

=== Belt tricks ===

Moving fast can be essential to defend alien attacks in time. Running on a belt will increase or decrease the movement speed of the [[player]] accordingly to the belts speed. That is why building a belt towards your [[defense]]s can be beneficial.

However, the player is not the only unit that can be moved by transport belts. Additionally, biters and spitters can be moved. This can be abused to improve your defense. Firstly, biters will have a harder time to reach your walls when placing express transport belt in front of them. Secondly, spitters can be moved closer to your walls. That way more turrets can attack a single spitter at once.

Another useful usage is [[car]]s on transport belts. Cars have an inventory and can be filled by [[inserters]]. So, they can be used as moving boxes on belts. This has several advantages: Firstly the throughput of the belt-car-boxes is amazingly high, secondly the inserter stack size bonus does apply here and makes inserters more effective.

== Splitters ==

[[Splitters]] are another form of item manipulation. Splitters are a 2×1 entity that splits incoming items on belts
from up to two input to up to two outputs, in a 1:1 ratio. They are used to divide resources between two belts, or balance
multiple belts.

=== Mechanics ===

The behavior of splitters looks simple at first glance. But they are not that simple. Splitters have an astonishing amount of uses.

* Splitters have two input belts and two output belts. If the splitter receives items on one belt, it will split the input evenly between its two outputs. If one of the outputs is fully backed-up and the splitter cannot split evenly, it will put all input on its other output.
* Splitters can also merge belts, taking two inputs and one output.
* Splitters preserve the lanes of the items, by moving through the splitter an item on the right lane will not be moved to the left lane, and vice versa.
* Splitters can prioritize one input and/or one output. Clicking on a splitter opens its GUI where the priorities can be set.
* One output of the splitter can be filtered to one item. Items of that type will only go to that output, and not to the other one. When a filter is set, the output of that side is prioritized.

The speed of the splitter is the same as its relevant type of belt, so in order to properly join/split belts, the splitter must be the same speed as the incoming belts. Otherwise the splitter will become a bottleneck.

==== Priority ====
For both the input and output side of the splitter it is possible to set the priority to either left or right.

A splitter where the input priority has been set will first try to consume the specified input side, and will only
consume the other input once there is a gap on the prioritized input belt.

Similarly a splitter where the output priority has been set will try to redirect all incoming items
to the specified output, and will only output on the other output once the specified output is full.

==== Filter ====
If a specific item is set in the splitter's filter slot, the slider for the output priority will
be used for the filter instead. All items of the set type will be redirected to that specific output
and all other items are directed to the other output. The input priority can be set independently of the filter.

=== Balancing ===

{{Main|Balancer mechanics}}

Balancers are used to evenly distribute items over multiple belts or multiple belt lanes.

=== Manipulating belt lanes ===
<gallery mode="slideshow">
File:Swap_belt_lanes.png|Swapping lanes on a belt with a different item per belt lane.
File:Splitter_seperate_belt_lanes.png|Separating lanes with different items on them.
</gallery>

== [[Circuit network]] ==

[[File:transport_belt_circuits.png|thumb|200px|Two belts connected to a [[constant combinator]].]][[Red wire|Red]] or [[green wire]]s can be connected to segments of transport belts to use them as part of a circuit. Belts connected to the circuit network will appear with a yellow cage above them, with a moving red scanner within it. When a belt is connected to a circuit, a GUI can be accessed from the connected belt for settings on how the belt will be used for a circuit; there are two modes of operation that can be used:

'''Enable/disable''' - A circuit condition dictates whether or not the belt will allow items through. 
'''Read belt contents''' - If enabled, the contents on the belt will be read.

The belt's GUI will also have a "content read mode" setting, which can be set to either '''pulse''' or '''hold'''. '''Pulse''' will read the belt's contents for only one [[Time|tick]], while '''hold''' will read the belt's contents continuously on every tick.

[[File:transport_belt_circuit_gui.png|thumb|right|Transport belt GUI.|130px]]

<gallery mode="slideshow">
File:transport_belt_circuit_example1.gif|A small example of a transport belt circuit reading belt contents to trigger two lamps.
File:transport_belt_circuit_example2.gif|[[Fast inserter]]s are activated by the [[arithmetic combinator]]s' setup; when a specific item enters a belt segment that's connected to the circuit network, the inserters place the same item on another belt.
</gallery>
{{clear}}

== Underground belts ==

Underground belts can be used to cross different flows of items without interfering. They move items like a [[Transport belts|normal belt]].

* Underground belts can cross any number of entities and all types of ground, like water and grass. (as long as the input and output endpoints are on land)
* Underground belts can cross other underground entities (any number of underground belts or underground pipes). They won't be mixed.
* For the connection only the endpoints (entry-side and exit-side) are relevant.
* The maximum distance underground is 8 [[Map_structure#Tile|tiles]] with [[express underground belt]]s.
* An underground belt pair that bridges a gap of 4 tiles stores up to 44 items. An express underground belt pair at max length stores up to 72 items.
* The half of the underground belt tile with a belt can accept input from the side. The other half (with a tunnel entrance) blocks incoming items.

=== Separating belt lanes ===
<gallery mode="slideshow">
File:Block belt lane.png|This is built by placing one underground belt and then using R to reverse its direction. This converts the underground belt entrance to an exit (and vice versa).
File:Transport belts unmerge.gif|This can also be used to split the lanes of a belt onto seperate belts instead of using a splitter filter.

</gallery>

== See also ==
* [[Splitters]]
* [[Transport belts]]
* [[Underground belts]]

{{C|Belt transport system}}

Transport belt

2019-11-07T12:22:26Z

Jon8RFC: /* Properties */ fix redirects

{{Languages}}{{:Infobox:Transport belt}}
The '''transport belt''' is the easiest and cheapest method of automatic item transportation. It is the first tier among the three [[belt transport system|transport belts]].

No prior [[research]] is required and it is available from the beginning of the game.

==Properties==

[[File:Basic_transport_belt_fulldensity.gif|right|frame|414px|3 [[fast inserter]]s per side will fill a basic transport belt to maximum density.]]

{| class="wikitable"
|-
! scope="col" | Type
! scope="col" | Max. throughput (items per [[Time#Seconds|game-second]] for two lanes)1
! scope="col" | Speed ([[Map_structure#Tile|tiles]] per game-second)1
! scope="col" | Max. density (items per tile)1
! scope="col" | Required [[research|technologies]]
|-
| {{Imagelink|Transport belt|Transport belt}} || 15 || 1.875 || 8 || None
|}

(1) See [[transport belts/Physics|physics of transport belts]] for more detailed information.

== History ==

{{history|0.17.0|
* Increased throughput from 13.33 to 15.
* Consistently holds 8 items per tile.}}

{{history|0.15.0|
* Increased stack size from 50 to 100.}}

{{history|0.13.0|
* Transport belt is now connectible to the [[circuit network]].
* Transport belt connectible entities will now disconnect from incoming belts when marked for deconstruction.}}

{{history|0.12.0|
* Items on transport belts don't go off the belt at the end, so the transport belt has to go directly in front of the required inserter.
* Optimised the transport belt movement.}}

{{history|0.11.9|
* Items marked for deconstruction cannot be moved by belts anymore.
* Reduced the CPU load caused by big counts of [[inserters]] loading/unloading transport belts.}}

{{history|0.9.7|
* Belts to be deconstructed no longer accept items. }}

{{history|0.9.6|
* New transport belt graphics. }}

{{history|0.9.0|
* Small optimisation. }}

{{history|0.6.0|
* Transport belt doesn't pull player out of the edge of it (like items), so player won't be almost trapped on faster transport belts. }}

{{history|0.5.0|
* Better movement on transport belts in turns and crossings. }}

{{history|0.2.8|
* Cross connections of transport belt of the same type are disabled. }}

{{history|0.2.2|
* When transport belts are rotated (or replaced with different than opposite direction), items on transport belt are collected.}}

{{history|0.2.1|
* Small optimisation. }}

{{history|0.1.0|
* Introduced}}

== See also ==

* [[Belt transport system]]
* [[Fast transport belt]]
** [[Fast splitter]]
* [[Express transport belt]]
** [[Express splitter]]

{{LogisticsNav}}
{{C|Belt transport system}}

Radar

2019-11-07T12:19:46Z

Jon8RFC: /* Nearby Pulse Scanning */ fix redirect

{{Languages}}
{{:Infobox:Radar}}
The radar triggers charting of the map of the force it belongs to.

It can be used to provide a small area of remote vision on the map; it also allows periodic scanning of distant chunks around it. The Radar has a high [[Electric system|power]] demand (300kW) so a radar indirectly contributes to [[pollution]] when powered by [[boiler]]s and [[Steam engine|steam engines]]. A radar can be continuously powered by eight solar panels and six accumulators. Seven solar panels and five accumulators is the most efficient; it gives the radar full power all but a short time in the morning, but never dips below the 20% power threshold for nearby scanning.

The radar will be attacked by enemies that come within very close range, like turrets, due to its status as a military building, but will not attract biters from long range like polluting structures do. The radar will show enemy lifeforms and structures, as well as [[Railway#Trains|trains]], [[Car|cars]], and other [[player]]s in the scanned area.

== Nearby Pulse Scanning ==

The Radar continuously charts an area of 7×7 [[Map_structure#Chunk|chunks]] (224×224 [[Map_structure#Tile|tiles]]), centered on the chunk the radar occupies. This nearby area is updated as a single pulse approximately every second. At reduced power levels, this nearby pulse scan will take longer, which can lead to 'blinking' on the player's map similar to the long range scan. This is particularly noticeable at dawn and dusk on solar powered radar stations.

At 20% power the radar will pulse about every 4 seconds which will still keep the nearby area continuously lit on the map, but will provide reduced detail. 20% power can be achieved by a single [[solar panel]], or by using one isolating accumulator for every 5 radars.

== Long Range Survey Scanning ==

The Radar charts one distant [[Map_structure#Chunk|chunk]] every time the sector scanning progress bar fills. This will take 33.333 seconds, if the Radar is receiving full power. Mouse-over or click-open the radar details to see this progress bar. Long range scanning is visible on the map as a single chunk lighting up for several seconds, then slowly darkening.

* It scans the unexplored chunks first, represented by the black areas on the map. Note that it also generates the chunks if they weren't generated at the time of the scan.
* One chunk scan takes 10 MJ of energy to complete. Since the Radar draws 300 kW of power, it takes 10 MJ ÷ 300 kW = 33.333 seconds to scan one chunk.
* This is done in an 29×29 chunks around the Radar, excluding the nearby 7×7 chunks.
** With a total number of 797 chunks (29×29 − 7×7), it takes one radar '''7 hours 20 minutes''' to complete one full scan cycle.
* If everything is already explored it continues to scan by re-scanning the longest-ago scanned chunk within range.
* Multiple radars will share long-range chunks, reducing the amount of time it takes to complete long-range survey scanning.
** This is a smart process, meaning that the radars will not scan chunks currently being scanned by other radars.

'''It is possible that a new alien nest will appear in a previously scanned chunk; just because you don't see it on the map, doesn't mean it is not there.

== Coverage ==

Radars grant sight of a square area around them, which is displayed brighter than the rest of the map. This allows the player to zoom into the normal world view from the map and makes interaction with [[blueprint]]s and [[deconstruction planner]]s possible.

[[File:Radar_coverage.png|thumb|500px|none|The coverage area of a radar and the player.]]

== Charting ==

If a [[Map_structure#Chunk|chunk]] is '''scanned''' by a radar or player, the image of that chunk that is copied into the map of the players of this surface force (every force has its own map).

This procedure is called "charting".

=== Charting Process ===

If the contents of a chunk changes between two ticks, the content of that chunk is "charted" into the map. The map is just a bitmap, a picture. You can see the entities moving, you can see enemies walking. Every entity is represented by one or more pixels. Not every entity is drawn. Users can recognize what is drawn because of the color.

Charting of several chunks that change each tick might have an impact on game performance, manifesting in the form of lowered <abbr title="Updates Per Second">UPS</abbr> or <abbr title="Frames Per Second">FPS</abbr>.

=== Charting Decay Time / Fog of War ===

Once a scan for a chunk is triggered, it keeps actively charted for '''10 seconds'''. This effect can also be seen in the map of the chunk highlighted and dims within 10 seconds to a greyed out version of the chunk.

If charting is not repeated within the 10 seconds, the charting process stops for this chunk after 10 seconds and is not longer updated. What you see after that time is the last charted picture for that chunk (also called "fog of war").

=== Charting of Vehicles ===

Even in the fog of war you can see the last charted position of vehicles. Trains last positions are not charted, because they normally always move after the charting stops.

Vehicles are shown as a circle, with an arrow pointing in the direction that they're facing.

=== Invisible (black) parts of the Map ===

The [[World_generator#Generating_new_Chunks|World Generator]] creates a "border" of invisible chunks around each chunk, that becomes active at some time. Active chunks are those that become charted or those that are active because the pollution spreads onto them.

== History ==

{{history|0.15.0|
* Radar now allows remote view via map.}}

{{history|0.12.17|
* Updated icons.}}

{{history|0.11.11|
* Radar ignores chunks outside the map radius.}}

{{history|0.10.0|
* New graphics.}}

{{history|0.9.0|
* Halved radar electricity consumption.}}

{{history|0.7.3|
* Radar continues refreshing chunks after all chunks in range have been discovered.}}

{{history|0.5.1|
* New Graphics}}

{{history|Unknown, presumed 0.1.0|
* Introduced}}

== See also ==
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].

{{CombatNav}}
{{C|Defense}}

Inserters

2019-11-07T12:18:53Z

Jon8RFC: fix redirects

{{Languages}}
''For the common yellow electrical inserter, see [[Inserter]].''

'''Inserters''' are devices which are used to move items over short distances. When placed, they have a fixed direction. They can move items from behind and place them in front of them. By doing this, they can move items from one transport belt to another, but also extract items from—and insert items into—machines or storage devices.

== Types of inserters ==

{| class="wikitable"
| {{Imagelink|Burner inserter}} || The only [[fuel]]-powered inserter, with the slowest speed.
|-
| {{Imagelink|Inserter}} || The standard electrical inserter.
|-
| {{Imagelink|Long handed inserter}} || Capable of inserting and removing items from a greater distance.
|-
| {{Imagelink|Fast inserter}} || Much faster than the inserter.
|-
| {{Imagelink|Filter inserter}} || Variant of the fast inserter that can filter items by type.
|-
| {{Imagelink|Stack inserter}} || As fast as the fast inserter, but can move many more items at the same time at once.
|-
| {{imagelink|Stack filter inserter}} || Variant of the stack inserter that can filter items by type.
|-
|}

==Mechanics==
Inserters '''will''':
* Pick up items off the ground, off of a [[Transport belts|transport belt]], or from any object that has storage space, including [[Chests|chests]], [[furnace]]s and [[assembling machine]]s.
* Place the item onto the ground, onto a transport belt, or into any object that has storage space.
* Run at slower speeds when starved for energy.
* Pick up as many items as their [[inserter capacity bonus (research)|stack size]] allows at once, if they do not have to wait too long to pick them up.

Inserters '''will not''':
* Pick up any items that can not be inserted into the adjacent entity.
* Pick up any items if the adjacent entity is a blueprint.
* Pick up items to place into an entity with a full inventory.
* Place more than one item at a time onto the same ground tile.
* Place items into an entity that can not hold them, for example due to [[Stack#Filtered_stacks|filtered]] or [[Stack#Stack_limitation|limited slots]].
* Fill up the entire target inventory of [[boiler]]s, [[nuclear reactor]]s, [[:Category:Producers|production building]]s, [[furnace]]s, and [[turret]]s.

If two or more inserters are picking up from the same tile, the inserter who can grab the items the fastest will grab them first. Besides faster inserters, this favors inserters taking from the inner lane of a transport belt.

=== Insertion limits ===
Depending on where an inserter is moving items, it does not always fill up the entire target inventory. This allows other inserters taking from the same transport belt to pick up their share of the items. For example, if a boiler has 5 or more items of fuel in it, an inserter will not insert additional fuel. This allows the other fuel to travel further down the transport belt. When the fuel drops below 5 items, the inserter will resume inserting fuel, up to the limit of 5 items.

{| class="wikitable"
! Entity !! Item type !! Automatic insertion limit
|-
| [[Boiler]]s, [[burner inserter]]s, [[furnace]]s, and [[nuclear reactor]]s || [[Fuel]] || align="center" | 5
|-
| [[Gun turret]]s || Bullet Magazines || align="center" | 10
|-
| [[Artillery turret]]s || [[Artillery shell]]s || align="center" | 5
|-
| [[Assembling machine]]s, [[furnace]]s, [[centrifuge]]s, [[chemical plant]]s, and [[Oil refinery|oil refineries]]|| Items needed for the recipe || The ingredients for 1 craft in addition to the ingredients for the number of crafts that can complete during one full inserter swing; but at least the ingredients for 2 crafts and at most the ingredients for 100 crafts.
|-
| [[Lab]]s || [[Science pack]]s || Double the number of science packs needed for one research unit.
|}

An inserter that has a higher [[inserter capacity bonus (research)|inserter capacity bonus]] than 1 can overfill the target building, due to the inserter picking up a higher amount of items than needed. Overfilling can also occur if multiple inserters are used to insert items into one building.

=== Inserters and transport belts ===
[[Transport belts]] have two lanes on which items can travel. Inserters only place items onto one side of the belt, either the far side from the inserter's perspective or if the belt is going the same or the opposite direction as the inserter the right side from the belt's perspective.

{|
| style="width:320px;" | [[File:Inserter_dropoff_locations.gif]] || [[File:Inserter_pickup_locations.gif]]
|-
| style="width:320px;" | Inserters place the item on the furthest lane. If a belt is in the same orientation as the inserter, the item will be placed on the right-hand lane, from the belt's perspective. In curves the inserter always places on the far side.
| style="width:320px;" | If the belt is perpendicular to the inserter, inserters '''prefer''' taking items from the nearest lane. If the nearest lane is empty, the inserter will take from the far lane. If the belt is the same/opposite orientation of the inserter or a curve, the inserter '''prefers''' taking from the left lane, from the belt's perspective. If the left lane is empty it will take from the right lane.
|}

=== Potential issues ===
Inserters may have problems picking up items:

* From very fast belts, because the items are moving too quickly.
* From the entry or exit of an underground belt (because the time they have to pick up is shorter)
* From turning belts if the item is on the inside of the corner

== Power usage ==
* Electric inserters drain energy even when they are not moving, as idle power
* The amount of energy used is the same for every turn
* The [[burner inserter]] does not drain energy when idle, but uses more energy when it is active.

== Inserter speed ==
[[File:all_inserter_speeds.gif|frame|right|Animation showing all inserter speeds at once.]]
{| class="wikitable"
! Type
! Rotation-speed (turns per [[Time#Ticks|tick]]) Extension-speed ([[Map_structure#Tile|Tiles]] per Tick)
! Turns per [[Time#Seconds|Game-second]]
! Game-second per full turn
! Ticks per full turn
|- align="center"
| align="left"| {{Imagelink|Burner inserter|Burner inserter}} || 0.01 0.0214 || 0.60 || 1.667 || 100
|- align="center"
| align="left"| {{Imagelink|Inserter|Inserter}} || 0.014 0.03 || 0.83 || 1.2 || 72
|- align="center"
| align="left"| {{Imagelink|Long handed inserter|Long handed inserter}} || 0.02 0.0457 || 1.2 || 0.833 || 50
|- align="center"
| align="left"| {{Imagelink|Fast inserter}} {{Imagelink|Filter inserter}} {{Imagelink|Stack inserter}} {{imagelink|Stack filter inserter}} || 0.04 0.07 || 2.31 || 0.433 || 26
|-
|}

'''Note:''' These numbers come directly from the [https://github.com/wube/factorio-data/tree/master/base/prototypes/entity factorio-data github repository].

===Rotation Speed===
Convention: 2π rad = 100% of a circle rotation = '''1 turn''' (or one full rotation).

Note: an Inserter doesn't always need to make full turns. When grabbing from a transport belt, it is slightly faster when grabbing items from the closest lane.

===Extension Speed===
The extension-speed is normally not visible (only when compared to other inserters), but there are measurable speed differences when taking - for example - from the near or the far side of a belt. Also Some mods can alter the pickup and drop locations of inserters, making this stat more relevant.

==Inserter Throughput==

The following is based on experimental data from [https://docs.google.com/spreadsheets/d/1Q4hxL69qrK3qeEKU8aDkuwM3gJy6I2dJ4FYSs-FQUpI/edit?usp=sharing 0.17].
Most of the 0.17 experimental data was gathered using the following circuit blueprint to measure the exact tick difference between inserter swings. A lot of the data on this page (specifically the belt to chest data) relies heavily on the conditions of the setup on which the measurements are done. If your setup differs from the ones tested on this page, you can use the following blueprint to do the measurements yourself.

{{BlueprintString|bp-string=0eNrtXO1u2zYUfRcB+zPIG79JGd2APMdQGIrNNMJs2ZDlYEHgd58kp7ZM+Uq8qtyWSFEghSPpijznfvGQzlv0uD7YXZHlZTR/i7LlNt9H83/eon32JU/X9e/K152N5lFW2k0UR3m6qT+lRVY+b2yZLWfL7eYxy9NyW0THOMrylf0vmtNjPGhjv0nX69k63exaD7Lj5ziyeZmVmT2NpPnwusgPm0dbVJYHxhBHu+2+enqb1y+uLM5MHL1W//E/ZPWaVVbY5emqiKNqumWxXS8e7XP6klVPV49czC6qy6vG1L6+8JQV+3LRmdRLVpSH6jeXeTV3zB7qWe1tbaM2tC/TGmNK4mi7s0V6GkP0Z/Xc9lDuDjjLx2Mz+Pw0l2Z4tP5R2FUbtKz6xKs7s2J5yMrmIz1+rp5lwM1UVpePNXkO7AwNu/4xsNt0+dxCHkdXm5lPn0ZQc3o7gh3ZYSeOvhTW5gM0sguNN2+nCiCSo4lUP3P8/Hb3+KEuQ/HVZcYHmGDd+LvFi0DzIj52XlOYvNawdAt2iYad/8prHuyw/qjRYJ5TuDzHBECsQhPLPnaeE/2McTrAhPTLc/o8yq+T7WeFvrNyvM3CU7YubQH0rBAwJGqsHWqgZ5RonXBFmRnoXiFr9MoaN4Iywlmro8UYY1fGEkIITTS9WOMoa7xlrZon14IaJs7GBMqYuBoa1UYmiWhZkyhr8pqDRGjKubhYUyhrqmWNUcGZSdrGNMqYvhqalNQkTBhytmZQ1syVNcWpNIJJdbaWoKwlV9ZY9U9y07JGCcrcw82pXqydgn5sL3udQRK/BGGwiZt87D6IUkwjxCHYEyzs9Fcf5MEO3Oi4vA11OpwBzNUu9z7KlV1mK1v08lYRdmJOXPOmbvP2bvLbSEvz1/I5y7+css3XWCH1h80uLZqBzqO/RxBSQ94Y3b0umjy2eCq2m0WWV1ai+VO63luIrdus8H59hHVIg+j1XPdRtKD1wftUM9CnJgNx5FmGKFrxOgcW9wqsqXh5j4AOM3Xn3Gbm97HRhYsfAma1W+HUudshU3mSdVG1qtkv/51l+d4W1cKgy5LuX098fdtmu7KL7dOihWBLgStsulo8pye8y2owFSplcbCXO5qLzW21pcZNx4MITlvcEtO7a6jkNGeGGYMg0EsvksnGrrLDZmbXlcWiio7ddm3h19PRmhtY+ZTf/M3V/EHOz2E4IgpJf2n7FKGiiPWHBTUQINoPEH1/QOikgNAEmrFBuQC944zZtDNWDukCjIIERfo9IeDTQqBdCCAVlxE/CFRwiQAinVG/GcsxqV9DL2UomO/paWJamInradD2GePY6ifR1U8MNEV+zQHzbA5EaDEh++FhIHXSDxAeWnFkYLwqlAuEUxyZcEiXULfKNIr0cIojky4EYCLwbJFYaImAg6R7dkR0RHGU0AkZTlAwB1Qcjetp0J4rp9jiSNHF0fRnf0/BgPt1MiS0kEgGWgeQOe6FBw2tNHIwWgXGAcKpjNylXEJaAZcYysMpjJy7CEDaAVfjNk7Y99s4OW9v/CR7Jn5bIr36u/LcGOF+nVt4XQsYkAYz4XD6B+7KOAqScXiC7B84XlkeOM6ptZ/0LAhGeico2ctd3AjwzCjFDIIi5X+HNGhZLRhGgSV3dFs5rfrotr0Cap4Exwiw90RATS26OwhA3ZQQGB+4Z+rSkyIgOssLSGoREuMD4XRTwu2mFFS+hMKIw+HkAeb6gAAR0BhNHlUTmFunBNTUCoOh4Z6OaKZ1RHc/TIEIJBgaKHJnxGkXIAlKEoz0GlA0uDRIqEOSFKO8hlMVmesDEvxuCcP4QDhVUbq9oYYaVMkxPhBOVZSdZQMYBQKjCoeTB7jrAxJaH0iJEeNxVdFtUCXUnkmFoSGcqijdtaIGk5HG0ECRWyLOIKCVkjQI1TWgYHBZUGBbkCBE13BqInc9QEEVQRGEBwRUEl2xQENLZUURHhBQRXRTsYbqgWKjVHdyLbqz7ym68w42U4vu9eFhFN6K4U5O95/DVsL3zxD4qveKI8TsgDK9G+cKjHMxys3pD3RzF5u/xn2XY7KdpSEfd7X6oW8o37r/JnUS4bvh9IrKlfI0JGQphdlXwJ0tBUHXGAn5ntt9ybS6lfAVUJXBSMj3ROBhWr/T3W0ETylPJRgxkwVTRpTx1ZQ1wYiZuFCEUNcUo1uFE4qS+ao2mmF0q3BCUdOudumpH2iOUVDCCUXNfIUsLTAKCu5QKaRbaYlYLocTiYr4rha1QiyXAwrEG4KJZ3Om9aiFBfuBCws2wfr5YeTq+ZtWu93TQHGvpf5Vdv3V9PjbliYac0YsoCSsbi+rK7iavxk6b/2Z0jh6scX+dPLSaMaUMYSQ4/F/sZ3s5g==}}

===Chest to chest===

'''Note:''' Experimental data from 0.17

{| class="wikitable"
! rowspan=2 | Type
! rowspan=2 | Arm cycles per second
! colspan=6 | Items/second at [[inserter capacity bonus (research)|capacity bonus]] level (stack size)
|-
! colspan=2 | No capacity bonus
! colspan=2 | Capacity bonus 2
! colspan=2 | Capacity bonus 7
|- align="center"
| align="left"| {{Imagelink|Burner inserter|Burner inserter}} || 0.60 || 0.60 || (1) || 1.20 || (2) || 1.80 || (3)
|- align="center"
| align="left"| {{Imagelink|Inserter|Inserter}} || 0.83 || 0.83 || (1) || 1.67 || (2) || 2.50 || (3)
|- align="center"
| align="left"| {{Imagelink|Long handed inserter|Long handed inserter}} || 1.20 || 1.20 || (1) || 2.40 || (2) || 3.60 || (3)
|- align="center"
| align="left"| {{Imagelink|Fast inserter|Fast inserter}} {{Imagelink|Filter inserter|Filter inserter}} || 2.31 || 2.31 || (1) || 4.62 || (2) || 6.92 || (3)
|- align="center"
| align="left"| {{Imagelink|Stack inserter|Stack inserter}} {{imagelink|stack_filter_inserter|Stack filter inserter}} || 2.31 || 4.62 || (2) || 9.23 || (4) || 27.69 || (12)
|-
|}

===Chest to belt===

Throughput going from chest to belt depends on how full the belt is. An inserter will not put down an item on a belt that have items back-to-back (aka full compression) - it waits until there is a gap. However, if the gap is narrower than the item then the items upstream on the belt will stop to make room for the item being inserted. The direction of the belt compared to the inserter does not matter however.

In these measurements inserters move items onto an empty belt. Values are given for the stack sizes at three different [[inserter capacity bonus (research)|capacity bonus]] levels.

'''Note:''' Experimental data from 0.17

{| class="wikitable"
! rowspan=3 | Type
! colspan=12 | Items/second at [[inserter capacity bonus (research)|capacity bonus]] level (stack size)
|-
! colspan=4 | No capacity bonus
! colspan=4 | Capacity bonus 2
! colspan=4 | Capacity bonus 7
|-
! [[File:Transport belt.png|link=Transport belt]] || [[File:Fast transport belt.png|link=Fast transport belt]] || [[File:Express transport belt.png|link=Express transport belt]] ||
! [[File:Transport belt.png|link=Transport belt]] || [[File:Fast transport belt.png|link=Fast transport belt]] || [[File:Express transport belt.png|link=Express transport belt]] ||
! [[File:Transport belt.png|link=Transport belt]] || [[File:Fast transport belt.png|link=Fast transport belt]] || [[File:Express transport belt.png|link=Express transport belt]] ||
|- align="center"
| align="left"| {{Imagelink|Burner inserter|Burner inserter}} || 0.60 || 0.60 || 0.60 || (1) || 1.19 || 1.19 || 1.19 || (2) || 1.67 || 1.73 || 1.76 || (3)
|- align="center"
| align="left"| {{Imagelink|Inserter|Inserter}} || 0.83 || 0.83 || 0.83 || (1) || 1.64 || 1.64 || 1.64 || (2) || 2.25 || 2.37 || 2.43 || (3)
|- align="center"
| align="left"| {{Imagelink|Long handed inserter|Long handed inserter}} || 1.20 || 1.20 || 1.20 || (1) || 2.35 || 2.35 || 2.35 || (2) || 3.10 || 3.33 || 3.46 || (3)
|- align="center"
| align="left"| {{Imagelink|Fast inserter|Fast inserter}} {{Imagelink|Filter inserter|Filter inserter}} || 2.31 || 2.31 || 2.31 || (1) || 4.44 || 4.44 || 4.44 || (2) || 5.29 || 6.00 || 6.43 || (3)
|- align="center"
| align="left"| {{Imagelink|Stack inserter|Stack inserter}} {{imagelink|stack_filter_inserter|Stack filter inserter}} || 4.44 || 4.44 || 4.44 || (2) || 5.71 || 7.06 || 7.74 || (4) || 6.79 || 10.91 || 13.85 || (12)
|-
|}

===Belt to chest (perpendicular)===

'''Note:''' Experimental data from 0.17

When picking items from a belt, many more factors come into play besides belt fullness:

* How fast the items move (i.e. if they are queued up on the belt or move at belt speed).
* Whether the belt is perpendicular to the inserter or approaches it head on.
* Whether items are on the near or far lane of a perpendicular belt.
* Whether the belt turns or not, and whether the items are in the inner or outer side of the bend.
* If the belt is an underground entrance or exit. This shortens the time items are visible to the inserter for pickup.
* All sorts of intricate timing factors between the inserter and the items on the belt, since the game simulates the arm homing in on every item.

The test setup used below is with an inserter taking items from a perpendicular belt with items on the far lane only. The belt is fully compressed and timings are both for items that move at full speed and queued up as much as possible. Values are given for the stack sizes at three different [[inserter capacity bonus (research)|capacity bonus]] levels.

{| class="wikitable"
! rowspan=4 | Type
! colspan=15 | Items/second at [[inserter capacity bonus (research)|capacity bonus]] level (stack size)
|-
! colspan=5 | No capacity bonus
! colspan=5 | Capacity bonus 2
! colspan=5 | Capacity bonus 7
|-
! colspan=3 | Items at belt speed
! rowspan=2 | Items queued up
! rowspan=2 |
! colspan=3 | Items at belt speed
! rowspan=2 | Items queued up
! rowspan=2 |
! colspan=3 | Items at belt speed
! rowspan=2 | Items queued up
! rowspan=2 |
|-
! [[File:Transport belt.png|link=Transport belt]] || [[File:Fast transport belt.png|link=Fast transport belt]] || [[File:Express transport belt.png|link=Express transport belt]]
! [[File:Transport belt.png|link=Transport belt]] || [[File:Fast transport belt.png|link=Fast transport belt]] || [[File:Express transport belt.png|link=Express transport belt]]
! [[File:Transport belt.png|link=Transport belt]] || [[File:Fast transport belt.png|link=Fast transport belt]] || [[File:Express transport belt.png|link=Express transport belt]]
|- align="center"
| align="left"| {{Imagelink|Burner inserter}} || 0.60 || '''0.63''' || 0.50 || 0.64 || (1) || 1.11 || '''1.20''' || 1.13 || 1.26 || (2) || '''1.61''' || '''1.61''' || '''1.61''' || 1.86 || (3)
|- align="center"
| align="left"| {{Imagelink|Inserter}} || '''0.94''' || '''0.94''' || '''0.94''' || 0.88 || (1) || '''1.67''' || '''1.67''' || 1.50 || 1.74 || (2) || '''2.50''' || 2.25 || 2.25 || 2.54 || (3)
|- align="center"
| align="left"| {{Imagelink|Long handed inserter}} || 1.18 || 1.18 || '''1.25''' || 1.20 || (1) || 2.20 || 2.31 || '''2.40''' || 2.40 || (2) || 3.21 || 3.21 || '''3.46''' || 3.40 || (3)
|- align="center"
| align="left"| {{Imagelink|Fast inserter}} {{Imagelink|Filter inserter}} || '''2.50''' || 2.31 || '''2.50''' || 2.50 || (1) || 4.50 || 4.29 || '''5.00''' || 4.80 || (2) || '''6.43''' || 6.00 || '''6.43''' || 6.43 || (3)
|- align="center"
| align="left"| {{Imagelink|Stack inserter}} {{imagelink|Stack filter inserter}} || 4.50 || 4.29 || '''5.00''' ||4.80 || (2) || 7.50 || 7.50 || '''8.00''' || 7.50 / 8.57 / 8.28 * || (4) || 7.50 || 11.25 || '''15.00''' || 7.50 / 13.09 / 15.32 * || (12)
|-
|}

<nowiki>*)</nowiki> Throughput for basic/fast/express belt.

Since there are many more factors involved, these measurements exhibit a more complex pattern than chest-to-belt.

* Boldface cells show for which belt each inserter has the best throughput on each bonus level when items move at belt speed. Higher speed belts mean that inserters have to work harder to catch the fast moving items. The effect is most noticeable for slower inserters and smaller stack sizes.
* When items are queued up the belt type hardly matters, so there is only a single column for that. The exceptions are the stack inserters - for basic transport belts it's the belt that sets the limit for stack sizes above 4, and there is also a notable difference between fast and express belts.

=== Belt to Chest (facing inserter) ===

'''Note:''' Experimental data from 0.17

When picking up items from a belt facing the inserter, there are multiple small differences between different setups. The following throughput tests are performed with [[express transport belt]]s and [[stack inserter]]s with the maximum [[inserter capacity bonus (research)|capacity bonus]].
Each setup in the following picture shows the amount of ticks per cycle of the inserter and the amount of items per second the inserter moves. These measurements are consistent in all orientations of the setup.

[[File:Inserter_belt_to_chest_throughput.png|900px]]

==See Also==
* [[Electric system]]
* [[Belt transport system]]
* [[Inserter capacity bonus (research)]]: Inserter moves more than an item per turn.

{{C|Inserters}}

Lab

2019-11-07T12:14:35Z

Jon8RFC: fix redirect

{{Languages}}
{{:Infobox:Lab}}
[[File:Simplescience.png|thumb|right|Science packs put into the front lab will be passed to labs behind it.]]
'''Labs''' are buildings that perform [[research]] for [[technologies]] by consuming [[science pack]]s. Use of a lab is required to progress in Factorio.

When [[productivity module]]s are used in labs, the productivity bonus is directly calculated and applied each [[Time#Ticks|tick]] so the productivity bar is simply cosmetic. This means that it does not matter that the productivity bar resets when the research is changed, no productivity bonus is lost. [https://forums.factorio.com/26860]

The player can only research one technology at a time, but can use multiple labs for faster results. The speed bonus of labs when [[lab research speed (research)|lab research speed]] is researched and modules are present can be calculated using this formula: <code>research_bonus × module_bonus = speed_bonus</code>; the percentage bonuses have to be converted to decimals (e.g. +140% = 2.4) before the formula is used.

==Production requirements==
Calculating the number of science packs needed per second is straightforward:
* <code>ERS = (1 + B[r] ÷ 100) × (1 + M[r] ÷ 100)</code>
* <code>ACT = T[r] ÷ ERS</code>
* <code>PPS = N ÷ ACT</code>

Where:
*'''''ERS''''' is "effective lab research speed"
*'''''B[r]''''' is the Lab Research Speed bonus as reported by the game, in percent
*'''''M[r]''''' is the sum of all module speed effects (Speed modules - positive; Productivity modules - negative), in percent
*'''''ACT''''' is "adjusted cycle time"
*'''''T[r]''''' is the research cycle time as displayed in the research screen
*'''''PPS''''' is "packs per second"
*'''''N''''' is the number of labs available.

Thus, for a 10-lab setup, researching Nuclear Power (30 second cycle time) with Lab Research Speed 4 (140% bonus) and no module effects, the calculation is:
*<code>ELRS = 1 + (140 ÷ 100) = 2.4</code>
*<code>ACT = 30 ÷ 2.4 = 12.5 s</code>
*<code>PPS = 10 ÷ 12.5 = 0.8</code>

This means 0.8 science packs per second, of each type, would need to be produced to continuously supply the labs.

=== Equation simplification ===
Assuming all labs have the same ''B[r]'' (which they always will unless they are affected by different module configurations), the above calculations can be combined into one equation:

* <code>PPS = N × (1 + [B[r] ÷ 100]) × (1 + [M[r] ÷ 100) ÷ T[r]</code>

Thus for the numerical example:
* <code>PPS = 10 × (1 + [140 ÷ 100]) × 1 ÷ 30</code> = <code>(10 ÷ 30) × (1 + 1.4)</code> = <code> (1 ÷ 3) × 2.4</code> = <code> 2.4 ÷ 3</code> = <code>0.8</code> packs per second

== History ==
{{history|0.15.12|
* Lab speed info in the description contains the researched speed bonus as well.}}

{{history|0.12.6|
* The research speed of a lab is now not dependent on its electricity consumption, and can be scripted.}}

{{history|0.12.0|
* Lab research is now continuous; Science packs now have progress bars.}}

{{history|0.9.2|
* Labs are now named after early access backers when built from [[blueprint]]s.}}

{{history|0.7.2|
* Changed the recipe of Lab to require 4 transport belts, down from 5.}}

{{history|0.7.0|
* Added support for modules to labs.}}

{{history|0.6.0|
* New graphics.
* Labs are dedicated to backers (displayed in entity info).}}

{{history|0.2.7|
* Contents of the Lab is now shown in the entity info. }}

{{history|0.1.0|
* Introduced }}

==See also==
* [[Electric system]]
* [[Crafting]]

{{ProductionNav}}
{{C|Producers}}

Rocket silo

2019-11-07T12:13:54Z

Jon8RFC: fix redirect

{{languages}}
{{:Infobox:Rocket silo}}

The '''Rocket silo''' is currently the only win condition. Once the silo has been built and placed it can be filled with [[low density structure]]s, [[rocket fuel]], and [[rocket control unit]]s, which will allow [[rocket part]]s to be created within the silo.

In order to launch a rocket, 100 rocket parts need to be crafted. Each rocket part requires 10 low density structures, 10 rocket fuel, and 10 rocket control units.

When all rocket parts have been completed, the rocket silo interface is at 100% and allows the player to input an item as cargo. Launching the rocket empty or with any payload will complete the game, displaying a victory screen. The screen shows all kills and time played, and offers the player a choice of exiting the current game, continuing play, or viewing the replay.

Launching the rocket with a [[satellite]] as cargo produces 1000 [[Space science pack]]s, which are generated inside the silo. The silo interface includes the option to "Auto-launch with cargo", which will immediately, automatically launch the rocket if it is completed ''and'' cargo has been inserted as payload.

Building a silo requires, among other things, [[electric engine unit]]s, [[engine unit]]s, and [[processing unit]]s, which must be produced in [[assembling machine]]s and cannot be crafted by hand from raw materials. The rocket itself can also only be produced in the silo. The rocket silo accepts [[productivity module|productivity modules]], and due to the high resource requirements to craft a rocket is a good candidate for their use.

The rocket silo result inventory can hold up to 2000 space science packs (one stack), the equivalent of 2 full rocket launch results. When receiving science packs from a launched satellite, the game discards (destroys) all space science packs that exceed the capacity of the rocket result inventory. The "Auto launch with cargo" checkbox does '''not''' check if the rocket result inventory can hold the expected space science packs, this has to be manually ensured by the player, for example through the [[circuit network]].

== Maximum throughput ==

The duration of the rocket launch animation is 2475 [[Time#Ticks|game-tick]]s, or 41.25 seconds. This is the time from when the rocket is finished to when production on the next rocket can start, but does not include the time to insert the payload. Unlike rocket part crafting, the animation's duration is not affected by any modules or beacons. This may become a factor if one is planning to launch rockets at high frequency.

For example, to launch one rocket per minute using a single rocket silo, one would need to produce the rocket parts within (60 - 41.25 =) 18.75 seconds. However, the shortest crafting time achievable for 100 rocket parts in a single silo is ~20.6 seconds; i.e., slightly longer than what would be required to launch 1 rocket / minute. This crafting time is achieved using the maximum of 20 beacons with all [[speed module 3|speed modules 3]], plus 4 [[productivity module 3|productivity modules 3]] in the silo itself. The latter not only cuts resource requirements by almost 30%, but is also faster than using more speed modules 3 in the silo.

Thus, the largest space science pack output one can obtain out of a single rocket silo is about (1000 * 60 / 61.85 =~) 970 per minute.

== Achievements ==

The rocket silo, which is used to win the game, is directly connected to the following game-win-based achievements:
{{Achievement|smoke-me-a-kipper-i-will-be-back-for-breakfast}}
{{Achievement|no-time-for-chitchat}}
{{Achievement|there-is-no-spoon}}
{{Achievement|raining-bullets}}
{{Achievement|steam-all-the-way}}
{{Achievement|logistic-network-embargo}}
{{Achievement|so-long-and-thanks-for-all-the-fish}}

== Trivia ==

The rocket can, technically, accept any item as cargo; however, most will do nothing in particular and simply waste the launch. Notable exceptions include:

{{Spoiler|button-text=Spoiler! Click to view.|message=
<ul><li> [[Vehicle]]s : When a vehicle is inserted into the payload slot, the player can enter the rocket like they would any other vehicle, then launch and ride it.
<ul><li> This allows a fast-moving view of one's base (as the game world is internally 2-dimensional, the rocket actually simply moves north along the map), and then returns the player next to the launching silo once the launch animation has finished.
<ul><li> If all space near the rocket silo is occupied, the player is placed at spawn instead. </li></ul>
<li> It also wastes the launch, as the rocket's sole payload slot is occupied by the vehicle, rather than a satellite. (Having any number of satellites in the car's trunk or the "astronaut"s inventory does not count.) </li></ul></li>
<li>[[Raw fish]]: Grants the "So long and thanks for all the fish!" achievement. Other than this, it also wastes the launch.</li></ul>}}
== History ==

{{history|0.17.0|
* Updated sprite and changed dimensions from 9×10 to 9×9. A satellite is no longer required to win the game.}}

{{history|0.13.9|
* Rocket parts from building rockets in the silo now show in production statistics.}}

{{history|0.12.7|
* Updated icon.}}

{{history|0.12.4|
* Rocket silo now behaves correctly when out of electricity.}}

{{history|0.12.0|
* Introduced}}

== See also ==
* [[Satellite]]

{{CombatNav}}
{{C|Defense}}

User:Jon8RFC

2019-11-07T12:11:58Z

Jon8RFC:

Interested in low-priority upkeep of grammar, punctuation, redirects, and adding to the History section.

I'll try to resist using oxford commas if it looks bad, stylistically--or if the rest of the page is flush without them--but I prefer them.

Map generator

2019-11-07T12:10:58Z

Jon8RFC: fix redirect

{{Languages}}
[[File:Default_123456789.png|thumb|right|An example how the world generator might create a new map: Default settings with map seed 123456789]]
World generation is the procedure by which the in game landscape is generated. In short: a number of settings, editable at the start of a new world, define what that world will look like. This can dramatically alter gameplay — a new player is advised to start with the default settings before deciding to change their world.
__TOC__{{Clear}}
== Map generation presets ==
[[File:MapGeneratorOverview.png|thumb|right|400px|Overview of the map generation screen]]
A preset may be chosen in the top left dropdown instead of manually configuring the generation.
=== Default ===
Normal settings. The recommended way to play Factorio.

All sliders are set to the center position. Map height and width is unlimited, peaceful mode is disabled.

All other settings are set to their defaults:
{| class="wikitable"
|-
! Enemy expansion !! Default !! Evolution !! Default
|-
| Enabled || Yes || Enabled || Yes
|-
| Maximum expansion distance || 7 || Time factor || 40
|-
| Minimum group size || 5 || Destroy factor || 200
|-
| Maximum group size || 20 || Pollution factor || 9
|-
| Minimum cooldown (Minutes) || 4
|-
| Maximum cooldown (Minutes) || 60
|-
|}

{| class="wikitable"
|-
! Pollution !! Default !! Recipes/Technology !! Default
|-
| Enabled || Yes || Recipe difficulty || Normal
|-
| Absorption modifier || 100% || Technology difficulty || Normal
|-
| Attack cost modifier || 100% || Technology price multiplier || 1
|-
| Minimum damage to trees || 60 || Research queue availability || After the game is finished
|-
| Absorbed per damaged tree || 10 ||
|-
| Diffusion ratio || 2% ||
|-
|}

=== Rich resources ===
Resources patches have a larger richness, so you don't have to expand far.

Difference from default: Resources have 200% richness instead of 100%.

=== Marathon ===
Recipes and technologies are more expensive.

Difference from default: Expensive recipes and technology, technology price multiplier 4.

=== Death world ===
Biters are more dangerous and evolve faster.

Difference from default: 200% enemy base frequency and 200% enemy base size, 75% starting area size, enemy evolution time factor is set to 200, pollution factor is set to 12. The pollution absorption modifier is set to 50% instead of 100%, same goes for the attack cost modifier.

=== Death world marathon ===
Recipes and technologies are expensive and biters are dangerous and plentiful. Only select this if you are a Factorio veteran.

Combines "Marathon" and "Death world" with some additional changes: Enemy evolution time factor is set to 150, pollution factor is set to 10. Attack cost modifier is set to 80% instead of 100% (50% for death world).

=== Rail world ===
Resource patches are large and spread far apart, to encourage train systems. Biters won't create any new bases or re-expand into cleared territory.

Difference from default: All resources are set to 33% frequency and 300% size. Water is set to 200% scale and 150% coverage. The evolution time factor is set to 20 from 40 and enemy expansion is disabled.

=== Ribbon world ===
The map height is limited to only 128 tiles, which introduces a range of challenges and interesting situations.

Difference from default: Map height is limited to 128. All resources are set to 300% frequency, 50% size and 200% richness. Water is set to 25% coverage and size. Starting area size is increased to 300%.

=== Island ===
A large island in an endless ocean.

Difference from default: Terrain map type is set to island.

== Manual configuration ==
It is possible experiment with different settings by opening the map preview, changing the settings and observing their effects. This makes it possible to directly observe what exactly particular settings modify in the world, beyond the textual descriptions provided on this page.

The seed is the starting value for the random number generator that Factorio uses for generating the world based on the generation settings. This means that even with the same generation settings, the world can look very different depending on the seed.

All resources and terrain features can be disabled by unchecking the checkbox in front of them.

=== Resources ===
Frequency determines the number of resource patches in a given area. It does not affect resource patch size or richness. A setting of 200% frequency that means roughly double the patches can be found in a given area.

The size setting adjusts the size of the resource patches. Setting the slider to 200% means the surface area of the patch is doubled.

Richness defines the yield of every ore tile and every oil field. If richness is set to 200%, each ore tile and oil field contains about double the amount of ore/oil. Outside of this, resource patch richness increases by distance.

=== Terrain ===
Setting the map type to island generates a single island around the spawn point and endless ocean beyond that. The normal map type generates endless terrain.

Water scale changes how much space there is between lakes. The smaller the scale, the swampier the terrain. Higher scale leads to bigger oceans separated by bigger landmasses. Water coverage influences the overall amount of water. Reducing it generates small lakes, increasing it generates large oceans.

The settings for trees behave in the same way. Higher scale increases the distance between forests while lower scale reduces it. High tree coverage allows to completely cover the world in trees, and low coverage nearly removes them from the world.

Cliff frequency influences how many cliff lines there are in the world. Higher frequency means more cliffs, lower frequency reduces their number. The continuity setting changes how long and unbroken the cliff lines are. Low continuity leads to very short lines, high continuity to long, nearly unbroken lines of cliffs.

The moisture settings control the distribution of grass versus desert. Higher bias generates more grass, lower bias generates more desert. Higher scale increases the size of the grass/desert areas, low scale leads to small grass and desert patches.

The terrain type setting controls the distribution of red desert versus sand. Higher bias generates more red desert, lower bias generates more sand. Higher scale increases the size of the red desert/sand areas, low scale leads to small red desert and sand patches.

=== Enemy ===
[[File:MapGeneratorEnemy.png|thumb|right|400px|The enemy tab]]
Frequency determines the number of enemy bases in a given area. It does not affect enemy base size. A setting of 200% frequency that means roughly double the enemy bases can be found in a given area.

The size setting adjusts the size of enemy bases. Setting the slider to 200% means the surface area covered by the enemy bases is doubled.

When peaceful mode is turned on, the [[enemies]] don't begin fights, only responding if the player hits them. Additionally, when a map is in peaceful mode, the enemies will not [[Enemies#Expansions|expand]].

The starting area is the an almost circular radius around the spawn point that does not contain enemy bases. Increasing its size pushes the bases further out, decreasing its size generates enemy bases closer to the spawn point. The size setting does not have any other effects.

[[Enemies#Expansions|Enemy expansion]] can be enabled/disabled and further adjusted using the below settings.

{| class="wikitable"
|-
! Enemy expansion setting !! Description
|-
| Maximum expansion distance || The maximum distance enemies will look to expand from other enemy bases.
|-
| Minimum group size || The minimum size of an enemy expansion party modified by the current evolution level.
|-
| Maximum group size || The maximum size of an enemy expansion party modified by the current evolution level.
|-
| Minimum cooldown (Minutes) || The minimum time between enemy expansions being sent out.
|-
| Maximum cooldown (Minutes) || The maximum time between enemy expansions being sent out.
|-
|}

[[Enemies#Evolution|Evolution]] can be enabled/disabled and further adjusted using the below settings.

{| class="wikitable"
|-
! Evolution setting !! Description
|-
| Time factor || Controls how fast evolution increases over time.
|-
| Destroy factor || Controls how fast evolution increases due to destroying enemy spawners.
|-
| Pollution factor || Controls how fast evolution increases due to producing pollution.
|-
|}

=== Advanced ===

The [[Replay system|replay]] can record all the actions that the player(s) perform during the game, so that they can later be played back as essentially a timelapse of the save file.

The map width and height allows to generate maps with finite resources and area. It is possible to limit generation in only direction, alike the [[#Ribbon world|ribbon world]].

The difficulty settings allow to change the [[Crafting#Recipe difficulties|recipe]]/technology difficulty and multiply the [[research|technology cost]]. Currently, setting the technology difficulty does not have an effect in vanilla. Furthermore, it can be controlled when the research queue is available: From the start, after launching a [[rocket silo|rocket]] or never.

[[Pollution]] can be enabled/disabled and further adjusted using the below settings.

{| class="wikitable"
|-
! Pollution setting !! Description
|-
| Absorption modifier || Modifier of how much pollution is absorbed by trees and tiles.
|-
| Attack cost modifier || Modifier of how much pollution is absorbed by enemy attacks.
|-
| Minimum damage to trees || Trees have 4 different stages of the progression towards being destroyed by pollution. Any pollution above this amount starts the process of moving a tree towards a more damaged stage.
|-
| Absorbed per damaged tree || Trees have 4 different stages of the progression towards being destroyed by pollution. This value specifies how much pollution is absorbed when moving to a more damaged stage.
|-
| Diffusion ratio || The amount of pollution diffused into neighboring chunks per second.
|-
|}

=== Map exchange string ===

A map exchange string generally looks like this:

>>>eNp1UTGIE0EU/WMu3F4EUUjhgR4prrDZJTlFJRyZURAR0d7Oz
WYiA5udOLsLnhaX4kptxEaraz3hOgu7wIEoKBxa2UVsLFROBC0U4
p+dnWSNdw/+583/f97/fwbgGLhAADGgAEPqzAXSD/HI8JRZJZD9P
leuVNyGtC0EKu1wV4qwGK3wiPfW3LYfc6NozBFKRv8qMFaOExnlE
WDPtrZoOVGcx3igxgb0cKr8SKQ9c1eL5aOSGIcebCxlNl6H2nisD
dkIC0YAtpIQjOWYOx7IKFEydGOeJCK61fTTO8228OMFt+416hqn9
ivpKn475VGw1uylYSL6oeDKqXtnNc6dnL3RkyJOUsUzZccKuweW7
ave8E5nKAeh6HYBahfQLuotCJB71e3LH+8+osTs5bGc7OWRYdtGr
lhynR2YWrbkTEHHdP9RIKZpgi3yKodNiUlu6CQhD74+3/z1crdF/
jz9/u5a+yYljUvVb3sr2y1MzusVDk3ck8caL+wqYDVHNE99oOTtG
40vlJT1jap27Dy64dUSkKNHkG3eR1c7AXa0lpWpMtLN8NNu8smS9
3R2D3yIVS2+pN0r7bKGk8lITm8wk1icZvHqChTbd6bLvbYddwqtZ
2b4/w+KK8xElgsPX9F9OhP3uTQZAl9wd96e2DorwRT4wTu/vYd/A
dl73Kk=<<<

The map exchange string can be used to share all map generation settings between different players. The player can paste the string (using {{Keybinding|ctrl|V}}) into the map exchange string field and the game will set the generation settings to the settings saved in the string, resulting in a complete copy of the map when generated.

The map exchange string can be retrieved from save files by going into the load game screen, selecting the desired map, clicking the map exchange string button in the upper right corner and copying the string from the window that pops up.

For a technical description of the map exchange string, see [[map exchange string format]].

== Mechanics ==

=== Starting area ===

There is a second internal starting area that is completely separate from the starting area that can be changed in the enemy settings tab. This starting area always has a constant size and affects the spawning of resources, cliffs and water directly at the spawn. The map generation logic makes sure that there is always at least one path of [[coal]], [[iron ore]], [[copper ore]], and [[stone]] each. Furthermore, there is always a lake in the starting area, even when water is turned off, and there are never any cliffs there. [[Uranium ore]] and [[crude oil]] do not spawn in the starting area. The richness of the ore patches is slightly influenced by the frequency setting.[https://forums.factorio.com/viewtopic.php?p=432592#p432592]

=== Chunks ===

A map is endless by default, though its size can be limited by height and width — see above. Because it is technically endless, the whole map is not generated from the start. Instead, a new [[Map_structure#Chunk|chunk]] of the map is generated only when needed, similar to other procedurally generated world games.

==== Invisible chunks (fog of war) ====

Outside of the visible chunk area, an invisible area of about 3 chunks wide is generated as a preloading mechanism. Enemies may be located inside these invisible chunks and can attack the player from there, while [[artillery turret]]s and [[artillery wagon|wagon]]s may automatically shoot enemy bases in these chunks if they are within their automatic range. Invisible chunks are also generated if pollution is generated heavily; the game generates (invisible) chunks as it needs to spread the pollution into the area.

==== Charting (removing fog of war) ====

As long as a chunk is invisible, the part of the players map stays black. This changes when a chunk is [[Radar#Charting|charted]], which means when it is "touched" by a radar. This can be either the player's internal radar, which is always available and continually charts chunks around the player, or the [[radar]] entity. If a far-away and thus ungenerated chunk is charted, it will be generated, together with the above-mentioned invisible 3 chunk radius of map around it.

==== Maximum map size and used memory ====

The map size is limited to 2,000 x 2,000 kilometers; internally, this is a square 2,000,000 tiles on a side, with an area of 4,000,000,000,000 (4 trillion) square tiles (assuming 1 tile = 1 meter on a side yields 2,000 x 2,000 km = 4 million square km). In real-world terms, this is between the sizes of India and Australia (or about 40% the area of the United States, or over 10 times the area of Germany). It would take around 200 [[game-second|game-minutes]] (ca 3.3 hours real time) to reach that border from the center when riding a [[locomotive|train]] fueled with [[rocket fuel|rocket]] or [[nuclear fuel]]. This makes the world essentially endless for practical purposes. The generated chunks are fully mapped and stored in the player's RAM, which is the practical limiting factor of exploration.

Because chunks are only generated in and close around the area revealed by radar, it is possible to reach that border without overloading your computer, as the size of the map in computer memory is dependent only on chunks actually generated. If only a narrow stripe of land is explored to far away, this remains manageable.

== History ==

{{History|0.17.44|
* The resource frequency slider in the map generator settings has a smaller influence over the amount of ore in the starting area patches.
}}

{{History|0.17.0|
* Resource generation changed significantly:
** The starting area contains only iron, copper, coal and stone, in very predictable amounts. Uranium and oil are excluded from the starting area.
** Resource generation settings now have a much more dramatic effect. Increased the number of steps for each setting.
** Ore patches are slightly less frequent but richer.
** There will be a more balanced amount of resources within a large enough region.
** Many other small tweaks.
* Biter generation changed significantly:
** Biter richness slider removed, biter placement is only configured by size and frequency settings.
** Biter generation settings now have a much more dramatic effect. Increased the number of steps for each setting.
** Biter bases will increase in size, frequency and number of worms depending on the distance from player spawn.
** Worm size increases depending on the distance from player spawn.
** Small biter bases are now closer to the player spawn.
** At large distances from player spawn, biter base frequency is lower than before but biter bases are larger.
** Other small tweaks.
* Terrain generation changed significantly:
** Water is generated as large lakes instead of swamps.
** Tile generation improved. Tile placement respects biomes better.
** More predictable cliff placement.
** Better controls in the map generator GUI for water, tiles and cliffs.
* New map terrain type selectable: Island. Launch the rocket with only a limited amount of resources available on the map.
}}

{{History|0.16.0|
* Added cliffs.
* New terrains and new terrain generation.
* Trees can now be configured in the generate-map GUI.
* Terrain can be configured in the generate map GUI.
* Biters scale less with distance and there are generally less biters.
* No uranium as a starting resource also no uranium is ever generated near the starting area, you need to go look for it.
}}

{{History|0.15.0|
* Extended map generator settings to include an advanced section.
* Added map generator presets.
* The map seed is used to generate unique maps instead of just shifting the starting position.
}}

{{History|0.13.7|
* Map size is now limited to 2000 km by 2000 km with a black bar rather than crashing when reaching this distance.
}}

{{History|0.13.0|
* Map generator algorithm changed, further resource field now have greater richness.
}}

== See also ==

* [https://forums.factorio.com/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [https://forums.factorio.com/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)

Player

2019-11-07T12:09:46Z

Jon8RFC: fix redirect

{{Languages}}{{:Infobox:Player}}
Factorio is played from the angled top down perspective of the ''player''.

The ''physical representation'' (or the '''Engineer''') of the player is the ''character'', who is always at the center of view. In multiplayer, player characters will appear in different colors. Color can be set manually with the <code>/color</code> command, see [[Console#Change_Player_color|Console]]. These colors transfer to any entered [[car]] or [[tank]], depending on which player is driving them. These colors also transfer to [[gun turret]]s, [[laser turret]]s or [[gate]]s, depending on who they were placed by.

The character is '''part of the player''' and represents the physical existence of the player in the game-world. In technical terms: A character is just one property of the [[player]], and it is the only that can be controlled at a time.

The character's maximum [[Damage|health]] is 250 (without energy shields). The character's main inventory has 80 slots (without bonuses from [[Power_armor|power armor]], [[Toolbelt_(research)|toolbelt research]], or [[Character_logistic_trash_slots_(research)|logistic trash slots]]). Similar to the stationary radar, the character constantly reveals an area of 5×5 [[Map_structure#Chunk|chunks]], centered on the chunk the character occupies.

== Distinction between player and character ==

[[File:twoplayers.png|thumb|right|180x180px|Two different color characters in multiplayer.]]

Technically the player is only the "player-view". The player is unlike the ''character'', (the little person that runs around on the ground) The character is part of the player, but the player is not just the character.

You can for example play in god-mode (such as in the sandbox game mode). In that mode you don't have a character, only a player.

In other words, the Player is a term that encompasses both the internal code that defines a player, and the entity in game that interacts with machines/rocks/trees, which is the ''character''. While this distinction is important for modding and understanding the game's core, the terms can be used interchangeably for most conversations. For the purpose of this article, "player" will be used.

== World interaction ==
The player has six primary ways of interacting with the world:

# Crafting items personally from resources using the craft menu (Default open key: E)
# Placing entities or [[tile]]s by selecting them from the inventory or quickbar (Default: Left Mouse Button)
## Opening contextual menus for entities like [[Assembling machine|Assembly Machines]] or [[Chests]], using the same button
## Removing an entity from the world, returning it to your inventory (Default: '''Hold''' Right Mouse Button)
# Harvesting resources from a resource entity (Default: '''Hold''' RMB)
# Picking up non-placed items from the ground and placing them in your inventory (Default: Hold/press F)
# Firing weapons at enemies (Default: Press or hold Spacebar depending on weapon)
# Passively with a flashlight that automatically turns on during the night time (which transfers to headlights if the player is in a vehicle.)

''For more key-bindings, see [[Keyboard bindings]]''

Note: The player can do that only, if his character owns the abilities for this. For example: He cannot fire a weapon, cause he has no weapons-slots.

== Death ==
When a player is killed, it leaves behind a corpse that lasts 15 minutes and contains all items that were located in the player's inventory, quickbar, trash slots, and equipment slots. 10 seconds after being killed, the player respawns at the center of the world.


== Quickbar and shortcut bar ==
{{Main|Quickbar}}
The quickbar is a user interface component for creating links to items that are always visible at the bottom of the screen. Once created they can be quickly selected at any time without needing to open the inventory. It shows between one and four bars from a set of ten available, each containing 10 slots. Clicking any filled slot will place the chosen item in the player's hand if available in the inventory.

{{Main|Shortcut bar}}
The shortcut bar is a group of icons for accessing regularly used features such as obtaining [[blueprint]]s and [[deconstruction planner]]s with a simple mouse click. It is always visible at the bottom of the screen, appearing to the right of the quickbar. The icons can be hidden and their order can be changed. A maximum of 12 icons can be visible at one time.

[[File:Quickbar and shortcut bar.png]]

== Gallery ==
<gallery mode="packed" heights=120px>
File:playerportrait.png|Portrait of the player character; seen when selecting the "First steps" campaign.
File:All_armor.png|The player character in every type of armor.
File:Multicolor_all.png|Different possible colors of players, cars, tanks, gun turrets and laser turrets. (Pre 0.17)
File:Playerflashlight.png|The player character's flashlight during the night.
File:dead_player.png|The player's corpse.
</gallery>

== History ==

{{history|0.13.14|
* Surplus items from crafting are again available for crafting other items. For example, crafting two green circuits will no longer result in two extra copper wires in the player's inventory. This only applies to items that are automatically crafted as a prerequisite; items the player has explicitly requested to craft will not be used to satisfy the dependencies of any further orders.}}

{{history|0.13.0|
* Armors have inventory size bonuses (10 for modular armor, 20 for power armor, 30 for power armor mk2).}}

{{history|0.12.1|
* Changed fast inventory transfer from the main player inventory so ctrl+clicking empty slots doesn't move items to the logistic trash slots.}}

{{history|0.12.0|
* New muzzle flash graphics.}}

{{history|0.11.4|
* Improved player running animation.}}

{{history|0.11.0|
* New player animation, depends on armor}}

{{history|0.10.9|
* Mining a chest now fails instead of spilling items onto the ground.}}

{{history|0.9.0|
* Player gets a separate warning icon when a building is destroyed.
* Recipe gui contains recipes not craftable by player (however, their tooltip shows machines where they can be crafted).}}

{{history|0.8.0|
* Player now starts with 1 [[burner mining drill]] and one [[stone furnace]] in the freeplay.
* The player can repair structures using [[repair pack]]s.}}

{{history|0.7.0|
* Player moves slower while shooting.}}

{{history|0.6.0|
* Added the ability for the player to request items directly from logistic robots.}}

{{history|0.5.0|
*Player picks all items in range when picking items on the ground, instead of 1 per tick
* Shooting particles added}}

{{history|0.4.0|
* Player slides around corners}}

{{history|0.2.8|
* Player no longer collides with [[Underground belt]].
* Added auto-targeting for guns.}}

{{history|0.2.1|
* Added warning message when the player tries to build in an invalid position.}}

{{history|0.2.0|
* Screen reddens when taking damage
* Character animations added}}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Armor]]
* [[Weapons]]
* [[Multiplayer]]

Debug mode

2019-11-07T12:06:55Z

Jon8RFC: /* List of debug-options and their function */ fix redirects

{{Languages}}
The ''debug mode'' is used mainly by developers and modders to analyze the running state of the game. It can be enabled to show detailed information about the game world. The default key to enable debug mode is {{keybinding|F5}}.

For example, one can:
* See the path the [[Enemies#Biters|biters]] are coming from and where they plan to target,
* See the position / coordinates of the cursor,
* See a grid-overlay for the [[map structure|tile]]s and [[Map_structure#Chunk|chunks]],
* See the blocks in a railway network,
* See additional non-game related information, such as Updates Per Second and FPS.

== Activate the debug mode ==

There are 4 debug-levels:

* '''Always''' - This is the default mode, if no mode is active. Keep very few things active here.
* '''Debug''' - Toggled by pressing {{keybinding|F5}}. Allows to toggle the debug overlays.

== Configuring the debug mode ==

To configure the 2 modes, press {{keybinding|F4}}. This opens up a menu with many options. You can move this menu with the mouse, if it hides some interesting underlying thing. You can switch between 2 folders, which reflects the option for that debug-mode ("always", "debug"). The options are the same for each mode. Each mode can be configured to the user's liking, the different modes are only for convenience. A search function ({{Keybinding|ctrl|F}}) is available.

== List of debug-options and their function ==
{| class="wikitable"
|-
! Option !! Description
|-
| show-fps || Will show the current frames-per-second and updates per second, short <abbr title="Frames Per Second">FPS</abbr> and <abbr title="Updates Per Second">UPS</abbr>. Should be normally about 60.
|-
| show-detailed-info ||
* Shows the cursor position in [[Map_structure#Tile|tiles]] (and subdivisions of that).
* Current resolution and zoom.
* How many objects are on the screen (painted by the graphic card).
* How many entities, chunks and paths are in the game and used.
|-
| show-time-usage ||
* Internal statistics about how long some calculations take, in milliseconds per [[Time#Ticks|tick]].
* Time is shown as average/min/max of the last 100 ticks, interval can be changed with /perf-avg-frames.
* Minimum values exclude zeroes (e.g. from ticks where no mod hooks were run).
* Overall calculation delays (some are parallel) must be under 16.6 ms to maintain normal framerate at 1x speed with 60 ticks per second.
* The Top section of metrics cover the wider game engines activities. The middle Update section relates to running the simulation for a tick. The bottom Map Generator section relates to the map generation activity.
|-
| show-gpu-time-usage ||
|-
| show-sprite-counts || The counts of each sprite rendered on screen.
|-
| show-lua-object-statistics ||
|-
| show-multiplayer-waiting-icon || When in a multiplayer game: if the game is currently waiting for the server to process.
|-
| show-multiplayer-statistics || The latency information when in multiplayer.
|-
| show-multiplayer-selection-rectangles || Allows to view selection rectangles of other players in multiplayer.
|-
| show-debug-info-in-tooltips || Shows additional information in the tooltips of entities, items, recipes, tiles etc.
|-
| hide-mod-guis || Hides GUIs added by mods.
|-
| show-tile-grid || Shows the borders of the [[Map_structure#Tile|tiles]] and [[Map_structure#Chunk|chunks]].
|-
| show-collision-rectangles || Shows the collision boxes of each entity (red).
|-
| show-selection-rectangles || Shows the a blue box over each entity, if you hover over it, it will be selected.
|-
| show-render-rectangles || Shows the a pink box over each entity, if that is on your screen, the entity will be rendered.
|-
| show-entity-positions ||
|-
| show-entity-velocities ||
|-
| show-selected-entity-advanced-tiles || Shows on which advanced tiles (2×2 tiles) the entity is registered.
|-
| show-selected-input-transport-belts || Shows which entities input into the selected transport line.
|-
| show-paths || The calculated paths for the biters in different colors.
|-
| show-path-requests ||
|-
| show-next-waypoint-bb || Shows waypoints for biters (in green), nearly the same info as the next.
|-
| show-target || Shows the current target of the biters (red).
|-
| show-unit-group-info || Biter groups, which belong together (circles and lines belonging together)
|-
| show-unit-behavior-info ||
|-
| show-pathfinder-fringe ||
|-
| show-path-cache || The source-positions of a path and about the length (?)
|-
| show-path-cache-paths ||
|-
| show-rail-paths || Which path a train will follow.
|-
| show-rolling-stock-count || Shows inserter positions
|-
| show-rail-connections || Shows rail connections.
|-
| show-rail-joints ||
|-
| show-rail-signal-states || Shows signal color on map view.
|-
| show-rail-segment-collision-boxes ||
|-
| show-train-stop-point || When a train slows down it shows the calculated point where it should halt
|-
| show-train-braking-distance || The distance a train will take to stop at its current speed
|-
| show-train-signals ||
|-
| show-train-repathing || Display a flying "repathed" text over a train whenever it repaths.
|-
| show-network-connected-entities || Displays the network-id of the electric network that a pole is connected to
|-
| show-circuit-network-numbers || Shows the number (and color) of circuit networks
|-
| show-energy-sources-networks || Which network-id an entity is connected to.
|-
| show-active-state || Inserters, fish, turrets are turned to passive, if not used; Red = inactive, Purple = inactive when enemies aren't around (turrets etc), Green = inactive when player isn't around (fish). Passive entities consume less CPU power.
|-
| show-wakeup-lists || When an entity is sleeping in another entity it shows which entities it's sleeping in.
|-
| show-transport-lines ||
|-
| show-transport-line-gaps ||
|-
| show-pollution-values || Shows the numeric pollution amount on each chunk.
|-
| show-active-entities-on-chunk-counts ||
Shows counts of active entities per chunk. They are devided into three categories:
* Red = active (e.g. furnaces)
* Blue = active when a player is around (e.g. fish)
* Green = active when enemies are around (e.g. turrets)
|-
| show-active-chunks || Shows in the map view, which chunks are "on", unmarked chunks are not calculated.
|-
| show-polluted-chunks || Shows which chunks have pollution.
|-
| show-enemy-expansion-candidate-chunks || Where is space left to spread the brood?. Goes from red (nearly no space) to green (space to expand).
|-
| show-enemy-expansion-candidate-chunk-values || Which chunks the enemies will try to expand into.
|-
| show-bad-attack-chunks ||
|-
| show-tile-variations || Shows, which tile-variation (1, 2 or 4 tile sized) is painted for which area of the map. Quite confusing, zoom in to see the meaning.
|-
| show-raw-tile-transitions || Turns connected textures for land and water off, so the distinction can easily be made.
|-
| show-fluid-box-fluid-info || How much fluid is in a pipe/storage tank, shows flow of liquid in pipes.
|-
| show-environment-sound-info || Displays which sound of which entity is played and how loud.
|-
| show-logistic-robot-targets ||
|-
| show-logistic-robots-on-map ||
|-
| show-recipe-icons-on-map ||
|-
| show-player-robots ||
|-
| show-fire-info ||
|-
| show-sticker-info ||
|-
| show-decorative-names ||
|-
| show-decorative-collision-rectangles ||
|-
| allow-increased-zoom ||
|-
|}

Debug mode

2019-11-07T12:02:12Z

Jon8RFC: fix redirect

{{Languages}}
The ''debug mode'' is used mainly by developers and modders to analyze the running state of the game. It can be enabled to show detailed information about the game world. The default key to enable debug mode is {{keybinding|F5}}.

For example, one can:
* See the path the [[Enemies#Biters|biters]] are coming from and where they plan to target,
* See the position / coordinates of the cursor,
* See a grid-overlay for the [[map structure|tile]]s and [[Map_structure#Chunk|chunks]],
* See the blocks in a railway network,
* See additional non-game related information, such as Updates Per Second and FPS.

== Activate the debug mode ==

There are 4 debug-levels:

* '''Always''' - This is the default mode, if no mode is active. Keep very few things active here.
* '''Debug''' - Toggled by pressing {{keybinding|F5}}. Allows to toggle the debug overlays.

== Configuring the debug mode ==

To configure the 2 modes, press {{keybinding|F4}}. This opens up a menu with many options. You can move this menu with the mouse, if it hides some interesting underlying thing. You can switch between 2 folders, which reflects the option for that debug-mode ("always", "debug"). The options are the same for each mode. Each mode can be configured to the user's liking, the different modes are only for convenience. A search function ({{Keybinding|ctrl|F}}) is available.

== List of debug-options and their function ==
{| class="wikitable"
|-
! Option !! Description
|-
| show-fps || Will show the current frames-per-second and updates per second, short <abbr title="Frames Per Second">FPS</abbr> and <abbr title="Updates Per Second">UPS</abbr>. Should be normally about 60.
|-
| show-detailed-info ||
* Shows the cursor position in [[Tile (unit)|tile]]s (and subdivisions of that).
* Current resolution and zoom.
* How many objects are on the screen (painted by the graphic card).
* How many entities, chunks and paths are in the game and used.
|-
| show-time-usage ||
* Internal statistics about how long some calculations take, in milliseconds per [[Game-tick|tick]].
* Time is shown as average/min/max of the last 100 ticks, interval can be changed with /perf-avg-frames.
* Minimum values exclude zeroes (e.g. from ticks where no mod hooks were run).
* Overall calculation delays (some are parallel) must be under 16.6 ms to maintain normal framerate at 1x speed with 60 ticks per second.
* The Top section of metrics cover the wider game engines activities. The middle Update section relates to running the simulation for a tick. The bottom Map Generator section relates to the map generation activity.
|-
| show-gpu-time-usage ||
|-
| show-sprite-counts || The counts of each sprite rendered on screen.
|-
| show-lua-object-statistics ||
|-
| show-multiplayer-waiting-icon || When in a multiplayer game: if the game is currently waiting for the server to process.
|-
| show-multiplayer-statistics || The latency information when in multiplayer.
|-
| show-multiplayer-selection-rectangles || Allows to view selection rectangles of other players in multiplayer.
|-
| show-debug-info-in-tooltips || Shows additional information in the tooltips of entities, items, recipes, tiles etc.
|-
| hide-mod-guis || Hides GUIs added by mods.
|-
| show-tile-grid || Shows the borders of the [[Tile (unit)|tile]]s and [[chunk]]s.
|-
| show-collision-rectangles || Shows the collision boxes of each entity (red).
|-
| show-selection-rectangles || Shows the a blue box over each entity, if you hover over it, it will be selected.
|-
| show-render-rectangles || Shows the a pink box over each entity, if that is on your screen, the entity will be rendered.
|-
| show-entity-positions ||
|-
| show-entity-velocities ||
|-
| show-selected-entity-advanced-tiles || Shows on which advanced tiles (2×2 tiles) the entity is registered.
|-
| show-selected-input-transport-belts || Shows which entities input into the selected transport line.
|-
| show-paths || The calculated paths for the biters in different colors.
|-
| show-path-requests ||
|-
| show-next-waypoint-bb || Shows waypoints for biters (in green), nearly the same info as the next.
|-
| show-target || Shows the current target of the biters (red).
|-
| show-unit-group-info || Biter groups, which belong together (circles and lines belonging together)
|-
| show-unit-behavior-info ||
|-
| show-pathfinder-fringe ||
|-
| show-path-cache || The source-positions of a path and about the length (?)
|-
| show-path-cache-paths ||
|-
| show-rail-paths || Which path a train will follow.
|-
| show-rolling-stock-count || Shows inserter positions
|-
| show-rail-connections || Shows rail connections.
|-
| show-rail-joints ||
|-
| show-rail-signal-states || Shows signal color on map view.
|-
| show-rail-segment-collision-boxes ||
|-
| show-train-stop-point || When a train slows down it shows the calculated point where it should halt
|-
| show-train-braking-distance || The distance a train will take to stop at its current speed
|-
| show-train-signals ||
|-
| show-train-repathing || Display a flying "repathed" text over a train whenever it repaths.
|-
| show-network-connected-entities || Displays the network-id of the electric network that a pole is connected to
|-
| show-circuit-network-numbers || Shows the number (and color) of circuit networks
|-
| show-energy-sources-networks || Which network-id an entity is connected to.
|-
| show-active-state || Inserters, fish, turrets are turned to passive, if not used; Red = inactive, Purple = inactive when enemies aren't around (turrets etc), Green = inactive when player isn't around (fish). Passive entities consume less CPU power.
|-
| show-wakeup-lists || When an entity is sleeping in another entity it shows which entities it's sleeping in.
|-
| show-transport-lines ||
|-
| show-transport-line-gaps ||
|-
| show-pollution-values || Shows the numeric pollution amount on each chunk.
|-
| show-active-entities-on-chunk-counts ||
Shows counts of active entities per chunk. They are devided into three categories:
* Red = active (e.g. furnaces)
* Blue = active when a player is around (e.g. fish)
* Green = active when enemies are around (e.g. turrets)
|-
| show-active-chunks || Shows in the map view, which chunks are "on", unmarked chunks are not calculated.
|-
| show-polluted-chunks || Shows which chunks have pollution.
|-
| show-enemy-expansion-candidate-chunks || Where is space left to spread the brood?. Goes from red (nearly no space) to green (space to expand).
|-
| show-enemy-expansion-candidate-chunk-values || Which chunks the enemies will try to expand into.
|-
| show-bad-attack-chunks ||
|-
| show-tile-variations || Shows, which tile-variation (1, 2 or 4 tile sized) is painted for which area of the map. Quite confusing, zoom in to see the meaning.
|-
| show-raw-tile-transitions || Turns connected textures for land and water off, so the distinction can easily be made.
|-
| show-fluid-box-fluid-info || How much fluid is in a pipe/storage tank, shows flow of liquid in pipes.
|-
| show-environment-sound-info || Displays which sound of which entity is played and how loud.
|-
| show-logistic-robot-targets ||
|-
| show-logistic-robots-on-map ||
|-
| show-recipe-icons-on-map ||
|-
| show-player-robots ||
|-
| show-fire-info ||
|-
| show-sticker-info ||
|-
| show-decorative-names ||
|-
| show-decorative-collision-rectangles ||
|-
| allow-increased-zoom ||
|-
|}

Radar

2019-11-07T12:01:15Z

Jon8RFC: /* Charting */ fix redirect

{{Languages}}
{{:Infobox:Radar}}
The radar triggers charting of the map of the force it belongs to.

It can be used to provide a small area of remote vision on the map; it also allows periodic scanning of distant chunks around it. The Radar has a high [[Electric system|power]] demand (300kW) so a radar indirectly contributes to [[pollution]] when powered by [[boiler]]s and [[Steam engine|steam engines]]. A radar can be continuously powered by eight solar panels and six accumulators. Seven solar panels and five accumulators is the most efficient; it gives the radar full power all but a short time in the morning, but never dips below the 20% power threshold for nearby scanning.

The radar will be attacked by enemies that come within very close range, like turrets, due to its status as a military building, but will not attract biters from long range like polluting structures do. The radar will show enemy lifeforms and structures, as well as [[Railway#Trains|trains]], [[Car|cars]], and other [[player]]s in the scanned area.

== Nearby Pulse Scanning ==

The Radar continuously charts an area of 7×7 [[Map_structure#Chunk|chunks]] (224×224 [[Tile (unit)|tile]]s), centered on the chunk the radar occupies. This nearby area is updated as a single pulse approximately every second. At reduced power levels, this nearby pulse scan will take longer, which can lead to 'blinking' on the player's map similar to the long range scan. This is particularly noticeable at dawn and dusk on solar powered radar stations.

At 20% power the radar will pulse about every 4 seconds which will still keep the nearby area continuously lit on the map, but will provide reduced detail. 20% power can be achieved by a single [[solar panel]], or by using one isolating accumulator for every 5 radars.

== Long Range Survey Scanning ==

The Radar charts one distant [[Map_structure#Chunk|chunk]] every time the sector scanning progress bar fills. This will take 33.333 seconds, if the Radar is receiving full power. Mouse-over or click-open the radar details to see this progress bar. Long range scanning is visible on the map as a single chunk lighting up for several seconds, then slowly darkening.

* It scans the unexplored chunks first, represented by the black areas on the map. Note that it also generates the chunks if they weren't generated at the time of the scan.
* One chunk scan takes 10 MJ of energy to complete. Since the Radar draws 300 kW of power, it takes 10 MJ ÷ 300 kW = 33.333 seconds to scan one chunk.
* This is done in an 29×29 chunks around the Radar, excluding the nearby 7×7 chunks.
** With a total number of 797 chunks (29×29 − 7×7), it takes one radar '''7 hours 20 minutes''' to complete one full scan cycle.
* If everything is already explored it continues to scan by re-scanning the longest-ago scanned chunk within range.
* Multiple radars will share long-range chunks, reducing the amount of time it takes to complete long-range survey scanning.
** This is a smart process, meaning that the radars will not scan chunks currently being scanned by other radars.

'''It is possible that a new alien nest will appear in a previously scanned chunk; just because you don't see it on the map, doesn't mean it is not there.

== Coverage ==

Radars grant sight of a square area around them, which is displayed brighter than the rest of the map. This allows the player to zoom into the normal world view from the map and makes interaction with [[blueprint]]s and [[deconstruction planner]]s possible.

[[File:Radar_coverage.png|thumb|500px|none|The coverage area of a radar and the player.]]

== Charting ==

If a [[Map_structure#Chunk|chunk]] is '''scanned''' by a radar or player, the image of that chunk that is copied into the map of the players of this surface force (every force has its own map).

This procedure is called "charting".

=== Charting Process ===

If the contents of a chunk changes between two ticks, the content of that chunk is "charted" into the map. The map is just a bitmap, a picture. You can see the entities moving, you can see enemies walking. Every entity is represented by one or more pixels. Not every entity is drawn. Users can recognize what is drawn because of the color.

Charting of several chunks that change each tick might have an impact on game performance, manifesting in the form of lowered <abbr title="Updates Per Second">UPS</abbr> or <abbr title="Frames Per Second">FPS</abbr>.

=== Charting Decay Time / Fog of War ===

Once a scan for a chunk is triggered, it keeps actively charted for '''10 seconds'''. This effect can also be seen in the map of the chunk highlighted and dims within 10 seconds to a greyed out version of the chunk.

If charting is not repeated within the 10 seconds, the charting process stops for this chunk after 10 seconds and is not longer updated. What you see after that time is the last charted picture for that chunk (also called "fog of war").

=== Charting of Vehicles ===

Even in the fog of war you can see the last charted position of vehicles. Trains last positions are not charted, because they normally always move after the charting stops.

Vehicles are shown as a circle, with an arrow pointing in the direction that they're facing.

=== Invisible (black) parts of the Map ===

The [[World_generator#Generating_new_Chunks|World Generator]] creates a "border" of invisible chunks around each chunk, that becomes active at some time. Active chunks are those that become charted or those that are active because the pollution spreads onto them.

== History ==

{{history|0.15.0|
* Radar now allows remote view via map.}}

{{history|0.12.17|
* Updated icons.}}

{{history|0.11.11|
* Radar ignores chunks outside the map radius.}}

{{history|0.10.0|
* New graphics.}}

{{history|0.9.0|
* Halved radar electricity consumption.}}

{{history|0.7.3|
* Radar continues refreshing chunks after all chunks in range have been discovered.}}

{{history|0.5.1|
* New Graphics}}

{{history|Unknown, presumed 0.1.0|
* Introduced}}

== See also ==
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].

{{CombatNav}}
{{C|Defense}}

Radar

2019-11-07T11:59:49Z

Jon8RFC: fix redirects

{{Languages}}
{{:Infobox:Radar}}
The radar triggers charting of the map of the force it belongs to.

It can be used to provide a small area of remote vision on the map; it also allows periodic scanning of distant chunks around it. The Radar has a high [[Electric system|power]] demand (300kW) so a radar indirectly contributes to [[pollution]] when powered by [[boiler]]s and [[Steam engine|steam engines]]. A radar can be continuously powered by eight solar panels and six accumulators. Seven solar panels and five accumulators is the most efficient; it gives the radar full power all but a short time in the morning, but never dips below the 20% power threshold for nearby scanning.

The radar will be attacked by enemies that come within very close range, like turrets, due to its status as a military building, but will not attract biters from long range like polluting structures do. The radar will show enemy lifeforms and structures, as well as [[Railway#Trains|trains]], [[Car|cars]], and other [[player]]s in the scanned area.

== Nearby Pulse Scanning ==

The Radar continuously charts an area of 7×7 [[Map_structure#Chunk|chunks]] (224×224 [[Tile (unit)|tile]]s), centered on the chunk the radar occupies. This nearby area is updated as a single pulse approximately every second. At reduced power levels, this nearby pulse scan will take longer, which can lead to 'blinking' on the player's map similar to the long range scan. This is particularly noticeable at dawn and dusk on solar powered radar stations.

At 20% power the radar will pulse about every 4 seconds which will still keep the nearby area continuously lit on the map, but will provide reduced detail. 20% power can be achieved by a single [[solar panel]], or by using one isolating accumulator for every 5 radars.

== Long Range Survey Scanning ==

The Radar charts one distant [[Map_structure#Chunk|chunk]] every time the sector scanning progress bar fills. This will take 33.333 seconds, if the Radar is receiving full power. Mouse-over or click-open the radar details to see this progress bar. Long range scanning is visible on the map as a single chunk lighting up for several seconds, then slowly darkening.

* It scans the unexplored chunks first, represented by the black areas on the map. Note that it also generates the chunks if they weren't generated at the time of the scan.
* One chunk scan takes 10 MJ of energy to complete. Since the Radar draws 300 kW of power, it takes 10 MJ ÷ 300 kW = 33.333 seconds to scan one chunk.
* This is done in an 29×29 chunks around the Radar, excluding the nearby 7×7 chunks.
** With a total number of 797 chunks (29×29 − 7×7), it takes one radar '''7 hours 20 minutes''' to complete one full scan cycle.
* If everything is already explored it continues to scan by re-scanning the longest-ago scanned chunk within range.
* Multiple radars will share long-range chunks, reducing the amount of time it takes to complete long-range survey scanning.
** This is a smart process, meaning that the radars will not scan chunks currently being scanned by other radars.

'''It is possible that a new alien nest will appear in a previously scanned chunk; just because you don't see it on the map, doesn't mean it is not there.

== Coverage ==

Radars grant sight of a square area around them, which is displayed brighter than the rest of the map. This allows the player to zoom into the normal world view from the map and makes interaction with [[blueprint]]s and [[deconstruction planner]]s possible.

[[File:Radar_coverage.png|thumb|500px|none|The coverage area of a radar and the player.]]

== Charting ==

If a [[chunk]] is '''scanned''' by a radar or player, the image of that chunk that is copied into the map of the players of this surface force (every force has its own map).

This procedure is called "charting".

=== Charting Process ===

If the contents of a chunk changes between two ticks, the content of that chunk is "charted" into the map. The map is just a bitmap, a picture. You can see the entities moving, you can see enemies walking. Every entity is represented by one or more pixels. Not every entity is drawn. Users can recognize what is drawn because of the color.

Charting of several chunks that change each tick might have an impact on game performance, manifesting in the form of lowered <abbr title="Updates Per Second">UPS</abbr> or <abbr title="Frames Per Second">FPS</abbr>.

=== Charting Decay Time / Fog of War ===

Once a scan for a chunk is triggered, it keeps actively charted for '''10 seconds'''. This effect can also be seen in the map of the chunk highlighted and dims within 10 seconds to a greyed out version of the chunk.

If charting is not repeated within the 10 seconds, the charting process stops for this chunk after 10 seconds and is not longer updated. What you see after that time is the last charted picture for that chunk (also called "fog of war").

=== Charting of Vehicles ===

Even in the fog of war you can see the last charted position of vehicles. Trains last positions are not charted, because they normally always move after the charting stops.

Vehicles are shown as a circle, with an arrow pointing in the direction that they're facing.

=== Invisible (black) parts of the Map ===

The [[World_generator#Generating_new_Chunks|World Generator]] creates a "border" of invisible chunks around each chunk, that becomes active at some time. Active chunks are those that become charted or those that are active because the pollution spreads onto them.

== History ==

{{history|0.15.0|
* Radar now allows remote view via map.}}

{{history|0.12.17|
* Updated icons.}}

{{history|0.11.11|
* Radar ignores chunks outside the map radius.}}

{{history|0.10.0|
* New graphics.}}

{{history|0.9.0|
* Halved radar electricity consumption.}}

{{history|0.7.3|
* Radar continues refreshing chunks after all chunks in range have been discovered.}}

{{history|0.5.1|
* New Graphics}}

{{history|Unknown, presumed 0.1.0|
* Introduced}}

== See also ==
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].

{{CombatNav}}
{{C|Defense}}

Pollution

2019-11-07T11:56:47Z

Jon8RFC: fix redirects

{{languages}}
[[File:Pollution.png|300px|thumb|Example of in-game pollution (red squares) in the map]]
[[File:pollution_gui.png|300px|thumb|Pollution tab in the production GUI.]]

Pollution is represented as an abstract "cloud", updated [[Map_structure#Chunk|per chunk]] every game second (60 ticks) and visible on the map, when "alt-view" is on (default [[Keyboard bindings|Alt-Key]]). It appears as a red colored blocky cloud.

It is produced by many buildings involved in processing items and spreads outwards at a steady rate.

The [[Enemies#Evolution|evolution factor]] is not increased by the spreading/absorbed pollution, but by the pollution produced by all the player's [[Pollution#Polluters|machinery]] at every tick. This means that no matter how hard the player tries to contain the pollution, [[enemies]] will still evolve at the same rate. They just won't attack the player as frequently. The pollution cloud is used to trigger biter attacks and determines the size of the attacks.

Pollution settings can be changed via [[map generator|map generation]] settings, or can be disabled entirely.

== Pollution spread ==

As soon as a chunk has reached 15.0 pollution it starts spreading in all four cardinal directions at a rate of 2% per [[game-second]] (60 ticks). Pollution can generate new chunks if it needs to spread to them.

For example, a chunk with 400.0 pollution and 4 adjacent chunks with 100.0 pollution each, raises the pollution in all adjacent chunks by 8.0 while reducing its own pollution by 32.0. But every one of the 4 surrounding spreads 2.0 pollution "back" to the center chunk, so it only loses 24.0 + [[Pollution#De-polluters|absorbed value]].

== Pollution dissipation==

* Every [[Map_structure#Chunk|chunk]] (32x32) of map slowly reduces the pollution it covers (See [[Pollution#Chunks]]). So the more the pollution spreads, the more is absorbed.
* [[Tree]]s also absorb some pollution (See [[Pollution#Trees]]).
* [[Enemies#Spawner|Spawners]] absorb a great amount of pollution, and use this to assign enemies to attacks.

== Native life ==
Pollution attracts [[Enemies#Biters|biters]] to the Player's factory. Biters who find themselves in a polluted area will attempt to reach the source of pollution and destroy it.

If a chunk's pollution is greater than 20, each enemy spawner absorbs 20 + 0.01 * [chunk's pollution] every game second (60 ticks), otherwise it absorbs 3 times the amount of pollution needed for the most expensive unit it can spawn for the current evolution factor.

Higher pollution values decrease the time it takes for biters to join the attack force. After a certain amount of pollution is absorbed the spawner sends one of its biters/spitters to a rendezvous point. Every 1 to 10 minutes (random) the mustered biters launch an attack. If not all biters have arrived at the rendezvous point by that time, they will wait up to an additional 2 minutes for stragglers.

Required pollution to add an additional biter/spitter to the attack wave:
{| class="wikitable" style="text-align:right;"
! style="width: 100px;" | Pollution 
! style="width: 130px;" | Type 
|-
| 4  || Small biter 
|-
| 20  || Medium biter 
|-
| 80  || Big biter 
|-
| 400  || Behemoth biter 
|-
| 4  || Small spitter 
|-
| 12  || Medium spitter 
|-
| 30  || Big spitter 
|-
| 200  || Behemoth spitter 
|-
|}

== Modules ==
[[Module]]s that list "+x% pollution" increase pollution multiplier, not a flat pollution rate. Final pollution value is (pollution multiplier * energy usage multiplier * base pollution), meaning heavily boosted buildings are likely to account for most of the pollution produced in a factory.

== Production/Absorption ==
These tables contain information about the levels of pollution produced/absorbed by items in the game.
=== Polluters ===
{| class="wikitable"
! Structure !! Pollution per minute at full power
|-
| {{Imagelink|Stone furnace}} || 2
|-
| {{Imagelink|Steel furnace}} || 4
|-
| {{Imagelink|Electric furnace}} || 1
|-
| {{Imagelink|Burner mining drill}} || 12
|-
| {{Imagelink|Electric mining drill}} || 10
|-
| {{imagelink|Pumpjack}} || 10
|-
| {{Imagelink|Assembling machine 1}} || 4
|-
| {{Imagelink|Assembling machine 2}} || 3
|-
| {{Imagelink|Assembling machine 3}} || 2
|-
| {{imagelink|Boiler}} || 30
|-
| {{Imagelink|Oil refinery}} || 6
|-
| {{Imagelink|Chemical plant}} || 4
|-
| {{Imagelink|Centrifuge}} || 4
|-
|}

Fire on the ground and burning trees produce 0.005 pollution per second.

=== De-polluters ===

==== Spawner ====
If a chunk's pollution is greater than 20, each enemy spawner absorbs 20 + 0.01 * [chunk's pollution] every game second (60 ticks), otherwise it absorbs 3 times the amount of pollution needed for the most expensive unit it can spawn for the current evolution factor.

==== Chunks ====
Every chunk has a natural absorption rate per second which is determined by the sum of the pollution absorption of its floor tiles.

Following numbers are the pollution reduction for a single tile per second.
{| class="wikitable"
! Tile !! Pollution per second
|-
| Grass 1-4 || -0.0000075
|-
| Dirt 1-7, dry dirt || -0.0000066
|-
| Sand 1-3 || -0.0000058
|-
| Red desert 0-3 || -0.0000066
|-
| Water, green water, deep water, deep green water, shallow water, mud water || -0.000005
|-
| Path tiles (Stone bricks, concrete etc), landfill || 0
|-
| Out of map || -0.00001
|-
| Special tiles (Lab tiles, tutorial grid) || 0
|-
|}

==== Trees ====
Every single tree absorbs a small amount of pollution in its chunk per second. If the total pollution in that chunk is above 60 units, trees lose their leaves for every 10 pollution absorbed. The less dense the leaves, the slower the tree absorbs pollution.

{| class="wikitable"
! Object !! Stage !! Pollution per second
|-
| rowspan="4" | [[File:Green tree.png|120px]] Tree, red tree, brown tree || 0 (Max leaf density) || -0.001
|-
| 1 || -0.00067
|-
| 2 || -0.00033
|-
| 3 (Min leaf density) || 0
|-
| [[File:Dead dry hairy tree.png|120px]] Dead dry hairy tree || No stages || -0.0001
|-
| [[File:Dead grey trunk.png|120px]] Dead grey trunk || No stages || -0.0001
|-
| [[File:Dead tree desert.png|120px]] Dead tree - desert|| No stages || -0.0001
|-
| [[File:Dry hairy tree.png|120px]] Dry hairy tree || No stages || -0.0001
|-
| [[File:Dry tree.png|120px]] Dry tree || No stages || -0.0001
|-
|}

== Achievements ==
Pollution is directly connected to the following achievement:
{{Achievement|it-stinks-and-they-dont-like-it}}

== History ==

{{history|0.17.12|
* Added pollution tab to the production statistics.
* Spawner tooltip (including the pollution statistics), shows distribution of biters spawn for the current evolution factor with the pollution costs.
* Pollution generation is now shown in the x/s format both on the entity and in the item/crafting slot.
* Internal pollution values have been normalized, and they are now roughly 60 times less compared to what they were.}}

{{history|0.17.0|
* Rebalanced assembling machine 1,2 and 3 power consumption and pollution - higher tiers eat more power, but produce less pollution.
* Changed spawner pollution absorption logic so that all the pollution on a chunk doesn't build up un-spent in a single spawner.}}

{{history|0.13.2|
* Optimized rendering of huge pollution clouds on the map.}}

{{history|0.13.0|
* Large amounts of pollution is created when burning fires.
* Pollution creation of the productivity module was reduced drastically.
* Optimized pollution rendering on map and minimap.
}}

{{history|0.12.0|
* [[Tree]]s degenerate slowly when exposed to pollution at high levels. }}

{{history|0.8.0|
* Added option to turn off pollution visibility even when detailed info is on. }}

{{history|0.7.1|
* Speed modules no longer produce extra pollution.
* Added missing pollution descriptions.
* Pollution is only shown on the minimap with alt mode on.
}}

{{history|0.7.0|
* Introduced concept of pollution.}}

== See also ==
* [[Crafting]]
* [[Module]]s
* [[Enemies]]

Tutorial:Circuit network cookbook

2019-11-07T11:46:39Z

Jon8RFC: /* Oil Setups */ fix redirect

{{Languages}}
== Foreword ==

This page provides examples of simple circuit network designs and some not so simple designs that others can use, combine and modify. They are designed to be as easy to understand as possible. To see the settings of combinators without opening them, the option "Show combinator settings when detailed info is on" in the graphics options has to be checked and detailed info has to be turned on.

==Lamp showing chest content condition==
[[File:LightWiredToChest.png|right]]

This is the simplest possible use of circuit-network. A lamp is light depending on the number of goods (in this example empty barrels) in a chest.

===Setting up circuit connection===
* The lamp is connected to the chest
* the lamp is set to light if the chest contain less than 10 empty barrels.
===To set the light condition===
* Open the lamp (left click on it)
* Set the input to barrels
* Set the operator to < (less than)
* Set the constant number:
** Left click on the constant number
** Move the slider until 10 is shown, or edit the value box directly
** Press set

Depending on the condition you set, the lamp may light if the chest is empty, or if it contains the required quantity of items.

The drawback with this scenario is that the lamp has a white light , and is therefore difficult to differentiate from an ordinary lamp at night.
{{clear}}

== Oil Setups ==
[[File:LgtOilCracking.png|left|400x400px]]
=== Light Oil Cracking ===
* This circuit provides balanced light oil and petroleum gas production by cracking excess light oil into gas.
* The [[Pump]] is connected to the [[Storage tank]] by a [[Red wire]].
* The [[Pump]] has an enabled condition set to '''Light Oil > 20000''' (nb image is out of date).
{{clear}}

[[File:HvyOilCracking.png|left|400x400px]]

=== Heavy Oil Cracking ===
* This circuit extends on the previous circuit by adding optional heavy oil cracking to provide lubricant etc.
* The [[Pump]] has an enabled condition set to '''Heavy oil > 20000''' (nb image is out of date).
{{clear}}

[[file:BalancedPlasticSulfur.png|left|400x400px]]

=== Petroleum split evenly between plastic and sulphuric acid ===
* This circuit buffers gas in the tank until there is at least 100, then it lets the tank drain until there is less than 50 and the cycle repeats.
* It has a few elements that work together to do achieve this.
* Firstly the [[Pump]] is connected to the [[Wooden chest]] by a [[Red wire]] and the enabled condition on the [[Pump]] is set to '''Raw wood > 0'''.
* Both of the [[Inserter]]s are connected to the [[Storage tank]] by [[Red wire]]s.
* The enabled condition on the left inserter is '''Petroleum gas > 100'''
* The enabled condition on the right inserter is '''Petroleum gas < 50'''.
* You will need to insert a single "Raw wood" into the chest to make it all work.
 
* It is also possible to do this with [[decider combinator]]s instead of the inserters, belt and the Wood chest or even just belts.
{{clear}}

== Lights ==
[[File:ConditionalLights.png|left|400x400px]]
=== Conditional Lights ===
* In this circuit we connect a series of [[lamp]]s to a [[Storage tank]].
* By setting different conditions on each [[lamp]] we can build an indicator strip.
* The Enabled condition of the first [[lamp]] is '''Petroleum gas > 100'''.
* The others light up when gas is greater than 200, 300, 400 and 500 respectively.
{{clear}}

In this scenario you can connect the storage tank to the lamps directly.

[[File:ColoredLights.png|left|400x400px]]

=== Colored Lights ===
* To light a [[lamp]] with a color rather than white, you need an intermediate device like an [[Arithmetic combinator]] that can send a color signal.
Instead of directly connect the the [[Lamp]] and the [[Storage tank]] you need: 
1 Add the [[Arithmetic combinator]]. 
2 Connect the [[Storage tank]] with the input of the [[Arithmetic combinator]]. 
3 Connect the output of the [[Arithmetic combinator]] with the [[lamp]]. 
4 Set up the [[Arithmetic combinator]]: 
4.1 Setting the input to Petroleum Gas + 0 (the constant 0 not the signal 0) 
4.2 Set the output to the Pink signal (on the bottom row of the last tab of signals.) 
5 Set up the [[lamp]]: 
5.1 Select the "Use colors" check box on the lamp. 
5.2 Set the condition to the Pink signal, and what value you want (i.e. > 100) 
{{clear}}

== Misc ==
[[file:MulitipleChestsAndPoles.png|left|400x400px]]
=== Multiple Storages ===
* If you connect multiple chests to a pole, the pole displays the sum of items in all the chests.
* This also works with [[Storage tank]]s and [[roboport]]s.
{{clear}}

[[File:ConstantComb.png|left|400x400px]]

=== Constant combinator ===
* With a [[constant combinator]] you can generate any signals you may need.
* In this example we have generated a signal of 50 Laser turrets and 200 Piercing round magazine.
* Constant combinators are not of much use on their own but we shall use them later.
{{clear}}

[[File:ThisASign.png|left|400x400px]]

=== Constant combinator signs ===
* You can use [[Constant combinator]]s to make signs, just set the letter signals in the combinator, each combinator can display 2 characters side by side.
{{clear}}

[[File:MemoryCell.png|left|400x400px]]

=== Memory Cell / Counter ===
* Basic memory cell that counts all the items moved by the inserter
* The [[Fast inserter]] is connected to '''BOTH''' ends of the arithmetic combinator.

* If the [[Fast inserter]] hasn't picked anything up this tick the input to the Arithmetic combinator is the same as and output and hence the values are persisted.
* When the [[Fast inserter]] does pick something up its value is added to the output from the previous tick thus incrementing that item.
{{clear}}

== Inserters ==
[[File:LimitItemsPlacedIntoAChest.png|left|400x400px]]
=== Limit items placed into a chest ===
* The [[Inserter]] is connected to the [[Wooden chest]] using a [[Red wire]].
* The inserter's enabled condition is '''Advanced Circuit < 10'''.
* In reality this means the inserter may place more than 10 Advanced circuits in the chest because it could pick up to 3 at once due to stack size bonuses.
* This effect can be even greater with Stack inserters because of their large carrying capacity.
* This technique still gives far greater control than limiting the inventory on the chest.
{{clear}}

=== Balanced chest insert ===
Goal: Load n chests with approximately the same number of items.
* Place n chests and n inserters.
* Place 1 [[Arithmetic combinator]]
* Set the combinator to take Each (yellow star) and divide by the negative number of chests. ie −n.
* Connect all chests to each other and to the input of the combinator using red wire.
* Connect all inserters to each other and to the output of the combinator using red wire.
* Connect each inserter to the box it inserts into with green wire.
* Set the enable condition on each inserter to be Everything (red star) < 0.

The combinator calculates the average number of items in the chests, and makes it negative. Each inserter gets the amount in the chest it is inserting to and adds the negative average, ie it calculates how many more than the average it has in its chest. Thus if that number is negative, it has less than the average in the chest and it enables.

Due to inserter stack bonus the count is not exact. If a precise count is needed, set the inserter stack size to 1.

{{clear}}

[[File:SmartOutpostUnloader.png|left|400x400px]]
=== Keeping outpost stocked with specified items ===
* This circuit keeps a [[Storage chest]] at an outpost stocked with customized levels of different items.
* For example you could keep an outpost stocked with 50 laser turrets and 200 piercing magazine rounds but not have to worry about it being over filled.
* The [[storage chest]] is attached to the input of the [[Arithmetic combinator]] (left side in the picture) with a [[Red wire]].
* Another couple of [[Red wire]]s join the output of the [[Arithmetic combinator]] (right side) to the [[constant combinator]] and to the [[stack filter inserter]].
* The [[Arithmetic combinator]] '''multiplies''' each input value (from the storage chest) by '''-1'''.
* Finally the filter stack inserter's mode of operation is set to '''Set filters'''.
* So the input to the [[stack filter inserter]] is '''<Constant combinator> - <Storage chest contents>''' and the filter is set to filter the item of greatest demand.
{{clear}}

[[File:SolarAccumalatorBalancer.png|left|400x400px]]

=== Balanced Solar panel / Accumulator Production ===
* This circuit balances production of [[Solar panel]]s and [[Accumulator]]s to a desired ratio in my case 24:20.
* The first [[Arithmetic combinator]] takes the number of accumulators in the chest and '''multiplies''' it by '''24'''.
* The second [[Arithmetic combinator]] takes the output of the first combinator and '''divides''' it by '''20'''.
* This gives us the number of accumulators that we can directly compare to the number of Solar panels in both inserters.
* If the number of accumulators is greater we enable the Solar panels inserter, if the number of Solar panels is greater we enable the accumulators inserter.
* However, if they are equal, neither machine does anything. So we add a single accumulator to one of the inserters using a constant combinator and a wire of the other color, therefore breaking the deadlock.
{{clear}}

== Sushi Belts ==
[[File:SushiScience1.png|left|400x400px]]
=== Reading Belt Design ===
* Six belts in a row are connected with Red wire and set to '''Read belts contents''' and '''Hold'''
* This [[Red wire]] is then connected to the inserters that insert onto the belt.
* Read hand contents is unselected for all inserters.
* Mode of operation is set to '''Enable/Disable''' on all inserters.
* The first inserter is enabled when '''Science pack 1 = 0'''
* The other inserters are set similarly for the other science packs.
{{clear}}

[[File:SushiScience2.png|left|400x400px]]
=== Memory Cell Design ===
* This circuit counts the number of items of each type on a looping belt by counting the numbers that are added and removed from the belt by inserters.
* Each inserter that takes items off the belt is connected together with Red wire and each of these inserters is set to '''Mode of operation none, Read hand content selected''' and '''Hand read mode pulse'''.
* These inserters are connected to the input of the left arithmetic combinator.
* The left [[Arithmetic combinator]] multiples '''each''' input by '''-1''' and outputs it to '''each'''.
* The right [[Arithmetic combinator]] is a '''memory cell''' as above.
* The memory cell's input is connected to the inserters that are placing items on the belt and the output of the left [[Arithmetic combinator]].
* The inserters that place items onto the belt have an enabled condition that is based on the number of items on the belt.
{{clear}}

== Power ==
[[File:SteamBackup.png|left|400x400px]]
=== Backup steam power ===
* The [[steam engine]]s are not directly connected to the power network. They are connected to the power network through a [[Power switch]].
* The [[power switch]] is connected to one of the [[accumulator]]s in the main network.
* The [[power switch]] turns on when A < 10. That is when the [[accumulator]]s are less than 10% full.
{{clear}}
=== Optimal usage of fuel for nuclear power ===
Unlike the normal steam power that adjusts fuel usage based on power usage, the [[Power_production#Nuclear_power|nuclear reactors]] spend fuel in fixed units of time. To be exact, the consumption of 1 fuel cell takes exactly 200 seconds.

Combined with the fact that creating the nuclear fuel cells are time consuming and expensive to create, it is therefore beneficial to optimize their use to match the actual consumed power.

[[File:NuclearCircuits.jpg]]

The above picture shows a setup with 4 reactors, that spend only 1 fuel cell each whenever steam runs low.

There are a few elements in this setup:

* Storage tank that provides the [[Steam]] signal. You should only read from one storage tank, and it should have pipe connections to all your other steam storage tanks.
* Chests containing [[Uranium_fuel_cell|Uranium fuel cells]] for the reactor.
* Output inserters that take [[Used_up_uranium_fuel_cell|Empty fuel cells]] from the reactor. This is connected to the storage tank to listen for the steam signal, and to the chests to listen for the uranium fuel cell signal. If the steam level is low and there are uranium fuel cells available, it removes the empty fuel cells from the reactor and sends an empty fuel cell signal (since "Read hand contents" is checked).
* Input inserters that put uranium fuel cells into the reactor. This is connected to the output inserters and listens for the empty fuel cell signal. The "Override stack size" is set to 1, so that it only inserts 1 fuel cell at a time.

Since this design uses empty fuel cells as a signal to fill the reactor, you need to manually insert 1 uranium fuel cell into the reactor to get it started.

== Latches ==
=== RS latch - single decider version ===
[https://forums.factorio.com/viewtopic.php?f=193&t=14556 This discussion] on the Factorio forums starts with the common 2 decider RS latch version, but the thread [https://forums.factorio.com/viewtopic.php?p=160896#p160896 goes on to explain] why this single decider version is better. In the thread, the latch is described as an SR latch. However, when both inputs are true, the latch will reset, so it is an RS latch.
==== Backup steam example ====
This example will turn on the steam generator when the Accumulator charge drops to 20%, but will "latch" (remember) the On state until the accumulator is charged to 90%.

Latching is used to introduce [[Wikipedia:hysteresis|hysteresis]] and avoid the power switch rapidly cycling on and off (as the accumulator falls to 19%, charges to 20%, falls to 19% and so on).
[[File:SR-01-Layout.png|left]]
{{clear}}
{{BlueprintString|bp-string=0eNrFVk1vozAQ/SuVz1ABCaRBq5WqXntKjqsKOTBJR8IGGTtpFPHfd+w0HyU0G6pVewkxnnmemfdmzI4tSgO1QqlZumOYV7Jh6Z8da3AleWnf6W0NLGVrVNrQG49JLuyLvYU/Z63HUBbwxtKw9QZ4zs48o15P1CBObgXkWIDy80osUHJdqTOAUfviMZAaNcI+A7fYZtKIBSiK7YgjoEAjfCgh1wpzv65KoFPqqiHnStrzCdAPA49t6Rm1NrYOWjQY7QrY6FQZwcvyX1jJFajxEYrnuRGmdGW6DCe+jx1KcB9TDYl1raoyW8ArXyM5kFVldG10djObj6zdI0kKHp2Mdiy0PysFIM8pwYKldHyOKjeo3TI8y8Wup93tl7Yv3fiaOC6zjt6z9uk4VqDaR+rY7CvBO2ZGewUec1qiaobVxaE3mtseiwK7EjVXLsaU/SKPobWe7zHrLYVmpM6WqhIZSsJg6ZKXDQyiYkzF9Vhk9xUU3d3kNiaSQUwEB/l9Hw+uZg1YjGzYiPpA1+/vpKuHjk7fRNf7JrJTsZf05MLwoIFbzLvtOvlEFZNjKepqQ5poNqjz10s9jA6N+fk8Ohx/FMFXNXDqxeCC20F901vCJxN07UjVG9K4+x9YQp5M2LUZfbTpq+XDKRsNnG4cuULZcz089HZWD+D0a8Pz52bnNPgPzTj76dlJAnDfNenZp5fHSr4ACp/NZ3fPnHrkDt64qN31vwbVuFIn43GUjCdxHIVt+xcL2lBp}}
{{clear}}
[[File:SR-02-Accumulator.png|left]]Accumulator outputs the current charge level as % on signal [[File:Signal-A.png|21px]]
{{clear}}
[[File:SR-03-RangeDeciders.png|left]]First decider outputs "Set" ([[File:Signal-S.png|21px]] = 1) if Accumulator is less than 20%.
Second decider outputs "Reset" ([[File:Signal-R.png|21px]] = 1) once Accumulator is more than 90% full.
{{clear}}
[[File:SR-04-SRLatch.png|left]]
==== RS Latch configuration ====
'''The central decider and green feedback wire is the actual RS Latch.'''
It latches the Set signal [[File:Signal-S.png|21px]] until the Reset signal [[File:Signal-R.png|21px]] is received (and vice-versa). 
NB: the latch expects binary inputs ([[File:Signal-S.png|21px]] & [[File:Signal-R.png|21px]] must be 0 or 1) - this is why the previous two deciders are required. 
When both inputs are true, the reset signal takes priority and the latch resets. This means it is an RS latch instead of an SR latch.
 
[[File:SR-05-PowerSwitch.png|left]]The Power switch isolates the generator from the rest of the factory until [[File:Signal-S.png|21px]] = 1
 
----

=== RS latch ===
[[File:SRLatch.png|left|400x400px]]
* This should be familiar to anyone with any background in electronics.
* The signal is set and reset with the [[constant combinator]]s on the left by setting an A=1 signal.
* The latch "remembers" which one was last set and the light stays on until another signal is received.
{{clear}}

[[File:SRlatchinaction.png|left|400x400px]]

=== Usage of RS latch ===
* Here is an example of how you could use an RS latch.
* The two extra [[Decider combinator]]s provide the set and reset conditions.
* Petroleum gas < 50 and petroleum gas > 100.
{{clear}}

[[File:BeltLatch.png|left|400x400px]]

=== Belt only latch ===
* To make it work, '''3''' pieces of raw wood must be placed on the inside lane of the belt.
* It will have higher latency than the combinator version, but in most situations you will not notice the difference.
{{clear}}

== Displays ==
[[File:5digitDisplay.png|left|400x400px]]
=== Numerical Display ===
* Each digit is driven by its own [[Green wire]], that wire holds 15 signals, one for each lamp used in the digit.
* [[Constant combinator]]s are used to define which lamp should light up for each value.
{{clear}}

[[File:BWDisplay.png|left|400x400px]]

=== Black and White Grid Display ===
* Each row has its own [[Red wire]] connection and within that row each light has a numbered signal 0-9.
* We turn each light on by just setting or clearing the relevant signal.
{{clear}}

[[File:MultiColoredDisplay.png|left|400x400px]]
=== Multicolor Display by DaveMcW ===
* To understand how this works, you first need to understand how color lights choose which color to light up when there are multiple colored signals.
* The [[lamp]] will light up with the colored signal that is greater than zero and earliest in this list: Red, Green, Blue, Yellow, Pink, Cyan, White.
* We have a [[Red wire]] per column, that wire has each of the colored signals on it at different values and a numbered signal for each row.
* There is a [[Arithmetic combinator]] for each cell that subtracts the "row" value from each of the colored signals.
* And this enables us to choose the color for each cell.
* Simple!
{{clear}}

== See Also ==
* [[Arithmetic combinator]]
* [[Constant combinator]]
* [[Decider combinator]]
* [[Circuit network]]

Map structure

2019-11-07T11:43:52Z

Jon8RFC: /* Chunk */ fix redirect

{{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 32x32 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 [[World_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 100 tiles diameter (100 tiles in each direction, bounded to the matching [[#Chunk|chunk]]).
* It takes about 1 minutes and 52 seconds to run 1000 tiles without speed up. [[Talk:Exoskeleton#Movement%20speed%20experiments|1]] (As a side note, this means that the character is a very fast runner.)

=== Real world size analogy ===

One tile is generally assumed to be one square meter in size, this is confirmed by the game using meter as the length unit, such as km/h for vehicle speed.

== Chunk ==

A '''chunk''' is a unit defined as either an area of the map 32×32 tiles in size (containing 1024 tiles in total) ''or'' a distance of 32 tiles.

Chunks are used for:
* Map generation. When the [[player]] moves, has a [[radar]] explore the map via sectors, or has [[artillery shell]]s fired across long distances, the map is revealed in chunks.
* Chunks are "switched off" to save CPU cycles. If nothing important happens in a chunk (e.g. nothing has moved except [[fish]]) the chunk is not computed in the next [[Time#Ticks|tick]].
* The [[pollution]] model is based on chunks, and pollution spreads to neighboring chunks.
* [[Enemies#Expansions|Enemy expansion]] is evaluated on a per-chunk basis. The game scans the map chunk by chunk to decide whether each chunk is a valid expansion target. Valid chunks are called 'candidate chunks' and assigned a score from 0 to 1.0 indicating their relative suitability. A chunk is then picked at random using a weighted dice roll such that chunks with higher scores are chosen more frequently.

== 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.

Debug mode

2019-11-07T11:40:55Z

Jon8RFC: fix redirect

{{Languages}}
The ''debug mode'' is used mainly by developers and modders to analyze the running state of the game. It can be enabled to show detailed information about the game world. The default key to enable debug mode is {{keybinding|F5}}.

For example, one can:
* See the path the [[Enemies#Biters|biters]] are coming from and where they plan to target,
* See the position / coordinates of the cursor,
* See a grid-overlay for the [[map structure|tile]]s and [[chunk]]s,
* See the blocks in a railway network,
* See additional non-game related information, such as Updates Per Second and FPS.

== Activate the debug mode ==

There are 4 debug-levels:

* '''Always''' - This is the default mode, if no mode is active. Keep very few things active here.
* '''Debug''' - Toggled by pressing {{keybinding|F5}}. Allows to toggle the debug overlays.

== Configuring the debug mode ==

To configure the 2 modes, press {{keybinding|F4}}. This opens up a menu with many options. You can move this menu with the mouse, if it hides some interesting underlying thing. You can switch between 2 folders, which reflects the option for that debug-mode ("always", "debug"). The options are the same for each mode. Each mode can be configured to the user's liking, the different modes are only for convenience. A search function ({{Keybinding|ctrl|F}}) is available.

== List of debug-options and their function ==
{| class="wikitable"
|-
! Option !! Description
|-
| show-fps || Will show the current frames-per-second and updates per second, short <abbr title="Frames Per Second">FPS</abbr> and <abbr title="Updates Per Second">UPS</abbr>. Should be normally about 60.
|-
| show-detailed-info ||
* Shows the cursor position in [[Tile (unit)|tile]]s (and subdivisions of that).
* Current resolution and zoom.
* How many objects are on the screen (painted by the graphic card).
* How many entities, chunks and paths are in the game and used.
|-
| show-time-usage ||
* Internal statistics about how long some calculations take, in milliseconds per [[Game-tick|tick]].
* Time is shown as average/min/max of the last 100 ticks, interval can be changed with /perf-avg-frames.
* Minimum values exclude zeroes (e.g. from ticks where no mod hooks were run).
* Overall calculation delays (some are parallel) must be under 16.6 ms to maintain normal framerate at 1x speed with 60 ticks per second.
* The Top section of metrics cover the wider game engines activities. The middle Update section relates to running the simulation for a tick. The bottom Map Generator section relates to the map generation activity.
|-
| show-gpu-time-usage ||
|-
| show-sprite-counts || The counts of each sprite rendered on screen.
|-
| show-lua-object-statistics ||
|-
| show-multiplayer-waiting-icon || When in a multiplayer game: if the game is currently waiting for the server to process.
|-
| show-multiplayer-statistics || The latency information when in multiplayer.
|-
| show-multiplayer-selection-rectangles || Allows to view selection rectangles of other players in multiplayer.
|-
| show-debug-info-in-tooltips || Shows additional information in the tooltips of entities, items, recipes, tiles etc.
|-
| hide-mod-guis || Hides GUIs added by mods.
|-
| show-tile-grid || Shows the borders of the [[Tile (unit)|tile]]s and [[chunk]]s.
|-
| show-collision-rectangles || Shows the collision boxes of each entity (red).
|-
| show-selection-rectangles || Shows the a blue box over each entity, if you hover over it, it will be selected.
|-
| show-render-rectangles || Shows the a pink box over each entity, if that is on your screen, the entity will be rendered.
|-
| show-entity-positions ||
|-
| show-entity-velocities ||
|-
| show-selected-entity-advanced-tiles || Shows on which advanced tiles (2×2 tiles) the entity is registered.
|-
| show-selected-input-transport-belts || Shows which entities input into the selected transport line.
|-
| show-paths || The calculated paths for the biters in different colors.
|-
| show-path-requests ||
|-
| show-next-waypoint-bb || Shows waypoints for biters (in green), nearly the same info as the next.
|-
| show-target || Shows the current target of the biters (red).
|-
| show-unit-group-info || Biter groups, which belong together (circles and lines belonging together)
|-
| show-unit-behavior-info ||
|-
| show-pathfinder-fringe ||
|-
| show-path-cache || The source-positions of a path and about the length (?)
|-
| show-path-cache-paths ||
|-
| show-rail-paths || Which path a train will follow.
|-
| show-rolling-stock-count || Shows inserter positions
|-
| show-rail-connections || Shows rail connections.
|-
| show-rail-joints ||
|-
| show-rail-signal-states || Shows signal color on map view.
|-
| show-rail-segment-collision-boxes ||
|-
| show-train-stop-point || When a train slows down it shows the calculated point where it should halt
|-
| show-train-braking-distance || The distance a train will take to stop at its current speed
|-
| show-train-signals ||
|-
| show-train-repathing || Display a flying "repathed" text over a train whenever it repaths.
|-
| show-network-connected-entities || Displays the network-id of the electric network that a pole is connected to
|-
| show-circuit-network-numbers || Shows the number (and color) of circuit networks
|-
| show-energy-sources-networks || Which network-id an entity is connected to.
|-
| show-active-state || Inserters, fish, turrets are turned to passive, if not used; Red = inactive, Purple = inactive when enemies aren't around (turrets etc), Green = inactive when player isn't around (fish). Passive entities consume less CPU power.
|-
| show-wakeup-lists || When an entity is sleeping in another entity it shows which entities it's sleeping in.
|-
| show-transport-lines ||
|-
| show-transport-line-gaps ||
|-
| show-pollution-values || Shows the numeric pollution amount on each chunk.
|-
| show-active-entities-on-chunk-counts ||
Shows counts of active entities per chunk. They are devided into three categories:
* Red = active (e.g. furnaces)
* Blue = active when a player is around (e.g. fish)
* Green = active when enemies are around (e.g. turrets)
|-
| show-active-chunks || Shows in the map view, which chunks are "on", unmarked chunks are not calculated.
|-
| show-polluted-chunks || Shows which chunks have pollution.
|-
| show-enemy-expansion-candidate-chunks || Where is space left to spread the brood?. Goes from red (nearly no space) to green (space to expand).
|-
| show-enemy-expansion-candidate-chunk-values || Which chunks the enemies will try to expand into.
|-
| show-bad-attack-chunks ||
|-
| show-tile-variations || Shows, which tile-variation (1, 2 or 4 tile sized) is painted for which area of the map. Quite confusing, zoom in to see the meaning.
|-
| show-raw-tile-transitions || Turns connected textures for land and water off, so the distinction can easily be made.
|-
| show-fluid-box-fluid-info || How much fluid is in a pipe/storage tank, shows flow of liquid in pipes.
|-
| show-environment-sound-info || Displays which sound of which entity is played and how loud.
|-
| show-logistic-robot-targets ||
|-
| show-logistic-robots-on-map ||
|-
| show-recipe-icons-on-map ||
|-
| show-player-robots ||
|-
| show-fire-info ||
|-
| show-sticker-info ||
|-
| show-decorative-names ||
|-
| show-decorative-collision-rectangles ||
|-
| allow-increased-zoom ||
|-
|}

User:Jon8RFC

2019-11-07T11:15:42Z

Jon8RFC:

Interested in low-priority upkeep of grammar, punctuation, and adding to the History section.

I'll try to resist using oxford commas if it looks bad, stylistically--or if the rest of the page is flush without them--but I prefer them.

User:Jon8RFC

2019-11-07T11:14:51Z

Jon8RFC:

Interested in low-priority upkeep of grammar, punctuation, and adding to the History section.

I'll try to resist using oxford commas if it looks bad (or the rest of the page is flush without them), stylistically, but I prefer them.

User:Jon8RFC

2019-11-07T11:14:40Z

Jon8RFC:

Interested in low-priority upkeep of grammar, punctuation, and adding to the History section.
I'll try to resist using oxford commas if it looks bad (or the rest of the page is flush without them), stylistically, but I prefer them.

User:Jon8RFC

2019-11-07T11:11:23Z

Jon8RFC:

Interested in low-priority upkeep of grammar, punctuation, and adding to the History section.

Construction robot

2019-11-07T11:05:36Z

Jon8RFC: /* Mechanics */ add tile information

{{Languages}}
{{:Infobox:Construction robot}}

'''Construction robots''' are autonomous floating devices capable of repairing or building the player's structures. They are one of two type of robotic floating devices, the other being the [[logistic robot]]s. They run on electricity from [[roboport]]s.

== Mechanics ==

Construction robots accomplish various tasks, including:

* They repair damaged entities using [[repair pack]]s.
* They replace destroyed entities as long as they are available in a [[provider chest]] or [[storage chest]].
* They remove entities marked with the [[deconstruction planner]]. Removed entities are transported into storage chests. As of 0.15, this includes [[raw fish|fish]].
* They add entities marked with a [[blueprint]] or placed as [[entity ghost]]s as long as these entities are available. Entities are fetched from the closest logistic chest.
* They can carry and place up to four [[tile]]s at once, as of 0.17.75.

Construction robots are priority targets of [[enemies]], meaning Biters/spitters will engage them even if there are [[pollution]]-producing buildings around. Construction robots have no means of defending themselves and do not run when they encounter enemies. Because they often operate at the "front", they are in high danger to be destroyed. Despite being a floating entity, ground units using melee are still capable of destroying them.

Researching [[Worker robot cargo size (research)|more cargo]] or [[Worker robot speed (research)|more speed]] for the logistic bots are also valid for the construction robots.

== Achievements ==
{{Achievement|automated-cleanup}}
{{Achievement|automated-construction}}
{{Achievement|you-are-doing-it-right}}

== History ==

{{history|0.17.75|
* Construction robots will attempt to batch build tiles.}}

{{history|0.17.0|
* Construction robots can blow up cliffs.
* Landfill can be built by construction robots and be included in blueprints.}}

{{history|0.15.0|
* Fish can be collected by construction robots.}}

{{history|0.12.4|
* Construction robots when used by the player will take primarily from the player's inventory, then the hotbar.
* Construction robots will check if their target is still in the network area when they return to personal roboport for charging.
}}

{{history|0.12.0|
* Construction robots can now be used by the player via a [[personal roboport]] embedded into a type of modular armor.}}

{{history|0.11.17|
* AI of the construction robots improved.}}

{{history|0.10.2|
* Construction robots take as many [[repair pack]]s as they can when going to repair.}}

{{history|0.10.0|
* Construction robots no longer die of lack of electricity, they just slow down to 20% of their normal speed.}}

{{history|0.9.0|
* The [[deconstruction planner]] can be used to order bots to destroy buildings/trees.}}

{{history|0.8.6|
* Robots can rebuild [[land mine]]s.}}

{{history|0.8.1|
* Construction robots now use the durability of the [[repair pack]]s when using them.}}

{{history|0.8.0|
* Introduced}}

== See also ==
* [[Robots]]
* [[Logistic robot]]
* [[Repair pack]]

{{LogisticsNav}}
{{C|Logistic network}}