Official Factorio Wiki - User contributions [en]

Debug mode

2023-05-31T14:48:10Z

Mithaldu:

{{Languages}}
[[File:debug_during_play.png|thumb|250px|right|Debug mode, with some of its features enabled.]]The ''debug mode'' is used mainly by developers and modders to analyze the running state of the game. It can be enabled to show detailed information about the game world. The default key to enable debug mode is {{keybinding|F5}}.

For example, one can:
* See the path the [[Enemies#Biters|biters]] are coming from and where they plan to target,
* See the position / coordinates of the cursor,
* See a grid-overlay for the [[map structure|tile]]s and [[Map_structure#Chunk|chunks]],
* See the blocks in a railway network,
* See additional non-game related information, such as Updates Per Second and FPS.

'''Note:''' In addition to this internal debugging tool there are also third-party debugging tools contributed by the community available on the [https://forums.factorio.com/viewforum.php?f=135 Factorio sub-forum for mod development tools].

== Activate the debug mode ==

There are 2 debug-levels:

* '''Always''' - This is the default mode, if no mode is active. Keep very few things active here.
* '''Debug''' - Toggled by pressing {{keybinding|F5}}. Allows to toggle the debug overlays.

== Configuring the debug mode ==

To configure the 2 modes, press {{keybinding|F4}}. This opens up a menu with many options. You can move this menu with the mouse, if it hides some interesting underlying thing. You can switch between 2 folders, which reflects the option for that debug-mode ("always", "debug"). The options are the same for each mode. Each mode can be configured to the user's liking, the different modes are only for convenience. A search function ({{Keybinding|ctrl|F}}) is available.

== List of debug-options and their function ==
{| class="wikitable"
|-
! Option !! Description
|-
| show-fps || Will show the current frames-per-second and updates per second, short <abbr title="Frames Per Second">FPS</abbr> and <abbr title="Updates Per Second">UPS</abbr>. Should be normally about 60.
|-
| show-clock || Shows a real time clock.
|-
| show-detailed-info ||
* Shows the cursor position in [[Map_structure#Tile|tiles]] (and subdivisions of that).
* Current resolution and zoom.
* How many objects are on the screen (painted by the graphic card).
* How many entities, chunks and paths are in the game and used.
|-
| show-time-usage ||
* Internal statistics about how long some calculations take, in milliseconds per [[Time#Ticks|tick]].
* Time is shown as average/min/max of the last 100 ticks, interval can be changed with /perf-avg-frames.
* Minimum values exclude zeroes (e.g. from ticks where no mod hooks were run).
* Overall calculation delays (some are parallel) must be under 16.6 ms to maintain normal framerate at 1x speed with 60 ticks per second.
* The Top section of metrics cover the wider game engines activities. The middle Update section relates to running the simulation for a tick. The bottom Map Generator section relates to the map generation activity.
|-
| show-entity-time-usage ||
|-
| show-gpu-time-usage ||
|-
| show-sprite-counts || The counts of each sprite rendered on screen.
|-
| show-lua-object-statistics ||
|-
| show-heat-buffer-info ||
|-
| show-multiplayer-waiting-icon || When in a multiplayer game: if the game is currently waiting for the server to process.
|-
| show-multiplayer-statistics || The latency information when in multiplayer.
|-
| show-multiplayer-selection-rectangles || Allows to view selection rectangles of other players in multiplayer.
|-
| show-debug-info-in-tooltips || Shows additional information in the tooltips of entities, items, recipes, tiles etc.
|-
| show-resistances-in-tooltips-always || Show entity resitances in all entity tooltips instead of just tooltips of enemy entities and entities with [[Prototype/EntityWithHealth#hide_resistances|hide_resistances]] set to false.
|-
| hide-mod-guis || Hides GUIs added by mods.
|-
| show-tile-grid || Shows the borders of the [[Map_structure#Tile|tiles]] and [[Map_structure#Chunk|chunks]].
|-
| show-blueprint-grid ||
|-
| show-collision-rectangles || Shows the collision boxes of each entity (red).
|-
| show-selection-rectangles || Shows the a blue box over each entity, if you hover over it, it will be selected.
|-
| show-render-rectangles || Shows the a pink box over each entity, if that is on your screen, the entity will be rendered.
|-
| show-sticker-boxes ||
|-
| show-entity-positions ||
|-
| show-entity-velocities ||
|-
| show-selected-entity-advanced-tiles || Shows on which advanced tiles (2×2 tiles) the entity is registered.
|-
| show-selected-input-transport-belts || Shows which entities input into the selected transport line.
|-
| show-paths || The calculated paths for the biters in different colors.
|-
| show-path-requests ||
|-
| show-next-waypoint-bb || Shows waypoints for biters (in green), nearly the same info as the next.
|-
| show-target || Shows the current target of the biters (red).
|-
| show-unit-group-info || Biter groups, which belong together (circles and lines belonging together)
|-
| show-unit-behavior-info ||
|-
| show-pathfinder-fringe ||
|-
| show-path-cache || The source-positions of a path and about the length (?)
|-
| show-path-cache-paths ||
|-
| show-rail-paths || Which path a train will follow.
|-
| show-rolling-stock-count || Shows inserter positions
|-
| show-rail-connections || Shows rail connections.
|-
| show-rail-joints ||
|-
| show-rail-segment-collision-boxes ||
|-
| show-train-stop-point || When a train slows down it shows the calculated point where it should halt
|-
| show-train-braking-distance || The distance a train will take to stop at its current speed
|-
| show-train-signals ||
|-
| show-train-repathing || Display a flying "repathed" text over a train whenever it repaths.
|-
| show-network-connected-entities || Displays the network-id of the electric network that a pole is connected to
|-
| show-circuit-network-numbers || Shows the number (and color) of circuit networks
|-
| show-energy-sources-networks || Which network-id an entity is connected to.
|-
| show-active-state || Inserters, fish, turrets are turned to passive, if not used; Red = inactive, Purple = inactive when enemies aren't around (turrets etc), Green = inactive when player isn't around (fish). Passive entities consume less CPU power.
|-
| show-wakeup-lists || When an entity is sleeping in another entity it shows which entities it's sleeping in.
|-
| show-transport-lines ||
|-
| show-transport-line-gaps ||
|-
| show-pollution-values || Shows the numeric pollution amount on each chunk.
|-
| show-active-entities-on-chunk-counts ||
Shows counts of active entities per chunk. They are divided into two categories:
* Blue = active when a player is around (e.g. fish)
* Green = active when enemies are around (e.g. turrets)
|-
| show-active-chunks || Shows in the map view, which chunks are "on", unmarked chunks are not calculated.
|-
| show-polluted-chunks || Shows which chunks have pollution.
|-
| hide-chart-tags || Hides map tags.
|-
| show-enemy-expansion-candidate-chunks || Where is space left to spread the brood?. Goes from red (nearly no space) to green (space to expand).
|-
| show-enemy-expansion-candidate-chunk-values || Which chunks the enemies will try to expand into.
|-
| show-bad-attack-chunks ||
|-
| show-tile-variations || Shows, which tile-variation (1, 2 or 4 tile sized) is painted for which area of the map. Quite confusing, zoom in to see the meaning.
|-
| show-raw-tile-transitions || Turns connected textures for land and water off, so the distinction can easily be made.
|-
| show-fluid-box-fluid-info || How much fluid is in a pipe/storage tank, shows flow of liquid in pipes.
|-
| show-environment-sound-info || Displays which sound of which entity is played and how loud.
|-
| show-environment-sound-area ||
|-
| show-selected-entity-audible-range ||
|-
| show-recently-played-sound-info ||
|-
| show-logistic-robot-targets ||
|-
| show-spidertron-movement ||
|-
| show-player-robots ||
|-
| show-fire-info ||
|-
| show-sticker-info ||
|-
| show-decorative-names ||
|-
| show-decorative-collision-rectangles ||
|-
| allow-increased-zoom ||
|-
| show-chunk-components ||
|-
| show-train-no-path-details || Chat shows extra info on pathfinder for no-pathing trains. [https://forums.factorio.com/viewtopic.php?p=567834#p567834]
|}

Tutorial:Modding tutorial

2023-05-31T14:28:36Z

Mithaldu:

These tutorials range from teaching the first steps of modding to in-depth explanations of individual mechanics:

* [[Tutorial:Modding tutorial/Gangsir|Modding tutorial/Gangsir]] — A simple modding tutorial that suits beginners well.
* [[Tutorial:Mod structure|Mod structure]] — More details on how mods need to be structured in order to be loaded by the game.
* [[Tutorial:Scripting|Scripting]] — A small tutorial that focuses on run-time scripting and provides some info on how to use the story script.
* [[Tutorial:Mod settings|Mod settings]] — A comprehensive tutorial about how to create and use mod settings.
* [[Tutorial:Localisation|Localisation]] — A tutorial about how to format and use localisation, which is how mods are translated.
* [[Tutorial:Inspecting a live mod|Inspecting a live mod]] — An annotated tour of a mod that is live on the mod portal right now.
* [[Tutorial:Mod changelog format|Mod changelog format]] — The formatting requirements for the mod changelog.txt file.
* [[Tutorial:Script interfaces|Script interfaces]] — A small tutorial about script interfaces ([http://lua-api.factorio.com/latest/LuaRemote.html LuaRemote]) and custom keyboard shortcuts.
* [https://togos.github.io/togos-example-noise-programs/ Noise Expressions] — A tutorial about generating terrain, complete with [https://mods.factorio.com/mod/togos-example-noise-programs example mod].
* [https://github.com/ClaudeMetz/UntitledGuiGuide/wiki Untitled GUI Guide] — A tutorial about building custom interfaces that also expands into more advanced parts of GUI modding.

=== Additional info ===
* [[Tutorial:Modding FAQ|Modding FAQ]]
* [[Prototype definitions|Prototype documentation]]
* [[Scenario system]] — Save-based mods ("soft mods") and their limitations
* [http://lua-api.factorio.com/latest/ Factorio API Documentation] — Documentation of the runtime api
* [https://lua-api.factorio.com/latest/Migrations.html Migrations guide] — All information about mod migrations
* [https://github.com/wube/factorio-data Factorio data github repository] — Tracks changes of the lua prototype definitions in Factorio in between releases.
<noinclude>{{Languages}}

=== Third-Party Tools ===

There is a wide variety of tools contributed by community members to help in mod development, such as plugins for IDEs to provide auto-completion, debuggers, as well as scripts to automate common tasks regarding translations or packaging.

* [https://forums.factorio.com/viewforum.php?f=135 Factorio sub-forum for mod development tools]

== See also ==
* [[Tutorials]]
* [[Modding]]
* [[:Category:Technical]] — Documentation of technical formats and API's not related to modding</noinclude>

Modding

2023-05-31T14:27:10Z

Mithaldu: /* Creating mods */

{{Languages}}
This page tells you how to download and install mods, and gives a quick overview of what you should keep in mind when creating a mod. For more detailed instructions on creating mods, you may view the [[Tutorial:Modding_tutorial| modding tutorial page]]. If you are looking for the modding API, check out the [http://lua-api.factorio.com/latest/ official Factorio Lua API documentation] website. If you wish to know where to install a mod which is in a zipped format, please read the instructions on the [[Application_directory|application directory]] page.

== Downloading & installing mods ==

You can download the mods from the following places:

* Mod portal (in-game)
* [https://mods.factorio.com/ Mod portal (website)]
* [https://forums.factorio.com/viewforum.php?f=14&sid=68de6ef9ee46dcd7566653335917752b Mod subforum]

=== Mod portal (in-game) ===

The "Mods" section of the main menu is the best way to get mods. It combines downloading & installing, checking installed mods for updates, and enabling/disabling installed mods.

=== Mod portal (website) ===

The [https://mods.factorio.com/ mod portal (website)] is the center of mod hosting, where authors upload mods, and you can find previous versions, and discussions. Mods come as ZIP files, installed by copying (not unzipping) into the "mods" directory in the [[Application_directory#User_Data_directory|user data directory]]. Verify a successful installation by viewing the "Mods" list through the main menu, in-game.

=== Mod subforum ===

Mod authors maintain threads in the official [https://forums.factorio.com/viewforum.php?f=14&sid=68de6ef9ee46dcd7566653335917752b mod subforum] to support their work. There may be experimental mods or updates here that aren't available on the main portal. They will be downloaded as ZIP files, either as forum "attachments", or with a link to a hosting site. These are installed the same way as mods downloaded from the portal.

=== Dependencies ===

Many mods use Factorio's base mod as their only dependency which you do not have to install separately. However, some mods may require you to install other mods for them to work and can also make suggestions for you to install other mods for them to extend their functionality.

==== Required dependency ====

When a mod you installed requires you to install another mod for it to work, the other mod, in this case, is a required dependency. The in-game mod portal automatically downloads required dependencies when downloading any mod.

==== Optional dependency ====

When a mod makes a suggestion to install another mod, but if it does not need that other mod for it to work, the other mod, in this case, is an optional dependency. You can install the optional dependencies which extend the functionality of a mod to enhance your gaming experience with the mod.

==== Incompatibility ====

The dependencies can also be used to declare a mod to be incompatible with other mods, which prevents them from being loaded together.

== Creating mods ==
: ''See also: [[Tutorial:Modding tutorial|Modding tutorial]]''

=== API documentation ===

* [[Prototype definitions|Prototype documentation]] — What prototypes can be added to the game, and what are their properties
* [http://lua-api.Factorio.com/latest Documentation of the runtime API] — Hook into events and change the world around the player.
* [[Tutorial:Mod structure|Mod structure]] — The basic structure of all mods
* [https://github.com/wube/factorio-data Factorio data github repository] — Tracks changes of the Lua prototype definitions in Factorio between releases.
* [[Data.raw]] — Lists the names and types of all built-in prototypes

=== Lua scripting ===

You need to use the Lua programming language (version 5.2.1) to create any mods in Factorio. The game's mod system injects your code into the startup and to the data construction stage of the game. You can use any text editor to write the code for your mod. Well-known text editors that offer syntax highlighting for Lua are Notepad++ and Sublime Text.

Useful resources for Lua:

* [http://lua-users.org/wiki/TutorialDirectory Lua tutorial]
* [https://www.lua.org/manual/5.2/ Lua reference manual]
* [https://repl.it/languages/lua Lua REPL] : A Lua read-eval-print-loop, essentially a sandbox.

=== Licensing ===

Every mod requires a license since Factorio '''v0.11'''. If a mod has no license, it is assumed to have a Creative Commons license — [http://creativecommons.org/licenses/by-nc/4.0 Attribution-Noncommercial 4.0 International (CC BY-NC 4.0)]. However, it is possible to purposely make the mod [https://choosealicense.com/licenses/unlicense/ unlicensed], to allow the code within it to be available to the public domain. The most popular distribution licenses for Factorio mods are the [https://choosealicense.com/licenses/mit/ MIT license] and the [https://choosealicense.com/licenses/gpl-3.0/ GPLv3] license.

Other useful legal links include:

* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=6202&p=48971#p48968 Forum post on allowed use of base-mod content]
* [http://www.factorio.com/terms-of-service Factorio terms of service]
* [https://choosealicense.com/licenses/ Choose a license]

=== Third-Party Tools ===

There is a wide variety of tools contributed by community members to help in mod development, such as plugins for IDEs to provide auto-completion, debuggers, as well as scripts to automate common tasks regarding translations or packaging.

* [https://forums.factorio.com/viewforum.php?f=135 Factorio sub-forum for mod development tools]

== See also ==
* [[:Category:Technical]] — Documentation of technical formats and API's not related to modding

Rich text

2023-05-27T13:48:41Z

Mithaldu: add an example of how to reach the utility sprites

{{Languages}}
Rich text formatting in allows the use of tags within most of the game's textboxes to change the visual formatting of text or to embed interactable images/entities. Predefined text tags are employed for this purpose.

== Tags ==

Tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations.
Ctrl+alt clicking the map or ground will automatically insert a gps tag and post it into [[console|chat]].

Shift clicking most things with the console open will insert a tag for that thing into chat. The chat and many other textboxes in the game have a button on the right edge that opens an icon selector. This can be used to easily insert rich text tags of recipes, items, fluids, virtual signals and entities into the textbox.

When used in chat, the tag image will be followed by a text description, except for the img tag.
Used elsewhere only the image is shown.

{| class="wikitable"
|-
! style="width:20%"| Syntax
! style="width:15%"| Example Input
! style="width:15%"| Example Result
! style="width:50%"| Description

|-
| [img=class/name] 
[img=class.name] 
[img=sprite-prototype-name]
| [img=item.iron-plate] 
[img=quantity-time] 
[img=utility/played_green]
| [[File:Iron_plate.png|28px]] 
[[File:Time_icon.png|28px]] 
[[File:Played green.png|28px]]
| Embeds only a small inline game graphic. The period format must be used in game save names. This tag uses [https://lua-api.factorio.com/latest/Concepts.html#SpritePath sprite paths]:
class is any of: item, entity, technology, recipe, item-group, fluid, tile, virtual-signal, achievement, equipment or utility.

name: see below

sprite-prototype-name is the [[Data.raw#sprite|internal-name]] of a [[Prototype/Sprite|sprite prototype]].

|-
| [item=name]
| [item=iron-plate]
| [[File:Iron_plate.png|28px]] [Item: Iron plate]
| name is the internal-name of the item

|-
| [entity=name]
| [entity=small-biter]
| [[File:Small_biter.png|28px]] [Entity: Small biter]
| name is the internal-name of the entity

|-
| [technology=name]
| [technology=logistics]
| [[File:Logistics_(research).png|28px]] [Technology: Logistics]
| name is the internal-name of the technology

|-
| [recipe=name]
| [recipe=basic-oil-processing]
| [[File:Basic_oil_processing.png|28px]] [Recipe: Basic oil processing]
| name is the internal-name of the recipe, usually the item name

|-
| [item-group=name]
| [item-group=combat]
| [[File:Item-group_military.png|28px]] [Item Group: Combat]
| name is any of: logistics, production, intermediate-products, combat, fluids or signals

|-
| [fluid=name]
| [fluid=water]
| [[File:Water.png|28px]] [Fluid: Water]
| name is the internal name of the fluid

|-
| [tile=name]
| [tile=grass-3]
| [[File:Grass_3.png|28px]] [Tile: Grass 3]
| name is the internal name of the tile, usually the lowercase name with hyphens replacing spaces as written from the map editor

|-
| [virtual-signal=name]
| [virtual-signal=signal-A]
| [[File:Signal-A.png|28px]] [Virtual Signal: Signal A]
| name is the word signal followed by either an uppercase letter, number, color, each, everything or anything

|-
| [achievement=name]
| [achievement=minions]
| [[File:Minions-achievement.png|28px]] [Achievement: Minions]
| name is the internal-name of the achievement, usually the lowercase name with hyphens replacing spaces

|-
| [gps=x,y]
[gps=x,y,surface]
| [gps=0,0]
| [[File:Map.png|28px]] [Location: 0,0]
| Embeds a map location and marks the location on the map of other players.
x is the x point coordinate 
y is the y point coordinate 
surface is the current surface. Is only added if the player Ctrl+alt clicks on a surface that is not the default surface. When the player is on another surface than surface, clicking the tag does nothing. Mods must handle this case with [https://lua-api.factorio.com/latest/events.html#on_player_clicked_gps_tag on_player_clicked_gps_tag]
|-
| [special-item=blueprint_string]
|
| [[File:Blueprint.png|28px]] [Blueprint]
| Embeds a blueprint. Players can get a blueprint item by clicking the icon.
blueprint_string is the blueprint string of a blueprint, deconstruction planner or upgrade planners

|-
| [armor=player]
| [armor=Player]
| [[File:Power_armor_MK2.png|28px]] [Armor: Player]
| Embeds the armor of a player. Allows other players to see the equipment installed.
player is the name of the player

|-
| [train=number]
| [train=93]
| [[File:Locomotive.png|28px]] [Train: 2]
| Embeds a reference to a train. Clicking the icon will open the train GUI for that train.
number is the internal unit number of the train

|-
| [train-stop=number]
| [train-stop=100]
| [[File:Train_stop.png|28px]] [Train Stop: Trangar]
| Embeds a reference to a train stop. Clicking the icon will open the GUI for that train stop.
number is the internal unit number of the train stop

|-
| [tooltip=text,tooltip locale key]
| [tooltip=Hover to see "Iron plate",item-name.iron-plate]
| [[File:Custom-tag-icon.png|28px]] Hover to see "Iron plate"
| Shows the given text with a tooltip that is specified with a [[Tutorial:Localisation#Localising_simple_strings|locale key]].

|}

== Text modifiers ==
[[File:Fonts.png|right|thumbnail|100px|Different fonts displayed in-game. (Click to enlarge.)]]

The color and font of text can be changed

{| class="wikitable"
|-
! style="width:20%"| Syntax
! style="width:15%"| Example Input
! style="width:15%"| Example Result
! style="width:50%"| Description
|-
| [color=rgb]...[/color] 
[color=#rrggbb]...[/color] 
[color=#aarrggbb]...[/color] 
[color=rgb]...[.color] 
[color=#rrggbb]...[.color] 
[color=#aarrggbb]...[.color]
| [color=red]Red[/color] text 
[color=1,0,0]Red[/color] text 
[color=255,0,0]Red[/color] text 
[color=#ff0000]Red[/color] text
| Red text
| rgb is a comma separated RGB color ranging from 0 to 1 or 0 to 255, or a color name
Available colors: default, red, green, blue, orange, yellow, pink, purple, white, black, gray, brown, cyan, acid.
|-
| [font=font-name]...[/font] 
[font=font-name]...[.font]
| [font=default-bold]Bold text[/font]
| Bold text
| font-name is the name of the [[Data.raw#font|Factorio font]] to render
|}

== See also ==
* [[Console]]
* [[Data.raw]] for the list of internal names of recipes, technologies, fluids, etc.

File:Played green.png

2023-05-27T13:47:55Z

Mithaldu:

Enemies

2017-08-19T11:35:24Z

Mithaldu: linkify first instances of damage and resistance

{{Languages}}
'''Enemies''' are creatures that want to harm the player. They normally come from spawners and begin on the enemy force. There are three types of enemies: Biters, Spitters and Worms. Each of these types comes in four stages of growth and thus strength.

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

==Creatures==
===Biters===
Biters are one of two main antagonists in the game. They are the native inhabitants of the extraterrestrial world and commonly live peacefully with worms and spitters.
Biters are arthropods living in organic nests. They come in four sizes: small, medium, big and behemoth. In the beginning of each freeplay game there will only be the small ones, with increasing [[pollution]] they will become bigger, related to the enemy's [[#Evolution|evolution]].
Biters are attracted by and enraged by pollution and will attempt to destroy its sources. They prefer to attack the player character, [[turret]]s and [[radar]]s and will stop searching for pollution if they can see and attack any of those. Biters deal physical [[damage]].

{| class="wikitable"
|-
! Picture !! Name !! Info
|-
| [[File:SmallBiter-anim.gif]] || Small Biter
| Weakest of biters, can be easily killed with a pistol.
* Health: 15
* Damage: 7
* Damage Type: Physical
|-
| [[File:MediumBiter-anim.gif]] || Medium Biter
| Stronger and slower than the small biter. Can pose a problem for and even kill weaker players.
* Health: 75
* Damage: 15
* Damage Type: Physical

[[Resistances]]:
*Explosion: 0/10%
*Physical: 4/10%
|-
| [[File:BigBiter-anim.gif]] || Big Biter
| Very resistant and dangerous, nearly immune to gunfire. Can attack through walls and hit objects directly behind them.
* Health: 375
* Damage: 30
* Damage Type: Physical

Resistances:
*Explosion: 0/10%
*Physical: 8/10%
|-
| [[File:BehemothBiter-anim.gif]] || Behemoth Biter
| Very resistant and dangerous, nearly immune to gunfire. Can attack through walls and hit objects directly behind them.
* Health: 3000
* Damage: 90
* Damage Type: Physical

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

|}

====Combat====
The biter class enemy will likely be the most common threat to a player's factory. While any attack can catch an undefended factory off guard, most players will be able to handle attacks from small biters with relative ease. Medium biters often pose a much greater threat due to their heavy armor. Big biters are another step in this direction and can come as another nasty shock to any player not familiar with their world's evolution level. Behemoth biters are a big threat to any factory and serve as the Player's prime incentive to avoid excess pollution. However, Biters of any size can be managed by static defense, though some of the larger waves can be overwhelming.

Biters come fairly early to attack a factory that produces large amounts of pollution, as pollution will attract an attack. Once the pollution cloud reaches a nest, the player can expect biters to be showing up shortly. The attack group will be focused on destroying the source of the pollution, but will change targets as soon as one appears of higher priority, typically by level of pollution, though they target the player or static defense first and foremost. Biters also have the ability to find their way around a [[defense]], to a degree. This can be used to partially control the movement of the biters allowing turrets to damage them for a longer time, but requires the "bait" of this trap be left open. Biters aren't always willing to fall for the bait. Some biters will choose the most direct route and will attack the walls of the trap regardless making them less predictable and more dangerous.

===Spitters===
[[Spitters]] are much like [[Biters]]. The only difference, besides their appearance, is that they only have a ranged attack. They spit at any opponents (e.g. players) with an acid projectile that can neither be dodged nor deal damage to anything else than the original target. Commonly the acid resistance of buildings (like a [[turret]]) and [[armor]] is much lower than its physical resistance. Because of this Spitters deal more average damage than Biters. Their behavior and sizes are very similar to the Biters, except their health and resistances.

{| class="wikitable"
|-
! Picture !! Name !! Info
|-
| [[File:SmallSpitter.png]] || Small Spitter
| Weakest of spitters. Easy to kill with any weapon, but attacks at range.
* Health: 10
* Damage: 10
* Damage Type: Acid
|-
| [[File:MediumSpitter.jpg|200x200px]] || Medium Spitter
| Stronger and slower than the smaller version. Can pose a problem for and even kill weaker players. Attacks at range, making it dangerous for [[turret]]s.
* Health: 50
* Damage: 20
* Damage Type: Acid

Resistances:
*Explosion: 0/10%
|-
| [[File:BigSpitter.png]] || Big Spitter
| An even bulkier spitter and so can take more damage. Attacks at range, making it dangerous for [[turret]]s and the player.
* Health: 200
* Damage: 30
* Damage Type: Acid

Resistances:
*Explosion: 0/15%
|-
| [[File:BehemothSpitter.jpg|200x200px]] || Behemoth Spitter
| The bulkiest of the spitters and so can take even more damage. Attacks at range, making it dangerous for [[turret]]s and the player.
* Health: 1500
* Damage: 50
* Damage Type: Acid

Resistances:
*Explosion: 0/30%
|}

===Worms===

The Worms are natural allies of Biters and Spitters and will attack the player if they get close enough. They act like static [[turret]]s and will not follow you, they will instead use their much greater range, in comparison to other enemies, to inflict damage without leaving the nest. However, their static nature does render them more vulnerable to certain attacks.

Like any other enemy, worms come in 3 sizes, their power increasing with size. Unlike Biters and Spitters, Big and Medium Worms can be created directly after start of a new game, and will not always spawn near [[Enemies#Spawners|spawners]]. Their appearance is not dependent on time, however their appearance frequency can be modified by distance from the initial player spawn point, with greater distance yielding bigger/more worms.

{| class="wikitable"
|-
! Picture !! Name !! Description
|-
| [[File:SmallWorm.png]] || Small Worm
| A weak worm. Still not easy to kill though.
* Health: 200
* Damage: 25
* Damage Type: Acid
|-
| [[File:MediumWorm.png]] || Medium Worm
| Medium worms are very dangerous to even more advanced players. They should be handled with care.
* Health: 400
* Damage: 40
* Damage Type: Acid

Resistances:
*Explosion: 5/15%
*Physical: 5/0%
*Fire: 2/50%
|-
| [[File:BigWorm.png]] || Big Worm
| Big worms are the most powerful enemy in Factorio. They deal a high damage and are almost immune to common gunfire of any sort.
* Health: 750
* Damage: 50
* Damage Type: Acid

Resistances:
*Explosion: 10/30%
*Physical: 10/0%
*Fire: 3/70%

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

[http://www.factorioforums.com/forum/viewtopic.php?f=23&t=6454 Big Worms Now Show Up In Early Game]

==Spawners==

The homes of biters and spitters. While spawners themselves are generally defenseless (Unless a worm is nearby), the enemies they release overtime effectively serve as a form of guards to distract the player and any nearby turrets. If a group of enemies of the same variety is given the opportunity, they will automatically combine into a new spawner, expanding enemy bases.

Spawners exposed to pollution will use it to evolve the enemies they spawn, which may also result in an attack.
Further away from the starting location the chances that stronger enemies spawn is higher. This is controlled by the <code>spawn_shift</code>; the higher the value of it, the higher the probability that stronger enemies spawn.

Spawners are effectively 'bullet sponges' capable of absorbing a large amount of damage. Explosives, shotguns, flamethrowers, and tanks are effective weapons against spawners.

Spawners are the only place to acquire alien artifacts, which are needed to create alien science packs, which in turn are needed to research late-game technologies. As of 0.15, alien artifacts were removed, meaning it is only beneficial to destroy spawners to clear out space or prevent incoming attacks.

{| class="wikitable"
|-
! Picture !! Name
|-
| [[File:Biternest-anim.gif]] || Biter's Nest
|
* Health: 350

Resistances:
*Explosion: 5/15%
*Physical: 2/0%
|-
| [[File:Spitternest.gif]] || Spitter's Nest
|
* Health: 350

Resistances:
*Explosion: 5/15%
*Physical: 2/0%
|}

===Expansions===
Every 4-60 minutes, a group of 5-20 biters will leave their base to create a new base. This group will search for a suitable spot that's at least 3 chunks and at most 7 chunks away from existing biter bases.
Once they have found a suitable spot the group of biters dies and forms a new base. This new base will first be very small (about one spawner and a few worms) but will get some additional spawners within a small area as time passes.

==Evolution==
[[File:Evolution Biters.png|thumb|right|400px|Spawn chances of biters from biter spawners by evolution factor. See the table below for exact values.]]
[[File:Evolution Spitters.png|thumb|right|400px|Spawn chances of spitters from spitter spawners by evolution factor. See the table below for exact values.]]
The evolution factor is a global variable that determines what kind of biters will be spawned. You can check the variable in the dev console via the following command:

/evolution

It goes from 0 (not evolved at all) to 1 (maximal evolution). At the moment the evolution factor can only increase. The evolution factor is increased by three kinds of events:

=== Methods of increasing ===

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

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

The current (as of 0.14.22) default settings are:

Percentual Increases:

{| class="wikitable"
!Source per
!Variable in <code>enemy_evolution</code>
!Percent increase
|-
| Tick || <code>time_factor</code> || 0.0004%
|-
| 1000 Pollution Units || <code>pollution_factor</code> || 0.0015%
|-
| Destroyed enemy spawner || <code>destroy_factor</code> || 0.2%
|}

Pollution production is the total pollution produced by [[Pollution_Production#Polluters|buildings]] per tick, not the pollution spreading on the map, so it is not reduced by trees or other absorbers.
e.g. : 15 burner mining drills produce 150 pollution per second, raising the evolution factor by 0,00000225 per tick.

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

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

=== Spawn chances by evolution factor ===
{| class="wikitable" style="float:left; margin-right:1em"
! !!colspan="4"| Biter's Nest
|-
!style="width:4em" | Factor
!style="width:5em" | Small Biter
!style="width:5em" | Medium Biter
!style="width:5em" | Big Biter
!style="width:5em" | Behemoth Biter
|-
|0 ||100.0% || || ||
|-
|0.05 ||100.0% || || ||
|-
|0.1 ||100.0% || || ||
|-
|0.15 ||100.0% || || ||
|-
|0.2 ||100.0% || || ||
|-
|0.25 ||100.0% || || ||
|-
|0.3 ||100.0% || || ||
|-
|0.35 ||71.25% ||28.75% || ||
|-
|0.4 ||50.0% ||50.0% || ||
|-
|0.45 ||33.75% ||66.25% || ||
|-
|0.5 ||20.0% ||80.0% || ||
|-
|0.55 ||7.6% ||79.8% ||12.6% ||
|-
|0.6 || ||79.0% ||21.0% ||
|-
|0.65 || ||62.5% ||37.5% ||
|-
|0.7 || ||38.25% ||61.75% ||
|-
|0.75 || ||33.5% ||66.5% ||
|-
|0.8 || ||29.5% ||70.5% ||
|-
|0.85 || ||26.25% ||73.25% ||
|-
|0.9 || ||24.0% ||76.0% ||
|-
|0.95 || ||16.25% ||58.75% || 25%
|-
|1 || ||12.5% ||50.0% ||37.5%
|}

{| class="wikitable"
! !!colspan="5"| Spitter's Nest
|-
!style="width:4em" | Factor
!style="width:5em" | Small Biter
!style="width:5em" | Small Spitter
!style="width:5em" | Medium Spitter
!style="width:5em" | Big Spitter
!style="width:5em" | Behemoth Spitter
|-
|0 ||100.0% || || || ||
|-
|0.05 ||100.0% || || || ||
|-
|0.1 ||100.0% || || || ||
|-
|0.15 ||100.0% || || || ||
|-
|0.2 ||100.0% || || || ||
|-
|0.25 ||100.0% || || || ||
|-
|0.3 ||41.25% ||58.75% || || ||
|-
|0.35 || ||100.0% || || ||
|-
|0.4 || ||100.0% || || ||
|-
|0.45 || ||100.0% || || ||
|-
|0.5 || ||100.0% || || ||
|-
|0.55 || ||66.0% ||11.5% ||22.5% ||
|-
|0.6 || ||39.5% ||39.5% ||21.0% ||
|-
|0.65 || ||17.5% ||53.75% ||28.75% ||
|-
|0.7 || || ||65.0% ||35.0% ||
|-
|0.75 || || ||55.00% ||45.0% ||
|-
|0.8 || || ||45.0% ||55.0% ||
|-
|0.85 || || ||35.0% ||65.0% ||
|-
|0.9 || || ||23.75% ||76.25% ||
|-
|0.95 || || ||16.25% ||58.75% ||25.0%
|-
|1 || || ||12.5% ||50.0% ||37.5%
|}

== History ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== See also ==

Resistance

2017-08-19T11:34:32Z

Mithaldu: redirect Resistance directly to Damage#Resistance

#REDIRECT [[Damage#Resistance]]

Resistances

2017-08-19T11:34:09Z

Mithaldu: redirect Resistances directly to Damage#Resistance

#REDIRECT [[Damage#Resistance]]

Logistic network

2017-02-18T21:13:50Z

Mithaldu: /* Priorities of robots */

{{Languages}}

[[File:RoboTrainStation.gif|thumb|632x562px|right|''This gif shows how robots can load or unload chests in a train station. The top track is for loading; and there are [[Requester chest]]s on both sides. The requested items are then filled into the wagons. The second track is the unloading track, the delivered items are filled into [[Active Provider chest]]s and then put into the [[Storage chest]]s at the very top and at the center. At the bottom the incoming ores from both sides are moved into [[Active Provider chest]]s; and then put into the requester chests at the top track.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed.]]

A [[Logistic network]] (LogNet) is a series of different chests and [[Logistic robot]]s all covered by one or more [[Roboport]]s.

Depending on the type and configuration of the chests and area of the [[Robotic network]] the robots will transport items between these chests as a power-hungry alternative to moving items manually, or by [[Transport network|belts]] or [[Railway network]]. However, robots offer much higher mobility, since they can fly over obstacles.

The player character can also act as [[Requester chest]] in the [[Logistic network]] with the correct researches, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots]], they can configure an amount of Items; and [[Logistic robot]]s will start to move the specified [[Items]] from the network to the character's inventory.

Do not mix up LogNet and [[Circuit network]]. They share common components, but are otherwise disconnected and do not exchange any information. Also, do not mix up logistic network with construction network or combinations of the two called [[Robotic network]].

== Achievements ==
{{Main|Achievements}}
The logistic network is directly connected to the following achievements:
; Logistic network embargo
: Win the game without building [[active provider chest]] and [[requester chest]].
; You've got a package
: Supply the player by [[logistic robot]].
; Delivery service
: Supply the player with 10k items delivered by logistic robots.

== Items ==
{| class="wikitable"
| {{imagelink|roboport|Roboport}} || Centre of the [[Robotic network]] in which the [[Robots]] can move and with its coverage forming the logistic network.
|-
| {{imagelink|Logistic-robot|Logistic robot}} || Moves items between Logistic Chests. (*)
|-
| {{imagelink|Provider-chest|Active Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network. (**)
|-
| {{imagelink|Logistic-chest-passive-provider|Passive Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network passively. (**)
|-
| {{imagelink|storage-chest|Storage chest}} || Logistic Chest: Stores [[Items]] currently not requested. Supplies the contained items to the Logistic network. (**)
|-
| {{imagelink|Requester-chest|Requester chest}} || Logistic Chest: Will be filled by [[Logistic robot]]s until the configured amount is reached, or the chest becomes full. Can request multiple different types of items. (**)
|}

(*) At the beginning each robot can carry only 1 [[Items|item]]. This amount can be increased by researching [[Logistic robot cargo]].

(**) Logistic chests are also usable for a [[Circuit network]] by using wires, like [[red wire]] or [[green wire]].

== Use ==

To start with, just use passive provider- and requester chests. Place the passive provider chests at the output [[inserters]] of [[assembling machine]]s and requester chests at the input (let them request the needed items). Place a [[Roboport]], which covers these chests with the inner orange area. Place some logistic bots. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item either with the [[Storage/Stack#Stack limitation|stack limitation]]-feature.

Logistic network is very capable for creating more and more complex items in a relatively small factory-area. Low complexity and high volume activities over longer distances (like smelting) can (and should) be left using belts or railway network.

The basic thing needed are [[Roboport]]s. When placing the port and hover over it, notice an orange and a larger green area.

* The orange zone is the Logistic Network area. This is also the maximum distance for connecting two roboports.
* The green zone is the Construction area.

''For more info on the specifics of how [[roboport]]s work, check the page dedicated to them.''

=== Expand the logistic zone ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, as described above. To prevent roboports from linking, the Player needs to build them far enough away from each other so that the orange zones don't touch.

Bots do not fly from one network into another, unless requiring a recharge. Robots will never "nest" in a different network.

=== Losing bots ===

Logistics robots are a priority target of biters, and will prioritize attacking them over many objects in the vicinity of the robots. Destroyed robots will not be replaced, unless automatic control of the robot creation system is used.

Bots are not destroyed when running out of energy, but will be reduced to 20% of their speed, which gives them the chance to recharge eventually and a chance for the player to notice the problem.

Pay attention to robotic networks which form some kind of U-shape (where the shortest way between two chests goes over an uncovered area): if a bot runs out of charge in this area, and cannot return fast enough to a roboport, the bot will be significantly slowed and as a result the logistics network will frequently slow down, with large groups of bots slowly flying over the uncovered area.

Robots may run out of charge on longer journeys. When the charging-queue for the bots gets too long, the bots (and their loads) will slow down. Generally, a roboport can charge between 50 and 70 bots per min, 4 at a time, but are not very efficient at charging large queues of bots and can quickly become overworked. Place more roboports near the first one to share the load.

=== Negative numbers ===
It is possible to notice negative numbers on the right info panel when looking at network storage. Contrary to common belief, this is intended.

The logistic network numbers report items in provider and storage chests, ''minus the amount of items scheduled to be picked up by robots.'' When negative numbers are shown, it means that more items are being requested than are available in the network. There is a deficit. This can be a problem, or intended, depending on the player's choice. The negative value is just to explain why items aren't being delivered. For example, a deficit of 20 iron plates would look like this:

{{icon|iron plate|-20}}

=== Receiving more items than requested ===

The delivered number of items in the requester chest can be higher than requested. This depends from the [[Logistic robot cargo]]-bonus you have researched, since bots will always take as much as they can carry if an unlimited amount is available.

== Priorities of robots ==

This overview reflects the priorities in which order the chests are filled/emptied.

The logistic network looks for orders by the chests in this order:

* A ''requested'' item is first looked up in the active provider chests, then in the storage chests, then the passive provider chests. So, the active provider chests are emptied first, then the storage chests, then the passive provider chests.
* If robots are free and there is space left in storage chests, and there are unrequested items in an active provider chests, the items are moved from active provider to a storage chest.
* For the storage chests, the bots search for one storage which has the same item already. If that can't be found, they choose the first storage chest with a free slot from the list, which is sorted by the order they were built in. [https://www.reddit.com/r/factorio/comments/5udwkd/hey_devs_this_is_the_one_thing_that_really_bugs/ddwbr94/] This is to avoid having storage chests with different items inside, allowing greater organisation.

Storage chests will be filled with items from active provider chests, and construction robots that have had their orders cancelled while they were carrying items.

=== Order of movement ===
The bots fulfill '''all requests with the same priority'''. The algorithm looks for the next free robot, then the next request in the queue and after giving orders to the robot, this request is put at the end of the queue, so that first all other requests are done.

=== Distance ===
When choosing between chests of equal priority, bots will always choose the closest one. [https://forums.factorio.com/viewtopic.php?f=6&t=40329&p=238918#p238901] This is however only true when an item is being requested, not when an item is sent away. [https://gfycat.com/HatefulUnlawfulErmine] In the case of items being sent into the logistics network distance does not matter, and the rules laid out above matter instead.

== See also ==
* [[Robotic network]]
* [[Robots]]
* [[Transport]]
* [[Roboport]]
* [[Logistic robot]]
* [[Construction robot]]

[[Category:Networks]]

Logistic network

2017-02-16T17:32:36Z

Mithaldu: /* Distance */

{{Languages}}

[[File:RoboTrainStation.gif|thumb|632x562px|right|''This gif shows how robots can load or unload chests in a train station. The top track is for loading; and there are [[Requester chest]]s on both sides. The requested items are then filled into the wagons. The second track is the unloading track, the delivered items are filled into [[Active Provider chest]]s and then put into the [[Storage chest]]s at the very top and at the center. At the bottom the incoming ores from both sides are moved into [[Active Provider chest]]s; and then put into the requester chests at the top track.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed.]]

A [[Logistic network]] (LogNet) is a series of different chests and [[Logistic robot]]s all covered by one or more [[Roboport]]s.

Depending on the type and configuration of the chests and area of the [[Robotic network]] the robots will transport items between these chests as a power-hungry alternative to moving items manually, or by [[Transport network|belts]] or [[Railway network]]. However, robots offer much higher mobility, since they can fly over obstacles.

The player character can also act as [[Requester chest]] in the [[Logistic network]] with the correct researches, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots]], they can configure an amount of Items; and [[Logistic robot]]s will start to move the specified [[Items]] from the network to the character's inventory.

Do not mix up LogNet and [[Circuit network]]. They share common components, but are otherwise disconnected and do not exchange any information. Also, do not mix up logistic network with construction network or combinations of the two called [[Robotic network]].

== Achievements ==
{{Main|Achievements}}
The logistic network is directly connected to the following achievements:
; Logistic network embargo
: Win the game without building [[active provider chest]] and [[requester chest]].
; You've got a package
: Supply the player by [[logistic robot]].
; Delivery service
: Supply the player with 10k items delivered by logistic robots.

== Items ==
{| class="wikitable"
| {{imagelink|roboport|Roboport}} || Centre of the [[Robotic network]] in which the [[Robots]] can move and with its coverage forming the logistic network.
|-
| {{imagelink|Logistic-robot|Logistic robot}} || Moves items between Logistic Chests. (*)
|-
| {{imagelink|Provider-chest|Active Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network. (**)
|-
| {{imagelink|Logistic-chest-passive-provider|Passive Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network passively. (**)
|-
| {{imagelink|storage-chest|Storage chest}} || Logistic Chest: Stores [[Items]] currently not requested. Supplies the contained items to the Logistic network. (**)
|-
| {{imagelink|Requester-chest|Requester chest}} || Logistic Chest: Will be filled by [[Logistic robot]]s until the configured amount is reached, or the chest becomes full. Can request multiple different types of items. (**)
|}

(*) At the beginning each robot can carry only 1 [[Items|item]]. This amount can be increased by researching [[Logistic robot cargo]].

(**) Logistic chests are also usable for a [[Circuit network]] by using wires, like [[red wire]] or [[green wire]].

== Use ==

To start with, just use passive provider- and requester chests. Place the passive provider chests at the output [[inserters]] of [[assembling machine]]s and requester chests at the input (let them request the needed items). Place a [[Roboport]], which covers these chests with the inner orange area. Place some logistic bots. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item either with the [[Storage/Stack#Stack limitation|stack limitation]]-feature.

Logistic network is very capable for creating more and more complex items in a relatively small factory-area. Low complexity and high volume activities over longer distances (like smelting) can (and should) be left using belts or railway network.

The basic thing needed are [[Roboport]]s. When placing the port and hover over it, notice an orange and a larger green area.

* The orange zone is the Logistic Network area. This is also the maximum distance for connecting two roboports.
* The green zone is the Construction area.

''For more info on the specifics of how [[roboport]]s work, check the page dedicated to them.''

=== Expand the logistic zone ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, as described above. To prevent roboports from linking, the Player needs to build them far enough away from each other so that the orange zones don't touch.

Bots do not fly from one network into another, unless requiring a recharge. Robots will never "nest" in a different network.

=== Losing bots ===

Logistics robots are a priority target of biters, and will prioritize attacking them over many objects in the vicinity of the robots. Destroyed robots will not be replaced, unless automatic control of the robot creation system is used.

Bots are not destroyed when running out of energy, but will be reduced to 20% of their speed, which gives them the chance to recharge eventually and a chance for the player to notice the problem.

Pay attention to robotic networks which form some kind of U-shape (where the shortest way between two chests goes over an uncovered area): if a bot runs out of charge in this area, and cannot return fast enough to a roboport, the bot will be significantly slowed and as a result the logistics network will frequently slow down, with large groups of bots slowly flying over the uncovered area.

Robots may run out of charge on longer journeys. When the charging-queue for the bots gets too long, the bots (and their loads) will slow down. Generally, a roboport can charge between 50 and 70 bots per min, 4 at a time, but are not very efficient at charging large queues of bots and can quickly become overworked. Place more roboports near the first one to share the load.

=== Negative numbers ===
It is possible to notice negative numbers on the right info panel when looking at network storage. Contrary to common belief, this is intended.

The logistic network numbers report items in provider and storage chests, ''minus the amount of items scheduled to be picked up by robots.'' When negative numbers are shown, it means that more items are being requested than are available in the network. There is a deficit. This can be a problem, or intended, depending on the player's choice. The negative value is just to explain why items aren't being delivered. For example, a deficit of 20 iron plates would look like this:

{{icon|iron plate|-20}}

=== Receiving more items than requested ===

The delivered number of items in the requester chest can be higher than requested. This depends from the [[Logistic robot cargo]]-bonus you have researched, since bots will always take as much as they can carry if an unlimited amount is available.

== Priorities of robots ==

This overview reflects the priorities in which order the chests are filled/emptied.

The logistic network looks for orders by the chests in this order:

* A ''requested'' item is first looked up in the active provider chests, then in the storage chests, then the passive provider chests. So, the active provider chests are emptied first, then the storage chests, then the passive provider chests.
* If robots are free and there is space left in storage chests, and there are unrequested items in an active provider chests, the items are moved from active provider to a storage chest.
* For the storage chests, the bots search for one storage which has the same item already. If that can't be found, they begin using a new storage chest. This is to avoid having storage chests with different items inside, allowing greater organisation.

Storage chests will be filled with items from active provider chests, and construction robots that have had their orders cancelled while they were carrying items.

=== Order of movement ===
The bots fulfill '''all requests with the same priority'''. The algorithm looks for the next free robot, then the next request in the queue and after giving orders to the robot, this request is put at the end of the queue, so that first all other requests are done.

=== Distance ===
When choosing between chests of equal priority, bots will always choose the closest one. [https://forums.factorio.com/viewtopic.php?f=6&t=40329&p=238918#p238901] This is however only true when an item is being requested, not when an item is sent away. [https://gfycat.com/HatefulUnlawfulErmine]

== See also ==
* [[Robotic network]]
* [[Robots]]
* [[Transport]]
* [[Roboport]]
* [[Logistic robot]]
* [[Construction robot]]

[[Category:Networks]]

Logistic network

2017-01-24T19:47:19Z

Mithaldu: /* Distance */ turns out i was being misinformed here

{{Languages}}

[[File:RoboTrainStation.gif|thumb|632x562px|right|''This gif shows how robots can load or unload chests in a train station. The top track is for loading; and there are [[Requester chest]]s on both sides. The requested items are then filled into the wagons. The second track is the unloading track, the delivered items are filled into [[Active Provider chest]]s and then put into the [[Storage chest]]s at the very top and at the center. At the bottom the incoming ores from both sides are moved into [[Active Provider chest]]s; and then put into the requester chests at the top track.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed.]]

A [[Logistic network]] (LogNet) is a series of different chests and [[Logistic robot]]s all covered by one or more [[Roboport]]s.

Depending on the type and configuration of the chests and area of the [[Robotic network]] the robots will transport items between these chests as a power-hungry alternative to moving items manually, or by [[Transport network|belts]] or [[Railway network]]. However, robots offer much higher mobility, since they can fly over obstacles.

The player character can also act as [[Requester chest]] in the [[Logistic network]] with the correct researches, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots]], they can configure an amount of Items; and [[Logistic robot]]s will start to move the specified [[Items]] from the network to the character's inventory.

Do not mix up LogNet and [[Circuit network]]. They share common components, but are otherwise disconnected and do not exchange any information. Also, do not mix up logistic network with construction network or combinations of the two called [[Robotic network]].

== Achievements ==
{{Main|Achievements}}
The logistic network is directly connected to the following achievements:
; Logistic network embargo
: Win the game without building [[active provider chest]] and [[requester chest]].
; You've got a package
: Supply the player by [[logistic robot]].
; Delivery service
: Supply the player with 10k items delivered by logistic robots.

== Items ==
{| class="wikitable"
| {{imagelink|roboport|Roboport}} || Centre of the [[Robotic network]] in which the [[Robots]] can move and with its coverage forming the logistic network.
|-
| {{imagelink|Logistic-robot|Logistic robot}} || Moves items between Logistic Chests. (*)
|-
| {{imagelink|Provider-chest|Active Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network. (**)
|-
| {{imagelink|Logistic-chest-passive-provider|Passive Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network passively. (**)
|-
| {{imagelink|storage-chest|Storage chest}} || Logistic Chest: Stores [[Items]] currently not requested. Supplies the contained items to the Logistic network. (**)
|-
| {{imagelink|Requester-chest|Requester chest}} || Logistic Chest: Will be filled by [[Logistic robot]]s until the configured amount is reached, or the chest becomes full. Can request multiple different types of items. (**)
|}

(*) At the beginning each robot can carry only 1 [[Items|item]]. This amount can be increased by researching [[Logistic robot cargo]].

(**) Logistic chests are also usable for a [[Circuit network]] by using wires, like [[red wire]] or [[green wire]].

== Use ==

To start with, just use passive provider- and requester chests. Place the passive provider chests at the output [[inserters]] of [[assembling machine]]s and requester chests at the input (let them request the needed items). Place a [[Roboport]], which covers these chests with the inner orange area. Place some logistic bots. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item either with the [[Storage/Stack#Stack limitation|stack limitation]]-feature.

Logistic network is very capable for creating more and more complex items in a relatively small factory-area. Low complexity and high volume activities over longer distances (like smelting) can (and should) be left using belts or railway network.

The basic thing needed are [[Roboport]]s. When placing the port and hover over it, notice an orange and a larger green area.

* The orange zone is the Logistic Network area. This is also the maximum distance for connecting two roboports.
* The green zone is the Construction area.

''For more info on the specifics of how [[roboport]]s work, check the page dedicated to them.''

=== Expand the logistic zone ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, as described above. To prevent roboports from linking, the Player needs to build them far enough away from each other so that the orange zones don't touch.

Bots do not fly from one network into another, unless requiring a recharge. Robots will never "nest" in a different network.

=== Losing bots ===

Logistics robots are a priority target of biters, and will prioritize attacking them over many objects in the vicinity of the robots. Destroyed robots will not be replaced, unless automatic control of the robot creation system is used.

Bots are not destroyed when running out of energy, but will be reduced to 20% of their speed, which gives them the chance to recharge eventually and a chance for the player to notice the problem.

Pay attention to robotic networks which form some kind of U-shape (where the shortest way between two chests goes over an uncovered area): if a bot runs out of charge in this area, and cannot return fast enough to a roboport, the bot will be significantly slowed and as a result the logistics network will frequently slow down, with large groups of bots slowly flying over the uncovered area.

Robots may run out of charge on longer journeys. When the charging-queue for the bots gets too long, the bots (and their loads) will slow down. Generally, a roboport can charge between 50 and 70 bots per min, 4 at a time, but are not very efficient at charging large queues of bots and can quickly become overworked. Place more roboports near the first one to share the load.

=== Negative numbers ===
It is possible to notice negative numbers on the right info panel when looking at network storage. Contrary to common belief, this is intended.

The logistic network numbers report items in provider and storage chests, ''minus the amount of items scheduled to be picked up by robots.'' When negative numbers are shown, it means that more items are being requested than are available in the network. There is a deficit. This can be a problem, or intended, depending on the player's choice. The negative value is just to explain why items aren't being delivered. For example, a deficit of 20 iron plates would look like this:

{{icon|iron plate|-20}}

=== Receiving more items than requested ===

The delivered number of items in the requester chest can be higher than requested. This depends from the [[Logistic robot cargo]]-bonus you have researched, since bots will always take as much as they can carry if an unlimited amount is available.

== Priorities of robots ==

This overview reflects the priorities in which order the chests are filled/emptied.

The logistic network looks for orders by the chests in this order:

* A ''requested'' item is first looked up in the active provider chests, then in the storage chests, then the passive provider chests. So, the active provider chests are emptied first, then the storage chests, then the passive provider chests.
* If robots are free and there is space left in storage chests, and there are unrequested items in an active provider chests, the items are moved from active provider to a storage chest.
* For the storage chests, the bots search for one storage which has the same item already. If that can't be found, they begin using a new storage chest. This is to avoid having storage chests with different items inside, allowing greater organisation.

Storage chests will be filled with items from active provider chests, and construction robots that have had their orders cancelled while they were carrying items.

=== Order of movement ===
The bots fulfill '''all requests with the same priority'''. The algorithm looks for the next free robot, then the next request in the queue and after giving orders to the robot, this request is put at the end of the queue, so that first all other requests are done.

=== Distance ===
When choosing between chests of equal priority, bots will always choose the closest one. [https://forums.factorio.com/viewtopic.php?f=6&t=40329&p=238918#p238901]

== See also ==
* [[Robotic network]]
* [[Robots]]
* [[Transport]]
* [[Roboport]]
* [[Logistic robot]]
* [[Construction robot]]

[[Category:Networks]]

Logistic network

2017-01-24T18:10:06Z

Mithaldu: /* Priorities of robots */ orthography

{{Languages}}

[[File:RoboTrainStation.gif|thumb|632x562px|right|''This gif shows how robots can load or unload chests in a train station. The top track is for loading; and there are [[Requester chest]]s on both sides. The requested items are then filled into the wagons. The second track is the unloading track, the delivered items are filled into [[Active Provider chest]]s and then put into the [[Storage chest]]s at the very top and at the center. At the bottom the incoming ores from both sides are moved into [[Active Provider chest]]s; and then put into the requester chests at the top track.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed.]]

A [[Logistic network]] (LogNet) is a series of [[Logistic network/Chests|different chests]] and [[Logistic robot]]s all covered by one or more [[Roboport]]s.

Depending on the type and configuration of the chests and area of the [[Robotic network]] the robots will transport items between these chests as a power-hungry alternative to moving items manually, or by [[Transport network|belts]] or [[Railway network]]. However, robots offer much higher mobility, since they can fly over obstacles.

The player character can also act as [[Requester chest]] in the [[Logistic network]] with the correct researches, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots]], they can configure an amount of Items; and [[Logistic robot]]s will start to move the specified [[Items]] from the network to the character's inventory.

Do not mix up LogNet and [[Circuit network]]. They share common components, but are otherwise disconnected and do not exchange any information. Also, do not mix up logistic network with construction network or combinations of the two called [[Robotic network]].

== Achievements ==
{{Main|Achievements}}
The logistic network is directly connected to the following achievements:
; Logistic network embargo
: Win the game without building [[active provider chest]] and [[requester chest]].
; You've got a package
: Supply the player by [[logistic robot]].
; Delivery service
: Supply the player with 10k items delivered by logistic robots.

== Items ==
{| class="wikitable"
| {{imagelink|roboport|Roboport}} || Centre of the [[Robotic network]] in which the [[Robots]] can move and with its coverage forming the logistic network.
|-
| {{imagelink|Logistic-robot|Logistic robot}} || Moves items between Logistic Chests. (*)
|-
| {{imagelink|Provider-chest|Active Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network. (**)
|-
| {{imagelink|Logistic-chest-passive-provider|Passive Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network passively. (**)
|-
| {{imagelink|storage-chest|Storage chest}} || Logistic Chest: Stores [[Items]] currently not requested. Supplies the contained items to the Logistic network. (**)
|-
| {{imagelink|Requester-chest|Requester chest}} || Logistic Chest: Will be filled by [[Logistic robot]]s until the configured amount is reached, or the chest becomes full. Can request multiple different types of items. (**)
|}

(*) At the beginning each robot can carry only 1 [[Items|item]]. This amount can be increased by researching [[Logistic robot cargo]].

(**) Logistic chests are also usable for a [[Circuit network]] by using wires, like [[red wire]] or [[green wire]].

== Use ==

To start with, just use passive provider- and requester chests. Place the passive provider chests at the output [[inserters]] of [[assembling machine]]s and requester chests at the input (let them request the needed items). Place a [[Roboport]], which covers these chests with the inner orange area. Place some logistic bots. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item either with the [[Storage/Stack#Stack limitation|stack limitation]]-feature.

Logistic network is very capable for creating more and more complex items in a relatively small factory-area. Low complexity and high volume activities over longer distances (like smelting) can (and should) be left using belts or railway network.

The basic thing needed are [[Roboport]]s. When placing the port and hover over it, notice an orange and a larger green area.

* The orange zone is the Logistic Network area. This is also the maximum distance for connecting two roboports.
* The green zone is the Construction area.

''For more info on the specifics of how [[roboport]]s work, check the page dedicated to them.''

=== Expand the logistic zone ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, as described above. To prevent roboports from linking, the Player needs to build them far enough away from each other so that the orange zones don't touch.

Bots do not fly from one network into another, unless requiring a recharge. Robots will never "nest" in a different network.

=== Losing bots ===

Logistics robots are a priority target of biters, and will prioritize attacking them over many objects in the vicinity of the robots. Destroyed robots will not be replaced, unless automatic control of the robot creation system is used.

With v0.10.0, the bots are not longer destroyed when running out of energy, but will be reduced to 20% of their speed, which gives them the chance to recharge eventually and a chance for the player to notice the problem.

Pay attention to robotic networks which form some kind of U-shape (where the shortest way between two chests goes over an uncovered area): if a bot runs out of charge in this area, and cannot return fast enough to a roboport, the bot will be significantly slowed and as a result the logistics network will frequently slow down, with large groups of bots slowly flying over the uncovered area.

Robots may run out of charge on longer journeys. When the charging-queue for the bots gets too long, the bots (and their loads) will slow down. Generally, a roboport can charge between 50 and 70 bots per min, 4 at a time, but are not very efficient at charging large queues of bots and can quickly become overworked. Place more roboports near the first one to share the load.

=== Negative numbers ===
It is possible to notice negative numbers on the right info panel when looking at network storage. Contrary to common belief, this is intended.

The logistic network numbers report items in provider and storage chests, ''minus the amount of items scheduled to be picked up by robots.'' When negative numbers are shown, it means that more items are being requested than are available in the network. There is a deficit. This can be a problem, or intended, depending on the player's choice. The negative value is just to explain why items aren't being delivered. For example, a deficit of 20 iron plates would look like this:

{{icon|iron plate|-20}}

=== Receiving more items than requested ===

The delivered number of items in the requester chest can be higher than requested. This depends from the [[Logistic robot cargo]]-bonus you have researched, since bots will always take as much as they can carry if an unlimited amount is available.

== Priorities of robots ==

This overview reflects the priorities in which order the chests are filled/emptied.

The logistic network looks for orders by the chests in this order:

* A ''requested'' item is first looked up in the active provider chests, then in the storage chests, then the passive provider chests. So, the active provider chests are emptied first, then the storage chests, then the passive provider chests.
* If robots are free and there is space left in storage chests, and there are unrequested items in an active provider chests, the items are moved from active provider to a storage chest.
* For the storage chests, the bots search for one storage which has the same item already. If that can't be found, they begin using a new storage chest. This is to avoid having storage chests with different items inside, allowing greater organisation.

Storage chests will be filled with items from active provider chests, and construction robots that have had their orders cancelled while they were carrying items.

=== Order of movement ===
The bots fulfill '''all requests with the same priority'''. The algorithm looks for the next free robot, then the next request in the queue and after giving orders to the robot, this request is put at the end of the queue, so that first all other requests are done.

=== Distance ===
Bots ignore distances between chests and request targets. Bots will fulfill requests from the very first chest they find that contains the required items, which can be right next to the target, or in the furthest corner of the logistics area. No check or sorting for distance is done.

== See also ==
* [[Robotic network]]
* [[Robots]]
* [[Transport]]
* [[Roboport]]
* [[Logistic robot]]
* [[Construction robot]]

[[Category:Networks]]

Logistic network

2017-01-24T18:09:45Z

Mithaldu: /* Priorities of robots */ a section stating clearly that logi bots ignore distance

{{Languages}}

[[File:RoboTrainStation.gif|thumb|632x562px|right|''This gif shows how robots can load or unload chests in a train station. The top track is for loading; and there are [[Requester chest]]s on both sides. The requested items are then filled into the wagons. The second track is the unloading track, the delivered items are filled into [[Active Provider chest]]s and then put into the [[Storage chest]]s at the very top and at the center. At the bottom the incoming ores from both sides are moved into [[Active Provider chest]]s; and then put into the requester chests at the top track.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed.]]

A [[Logistic network]] (LogNet) is a series of [[Logistic network/Chests|different chests]] and [[Logistic robot]]s all covered by one or more [[Roboport]]s.

Depending on the type and configuration of the chests and area of the [[Robotic network]] the robots will transport items between these chests as a power-hungry alternative to moving items manually, or by [[Transport network|belts]] or [[Railway network]]. However, robots offer much higher mobility, since they can fly over obstacles.

The player character can also act as [[Requester chest]] in the [[Logistic network]] with the correct researches, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots]], they can configure an amount of Items; and [[Logistic robot]]s will start to move the specified [[Items]] from the network to the character's inventory.

Do not mix up LogNet and [[Circuit network]]. They share common components, but are otherwise disconnected and do not exchange any information. Also, do not mix up logistic network with construction network or combinations of the two called [[Robotic network]].

== Achievements ==
{{Main|Achievements}}
The logistic network is directly connected to the following achievements:
; Logistic network embargo
: Win the game without building [[active provider chest]] and [[requester chest]].
; You've got a package
: Supply the player by [[logistic robot]].
; Delivery service
: Supply the player with 10k items delivered by logistic robots.

== Items ==
{| class="wikitable"
| {{imagelink|roboport|Roboport}} || Centre of the [[Robotic network]] in which the [[Robots]] can move and with its coverage forming the logistic network.
|-
| {{imagelink|Logistic-robot|Logistic robot}} || Moves items between Logistic Chests. (*)
|-
| {{imagelink|Provider-chest|Active Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network. (**)
|-
| {{imagelink|Logistic-chest-passive-provider|Passive Provider chest}} || Logistic Chest: Supplies the contained items to the logistic network passively. (**)
|-
| {{imagelink|storage-chest|Storage chest}} || Logistic Chest: Stores [[Items]] currently not requested. Supplies the contained items to the Logistic network. (**)
|-
| {{imagelink|Requester-chest|Requester chest}} || Logistic Chest: Will be filled by [[Logistic robot]]s until the configured amount is reached, or the chest becomes full. Can request multiple different types of items. (**)
|}

(*) At the beginning each robot can carry only 1 [[Items|item]]. This amount can be increased by researching [[Logistic robot cargo]].

(**) Logistic chests are also usable for a [[Circuit network]] by using wires, like [[red wire]] or [[green wire]].

== Use ==

To start with, just use passive provider- and requester chests. Place the passive provider chests at the output [[inserters]] of [[assembling machine]]s and requester chests at the input (let them request the needed items). Place a [[Roboport]], which covers these chests with the inner orange area. Place some logistic bots. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item either with the [[Storage/Stack#Stack limitation|stack limitation]]-feature.

Logistic network is very capable for creating more and more complex items in a relatively small factory-area. Low complexity and high volume activities over longer distances (like smelting) can (and should) be left using belts or railway network.

The basic thing needed are [[Roboport]]s. When placing the port and hover over it, notice an orange and a larger green area.

* The orange zone is the Logistic Network area. This is also the maximum distance for connecting two roboports.
* The green zone is the Construction area.

''For more info on the specifics of how [[roboport]]s work, check the page dedicated to them.''

=== Expand the logistic zone ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, as described above. To prevent roboports from linking, the Player needs to build them far enough away from each other so that the orange zones don't touch.

Bots do not fly from one network into another, unless requiring a recharge. Robots will never "nest" in a different network.

=== Losing bots ===

Logistics robots are a priority target of biters, and will prioritize attacking them over many objects in the vicinity of the robots. Destroyed robots will not be replaced, unless automatic control of the robot creation system is used.

With v0.10.0, the bots are not longer destroyed when running out of energy, but will be reduced to 20% of their speed, which gives them the chance to recharge eventually and a chance for the player to notice the problem.

Pay attention to robotic networks which form some kind of U-shape (where the shortest way between two chests goes over an uncovered area): if a bot runs out of charge in this area, and cannot return fast enough to a roboport, the bot will be significantly slowed and as a result the logistics network will frequently slow down, with large groups of bots slowly flying over the uncovered area.

Robots may run out of charge on longer journeys. When the charging-queue for the bots gets too long, the bots (and their loads) will slow down. Generally, a roboport can charge between 50 and 70 bots per min, 4 at a time, but are not very efficient at charging large queues of bots and can quickly become overworked. Place more roboports near the first one to share the load.

=== Negative numbers ===
It is possible to notice negative numbers on the right info panel when looking at network storage. Contrary to common belief, this is intended.

The logistic network numbers report items in provider and storage chests, ''minus the amount of items scheduled to be picked up by robots.'' When negative numbers are shown, it means that more items are being requested than are available in the network. There is a deficit. This can be a problem, or intended, depending on the player's choice. The negative value is just to explain why items aren't being delivered. For example, a deficit of 20 iron plates would look like this:

{{icon|iron plate|-20}}

=== Receiving more items than requested ===

The delivered number of items in the requester chest can be higher than requested. This depends from the [[Logistic robot cargo]]-bonus you have researched, since bots will always take as much as they can carry if an unlimited amount is available.

== Priorities of robots ==

This overview reflects the priorities in which order the chests are filled/emptied.

The logistic network looks for orders by the chests in this order:

* A ''requested'' item is first looked up in the active provider chests, then in the storage chests, then the passive provider chests. So, the active provider chests are emptied first, then the storage chests, then the passive provider chests.
* If robots are free and there is space left in storage chests, and there are unrequested items in an active provider chests, the items are moved from active provider to a storage chest.
* For the storage chests, the bots search for one storage which has the same item already. If that can't be found, they begin using a new storage chest. This is to avoid having storage chests with different items inside, allowing greater organisation.

Storage chests will be filled with items from active provider chests, and construction robots that have had their orders cancelled while they were carrying items.

=== Order of movement ===
The bots fulfil '''all requests with the same priority'''. The algorithm looks for the next free robot, then the next request in the queue and after giving orders to the robot, this request is put at the end of the queue, so that first all other requests are done.

=== Distance ===
Bots ignore distances between chests and request targets. Bots will fulfill requests from the very first chest they find that contains the required items, which can be right next to the target, or in the furthest corner of the logistics area. No check or sorting for distance is done.

== See also ==
* [[Robotic network]]
* [[Robots]]
* [[Transport]]
* [[Roboport]]
* [[Logistic robot]]
* [[Construction robot]]

[[Category:Networks]]