Official Factorio Wiki - User contributions [en]

Energy and work

2017-07-19T20:38:54Z

Ssilk:

{{Languages}}
Factorio simulates many aspects of real physics and the quite correct use of energy is one important aspect.

Energy and work are directly dependent.

== Game physics is not reality ==

The Factorio Game physics is quite realistic, but simplified. Please do not compare this definition to those of [http://en.wikipedia.org/wiki/Work_%28physics%29 real physic]. See also the [[Talk:Energy and Work|Talk-page]].

Another explanation can be found in the [https://forums.factorio.com/viewtopic.php?f=18&t=33963 Forum]

== Work ==

'''Work is "stored energy" or the "result of using power". If you divide the work into parts and release the parts in some time you have energy.

Work is measured in [[Units#Work|Joules]], which is one Watt over the time of one second.

See [[Units#Work]].

=== Types of work ===

Work is available (or storable) as
* [[Fuel]].
* Capacity in the [[Basic accumulator]]s.
* [[Steam]]. It can be created in [[boiler]]s or [[heat exchanger]]s and stored in the [[Storage Tank]].

== Energy / Power ==

'''Energy is the "ability to do work". The speed of this doing needs more or less power. The faster something works, the more power is needed, but the result (the work) is the same. In Factorio this is also used a lot to [[Mining drill#Mining_Speed_Formula|calculate, how much time is needed to produce stuff]].

Energy is measured in [[Units#Power|Watts]], nearly every device in Factorio needs energy to work. Energy is produced by [[Electric system|Generators]], [[Boiler]]- or other burner- (or motor-driven) devices (like the car or train).

See [[Units#Power]].

=== Types of energy ===

==== [[Fuel|Fuel-based]] (Boiler, Burner) ====

[[Fuel]] contains a certain amount of energy. The fuel is burned and produces energy (which is converted into movement or heat) and [[Pollution]] is emitted.

There are [[Fuel#Burner devices to be fueled directly|some devices]], which can use fuel directly.

==== [[Electric system|Electricity]] ====

[[Electric system|Electricity]] is produced by [[Electric system|Generators]]. The [[Electric system|distribution]] is made over an [[Electric system|Electric network]], and it is used by [[Electric system|Consumer]]s.

That's the single parts! The whole process is also explained as [[Electric system|Power Production]].

Electricity is the only way to transport energy over long distances. [[Electric system|Electricity]] itself doesn't pollute, the pollution comes either from burning fuel or consuming electricity.

Achievements

2017-01-28T17:55:28Z

Ssilk:

{{Languages}}

''Achievements'' are a new feature added in 0.13. They keep track of notable milestones obtained while playing. Achievements are available both in the [http://store.steampowered.com/app/427520/ Steam] and DRM-free versions of the game, such as downloading from the factorio site.

== Disabling achievements ==

Achievements will be disabled on use of the [[Console]] or installing mods. If mods are installed, a separate instance of achievements will be used, and earned achievements will not register with Steam.

== List of all achievements ==
''Tip: This is a very large table. Use {{keybinding|CTRL|F}} on most browsers to find specific achievements easily.''

{| class="wikitable"
|-
! Achievement !! Icon !! Description
|-
| Automated cleanup || [[File:automated-cleanup-achievement.png|64x64px]] || De-construct 100 objects with the [[construction robot]]s.
|-
| Circuit veteran 1 || [[File:circuit-veteran-1-achievement.png|64x64px]] ||Produce 1.0k [[Advanced circuit]]s per hour.
|-
| Computer age 1 ||[[File:computer-age-1-achievement.png|64x64px]] || Produce 500 [[Processing unit]]s per hour.
|-
| You've got a package ||[[File:you-have-got-a-package-achievement.png|64x64px]] || Supply the player by [[logistic robot]].
|-
| Eco unfriendly ||[[File:eco-unfriendly-achievement.png|64x64px]] || Research [[Oil processing]].
|-
| Iron throne 1||[[File:iron-throne-1-achievement.png|64x64px]] ||Produce 20k [[Iron plate]]s per hour.
|-
| It stinks and they don't like it|| [[File:it-stinks-and-they-dont-like-it-achievement.png|64x64px]]||Trigger an alien attack by pollution.
|-
| Mass production 1||[[File:mass-production-1-achievement.png|64x64px]] ||Produce 10k [[Electronic circuit]]s.
|-
| Solaris||[[File:solaris-achievement.png|64x64px]] || Produce more than 10 GJ energy per hour without the usage of [[Steam engine]].
|-
| Automated construction || [[File:automated-construction-achievement.png|64x64px]]||Construct 100 machines using robots.
|-
| Circuit veteran 2||[[File:circuit-veteran-2-achievement.png|64x64px]] ||Produce 10k [[Advanced circuit]]s per hour.
|-
| Circuit veteran 3|| [[File:circuit-veteran-3-achievement.png|64x64px]]||Produce 25k [[Advanced circuit]]s per hour.
|-
| Computer age 3|| [[File:computer-age-3-achievement.png|64x64px]]|| Produce 5k [[Processing unit]]s per hour.
|-
| Computer age 2|| [[File:computer-age-2-achievement.png|64x64px]]|| Produce 1.0k [[Processing unit]]s per hour.
|-
| Delivery service ||[[File:delivery-service-achievement.png|64x64px]] || Supply the player with 10k items delivered by the [[logistic robot]]s.
|-
| Getting on track||[[File:getting-on-track-achievement.png|64x64px]] ||Build a [[Diesel locomotive]].
|-
| Getting on track like a pro||[[File:getting-on-track-like-a-pro-achievement.png|64x64px]] ||Build a [[Diesel locomotive]] within first 1 hour and 30 minutes of the game.
|-
| Golem|| [[File:golem-achievement.png|64x64px]]||Take 500 [[damage]] in one hit and survive.
|-
| Iron throne 2|| [[File:iron-throne-2-achievement.png|64x64px]]||Produce 200k [[Iron plate]]s per hour
|-
| Iron throne 3||[[File:iron-throne-3-achievement.png|64x64px]] ||Produce 400k [[Iron plate]]s per hour.
|-
| Lazy bastard || [[File:lazy-bastard-achievement.png|64x64px]]||Win the game by crafting no more than 111 items manually.
|-
| [[Logistic network]] embargo||[[File:logistic-network-embargo-achievement.png|64x64px]] ||Win the game without building [[Active provider chest]] and [[requester chest]].
|-
| Mass production 2||[[File:mass-production-2-achievement.png|64x64px]] ||Produce 1M [[electronic circuit]]s.
|-
| Mass production 3||[[File:mass-production-3-achievement.png|64x64px]] ||Produce 20M [[Electronic circuit]]s.
|-
| Minions||[[File:minions-achievement.png|64x64px]] ||Get 100 combat robots following you
|-
| Smoke me a kipper, I'll be back for breakfast|| [[File:smoke-me-a-kipper-i-will-be-back-for-breakfast-achievement.png|64x64px]]||Finish the game.
|-
| No time for chit-chat||[[File:no-time-for-chitchat-achievement.png|64x64px]] ||Finish the game in 15 hours
|-
| There is no spoon|| [[File:there-is-no-spoon-achievement.png|64x64px]]||Finish the game in 8 hours
|-
| Pyromaniac||[[File:pyromaniac-achievement.png|64x64px]] ||Destroy 10k trees with fire
|-
| Raining bullets|| [[File:raining-bullets-achievement.png|64x64px]]||Win the game without building [[Laser turret]].
|-
| Run forrest run ||[[File:run-forrest-run-achievement.png|64x64px]] ||Destroy 100 trees by impact.
|-
| So long and thanks for all the fish|| [[File:so-long-and-thanks-for-all-the-fish-achievement.png|64x64px]]|| {{spoiler|button-text=Spoiler! Click to view.|message=Send a raw fish into space via rocket.}}
|-
| Steam all the way||[[File:steam-all-the-way-achievement.png|64x64px]] ||Win the game without using a [[solar panel]].
|-
| Streamrolled|| [[File:steamrolled-achievement.png|64x64px]]||Destroy 10 [[Spawners]] by impact.
|-
| Tech maniac||[[File:tech-maniac-achievement.png|64x64px]] ||Research all technologies
|-
| Trans factorio express|| [[File:trans-factorio-express-achievement.png|64x64px]]||Have a [[Train]] plans a path 1000 tiles long.
|-
| Watch your step||[[File:watch-your-step-achievement.png|64x64px]] ||Get killed by moving Locomotive.
|-
| You are doing it right!|| [[File:you-are-doing-it-right-achievement.png|64x64px]]||Construct more machines using robots than manually.
|}

== How to Re-Enable Achievements ==

See this [https://forums.factorio.com/viewtopic.php?f=5&t=29709&start=20 forum thread].

== See also ==

* [[Console]]
* [https://www.factorio.com/blog/post/fff-125 Friday Facts #125 - Achievements]

Belt transport system

2016-12-21T23:24:02Z

Ssilk:

{{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]], make up the systems of item transportation in
Factorio.

Belts specifically are used to transport [[Items]]. By developer design, all transport belts run without using energy.
This is to reduce complexity and allow belts to be placed outside of electricity networks.

== All types of Transport belts ==

Below is a chart of all the Transport Belts present and available for use in Factorio.

{| class="wikitable"
! [[Transport belts]] !! [[Underground belts]] !! [[Splitters]] !! Max. throughput ([[Items]] per [[game-second]]) !! Needed research
|-
| {{imagelink|basic-transport-belt|Basic transport belt}}
| {{imagelink|basic-transport-belt-to-ground|Basic underground belt}}
| {{imagelink|basic-splitter|Basic splitter}}
| 13.333
| [[Logistics 1]]
|-
| {{imagelink|fast-transport-belt|Fast transport belt}}
| {{imagelink|fast-transport-belt-to-ground|Fast underground belt}}
| {{imagelink|fast-splitter|Fast splitter}}
| 26.666
| [[Logistics 2]]
|-
| {{imagelink|express-transport-belt|Express transport belt}}
| {{imagelink|express-transport-belt-to-ground|Express underground belt}}
| {{imagelink|express-splitter|Express splitter}}
| 40.0
| [[Logistics 3]]
|-
|}

 See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

== Tiers of belts ==

[[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. [[Transport belt|The basic type]] has a yellow color and is
the slowest. [[Fast transport belt|Next tier up]] has a red color, and is twice is fast as the yellow tier. [[Express transport belt|The third]] and final tier is colored blue and is three times as fast.

{{clear}}

== Mechanics of belts ==

This section describes the mechanics of transport belts.

=== 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 with
some careful setup, transporting two different materials on the same belt. Mixed belts can be beneficial for
smelting ore, or producing items with many different ingredients such as [[science pack 3]]. Un-merging a mixed belt is
fairly easy too, since an underground belt will block half of the belt.

[[File:Transport_belts_merge.gif|300px|top]]   [[File:Transport_belts_unmerge.gif|300px|top]]

Commonly, merging and un-merging is done by using a [[splitter]]. The trick in the second picture is better described in '''[[Underground_belts/More_uses|More uses of Underground Belt]]'''.

=== Belt 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 how to do this:

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

=== Belt Throughput ===

Maximizing the throughput is important, since it will keep belts efficient. Therefore some definitions need to
be introduced:

; Speed
: How fast a belt moves.
; Density
: How tight are the items put onto the belts.
; Throughput
: This is speed * density. It describes how many items pass by in a given time.

So, there are three opportunities to enhance the throughput:

* More density

Sometimes items have little spaces next to each other that aren't big enough for other items to fit
in. In this case reordering the items can still increase the density. This can be done by temporarily increasing the
belt speed on a single tile or by merging 2 lanes with an inserter.

The gif below shows the problem with a low density belt, and the right shows how it can be rectified. (Notice the red belt)

[[File:Transport_belts_density.gif|top|300px]]

* 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, and add [[splitter]]s to balance items between them.

=== 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 are [[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 make inserters more
effective.

=== Placement ===
{| style="float:right; padding-left:10px; padding-right:10px;">
| style="padding-right:1em" | [[File:Transport_belts_notplace.gif|300px|top]]
| style="padding-right:1em" | [[File:Transport_belts_doplace.gif|300px|top]]
| [[File:Transport_belts_replace.gif|300px|top]]
|}

While conveyor belts can be placed in a line by clicking and dragging the mouse, it is often easier to hold the mouse down and move your character. Conveyor belts can be rotated after being placed by hovering over them with an empty hand and pressing {{keybinding|r}}, or by building over them with another conveyor belt. Conveyor belts can also be upgraded in this manner, by placing the another belt over top of it.

{{clear}}

== Splitters ==

[[Splitters]] are another form of item manipulation. Splitters are a 2x1 tile that split incoming [[Item]]s on belts
from one input to two outputs, in a 50/50 ratio. They are used to divide resources between two belts, or balance
multiple belts.

== Mechanics of splitters ==

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 it's two sides.

* If one of the outputs is fully backed-up and the splitter cannot split evenly, it will put all input on it's other
output.

* Splitters can also take two inputs and one output.

The output will be an even mix of both the inputs. This can be
used to efficiently merge two belts together. When it does this, the items will not be shuffled.

In order to join/split belts, the splitter must be the same speed as the incoming belts, otherwise the splitter will
become a bottleneck.

However, when both belts are at full capacity, the splitter will prefer one side, and use the other to fill gaps. This
behavior is due to the game being unable to fairly reverse-split the belts. Explained by the developers:

''"But there are fundamental problems with equal joining. How exactly will you define it? Once you have an available
item to move to the belt on the left belt, you would have to wait, if some other item on the right belt doesn't
arrive, as it would be the time for the right belt to be activated. But how long do you wait? And once you wait you
limit the throughput of the splitter."''

This behavior can be used to prioritize input from certain belts, such as from a storage.

=== Diving/Weightng ===

See [[Splitters/Weighted_splitters|Weighted Splitters]]

== Underground belts ==

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

* You can cross any number of entities and all types of ground, like water, swamps, etc. (input and output of course over water)
* You can cross other underground stuff (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 4 [[tile]]s.
* An underground belt pair with a blocked output stores up to 20 items. (Per lane? Untested!)
* If you mine an underground belt, up to 20 items are recovered, the remaining items in the underground are placed into your inventory.
* 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.

''This last fact is important, because it can be used to do some tricks.''

More information in '''[[Underground_belts/More_uses|More uses of Underground Belt]]'''.

== See also ==
* [[Splitter]]
* [[Transport belt]]
* [[Time]]
* [[Items]]

Belt transport system

2016-12-21T23:20:04Z

Ssilk:

{{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]], make up the systems of item transportation in
Factorio.

Belts specifically are used to transport [[Items]]. By developer design, all transport belts run without using energy.
This is to reduce complexity and allow belts to be placed outside of electricity networks.

== All types of Transport belts ==

Below is a chart of all the Transport Belts present and available for use in Factorio.

{| class="wikitable"
! [[Transport belts]] !! [[Underground belts]] !! [[Splitters]] !! Max. throughput ([[Items]] per [[game-second]]) !! Needed research
|-
| {{imagelink|basic-transport-belt|Basic transport belt}}
| {{imagelink|basic-transport-belt-to-ground|Basic underground belt}}
| {{imagelink|basic-splitter|Basic splitter}}
| 13.333
| [[Logistics 1]]
|-
| {{imagelink|fast-transport-belt|Fast transport belt}}
| {{imagelink|fast-transport-belt-to-ground|Fast underground belt}}
| {{imagelink|fast-splitter|Fast splitter}}
| 26.666
| [[Logistics 2]]
|-
| {{imagelink|express-transport-belt|Express transport belt}}
| {{imagelink|express-transport-belt-to-ground|Express underground belt}}
| {{imagelink|express-splitter|Express splitter}}
| 40.0
| [[Logistics 3]]
|-
|}

 See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

== Tiers of belts ==

[[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. [[Transport belt|The basic type]] has a yellow color and is
the slowest. [[Fast transport belt|Next tier up]] has a red color, and is twice is fast as the yellow tier. [[Express transport belt|The third]] and final tier is colored blue and is three times as fast.

{{clear}}

== Mechanics of belts ==

This section describes the mechanics of transport belts.

=== 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 with
some careful setup, transporting two different materials on the same belt. Mixed belts can be beneficial for
smelting ore, or producing items with many different ingredients such as [[science pack 3]]. Un-merging a mixed belt is
fairly easy too, since an underground belt will block half of the belt.

[[File:Transport_belts_merge.gif|300px|top]]   [[File:Transport_belts_unmerge.gif|300px|top]]

Commonly, merging and un-merging is done by using a [[splitter]]. The trick in the second picture is better described in '''[[Underground_belts/More_uses|More uses of Underground Belt]]'''.

=== Belt 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 how to do this:

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

=== Belt Throughput ===

Maximizing the throughput is important, since it will keep belts efficient. Therefore some definitions need to
be introduced:

; Speed
: How fast a belt moves.
; Density
: How tight are the items put onto the belts.
; Throughput
: This is speed * density. It describes how many items pass by in a given time.

So, there are three opportunities to enhance the throughput:

* More density

Sometimes items have little spaces next to each other that aren't big enough for other items to fit
in. In this case reordering the items can still increase the density. This can be done by temporarily increasing the
belt speed on a single tile or by merging 2 lanes with an inserter.

The gif below shows the problem with a low density belt, and the right shows how it can be rectified. (Notice the red belt)

[[File:Transport_belts_density.gif|top|300px]]

* 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, and add [[splitter]]s to balance items between them.

=== 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 are [[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 make inserters more
effective.

=== Placement ===
{| style="float:right; padding-left:10px; padding-right:10px;">
| style="padding-right:1em" | [[File:Transport_belts_notplace.gif|300px|top]]
| style="padding-right:1em" | [[File:Transport_belts_doplace.gif|300px|top]]
| [[File:Transport_belts_replace.gif|300px|top]]
|}

While conveyor belts can be placed in a line by clicking and dragging the mouse, it is often easier to hold the mouse down and move your character. Conveyor belts can be rotated after being placed by hovering over them with an empty hand and pressing {{keybinding|r}}, or by building over them with another conveyor belt. Conveyor belts can also be upgraded in this manner, by placing the another belt over top of it.

{{clear}}

== Splitters ==

[[Splitters]] are another form of item manipulation. Splitters are a 2x1 tile that split incoming [[Item]]s on belts
from one input to two outputs, in a 50/50 ratio. They are used to divide resources between two belts, or balance
multiple belts.

== Mechanics of splitters ==

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 it's two sides.

* If one of the outputs is fully backed-up and the splitter cannot split evenly, it will put all input on it's other
output.

* Splitters can also take two inputs and one output.

The output will be an even mix of both the inputs. This can be
used to efficiently merge two belts together. When it does this, the items will not be shuffled.

In order to join/split belts, the splitter must be the same speed as the incoming belts, otherwise the splitter will
become a bottleneck.

However, when both belts are at full capacity, the splitter will prefer one side, and use the other to fill gaps. This
behavior is due to the game being unable to fairly reverse-split the belts. Explained by the developers:

''"But there are fundamental problems with equal joining. How exactly will you define it? Once you have an available
item to move to the belt on the left belt, you would have to wait, if some other item on the right belt doesn't
arrive, as it would be the time for the right belt to be activated. But how long do you wait? And once you wait you
limit the throughput of the splitter."''

This behavior can be used to prioritize input from certain belts, such as from a storage.

=== Diving/Weightng ===

See [[Splitters/Weighted_splitters|Weighted Splitters]]

== Underground belts ==

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

* You can cross any number of entities and all types of ground, like water, swamps, etc. (input and output of course over water)
* You can cross other underground stuff (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 4 [[tile]]s.
* An underground belt pair with a blocked output stores up to 20 items. (Per lane? Untested!)
* If you mine an underground belt, up to 20 items are recovered, the remaining items in the underground are placed into your inventory.
* 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.

''This last fact is important, because it can be used to do some tricks.''

== See also ==
* [[Splitter]]
* [[Transport belt]]
* [[Time]]
* [[Items]]

Belt transport system

2016-12-21T23:18:57Z

Ssilk:

{{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]], make up the systems of item transportation in
Factorio.

Belts specifically are used to transport [[Items]]. By developer design, all transport belts run without using energy.
This is to reduce complexity and allow belts to be placed outside of electricity networks.

== All types of Transport belts ==

Below is a chart of all the Transport Belts present and available for use in Factorio.

{| class="wikitable"
! [[Transport belts]] !! [[Underground belts]] !! [[Splitters]] !! Max. throughput ([[Items]] per [[game-second]]) !! Needed research
|-
| {{imagelink|basic-transport-belt|Basic transport belt}}
| {{imagelink|basic-transport-belt-to-ground|Basic underground belt}}
| {{imagelink|basic-splitter|Basic splitter}}
| 13.333
| [[Logistics 1]]
|-
| {{imagelink|fast-transport-belt|Fast transport belt}}
| {{imagelink|fast-transport-belt-to-ground|Fast underground belt}}
| {{imagelink|fast-splitter|Fast splitter}}
| 26.666
| [[Logistics 2]]
|-
| {{imagelink|express-transport-belt|Express transport belt}}
| {{imagelink|express-transport-belt-to-ground|Express underground belt}}
| {{imagelink|express-splitter|Express splitter}}
| 40.0
| [[Logistics 3]]
|-
|}

 See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

== Tiers of belts ==

[[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. [[Transport belt|The basic type]] has a yellow color and is
the slowest. [[Fast transport belt|Next tier up]] has a red color, and is twice is fast as the yellow tier. [[Express transport belt|The third]] and final tier is colored blue and is three times as fast.

{{clear}}

== Mechanics of belts ==

This section describes the mechanics of transport belts.

=== 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 with
some careful setup, transporting two different materials on the same belt. Mixed belts can be beneficial for
smelting ore, or producing items with many different ingredients such as [[science pack 3]]. Un-merging a mixed belt is
fairly easy too, since an underground belt will block half of the belt.

[[File:Transport_belts_merge.gif|300px|top]]   [[File:Transport_belts_unmerge.gif|300px|top]]

Commonly, merging and un-merging is done by using a [[splitter]]. The trick in the second picture is better described in '''[[Underground_belts/More_uses|More uses of Underground Belt]]'''.

Some of this [[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).]]

=== Belt 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 how to do this:

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

=== Belt Throughput ===

Maximizing the throughput is important, since it will keep belts efficient. Therefore some definitions need to
be introduced:

; Speed
: How fast a belt moves.
; Density
: How tight are the items put onto the belts.
; Throughput
: This is speed * density. It describes how many items pass by in a given time.

So, there are three opportunities to enhance the throughput:

* More density

Sometimes items have little spaces next to each other that aren't big enough for other items to fit
in. In this case reordering the items can still increase the density. This can be done by temporarily increasing the
belt speed on a single tile or by merging 2 lanes with an inserter.

The gif below shows the problem with a low density belt, and the right shows how it can be rectified. (Notice the red belt)

[[File:Transport_belts_density.gif|top|300px]]

* 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, and add [[splitter]]s to balance items between them.

=== 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 are [[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 make inserters more
effective.

=== Placement ===
{| style="float:right; padding-left:10px; padding-right:10px;">
| style="padding-right:1em" | [[File:Transport_belts_notplace.gif|300px|top]]
| style="padding-right:1em" | [[File:Transport_belts_doplace.gif|300px|top]]
| [[File:Transport_belts_replace.gif|300px|top]]
|}

While conveyor belts can be placed in a line by clicking and dragging the mouse, it is often easier to hold the mouse down and move your character. Conveyor belts can be rotated after being placed by hovering over them with an empty hand and pressing {{keybinding|r}}, or by building over them with another conveyor belt. Conveyor belts can also be upgraded in this manner, by placing the another belt over top of it.

{{clear}}

== Splitters ==

[[Splitters]] are another form of item manipulation. Splitters are a 2x1 tile that split incoming [[Item]]s on belts
from one input to two outputs, in a 50/50 ratio. They are used to divide resources between two belts, or balance
multiple belts.

== Mechanics of splitters ==

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 it's two sides.

* If one of the outputs is fully backed-up and the splitter cannot split evenly, it will put all input on it's other
output.

* Splitters can also take two inputs and one output.

The output will be an even mix of both the inputs. This can be
used to efficiently merge two belts together. When it does this, the items will not be shuffled.

In order to join/split belts, the splitter must be the same speed as the incoming belts, otherwise the splitter will
become a bottleneck.

However, when both belts are at full capacity, the splitter will prefer one side, and use the other to fill gaps. This
behavior is due to the game being unable to fairly reverse-split the belts. Explained by the developers:

''"But there are fundamental problems with equal joining. How exactly will you define it? Once you have an available
item to move to the belt on the left belt, you would have to wait, if some other item on the right belt doesn't
arrive, as it would be the time for the right belt to be activated. But how long do you wait? And once you wait you
limit the throughput of the splitter."''

This behavior can be used to prioritize input from certain belts, such as from a storage.

=== Diving/Weightng ===

See [[Splitters/Weighted_splitters|Weighted Splitters]]

== Underground belts ==

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

* You can cross any number of entities and all types of ground, like water, swamps, etc. (input and output of course over water)
* You can cross other underground stuff (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 4 [[tile]]s.
* An underground belt pair with a blocked output stores up to 20 items. (Per lane? Untested!)
* If you mine an underground belt, up to 20 items are recovered, the remaining items in the underground are placed into your inventory.
* 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.

''This last fact is important, because it can be used to do some tricks.''

== See also ==
* [[Splitter]]
* [[Transport belt]]
* [[Time]]
* [[Items]]

Belt transport system

2016-12-21T23:05:18Z

Ssilk:

{{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]], make up the systems of item transportation in
Factorio.

Belts specifically are used to transport [[Items]]. By developer design, all transport belts run without using energy.
This is to reduce complexity and allow belts to be placed outside of electricity networks.

== All types of Transport belts ==

Below is a chart of all the Transport Belts present and available for use in Factorio.

{| class="wikitable"
! [[Transport belts]] !! [[Underground belts]] !! [[Splitters]] !! Max. throughput ([[Items]] per [[game-second]]) !! Needed research
|-
| {{imagelink|basic-transport-belt|Basic transport belt}}
| {{imagelink|basic-transport-belt-to-ground|Basic underground belt}}
| {{imagelink|basic-splitter|Basic splitter}}
| 13.333
| [[Logistics 1]]
|-
| {{imagelink|fast-transport-belt|Fast transport belt}}
| {{imagelink|fast-transport-belt-to-ground|Fast underground belt}}
| {{imagelink|fast-splitter|Fast splitter}}
| 26.666
| [[Logistics 2]]
|-
| {{imagelink|express-transport-belt|Express transport belt}}
| {{imagelink|express-transport-belt-to-ground|Express underground belt}}
| {{imagelink|express-splitter|Express splitter}}
| 40.0
| [[Logistics 3]]
|-
|}

 See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

[[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).]]
== Tiers of belts ==

There are 3 different tiers of belts available for use. [[Transport belt|The basic type]] has a yellow color and is
the slowest. [[Fast transport belt|Next tier up]] has a red color, and is twice is fast as the yellow tier. [[Express transport belt|The third]] and final tier is colored blue and is three times as fast.

{{clear}}

== Mechanics of belts ==

This section describes the mechanics of transport belts.

=== 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 with
some careful setup, transporting two different materials on the same belt. Mixed belts can be beneficial for
smelting ore, or producing items with many different ingredients such as [[science pack 3]]. Un-merging a mixed belt is
fairly easy too, since an underground belt will block half of the belt.

[[File:Transport_belts_merge.gif|300px|top]]   [[File:Transport_belts_unmerge.gif|300px|top]]

Commonly, merging and un-merging is done by using a [[splitter]].

=== Belt 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 how to do this:

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

=== Belt Throughput ===

Maximizing the throughput is important, since it will keep belts efficient. Therefore some definitions need to
be introduced:

; Speed
: How fast a belt moves.
; Density
: How tight are the items put onto the belts.
; Throughput
: This is speed * density. It describes how many items pass by in a given time.

So, there are three opportunities to enhance the throughput:

* More density

Sometimes items have little spaces next to each other that aren't big enough for other items to fit
in. In this case reordering the items can still increase the density. This can be done by temporarily increasing the
belt speed on a single tile or by merging 2 lanes with an inserter.

The gif below shows the problem with a low density belt, and the right shows how it can be rectified. (Notice the red belt)

[[File:Transport_belts_density.gif|top|300px]]

* 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, and add [[splitter]]s to balance items between them.

=== 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 are [[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 make inserters more
effective.

=== Placement ===
{| style="float:right; padding-left:10px; padding-right:10px;">
| style="padding-right:1em" | [[File:Transport_belts_notplace.gif|300px|top]]
| style="padding-right:1em" | [[File:Transport_belts_doplace.gif|300px|top]]
| [[File:Transport_belts_replace.gif|300px|top]]
|}

While conveyor belts can be placed in a line by clicking and dragging the mouse, it is often easier to hold the mouse down and move your character. Conveyor belts can be rotated after being placed by hovering over them with an empty hand and pressing {{keybinding|r}}, or by building over them with another conveyor belt. Conveyor belts can also be upgraded in this manner, by placing the another belt over top of it.

{{clear}}

== Splitters ==

[[Splitters]] are another form of item manipulation. Splitters are a 2x1 tile that split incoming [[Item]]s on belts
from one input to two outputs, in a 50/50 ratio. They are used to divide resources between two belts, or balance
multiple belts.

== Mechanics of splitters ==

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 it's two sides.

* If one of the outputs is fully backed-up and the splitter cannot split evenly, it will put all input on it's other
output.

* Splitters can also take two inputs and one output.

The output will be an even mix of both the inputs. This can be
used to efficiently merge two belts together. When it does this, the items will not be shuffled.

In order to join/split belts, the splitter must be the same speed as the incoming belts, otherwise the splitter will
become a bottleneck.

However, when both belts are at full capacity, the splitter will prefer one side, and use the other to fill gaps. This
behavior is due to the game being unable to fairly reverse-split the belts. Explained by the developers:

''"But there are fundamental problems with equal joining. How exactly will you define it? Once you have an available
item to move to the belt on the left belt, you would have to wait, if some other item on the right belt doesn't
arrive, as it would be the time for the right belt to be activated. But how long do you wait? And once you wait you
limit the throughput of the splitter."''

This behavior can be used to prioritize input from certain belts, such as from a storage.

Diving/Weightng

See [[Splitters/Weighted_splitters|Weighted Splitters]]

== Underground belts ==

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

* You can cross any number of entities and all types of ground, like water, swamps, etc. (input and output of course over water)
* You can cross other underground stuff (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 4 [[tile]]s.
* An underground belt pair with a blocked output stores up to 20 items. (Per lane? Untested!)
* If you mine an underground belt, up to 20 items are recovered, the remaining items in the underground are placed into your inventory.
* 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.

''This last fact is important, because it can be used to do some tricks.''

== See also ==
* [[Splitter]]
* [[Transport belt]]
* [[Time]]
* [[Items]]

Belt transport system

2016-12-21T22:57:32Z

Ssilk:

{{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]], make up the systems of item transportation in
Factorio.

Belts specifically are used to transport [[Items]]. By developer design, all transport belts run without using energy.
This is to reduce complexity and allow belts to be placed outside of electricity networks.

== All types of Transport belts ==

Below is a chart of all the Transport Belts present and available for use in Factorio.

{| class="wikitable"
! [[Transport belts]] !! [[Underground belts]] !! [[Splitters]] !! Max. throughput ([[Items]] per [[game-second]]) !! Needed research
|-
| {{imagelink|basic-transport-belt|Basic transport belt}}
| {{imagelink|basic-transport-belt-to-ground|Basic underground belt}}
| {{imagelink|basic-splitter|Basic splitter}}
| 13.333
| [[Logistics 1]]
|-
| {{imagelink|fast-transport-belt|Fast transport belt}}
| {{imagelink|fast-transport-belt-to-ground|Fast underground belt}}
| {{imagelink|fast-splitter|Fast splitter}}
| 26.666
| [[Logistics 2]]
|-
| {{imagelink|express-transport-belt|Express transport belt}}
| {{imagelink|express-transport-belt-to-ground|Express underground belt}}
| {{imagelink|express-splitter|Express splitter}}
| 40.0
| [[Logistics 3]]
|-
|}

 See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

[[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).]]
== Tiers of belts ==

There are 3 different tiers of belts available for use. [[Transport belt|The basic type]] has a yellow color and is
the slowest. [[Fast transport belt|Next tier up]] has a red color, and is twice is fast as the yellow tier. [[Express transport belt|The third]] and final tier is colored blue and is three times as fast.

{{clear}}

== Mechanics of belts ==

This section describes the mechanics of transport belts.

=== 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 with
some careful setup, transporting two different materials on the same belt. Mixed belts can be beneficial for
smelting ore, or producing items with many different ingredients such as [[science pack 3]]. Un-merging a mixed belt is
fairly easy too, since an underground belt will block half of the belt.

[[File:Transport_belts_merge.gif|300px|top]]   [[File:Transport_belts_unmerge.gif|300px|top]]

Commonly, merging and un-merging is done by using a [[splitter]].

=== Belt 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 how to do this:

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

=== Belt Throughput ===

Maximizing the throughput is important, since it will keep belts efficient. Therefore some definitions need to
be introduced:

; Speed
: How fast a belt moves.
; Density
: How tight are the items put onto the belts.
; Throughput
: This is speed * density. It describes how many items pass by in a given time.

So, there are three opportunities to enhance the throughput:

* More density

Sometimes items have little spaces next to each other that aren't big enough for other items to fit
in. In this case reordering the items can still increase the density. This can be done by temporarily increasing the
belt speed on a single tile or by merging 2 lanes with an inserter.

The gif below shows the problem with a low density belt, and the right shows how it can be rectified. (Notice the red belt)

[[File:Transport_belts_density.gif|top|300px]]

* 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, and add [[splitter]]s to balance items between them.

=== Belt physics ===

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 are [[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 make inserters more
effective.

=== Placement ===
{| style="float:right; padding-left:10px; padding-right:10px;">
| style="padding-right:1em" | [[File:Transport_belts_notplace.gif|300px|top]]
| style="padding-right:1em" | [[File:Transport_belts_doplace.gif|300px|top]]
| [[File:Transport_belts_replace.gif|300px|top]]
|}

While conveyor belts can be placed in a line by clicking and dragging the mouse, it is often easier to hold the mouse down and move your character. Conveyor belts can be rotated after being placed by hovering over them with an empty hand and pressing {{keybinding|r}}, or by building over them with another conveyor belt. Conveyor belts can also be upgraded in this manner, by placing the another belt over top of it.

{{clear}}

== Splitters ==

[[Splitters]] are another form of item manipulation. Splitters are a 2x1 tile that split incoming [[Item]]s on belts
from one input to two outputs, in a 50/50 ratio. They are used to divide resources between two belts, or balance
multiple belts.

== Mechanics of splitters ==

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 it's two sides.

* If one of the outputs is fully backed-up and the splitter cannot split evenly, it will put all input on it's other
output.

* Splitters can also take two inputs and one output.

The output will be an even mix of both the inputs. This can be
used to efficiently merge two belts together. When it does this, the items will not be shuffled.

In order to join/split belts, the splitter must be the same speed as the incoming belts, otherwise the splitter will
become a bottleneck.

However, when both belts are at full capacity, the splitter will prefer one side, and use the other to fill gaps. This
behavior is due to the game being unable to fairly reverse-split the belts. Explained by the developers:

''"But there are fundamental problems with equal joining. How exactly will you define it? Once you have an available
item to move to the belt on the left belt, you would have to wait, if some other item on the right belt doesn't
arrive, as it would be the time for the right belt to be activated. But how long do you wait? And once you wait you
limit the throughput of the splitter."''

This behavior can be used to prioritize input from certain belts, such as from a storage.

== Underground belts ==

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

* You can cross any number of entities and all types of ground, like water, swamps, etc. (input and output of course over water)
* You can cross other underground stuff (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 4 [[tile]]s.
* An underground belt pair with a blocked output stores up to 20 items. (Per lane? Untested!)
* If you mine an underground belt, up to 20 items are recovered, the remaining items in the underground are placed into your inventory.
* 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.

''This last fact is important, because it can be used to do some tricks.''

== See also ==
* [[Splitter]]
* [[Transport belt]]
* [[Time]]
* [[Items]]

Express transport belt

2016-12-21T22:48:04Z

Ssilk:

{{Languages}}

{{:Express transport belt/infobox}}
The [[Express transport belt]] is the most advanced variant of the [[Basic transport belt]]. Its available when [[Logistics 3]] has been [[Research|researched]]. Its behaviour is exactly the same as the [[Basic transport belt]] at triple speed. Making an express transport belt is costly and should be used mainly in places where high throughput is needed.

See '''[[Transport_belts|Transport belts]]''' for more general information about transport belts.

[[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 [[game-second]]*)
! scope="col" | Speed ([[Tile|Tiles]] per [[game-second]])*
! scope="col" | Max. density ([[Items]] per [[Tile|tile]])*
! scope="col" | Required [[Research|technologies]]
|-
| {{imagelink|express-transport-belt|Express transport belt}} || 40.0 || 5.625 || 7.111 || [[Logistics 3]]
|}
 *See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

==Production Layouts==



{| class="wikitable"
|-
! scope="col" | Design
! scope="col" | Input: ([[Items]] per [[game-second]])
|- style="vertical-align:top;"
|rowspan="3" | [[File:Express_Transport_belt_layout1.jpg|top|400px]]
|{{icon|iron plate|21.5}} {{icon|Lubricant|2}}
|-
! scope="col"|Output: ([[Items]] per [[game-second]])
|- style="vertical-align:top;"
|{{icon|express transport belt|1}}
|}

== History ==

{{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.7.1|
* [[Express transport belt]] now takes 15 [[Iron gear wheel]]s to craft. }}

{{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 network]]

{{LogisticsNav}}

[[Category:Items]]

Fast transport belt

2016-12-21T22:45:07Z

Ssilk:

{{Languages}}

{{:Fast transport belt/infobox}}

The '''Fast transport belt''' is a faster variant of the [[Basic transport belt]]. It's available when [[Logistics 2]] has been [[Research|researched]]. Its behaviour is exactly the same as the [[Basic transport belt]] at double speed. 
See '''[[Belt transport system]]''' for more general information about transport belts. 

==Properties==

{| class="wikitable"
|-
! scope="col" | Type
! scope="col" | Max. throughput ([[Items]] per [[game-second]])*
! scope="col" | Speed ([[Tile|Tiles]] per [[game-second]])*
! scope="col" | Max. density ([[Items]] per [[Tile|tile]])*
! scope="col" | Required [[Research|technologies]]
|-
| {{imagelink|fast-transport-belt|Fast transport belt}} || 26.66 || 3.75 || 7.111 || [[Logistics 2]]
|}

*See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

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

[[File:Fast_Transport_belt_layout1.jpg|right|top|thumb|300px|Input:{{icon|iron plate|11.5}} / per game second. Output: {{icon|fast transport belt|1}} / per game second.]]

== History ==

{{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.7.1|
* [[Express transport belt]] now takes 15 [[Iron gear wheel]]s to craft. }}

{{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 network]]

{{LogisticsNav}}

[[Category:Items]]

Transport belts/Physics

2016-12-21T22:40:39Z

Ssilk:

{{Languages}}
{{sublinks}}

In Factorio, every item on screen is a real object in memory and follows the rules of the Game engine. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the simulation doesn't simulate every inhabitant of the city.

The reason for that is CPU-performance. Real-time game-physics for up to tens of thousands of objects at the same time is not typical for a simulation game. The Factorio Game engine creates an exact and reproducible simulation of the Factorio world, so exact that it can be used to measure some astonishing behavior of belts.

== What to measure ==
Some stats can be measured for belts:

* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So, 10 items laying in a single row on a belt non moving take the length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note that internally it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjunction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7.11 (32/9*2) on a tile of belt (2 lanes). Which means in practical terms that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): (1/32 tiles/tick) / (9/32 items/tile) = 0.111111111 items per tick or 6.666666667 items per second for one lane. For two lanes it is then 13.33 items/second.

== How to calculate these numbers yourself ==

=== Introduction ===
Belts have two ''lanes'': The left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item that is put on a belt (on a lane) takes 9 slots of space. This shows the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). 32/9 items (3.55 items) can fit on one lane of one belt. Essentially, up to 8 items can fit on one belt at any tick.
<pre>
Step by step movement of an item on a belt-lane. <---*---> represents an item, and the slots it consumes.

|==============================| <----- 32 slots
1 <---*---><---*---><---*---><---* 4 items
2 ><---*---><---*---><---*---><--- 3 items
3 -><---*---><---*---><---*---><-- 3 items
4 --><---*---><---*---><---*---><- 3 items
5 ---><---*---><---*---><---*--->< 3 items
6 *---><---*---><---*---><---*---> 4 items
7 -*---><---*---><---*---><---*--- 4 items
8 --*---><---*---><---*---><---*-- 4 items
9 ---*---><---*---><---*---><---*- 4 items
</pre>

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot.

=== Curves ===
The inner lane has 13.5 slots, compared to the outer 37 slots. In the end, 6 or 7 items can be in a curving belt at once.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

=== The faster belts ===
To obtain higher speeds on higher tier belts, the quantity of slots that each item moves per tick is multiplied. For [[Fast transport belt]]s two slots, for [[Express transport belt]]s 3 slots. That explains why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

=== Good to know, but practically useless ===

The least common multiple of 9 and 32 is 288. After 9 tiles, the slots are repeating their positions. If you place some inserters every 9 tiles and move them in exact sync (via circuit network) you can fill a belt without the trick of using a [[splitter]] or underground-belt.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes (Version 13.3 and above).

{| class="wikitable"
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | density (two lanes) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.556
|align="center" |7.111
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.556
|align="center" |7.111
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.556
|align="center" |7.111
|align="center" |40.00
|align="center" |2400.00
|}

We assume here that the density of items is always equal and maximum compressed (see above), so the transported amount should reflect the speed.

For measured results see '''[[Transport_belt_experiments|Transport belt experiments]]'''.

== History ==
'''This is outdated and should be outsourced from this article but not deleted, because it is an interesting fact.'''
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Kept for historical purposes, expand to view
<div class="mw-collapsible-content">

; Theory

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

; Measured Results for v0.11 or Older

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|This is NOT double as fast as basic! it's only 1.65 times faster
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|About 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

; Comments to the results

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

</div></div>

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

Transport belt

2016-12-21T22:37:15Z

Ssilk:

{{Languages}}
{{:Transport belt/infobox}}
The '''Basic Transport Belt''' is the easiest and cheapest method of automatic item transportation. It is available from the beginning of the game, without any [[research]]. See '''[[Belt transport system]]''' for more general information about transport belts.

==Properties==

{| class="wikitable"
|-
! scope="col" | Type
! scope="col" | Max. throughput ([[Items]] per [[game-second]])*
! scope="col" | Speed ([[Tile|Tiles]] per [[game-second]])*
! scope="col" | Max. density ([[Items]] per [[Tile|tile]])*
! scope="col" | Required [[Research|technologies]]
|-
| {{imagelink|basic-transport-belt|Basic transport belt}} || 13.33 || 1.875 || 7.111 || none
|}

 *See '''[[Transport_belts/Physics|Physics of Transport Belts]]''' for more detailed information.

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

Stepping on a transport belt will convey the [[player]] in the direction of the transport belt, at a somewhat slow speed. The player can fight the movement, or run with it to speed up. This can be used for transportation over short distances faster than running.

==Production Layouts==
[[Iron gear wheel]]s take the same amount of time to manufacture as transport belts, so one gear [[Assembling machine 1|assembler]] can supply one belt assembler at full capacity, provided they are the same tier. An example is below.

{| class="wikitable"
|-
! scope="col" | Design
! scope="col" | Input: ([[Items]] per [[game-second]])
|- style="vertical-align:top;"
|rowspan="3" | [[File:Transport_belt_layout1.jpg|top|400px]]
|
{{icon|iron plate|3}}
|-
! scope="col"|Output: ([[Items]] per [[game-second]])
|- style="vertical-align:top;"
|
{{icon|transport belt|2}}
|}

== History ==

{{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.7.1|
* [[Express transport belt]] now takes 15 [[Iron gear wheel]]s to craft. }}

{{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}}

[[Category:Items]]
{{C|Transport network}}

Worker robot speed (research)

2016-12-13T20:16:35Z

Ssilk:

{{Languages}}
{{:Worker robot speed (research)/infobox}}

The '''Worker robot speed''' bonus applies to [[logistic robot]]s and [[construction robot]]s.
The basic speed of logistic robots is 0.05 tiles/tick (3 tiles per second) and for construction robots 0.06 tiles/tick (3.6 tiles per second).

{| class="wikitable"
! Technology !! Cost !! Effects !! Cumulative effect[1] !! Relative effect[2]
|-
| {{icontech|worker-robots-speed-research|1|worker robot speed}} Worker robot speed 1 || {{icon|time|30}} {{icon|science pack 1|1}} {{icon|science pack 2|1}} {{icon|science pack 3|1}} <big>X 50</big> || 35% || 35% || 35%
|-
| {{icontech|worker-robots-speed-research|2|worker robot speed}} Worker robot speed 2 || {{icon|time|30}} {{icon|science pack 1|1}} {{icon|science pack 2|1}} {{icon|science pack 3|1}} <big>X 100</big> || 40% || 75% || 29.6%
|-
| {{icontech|worker-robots-speed-research|3|worker robot speed}} Worker robot speed 3 || {{icon|time|60}} {{icon|science pack 1|1}} {{icon|science pack 2|1}} {{icon|science pack 3|1}} {{icon|alien science pack|1}} <big>X 150</big> || 45% || 120% || 25.7%
|-
| {{icontech|worker-robots-speed-research|4|worker robot speed}} Worker robot speed 4 || {{icon|time|60}} {{icon|science pack 1|1}} {{icon|science pack 2|1}} {{icon|science pack 3|1}} {{icon|alien science pack|1}} <big>X 250</big> || 55% || 175% || 25%
|-
| {{icontech|worker-robots-speed-research|5|worker robot speed}} Worker robot speed 5 || {{icon|time|60}} {{icon|science pack 1|1}} {{icon|science pack 2|1}} {{icon|science pack 3|1}} {{icon|alien science pack|1}} <big>X 500</big> || 65% || 240% || 23.6%
|-
|}

[1] percent bonus compared to bot without speed research

[2] percent bonus compared to bot with speed research of previous tier

== See also ==
* [[Research]]
* [[Research#Technologies|Technologies]]

[[Category:Technology]]
{{TechNav}}

Transport belts/Physics

2016-12-09T14:45:39Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): (1/32 tiles/tick) / (9/32 items/tile) = 0,111111111 items per tick or 6,666666667 items per second for one lane. For two lanes it is then 13,333333333 items/second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on one lane of a belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt (two lanes)!

Step by step movement of an item on a belt-lane.

|==============================| <----- 32 slots
1 <---*---><---*---><---*---><---* 4 items
2 ><---*---><---*---><---*---><--- 3 items
3 -><---*---><---*---><---*---><-- 3 items
4 --><---*---><---*---><---*---><- 3 items
5 ---><---*---><---*---><---*--->< 3 items
6 *---><---*---><---*---><---*---> 4 items
7 -*---><---*---><---*---><---*--- 4 items
8 --*---><---*---><---*---><---*-- 4 items
9 ---*---><---*---><---*---><---*- 4 items

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast transport belt]]s two slots, for [[Express transport belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

==== Good to know, but practically useless ====

The least common multiple of 9 and 32 is 288. That is 9 * 32, which means: After 9 tiles the slots are repeating their positions. Which means: if you place some inserters every 9 tiles and move them in exact sync (via circuit network) you can fill a belt without the trick of using a splitter or undergroud-belt.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes (Version 13.3 and above).

{| class="wikitable"
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | density (two lanes) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.556
|align="center" |7.111
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.556
|align="center" |7.111
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.556
|align="center" |7.111
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal and maximum compressed (see above), so the transported amount should reflect the speed.

= History =
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

== Theory ==

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

== Measured Results for v0.11 or Older ==

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Map generator

2016-12-05T17:32:12Z

Ssilk:

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Charting (Make Invisible Chunks Visible on Map)===

As long as a chunk is invisible the part of the players map keeps black. This changes, when a chunk is '''[[Radar#Charting|charted]]''', which means when it is "touched" by radar. Either the players internal radar, which is always available, or the '''[[Radar]]''' entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 240 [[game-second|game-minutes]] (=4 hours) by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Radar

2016-12-05T17:32:10Z

Ssilk:

{{Languages}}
{{:Radar/infobox}}
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. Radar has a high [[Electric network|power]] demand (300kW) so a radar indirectly contributes to [[Pollution]] when powered by [[Boiler]]s and [[Steam engine|steam engines]]. The radar will be attacked by enemies that come within very close range, like turrets, but will not attract biters from long range like polluting structures do.
The radar will show enemy lifeforms and structures, as well as trains, cars, and other players in the scanned area.

== Nearby Pulse Scanning ==

Radar continuously charts a charting area of 100x100 [[tile]]s, AKA a 7x7 [[Chunk]] (224x224 [[Tile]]s) area, 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 ==

Radar charts one distant [[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.
* 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 29x29 chunks around the Radar, excluding the nearby 7x7 chunk.
** With a total number of 797 chunks (29x29 - 7x7), 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, don't be taken unawares.

== Coverage ==

Something easily missed is that Radars give a line of sight around them, this is good for keeping tabs on distant bases if they get attacked and to see how big the attack is. The radar's LOS updates once every second, so keeping one or two around your base could prove to be an early warning system. Keep in mind the update rate for the LOS of the radar is not the same as the rate at which the radar will reveal unexplored terrain, which updates once every ~30 seconds. You can see the LOS given in the image below, taken from map view.

[[File:Radar_Coverage.jpg|upright=3]]

== 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 [[Lua/Force|force]] (every force has it's 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. See below. You can see the entities moving, you can see enemies walking. Every entity is represented by one ore more pixels. Not every entity is drawn. What's drawn and in which color etc. is configurable and there are also mods, that changes this.

Charting of very much chunks that change each tick might have an impact on game-performance.

==== 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 dark-grey.

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").

Once a new scan has been triggered the chunk keeps again charted for 10 seconds.

===== Charting of Vehicles =====

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

==== The Map ====
That is just a bitmap (graphics). The map for each force is stored with a save. Uncharted areas (never charted before) keep black and are not saved.

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

The [[World_generator#Generating_new_Chunks|World Generator]] creates a "border" of invisble chunks around each chunk, that becomes active at some time. Active chunks are in general those, that become charted or those, that are active, because the pollution spreads on them. Which means for the normal case: Once you chart a formerly invisible chunk then automatically one to eight new chunks are generated.

==== Charting-Area vs. Charted Chunks ====
For example: A [[radar]] actively charts an ''charting-area'' of 100x100 tiles. This means: Each chunk, that is '''touched''' by the charting-area is charted. Which means, that you nearly always chart a bigger area than defined in charting-area.

==== Visible Area vs. Charted ====
Like in reality there is a difference between what a player can "see" and what of that is charted. A player can see a much bigger area (use for example this [[console]]-command: "/c game.player.zoom=0.1"), than what is charted. This depends in normal game for example on your screen-resolution. The charting has nothing to do with that, it depends only on charting area.

==== Charting entities ====
The default game has two sources of triggering charting: The [[player]] and [[radar]]s.

== History ==

{{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 ==
* [[Electric network]]
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3925 Self sufficient radar outpost].
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5793 Self defending independent radar layout].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=6008&p=53660#p53660 Forum Radar Build Thread].

{{CombatNav}}

[[Category: Items]] [[Category: Electric network]] [[Category: Combat]]

Radar

2016-12-05T16:48:55Z

Ssilk:

{{Languages}}
{{:Radar/infobox}}
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. Radar has a high [[Electric network|power]] demand (300kW) so a radar indirectly contributes to [[Pollution]] when powered by [[Boiler]]s and [[Steam engine|steam engines]]. The radar will be attacked by enemies that come within very close range, like turrets, but will not attract biters from long range like polluting structures do.
The radar will show enemy lifeforms and structures, as well as trains, cars, and other players in the scanned area.

== Nearby Pulse Scanning ==

Radar continuously charts a charting area of 100x100 [[tile]]s, AKA a 7x7 [[Chunk]] (224x224 [[Tile]]s) area, 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 ==

Radar charts one distant [[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.
* 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 29x29 chunks around the Radar, excluding the nearby 7x7 chunk.
** With a total number of 797 chunks (29x29 - 7x7), 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, don't be taken unawares.

== Coverage ==

Something easily missed is that Radars give a line of sight around them, this is good for keeping tabs on distant bases if they get attacked and to see how big the attack is. The radar's LOS updates once every second, so keeping one or two around your base could prove to be an early warning system. Keep in mind the update rate for the LOS of the radar is not the same as the rate at which the radar will reveal unexplored terrain, which updates once every ~30 seconds. You can see the LOS given in the image below, taken from map view.

[[File:Radar_Coverage.jpg|upright=3]]

== 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 [[Lua/Force|force]] (every force has it's 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. See below. You can see the entities moving, you can see enemies walking. Every entity is represented by one ore more pixels. Not every entity is drawn. What's drawn and in which color etc. is configurable and there are also mods, that changes this.

Charting of very much chunks that change each tick might have an impact on game-performance.

==== 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 dark-grey.

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").

Once a new scan has been triggered the chunk keeps again charted for 10 seconds.

===== Charting of Vehicles =====

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

==== The Map ====
That is just a bitmap (graphics). The map for each force is stored with a save. Uncharted areas (never charted before) keep black and are not saved.

==== Charting-Area vs. Charted Chunks ====
For example: A [[radar]] actively charts an ''charting-area'' of 100x100 tiles. This means: Each chunk, that is '''touched''' by the charting-area is charted. Which means, that you nearly always chart a bigger area than defined in charting-area.

==== Visible Area vs. Charted ====
Like in reality there is a difference between what a player can "see" and what of that is charted. A player can see a much bigger area (use for example this [[console]]-command: "/c game.player.zoom=0.1"), than what is charted. This depends in normal game for example on your screen-resolution. The charting has nothing to do with that, it depends only on charting area.

==== Charting entities ====
The default game has two sources of triggering charting: The [[player]] and [[radar]]s.

== History ==

{{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 ==
* [[Electric network]]
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3925 Self sufficient radar outpost].
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5793 Self defending independent radar layout].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=6008&p=53660#p53660 Forum Radar Build Thread].

{{CombatNav}}

[[Category: Items]] [[Category: Electric network]] [[Category: Combat]]

Tutorial:Transport use cases

2016-12-04T14:03:42Z

Ssilk:

{{sublinks}}
This page compares the three main [[Transport]] methods: [[Belt transport system]] (conveyor belts), [[Railway]] (trains) and [[Logistic robot|Logistic robots]]. Note, that there are two more useful methods to transport stuff: The characters [[Inventory]] and the [[Vehicles/Car]]. (Especially the car has an extremely high capacity and can be used instead of trains - of course you need to drive everything yourself, see the chapter about the car).

The best choice depends on the context in which they are used. For example on the amount of resources you need to transport, or how far away they are.

== Comparison of Belts, Trains and Logistic Robots ==

{| class="wikitable"
|-
! width=10% |
! width=30% | Belts
! width=30% | Trains
! width=30% | Logistic Robots
|-
| Throughput
| Constant, low for one belt, precisely calculable, limited
| Extremely high, fast, not easily calculable but constant, nearly unlimited if enough space,
| High in small areas, not calculable/chaotic, unlimited if enough bots, cannot be optimized, terrible over long distances and bulk goods
|-
| Space required
| Small for simple products, large for complicated product chains
| Large due to train stations and bends. There is a difference in using [https://forums.factorio.com/viewtopic.php?f=5&t=35806 Rollon-Rolloff-Stations (lot of space) or Terminus (much smaller)].
| Small for complex products.
|-
| Optimization
| Highly optimizable. Source of never ending fun.
| Seldom really needed - better rebuild or built more tracks. For larger networks you can get some trouble with deadlocks/gridlocks, if not optimized, using chain signals. Optimize train stations: connect either with belts (complex) or with logistic bots (recommended).
| Optimize placing of roboports (for charging) and used number of ports vs. number of bots in the air.
|-
| Parallelization
| High. Two parallel belts have the doubled throughput as one. Cost is also only double. On the other hand: Afford to build that doubles also.
| Extreme. Two parallel tracks can transport 5-10 times more trains than one, cause if a track is blocked the trains can choose the other free track and so they don't need to stop. The afford to build two tracks in parallel is lower than doubled.
| Not so good. Doubling the amount of bots from one to two surely doubles the throughput, but doubling robots from 500 to 1000 can result in complete chaos.
|-
| Initial costs
| Very small as long as conveyor belts are short. Still good with parallel belts. Larger when making express transport belts. Expensive with express; which should be used for special cases only.
| Considerable amount of material is needed for initial locomotive. Small costs (when compared to the increase of transport) for making rails.
| Roboports and especially bots require a lot of resources to make. Logistic bot upgrades are very expensive, but needed and must be calculated into the total costs. Maintaining costs a lot of time.
|-
| Use of energy
| Gratis. Free. Always an object of discussion. ;)
| Low. The usage of fuel is currently very affordable.
| High. The roboports need a lot of energy and the bots take even more energy, as more are in the air. This can be a big problem, but is normally not an issue.
|-
| Items in transit vs. duration of transport
| Bad. 100 tiles of belts stores about 700 items if fully loaded, but takes with basic belts 56 seconds for transport. With express belt, this is only 3 times faster.
| Very good. Lot of items transported in very short time.
| Chaotic. When jammed it can happen, that the most important items are unreachable in the air.
|-
| Maintenance costs
| None
| Some fuel needed
| Considerable amount of electricity needed
|-
| Pollution
| None
| Some
| None, indirectly caused by use of electricity.
|-
| Best used for
| High throughput, bulk-goods (ores, some intermediates), small to medium distance. Examples include raw materials and simple products.
| High throughput, long distance. Examples include transporting ores or plates from resource fields to main factory area.
| Extremely high throughput over very short distances (< 50 tiles), low to medium throughput over medium distance (50-500), catastrophic over long distance. Best used in main factory area for complex products like modules and advanced circuits. Also best used for products needed in smaller quantities like placeable structures and ammunition. Unbeatable for train station (loading/unloading chests).
|-
| Most annoying problems
| Left/right lane problems (part of the game), splitting off the right amount of items.
| Deadlock situations (in complicated crossings), complex train-station and signal setup.
| Blocking of roboports by waiting for charging, "stupid" behavior that far away bots are used, instead of near and vice versa, Robots that take a "shortage" and cross a native village.
|}

== Experts ==

=== Belts ===

* practical up to distances of 500 tiles (to compare: a radar station watches up to 200 tiles (100 tiles "radius")).
* connect small resource-fields to the factory area, as the capacity of a belt is limited to about 700 items per minute in the best case, when using basic belts. With fast or express belt, this is higher (up to 1750) but the price is gigantic. Using multiple parallel belts is costly, but with basic belts still affordable over long distances.
* Conveyor belts are best for working within an automated facility for '''bulk goods'''. Transporting ore, plates, circuit boards, etc over short or medium distances.
* they store over a long distance a not to be underestimated number of items (about 12 per tile, with two lanes, so you can calculate over 500 tiles with 6000 items!). This storage is out of reach and could be counted as wasted, until it is transported.

Note: the length of 500 tiles is just a "rule of thumb", and comes from these facts:
* It takes nearly 5 minutes (4.44) for an item to run from one end to the other ([[Basic belt]]).
* A belt with 500 tiles stores about 3571 items (about a chest of resources).
* The fact, that about after this length it makes sense to use train.

The advantages of belts are:
* coming to transport-performance, belts deliver very constantly
* easy calculations possible (e. g. is belt able to transport output of all mines)
* basic belts are cheap compared to tracks and it is built faster
* you see how much items are on the belt
* you can use the belt as an open storage: you can store about 72 items in a length of 10 belts, when using both lanes (but for long belts this is a big disadvantage!)
*
Disadvantages:
* limited transport capacity, cause limited throughput.
* slow. This is a problem with verily long belts because it takes a while to fill the belt. The items on the belt cannot be used. A belt with length of 100 holds 714 items for 56 seconds. With trains this is much lower (10 seconds) and as long as they are not loaded into a wagon, they still can be used.
* items on the belts are "lost items" until they are transported.

Belts have the best short-distance throughput for continuous, direct-to-factory transportation. '''This is especially true, if you use basic belts in parallel, cause this combination has an incredible high throughput at low costs.

=== Trains ===

* Trains should be used to get items from big and distant resource fields. Nothing can compare with it, especially, when thinking about speed. The planning is difficult and the building itself is currently tedious. (tip: use the train to build the rails, this is much faster: sit in the train and build the next rail before you, hold mouse, start driving slowly. You can use it also to build the power poles like so).
* Trains are for linking separate factory assemblies together over long distances. This additionally lets you 'take a ride' out to outposts that require attention.

Smelt ore locally and ship the plates via train, you can double your wagon capacity and route directly to a storage yard or factory. See also [[Transport/Compress_by_Pre-production]].

Some interesting thread: [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6799&p=53609#53609 Long distance transport].

=== Logistic robots ===

* Logistic robots should be used in a limited area with dense building placement In most cases this is the main factory area. With some updates the logistic bots can handle enormous amounts of items.
* Bots are terrible at long distances and bulk goods: It's not a good idea use bots for ore-transport or from/to furnaces. It is possible to use them for this task, but don't await, that this works perfect; there are some difficulties cause they do not optimize their work. Some players take that problems as challenge.
* They do a perfect job on bulk-goods, if they can charge between their jobs, which is the case on train-stations: Train comes in, train is unloaded, bots transports to the target chests, bots charge. Next rain comes in.
* Bots do a perfect job, if you use them for random transport of expensive products; transport intermediate products to where they're needed within the local network, especially if it's completely impractical to route a belt for the job.

Bots, while great at moving sparse items with slow production speeds, are a very costly thing to integrate with high-volume affairs like mining/smelting because they need frequent breaks to recharge.

The exception is the incredible benefit they offer to train stations because of the space/logistical challenge of routing and load-balancing belts around the train tracks, especially since it isn't necessarily 'constant flow', offering them time to recharge.

== Seeing from throughput side ==

A [[Basic transport belt]] cannot transport much more than 700 item/minute and an [[Express transport belt]] (the fastest) not more than 1750 (see above). Now compare that with a locomotive: a [[Cargo wagon]] can deliver 2000 items (ores) '''per wagon'''! And if you smelt the resources at your outpost and transport intermediate plates (copper, iron) you can transport 4000 per wagon. So when speaking from throughput, you need to swap to train or make multiple parallel belts.

This picture might change when you developed [[Logistic robot]]s. But that is not true! They can't be beaten for relatively small areas, especially with their researched bonuses, and they have some kind of intelligence; they try to deliver all requests as equally as possible.

But bots are terrible at long distances and bulk goods. Here are some calculations, which explain the problem (all calculations are assumed with full upgrade for the logistic bots!):

Needed robots to transport 3000 items per minute over a distance of 50 tiles you need:
Robot speed: 3 tiles/sec (basic speed) * 1.4 (logistic speed bonus) = 4.2 tiles/sec
Needed time for one transport: 100 tiles / 4.2 tiles/sec = 24 secs
Need robots per minute: 24 secs / 60 secs = you need 0.4 bots to transport one item per minute over 50 tiles.
Because of Logistic robot cargo: 0.4 bots / 5 items per transport = 0.08 bots to transport one item per minute
Total: 3000 items * 0.08 bots/per item = 240 bots
240 is a high, but still very realistic number for a logistic network with 4-5 roboports.

Needed robots to transport 3000 items per minute over a distance of 500 tiles you need:
Needed time for one transport: 1000 tiles / 4.2 tiles/sec = 240 secs
Need robots per minute: 240 secs / 60 secs = you need 4 bots to transport one item per minute over 500 tiles.
Because of Logistic robot cargo: 4 bots / 5 items per transport = 0.8 bots to transport one item per minute
Total: 3000 items * 0.8 bots/per item = 2400 bots

2400 bots need a quite big amount of resources to produce, not accounted the needed research (for bots, speed/stacksize bonuses), number of roboports and the needed energy.

That leaves conveyors and trains.

Trains are faster than belts and offer better logistic control as you go between logistic networks.

Belts simply take forever, and you may wind up with a lot of asset tied up with simply being 'in transit'. You should see items sitting on a belt as "non-useable storage". Backed up belts can be a good thing for buffer space, but long belts are just inefficient, or better: You loose the control over the other end, due to the long gap; the resources on the other side could be long depleted, but you see it only five minutes later.

=== Or in other words ===
The afford, to squeeze out the last 20% of belt-performance rises depending on distance and total amount and at some point the train will win. But in your central factory area the bots will never be beaten. On the other hand: in small areas, and for simple throughput of one type of item (furnace iron ore to iron-plates for example) we can place some belts in parallel, which is cheap and efficient (uses no energy) and when using parallel belts we reach also enormous throughput. For later game, the [[Fast transport belt]] is a good compromise between cost and efficiency, and the [[Express transport belt]]s should be use only for short sections.

=== Or in more other words ===
The amount of robots you need is directly dependent on the density you built. The central part of your factory should be dense, cause not only throughput is important here, but also speed: How fast can an item be produced in total (including the transportation time).

== See also ==

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3948 Discussion about using conveyor belts vs. trains]. There are some interesting tips in this thread.
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5478 More trains vs. longer trains]
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5715 Deciding which items to re-make and which to keep on belts?]
{{Languages}}

Infobox:Cargo wagon

2016-12-04T13:25:24Z

Ssilk:

{{Infobox
| category = Machinery
| category-name = Machine
|health =600
|stack-size =5
|storage-size =40
|recipe =time, 0.5 + iron plate, 20 + steel plate, 20 + iron gear wheel, 10
|total-raw =time, 5.5 + iron plate, 40 + steel plate, 20
|required-technologies =Automated rail transportation
|producers =Manual + Assembling machine 2 + Assembling machine 3
}}<noinclude>[[Category:Infobox page]]</noinclude>

Cargo wagon

2016-12-04T13:23:29Z

Ssilk:

{{Languages}}
{{:Cargo wagon/infobox}}

The '''Cargo wagon''' is used in conjunction with [[Diesel locomotive]]s to form [[Train]]s for the [[Railway network]].

A wagon is used to transport items and can be filled and emptied like a chest, but with many more inserters at the same time. Up to 12 inserters per wagon are possible (from both sides).
The [[Inserter item stack size]] is important to fill the wagon fast!

In manual-mode cargo wagons can only be filled or emptied when they are not moving and horizontally or vertically orientated. In automated-mode it is the same, but additionally they can only filled/empty, when stopped on a train-stop (not on a signal). A spot where inserters are prepositioned to transfer cargo for wagons is called a [[Railway_network/Train_station|train station]].

== Stack limitation ==

Wagons have a [[Storage/Stack#Stack limitation|stack limitation]] option the same way chests do, which is useful if you need to limit the number of transported items for some reason.

== Stack filter ==

Each stack in the cargo wagon can be filtered. This works in the same way as the quick bar (toolbelt); the default key to define or remove the filter is the middle mouse button.

This can be used to transport different items in one wagon. For example, you could transport both empty and full oil barrels in one wagon; at the train stations, the barrels would be handled using smart inserters for each kind of barrel. This is discussed in the forum thread [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=68288&p=53467&hilit=Filter#p53467 Tired of babysitting expansions? Auto-supply w/ trains!].

== Compressing items ==

A cargo wagon can be filled with 2000 items of ores ([[Copper ore|copper]], [[Iron ore|iron]], [[Coal|coal]]...) or 4000 items of processed plates ([[Copper plate|copper plates]], [[Iron plate|iron plates]], [[Steel bar|steel]]). This makes preprocessing your ores into plates (near the mines) a useful strategy, before you transport it to your factory. See [[Transport/Compress by Pre-production]] for a more detailed discussion of this concept.

== Use as big chest ==

It is possible to use the cargo wagon as a "big chest": Place rails, put an unmoving wagon on it and inserters around. The advantages of this construction are:
* Cargo can be transferred with many more inserters than with a chest, bypassing the limitations of the [[Inserter item stack size bonus|inserter stack size bonus]].
* Items are transported instantly over the length of the wagon. Correctly configured, this is faster than a transport belt.

For examples of this, see these forum threads:
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3537 Solar panel factory]
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=7568 Cargo wagon sourced RGB circuits production facility]
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=8551 Mass production with ZERO belts and robots]

==See also==
* [[Diesel locomotive]]
* [[Railway network]]

{{LogisticsNav}}

{{C|Railway network}}
{{C|Vehicle}}

Cargo wagon

2016-12-04T13:20:29Z

Ssilk:

{{Languages}}
{{:Cargo wagon/infobox}}

The '''Cargo wagon''' is used in conjunction with [[Diesel locomotive]]s to form [[Train]]s for the [[Railway network]].

A wagon is used to transport items and can be filled and emptied like a chest, but with many more inserters at the same time. Up to 12 inserters per wagon are possible (from both sides).
The [[Inserter item stack size]] is important to fill the wagon fast!

Cargo wagons can only be filled or emptied when they are not moving. In automated-mode they can only filled/empty, when stopped on a train-stop (not on a signal). A spot where inserters are prepositioned to transfer cargo for wagons is called a [[Railway_network/Train_station|train station]].

== Stack limitation ==

Wagons have a [[Storage/Stack#Stack limitation|stack limitation]] option the same way chests do, which is useful if you need to limit the number of transported items for some reason.

== Stack filter ==

Each stack in the cargo wagon can be filtered. This works in the same way as the quick bar (toolbelt); the default key to define or remove the filter is the middle mouse button.

This can be used to transport different items in one wagon. For example, you could transport both empty and full oil barrels in one wagon; at the train stations, the barrels would be handled using smart inserters for each kind of barrel. This is discussed in the forum thread [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=68288&p=53467&hilit=Filter#p53467 Tired of babysitting expansions? Auto-supply w/ trains!].

== Compressing items ==

A cargo wagon can be filled with 2000 items of ores ([[Copper ore|copper]], [[Iron ore|iron]], [[Coal|coal]]...) or 4000 items of processed plates ([[Copper plate|copper plates]], [[Iron plate|iron plates]], [[Steel bar|steel]]). This makes preprocessing your ores into plates (near the mines) a useful strategy, before you transport it to your factory. See [[Transport/Compress by Pre-production]] for a more detailed discussion of this concept.

== Use as big chest ==

It is possible to use the cargo wagon as a "big chest": Place rails, put an unmoving wagon on it and inserters around. The advantages of this construction are:
* Cargo can be transferred with many more inserters than with a chest, bypassing the limitations of the [[Inserter item stack size bonus|inserter stack size bonus]].
* Items are transported instantly over the length of the wagon. Correctly configured, this is faster than a transport belt.

For examples of this, see these forum threads:
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3537 Solar panel factory]
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=7568 Cargo wagon sourced RGB circuits production facility]
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=8551 Mass production with ZERO belts and robots]

==See also==
* [[Diesel locomotive]]
* [[Railway network]]

{{LogisticsNav}}

{{C|Railway network}}
{{C|Vehicle}}

Radar

2016-12-03T23:00:17Z

Ssilk:

{{Languages}}
{{:Radar/infobox}}
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. Radar has a high [[Electric network|power]] demand (300kW) so a radar indirectly contributes to [[Pollution]] when powered by [[Boiler]]s and [[Steam engine|steam engines]]. The radar will be attacked by enemies that come within very close range, like turrets, but will not attract biters from long range like polluting structures do.
The radar will show enemy lifeforms and structures, as well as trains, cars, and other players in the scanned area.

== Nearby Pulse Scanning ==

Radar continuously charts a charting area of 100x100 [[tile]]s. Which mean, that you most times chart 7x7 [[Chunk]] (224x224 [[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 ==

Radar charts one distant [[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.
* 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 29x29 chunks around the Radar, excluding the nearby 7x7 chunk.
** With a total number of 797 chunks (29x29 - 7x7), 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, don't be taken unawares.

== Coverage ==

Something easily missed is that Radars give a line of sight around them, this is good for keeping tabs on distant bases if they get attacked and to see how big the attack is. The radar's LOS updates once every second, so keeping one or two around your base could prove to be an early warning system. Keep in mind the update rate for the LOS of the radar is not the same as the rate at which the radar will reveal unexplored terrain, which updates once every ~30 seconds. You can see the LOS given in the image below, taken from map view.

[[File:Radar_Coverage.jpg|upright=3]]

== 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 [[Lua/Force|force]] (every force has it's 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. See below. You can see the entities moving, you can see enemies walking. Every entity is represented by one ore more pixels. Not every entity is drawn. What's drawn and in which color etc. is configurable and there are also mods, that changes this.

==== 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 that chunk is highlighted and dims within 10 seconds to dark-grey.

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").

Once a new scan has been triggered the chunk keeps again charted for 10 seconds.

While charting one chunk is quite fast, charting of very much chunks, that changes each tick can become a problem in big maps. Because of that, it is recommended to use not more radars than really needed.

==== The Map ====
That is just a bitmap (graphics). The map for each force is stored with a save. Uncharted areas (never charted before) keep black and are not saved.

==== Charting-Area vs. Charted Chunks ====
For example: A [[radar]] actively charts an ''charting-area'' of 100x100 tiles. This means: Each chunk, that is '''touched''' by the charting-area is charted. Which means, that you nearly always chart a bigger area than defined in charting-area.

==== Visible Area vs. Charted ====
Like in reality there is a difference between what a player can "see" and what of that is charted. A player can see a much bigger area (use for example this [[console]]-command: "/c game.player.zoom=0.1"), than what is charted. This depends in normal game for example on your screen-resolution. The charting has nothing to do with that, it depends only on charting area.

==== Charting entities ====
The default game has two sources of triggering charting: The [[player]] and [[radar]]s.

== History ==

{{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 ==
* [[Electric network]]
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3925 Self sufficient radar outpost].
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5793 Self defending independent radar layout].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=6008&p=53660#p53660 Forum Radar Build Thread].

{{CombatNav}}

[[Category: Items]] [[Category: Electric network]] [[Category: Combat]]

Player

2016-11-08T16:07:46Z

Ssilk:

{{Languages}}

[[File:Player icon.png|right]]

Factorio is played from the angled top down perspective of ''player''.

The ''physical representation'' of the player is the ''[[character]]'', who is always at the center of view. In multiplayer, players characters will appear in different colors.

== Distinction between Player and Character ==

Technically the player is only the "player-view". It is a ''virtually, sweeping "it"''. The player stands unlike to the [[character]], the little person, that runs around on ground! The character is part of the player, but the player is not the character.

You can for example play in good-mode (play in sandbox-mode). In that mode you don't have a character, only a player-view.
Only a character can have slots for your weapons, which means: You cannot fire weapons, when in good-mode.

== World Interaction ==
The player has five primary ways of interacting with the world:

# Crafting [[Item|items]] and [[Items#Placeable_items|entities]] personally from resources using the craft menu (Default open key: E)
# Placing entities by selecting them from the inventory or toolbar and placing them on a [[tile]] (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 [[Item#Resources|resources]] from a tile (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)

''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.

== Equipment ==

Equipment are items used to speed up entity/resource collection, kill [[enemies]], protect the player's health, etc. All equipment except for weapons and capsules have durability, and will break after enough uses. Examples of equipment and the equipment inventory are discussed below.

[[File:EquipSlots.jpg|thumb|right|1: The tool slot for pickaxes. 2: The armor slot. 3: The weapon slots. 4: The ammo slots.]]

=== Tools ===
Removing or harvesting machines, entities, or resources from the world requires effort and this is implemented by way of a progress bar that needs to fill uninterrupted in order to complete and pick up the object. Starting without a pickaxe, it will take around two seconds to cut down a single tree. Since this is the sort of action required thousands of times over the course of a game, ''it is heavily recommended to craft an [[iron axe]] as the first action the player takes in the game''.

A full list of all tools in the game:

* [[Iron axe]]
* [[Steel axe]]
* [[Repair pack]]
* [[Basic electric discharge defense remote]]

=== Weapons ===
Eventually, whether in a peaceful game or not, one will need the capability to destroy the various [[Enemies]] that live in the world.

This capability mostly comes in the form of [[Turrets]] for base defense, but for the player there are two broad categories, more traditional weapons and capsules; discussed below. To fire the main equip-able weapons, the weapon must be in one of the weapon slots. (see above)

If all the preparation is done, fire the weapon with the target enemy key (Default: Spacebar) or the target cursor key (Default: C). Target enemy is a ''safe'' auto-aim that will snap to any enemy in range and begin firing at it for as long as the key is held down. A green target reticle will be shown below the enemy when in range, red when not.

Target cursor will fire your weapon in the direction of your cursor, which is mainly used to clear obstacles such as [[Tree]]s and rocks that block placing things. Bear in mind that damage is calculated as a combination of weapon, ammunition and technology together. Target cursor is capable of shooting anything with health, so be careful when near important buildings. In late game, player gunfire can nearly instantly destroy some buildings.

Each player starts with a simple [[Pistol]] and ten magazines of [[Firearm magazine|basic ammo]], which will fend off the first few biter attacks, but will quickly be insufficient against the growing alien forces.

A list of all traditional weapons in the game:

* [[Pistol]]
* [[Submachine gun]]
* [[Shotgun]]
* [[Combat shotgun]]
* [[Rocket launcher]]
* [[Flamethrower]]

=== Capsules ===
Capsules are consumable weapons systems, they are picked up from the inventory and thrown somewhere in the game world to spawn their effect at that position. Early in the game, these take the form of instant effect grenades that detonate upon reaching the location they were thrown to.

A list of all throw-able capsules in the game:

* [[Basic grenade]]
* [[Cluster grenade]]
* [[Poison capsule]]
* [[Slowdown capsule]]

=== Combat Robot Capsules ===
With the mid-game comes access to combat robot capsules, which are deployed the exact same way as previous capsules, however they deploy different forms of hovering robots, with various behaviors and types of attacks/movement. The amount of robots that can be out at one time is limited by the [[Follower robot count (research)|Robot follower count research]].

A list of all robot capsules in the game:

* [[Defender capsule]]
* [[Distractor capsule]]
* [[Destroyer capsule]]

=== Armor ===
Once the player has faced the first proper attack, they will quickly come to learn how much damage they can handle, not much at all. Equipping a decent set of armor is therefore a priority. There are two subcategories of armor in the game, however early in the game the player will only have access to simple basic armor.

A list of all armors in the game:

* [[Light armor]]
* [[Heavy armor]]
* [[Basic modular armor]]
* [[Power armor]]
* [[Power armor MK2]]

=== Armor Modules ===
Once the player has crafted any modular armor they gain access to various general purpose enhancements, which can be freely added or removed from any modular armor. While all of them are capable of fitting in even the [[Basic modular armor]] individually, their usefulness greatly depends on player choice; i.e. there are no specific best modules or best arrangement of modules.

A list of all armor modules in the game:

* [[Basic exoskeleton equipment]]
* [[Battery MK1]]
* [[Battery MK2]]
* [[Portable solar panel]]
* [[Portable fusion reactor]]
* [[Energy shield]]
* [[Energy shield MK2]]
* [[Night vision]]
* [[Personal laser defense]]
* [[Discharge defense]]

== 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}}

{{EquipNav}}

Player

2016-11-08T16:03:18Z

Ssilk:

{{Languages}}

[[File:Player icon.png|right]]

Factorio is played from the angled top down perspective of ''player''.

The ''physical representation'' of the player is the ''[[character]]'', who is always at the center of view. In multiplayer, players characters will appear in different colors.

== Distinction between Player and Character ==

The player is only the "player-view". It is a virtualy, sweeping "it". The player stands unlike to the [[character]], the little person, that runs around on ground! The character is part of the player, but the player is not the character.

You can for example play in good-mode (play in sandbox-mode). In that mode you don't have a character, only a player-view.
Only a character can have slots for your weapons, which means: You cannot fire weapons, when in good-mode.

== World Interaction ==
The player has five primary ways of interacting with the world:

# Crafting [[Item|items]] and [[Items#Placeable_items|entities]] personally from resources using the craft menu (Default open key: E)
# Placing entities by selecting them from the inventory or toolbar and placing them on a [[tile]] (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 [[Item#Resources|resources]] from a tile (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)

''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.

== Equipment ==

Equipment are items used to speed up entity/resource collection, kill [[enemies]], protect the player's health, etc. All equipment except for weapons and capsules have durability, and will break after enough uses. Examples of equipment and the equipment inventory are discussed below.

[[File:EquipSlots.jpg|thumb|right|1: The tool slot for pickaxes. 2: The armor slot. 3: The weapon slots. 4: The ammo slots.]]

=== Tools ===
Removing or harvesting machines, entities, or resources from the world requires effort and this is implemented by way of a progress bar that needs to fill uninterrupted in order to complete and pick up the object. Starting without a pickaxe, it will take around two seconds to cut down a single tree. Since this is the sort of action required thousands of times over the course of a game, ''it is heavily recommended to craft an [[iron axe]] as the first action the player takes in the game''.

A full list of all tools in the game:

* [[Iron axe]]
* [[Steel axe]]
* [[Repair pack]]
* [[Basic electric discharge defense remote]]

=== Weapons ===
Eventually, whether in a peaceful game or not, one will need the capability to destroy the various [[Enemies]] that live in the world.

This capability mostly comes in the form of [[Turrets]] for base defense, but for the player there are two broad categories, more traditional weapons and capsules; discussed below. To fire the main equip-able weapons, the weapon must be in one of the weapon slots. (see above)

If all the preparation is done, fire the weapon with the target enemy key (Default: Spacebar) or the target cursor key (Default: C). Target enemy is a ''safe'' auto-aim that will snap to any enemy in range and begin firing at it for as long as the key is held down. A green target reticle will be shown below the enemy when in range, red when not.

Target cursor will fire your weapon in the direction of your cursor, which is mainly used to clear obstacles such as [[Tree]]s and rocks that block placing things. Bear in mind that damage is calculated as a combination of weapon, ammunition and technology together. Target cursor is capable of shooting anything with health, so be careful when near important buildings. In late game, player gunfire can nearly instantly destroy some buildings.

Each player starts with a simple [[Pistol]] and ten magazines of [[Firearm magazine|basic ammo]], which will fend off the first few biter attacks, but will quickly be insufficient against the growing alien forces.

A list of all traditional weapons in the game:

* [[Pistol]]
* [[Submachine gun]]
* [[Shotgun]]
* [[Combat shotgun]]
* [[Rocket launcher]]
* [[Flamethrower]]

=== Capsules ===
Capsules are consumable weapons systems, they are picked up from the inventory and thrown somewhere in the game world to spawn their effect at that position. Early in the game, these take the form of instant effect grenades that detonate upon reaching the location they were thrown to.

A list of all throw-able capsules in the game:

* [[Basic grenade]]
* [[Cluster grenade]]
* [[Poison capsule]]
* [[Slowdown capsule]]

=== Combat Robot Capsules ===
With the mid-game comes access to combat robot capsules, which are deployed the exact same way as previous capsules, however they deploy different forms of hovering robots, with various behaviors and types of attacks/movement. The amount of robots that can be out at one time is limited by the [[Follower robot count (research)|Robot follower count research]].

A list of all robot capsules in the game:

* [[Defender capsule]]
* [[Distractor capsule]]
* [[Destroyer capsule]]

=== Armor ===
Once the player has faced the first proper attack, they will quickly come to learn how much damage they can handle, not much at all. Equipping a decent set of armor is therefore a priority. There are two subcategories of armor in the game, however early in the game the player will only have access to simple basic armor.

A list of all armors in the game:

* [[Light armor]]
* [[Heavy armor]]
* [[Basic modular armor]]
* [[Power armor]]
* [[Power armor MK2]]

=== Armor Modules ===
Once the player has crafted any modular armor they gain access to various general purpose enhancements, which can be freely added or removed from any modular armor. While all of them are capable of fitting in even the [[Basic modular armor]] individually, their usefulness greatly depends on player choice; i.e. there are no specific best modules or best arrangement of modules.

A list of all armor modules in the game:

* [[Basic exoskeleton equipment]]
* [[Battery MK1]]
* [[Battery MK2]]
* [[Portable solar panel]]
* [[Portable fusion reactor]]
* [[Energy shield]]
* [[Energy shield MK2]]
* [[Night vision]]
* [[Personal laser defense]]
* [[Discharge defense]]

== 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}}

{{EquipNav}}

Player

2016-11-08T16:02:41Z

Ssilk:

{{Languages}}

[[File:Player icon.png|right]]

Factorio is played from the angled top down perspective of ''player''.

The ''physical representation'' of the player is the ''[[character]]'', who is always at the center of view. In multiplayer, players characters will appear in different colors.

== Distinction between Player and Character ==

The player is only the "player-view". It is a virtualy, sweeping "it". The player stands unlike to the [[character]], the little person, that runs around on ground! The character is part of the player, but the player is not the character.

You can for example play in good-mode (play in sandbox-mode). In that mode you don't have a character, only a player-view.
Only a character can have slots for your weapons, which means: You cannot fire weapons, when in good-mode.

== World Interaction ==
The player has five primary ways of interacting with the world:

# Crafting [[Item|items]] and [[Items#Placeable_items|entities]] personally from resources using the craft menu (Default open key: E)
# Placing entities by selecting them from the inventory or toolbar and placing them on a [[tile]] (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 [[Item#Resources|resources]] from a tile (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)

''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.

== Equipment ==

Equipment are items used to speed up entity/resource collection, kill [[enemies]], protect the player's health, etc. All equipment except for weapons and capsules have durability, and will break after enough uses. Examples of equipment and the equipment inventory are discussed below.

[[File:EquipSlots.jpg|thumb|right|1: The tool slot for pickaxes. 2: The armor slot. 3: The weapon slots. 4: The ammo slots.]]

=== Tools ===
Removing or harvesting machines, entities, or resources from the world requires effort and this is implemented by way of a progress bar that needs to fill uninterrupted in order to complete and pick up the object. Starting without a pickaxe, it will take around two seconds to cut down a single tree. Since this is the sort of action required thousands of times over the course of a game, ''it is heavily recommended to craft an [[iron axe]] as the first action the player takes in the game''.

A full list of all tools in the game:

* [[Iron axe]]
* [[Steel axe]]
* [[Repair pack]]
* [[Basic electric discharge defense remote]]

=== Weapons ===
Eventually, whether in a peaceful game or not, one will need the capability to destroy the various [[Enemies]] that live in the world.

This capability mostly comes in the form of [[Turrets]] for base defense, but for the player there are two broad categories, more traditional weapons and capsules; discussed below. To fire the main equip-able weapons, the weapon must be in one of the weapon slots. (see above)

If all the preparation is done, fire the weapon with the target enemy key (Default: Spacebar) or the target cursor key (Default: C). Target enemy is a ''safe'' auto-aim that will snap to any enemy in range and begin firing at it for as long as the key is held down. A green target reticle will be shown below the enemy when in range, red when not.

Target cursor will fire your weapon in the direction of your cursor, which is mainly used to clear obstacles such as [[Tree]]s and rocks that block placing things. Bear in mind that damage is calculated as a combination of weapon, ammunition and technology together. Target cursor is capable of shooting anything with health, so be careful when near important buildings. In late game, player gunfire can nearly instantly destroy some buildings.

Each player starts with a simple [[Pistol]] and ten magazines of [[Firearm magazine|basic ammo]], which will fend off the first few biter attacks, but will quickly be insufficient against the growing alien forces.

A list of all traditional weapons in the game:

* [[Pistol]]
* [[Submachine gun]]
* [[Shotgun]]
* [[Combat shotgun]]
* [[Rocket launcher]]
* [[Flamethrower]]

=== Capsules ===
Capsules are consumable weapons systems, they are picked up from the inventory and thrown somewhere in the game world to spawn their effect at that position. Early in the game, these take the form of instant effect grenades that detonate upon reaching the location they were thrown to.

A list of all throw-able capsules in the game:

* [[Basic grenade]]
* [[Cluster grenade]]
* [[Poison capsule]]
* [[Slowdown capsule]]

=== Combat Robot Capsules ===
With the mid-game comes access to combat robot capsules, which are deployed the exact same way as previous capsules, however they deploy different forms of hovering robots, with various behaviors and types of attacks/movement. The amount of robots that can be out at one time is limited by the [[Follower robot count (research)|Robot follower count research]].

A list of all robot capsules in the game:

* [[Defender capsule]]
* [[Distractor capsule]]
* [[Destroyer capsule]]

=== Armor ===
Once the player has faced the first proper attack, they will quickly come to learn how much damage they can handle, not much at all. Equipping a decent set of armor is therefore a priority. There are two subcategories of armor in the game, however early in the game the player will only have access to simple basic armor.

A list of all armors in the game:

* [[Light armor]]
* [[Heavy armor]]
* [[Basic modular armor]]
* [[Power armor]]
* [[Power armor MK2]]

=== Armor Modules ===
Once the player has crafted any modular armor they gain access to various general purpose enhancements, which can be freely added or removed from any modular armor. While all of them are capable of fitting in even the [[Basic modular armor]] individually, their usefulness greatly depends on player choice; i.e. there are no specific best modules or best arrangement of modules.

A list of all armor modules in the game:

* [[Basic exoskeleton equipment]]
* [[Battery MK1]]
* [[Battery MK2]]
* [[Portable solar panel]]
* [[Portable fusion reactor]]
* [[Energy shield]]
* [[Energy shield MK2]]
* [[Night vision]]
* [[Personal laser defense]]
* [[Discharge defense]]

== 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}}

{{EquipNav}}

Radar

2016-11-08T15:28:08Z

Ssilk:

{{Languages}}
{{:Radar/infobox}}
The radar triggers '''[[charting]]''' of the map, which 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. Radar has a high [[Electric network|power]] demand (300kW) so a radar indirectly contributes to [[Pollution]] when powered by [[Boiler]]s and [[Steam engine|steam engines]]. The radar will be attacked by enemies that come within very close range, like turrets, but will not attract biters from long range like polluting structures do.
The radar will show enemy lifeforms and structures, as well as trains, cars, and other players in the scanned area.

== Nearby Pulse Scanning ==

Radar continuously [[charting|charts]] a charting area of 100x100 [[tile]]s. Which mean, that you most times chart 7x7 [[Chunk]] (224x224 [[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 ==

Radar [[charting|charts]] one distant [[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.
* 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 29x29 chunks around the Radar, excluding the nearby 7x7 chunk.
** With a total number of 797 chunks (29x29 - 7x7), 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, don't be taken unawares.

== Coverage ==

Something easily missed is that Radars give a line of sight around them, this is good for keeping tabs on distant bases if they get attacked and to see how big the attack is. The radar's LOS updates once every second, so keeping one or two around your base could prove to be an early warning system. Keep in mind the update rate for the LOS of the radar is not the same as the rate at which the radar will reveal unexplored terrain, which updates once every ~30 seconds. You can see the LOS given in the image below, taken from map view.

[[File:Radar_Coverage.jpg|upright=3]]

== History ==

{{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 ==
* [[Electric network]]
* [[Enemies]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3362 long term radar behavior].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3925 Self sufficient radar outpost].
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5793 Self defending independent radar layout].
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=6008&p=53660#p53660 Forum Radar Build Thread]

[[Category: Items]] [[Category: Electric network]] [[Category: Combat]]

Map generator

2016-11-08T14:20:59Z

Ssilk:

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Charting (Make Invisible Chunks Visible on Map)===

As long as a chunk is invisible the part of the players map keeps black. This changes, when a chunk is '''charted''', which means when it is "touched" by radar. Either the players internal radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 240 [[game-second|game-minutes]] (=4 hours) by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Transport belts/Physics

2016-11-08T14:09:07Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): (1/32 tiles/tick) / (9/32 items/tile) = 0,111111111 items per tick or 6,666666667 items per second for one lane. For two lanes it is then 13,333333333 items/second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on one lane of a belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt (two lanes)!

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast transport belt]]s two slots, for [[Express transport belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

==== Good to know, but practically useless ====

The least common multiple of 9 and 32 is 288. That is 9 * 32, which means: After 9 tiles the slots are repeating their positions. Which means: if you place some inserters every 9 tiles and move them in exact sync (via circuit network) you can fill a belt without the trick of using a splitter or undergroud-belt.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes (Version 13.3 and above).

{| class="wikitable"
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | density (two lanes) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.556
|align="center" |7.111
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.556
|align="center" |7.111
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.556
|align="center" |7.111
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal and maximum compressed (see above), so the transported amount should reflect the speed.

= History =
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

== Theory ==

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

== Measured Results for v0.11 or Older ==

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Transport belts/Physics

2016-11-08T14:04:28Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): (1/32 tiles/tick) / (9/32 items/tile) = 0,111111111 items per tick or 6,666666667 items per second for one lane. For two lanes it is then 13,333333333 items/second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on a tile of belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt!

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast transport belt]]s two slots, for [[Express transport belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

==== Good to know, but practically useless ====

The least common multiple of 9 and 32 is 288. That is 9 * 32, which means: After 9 tiles the slots are repeating their positions. Which means: if you place some inserters every 9 tiles and move them in exact sync (via circuit network) you can fill a belt without the trick of using a splitter or undergroud-belt.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes (Version 13.3 and above).

{| class="wikitable"
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | density (two lanes) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.556
|align="center" |7.111
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.556
|align="center" |7.111
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.556
|align="center" |7.111
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal and maximum compressed (see above), so the transported amount should reflect the speed.

= History =
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

== Theory ==

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | throughput (2 lanes) items/sec
! scope="col" | throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

== Measured Results for v0.11 or Older ==

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Transport belts/Physics

2016-11-08T13:43:16Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): 9/32 items/tile * 1/32 tiles/tick = 0,008789062 items per tick or 0,52734375 items per second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on a tile of belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt!

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast transport belt]]s two slots, for [[Express transport belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

==== Good to know, but practically useless ====

The least common multiple of 9 and 32 is 288. That is 9 * 32, which means: After 9 tiles the slots are repeating their positions. Which means: if you place some inserters every 9 tiles and move them in exact sync (via circuit network) you can fill a belt without the trick of using a splitter or undergroud-belt.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes.

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

{| class="wikitable"
|+Expected results 13.3 and newer
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.555
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.555
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.555
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal, so the transported amount should reflect the speed.

Awaited throughput above matches actual for .12 and .13 versions of the game.

== Measured Results for v0.11 or Older ==
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Transport belts/Physics

2016-11-08T13:39:41Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): 9/32 items/tile * 1/32 tiles/tick = 0,008789062 items per tick or 0,52734375 items per second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on a tile of belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt!

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast belt]]s two slots, for [[Express belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

==== Good to know, but practically useless ====

The least common multiple of 9 and 32 is 288. That is 9 * 32, which means: After 9 tiles the slots are repeating their positions. Which means: if you place some inserters every 9 tiles and move them in exact sync (via circuit network) you can fill a belt without the trick of using a splitter or undergroud-belt.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes.

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

{| class="wikitable"
|+Expected results 13.3 and newer
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.555
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.555
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.555
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal, so the transported amount should reflect the speed.

Awaited throughput above matches actual for .12 and .13 versions of the game.

== Measured Results for v0.11 or Older ==
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Transport belts/Physics

2016-11-08T13:27:44Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): 9/32 items/tile * 1/32 tiles/tick = 0,008789062 items per tick or 0,52734375 items per second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on a tile of belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt!

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

Yes, the interior has a fractional slot: every odd interior curve is 14 slots and every even interior curve is 13 slots.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast belt]]s two slots, for [[Express belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes.

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

{| class="wikitable"
|+Expected results 13.3 and newer
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.555
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.555
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.555
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal, so the transported amount should reflect the speed.

Awaited throughput above matches actual for .12 and .13 versions of the game.

== Measured Results for v0.11 or Older ==
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Transport belts/Physics

2016-11-08T13:22:52Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28125 x 0.28125 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8125 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec). The speed of basic belt is 0.03125 tiles per tick (1/32) or 1.875 [[tile]]s per [[Game-second]].
* '''Density'''. The density is ''items per tile''. How many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.5555556 items per lane or 7,111111111 (32/9*2) on a tile of belt (=2 lanes). Which means in practical terms, that on a fully compressed belt there can be either 6, 7 or 8 items during one tick.
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min. That is for basic belt density (items per tile) multiplied with speed (tiles per second): 9/32 items/tile * 1/32 tiles/tick = 0,008789062 items per tick or 0,52734375 items per second.

=== How to calculate this numbers yourself ===

==== Basic belt ====
Belts have two ''lanes'': Left and right lane.

Each lane of a belt consists out of 32 '''slots'''. A slot is just a virtual position on the belt with the width of 1/32 tiles (= 0.03125 tiles).

An item, that is put on a belt (on a lane) takes 9 slots of space. This explains the size of items: 0.28125 x 0.28125 [[tile]]s (9/32 = 0.28125). Which means also, that 32/9 items (3,555555556 items) can fit on one lane of one belt. Which means: Either 3 or 4 items fit on a tile of belt (32/9 × 2), which means either 6, 7 or 8 items fit on one belt!

Speed: Each [[Game-tick|tick]] an item on a belt (the 9 slots it takes) is moved by one slot. That explains the speed of a basic belt: 0.03125 tiles per tick (1/32).

==== Curves ====
The inner lane has 13.5 slots the outer 37 slots. Which means in the end, that either 6 or 7 items can be in curves.

==== The faster belts ====
For that the number of slots, that an item is moved per tick is just multiplied. For [[Fast belt]]s two slots, for [[Express belt]]s 3 slots. That explains, why fast belts are exactly 2 times faster, than basic and express belt is 3 times faster than basic.

For more information around this subject you might read this article: [https://forums.factorio.com/viewtopic.php?f=18&t=33685&hilit=belts+pipes Factorio: a quantitative guide]

== Theory ==
The data here is taken from the transport-belt prototypes.

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

{| class="wikitable"
|+Expected results 13.3 and newer
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.555
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.555
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.555
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal, so the transported amount should reflect the speed.

Awaited throughput above matches actual for .12 and .13 versions of the game.

== Measured Results for v0.11 or Older ==
'''This is outdated and should be outsourced from this article but not deleted, cause it is an interesting fact.'''

With Factorio v0.12 new belt physics was introduced. Before that the items where moved as real objects (which means, they need to look forward, if there is space to move), with 0.12 the items are moved "per lane". Also the physics in curves changed so that curves are now not longer have lower throughput.

{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

=== Comments to the results ===

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450|Factorio and real physics]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

Map generator

2016-10-21T22:20:47Z

Ssilk: Fixed math

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console/Lua_commands#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Generating Visible Chunks===

A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 240 [[game-second|game-minutes]] (=4 hours) by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Map generator

2016-10-21T22:19:22Z

Ssilk: Fixed math

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console/Lua_commands#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Generating Visible Chunks===

A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 480 [[game-second|game-minutes]] (=8 hours) by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Energy and work

2016-10-13T11:16:00Z

Ssilk:

{{Languages}}
Factorio simulates many aspects of real physics and the quite correct use of energy is one important aspect.

Energy and work are directly dependent.

== Game physics is not reality ==

The Factorio Game physics is quite realistic, but simplified. Please do not compare this definition to those of [http://en.wikipedia.org/wiki/Work_%28physics%29 real physic]. See also the [[Talk:Energy and Work|Talk-page]].

Another explanation can be found in the [https://forums.factorio.com/viewtopic.php?f=18&t=33963 Forum]

== Work ==

'''Work is "stored energy" or the "result of using power". If you divide the work into parts and release the parts in some time you have energy.

Work is measured in Joules, which is one Watt over the time of one second. See [[Units#Work]].

=== Types of work ===

Work is available (or storable) as
* [[Fuel]].
* Capacity in the [[Basic accumulator]]s.
* [[Liquids/Hot|Hot liquids]]. You can create them in the [[Boiler]] and store serious amount in the [[Storage Tank]].

== Energy / Power ==

'''Energy is the "ability to do work". The speed of this doing needs more or less power. The faster something works, the more power is needed, but the result (the work) is the same. In Factorio this is also used a lot to [[Mining drill#Mining_Speed_Formula|calculate, how much time is needed to produce stuff]].

Energy is measured in Watts, nearly every device in Factorio needs energy to work. Energy is produced by [[Electricity/Generator|Generators]], [[Boiler]]- or other burner- (or motor-driven) devices (like the car or train).

See [[Units#Power]].

=== Types of energy ===

==== [[Fuel|Fuel-based]] (Boiler, Burner) ====

[[Fuel]] contains a certain amount of energy. The fuel is burned and produces energy (which is converted into movement or heat) and [[Pollution]] is emitted.

There are [[Fuel#Burner devices to be fueled directly|some devices]], which can use fuel directly.

==== [[Electric system|Electricity]] ====

[[Electric system|Electricity]] is produced by [[Electric system|Generators]]. The [[Electric system|distribution]] is made over an [[Electric system|Electric network]], and it is used by [[Electric system|Consumer]]s.

That's the single parts! The whole process is also explained as [[Electric system|Power Production]].

Electricity is the only way to transport energy over long distances. [[Electric system|Electricity]] itself doesn't pollute, the pollution comes either from burning fuel or consuming electricity.

Transport belts/Physics

2016-10-03T19:54:55Z

Ssilk:

{{Languages}}
{{sublinks}}
In Factorio every item on screen is a real object in memory and follows the rules of the [[Game engine]]. For simulation games, this is not typical; it's much more common to generalize. Best examples are the older versions of SimCity, where the the simulation doesn't simulate every inhabitant of the city.

The reason for that is just CPU-performance. Real-time game-physics for up to 100,000 of objects at the same time is not typical for a simulation game. And the Factorio [[Game engine]] creates an exact and reproducible simulation of the Factorio world and it is so exact, that it can be used, to measure some astonishing behavior of belts.

== What to measure ==
Some things can be measured for belts:
* '''Length''' (or area). Items have a collision box of 0.28 x 0.28 [[tile]]s. So 10 items laying in a single row on a belt, non moving, take length of 2.8 tiles.
* '''Speed'''. The speed of items on a belt is measured for practical reasons in tiles/sec or tiles/min. Note, that internaly it's measured in tiles per tick (1/60 sec)
* '''Density'''. See length. The density is how many items can lay on a tile or in conjuction with belts: how many items can lay in a row/lane. There are in average 3.571 items per lane or 7.143 on a tile of belt (=2 lanes). But the density differs depending on standing still or moving - read further!
* '''Throughput'''. How many items per minute are moved from one tile to the next. Measured in items/sec or better items/min.

More about physics can be found in this [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1213&p=8450&hilit=physics#p8450 thread].

== Theory ==
The data here is taken from the transport-belt prototypes.

{| class="wikitable"
|+Expected results 13.2 or older
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.571
|align="center" |13.39125
|align="center" |803.475
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.571
|align="center" |26.7825
|align="center" |1606.95
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.571
|align="center" |40.17375
|align="center" |2410.425
|}

{| class="wikitable"
|+Expected results 13.3 and newer
|-
! scope="col" | belt-type
! scope="col" | factor basic belt speed
! scope="col" | speed (tiles/tick)
! scope="col" | speed (tiles/sec)
! scope="col" | speed (tiles/min)
! scope="col" | density (single lane) items/tile
! scope="col" | awaited throughput (2 lanes) items/sec
! scope="col" | awaited throughput items/min
|-
|Basic
|align="center" |1
|align="center" |0.03125
|align="center" |1.875
|align="center" |112.5
|align="center" |3.555
|align="center" |13.33
|align="center" |800.00
|-
|Fast
|align="center" |2
|align="center" |0.0625
|align="center" |3.75
|align="center" |225
|align="center" |3.555
|align="center" |26.66
|align="center" |1600.00
|-
|Express
|align="center" |3
|align="center" |0.09375
|align="center" |5.625
|align="center" |337.5
|align="center" |3.555
|align="center" |40.00
|align="center" |2400.00
|}

We assume here, that the density of items is always equal, so the transported amount should reflect the speed.

Awaited throughput above matches actual for .12 and .13 versions of the game.

== Measured Results .11 or Older ==
{| class="wikitable"
| This results have been measured with a special designed factory (a complicated setup to guarantee, that only the running items on a belt are measured and a "timer" which stops the measuring exactly) and Factorio v0.6.x, so this has to be redone.
See [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1144&start=10#p8361 forum article]
|}

{| class="wikitable"
|+Simple straight belt
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| throughput items/sec
! scope="col"| percent of awaited
! scope="col"| comments
|-
|Basic
|align="center" | 719
|align="center" | 11.98
|align="center" | 90%
|
|-
|Fast
|align="center" | 1184
|align="center" | 19.73
|align="center" | 74%
|this is NOT double as fast as basic! it's only 1,65 times faster - see comments down
|-
|Express
|align="center" | 1775
|align="center" | 29.58
|align="center" | 74%
|about 2.5 times faster than basic
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right, see down into next chapter)
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic
|align="center" | 477-486
| About 1.5 times slower. This is because the '''inner lane''' of a belt in a turn has only the half speed.
|-
|Fast
|align="center" | 786-792
|
|-
|Express
|align="center" |1038-1042
|
|}

{| class="wikitable"
|+Belt with 4 turns (2 left, 2 right), but faster belt at the edges
|-
! scope="col"| belt-type
! scope="col"| throughput items/min
! scope="col"| comments
|-
|Basic with fast edge-belts
|align="center" | 674-683
|
|-
|Fast with express edge-belts
|align="center" | 1058-1061
|The fast belt with express edge seems to be faster, than pure express belt!
|}

== Comments to the results ==

The first surprising result is, that the theoretic throughput differs from real measured. Too much to be just measurement errors.The second result is, that the more speed a belt has, the more ineffective it becomes. That is in the first moment not clearly explainable. The awaited result is, that a fast belt can transport exactly the double amount of items, than a basic, because it is double as fast (1.875 tiles/sec vs. 3.75 tiles/sec).

The reason for this difference is the distance of the items on the belt when running. Items on the belt cannot run completely compressed, they need a small distance. This is the same problem as in a traffic jam: You cannot drive, when the first car drives, you need to wait until the car before you drives and then you have a reaction-time of about 1/2 second before yourself begin to drive. The same is it with the items on the belt and the reaction-time here is 1/60 or one tick [currently not really validated, but not more than 2 ticks; this can be calculated by measuring how fast the standing wave goes through the items (needs to built a very complicated testing factory)]. You can see this reaction time running through your items as a standing wave, when you have a belt, which is completely filled and only sometimes an item is removed. When you compare the speed of this standing waves, you can see clearly, that they are the same speed for all types of belts.

The reaction-distance for items on a basic belt is
(1.875 tiles/sec) / 1 tick = 1.875 tiles/sec / 1/60 sec = 0.031125 tiles
or in other words: An item on a moving belt is not 0.28 tiles long, it is 0.31125 tiles, which makes it 11.2% longer

Overview for all belts:
Basic: 0.28 tiles + 0.03125 tiles = 0.31125 tiles => 11.2%
Fast: 0.28 tiles + 0.0625 tiles = 0.3425 tiles => 22.3%
Express: 0.28 tiles + 0.09375 tiles = 0.37375 tiles => 33.5%
This explains the reduction to 90% of speed for basic belt and the 74% for the fast belt (all inside measuring errors), but doesn't explain the results for express belt. This is part of further research.

This shows clearly, that the faster a belt is, the more distance the items have on a moving belt. More distance means, the density is lighter and this means, there are not so many items transported.

(This may explain the discrepancy in transported items, but don't use the numbers for real calculations, because they need to be redone!)
(This is eventually one reason: http://www.factorioforums.com/forum/viewtopic.php?f=8&t=3630 )

A possible reason for this: http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817

== See also ==
* [[Transport network]]
** [[Transport belts]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=6817 Yellow splitters are as fast as blue belts]
* [http://www.factorioforums.com/forum/viewtopic.php?f=16&t=7043 Fast belts have lower density, than other belts]

* [http://www.conveyorbeltguide.com/ Some general information about real conveyor belts]

* [https://forums.factorio.com/viewtopic.php?f=18&t=33685 Factorio: a quantitative guide]

[[Category: Items]] [[Category: Transport network]] [[Category: Moving ground]]

User:Ssilk/test

2016-09-20T03:40:11Z

Ssilk: Created page with "== some ref test == <ref>Aristoteles: ''Physics''; [https://ebooks.adelaide.edu.au/a/aristotle/physics/ Aristotle, ''Physics'', trans. by R. P. Hardie and R. K. Gaye].</ref>..."

== some ref test ==
<ref>Aristoteles: ''Physics''; [https://ebooks.adelaide.edu.au/a/aristotle/physics/ Aristotle, ''Physics'', trans. by R. P. Hardie and R. K. Gaye].</ref>

== references ==
<references />

Circuit network

2016-08-12T07:45:03Z

Ssilk:

{{Languages}}
'''Circuit networks''' are built using red or green wire, and enable the control of [[Automatic control/Devices#Receiver|receiver devices]], based upon information broadcast onto the network by connected [[Automatic control/Devices#Sender|sender devices]]. Most senders are storage devices, and broadcast their information onto a specific channel, based on the item or liquid the storage device contains. Each circuit network contains a channel for every kind of item, as well as 45 extra [[Automatic control/Virtual signals|Virtual signals]] which act as user-definable channels.

:[[File:InnerOfGreenCable.jpg|400px]]

== Physical network structure ==
A circuit network consists only of those devices connected together with the same color wire. Wire can be strung directly from device to device, or across any intervening power poles.

Note that each connected set of wires forms a separate network. For example, it's entirely possible to have four red-wire networks and three green-wire networks. Red and green networks will remain separate and do not link up if red and green wires happen to touch the same power pole or device.

* To connect wires or cables to a power pole, drag the wire to the base of the pole.
* To erase a wire or cable connection, drag the same color wire over an existing connection. You don't get the wire/cable back.
* To remove '''all''' connections from a power pole, shift-click on the pole. The first shift-click will remove all electrical connections, and the second will remove all red and green wires. You don't get the wires back.
* When connecting to a [[Arithmetic Combinator]] or [[Decider Combinator]], take care to drag the wire to the correct input or output side. Use ALT-Key-Mode to see direction of combinator.

== Broadcast Information ==
[[Automatic control/Devices#Sender|Sending devices]] broadcast the amount of [[Items]] or [[Liquids system|Fluids]] they contain or other data definable by the player. Each amount is broadcast as a numeric value on a 'channel' corresponding to the item they contain. For example, a Storage Tank containing 1000 Crude Oil will broadcast 1000 on the Crude Oil channel.

Multiple broadcasts of the same item or fluid are additive: if there are two connected Storage Tanks with 1000 Crude Oil each, the value of the Crude Oil channel will be 2000.

Wires which are connected together by a junction will pass their signals to the other wires of the same color. For example, if two red wires are connected to the same combinator input, each wire receives the content from the other. This can result in feedback if care is not taken; see Feedback (under Arithmetic Combinator, below) for discussion.

== Use of Information ==
[[File:smart_inserter.png|thumb|250px|Example condition: "Work only if the count of Iron plates is lower than the count of Steel plates."]]
[[Automatic control/Devices#Receiver|Receiving devices]] can use broadcast information, in most cases to enable/disable the device.

They can either compare results between different channels, or compare a channel to a specific value. The pictured inserter works if the count of [[Iron plate|Iron plates]] is lower than the count of [[Steel plate|Steel plates]].

Receiving devices sum all signals from each wire connected to them, even red and green wires. For example, if an inserter is connected to a red wire carrying a signal for 20 iron plates, a green wire with 10 copper plates and another green wire with 5 iron plates, the input signal set for that receiver will be 25 iron plates and 10 copper plates.

== Basic ==
[[File:circuit-network-example-1.png|thumb|256px|A basic circuit network usable to fill a chest with a defined amount of items.]]

The simplest network is to connect a smart inserter with a chest next to it, to control the amount of items in the chest.
(Note that you do not have to connect them using a power pole as the picture shows; you can connect them directly.)

== Combinators ==
Combinators can function as both receiving and sending devices and allow more advanced functions to be used on a circuit network.

*The [[Constant Combinator]] broadcasts up to 15 values on any of the channels for whatever networks it is connected to. (You cannot currently specify whether a value should be red or green; if you need different values, use two combinators, one for each color wire.) You can use any item channel or any of the [[Automatic control/Virtual signals|virtual signal]] channels.
**Note that using two of the 15 slots to broadcast values on the '''same''' channel is the same as broadcasting the sum of the two values from one slot.

*The [[Arithmetic Combinator]] performs arithmetic operations on input values and broadcasts the result to the specified output channel. The input and output channels can be any item channel or any of the virtual signal channels.
** Connecting: The Arithmetic Combinator connects to a red or green network on its '''input''' side (the terminals are set into the main body and look like spark plugs) and performs an arithmetic calculation which is broadcast into the specified channel on its '''output''' side (the output wires appear to stretch out a bit from the body of the device).
** Feedback: Note that the input network and the output network '''are not the same network'''. Connecting the output network back to the input network will result in a feedback loop. For example, adding 1 to the value for Copper Plates and broadcasting it as Copper Plates is an action that results in an infinite loop if output is connected back to input. The value for Copper Plates will rapidly (but not instantly) shoot upward. This technique can be combined with Decider Combinator logic to make electronic clocks, gates, and other systems; see [[Combinator Tutorial]] for advanced techniques.
** Each: This combinator can use the 'Each' signal for both input and output, in which case '''all''' non-zero input channels will have the combinator's operation performed and broadcast on the output side. Having Each signals for input and output and using a non-changing operation (like adding zero) is equivalent to having a 'one-way' wire; all the information from the input network is copied to the output network, but the reverse is not true.
**Multi-network: The Arithmetic Combinator can be joined to both red and green networks on the input side and will sum their inputs.

*The [[Decider Combinator]] functions much like an Arithmetic Combinator, but is designed to compare values. In terms of Connecting, Feedback, and the Each signal it functions as specified above. In addition, it can handle the Everything and Anything signals, and performs more complex functions than summing when attached to multiple networks. See the [[Decider Combinator]] page for more details on how to use this.

== Logistic Network ==
The Logistic network used by [[Logistic robot|Logistic Robots]] is essentially a third network (a wireless one), along with the green and red wired network. The Logistic Network is based on proximity to a central [[Roboport]].

Some devices can also be connected to the logistic network. If a device has conditions set for circuit and for logistic network, it will become activated if both conditions are true.

See [[Logistic network]] for more information.

== [[Automatic_control/Devices|Items/Devices]] ==
In v0.13 the factorio developers made many devices connectable to the circuit network, so there are many possibilities to control and program your factory based on conditions.

=== Examples (''outdated'') ===
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3149 Forum article about the basic usage]
* [http://www.factorioforums.com/forum/viewtopic.php?f=9&t=696&p=24183#p24183 About comparison of the circuit wires with examples from the real world]* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=348 Logic Gates, Edge Detector]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=4728&p=37251#p37157 Logic gates revisited]
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=3211&p=23692#p23676 Evenly fill two item onto one lane]
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=298 Material splitters]
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=6839 Logic gates using side inserter mod]

== See also ==
* [[Circuit network (research)]]
* [[Transport network]]
* [[Combinators]]
* [[Automatic control/Virtual signals]]

[[Category: Networks]] [[Category: Circuit network]] [[Category: Transport network]]

Map generator

2016-07-24T23:42:21Z

Ssilk: /* Maximum Map Size and used Memory */

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console/Lua_commands#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Generating Visible Chunks===

A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 240 [[game-second|game-minutes]] (by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Map generator

2016-07-24T23:40:19Z

Ssilk: /* Maximum Map Size and used Memory */

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console/Lua_commands#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Generating Visible Chunks===

A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 4 [[game-second|game-hours]] (by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Map generator

2016-07-24T23:27:33Z

Ssilk: /* Generating new Chunks */

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console/Lua_commands#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Generating Visible Chunks===

A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is larger than the earth land-surface. It would take around 4 game-hours by train to reach that border from the center. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Map generator

2016-07-24T13:20:30Z

Ssilk: /* Generating when exploring */

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

Everything above a defined level defines the existing (or non-existing) features of some type of terrain.

The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

 

===The top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources.
Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'': For Terrain segmentation it means: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'': For Terrain segmentation it means: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[enemy]] expansion due to the much higher number of nest clusters.

====Size====
This defines the size of generated ore patches and water through defining "levels."

It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes enemy bases to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

====Richness====
This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave.

Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

===The left column===
* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How water is generated on each map. Be warned that, since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these change.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===
This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc. from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game.

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console/Lua_commands#Useful_commands_.28cheats.29|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge.

===Map seed / Map Exchange String===

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance.

====Map Exchange String====
A string generally looks like so:
>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

There is a thread for exchanging new strings: http://www.factorioforums.com/forum/viewtopic.php?f=36&t=5807

=====Where can I use this string?=====
It can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

=====Where can I get this string from?=====
In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator or send it to a friend.

==Generation==
The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API document.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources.
The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them.

This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new 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 isn't generated from the start. A new [[Chunk]] of map is generated only when needed.

===Generating Invisible Chunks (Fog of War)===

Around the visible chunks a perimeter of three chunks wide range of invisible chunks are generated (not for the limited parts).

Invisible chunks are also generated if you produce very much pollution; the games generates so much (invisible) chunks as it needs to spread the pollution into the area.

Reason: This is for the natives, so that they can attack you from places, that you cannot see yet. This is also know as "fog of war".

===Generating Visible Chunks===

A visible chunk is generated, when it is touched by radar. Either the players radar, which is always available, or the [[Radar]] entity. When a visible chunk is generated there might be also invisible generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

===Limited Maps===

The player can limit the map size ('''limited width and height'''). Note that the player can also limit only the width or only the height, so they may generate "stripes" of land. For example, one could generate a map only 20 tiles high, but endless long!

A map is not bigger than this, there are also no invisible chunks generated beyond that limits.

Everything around the map-limits '''is considered water'''. The player can place a [[Pump]] at the edge of such a map and it will suck water out of nothing.

===For Explorers===

If the player arrives at the current visible borders the needed chunks are generated. It generally makes no difference '''when''' these chunks are generated. Note, that if you go for example east, that for every generated chunk a perimeter of 3 more chunks are generated. That means a lot of work for the CPU. The map generation runs in "background" so it is possible, that the player "overruns" the map generator, if he drives very, very fast.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (2,000,000 tiles). This is larger than the earth land-surface. It would take around 8 game-hours by train to reach that border. So we can speak here from "endless".

Because only chunks are generated around the area, that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much, if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, that is the limiting factor.

==== Maps bigger than the active available RAM?====

Maps don't need to be stored completely in active RAM. Because in case of very large maps it is quite uncertain, that a chunk changes over time, there is currently not the need to keep all chunks in RAM; for example players reported games, which need 12 GB of RAM, but they had only 8, the remaining 4 GB had been swapped out to disk. It takes then of course long to load or save such a game, but it is possible to play those games without performance issue. ([https://forums.factorio.com/viewtopic.php?f=5&t=29566 How to store 4 trillion square tiles of map in just 8 GB RAM])

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Main Page

2016-03-14T17:46:29Z

Ssilk:

[[Image:Factorio-logo.png|center|link=http://factorio.com/]]

{| style="width: 100%;"
{{ContentCell|68%|
|{{:Factorio:About}}
}}
{{ContentCell||Get the game|link=http://www.factorio.com/preorder
}}
|}

{| style="width: 100%;"
{{ContentCell|61%|[[News]]
}}
{{ContentCell|39%|Contribute|
|}}
|}

==== Before you play ====
{| style="width: 100%;"
{{ContentCell|33%|Technical
}}
{{ContentCell|33%|Frequently asked questions
}}
{{ContentCell|34%|Modding and scripting
}}
|}

==== Around the game ====
{| style="width: 100%;"
{{ContentCell|33%|[[New content]]
}}
{{ContentCell|33%|Game misc
}}
{{ContentCell|34%|Community
}}
|}

==== Playing the game ====
{| style="width: 100%;"
{{ContentCell|33%|Beginners|
|Concepts|
}}
{{ContentCell|33%|Advanced
}}
{{ContentCell|34%|Expert
}}
|-
{{ContentCell|33%|Devices
}}
{{ContentCell|33%|[[Items]]
}}
{{ContentCell|34%|Solving conflicts
}}
|}

__NOEDITSECTION__

{{C|Main}}

User talk:ACryInShame

2016-02-25T01:02:21Z

Ssilk:

'''Welcome to ''factorio''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Klonan|Klonan]] ([[User talk:Klonan|talk]]) 20:48, 10 February 2016 (UTC)

----

Well, here my promised review of this page ( http://factorioforums.com/forum/viewtopic.php?f=50&t=20029 )

All in all the page is "too condensed".

Let's begin left to right and up to down:
FAQ or News on top is a good question. It's about relevance. Currently the news are not very relevant anymore, just a copy of the FFF-links (it was much more a year ago). It would be much more useful if it's included news like "when is a release?" "What's the current state of Steam?" etc. But as it currently is, that seems to be not relevant, so bringing the FAQ into front seem currently the right idea.

Technical: It's so compressed like so doesn't look nice. Well, when I see it now it seem for me to be logical to move that box to the right to "Get the game".

Get the game: When the "Technical" is moved into here it has the right size for that.

Community: Hm. Dunno. Putting two items into one box looks for me in most cases to compressed/not good looking. I don't know yet, where to move it... but here it doesn't look nice.

Beginners/Advanced/Expert: Well that is taken more or less from the original (and I made it), but when I look at it with the distance of one year I can say, that I like the Beginners, but not Advanced/Expert. There is no logic to say "This is beginner, that is Expert".

Concepts: Would be more useful right to Beginners.

Modding and scripting: Doesn't belong here!

The next line with the 5 boxes is a no go! Maybe 4, if only that slim, but 5 will kill the design.

Networks: Well you cannot know, that these is a remaining things from 2 years ago, where the homepage was sorted into "networks". We had some discussion around this and the result is mainly, that Factorio has some networks, like Electrity, Logistic, eventually Liquid and Railway, the rest is no "network" at all. And the better word to describe that all is "System". One result of that discussion was for example the "Belt Transport System". So this box shows only, that there is much, much work to do to rename all that pages. :)

Contribute: I don't see, why that is sorted at the bottom. That thing is essential. Maybe not on the top, but I see that generally more in the middle of the page.

New contents: that is completely outdated. In it's origin it was thought for the roadmap and new game contents.

Game misc: That is generally much more on top. Stuff like how to use the console is important.

'''Summary''': Some ideas a neat, but the current sorting of this page is not useful. I've some ideas of how to improve that, but I'm currently too tired to continue here so i hope it's o.k. to stop now, so that you have a chance to answer. :)

[[User:Ssilk|Ssilk]] ([[User talk:Ssilk|talk]]) 01:02, 25 February 2016 (UTC)

Talk:Stone/es

2016-02-18T13:47:27Z

Ssilk: Created page with "Please read Wiki_Howto#Translations how to make translated pages."

Please read [[Wiki_Howto#Translations]] how to make translated pages.

Power production/Optimal ratios

2016-02-12T17:52:36Z

Ssilk: Changed table, cause I need to think 3 minutes how to interpret it. Dunno, who has made that... :)

{{Languages}}
{{sublinks}}

This is about how many [[Boiler]]s, [[Pump]]s, [[Steam engine]]s and also ratios of [[Solar panel]] and [[Basic accumulator]] (and more).

== Hot liquids ==

=== Steam engines, pumps and boilers ===

{| class="wikitable"
|+ Needed number of entities in different situations
! Situation !! # of steam engines !! # of boilers !! # offshore pumps !! Comment
|-
| One steam engine || '''1''' || 2 || 1 || makes barely sense
|-
| One off-shore pump || 10 || 14 || '''1''' || this is the most used setup!
|-
| Full throughput of a pipe || max. 21 || max. 28 || 2, better 3 || the total throughput depends on the total length of all pipes in a row
|}

Each steam engine needs roughly 1.31 boilers when running at full capacity.

One [[Pump|offshore pump]] can satisfy 14 [[Boiler]]s and 10 [[Steam engine|steam engines]]. 13 boilers will make the job also, but this tends to have problems to raise the temp after coal shortness or other accidents ([[Biter]]s love to attack the boilers).

To fully satisfy a pipe you need 3 [[Pump]]s or 5 [[Small pump]]s (or better 6, but that depends on pressure!). But with this setup you will find, that the length of your pipe-setup will influence this too much. This is definitely not a beginner strategy.

==== See also ====
* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=5950 Research topic about energy]
* [[Liquids/Hot|Hot Liquids]]
* [[Liquids/Pipe physics]].

=== Hot liquids in tanks ===

To equalize the needed throughput (different needs of energy between day and night for example), hot water from boilers can also be stored in [[Storage Tank|storage tanks]] and used by extra steam engines during peak times or during night (if solar is in place). This energy storage technique can be used instead of or in addition to [[Basic accumulator|accumulators]].

See [[Liquids/Hot#Storing_hot_liquids_as_energy_storage|about storing of hot liquids]] how to use that.

== Solar/Accu ==

=== Optimal ratio ===

The optimal ratio is 0.84 (25:21) accumulators per solar panel.

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!

There are former threads:

* http://www.factorioforums.com/forum/viewtopic.php?f=5&t=5168
* http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5394

And later:
* http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7619

=== Perfect placing ===

* [http://www.factorioforums.com/forum/viewtopic.php?f=8&t=1865 Big solar farm]: About the perfect placing of panels

Offshore pump

2016-02-12T17:42:07Z

Ssilk: Made also a link to the ratios page...

{{Languages}}
{{Machinery
|health =80
|input =time, 0.5 + electronic circuit, 2 + pipe + iron gear wheel
|raw =time, 4 + iron plate, 5 + copper plate, 3
|producers =Manual + assembling machine 2 + assembling machine 3
}}
The '''offshore pump''' is the only source of water. It is commonly used to provide steam to [[Steam engine|steam engines]] for power generation. The offshore pump itself requires no power to operate. (This is because, otherwise the game might fall into a serious deadlock: No coal, no electricity, no water...)

You need 2 (or better 3) offshore-pumps to feed one pipe to the '''maximum throughput''' (for example if you have '''more than 10''' [[Steam engine]]s working at 100%).

'''This is explained more in [[Power_production/Optimal_ratios#Hot_liquids|optimal ratios]]'''.

==See also==
* [[Electric network]]
* [[Liquid network]]

{{MachineNav}}

[[Category:Items]]
[[Category:Liquid network]]

Offshore pump

2016-02-12T17:33:11Z

Ssilk: Reverted to former version and edited, cause "fill" was meant to "feed ... fill", which is meant as the throughput of a pipe, not the level - which can be misunderstood, that is correct, but the replacement was not understandable for beginners.

{{Languages}}
{{Machinery
|health =80
|input =time, 0.5 + electronic circuit, 2 + pipe + iron gear wheel
|raw =time, 4 + iron plate, 5 + copper plate, 3
|producers =Manual + assembling machine 2 + assembling machine 3
}}
The '''offshore pump''' is the only source of water. It is commonly used to provide steam to [[Steam engine|steam engines]] for power generation. The offshore pump itself requires no power to operate. (This is because, otherwise the game might fall into a serious deadlock: No coal, no electricity, no water...)

You need 2 (or better 3) offshore-pumps to feed one pipe to the maximum throughput (for example if you have 10 [[Steam engine]]s working at 100%).

==See also==
* [[Electric network]]
* [[Liquid network]]

{{MachineNav}}

[[Category:Items]]
[[Category:Liquid network]]

Offshore pump

2016-02-12T17:25:50Z

Ssilk: Reverted edits by ACryInShame (talk) to last revision by Emailformygames

{{Languages}}
{{Machinery
|health =80
|input =time, 0.5 + electronic circuit, 2 + pipe + iron gear wheel
|raw =time, 4 + iron plate, 5 + copper plate, 3
|producers =Manual + assembling machine 2 + assembling machine 3
}}
The '''offshore pump''' is the only source of water. It is commonly used to provide steam to [[Steam engine|steam engines]] for power generation. The offshore pump itself requires no power to operate. (This is because, otherwise the game might fall into a serious deadlock: No coal, no electricity, no water...)

You need 3 offshore-pumps to feed a full pipe to the maximum (two will do also the job).

==See also==
* [[Electric network]]
* [[Liquid network]]

{{MachineNav}}

[[Category:Items]]
[[Category:Liquid network]]

Talk:Main Page

2016-02-12T17:18:06Z

Ssilk:

==Main Page Overhaul==
The Wiki Page needs to be reorganized. It currently is a confusing mess and should be more organized for easier navigation. As i do not have access to edit this page i'll continue to add to other pages but i believe the real fixing of this WIKI would need to start at the root.
--[[User:ACryInShame|ACryInShame]] ([[User talk:ACryInShame|Talk]]) -12 Feb 2015 10:15 (EST) -5hr

:I read your forum-article and answered there http://factorioforums.com/forum/viewtopic.php?f=50&t=20029 [[User:Ssilk|Ssilk]] ([[User talk:Ssilk|talk]]) 17:18, 12 February 2016 (UTC)

==Adding Changelogs==
Shouldn't we add a changelog page and link it to the main one ?--[[User:Staxxy|Staxxy]] ([[User talk:Staxxy|talk]]) 22:53, 4 March 2013 (CET)
:It is actually linked on the main page as "Version History" under the "get the game" section. Not sure what the preference is on that name comparged to "Change Log". - [[User:BenWo|BenWo]] ([[User talk:BenWo|talk]]) 12:46, 16 May 2014 (CEST)

==Pages blueprint==
We would need to set up conventional presentations for pages depending of their topic.
For example, all pages covering weapons should be presented the same way, with the same organisation, ect...--[[User:Staxxy|Staxxy]] ([[User talk:Staxxy|talk]]) 23:14, 4 March 2013 (CET)
:I like this idea! We need standard templates for the big categories to make navigating easier. I'll certainly start work on this as time allows. [[User:BenWo|BenWo]] ([[User talk:BenWo|talk]]) 08:11, 15 May 2014 (CEST)
::Putting updates on my navbox work over on [[Talk:Wiki_To-do_List]] to save this for talk about the main page. - [[User:BenWo|BenWo]] ([[User talk:BenWo|talk]]) 12:35, 16 May 2014 (CEST)

==More content==

I started doing a bit of tweaking on the Main page over on [[User:BenWo/Main_Page]] to try and fit some more of these items. I've also moved all of the HTML off into some templates to keep it cleaner. Feel free to go over there and move bits around with whatever ideas you've got. :) - [[User:BenWo|BenWo]] ([[User talk:BenWo|talk]]) 12:44, 16 May 2014 (CEST)
:Moved over the new version of the Main page I worked on, cleaning up the source a ton using some templates. There's empty space in the center cell for the GUIDES section (see To-Do talk page, now linked in lower-right main page cell). Any suggestions or whatnot, please discuss!! [[User:BenWo|BenWo]] ([[User talk:BenWo|talk]]) 13:54, 25 May 2014 (CEST)

=== Top right box ===

* Link to the list of News (Friday Facts, Random Ramblings...)

=== Left box ===

* What it is (short explanation)

* [[Let's play]] page
http://www.factorioforums.com/forum/viewtopic.php?f=19&t=829

* Beginners Guide
(Sub-pages:
** Joseki (Good starting moves)
** The first day
** Exploring the map
** Electric Power
** Crafting
** Research
** Red&Green Potion
** Weapons&Armour
** Blue Potion
** Car
** Logistic Bots
** Train
** And bejond?)

=== Center + right Box ===

(Items, Networks, Special, Concept) is one big point in the center.

=== Left lower box ===

* FAQ

* Map-Editor
** Convert map to Scenario

* Game-Options
** Key-Defaults

* Contributing
(
** For this wiki
** Link to mods
)

...

== "Before you play" ==

The main page has "Console" under "Before you play". I don't think it's appropriate for that section. --[[User:Glyph|Glyph]] ([[User talk:Glyph|talk]]) 15:27, 13 August 2014 (CEST)

: Fixed. You are allowed to make such changes. This is a wiki. :) [[User:Ssilk|Ssilk]] ([[User talk:Ssilk|talk]]) 23:40, 13 August 2014 (CEST)

:: Thanks! I am hesitant to edit the main page because I would start to move everything around and couldn't stop! --[[User:Glyph|Glyph]] ([[User talk:Glyph|talk]]) 09:55, 14 August 2014 (CEST)

::: There is the "restore previous version"-button. :) Currrently I think the amount of links to other pages has reached a limit, the lower, the better. [[User:Ssilk|Ssilk]] ([[User talk:Ssilk|talk]]) 19:39, 15 August 2014 (CEST)

== Contributors ==

Suggestion: Remove the contributors (currently only the translators) from the main page and move it to "Contributors"-page.

Anything against?
:Support - I indeed think this should not be on the main page, but also not on another page. A wiki is for people to work together, so everyone contributes to it, why only display a few names? [[User:TheWombatGuru|TheWombatGuru]] ([[User talk:TheWombatGuru|talk]]) 07:54, 29 August 2014 (CEST)
:: Indeed. I think removing the names is logical for a wiki, cause the changes can be seen in the history. I will put this into the forum, too and wait and if nobody has anything against I'll remove that... [[User:Ssilk|Ssilk]] ([[User talk:Ssilk|talk]]) 13:12, 31 August 2014 (CEST)
::: I made a change to this section, is this a good alternative? [[User:TheWombatGuru|TheWombatGuru]] ([[User talk:TheWombatGuru|talk]]) 00:14, 4 October 2014 (CEST)
:::: I think yes, but now I have a question — how is it works? And what should I do to insert local names of the languages to the list? E.g. Czech lang is "Чеська", English lang is "Англійська", French is "Французька", etc (by Ukrainian language). I was trying to use the new template in [[Main_Page/uk]] but the brackets after a language's self-name are empty... --[[User:Vitduo|Vitduo]] ([[User talk:Vitduo|talk]]) 16:16, 4 October 2014 (CEST)
::::: I saw you already figured out how, thanks for extending the template :) [[User:TheWombatGuru|TheWombatGuru]] ([[User talk:TheWombatGuru|talk]]) 16:35, 4 October 2014 (CEST)

== New "Around the game" introduced ==

I'm not so sure, if that was a good idea. My normal way would be to change it and then look at it in some days/weeks, but with more wikianers I could just ask. So maybe, this Main page gets a little bit to big now? If so, please make suggestions or change it. :) [[User:Ssilk|Ssilk]] ([[User talk:Ssilk|talk]]) 23:37, 18 October 2014 (CEST)
: I think it's good like this, good editing :) [[User:TheWombatGuru|TheWombatGuru]] ([[User talk:TheWombatGuru|talk]]) 00:50, 19 October 2014 (CEST)