Official Factorio Wiki - User contributions [en]

Storage chest

2024-11-27T13:19:49Z

Morsk: /* History */ noting when 2.0 behavior first appeared. It's in 2.0.7 but not 1.1.110.

{{Languages}}
{{:Infobox:Storage chest}}

The '''storage chest''' is a large advanced storage item that is part of the [[logistic network]]. [[Logistic robot]]s store any items taken out of the [[Player|player's]] logistic trash slots here, as well as items picked up from [[active provider chest]]s. [[Construction robot]]s will use stored items to repair damaged entities and construct [[ghost]]s, as well as storing items picked up as a result of a [[deconstruction planner|deconstruction order]]; this includes the [[wood]]/[[stone]]/[[coal]] from [[tree]]s & [[rock]]s which were in the way of a ghost placement, and any items in other chests or on belts or inside buildings such as [[assembling machine]]s when they are marked for deconstruction. Storage chests can be filtered to only accept one type of item from the logistic network.

=== Notes ===
* Logistic robots will pick up items in the following priority: [[active provider chest]]s > storage chests, [[buffer chest]]s > [[passive provider chest]]s
* Logistic robots will begin to fill storage chests from active provider chests if there are no other tasks available.
* Logistic robots, and construction robots fulfilling deconstruction orders, will fill storage chests in the following priority:
*# Storage chests with a matching filter
*# Storage chests with a matching inventory
*# Storage chests with no filter and no inventory
*# Storage chests with no filter and a mismatched inventory
* The filter that can be set on the storage chest is respected even if items that are actively being pushed to the network can not be stored anywhere else.
* If a logistic robot carrying an item is unable to deliver its cargo (e.g. if the player moves out of range), it will drop its cargo in a storage chest before moving to other tasks.

[[File:storage_logistic_robots_anim.gif|frame|none|Logistic robots placing items in storage chests.]]

== Gallery ==
[[File:Storage chest gui.png|thumb|none|400px|Storage chest GUI.]]

== History ==
{{history|2.0.7|
* Matching filters are prioritized before matching inventory.}}

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

{{history|0.16.8|
* Storage chests can be filtered.}}

{{history|0.15.28|
* Warning icon for logistic chests that are not in a reach of roboport.}}

{{history|0.13.0|
* All types of chests can be connected to the circuit network.}}

{{history|0.10.1|
* Changed the priority of resupplying source of logistic robots. Provider has biggest priority, then storage, and the last one is passive provider.}}

{{history|0.8.1|
* Keep the inventory limit of chests when fast rebuilding.}}

{{history|0.8.0|
* Chests inventory size can be limited.}}

{{history|0.7.0|
* Logistic robots try to not mix different items in storage chests if possible.}}

{{history|0.2.0|
* Introduced}}

== See also ==
* [[Circuit network]]
* [[Logistic network]]

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

Achievements

2024-11-26T18:47:54Z

Morsk: /* List of Space Age DLC achievements */ Filled in criteria for finishing DLC from the 3 entries that didn't have it.

{{Languages}}
'''Achievements''' are given to the player when certain events happen or criteria is fulfilled. Some achievements are meant to make the player feel invested in the game. Others are meant to guide the player to use different strategies and optional game mechanics. Achievements are available in both the [http://store.steampowered.com/app/427520/ Steam] and standalone versions. There are 88 achievements available: 57 in the base game, and an additional 31 when using [[Space Age]]{{SA}}

== Disabling achievements ==
[[File:achievement_list.png|thumb|200px|right|Achievement list in-game.]]Achievements can only be unlocked in the default game mode, called ''Freeplay''. Any scenarios, such as the [[tutorial]] or [[scenario system|custom scenarios]] disable achievements. Furthermore, using script or cheat commands in the [[Console#Scripting_and_cheat_commands|console]] disables achievements, however the user will be warned about this the first time they try to run such a command. Within the freeplay game, enabling peaceful mode or no enemies mode disables the following achievements:
* There is no spoon
* No time for chitchat
* Raining bullets
* Steam all the way
* Keeping your hands clean
* Work around the clock{{SA}}
* Express delivery{{SA}}

Any other changes to map generation or using the [[debug mode]]s does not disable achievements.

A separate instance of achievements will be used when mods are installed and earned achievements will not register with Steam. In multiplayer, achievements can only be earned if the player has spent more than 50% of the time online.

Re-enabling achievements again can be achieved by editing the binary data of a save. ([https://forums.factorio.com/58077 reference])

== List of original achievements ==
The search function of a browser may be used to find a specific achievement faster. This is usually {{keybinding|Ctrl|F}}


{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|getting-on-track}}
| The locomotive must be placed on [[rail]]s, not just crafted.
|
|-
| {{Achievement|eco-unfriendly}}
|
|
|-
| {{Achievement|tech-maniac}}
| Completing infinite technologies of any level is not required. All non-infinite levels of technologies that have infinite continuations are still required (for example, it requires only first 6 levels of [[physical projectile damage (research)|physical projectile damage]]). The achievement's condition is checked when any technology (finite or infinite) is researched.
|
|-
| {{Achievement|smoke-me-a-kipper-i-will-be-back-for-breakfast}}
|
| This line was spoken by Ace Rimmer from the British sci-fi comedy show ''Red Dwarf''.
|-
| {{Achievement|it-stinks-and-they-dont-like-it}}
| This achievement is not disabled in peaceful mode, however pollution will not trigger attacks in peaceful mode.
|The line "He stinks and I don't like him" was spoken by comedian Jim Norton in the 2002 film Spider-Man. It became a regular sound drop on the radio program Opie and Anthony, where Norton was third mic.
|-
| {{Achievement|automated-construction}}
|
|
|-
| {{Achievement|you-are-doing-it-right}}
|
|
|-
| {{Achievement|automated-cleanup}}
|
|
|-
| {{Achievement|you-have-got-a-package}}
|
|
|-
| {{Achievement|delivery-service}}
|
|
|-
| {{Achievement|trans-factorio-express}}
|
| Refers to the ''Trans-Europ Express'', an international passenger railway company that served west and central Europe from 1957 to 1995.
|-
| {{Achievement|watch-your-step}}
|
|
|-
| {{Achievement|golem}}
|
|
|-
| {{Achievement|getting-on-track-like-a-pro}}
|
|
|-
| {{Achievement|mass-production-1}}
|
|
|-
| {{Achievement|mass-production-2}}
|
|
|-
| {{Achievement|mass-production-3}}
|
|
|-
| {{Achievement|circuit-veteran-1}}
|
|
|-
| {{Achievement|circuit-veteran-2}}
|
|
|-
| {{Achievement|circuit-veteran-3}}
|
|
|-
| {{Achievement|computer-age-1}}
|
|
|-
| {{Achievement|computer-age-2}}
|
|
|-
| {{Achievement|computer-age-3}}
|
|
|-
| {{Achievement|iron-throne-1}}
|
| These three achievements refer to the Iron Throne, a large throne in the fantasy novel series ''A Song of Ice and Fire'' made from many swords fused together with dragonfire.
|-
| {{Achievement|iron-throne-2}}
|
|
|-
| {{Achievement|iron-throne-3}}
|
|
|-
| {{Achievement|solaris}}
| The electric network may not have any electricity producers besides solar panels connected to it.
| ''Solaris'' is a 1961 philosophical sci-fi novel written by Stanisław Lem, and a Unix-based computer operating system.
|-
| {{Achievement|steamrolled}}
|
| 'Steamroll' generally refers to a multiplayer match in which one team is performing significantly better than the other.
|-
| {{Achievement|pyromaniac}}
|
|
|-
| {{Achievement|run-forrest-run}}
|
| This line was spoken by Jenny Curran in the 1994 drama film ''Forrest Gump''.
|-
| {{Achievement|minions}}
| This achievement requires follower robot count level 11 for a total of 100 robots. 6 rocket launches are needed to obtain the space science packs to get to and research level 11.
|
|-
| {{Achievement|lazy-bastard}}
| In multiplayer, the crafts of all players are counted towards this achievement. The minimum amount of items crafted by hand is 101 if the player uses the stone furnace in the starting inventory to craft the boiler necessary to power a lab for the [[automation (research)]].
|
|-
| {{Achievement|steam-all-the-way}}
| Only ''placing'' solar panels breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies or peaceful mode.
|
|-
| {{Achievement|raining-bullets}}
| Only ''placing'' laser turrets breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies or peaceful mode.
|
|-
| {{Achievement|logistic-network-embargo}}
|
|
|-
| {{Achievement|no-time-for-chitchat}}
| Disabled when using no enemies or peaceful mode.
|
|-
| {{Achievement|there-is-no-spoon}}
| Disabled when using no enemies or peaceful mode.
| This line was spoken by Spoon Boy in the 1999 sci-fi action film ''The Matrix''.
|-
| {{Achievement|so-long-and-thanks-for-all-the-fish}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Send a [[raw fish]] into space via [[rocket silo|rocket]].}}
| The last message left by the dolphins before leaving Earth in ''The Hitchhiker's Guide to the Galaxy''. Also the name of the fourth book in the series.
|}

== List of achievements added in version 2.0 ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|automate-this}}
| If you hand craft your way up to mk2 assembling machines, placing a mk2 will -not- trigger this achievement.
|
|-
| {{Achievement|arachnophilia}}
|
| Arachnophilia means "love of spiders".
|-
| {{Achievement|steam-power}}
|
|
|-
| {{Achievement|solar-power}}
|
|
|-
| {{Achievement|nuclear-power}}
|
|
|-
| {{Achievement|crafting-with-speed}}
|
|
|-
| {{Achievement|crafting-with-efficiency}}
|
|
|-
| {{Achievement|crafting-with-productivity}}
|
|
|-
| {{Achievement|mining-with-determination}}
| With map generation settings for patch richness and size set to minimum, mining out the minuscule stone starting patch triggers this achievement.
|
|-
| {{Achievement|research-with-automation}}
|
|
|-
| {{Achievement|research-with-logistics}}
|
|
|-
| {{Achievement|research-with-chemicals}}
|
|
|-
| {{Achievement|research-with-military}}
|
|
|-
| {{Achievement|research-with-production}}
|
|
|-
| {{Achievement|research-with-utility}}
|
|
|-
| {{Achievement|research-with-space}}
|
|
|-
| {{Achievement|pest-control}}
|
|
|-
| {{Achievement|terraformer}}
|
|
|-
| {{Achievement|destroyer-of-worlds}}
|
| A variation of a quote from physicist J. Robert Oppenheimer upon his invention of the atomic bomb.
|-
| {{Achievement|art-of-siege}}
|
|
|-
| {{Achievement|keeping-your-hands-clean}}
| This achievement becomes disabled if you manually destroy an enemy structure before destroying one using artillery, or if using no enemies or peaceful mode.
|
|}

== List of Space Age DLC achievements ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|fusion-power}}
|
|
|-
| {{Achievement|reach-for-the-stars}}
|
|
|-
| {{Achievement|visit-fulgora}}
|
|
|-
| {{Achievement|visit-gleba}}
|
|
|-
| {{Achievement|visit-vulcanus}}
|
|
|-
| {{Achievement|visit-aquilo}}
|
|
|-
| {{Achievement|make-it-better}}
|
|
|-
| {{Achievement|crafting-with-quality}}
|
|
|-
| {{Achievement|second-star-to-the-right-and-straight-on-till-morning}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Travel to the Solar System Edge. Skipping past, by traveling towards the Shattered Planet, may not award the achievement. Set Solar System Edge as the destination.}}
| The directions to the island of Never Land, as told in the various adaptations of the character Peter Pan
Also the last order Captain Kirk gives to the Enterprise in ''Star Trek VI: The Undiscovered Country''
|-
| {{Achievement|it-stinks-and-they-do-like-it}}
| Spores are affected by the pollution map settings, disabling pollution when generating the map will prevent you from earning this achievement.
|
|-
| {{Achievement|get-off-my-lawn}}
|
| Quote from Gran Torino movie.
|-
| {{Achievement|shattered-planet-1}}
|
|
|-
| {{Achievement|shattered-planet-2}}
|
|
|-
| {{Achievement|shattered-planet-3}}
|
|
|-
| {{Achievement|research-with-metallurgics}}
|
|
|-
| {{Achievement|research-with-agriculture}}
|
|
|-
| {{Achievement|research-with-electromagnetics}}
|
|
|-
| {{Achievement|research-with-cryogenics}}
|
|
|-
| {{Achievement|research-with-promethium}}
|
|
|-
| {{Achievement|rush-to-space}}
| This achievement becomes disabled if you finish researching [[Production_science_pack_(research)|production science]] or [[Utility_science_pack_(research)|utility science]]
|
|-
| {{Achievement|if-it-bleeds}}
|
| Arnold Schwarzenegger quote from Predator (1987) movie.
|-
| {{Achievement|we-need-bigger-guns}}
|
| Quote from Split Second movie.
|-
| {{Achievement|size-doesnt-matter}}
|
| Wink wink.
|-
| {{Achievement|look-at-my-shiny-rare-armor}}
|
|
|-
| {{Achievement|todays-fish-is-trout-a-la-creme}}
|
| This line was spoken by a machine dispensing said fish in the British sci-fi comedy show ''Red Dwarf.''
|-
| {{Achievement|my-modules-are-legendary}}
|
|
|-
| {{Achievement|no-room-for-more}}
|
|
|-
| {{Achievement|work-around-the-clock}}
| Disabled when using no enemies or peaceful mode. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to the Solar System Edge. Skipping past, by traveling towards the Shattered Planet, may not award the achievement. Set Solar System Edge as the destination.}}
|
|-
| {{Achievement|express-delivery}}
| Disabled when using no enemies or peaceful mode. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to the Solar System Edge. Skipping past, by traveling towards the Shattered Planet, may not award the achievement. Set Solar System Edge as the destination.}}
|
|}

== History ==
{{History|2.0.9|
* Logistic network embargo achievement now have different condition for base game and [[space age]]{{SA}}.
}}

{{History|2.0.7|
* Added new achievements.
}}

{{History|0.13.0|
* Introduced.
}}

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

{{C|Main}}

Console

2024-11-20T16:06:08Z

Morsk: add 2 lines for more settings /* Enable long reach */

{{Languages}}
The '''console''' is Factorio's in-game command-line interface. See [[command line parameters]] for the command line interface of the Factorio executable.

The in-game console can be used for:

* Chatting with other players
* Occasional status updates
* Running commands / scripts / cheats

There are three types of commands:

* '''[[#Normal commands|Normal]]''' - Display information about the game and customize your experience.
* '''[[#Multiplayer commands|Multiplayer]]''' - Message filtering, banning users, etc.
* '''[[#Scripting and cheat commands|Scripting/Cheating]]''' - Run small Lua scripts (but they disable achievements for the save game)

__TOC__

=== Using the console ===
The console display can be toggled with the {{Keybinding|grave}} key (<code>`</code>). This is the key located to the left of the <code>1</code> key, above <code>Tab</code>.

You can customize the keys via '''Settings menu → Controls → Toggle chat (and Lua console)'''.
When the console is open, you'll see a blinking cursor at the bottom of the screen; type your message or command and hit '''Return''' to send it (this will also close the console).
Documentation about message and command prefixes can be found further down this page.

The console supports [[rich text]] tags. These 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 the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

When the console is closed, only the most recent messages/commands will be displayed, but they will gradually fade away (opening the console will immediately re-display all recent messages).
Note that by default, all executed commands are made visible to all users. The fade-out time can be changed via '''Settings menu → Interface → Chat message delay'''.

The console can be cleared with the '''/clear''' command.

Use the {{keybinding|↑}} and {{keybinding|↓}} keys to scroll through the console history. The {{keybinding|Tab}} key provides intelligent code completion on commands, options and player names.

== Normal commands ==

{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| /alerts <enable/disable/mute/unmute> <alert>
| /alerts disable turret_fire
| Enables, disables, mutes, or unmutes the given [[alerts|alert]] type. Available alerts: entity_destroyed, entity_under_attack, not_enough_construction_robots, no_material_for_construction, not_enough_repair packs, turret_fire, custom, no_storage, train_out_of_fuel, fluid_mixing.
| No
|-
| /clear
| /clear
| Clears the console.
| No
|-
| /color <color>
| /color 20 255 255
| Changes your color. Can either be one of the pre-defined colors or [[:Wikipedia:RGB_color_space|RGB value]] in the format of “# # #”. Available colors: default, red, green, blue, orange, yellow, pink, purple, white, black, gray, brown, cyan, acid.
| No
|-
| /evolution
| /evolution
| Prints info about the alien evolution factor.
| No
|-
| /help [command]
| /help
| Prints a list of available commands, the optional argument can specify the command that should be described.
| No
|-
| /h [command]
| /h
| Same as /help.
| No
|-
| /mute-programmable-speaker <mute/unmute> <local/everyone>
| /mute-programmable-speaker mute local
| Mutes or unmutes the global sounds created by the Programmable Speaker. Use “local” to mute just the local client. Admins can use “everyone” to mute the sounds for everyone on the server.
| No
|-
| /perf-avg-frames <number>
| /perf-avg-frames 100
| Number of ticks/updates used to average performance counters. Default is 100. Value of 5-10 is recommended for fast convergence, but numbers will jitter more rapidly.
| No
|-
| /permissions
| /permissions
| Opens the [[permissions]] GUI.
| Yes
|-
| /permissions <action> <parameters>
| /permissions add-player DeveloperGroup kovarex
| Available actions are add-player <group> <player>, create-group <name>, delete-group <group>, edit-group <group> <input_action> <true/false>, get-player-group <player>, remove-player <group> <player>, rename-group <group> <new_name> and reset
| Yes
|-
| /reset-tips
| /reset-tips
| Resets the state of the tips and tricks as if the game was just started for the first time.
| No
|-
| /screenshot [x resolution] [y resolution] [zoom]
| /screenshot
| Takes a screenshot with the GUI hidden, centered on the player. It is saved in the "script-output" subfolder of your [[User data directory]]. Resolution is optional and defaults to the current window size. Zoom is optional and defaults to 1.
| No
|-
| /seed
| /seed
| Prints the starting map seed.
| No
|-
| /time
| /time
| Prints info about how old the map is.
| No
|-
| /toggle-action-logging
| /toggle-action-logging
| Toggles logging all input actions performed by the game. This value isn’t persisted between game restarts and only affects your local game in multiplayer sessions.
| Yes
|-
| /toggle-heavy-mode
| /toggle-heavy-mode
| Used to investigate [[Desynchronization#Using_heavy_mode_command|desyncs]]. Will slow down the game and make multiplayer unplayable.
| Yes
|-
| /unlock-shortcut-bar
| /unlock-shortcut-bar
| Unlocks all [[shortcut bar]] items, including blueprint string import, copy & paste, deconstruction and upgrade planner.
| No
|-
| /unlock-tips
| /unlock-tips
| Unlocks all tips and tricks entries.
| No
|-
| /version
| /version
| Prints the current game version.
| No
|-
|}

== Multiplayer commands ==
{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| <message>
| Hello team!
| Console input that does not start with {{keybinding|/}} is shown as a chat message to your team.
| No
|-
| /admin
| /admin
| Opens the player management GUI.
| Yes
|-
| /admins
| /admins
| Prints a list of game admins.
| No
|-
| /ban <player> <reason>
| /ban xTROLLx Throwing grenades in base
| Bans the specified player.
| Yes
|-
| /bans
| /bans
| Prints a list of banned players.
| No
|-
| /banlist <add/remove/get/clear> <player>
| /banlist get
| Adds or removes a player from the banlist. Same as /ban or /unban.
| No
|-
| /config
| /config
| Opens the server configuration GUI.
| Yes
|-
| /config <get/set> <option> <value>
| /config set password hunter2
| Gets or sets various multiplayer game settings. Available configs are: afk-auto-kick, allow-commands, allow-debug-settings, autosave-interval, autosave-only-on-server, ignore-player-limit-for-returning-players, max-players, max-upload-speed, only-admins-can-pause, password, require-user-verification, visibility-lan, visibility-public. The units for the options afk-auto-kick and autosave-interval are in minutes.
| Yes
|-
| /delete-blueprint-library <player>
| /delete-blueprint-library everybody confirm
| Deletes the blueprint library storage for the given offline player from the save file. Enter “everybody confirm” to delete the storage of all offline players.
| Yes
|-
| /demote <player>
| /demote AzureDiamond
| Demotes the player from admin.
| Yes
|-
| /ignore <player>
| /ignore Cthon98
| Prevents the chat from showing messages from this player. Admin messages are still shown.
| No
|-
| /ignores
| /ignores
| Prints a list of ignored players.
| No
|-
| /kick <player> <reason>
| /kick xTROLLx Throwing grenades in base
| Kicks the specified player.
| Yes
|-
| /mute <player>
| /mute Cthon98
| Prevents the player from saying anything in chat.
| Yes
|-
| /mutes
| /mutes
| All players that are muted (can’t talk in chat).
| No
|-
| /open <player>
| /open AzureDiamond
| Opens another player’s inventory.
| Yes
|-
| /o <player>
| /o AzureDiamond
| Same as /open.
| Yes
|-
| /players [online/o/count/c]
| /players
| Prints a list of players in the game. (parameter online/o, it prints only players that are online, count/c prints only count)
| No
|-
| /p [online/o/count/c]
| /p o c
| Same as /players.
| No
|-
| /promote <player>
| /promote AzureDiamond
| Promotes the player to admin.
| Yes
|-
| /purge <player>
| /purge Cthon98
| Clears all the messages from this player from the chat log.
| Yes
|-
| /reply <message>
| /reply oh, really?
| Replies to the last player that whispered to you.
| No
|-
| /r <message>
| /r oh, really?
| Same as /reply.
| No
|-
| /server-save
| /server-save
| Saves the game on the server in a multiplayer game.
| Yes
|-
| /shout <message>
| /shout Hello world!
| Sends a message to all players including other forces.
| No
|-
| /s <message>
| /s Hello world!
| Same as /shout.
| No
|-
| /swap-players <player> [player]
| /swap-players AzureDiamond
| Swaps your character with the given player’s character, or if two players are given swaps the two player characters.
| Yes
|-
| /unban <player>
| /unban xTROLLx
| Unbans the specified player.
| Yes
|-
| /unignore <player>
| /unignore Cthon98
| Allows the chat to show messages from this player.
| No
|-
| /unmute <player>
| /unmute Cthon98
| Allows the player to talk in chat again.
| Yes
|-
| /whisper <player> <message>
| /whisper AzureDiamond that's what I see
| Sends a message to the specified player.
| No
|-
| /w <player> <message>
| /w AzureDiamond that's what I see
| Same as /whisper.
| No
|-
| /whitelist <add/remove/get/clear> [player]
| /whitelist get
| Adds or removes a player from the whitelist, where only whitelisted players can join the game. Enter nothing for “player” when using “get” to print a list of all whitelisted players. An empty whitelist disables the whitelist functionality allowing anyone to join.
| No
|}

== Scripting and cheat commands ==
{| class="wikitable"
|-
! Command
! Description
|-
| /cheat [all/<planet-name>/<platform-name>/off]
| Researches all technologies and enables cheat mode (allowing free crafting of any item).
* Using the '''all''' option also gives the player some additional items.
* Specifying a ''planet-name'' or ''platform-name'' also moves the player to the origin of the specified planet or platform.
* Using the '''off''' option turns cheat mode off.
|-
| /command <command>
| Executes a Lua command (if allowed).
|-
| /c <command>
| Executes a Lua command (if allowed).
|-
| /editor
| Toggles the map editor.
|-
| /measured-command <command>
| Executes a Lua command (if allowed) and measures time it took.
|-
| /mc <command>
| Executes a Lua command (if allowed) and measures time it took.
|-
| /silent-command <command>
| Executes a Lua command (if allowed) without printing it to the console.
|-
| /sc <command>
| Executes a Lua command (if allowed) without printing it to the console.
|}

This is a very powerful feature, which also allows cheating, and as such achievements will be permanently disabled for the save as soon as you use a script command.

== Basic example scripts ==

=== Use it as calculator ===
<syntaxhighlight lang="lua">
/c game.player.print(1234*5678)
</syntaxhighlight>

=== Zoom beyond normal bounds ===
Note that zooming too far out can cause performance hits. Be careful.
<syntaxhighlight lang="lua">
/c game.player.zoom=0.1
</syntaxhighlight>

=== Mine faster ===
<syntaxhighlight lang="lua">
/c game.player.force.manual_mining_speed_modifier=1000
</syntaxhighlight>

=== Craft faster ===
<syntaxhighlight lang="lua">
/c game.player.force.manual_crafting_speed_modifier=1000
</syntaxhighlight>

=== Unlock and research all technologies ===
<syntaxhighlight lang="lua">
/c game.player.force.research_all_technologies()
</syntaxhighlight>

Undo this with the command in the next section.

Note: Specific technologies can be researched using the [[map editor]] by shift clicking the "start research" button on the technology GUI.

=== Unresearch all technologies ===
This does not reset manually applied bonuses
<syntaxhighlight lang="lua">
/c for _, tech in pairs(game.player.force.technologies) do
tech.researched=false
end
</syntaxhighlight>

Note: Specific technologies can be unresearched using the [[map editor]] by clicking the "un-research" button on the technology GUI.

=== Reset your force ===
This resets all data for your force, including kill and production statistics, technologies, bonuses and charting status.
<syntaxhighlight lang="lua">
/c game.player.force.reset()
</syntaxhighlight>

=== Always show rail block visualization ===
Permanently show the rail block visualization instead of only when holding a rail signal. Disable by replacing true with false.

<syntaxhighlight lang="lua">
/c game.player.game_view_settings.show_rail_block_visualisation = true
</syntaxhighlight>

=== Set all trains to Automatic mode ===
Set all trains to automatic mode - for example after building them with a blueprint.

<syntaxhighlight lang="lua">
/c for key,ent in pairs (game.player.surface.find_entities_filtered{name="locomotive"}) do
ent.train.manual_mode = false
end
</syntaxhighlight>

== Inventory manipulation scripts ==

=== Cheat mode ===
Allows for infinite free crafting. Disable by replacing true with false.
<syntaxhighlight lang="lua">
/c game.player.cheat_mode=true
</syntaxhighlight>

=== Refill resources (refill oil, iron etc.) ===
While holding the cursor over a resource tile in-game:
<syntaxhighlight lang="lua">
/c game.player.selected.amount=7500
</syntaxhighlight>

Alternatively you can refill all resources in the map with the following command. Change ore.amount to the desired value.
<syntaxhighlight lang="lua">
/c surface = game.player.surface
for _, ore in pairs(surface.find_entities_filtered({type="resource"})) do
ore.amount = 10000
end
</syntaxhighlight>

=== Add items to the player's inventory ===
Replace iron-plate with the [[data.raw|internal name]] of the item desired.
<syntaxhighlight lang="lua">
/c game.player.insert{name="iron-plate", count=100}
</syntaxhighlight>

For instance, here's a stack of the god-mode energy system interface:
<syntaxhighlight lang="lua">
/c game.player.insert{name="electric-energy-interface"}
</syntaxhighlight>

There are several god-mode items available:

* <code>infinity-chest</code>
* <code>infinity-pipe</code>
* <code>electric-energy-interface</code>
* <code>heat-interface</code>

Add a powerful armor with equipment and some tools for construction:
<syntaxhighlight lang="lua">
/c local player = game.player
player.insert{name="power-armor-mk2", count = 1}
local p_armor = player.get_inventory(5)[1].grid
p_armor.put({name = "fission-reactor-equipment"})
p_armor.put({name = "fission-reactor-equipment"})
p_armor.put({name = "fission-reactor-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "personal-roboport-mk2-equipment"})
p_armor.put({name = "night-vision-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
player.insert{name="construction-robot", count = 25}
</syntaxhighlight>

=== Increase player inventory slots ===
Gives 100 additional bonus inventory slots to your entire force. Used by the [[Toolbelt (research)]].
<syntaxhighlight lang="lua">
/c game.player.force.character_inventory_slots_bonus=100
</syntaxhighlight>

== World manipulation scripts ==

=== Reveal the map around the player ===

Reveals the map around the player, similar to a [[radar]].
<syntaxhighlight lang="lua">
/c local radius=150
game.player.force.chart(game.player.surface, {{game.player.position.x-radius, game.player.position.y-radius}, {game.player.position.x+radius, game.player.position.y+radius}})
</syntaxhighlight>
or from start position
<syntaxhighlight lang="lua">
/c local radius=150
game.player.force.chart(game.player.surface, {{x = -radius, y = -radius}, {x = radius, y = radius}})
</syntaxhighlight>
Change 150 to the desired radius, higher values take longer.

=== Hide revealed map ===

Hides all revealed chunks, inverted map revealing.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local force = game.player.force
for chunk in surface.get_chunks() do
force.unchart_chunk({x = chunk.x, y = chunk.y}, surface)
end
</syntaxhighlight>

=== Reveal all generated map ===

Revels all of the generated map to the player's team.
<syntaxhighlight lang="lua">
/c game.player.force.chart_all()
</syntaxhighlight>

=== Delete chunks ===
If much of the map is revealed, it increases the size of the save file. The following command cancels the generation of all chunks that are currently queued for generation and removes chunks outside a 32 chunks radius around 0,0. Note that this will remove player entities if there are any on these chunks.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface;
game.player.force.cancel_charting(surface);
local chunk_radius = 32;
for chunk in surface.get_chunks() do
if (chunk.x < -chunk_radius or chunk.x > chunk_radius or chunk.y < -chunk_radius or chunk.y > chunk_radius) then
surface.delete_chunk(chunk)
end
end
</syntaxhighlight>

=== Delete unrevealed chunks ===
This command deletes chunks that are not revealed by the player. Can be used after the command for [[#Hide revealed map|hiding revealed map]] to delete the chunks not covered by radar.

<syntaxhighlight lang="lua">/c local surface = game.player.surface
local force = game.player.force
for chunk in surface.get_chunks() do
if not force.is_chunk_charted(surface, chunk) then
surface.delete_chunk(chunk)
end
end</syntaxhighlight>

=== Turn off night ===
Enables eternal day.
<syntaxhighlight lang="lua">
/c game.player.surface.always_day=true
</syntaxhighlight>

=== Change game speed ===
0.5 is half speed, 1 is default, 2 is double speed, etc. Minimum is 0.01. This can be used for a lot of things like when you know you will have to wait for long periods of time for something to complete. Increasing will decrease performance, be careful.
<syntaxhighlight lang="lua">
/c game.speed=X
</syntaxhighlight>

=== Freeze time ===
Stops the advancement of the time. Unfreezes it if you by replace "true" with "false".
<syntaxhighlight lang="lua">
/c game.player.surface.freeze_daytime=true
</syntaxhighlight>

=== Remove all pollution ===
<syntaxhighlight lang="lua">
/c game.player.surface.clear_pollution()
</syntaxhighlight>

=== Completely turn off pollution ===

<syntaxhighlight lang="lua">
/c for _, surface in pairs(game.surfaces) do
surface.clear_pollution()
end
game.map_settings.pollution.enabled = false
</syntaxhighlight>

=== Add a lot of pollution ===
<syntaxhighlight lang="lua">
/c game.player.surface.pollute(game.player.position, 1000000)
</syntaxhighlight>

=== Where speakers are, who placed them ===
<syntaxhighlight lang="lua">
/c local speakers = game.player.surface.find_entities_filtered{force = game.player.force, type="programmable-speaker"}
for key, speaker in pairs(speakers) do
game.player.print(speaker.last_user.name .. " placed a speaker at " .. speaker.gps_tag)
end
</syntaxhighlight>

=== Disable friendly fire for your force ===
<syntaxhighlight lang="lua">
/c game.player.force.friendly_fire = false
</syntaxhighlight>

=== Add new resource patch ===
This creates a new 11×11 patch of resources, centered on the player character, where the ground is not water.
The patch it creates is perfectly square but it randomizes the amount similar to natural generation, with fewer ore at the edges and more ore in the center.
The default numbers result in a patch with 2500-3000 ore.

If you want a larger patch, change "local size = 5" to a larger number.
A larger patch will have exponentially more ore.
Entering a number above 30 is not recommended.

If you want a richer patch, change "local density = 10" to a larger number.
Entering a very large number shouldn't hurt anything but you probably don't need to go above 100.

To choose which resource is spawned, change "stone" near the bottom to "iron-ore", "copper-ore", "coal", or "uranium-ore".

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local ore=nil
local size=5
local density=10
for y=-size, size do
for x=-size, size do
a=(size+1-math.abs(x))*10
b=(size+1-math.abs(y))*10
if a<b then
ore=math.random(a*density-a*(density-8), a*density+a*(density-8))
end
if b<a then
ore=math.random(b*density-b*(density-8), b*density+b*(density-8))
end
if surface.get_tile(game.player.position.x+x, game.player.position.y+y).collides_with("ground-tile") then
surface.create_entity({name="stone", amount=ore, position={game.player.position.x+x, game.player.position.y+y}})
end
end
end
</syntaxhighlight>

For more flexibility, the [[map editor]] can also be used to create/alter/remove resource patches.

=== Remove resources around the player ===
Removes all resource patches from the ground in a 50 x 50 area around the player.

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local size=50
local pos=game.player.position

for _, e in pairs(surface.find_entities_filtered{area={{pos.x-size, pos.y-size},{pos.x+size, pos.y+size}}, type="resource"})
do e.destroy()
end
</syntaxhighlight>

=== Add new oil patch ===
This creates 9 crude oil patches in a 3×3 square.
<syntaxhighlight lang="lua">
/c for y=0,2 do
for x=0,2 do
game.player.surface.create_entity({name="crude-oil", amount=100000, position={game.player.position.x+x*7-7, game.player.position.y+y*7-7}})
end
end
</syntaxhighlight>

or randomly without any collision:
<syntaxhighlight lang="lua">
/c local position=nil
for i=1,9 do
position=game.player.surface.find_non_colliding_position("crude-oil", game.player.position, 0, i/2+1.5)
if position then
game.player.surface.create_entity({name="crude-oil", amount=100000, position=position})
end
end
</syntaxhighlight>

=== Regenerate resources ===
For solid resources like iron, destroys all resource entities and creates resource entities as in the original map generation. For fluid resources like oil, sets the yield of all existing resource entities to the original amount. Regenerates resources on the entire surface.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
for _, e in pairs(surface.find_entities_filtered{type="resource"}) do
if e.prototype.infinite_resource then
e.amount = e.initial_amount
else
e.destroy()
end
end
local non_infinites = {}
for resource, prototype in pairs(prototypes.get_entity_filtered{{filter="type", type="resource"}}) do
if not prototype.infinite_resource then
table.insert(non_infinites, resource)
end
end
surface.regenerate_entity(non_infinites)
for _, e in pairs(surface.find_entities_filtered{type="mining-drill"}) do
e.update_connections()
end
</syntaxhighlight>

=== Count entities ===
Counts all entities whose name includes the string in local entity.
<syntaxhighlight lang="lua">
/c local entity="belt"
local surface=game.player.surface
local count=0
for key, ent in pairs(surface.find_entities_filtered({force=game.player.force})) do
if string.find(ent.name,entity) then
count=count+1
end
end
game.player.print(count)
</syntaxhighlight>

=== Turn off cliff generation ===
Sets size to "none". Only effective on chunks that are generated after using this command. Use [[#Remove all cliffs]] to delete existing cliffs.

<syntaxhighlight lang="lua">
/c local mgs = game.player.surface.map_gen_settings
mgs.cliff_settings.cliff_elevation_0 = 1024
game.player.surface.map_gen_settings = mgs</syntaxhighlight>

=== Remove all cliffs ===
Removes all cliffs existing cliffs from the world. Use [[#Turn off cliff generation]] to turn off cliff generation in new chunks.

<syntaxhighlight lang="lua">
/c for _, v in pairs(game.player.surface.find_entities_filtered{type="cliff"}) do
v.destroy()
end</syntaxhighlight>

=== Delete all decoratives ===
Delete the decoratives that can be found in the world.

<syntaxhighlight lang="lua">
/c game.player.surface.destroy_decoratives({})</syntaxhighlight>

=== Change map generation settings ===
This allows to change the map generation settings for new chunks; it does not alter already generated chunks. [[#Delete chunks|Deleted chunks]] are affected by the setting change because they are newly generated when they get explored again.

To change resource generation settings, replace "iron-ore" with the [[Data.raw#resource|resource]] that should be changed and replace "very-high" with the desired [https://lua-api.factorio.com/latest/Concepts.html#MapGenSize MapGenSize] in the following command. Replace "iron-ore" with "enemy-base" to change the enemy base generation settings.

<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local resource = "iron-ore"
local mgs = surface.map_gen_settings
mgs.autoplace_controls[resource].size = "very-high"
mgs.autoplace_controls[resource].frequency = "very-high"
mgs.autoplace_controls[resource].richness = "very-high"
surface.map_gen_settings = mgs</syntaxhighlight>

To change water generation settings, replace "very-high" with the desired [https://lua-api.factorio.com/latest/Concepts.html#MapGenSize MapGenSize] in the following command.

<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local mgs = surface.map_gen_settings
mgs.water = "very-high" --[[ size]]
mgs.terrain_segmentation = "very-high" --[[ frequency]]
surface.map_gen_settings = mgs </syntaxhighlight>

=== Making a structure indestructible ===
This makes it impossible for an entity to be damaged or killed, e.g. by biters. Hover over the entity and then run:
<syntaxhighlight lang="lua">
/c game.player.selected.destructible = false
</syntaxhighlight>

=== Connect linked belts ===
If there exist at least two [https://lua-api.factorio.com/latest/prototypes/LinkedBeltPrototype.html linked belts], and one of them has the "Entity tag" <code>in</code>, and another linked belt has the "Entity tag" <code>out</code>, then the following command should link these two linked belts.

<syntaxhighlight lang="lua">
/c local i = game.get_entity_by_tag('in')
local o = game.get_entity_by_tag('out')
i.linked_belt_type = 'input'
o.linked_belt_type = 'output'
i.connect_linked_belts(o)
</syntaxhighlight>

== Enemy/evolution scripts ==

=== Set evolution factor ===
Ranges from 0 (new game) to 1.
<syntaxhighlight lang="lua">
/c game.forces["enemy"].set_evolution_factor(X, game.player.surface)
</syntaxhighlight>

=== Disable time-based evolution & increases pollution-based evolution ===
<syntaxhighlight lang="lua">
/c game.map_settings.enemy_evolution.time_factor=0
/c game.map_settings.enemy_evolution.pollution_factor=game.map_settings.enemy_evolution.pollution_factor*2
</syntaxhighlight>

The "2" at the end of the last command will double the default pollution factor. You can substitute another number to increase (or decrease) the pollution factor further.

=== Kill all biters on the "enemy" force ===
Note that this will kill only mobile units, spawners will not be killed.
<syntaxhighlight lang="lua">
/c game.forces["enemy"].kill_all_units()
</syntaxhighlight>

=== Kill all enemies ===
This will kill all biters, bases and worms. Anything that is an enemy will be completely destroyed. This only affects enemies in the generated world, so any unexplored parts of the map which still need to be generated will still have enemies. You can [[#Prevent biters being on newly generated chunks|prevent biters being on newly generated chunks]] if desired.
<syntaxhighlight lang="lua">
/c local surface=game.player.surface
for key, entity in pairs(surface.find_entities_filtered({force="enemy"})) do
entity.destroy()
end
</syntaxhighlight>

=== Kill all nearby enemies ===

This will kill all biters, bases and worms in a configurable radius. The default, 250 tiles, is about two zoomed-out screen widths on full HD. After destruction, it shows how many objects were destroyed.

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local pp = game.player.position
local cnt = 0
for key, entity in pairs(surface.find_entities_filtered({force="enemy", radius=250, position=pp })) do
cnt = cnt+1
entity.destroy()
end
game.player.print(cnt)
</syntaxhighlight>

=== Enable/Disable peaceful mode ===
Enabling peaceful mode prevents biter attacks until provoked. Substitute true for false to disable. Already existing biters are not affected by this command so attacks could continue for a while after activating peaceful mode.
<syntaxhighlight lang="lua">
/c game.player.surface.peaceful_mode = true
</syntaxhighlight>

=== Enable/Disable biter expansion ===
Biter expansion allows biters to create new nests, it is enabled by default. Substitute true for false to disable.
<syntaxhighlight lang="lua">
/c game.map_settings.enemy_expansion.enabled = true
</syntaxhighlight>

=== Prevent biters being on newly generated chunks ===
On newly generated chunks no biters will be present, however all current biters will remain unaffected. Equivalent of setting the Enemy Base Size to None under the Terrain settings during map generation but achieved mid game by [[#Change map generation settings|changing map generation settings]].
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local mgs = surface.map_gen_settings
mgs.autoplace_controls["enemy-base"].size = "none"
surface.map_gen_settings = mgs
</syntaxhighlight>

Instead of the command, it is also possible to use a GUI in the [[map editor]] to changing map generation settings mid game. Access the map editor with <code>/editor</code>, go to the "Surfaces" tab and click "Edit map gen settings".

== Player character scripts ==
Commands concerning the player directly.
=== Get player position ===
Prints coordinates of your current position.
<syntaxhighlight lang="lua">
/c game.player.print(game.player.position)
</syntaxhighlight>

=== Teleport player ===
Moves the player to the specified location. You should be able to teleport to a specific player if you obtain their coordinates via them executing the previous command and giving them to you.
<syntaxhighlight lang="lua">
/c game.player.teleport({X, Y})
</syntaxhighlight>

To teleport to the world's origin, use 0,0.

To teleport to a different planet / surface, use:
<syntaxhighlight lang="lua">
/c game.player.teleport({X, Y}, 'surface_name')
</syntaxhighlight>

=== Enable god mode ===
God mode removes your player character allowing you to fly over obstacles and take no damage.

Disassociate your controls from the character and destroy it:
<syntaxhighlight lang="lua">
/c game.player.character.destroy()
</syntaxhighlight>

To undo, spawn a player character. This will spawn a new character at the spawn point of the world, and connect your controls to it.
<syntaxhighlight lang="lua">
/c game.player.create_character()
</syntaxhighlight>

=== Enable long reach ===
Enables long reach, which allows the player to build and interact with entities at a greater distance. The default reach is 10.
<syntaxhighlight lang="lua">
/c local reach = 10000
game.player.force.character_build_distance_bonus = reach
game.player.force.character_reach_distance_bonus = reach
game.player.force.character_resource_reach_distance_bonus = reach
game.player.force.character_item_drop_distance_bonus = reach
</syntaxhighlight>

=== Find player corpses ===
Pings player corpses on the map.
<syntaxhighlight lang="lua">
/c local found_corpses = game.player.surface.find_entities_filtered{type="character-corpse"}
for _,corpse in pairs(found_corpses) do
local player = game.get_player(corpse.character_corpse_player_index)
local name = player and player.name or "????"
game.player.print(name .. " --> " .. corpse.gps_tag)
end
</syntaxhighlight>

=== Run faster ===
<syntaxhighlight lang="lua">
/c game.player.character_running_speed_modifier=3
</syntaxhighlight>

== Research scripts ==
=== Enable faster research ===
<syntaxhighlight lang="lua">
/c game.player.force.laboratory_speed_modifier=1
</syntaxhighlight>
-0.5 is half speed, 0 is normal speed, 1 is double speed, 2 is triple etc.

=== Research specific technologies ===
The internal technology names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.technologies['electric-energy-distribution-1'].researched=true
/c game.player.force.technologies['steel-processing'].researched=true
</syntaxhighlight>

To research a high level of an infinite technology, set its level:
<syntaxhighlight lang="lua">
/c game.player.force.technologies['worker-robots-speed-6'].level = 100
/c game.player.force.technologies['mining-productivity-4'].level = 100
</syntaxhighlight>

=== Unresearch specific technologies ===
The internal technology names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.technologies['electric-energy-distribution-1'].researched=false
/c game.player.force.technologies['steel-processing'].researched=false
</syntaxhighlight>

=== Enabling specific recipes ===
The internal recipe/item names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.recipes["electric-energy-interface"].enabled=true
/c game.player.force.recipes["rocket-silo"].enabled=true
/c game.player.force.recipes.loader.enabled=true
/c game.player.force.recipes["fast-loader"].enabled = true
/c game.player.force.recipes["express-loader"].enabled = true
</syntaxhighlight>

=== Enable all recipes ===
<syntaxhighlight lang="lua">
/c for name, recipe in pairs(game.player.force.recipes) do recipe.enabled = true end
</syntaxhighlight>

=== Resetting technology effects to default ===
This will reset the enabled/unlocked state of all recipes to what they would be purely based on the currently researched technologies, as well as resetting other technology effects like mining speed, etc. Any manual modifications to these effects and recipe unlocks will be undone.
<syntaxhighlight lang="lua">
/c game.player.force.reset_technology_effects()
</syntaxhighlight>
Note: Can be used as a quick workaround when recipes are unavailable after adding or changing mods even though the technology unlocking them has already been researched.

== Modding tools ==
A list of the internal names of most things in the vanilla game can also be found on [[data.raw]].

=== Access a mod's data ===
If the first word of the command is __mod-name__ it will run in the context of the mod with the same name. For instance, this command prints the data from the Even Distribution mod:
<syntaxhighlight lang="lua">
/c __even-distribution__ game.player.print(serpent.dump(global))
</syntaxhighlight>

=== Print to console the tile under the player ===
<syntaxhighlight lang="lua">
/c game.player.print(game.player.surface.get_tile(game.player.position).name)
</syntaxhighlight>

=== Write all researched technologies to file ===
<syntaxhighlight lang="lua">
/c local list = {}
for _, tech in pairs(game.player.force.technologies) do
if tech.researched then
list[#list+1] = tech.name
end
end
game.write_file("techs.lua", serpent.block(list) .. "\n", true)
</syntaxhighlight>

=== Write all enabled recipes to file ===
<syntaxhighlight lang="lua">
/c local list = {}
for _, recipe in pairs(game.player.force.recipes) do
if recipe.enabled then
list[#list+1] = recipe.name
end
end
game.write_file("recipes.lua", serpent.block(list) .. "\n", true)
</syntaxhighlight>

=== Write mod list to file ===
Write all currently active mods and their version to the file script-output/mods.txt in the [[user data directory]].

<syntaxhighlight lang="lua">
/c game.write_file("mods.txt", serpent.block(game.active_mods))
</syntaxhighlight>

== History ==
{{History|1.1.92|
* Added a notification when a technology is researched.
* Added /enable-research-queue console command to enable the research queue without disabling achievements.}}

== See also ==
* [[Command line parameters]]
* https://lua-api.factorio.com/latest/index-runtime.html - Factorio API reference for latest version

{{C|Modding}}

Achievements

2024-11-10T23:20:25Z

Morsk: Added trivia of Star Trek reference

{{Languages}}
'''Achievements''' are given to the player when certain events happen or criteria is fulfilled. Some achievements are meant to make the player feel invested in the game. Others are meant to guide the player to use different strategies and optional game mechanics. Achievements are available in both the [http://store.steampowered.com/app/427520/ Steam] and standalone versions. There are 88 achievements available: 57 in the base game, and an additional 31 when using [[Space Age]]{{SA}}

== Disabling achievements ==
[[File:achievement_list.png|thumb|200px|right|Achievement list in-game.]]Achievements can only be unlocked in the default game mode, called ''Freeplay''. Any scenarios, such as the [[tutorial]] or [[scenario system|custom scenarios]] disable achievements. Furthermore, using script or cheat commands in the [[Console#Scripting_and_cheat_commands|console]] disables achievements, however the user will be warned about this the first time they try to run such a command. Within the freeplay game, enabling peaceful mode or no enemies mode disables the following achievements:
* There is no spoon
* No time for chitchat
* Raining bullets
* Steam all the way
* Keeping your hands clean
* Work around the clock{{SA}}
* Express delivery{{SA}}

Any other changes to map generation or using the [[debug mode]]s does not disable achievements.

A separate instance of achievements will be used when mods are installed and earned achievements will not register with Steam. In multiplayer, achievements can only be earned if the player has spent more than 50% of the time online.

Re-enabling achievements again can be achieved by editing the binary data of a save. ([https://forums.factorio.com/58077 reference])

== List of original achievements ==
The search function of a browser may be used to find a specific achievement faster. This is usually {{keybinding|Ctrl|F}}


{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|getting-on-track}}
| The locomotive must be placed on [[rail]]s, not just crafted.
|
|-
| {{Achievement|eco-unfriendly}}
|
|
|-
| {{Achievement|tech-maniac}}
| Completing infinite technologies of any level is not required. All non-infinite levels of technologies that have infinite continuations are still required (for example, it requires only first 6 levels of [[physical projectile damage (research)|physical projectile damage]]). The achievement's condition is checked when any technology (finite or infinite) is researched.
|
|-
| {{Achievement|smoke-me-a-kipper-i-will-be-back-for-breakfast}}
|
| This line was spoken by Ace Rimmer from the British sci-fi comedy show ''Red Dwarf''.
|-
| {{Achievement|it-stinks-and-they-dont-like-it}}
| This achievement is not disabled in peaceful mode, however pollution will not trigger attacks in peaceful mode.
|The line "He stinks and I don't like him" was spoken by comedian Jim Norton in the 2002 film Spider-Man. It became a regular sound drop on the radio program Opie and Anthony, where Norton was third mic.
|-
| {{Achievement|automated-construction}}
|
|
|-
| {{Achievement|you-are-doing-it-right}}
|
|
|-
| {{Achievement|automated-cleanup}}
|
|
|-
| {{Achievement|you-have-got-a-package}}
|
|
|-
| {{Achievement|delivery-service}}
|
|
|-
| {{Achievement|trans-factorio-express}}
|
| Refers to the ''Trans-Europ Express'', an international passenger railway company that served west and central Europe from 1957 to 1995.
|-
| {{Achievement|watch-your-step}}
|
|
|-
| {{Achievement|golem}}
|
|
|-
| {{Achievement|getting-on-track-like-a-pro}}
|
|
|-
| {{Achievement|mass-production-1}}
|
|
|-
| {{Achievement|mass-production-2}}
|
|
|-
| {{Achievement|mass-production-3}}
|
|
|-
| {{Achievement|circuit-veteran-1}}
|
|
|-
| {{Achievement|circuit-veteran-2}}
|
|
|-
| {{Achievement|circuit-veteran-3}}
|
|
|-
| {{Achievement|computer-age-1}}
|
|
|-
| {{Achievement|computer-age-2}}
|
|
|-
| {{Achievement|computer-age-3}}
|
|
|-
| {{Achievement|iron-throne-1}}
|
| These three achievements refer to the Iron Throne, a large throne in the fantasy novel series ''A Song of Ice and Fire'' made from many swords fused together with dragonfire.
|-
| {{Achievement|iron-throne-2}}
|
|
|-
| {{Achievement|iron-throne-3}}
|
|
|-
| {{Achievement|solaris}}
| The electric network may not have any electricity producers besides solar panels connected to it.
| ''Solaris'' is a 1961 philosophical sci-fi novel written by Stanisław Lem, and a Unix-based computer operating system.
|-
| {{Achievement|steamrolled}}
|
| 'Steamroll' generally refers to a multiplayer match in which one team is performing significantly better than the other.
|-
| {{Achievement|pyromaniac}}
|
|
|-
| {{Achievement|run-forrest-run}}
|
| This line was spoken by Jenny Curran in the 1994 drama film ''Forrest Gump''.
|-
| {{Achievement|minions}}
| This achievement requires follower robot count level 11 for a total of 100 robots. 6 rocket launches are needed to obtain the space science packs to get to and research level 11.
|
|-
| {{Achievement|lazy-bastard}}
| In multiplayer, the crafts of all players are counted towards this achievement. The minimum amount of items crafted by hand is 101 if the player uses the stone furnace in the starting inventory to craft the boiler necessary to power a lab for the [[automation (research)]].
|
|-
| {{Achievement|steam-all-the-way}}
| Only ''placing'' solar panels breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies or peaceful mode.
|
|-
| {{Achievement|raining-bullets}}
| Only ''placing'' laser turrets breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies or peaceful mode.
|
|-
| {{Achievement|logistic-network-embargo}}
|
|
|-
| {{Achievement|no-time-for-chitchat}}
| Disabled when using no enemies or peaceful mode.
|
|-
| {{Achievement|there-is-no-spoon}}
| Disabled when using no enemies or peaceful mode.
| This line was spoken by Spoon Boy in the 1999 sci-fi action film ''The Matrix''.
|-
| {{Achievement|so-long-and-thanks-for-all-the-fish}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Send a [[raw fish]] into space via [[rocket silo|rocket]].}}
| The last message left by the dolphins before leaving Earth in ''The Hitchhiker's Guide to the Galaxy''. Also the name of the fourth book in the series.
|}

== List of achievements added in version 2.0 ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|automate-this}}
| If you hand craft your way up to mk2 assembling machines, placing a mk2 will -not- trigger this achievement.
|
|-
| {{Achievement|arachnophilia}}
|
| Arachnophilia means "love of spiders".
|-
| {{Achievement|steam-power}}
|
|
|-
| {{Achievement|solar-power}}
|
|
|-
| {{Achievement|nuclear-power}}
|
|
|-
| {{Achievement|crafting-with-speed}}
|
|
|-
| {{Achievement|crafting-with-efficiency}}
|
|
|-
| {{Achievement|crafting-with-productivity}}
|
|
|-
| {{Achievement|mining-with-determination}}
| With map generation settings for patch richness and size set to minimum, mining out the minuscule stone starting patch triggers this achievement.
|
|-
| {{Achievement|research-with-automation}}
|
|
|-
| {{Achievement|research-with-logistics}}
|
|
|-
| {{Achievement|research-with-chemicals}}
|
|
|-
| {{Achievement|research-with-military}}
|
|
|-
| {{Achievement|research-with-production}}
|
|
|-
| {{Achievement|research-with-utility}}
|
|
|-
| {{Achievement|research-with-space}}
|
|
|-
| {{Achievement|pest-control}}
|
|
|-
| {{Achievement|terraformer}}
|
|
|-
| {{Achievement|destroyer-of-worlds}}
|
| A variation of a quote from physicist J. Robert Oppenheimer upon his invention of the atomic bomb.
|-
| {{Achievement|art-of-siege}}
|
|
|-
| {{Achievement|keeping-your-hands-clean}}
| This achievement becomes disabled if you manually destroy an enemy structure before destroying one using artillery, or if using no enemies or peaceful mode.
|
|}

== List of Space Age DLC achievements ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|fusion-power}}
|
|
|-
| {{Achievement|reach-for-the-stars}}
|
|
|-
| {{Achievement|visit-fulgora}}
|
|
|-
| {{Achievement|visit-gleba}}
|
|
|-
| {{Achievement|visit-vulcanus}}
|
|
|-
| {{Achievement|visit-aquilo}}
|
|
|-
| {{Achievement|make-it-better}}
|
|
|-
| {{Achievement|crafting-with-quality}}
|
|
|-
| {{Achievement|second-star-to-the-right-and-straight-on-till-morning}}
| {{spoiler|button-text=Spoiler! Click to view.|message=The criteria for completing the dlc.}}
| The directions to the island of Never Land, as told in the various adaptations of the character Peter Pan
Also the last order Captain Kirk gives to the Enterprise in ''Star Trek VI: The Undiscovered Country''
|-
| {{Achievement|it-stinks-and-they-do-like-it}}
|
|
|-
| {{Achievement|get-off-my-lawn}}
|
| Quote from Gran Torino movie.
|-
| {{Achievement|shattered-planet-1}}
|
|
|-
| {{Achievement|shattered-planet-2}}
|
|
|-
| {{Achievement|shattered-planet-3}}
|
|
|-
| {{Achievement|research-with-metallurgics}}
|
|
|-
| {{Achievement|research-with-agriculture}}
|
|
|-
| {{Achievement|research-with-electromagnetics}}
|
|
|-
| {{Achievement|research-with-cryogenics}}
|
|
|-
| {{Achievement|research-with-promethium}}
|
|
|-
| {{Achievement|rush-to-space}}
| This achievement becomes disabled if you finish researching [[Production_science_pack_(research)|production science]] or [[Utility_science_pack_(research)|utility science]]
|
|-
| {{Achievement|if-it-bleeds}}
|
| Arnold Schwarzenegger quote from Predator (1987) movie.
|-
| {{Achievement|we-need-bigger-guns}}
|
| Quote from Split Second movie.
|-
| {{Achievement|size-doesnt-matter}}
|
| Wink wink.
|-
| {{Achievement|look-at-my-shiny-rare-armor}}
|
|
|-
| {{Achievement|todays-fish-is-trout-a-la-creme}}
|
| This line was spoken by a machine dispensing said fish in the British sci-fi comedy show ''Red Dwarf.''
|-
| {{Achievement|my-modules-are-legendary}}
|
|
|-
| {{Achievement|no-room-for-more}}
|
|
|-
| {{Achievement|work-around-the-clock}}
| Disabled when using no enemies or peaceful mode. {{spoiler|button-text=Spoiler! Click to view.|message=The criteria for completing the dlc.}}
|
|-
| {{Achievement|express-delivery}}
| Disabled when using no enemies or peaceful mode. {{spoiler|button-text=Spoiler! Click to view.|message=The criteria for completing the dlc.}}
|
|}

== History ==
{{History|2.0.9|
* Logistic network embargo achievement now have different condition for base game and [[space age]]{{SA}}.
}}

{{History|2.0.7|
* Added new achievements.
}}

{{History|0.13.0|
* Introduced.
}}

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

{{C|Main}}

Console

2020-09-05T22:56:07Z

Morsk: /* Player character scripts */ add script to find player corpses

{{Languages}}
The '''console''' is Factorio's in-game command-line interface. See [[command line parameters]] for the command line interface of the Factorio executable.

The in-game console can be used for:

* Chatting with other players
* Occasional status updates
* Running commands / scripts / cheats

There are three types of commands:

* '''[[#Normal commands|Normal]]''' - Display information about the game and customize your experience.
* '''[[#Multiplayer commands|Multiplayer]]''' - Message filtering, banning users, etc.
* '''[[#Scripting and cheat commands|Scripting/Cheating]]''' - Run small Lua scripts (but they disable achievements for the save game)

__TOC__

=== Using the console ===
The console display can be toggled with the {{keybinding|/}} (slash) or {{keybinding|~}} (tilde) keys.

You can customize the keys via '''Options Menu → Keyboard → Toggle Lua console'''.
When the console is open, you'll see a blinking cursor at the bottom of the screen; type your message or command and hit '''Return''' to send it (this will also close the console).
Documentation about message and command prefixes can be found further down this page.

The console supports [[rich text]] tags. These 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 the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

When the console is closed, only the most recent messages/commands will be displayed, but they will gradually fade away (opening the console will immediately re-display all recent messages).
Note that by default, all executed commands are made visible to all users. You can set the fade-out time via '''Options Menu → Other Settings → Message Delay'''.

If you want to immediately hide the console, open the console and then press '''Escape''' key (or press '''Return''' without entering any message/command).
This not only closes the console, but it also hides all the recent messages/commands.
The console can be cleared with the '''/clear''' command.

Use the {{keybinding|↑}} and {{keybinding|↓}} keys to scroll through the console history. The {{keybinding|Tab}} key will auto-complete commands and player names.

== Normal commands ==

{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| /alerts <enable/disable/mute/unmute> <alert>
| /alerts disable turret_fire
| Enables, disables, mutes, or unmutes the given [[alerts|alert]] type. Available alerts: entity_destroyed, entity_under_attack, not_enough_construction_robots, no_material_for_construction, not_enough_repair packs, turret_fire, custom, no_storage, train_out_of_fuel, fluid_mixing.
| No
|-
| /clear
| /clear
| Clears the console.
| No
|-
| /color <color>
| /color 20 255 255 100
| Changes your color. Can either be one of the pre-defined colors or [[:Wikipedia:RGBA_color_space|RGBA value]] in the format of “# # # #”. Available colors: default, red, green, blue, orange, yellow, pink, purple, white, black, gray, brown, cyan, acid.
| No
|-
| /evolution
| /evolution
| Prints info about the alien evolution factor.
| No
|-
| /help [command]
| /help
| Prints a list of available commands, the optional argument can specify the command that should be described.
| No
|-
| /h [command]
| /h
| Same as /help.
| No
|-
| /mute-programmable-speaker <mute/unmute> <local/everyone>
| /mute-programmable-speaker mute local
| Mutes or unmutes the global sounds created by the Programmable Speaker. Use “local” to mute just the local client. Admins can use “everyone” to mute the sounds for everyone on the server.
| No
|-
| /perf-avg-frames <number>
| /perf-avg-frames 100
| Number of ticks/updates used to average performance counters. Default is 100. Value of 5-10 is recommended for fast convergence, but numbers will jitter more rapidly.
| No
|-
| /permissions
| /permissions
| Opens the permissions GUI.
| Yes
|-
| /screenshot [x resolution] [y resolution] [zoom]
| /screenshot
| Takes a screenshot with the GUI hidden, centered on the player. It is saved in the "script-output" subfolder of your [[User data directory]]. Resolution is optional and defaults to the current window size. Zoom is optional and defaults to 1.
| No
|-
| /seed
| /seed
| Prints the starting map seed.
| No
|-
| /time
| /time
| Prints info about how old the map is.
| No
|-
| /toggle-action-logging
| /toggle-action-logging
| Toggles logging all input actions performed by the game. This value isn’t persisted between game restarts and only affects your local game in multiplayer sessions.
| Yes
|-
| /toggle-heavy-mode
| /toggle-heavy-mode
| Used to investigate [[Desynchronization#Using_heavy_mode_command|desyncs]]. Will slow down the game and make multiplayer unplayable.
| Yes
|-
| /toggle-rockets-sent-gui
| /toggle-rockets-sent-gui
| Toggles if the rockets sent button is shown in the upper left corner of the screen.
| No
|-
| /unlock-shortcut-bar
| /unlock-shortcut-bar
| Unlocks all shortcut bar items.
| No
|-
| /version
| /version
| Prints the current game version.
| No
|-
|}

== Multiplayer commands ==

{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| <message>
| Hello team!
| Console input that does not start with {{keybinding|/}} is shown as a chat message to your team.
| No
|-
| /admin
| /admin
| Opens the player management GUI.
| Yes
|-
| /admins
| /admins
| Prints a list of game admins.
| No
|-
| /ban <player> <reason>
| /ban xTROLLx Throwing grenades in base
| Bans the specified player.
| Yes
|-
| /banlist <add/remove/get/clear> <player>
| /banlist get
| Adds or removes a player from the banlist. Same as /ban or /unban.
| No
|-
| /config <get/set> <option> <value>
| /config set password hunter2
| Gets or sets various multiplayer game settings. Available configs are: afk-auto-kick, allow-commands, allow-debug-settings, autosave-interval, autosave-only-on-server, ignore-player-limit-for-returning-players, max-players, max-upload-speed, only-admins-can-pause, password, require-user-verification, visibility-lan, visibility-public.
| Yes
|-
| /delete-blueprint-library <player>
| /delete-blueprint-library everybody confirm
| Deletes the blueprint library storage for the given offline player from the save file. Enter “everybody confirm” to delete the storage of all offline players.
| Yes
|-
| /demote <player>
| /demote AzureDiamond
| Demotes the player from admin.
| Yes
|-
| /ignore <player>
| /ignore Cthon98
| Prevents the chat from showing messages from this player. Admin messages are still shown.
| No
|-
| /ignores
| /ignores
| Prints a list of ignored players.
| No
|-
| /kick <player> <reason>
| /kick xTROLLx Throwing grenades in base
| Kicks the specified player.
| Yes
|-
| /mute <player>
| /mute Cthon98
| Prevents the player from saying anything in chat.
| Yes
|-
| /mutes
| /mutes
| All players that are muted (can’t talk in chat).
| No
|-
| /open <player>
| /open AzureDiamond
| Opens another player’s inventory.
| Yes
|-
| /o <player>
| /o AzureDiamond
| Same as /open.
| Yes
|-
| /players [online/o/count/c]
| /players
| Prints a list of players in the game. (parameter online/o, it prints only players that are online, count/c prints only count)
| No
|-
| /promote <player>
| /promote AzureDiamond
| Promotes the player to admin.
| Yes
|-
| /purge <player>
| /purge Cthon98
| Clears all the messages from this player from the chat log.
| Yes
|-
| /reply <message>
| /reply oh, really?
| Replies to the last player that whispered to you.
| No
|-
| /r <message>
| /r oh, really?
| Same as /reply.
| No
|-
| /server-save
| /server-save
| Saves the game on the server in a multiplayer game.
| Yes
|-
| /shout <message>
| /shout Hello world!
| Sends a message to all players including other forces.
| No
|-
| /s <message>
| /s Hello world!
| Same as /shout.
| No
|-
| /swap-players <player> [player]
| /swap-players AzureDiamond
| Swaps your character with the given player’s character, or if two players are given swaps the two player characters.
| Yes
|-
| /unban <player>
| /unban xTROLLx
| Unbans the specified player.
| Yes
|-
| /unignore <player>
| /unignore Cthon98
| Allows the chat to show messages from this player.
| No
|-
| /unmute <player>
| /unmute Cthon98
| Allows the player to talk in chat again.
| Yes
|-
| /whisper <player> <message>
| /whisper AzureDiamond that's what I see
| Sends a message to the specified player.
| No
|-
| /w <player> <message>
| /w AzureDiamond that's what I see
| Same as /whisper.
| No
|-
| /whitelist <add/remove/get/clear> [player]
| /whitelist get
| Adds or removes a player from the whitelist, where only whitelisted players can join the game. Enter nothing for “player” when using “get” to print a list of all whitelisted players. An empty whitelist disables the whitelist functionality allowing anyone to join.
| No
|}

== Scripting and cheat commands ==
{| class="wikitable"
|-
! Command
! Description
|-
| /cheat <all>
| Researches all technologies and enables cheat mode. Using the '''all''' option also gives the player some additional items.
|-
| /command <command>
| Executes a Lua command (if allowed).
|-
| /c <command>
| Executes a Lua command (if allowed).
|-
| /editor
| Toggles the map editor.
|-
| /measured-command <command>
| Executes a Lua command (if allowed) and measures time it took.
|-
| /silent-command <command>
| Executes a Lua command (if allowed) without printing it to the console.
|}

This is a very powerful feature, which also allows cheating, and as such achievements will be permanently disabled for the save as soon as you use a script command.

== Basic example scripts ==

=== Use it as calculator ===
<syntaxhighlight lang="lua">
/c game.player.print(1234*5678)
</syntaxhighlight>

=== Zoom beyond normal bounds ===
Note that zooming too far out can cause performance hits. Be careful.
<syntaxhighlight lang="lua">
/c game.player.zoom=0.1
</syntaxhighlight>

=== Mine faster ===
<syntaxhighlight lang="lua">
/c game.player.force.manual_mining_speed_modifier=1000
</syntaxhighlight>

=== Craft faster ===
<syntaxhighlight lang="lua">
/c game.player.force.manual_crafting_speed_modifier=1000
</syntaxhighlight>

=== Unlock and research all technologies ===
<syntaxhighlight lang="lua">
/c game.player.force.research_all_technologies()
</syntaxhighlight>

Undo this with the command in the next section.

=== Unresearch all technologies ===
This does not reset manually applied bonuses
<syntaxhighlight lang="lua">
/c for _, tech in pairs(game.player.force.technologies) do
tech.researched=false
game.player.force.set_saved_technology_progress(tech, 0)
end
</syntaxhighlight>

=== Reset your force ===
This resets all data for your force, including kill and production statistics, technologies, bonuses and charting status.
<syntaxhighlight lang="lua">
/c game.player.force.reset()
</syntaxhighlight>

=== Always show rail block visualization ===
Permanently show the rail block visualization instead of only when holding a rail signal. Disable by replacing true with false.

<syntaxhighlight lang="lua">
/c game.player.game_view_settings.show_rail_block_visualisation = true
</syntaxhighlight>

== Inventory manipulation scripts ==

=== Cheat mode ===
Allows for infinite free crafting. Disable by replacing true with false.
<syntaxhighlight lang="lua">
/c game.player.cheat_mode=true
</syntaxhighlight>

=== Refill resources (refill oil, iron etc.) ===
While holding the cursor over a resource tile in-game
<syntaxhighlight lang="lua">
/c game.player.selected.amount=7500
</syntaxhighlight>

Alternatively you can refill all resources in the map with the following command. Change ore.amount to the desired value.
<syntaxhighlight lang="lua">
/c surface = game.player.surface
for _, ore in pairs(surface.find_entities_filtered({type="resource"})) do
ore.amount = 10000
end
</syntaxhighlight>

=== Add items to the player's inventory ===
Replace iron-plate with the [[data.raw|internal name]] of the item desired.
<syntaxhighlight lang="lua">
/c game.player.insert{name="iron-plate", count=100}
</syntaxhighlight>

For instance, here's a stack of the god-mode energy system interface:
<syntaxhighlight lang="lua">
/c game.player.insert{name="electric-energy-interface"}
</syntaxhighlight>

Add a powerful armor with equipment and some tools for construction:
<syntaxhighlight lang="lua">
/c local player = game.player
player.insert{name="power-armor-mk2", count = 1}
local p_armor = player.get_inventory(5)[1].grid
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "personal-roboport-mk2-equipment"})
p_armor.put({name = "night-vision-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
player.insert{name="construction-robot", count = 25}
</syntaxhighlight>

=== Increase player inventory slots ===
Gives 100 additional bonus inventory slots to your entire force. Used by the [[Toolbelt]] research.
<syntaxhighlight lang="lua">
/c game.player.force.character_inventory_slots_bonus=100
</syntaxhighlight>

== World manipulation scripts ==

=== Reveal the map around the player ===

Reveals the map around the player, similar to a [[radar]].
<syntaxhighlight lang="lua">
/c local radius=150
game.player.force.chart(game.player.surface, {{game.player.position.x-radius, game.player.position.y-radius}, {game.player.position.x+radius, game.player.position.y+radius}})
</syntaxhighlight>
or from start position
<syntaxhighlight lang="lua">
/c local radius=150
game.player.force.chart(game.player.surface, {{x = -radius, y = -radius}, {x = radius, y = radius}})
</syntaxhighlight>
Change 150 to the desired radius, higher values take longer.

=== Hide revealed map ===

Hides all revealed chunks, inverted map revealing.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local force = game.player.force
for chunk in surface.get_chunks() do
force.unchart_chunk({x = chunk.x, y = chunk.y}, surface)
end
</syntaxhighlight>

=== Reveal all generated map ===

Revels all of the generated map to the player's team.
<syntaxhighlight lang="lua">
/c game.player.force.chart_all()
</syntaxhighlight>

=== Delete chunks ===
If much of the map is revealed, it increases the size of the save file. The following command cancels the generation of all chunks that are currently queued for generation and removes chunks outside a 32 chunks radius around 0,0. Note that this will remove player entities if there are any on these chunks.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface;
game.player.force.cancel_charting(surface);
local chunk_radius = 32;
for chunk in surface.get_chunks() do
if (chunk.x < -chunk_radius or chunk.x > chunk_radius or chunk.y < -chunk_radius or chunk.y > chunk_radius) then
surface.delete_chunk(chunk)
end
end
</syntaxhighlight>

=== Turn off night ===
Enables eternal day.
<syntaxhighlight lang="lua">
/c game.player.surface.always_day=true
</syntaxhighlight>

=== Change game speed ===
0.5 is half speed, 1 is default, 2 is double speed, etc. Minimum is 0.01. This can be used for a lot of things like when you know you will have to wait for long periods of time for something to complete. Increasing will decrease performance, be careful.
<syntaxhighlight lang="lua">
/c game.speed=X
</syntaxhighlight>

=== Expensive (marathon) or normal mode ===
To change from normal to expensive mode preset (this changes the research cost and intermediate product cost):
<syntaxhighlight lang="lua">
/c game.difficulty_settings.recipe_difficulty=1
game.difficulty_settings.technology_difficulty=1
game.difficulty_settings.technology_price_multiplier=4
</syntaxhighlight>

To change back to normal:
<syntaxhighlight lang="lua">
/c game.difficulty_settings.recipe_difficulty=0
game.difficulty_settings.technology_difficulty=0
game.difficulty_settings.technology_price_multiplier=1
</syntaxhighlight>

=== Freeze time ===
Stops the advancement of the time if you replace "BOOL" with "true" or unfreezes it if you replace it with "false".
<syntaxhighlight lang="lua">
/c game.player.surface.freeze_daytime=BOOL
</syntaxhighlight>

=== Remove all pollution ===
<syntaxhighlight lang="lua">
/c game.player.surface.clear_pollution()
</syntaxhighlight>

=== Completely turn off pollution ===

<syntaxhighlight lang="lua">
/c for _, surface in pairs(game.surfaces) do
surface.clear_pollution()
end
game.map_settings.pollution.enabled = false
</syntaxhighlight>

=== Add a lot of pollution ===
<syntaxhighlight lang="lua">
/c game.player.surface.pollute(game.player.position, 1000000)
</syntaxhighlight>

=== Where speakers are, by who ===
<syntaxhighlight lang="lua">
/c speakers = game.player.surface.find_entities_filtered{force = game.player.force, type="programmable-speaker"}
for key, speaker in pairs(speakers) do
game.player.print(speaker.last_user.name .. " placed a speaker at X=" .. speaker.position.x .. ", Y=" .. speaker.position.y)
end
</syntaxhighlight>

=== Disable friendly fire for your force ===
<syntaxhighlight lang="lua">
/c game.player.force.friendly_fire = false
</syntaxhighlight>

=== Add new resource patch ===
This creates a new 11×11 patch of resources, centered on the player character, where the ground is not water.
The patch it creates is perfectly square but it randomizes the amount similar to natural generation, with fewer ore at the edges and more ore in the center.
The default numbers result in a patch with 2500-3000 ore.

If you want a larger patch, change "local size = 5" to a larger number.
A larger patch will have exponentially more ore.
Entering a number above 30 is not recommended.

If you want a richer patch, change "local density = 10" to a larger number.
Entering a very large number shouldn't hurt anything but you probably don't need to go above 100.

To choose which resource is spawned, change "stone" near the bottom to "iron-ore", "copper-ore", "coal", or "uranium-ore".

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local ore=nil
local size=5
local density=10
for y=-size, size do
for x=-size, size do
a=(size+1-math.abs(x))*10
b=(size+1-math.abs(y))*10
if a<b then
ore=math.random(a*density-a*(density-8), a*density+a*(density-8))
end
if b<a then
ore=math.random(b*density-b*(density-8), b*density+b*(density-8))
end
if surface.get_tile(game.player.position.x+x, game.player.position.y+y).collides_with("ground-tile") then
surface.create_entity({name="stone", amount=ore, position={game.player.position.x+x, game.player.position.y+y}})
end
end
end
</syntaxhighlight>

=== Remove resources around the player ===
Removes all resource patches from the ground in a 50 x 50 area around the player.

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local size=50
local pos=game.player.position

for _, e in pairs(surface.find_entities_filtered{area={{pos.x-size, pos.y-size},{pos.x+size, pos.y+size}}, type="resource"})
do e.destroy()
end
</syntaxhighlight>

=== Add new oil patch ===
This creates 9 crude oil patches in a 3×3 square.
<syntaxhighlight lang="lua">
/c for y=0,2 do
for x=0,2 do
game.player.surface.create_entity({name="crude-oil", amount=100000, position={game.player.position.x+x*7-7, game.player.position.y+y*7-7}})
end
end
</syntaxhighlight>

or randomly without any collision:
<syntaxhighlight lang="lua">
/c local position=nil
for i=1,9 do
position=game.player.surface.find_non_colliding_position("crude-oil", game.player.position, 0, i/2+1.5)
if position then
game.player.surface.create_entity({name="crude-oil", amount=100000, position=position})
end
end
</syntaxhighlight>

=== Create 10 fishes ===
This creates 10 fishes around of player. The player must be on the water edge.
<syntaxhighlight lang="lua">
/c local player = game.player
local surface = player.surface
for i = 1, 10 do
local position = surface.find_non_colliding_position('fish', player.position, 10, 1)
if not position then return end
surface.create_entity {name = 'fish', position = position}
end
</syntaxhighlight>

=== Count entities ===
Counts all entities whose name includes the string in local entity.
<syntaxhighlight lang="lua">
/c local entity="belt"
local surface=game.player.surface
local count=0
for key, ent in pairs(surface.find_entities_filtered({force=game.player.force})) do
if string.find(ent.name,entity) then
count=count+1
end
end
game.player.print(count)
</syntaxhighlight>

=== Emptying all pipes, underground pipes and pumps ===
Useful when pipes contain a fluid you dont want.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local deleted=0
for key, entity in pairs(surface.find_entities_filtered({force=game.player.force})) do
if string.find(entity.name, "pipe") or
string.find(entity.name, "pump")
then
for i=1,#entity.fluidbox do
deleted = deleted + 1
entity.fluidbox[i] = nil;
end
end
end
game.player.print("Fluids removed from "..deleted .." entities")
</syntaxhighlight>

=== Turn off cliff generation ===
Sets size to "none". Only effective on chunks that are generated after using this command. Use [[#Remove all cliffs]] to delete existing cliffs.

<syntaxhighlight lang="lua">
/c local mgs = game.player.surface.map_gen_settings
mgs.cliff_settings.cliff_elevation_0 = 1024
game.player.surface.map_gen_settings = mgs</syntaxhighlight>

=== Remove all cliffs ===
Removes all cliffs existing cliffs from the world. Use [[#Turn off cliff generation]] to turn off cliff generation in new chunks.

<syntaxhighlight lang="lua">
/c for _, v in pairs(game.player.surface.find_entities_filtered{type="cliff"}) do
v.destroy()
end</syntaxhighlight>

=== Delete all decoratives ===
Delete the decoratives that can be found in the world.

<syntaxhighlight lang="lua">
/c game.player.surface.destroy_decoratives({})</syntaxhighlight>

=== Change map generation settings ===
This allows to change the map generation settings for new chunks; it does not alter already generated chunks. [[#Delete chunks|Deleted chunks]] are affected by the setting change because they are newly generated when they get explored again.

To change resource generation settings, replace "iron-ore" with the [[Data.raw#resource|resource]] that should be changed and replace "very-high" with the desired [https://lua-api.factorio.com/latest/Concepts.html#MapGenSize MapGenSize] in the following command. Replace "iron-ore" with "enemy-base" to change the enemy base generation settings.

<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local resource = "iron-ore"
local mgs = surface.map_gen_settings
mgs.autoplace_controls[resource].size = "very-high"
mgs.autoplace_controls[resource].frequency = "very-high"
mgs.autoplace_controls[resource].richness = "very-high"
surface.map_gen_settings = mgs</syntaxhighlight>

To change water generation settings, replace "very-high" with the desired [https://lua-api.factorio.com/latest/Concepts.html#MapGenSize MapGenSize] in the following command.

<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local mgs = surface.map_gen_settings
mgs.water = "very-high" --[[ size]]
mgs.terrain_segmentation = "very-high" --[[ frequency]]
surface.map_gen_settings = mgs </syntaxhighlight>

== Enemy/evolution scripts ==

=== Set evolution factor ===
Ranges from 0 (new game) to 1.
<syntaxhighlight lang="lua">
/c game.forces["enemy"].evolution_factor=X
</syntaxhighlight>

=== Disable time-based evolution & increases pollution-based evolution ===
<syntaxhighlight lang="lua">
/c game.map_settings.enemy_evolution.time_factor=0
/c game.map_settings.enemy_evolution.pollution_factor=game.map_settings.enemy_evolution.pollution_factor*2
</syntaxhighlight>

The "2" at the end of the last command will double the default pollution factor. You can substitute another number to increase (or decrease) the pollution factor further.

=== Kill all biters on the "enemy" force ===
Note that this will kill only mobile units, spawners will not be killed.
<syntaxhighlight lang="lua">
/c game.forces["enemy"].kill_all_units()
</syntaxhighlight>

=== Kill all enemies ===
This will kill all biters, bases and worms. Anything that is an enemy will be completely destroyed. This only affects enemies in the explored world, so any unexplored parts of the map which still need to be generated will still have enemies. You can [[#Prevent biters being on newly generated chunks|prevent biters being on newly generated chunks]] if desired.
<syntaxhighlight lang="lua">
/c local surface=game.player.surface
for key, entity in pairs(surface.find_entities_filtered({force="enemy"})) do
entity.destroy()
end
</syntaxhighlight>

=== Kill all nearby enemies ===

This will kill all biters, bases and worms in a configurable radius. The default, 250 tiles, is about two zoomed-out screen widths on full HD. After destruction, it shows how many objects were destroyed.

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local pp = game.player.position
local cnt = 0
for key, entity in pairs(surface.find_entities_filtered({force="enemy", radius=250, position=pp })) do
cnt = cnt+1
entity.destroy()
end
game.player.print(cnt)
</syntaxhighlight>

=== Enable/Disable peaceful mode ===
Enabling peaceful mode prevents biter attacks until provoked. Substitute true for false to disable. Already existing biters are not affected by this command so attacks could continue for a while after activating peaceful mode.
<syntaxhighlight lang="lua">
/c game.player.surface.peaceful_mode = true
</syntaxhighlight>

=== Enable/Disable biter expansion ===
Biter expansion allows biters to create new nests, it is enabled by default. Substitute true for false to disable.
<syntaxhighlight lang="lua">
/c game.map_settings.enemy_expansion.enabled = true
</syntaxhighlight>

=== Prevent biters being on newly generated chunks ===
On newly generated chunks no biters will be present, however all current biters will remain unaffected. Equivalent of setting the Enemy Base Size to None under the Terrain settings during map generation but achieved mid game by [[#Change map generation settings|changing map generation settings]].
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local mgs = surface.map_gen_settings
mgs.autoplace_controls["enemy-base"].size = "none"
surface.map_gen_settings = mgs
</syntaxhighlight>

== Player character scripts ==
Commands concerning the player directly.
=== Get player position ===
Prints coordinates of your current position.
<syntaxhighlight lang="lua">
/c game.player.print(game.player.position.x .. ", " .. game.player.position.y)
</syntaxhighlight>

=== Teleport player ===
Moves the player to the specified location. You should be able to teleport to a specific player if you obtain their coordinates via them executing the previous command and giving them to you.
<syntaxhighlight lang="lua">
/c game.player.teleport({X, Y})
</syntaxhighlight>

To teleport to the world's origin, use 0,0.

=== Enable god mode ===
God mode removes your player character allowing you to fly over obstacles and take no damage.

Disassociate your controls from the player:
<syntaxhighlight lang="lua">
/c game.player.character=nil
</syntaxhighlight>

Then, hover the mouse over the useless player and destroy it by typing:
<syntaxhighlight lang="lua">
/c game.player.selected.destroy()
</syntaxhighlight>

To undo, spawn a player character. This will spawn a new player at the spawn point of the world, and connect your controls to it.
<syntaxhighlight lang="lua">
/c game.player.create_character()
</syntaxhighlight>

=== Enable long reach ===
Enables long reach, which allows the player to build and interact with entities at a greater distance. The default reach is 10.
<syntaxhighlight lang="lua">
/c local reach = 10000
game.player.force.character_build_distance_bonus = reach
game.player.force.character_reach_distance_bonus = reach
</syntaxhighlight>

=== Find player corpses ===
Pings player corpses on the map.
<syntaxhighlight lang="lua">
/c local found_corpses = game.player.surface.find_entities_filtered{type="character-corpse"}
for _,corpse in pairs(found_corpses) do
local index = corpse.character_corpse_player_index
local player = (index > 0) and game.players[index] or nil
local name = player and player.name or "????"
game.player.print(name .. " --> [gps=" .. corpse.position.x .. "," .. corpse.position.y .. "]")
end
</syntaxhighlight>

== Research scripts ==

=== Enable Research Queue ===
Enable the research queue for the players current team. Can be done after the game has started if it was forgotten during the map's setup.
<syntaxhighlight lang="lua">
/c game.player.force.research_queue_enabled = true
</syntaxhighlight>

=== Enable faster research ===
<syntaxhighlight lang="lua">
/c game.player.force.laboratory_speed_modifier=1
</syntaxhighlight>
1 is normal speed, 2 is double speed 3 is triple etc.

=== Research specific technologies ===
The internal technology names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.technologies['electric-energy-distribution-1'].researched=true
/c game.player.force.technologies['steel-processing'].researched=true
</syntaxhighlight>

=== Unresearch specific technologies ===
The internal technology names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.technologies['electric-energy-distribution-1'].researched=false; game.player.force.set_saved_technology_progress('electric-energy-distribution-1', 0)
/c game.player.force.technologies['steel-processing'].researched=false; game.player.force.set_saved_technology_progress('steel-processing', 0)
</syntaxhighlight>

=== Enabling specific recipes ===
The internal recipe/item names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.recipes["electric-energy-interface"].enabled=true
/c game.player.force.recipes["rocket-silo"].enabled=true
/c game.player.force.recipes.loader.enabled=true
/c game.player.force.recipes["fast-loader"].enabled = true
/c game.player.force.recipes["express-loader"].enabled = true
</syntaxhighlight>

=== Enable all recipes ===
<syntaxhighlight lang="lua">
/c for name, recipe in pairs(game.player.force.recipes) do recipe.enabled = true end
</syntaxhighlight>

== Modding tools ==
A list of the internal names of most things in the vanilla game can also be found on [[data.raw]].

=== Access a mod's data ===
If the first word of the command is __mod-name__ it will run in the context of the mod with the same name. For instance, this command prints the data from Resource Spawner Overhaul:
<syntaxhighlight lang="lua">
/c __rso-mod__ game.player.print(serpent.dump(global))
</syntaxhighlight>

=== Print to console which tile are you have under the player position ===
<syntaxhighlight lang="lua">
/c game.player.print(game.player.surface.get_tile(game.player.position).name)
</syntaxhighlight>

=== Write all researched technologies to file ===
<syntaxhighlight lang="lua">
/c local list = {}
for _, tech in pairs(game.player.force.technologies) do
if tech.researched then
list[#list+1] = tech.name
end
end
game.write_file("techs.lua", serpent.block(list) .. "\n", true)
</syntaxhighlight>

=== Write all enabled recipes to file ===
<syntaxhighlight lang="lua">
/c local list = {}
for _, recipe in pairs(game.player.force.recipes) do
if recipe.enabled then
list[#list+1] = recipe.name
end
end
game.write_file("recipes.lua", serpent.block(list) .. "\n", true)
</syntaxhighlight>

=== Write mod list to file ===
Write all currently active mods and their version to the file script-output/mods.txt in the [[user data directory]].

<syntaxhighlight lang="lua">
/c game.write_file("mods.txt", serpent.block(game.active_mods))
</syntaxhighlight>

== See also ==

* [[Command line parameters]]
* http://lua-api.factorio.com/latest/ - Factorio API reference for latest version

Logistic network

2019-12-16T00:45:33Z

Morsk: /* Priorities of robots */ describe storage as part of the priorities, the last priority

{{Languages}}
[[File:RoboTrainStation_small.gif|thumb|420x336px|right|''This gif shows how robots can load or unload chests in a train station. The train delivers items that are filled into [[active provider chest]]s and then put into the [[requester chest]]s to be loaded onto belts.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed. Click [https://wiki.factorio.com/File:RoboTrainStation.gif here] for a larger image.]]

A [[logistic network]] is a series of different logistics chests and [[logistic robot]]s all covered by one or more connected [[roboport]]s.

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

The player character can also act as [[requester chest]] in the logistic network, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots (research)|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.

== Items ==
{| class="wikitable"
!style="width: 220px;" |Entity
!Description
|-
| {{imagelink|Roboport}} || Central component of the logistic network in which the robots operate. Roboport coverage defines the area of the logistic network. Robots need to periodically return here to recharge.
|-
| {{Imagelink|Logistic robot}} || Moves items between logistic chests.1
|-
| {{Imagelink|Construction robot}} || [[Repair pack|Repairs]] broken or replaces destroyed entities. [[blueprint|Builds]], [[deconstruction planner|deconstructs]] and [[upgrade planner|upgrades]] entities on command.
|-
| {{Imagelink|Active provider chest}} || Logistic chest: Pushes stored items into the logistic network.2
|-
| {{Imagelink|Passive provider chest}} || Logistic chest: Places stored items at the logistic network's disposal.2
|-
| {{Imagelink|Storage chest}} || Logistic chest: Stores items currently not requested. Can be filtered to only store one type of item. Supplies stored items to the Logistic network.2
|-
| {{Imagelink|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.2
|-
| {{Imagelink|Buffer chest}} || Logistic chest: Functions as both a [[requester chest]] and [[passive provider chest]].2
|}

(1) Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].

(2) Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

== Usage ==

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 in the roboport. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item with the [[Stack#Stack limitation|stack limitation]]-feature.

The logistic network makes it possible to create complex items in a relatively small factory area, but its throughput is limited by how many robot charge points (roboports) exist in the network.

[[File:Roboport_network_gui.png|thumb|right|200px|Supply area 50×50 tiles (orange); Construction area 110×110 tiles (green)]]
The basic thing needed for item transportation is [[roboport]]s. The roboport shows the orange logistic coverage and the green construction coverage when held in the cursor or hovered after placing.

* The orange zone is the logistic network coverage. This is also the maximum distance for connecting two roboports.
* The green zone is the construction area.

=== Expanding the logistic network ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, so if their logistic areas are touching. Visually this is represented by a dashed yellow line connecting them.
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 migrate from one network to another, unless their home network is destroyed in some way, for example when all roboports are removed or out of power.

== Mechanics ==

=== Losing bots ===

Worker robots are a priority target of biters, and the [[enemies]] will prioritize attacking them over many objects in the vicinity of the robots.

Robots may run out of charge on longer journeys which will reduce their flying speed to 20% of their normal speed. Robots that run out of charge will fly to the closest recharge point instead of their original target. This means that they may depart from the original route and even go into the opposite direction, depending on where the closest charging point is.

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.

=== Negative numbers ===
It is possible to notice negative numbers on the 'Logistic Network'-Screen when looking at network storage or opening the logistic networks GUI the with {{Keybinding|L}}.

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 on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.

=== Choosing the post for charging ===
Normally a robot flies to the nearest roboport to recharge. If the queue on that roboport is too long, they eventually choose another port. This is specified by the ratio of <distance to different roboport in tiles> / <queue size of robots waiting>.

Currently, to choose the more distant roboport, the distance must be at most <Number of robots in the queue and on the way> / 2. So, to choose a roboport that is 10 tiles more distant, it has to have 20 less robots waiting in the queue.

== Priorities of robots ==

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

Logistic robots on the logistic network look for orders by the chests in this order:

* A requested item is first ''looked up'' in active provider chests, then in the player's trash slots, then in the storage chests and buffer chests, then the passive provider chests. So, the active provider chests are emptied first, then the storage chests and buffer chests, then the passive provider chests.

* Requests are ''assigned'' first for player logistics, then for requester chests, then for buffer chests.

{| class="wikitable"
! Source Priority
| {{icon|active provider chest}} > {{icon|Character logistic trash slots (research)}} > {{icon|storage chest}}{{icon|buffer chest}} > {{icon|passive provider chest}}
! Target Priority
| {{icon|Character logistic slots (research)}}{{icon|requester chest}}1 > {{icon|requester chest}} > {{icon|buffer chest}} > {{icon|storage chest}}2
|}

(1) Requesters with "request from buffer chests" have higher priority than others, the same as a player.

(2) Storage does not "request" items on its own. It receives actively discarded items from a) active providers, b) player trash slots, c) deconstruction, and d) robots that have their orders cancelled while carrying items. Storage is the last priority, and receives only items that have nowhere else to go.

* To place items into storage chests, the bots search for a storage chest that already stores items of the same type, then for one which has its filter set to the item type. 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.

=== Distance ===
When looking to pick up requested items from multiple 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.

== Achievements ==
{{Achievement|you-have-got-a-package}}
{{Achievement|delivery-service}}
{{Achievement|logistic-network-embargo}}

[[Category:Logistic network]]

Modding

2019-12-16T00:11:54Z

Morsk: grammar, phrasing

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

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

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

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

Modding

2019-12-15T18:09:05Z

Morsk: /* Downloading & installing mods */ reorder header to match sections

{{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 the ability to download & install, with checking installed mods for updates, and enabling/disabling installed mods.

=== Mod portal (website) ===

Mods can be browsed and downloaded from [https://mods.factorio.com/ mod portal (website)] as well. Mods come in the form of ZIP files, installed by copying (not unzipping) them into the "mods" directory within the [[Application_directory#User_Data_directory|user data directory]]. Verify a successful installation by viewing the "Mods" list through the game's main menu.

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

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

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

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

Modding

2019-12-15T18:07:48Z

Morsk: /* Downloading & installing mods */ recommend in-game mod downloader before website, and rephrase sections so it fits

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

* [https://mods.factorio.com/ Mod portal (website)]
* Mod portal (in-game)
* [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 the ability to download & install, with checking installed mods for updates, and enabling/disabling installed mods.

=== Mod portal (website) ===

Mods can be browsed and downloaded from [https://mods.factorio.com/ mod portal (website)] as well. Mods come in the form of ZIP files, installed by copying (not unzipping) them into the "mods" directory within the [[Application_directory#User_Data_directory|user data directory]]. Verify a successful installation by viewing the "Mods" list through the game's main menu.

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

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

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

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

Logistic network

2019-12-13T13:44:27Z

Morsk: /* Priorities of robots */ undo my addition about distance; it was redundant

{{Languages}}
[[File:RoboTrainStation_small.gif|thumb|420x336px|right|''This gif shows how robots can load or unload chests in a train station. The train delivers items that are filled into [[active provider chest]]s and then put into the [[requester chest]]s to be loaded onto belts.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed. Click [https://wiki.factorio.com/File:RoboTrainStation.gif here] for a larger image.]]

A [[logistic network]] is a series of different logistics chests and [[logistic robot]]s all covered by one or more connected [[roboport]]s.

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

The player character can also act as [[requester chest]] in the logistic network, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots (research)|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.

== Items ==
{| class="wikitable"
!style="width: 220px;" |Entity
!Description
|-
| {{imagelink|Roboport}} || Central component of the logistic network in which the robots operate. Roboport coverage defines the area of the logistic network. Robots need to periodically return here to recharge.
|-
| {{Imagelink|Logistic robot}} || Moves items between logistic chests.1
|-
| {{Imagelink|Construction robot}} || [[Repair pack|Repairs]] broken or replaces destroyed entities. [[blueprint|Builds]], [[deconstruction planner|deconstructs]] and [[upgrade planner|upgrades]] entities on command.
|-
| {{Imagelink|Active provider chest}} || Logistic chest: Pushes stored items into the logistic network.2
|-
| {{Imagelink|Passive provider chest}} || Logistic chest: Places stored items at the logistic network's disposal.2
|-
| {{Imagelink|Storage chest}} || Logistic chest: Stores items currently not requested. Can be filtered to only store one type of item. Supplies stored items to the Logistic network.2
|-
| {{Imagelink|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.2
|-
| {{Imagelink|Buffer chest}} || Logistic chest: Functions as both a [[requester chest]] and [[passive provider chest]].2
|}

(1) Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].

(2) Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

== Usage ==

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 in the roboport. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item with the [[Stack#Stack limitation|stack limitation]]-feature.

The logistic network makes it possible to create complex items in a relatively small factory area, but its throughput is limited by how many robot charge points (roboports) exist in the network.

[[File:Roboport_network_gui.png|thumb|right|200px|Supply area 50×50 tiles (orange); Construction area 110×110 tiles (green)]]
The basic thing needed for item transportation is [[roboport]]s. The roboport shows the orange logistic coverage and the green construction coverage when held in the cursor or hovered after placing.

* The orange zone is the logistic network coverage. This is also the maximum distance for connecting two roboports.
* The green zone is the construction area.

=== Expanding the logistic network ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, so if their logistic areas are touching. Visually this is represented by a dashed yellow line connecting them.
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 migrate from one network to another, unless their home network is destroyed in some way, for example when all roboports are removed or out of power.

== Mechanics ==

=== Losing bots ===

Worker robots are a priority target of biters, and the [[enemies]] will prioritize attacking them over many objects in the vicinity of the robots.

Robots may run out of charge on longer journeys which will reduce their flying speed to 20% of their normal speed. Robots that run out of charge will fly to the closest recharge point instead of their original target. This means that they may depart from the original route and even go into the opposite direction, depending on where the closest charging point is.

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.

=== Negative numbers ===
It is possible to notice negative numbers on the 'Logistic Network'-Screen when looking at network storage or opening the logistic networks GUI the with {{Keybinding|L}}.

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 on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.

=== Choosing the post for charging ===
Normally a robot flies to the nearest roboport to recharge. If the queue on that roboport is too long, they eventually choose another port. This is specified by the ratio of <distance to different roboport in tiles> / <queue size of robots waiting>.

Currently, to choose the more distant roboport, the distance must be at most <Number of robots in the queue and on the way> / 2. So, to choose a roboport that is 10 tiles more distant, it has to have 20 less robots waiting in the queue.

== Priorities of robots ==

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

Logistic robots on the logistic network look for orders by the chests in this order:

* A requested item is first ''looked up'' in the player's trash slots, then in active provider chests, then in the storage chests and buffer chests (only for character logistic slot requests), then the passive provider chests. So, the active provider chests are emptied first, then the storage chests and buffer chests, then the passive provider chests.

* Requests are ''assigned'' first for player logistics, then for requester chests, then for buffer chests.

{| class="wikitable"
! Source Priority
| {{icon|active provider chest}} > {{icon|Character logistic trash slots (research)}} > {{icon|storage chest}}{{icon|buffer chest}} > {{icon|passive provider chest}}
! Target Priority
| {{icon|Character logistic slots (research)}}{{icon|requester chest}}1 > {{icon|requester chest}} > {{icon|buffer chest}}
|}

(1) Requesters with "request from buffer chests" have higher priority than others, the same as a player.

Storage chests will be filled with items from active provider chests, from robots that have had their orders cancelled while they were carrying items, and from the player's logistic trash slots. Furthermore, items deconstructed by construction robots will be placed into storage chests.

* To place items into storage chests, the bots search for a storage chest that already stores items of the same type, then for one which has its filter set to the item type. 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.

=== Distance ===
When looking to pick up requested items from multiple 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.

== Achievements ==
{{Achievement|you-have-got-a-package}}
{{Achievement|delivery-service}}
{{Achievement|logistic-network-embargo}}

[[Category:Logistic network]]

Logistic network

2019-12-13T13:37:31Z

Morsk: /* Priorities of robots */ Active Provider > Player. Not that it matters (no one noticed for a year), but the test was clear.

{{Languages}}
[[File:RoboTrainStation_small.gif|thumb|420x336px|right|''This gif shows how robots can load or unload chests in a train station. The train delivers items that are filled into [[active provider chest]]s and then put into the [[requester chest]]s to be loaded onto belts.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed. Click [https://wiki.factorio.com/File:RoboTrainStation.gif here] for a larger image.]]

A [[logistic network]] is a series of different logistics chests and [[logistic robot]]s all covered by one or more connected [[roboport]]s.

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

The player character can also act as [[requester chest]] in the logistic network, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots (research)|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.

== Items ==
{| class="wikitable"
!style="width: 220px;" |Entity
!Description
|-
| {{imagelink|Roboport}} || Central component of the logistic network in which the robots operate. Roboport coverage defines the area of the logistic network. Robots need to periodically return here to recharge.
|-
| {{Imagelink|Logistic robot}} || Moves items between logistic chests.1
|-
| {{Imagelink|Construction robot}} || [[Repair pack|Repairs]] broken or replaces destroyed entities. [[blueprint|Builds]], [[deconstruction planner|deconstructs]] and [[upgrade planner|upgrades]] entities on command.
|-
| {{Imagelink|Active provider chest}} || Logistic chest: Pushes stored items into the logistic network.2
|-
| {{Imagelink|Passive provider chest}} || Logistic chest: Places stored items at the logistic network's disposal.2
|-
| {{Imagelink|Storage chest}} || Logistic chest: Stores items currently not requested. Can be filtered to only store one type of item. Supplies stored items to the Logistic network.2
|-
| {{Imagelink|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.2
|-
| {{Imagelink|Buffer chest}} || Logistic chest: Functions as both a [[requester chest]] and [[passive provider chest]].2
|}

(1) Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].

(2) Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

== Usage ==

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 in the roboport. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item with the [[Stack#Stack limitation|stack limitation]]-feature.

The logistic network makes it possible to create complex items in a relatively small factory area, but its throughput is limited by how many robot charge points (roboports) exist in the network.

[[File:Roboport_network_gui.png|thumb|right|200px|Supply area 50×50 tiles (orange); Construction area 110×110 tiles (green)]]
The basic thing needed for item transportation is [[roboport]]s. The roboport shows the orange logistic coverage and the green construction coverage when held in the cursor or hovered after placing.

* The orange zone is the logistic network coverage. This is also the maximum distance for connecting two roboports.
* The green zone is the construction area.

=== Expanding the logistic network ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, so if their logistic areas are touching. Visually this is represented by a dashed yellow line connecting them.
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 migrate from one network to another, unless their home network is destroyed in some way, for example when all roboports are removed or out of power.

== Mechanics ==

=== Losing bots ===

Worker robots are a priority target of biters, and the [[enemies]] will prioritize attacking them over many objects in the vicinity of the robots.

Robots may run out of charge on longer journeys which will reduce their flying speed to 20% of their normal speed. Robots that run out of charge will fly to the closest recharge point instead of their original target. This means that they may depart from the original route and even go into the opposite direction, depending on where the closest charging point is.

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.

=== Negative numbers ===
It is possible to notice negative numbers on the 'Logistic Network'-Screen when looking at network storage or opening the logistic networks GUI the with {{Keybinding|L}}.

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 on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.

=== Choosing the post for charging ===
Normally a robot flies to the nearest roboport to recharge. If the queue on that roboport is too long, they eventually choose another port. This is specified by the ratio of <distance to different roboport in tiles> / <queue size of robots waiting>.

Currently, to choose the more distant roboport, the distance must be at most <Number of robots in the queue and on the way> / 2. So, to choose a roboport that is 10 tiles more distant, it has to have 20 less robots waiting in the queue.

== Priorities of robots ==

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

Logistic robots on the logistic network look for orders by the chests in this order:

* A requested item is first ''looked up'' in the player's trash slots, then in active provider chests, then in the storage chests and buffer chests (only for character logistic slot requests), then the passive provider chests. So, the active provider chests are emptied first, then the storage chests and buffer chests, then the passive provider chests.

* Requests are ''assigned'' first for player logistics, then for requester chests, then for buffer chests.

* An item available from multiple sources with the same priority (multiple storage and buffer chests) will be taken from the closest.

{| class="wikitable"
! Source Priority
| {{icon|active provider chest}} > {{icon|Character logistic trash slots (research)}} > {{icon|storage chest}}{{icon|buffer chest}} > {{icon|passive provider chest}}
! Target Priority
| {{icon|Character logistic slots (research)}}{{icon|requester chest}}1 > {{icon|requester chest}} > {{icon|buffer chest}}
|}

(1) Requesters with "request from buffer chests" have higher priority than others, the same as a player.

Storage chests will be filled with items from active provider chests, from robots that have had their orders cancelled while they were carrying items, and from the player's logistic trash slots. Furthermore, items deconstructed by construction robots will be placed into storage chests.

* To place items into storage chests, the bots search for a storage chest that already stores items of the same type, then for one which has its filter set to the item type. 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.

=== Distance ===
When looking to pick up requested items from multiple 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.

== Achievements ==
{{Achievement|you-have-got-a-package}}
{{Achievement|delivery-service}}
{{Achievement|logistic-network-embargo}}

[[Category:Logistic network]]

Logistic network

2019-12-13T13:12:59Z

Morsk: /* Priorities of robots */ Groups are clearer without the = signs putting space into them.

{{Languages}}
[[File:RoboTrainStation_small.gif|thumb|420x336px|right|''This gif shows how robots can load or unload chests in a train station. The train delivers items that are filled into [[active provider chest]]s and then put into the [[requester chest]]s to be loaded onto belts.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed. Click [https://wiki.factorio.com/File:RoboTrainStation.gif here] for a larger image.]]

A [[logistic network]] is a series of different logistics chests and [[logistic robot]]s all covered by one or more connected [[roboport]]s.

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

The player character can also act as [[requester chest]] in the logistic network, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots (research)|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.

== Items ==
{| class="wikitable"
!style="width: 220px;" |Entity
!Description
|-
| {{imagelink|Roboport}} || Central component of the logistic network in which the robots operate. Roboport coverage defines the area of the logistic network. Robots need to periodically return here to recharge.
|-
| {{Imagelink|Logistic robot}} || Moves items between logistic chests.1
|-
| {{Imagelink|Construction robot}} || [[Repair pack|Repairs]] broken or replaces destroyed entities. [[blueprint|Builds]], [[deconstruction planner|deconstructs]] and [[upgrade planner|upgrades]] entities on command.
|-
| {{Imagelink|Active provider chest}} || Logistic chest: Pushes stored items into the logistic network.2
|-
| {{Imagelink|Passive provider chest}} || Logistic chest: Places stored items at the logistic network's disposal.2
|-
| {{Imagelink|Storage chest}} || Logistic chest: Stores items currently not requested. Can be filtered to only store one type of item. Supplies stored items to the Logistic network.2
|-
| {{Imagelink|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.2
|-
| {{Imagelink|Buffer chest}} || Logistic chest: Functions as both a [[requester chest]] and [[passive provider chest]].2
|}

(1) Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].

(2) Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

== Usage ==

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 in the roboport. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item with the [[Stack#Stack limitation|stack limitation]]-feature.

The logistic network makes it possible to create complex items in a relatively small factory area, but its throughput is limited by how many robot charge points (roboports) exist in the network.

[[File:Roboport_network_gui.png|thumb|right|200px|Supply area 50×50 tiles (orange); Construction area 110×110 tiles (green)]]
The basic thing needed for item transportation is [[roboport]]s. The roboport shows the orange logistic coverage and the green construction coverage when held in the cursor or hovered after placing.

* The orange zone is the logistic network coverage. This is also the maximum distance for connecting two roboports.
* The green zone is the construction area.

=== Expanding the logistic network ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, so if their logistic areas are touching. Visually this is represented by a dashed yellow line connecting them.
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 migrate from one network to another, unless their home network is destroyed in some way, for example when all roboports are removed or out of power.

== Mechanics ==

=== Losing bots ===

Worker robots are a priority target of biters, and the [[enemies]] will prioritize attacking them over many objects in the vicinity of the robots.

Robots may run out of charge on longer journeys which will reduce their flying speed to 20% of their normal speed. Robots that run out of charge will fly to the closest recharge point instead of their original target. This means that they may depart from the original route and even go into the opposite direction, depending on where the closest charging point is.

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.

=== Negative numbers ===
It is possible to notice negative numbers on the 'Logistic Network'-Screen when looking at network storage or opening the logistic networks GUI the with {{Keybinding|L}}.

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 on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.

=== Choosing the post for charging ===
Normally a robot flies to the nearest roboport to recharge. If the queue on that roboport is too long, they eventually choose another port. This is specified by the ratio of <distance to different roboport in tiles> / <queue size of robots waiting>.

Currently, to choose the more distant roboport, the distance must be at most <Number of robots in the queue and on the way> / 2. So, to choose a roboport that is 10 tiles more distant, it has to have 20 less robots waiting in the queue.

== Priorities of robots ==

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

Logistic robots on the logistic network look for orders by the chests in this order:

* A requested item is first ''looked up'' in the player's trash slots, then in active provider chests, then in the storage chests and buffer chests (only for character logistic slot requests), then the passive provider chests. So, the active provider chests are emptied first, then the storage chests and buffer chests, then the passive provider chests.

* Requests are ''assigned'' first for player logistics, then for requester chests, then for buffer chests.

* An item available from multiple sources with the same priority (multiple storage and buffer chests) will be taken from the closest.

{| class="wikitable"
! Source Priority
| {{icon|Character logistic trash slots (research)}} > {{icon|active provider chest}} > {{icon|storage chest}}{{icon|buffer chest}} > {{icon|passive provider chest}}
! Target Priority
| {{icon|Character logistic slots (research)}}{{icon|requester chest}}1 > {{icon|requester chest}} > {{icon|buffer chest}}
|}

(1) Requesters with "request from buffer chests" have higher priority than others, the same as a player.

Storage chests will be filled with items from active provider chests, from robots that have had their orders cancelled while they were carrying items, and from the player's logistic trash slots. Furthermore, items deconstructed by construction robots will be placed into storage chests.

* To place items into storage chests, the bots search for a storage chest that already stores items of the same type, then for one which has its filter set to the item type. 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.

=== Distance ===
When looking to pick up requested items from multiple 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.

== Achievements ==
{{Achievement|you-have-got-a-package}}
{{Achievement|delivery-service}}
{{Achievement|logistic-network-embargo}}

[[Category:Logistic network]]

Logistic network

2019-12-13T12:38:13Z

Morsk: /* Priorities of robots */ removed old comment that buffers only supply players. added that "request from buffers" has special priority. you may be able to find nicer formatting than how I did it.

{{Languages}}
[[File:RoboTrainStation_small.gif|thumb|420x336px|right|''This gif shows how robots can load or unload chests in a train station. The train delivers items that are filled into [[active provider chest]]s and then put into the [[requester chest]]s to be loaded onto belts.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed. Click [https://wiki.factorio.com/File:RoboTrainStation.gif here] for a larger image.]]

A [[logistic network]] is a series of different logistics chests and [[logistic robot]]s all covered by one or more connected [[roboport]]s.

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

The player character can also act as [[requester chest]] in the logistic network, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots (research)|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.

== Items ==
{| class="wikitable"
!style="width: 220px;" |Entity
!Description
|-
| {{imagelink|Roboport}} || Central component of the logistic network in which the robots operate. Roboport coverage defines the area of the logistic network. Robots need to periodically return here to recharge.
|-
| {{Imagelink|Logistic robot}} || Moves items between logistic chests.1
|-
| {{Imagelink|Construction robot}} || [[Repair pack|Repairs]] broken or replaces destroyed entities. [[blueprint|Builds]], [[deconstruction planner|deconstructs]] and [[upgrade planner|upgrades]] entities on command.
|-
| {{Imagelink|Active provider chest}} || Logistic chest: Pushes stored items into the logistic network.2
|-
| {{Imagelink|Passive provider chest}} || Logistic chest: Places stored items at the logistic network's disposal.2
|-
| {{Imagelink|Storage chest}} || Logistic chest: Stores items currently not requested. Can be filtered to only store one type of item. Supplies stored items to the Logistic network.2
|-
| {{Imagelink|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.2
|-
| {{Imagelink|Buffer chest}} || Logistic chest: Functions as both a [[requester chest]] and [[passive provider chest]].2
|}

(1) Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].

(2) Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

== Usage ==

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 in the roboport. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item with the [[Stack#Stack limitation|stack limitation]]-feature.

The logistic network makes it possible to create complex items in a relatively small factory area, but its throughput is limited by how many robot charge points (roboports) exist in the network.

[[File:Roboport_network_gui.png|thumb|right|200px|Supply area 50×50 tiles (orange); Construction area 110×110 tiles (green)]]
The basic thing needed for item transportation is [[roboport]]s. The roboport shows the orange logistic coverage and the green construction coverage when held in the cursor or hovered after placing.

* The orange zone is the logistic network coverage. This is also the maximum distance for connecting two roboports.
* The green zone is the construction area.

=== Expanding the logistic network ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, so if their logistic areas are touching. Visually this is represented by a dashed yellow line connecting them.
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 migrate from one network to another, unless their home network is destroyed in some way, for example when all roboports are removed or out of power.

== Mechanics ==

=== Losing bots ===

Worker robots are a priority target of biters, and the [[enemies]] will prioritize attacking them over many objects in the vicinity of the robots.

Robots may run out of charge on longer journeys which will reduce their flying speed to 20% of their normal speed. Robots that run out of charge will fly to the closest recharge point instead of their original target. This means that they may depart from the original route and even go into the opposite direction, depending on where the closest charging point is.

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.

=== Negative numbers ===
It is possible to notice negative numbers on the 'Logistic Network'-Screen when looking at network storage or opening the logistic networks GUI the with {{Keybinding|L}}.

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 on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.

=== Choosing the post for charging ===
Normally a robot flies to the nearest roboport to recharge. If the queue on that roboport is too long, they eventually choose another port. This is specified by the ratio of <distance to different roboport in tiles> / <queue size of robots waiting>.

Currently, to choose the more distant roboport, the distance must be at most <Number of robots in the queue and on the way> / 2. So, to choose a roboport that is 10 tiles more distant, it has to have 20 less robots waiting in the queue.

== Priorities of robots ==

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

Logistic robots on the logistic network look for orders by the chests in this order:

* A requested item is first ''looked up'' in the player's trash slots, then in active provider chests, then in the storage chests and buffer chests (only for character logistic slot requests), then the passive provider chests. So, the active provider chests are emptied first, then the storage chests and buffer chests, then the passive provider chests.

* Requests are ''assigned'' first for player logistics, then for requester chests, then for buffer chests.

* An item available from multiple sources with the same priority (multiple storage and buffer chests) will be taken from the closest.

{| class="wikitable"
! Source Priority
| {{icon|Character logistic trash slots (research)}} > {{icon|active provider chest}} > {{icon|storage chest}} = {{icon|buffer chest}} > {{icon|passive provider chest}}
! Target Priority
| {{icon|Character logistic slots (research)}} = {{icon|requester chest}}1 > {{icon|requester chest}} > {{icon|buffer chest}}
|}

(1) Requesters with "request from buffer chests" have higher priority than others, the same as a player.

Storage chests will be filled with items from active provider chests, from robots that have had their orders cancelled while they were carrying items, and from the player's logistic trash slots. Furthermore, items deconstructed by construction robots will be placed into storage chests.

* To place items into storage chests, the bots search for a storage chest that already stores items of the same type, then for one which has its filter set to the item type. 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.

=== Distance ===
When looking to pick up requested items from multiple 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.

== Achievements ==
{{Achievement|you-have-got-a-package}}
{{Achievement|delivery-service}}
{{Achievement|logistic-network-embargo}}

[[Category:Logistic network]]

Logistic network

2019-12-13T12:30:23Z

Morsk: /* Priorities of robots */ add info about preferring closer sources

{{Languages}}
[[File:RoboTrainStation_small.gif|thumb|420x336px|right|''This gif shows how robots can load or unload chests in a train station. The train delivers items that are filled into [[active provider chest]]s and then put into the [[requester chest]]s to be loaded onto belts.'' Logistics robots are ideal in train stations, since very high item throughput on a short distance is needed. Click [https://wiki.factorio.com/File:RoboTrainStation.gif here] for a larger image.]]

A [[logistic network]] is a series of different logistics chests and [[logistic robot]]s all covered by one or more connected [[roboport]]s.

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

The player character can also act as [[requester chest]] in the logistic network, allowing them to 'request' various items be kept at a set limit within their personal inventory. After [[Research|researching]] [[Character logistic slots (research)|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.

== Items ==
{| class="wikitable"
!style="width: 220px;" |Entity
!Description
|-
| {{imagelink|Roboport}} || Central component of the logistic network in which the robots operate. Roboport coverage defines the area of the logistic network. Robots need to periodically return here to recharge.
|-
| {{Imagelink|Logistic robot}} || Moves items between logistic chests.1
|-
| {{Imagelink|Construction robot}} || [[Repair pack|Repairs]] broken or replaces destroyed entities. [[blueprint|Builds]], [[deconstruction planner|deconstructs]] and [[upgrade planner|upgrades]] entities on command.
|-
| {{Imagelink|Active provider chest}} || Logistic chest: Pushes stored items into the logistic network.2
|-
| {{Imagelink|Passive provider chest}} || Logistic chest: Places stored items at the logistic network's disposal.2
|-
| {{Imagelink|Storage chest}} || Logistic chest: Stores items currently not requested. Can be filtered to only store one type of item. Supplies stored items to the Logistic network.2
|-
| {{Imagelink|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.2
|-
| {{Imagelink|Buffer chest}} || Logistic chest: Functions as both a [[requester chest]] and [[passive provider chest]].2
|}

(1) Default capacity is 1 item per robot. This can be increased by researching [[Worker robot cargo size (research)]].

(2) Logistic chests can also be connected to the [[circuit network]] with [[red wire]] or [[green wire]].

== Usage ==

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 in the roboport. The robots will fly out of the top hatch and will begin to work. You can now limit the number of produced item with the [[Stack#Stack limitation|stack limitation]]-feature.

The logistic network makes it possible to create complex items in a relatively small factory area, but its throughput is limited by how many robot charge points (roboports) exist in the network.

[[File:Roboport_network_gui.png|thumb|right|200px|Supply area 50×50 tiles (orange); Construction area 110×110 tiles (green)]]
The basic thing needed for item transportation is [[roboport]]s. The roboport shows the orange logistic coverage and the green construction coverage when held in the cursor or hovered after placing.

* The orange zone is the logistic network coverage. This is also the maximum distance for connecting two roboports.
* The green zone is the construction area.

=== Expanding the logistic network ===

There can be many separate logistic networks. Two roboports are in the same network only if they are connected, so if their logistic areas are touching. Visually this is represented by a dashed yellow line connecting them.
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 migrate from one network to another, unless their home network is destroyed in some way, for example when all roboports are removed or out of power.

== Mechanics ==

=== Losing bots ===

Worker robots are a priority target of biters, and the [[enemies]] will prioritize attacking them over many objects in the vicinity of the robots.

Robots may run out of charge on longer journeys which will reduce their flying speed to 20% of their normal speed. Robots that run out of charge will fly to the closest recharge point instead of their original target. This means that they may depart from the original route and even go into the opposite direction, depending on where the closest charging point is.

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.

=== Negative numbers ===
It is possible to notice negative numbers on the 'Logistic Network'-Screen when looking at network storage or opening the logistic networks GUI the with {{Keybinding|L}}.

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 on the researched [[Worker robot cargo size (research)|Worker robot cargo size]]-bonus, since bots will always take as much as they can carry if an unlimited amount is available.

=== Choosing the post for charging ===
Normally a robot flies to the nearest roboport to recharge. If the queue on that roboport is too long, they eventually choose another port. This is specified by the ratio of <distance to different roboport in tiles> / <queue size of robots waiting>.

Currently, to choose the more distant roboport, the distance must be at most <Number of robots in the queue and on the way> / 2. So, to choose a roboport that is 10 tiles more distant, it has to have 20 less robots waiting in the queue.

== Priorities of robots ==

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

Logistic robots on the logistic network look for orders by the chests in this order:

* A requested item is first ''looked up'' in the player's trash slots, then in active provider chests, then in the storage chests and buffer chests (only for character logistic slot requests), then the passive provider chests. So, the active provider chests are emptied first, then the storage chests and buffer chests, then the passive provider chests.

* Requests are ''assigned'' first for player logistics, then for requester chests, then for buffer chests.

* An item available from multiple sources with the same priority (multiple storage and buffer chests) will be taken from the closest.

{| class="wikitable"
! Source Priority
| {{icon|Character logistic trash slots (research)}} {{icon|active provider chest}} {{icon|storage chest}} {{icon|buffer chest}}1 {{icon|passive provider chest}}
! Target Priority
| {{icon|Character logistic slots (research)}} {{icon|requester chest}} {{icon|buffer chest}}
|}

(1) Player logistic slots only, same priority as storage chests

Storage chests will be filled with items from active provider chests, from robots that have had their orders cancelled while they were carrying items, and from the player's logistic trash slots. Furthermore, items deconstructed by construction robots will be placed into storage chests.

* To place items into storage chests, the bots search for a storage chest that already stores items of the same type, then for one which has its filter set to the item type. 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.

=== Distance ===
When looking to pick up requested items from multiple 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.

== Achievements ==
{{Achievement|you-have-got-a-package}}
{{Achievement|delivery-service}}
{{Achievement|logistic-network-embargo}}

[[Category:Logistic network]]

Tutorial:Circuit network cookbook

2018-05-27T18:20:57Z

Morsk: link directly to source post; it took me 10 mins to find, so this should help someone else

{{Languages}}
== Foreword ==

This page provides examples of simple circuit network designs and some not so simple designs that others can use, combine and modify. They are designed to be as easy to understand as possible. To see the settings of combinators without opening them, the option "Show combinator settings when detailed info is on" in the graphics options has to be checked and detailed info has to be turned on.

==Lamp showing chest content condition==
[[File:LightWiredToChest.png|right|218 × 412px]]

This is the simplest possible use of circuit-network. A lamp is light depending on the number of goods (in this example empty barrels) in a chest.

===Setting up circuit connection===
* The lamp is connected to the chest
* the lamp is set to light if the chest contain less than 10 empty barrels.
{{clear}}

[[File:LamponBarrelCondition.png|right|400x400px]]
===To set the light condition===
# open the lamp (left click on it)
# Set the input to barrels
# Set the operator to < (less than)
# Set the constant number:
## Left click on the constant number
## Move the slider until 10 is shown, or edit the value box directly
## Press set

Depending on the condition you set, the lamp may light if the chest is empty, or if it contains the required quantity of items.

The drawback with this scenario is that the lamp has a white light , and is therefore difficult to differentiate from an ordinary lamp at night.

== Oil Setups ==
[[File:LgtOilCracking.png|left|400x400px]]
=== Light Oil Cracking ===
* This circuit provides balanced light oil and petroleum gas production by cracking excess light oil into gas.
* The [[Pump]] is connected to the [[Storage tank]] by a [[Red wire]].
* The [[small pump]] has an enabled condition set to '''Light Oil > 2000'''.
{{clear}}

[[File:HvyOilCracking.png|left|400x400px]]

=== Heavy Oil Cracking ===
* This circuit extends on the previous circuit by adding optional heavy oil cracking to provide lubricant etc.
* The [[Pump]] has an enabled condition set to '''Heavy oil > 2000'''.
{{clear}}

[[file:BalancedPlasticSulfur.png|left|400x400px]]

=== Petroleum split evenly between plastic and sulphuric acid ===
* This circuit buffers gas in the tank until there is at least 100, then it lets the tank drain until there is less than 50 and the cycle repeats.
* It has a few elements that work together to do achieve this.
* Firstly the [[Pump]] is connected to the [[Wooden chest]] by a [[Red wire]] and the enabled condition on the [[Pump]] is set to '''Raw wood > 0'''.
* Both of the [[Inserter]]s are connected to the [[Storage tank]] by [[Red wire]]s.
* The enabled condition on the left inserter is '''Petroleum gas > 100'''
* The enabled condition on the right inserter is '''Petroleum gas < 50'''.
* You will need to insert a single "Raw wood" into the chest to make it all work.
 
* It is also possible to do this with [[decider combinator]]s instead of the inserters, belt and the Wood chest or even just belts.
{{clear}}

== Lights ==
[[File:ConditionalLights.png|left|400x400px]]
=== Conditional Lights ===
* In this circuit we connect a series of [[lamp]]s to a [[Storage tank]].
* By setting different conditions on each [[lamp]] we can build an indicator strip.
* The Enabled condition of the first [[lamp]] is '''Petroleum gas > 100'''.
* The others light up when gas is greater than 200, 300, 400 and 500 respectively.
{{clear}}

In this scenario you can connect the storage tank to the lamps directly.

[[File:ColoredLights.png|left|400x400px]]

=== Colored Lights ===
* To light a [[lamp]] with a color rather than white, you need an intermediate device like an [[Arithmetic combinator]] that can send a color signal.
Instead of directly connect the the [[Lamp]] and the [[Storage tank]] you need: 
1 Add the [[Arithmetic combinator]]. 
2 Connect the [[Storage tank]] with the input of the [[Arithmetic combinator]]. 
3 Connect the output of the [[Arithmetic combinator]] with the [[lamp]]. 
4 Set up the [[Arithmetic combinator]]: 
4.1 Setting the input to Petroleum Gas + 0 (the constant 0 not the signal 0) 
4.2 Set the output to the Pink signal (on the bottom row of the last tab of signals.) 
5 Set up the [[lamp]]: 
5.1 Select the "Use colors" check box on the lamp. 
5.2 Set the condition to the Pink signal, and what value you want (i.e. > 100) 
{{clear}}

== Misc ==
[[file:MulitipleChestsAndPoles.png|left|400x400px]]
=== Multiple Storages ===
* If you connect multiple chests to a pole, the pole displays the sum of items in all the chests.
* This also works with [[Storage tank]]s and [[roboport]]s.
{{clear}}

[[File:ConstantComb.png|left|400x400px]]

=== Constant combinator ===
* With a [[constant combinator]] you can generate any signals you may need.
* In this example we have generated a signal of 50 Laser turrets and 200 Piercing round magazine.
* Constant combinators are not of much use on their own but we shall use them later.
{{clear}}

[[File:LogicGates.png|left|400x400px]]

=== Logic gates ===
* In each case the two inputs can be connected with the same color wire or different colors. The inputs are powered by two [[Constant combinator]]s each of them output an A signal with value 1 for true and nothing or false.
* You can use [[Decider combinator]]s to make all of the common logic gates.
* The output for each should be set to 1 and the signal of your choice.
* Use the following settings to create different gates:
{{clear}}

NOT A=0
NOR A=0
NAND A<2
XOR A=1
AND A=2
OR A>0

{{clear}}

[[File:ThisASign.png|left|400x400px]]

=== Constant combinator signs ===
* You can use [[Constant combinator]]s to make signs, just set the letter signals in the combinator, each combinator can display 2 characters side by side.
{{clear}}

[[File:MemoryCell.png|left|400x400px]]

=== Memory Cell / Counter ===
* Basic memory cell that counts all the items moved by the inserter
* The [[Fast inserter]] is connected to '''BOTH''' ends of the arithmetic combinator.

* If the [[Fast inserter]] hasn't picked anything up this tick the input to the Arithmetic combinator is the same as and output and hence the values are persisted.
* When the [[Fast inserter]] does pick something up its value is added to the output from the previous tick thus incrementing that item.
{{clear}}

[[File:BeltCache.png|left|400x400px]]

=== Automatic Belt-Cache ===
* Some intermediate products are huge in demand during peak-production only. To bypass the need of providing a huge amount of factories in order to cover that peaks, a cache-unit can be used. The unit stores items while the belt has backed up (so there's obviously no current demand downstream) and releases items as soon as the belt gets too empty.
* The blue area is 3 parts of Express belts. According to the wiki, each belt can hold up to 7.11 items. This means the feeding fast belt can not provide 7.11 items for the express belts as long as the belt is moving. (And while the belt is moving, we don't want to cache items, but let regular production run, or even release items from the cache.)
* This means, once the counters on the two express belts are 7.11 each, the belt has backed up, so we can start "caching" items into our storage array.
* For this purpose, the counters are connected to the arithmetic combinator (A) which multiples the input (*100) into green signals. So, if the belt has backed up, B shows ">1422" green signals.
* This is the activation condition for the Belt (C), which will redirect the input tp the storage array.
* Since items should only be released if the belt starts to clear, the counter (D) is evaluated by the belt (E) which is only activated, if item-count on (D) is smaller than 6 (this number has to be adjusted to personal needs, when the cache should become "active" and release items)
* The layout can be extended to cache whatever amount of items is required. (Some balancing for the release-method would be required of course.)
{{clear}}

[[File:combinatorMultiplierDetailed.png|left|400x400px]]

=== Multiplier and Dictionaries/Arrays ===
* Multiplying two signals together is simple and requires only a single combinator, however multiplying a set of signals is more complicated.
* A proof is shown below for the equation and why it works.
* A dictionary is a system that allows a value on a specific signal to be accessed. For example, A can contain many signals (either from a constant combinator or memory cell) and B can contain 1 of a specific signal (such as blue signal). What remains is the blue-signal value from A. This is because all the other signals are multiplied by 0.
* Arrays are similar to dictionaries, but instead of using a signal as a key, we use a number. Constant combinators are placed mapping each signal to a unique number (such as 1 yellow belt, 2 red belt, 3 blue belt, 4 burner inserter, etc). Then, use a combinator of "each = index OUTPUT 1 of each" and plug that in as the input to a dictionary.
[[File:combinatorMultiplierMath.png|left|400x400px]]

((A+B)^2 - (A-B)^2)/4 = AB
(A+B)^2 - (A-B)^2 = 4AB
(A^2 + 2AB + B^2) - (A^2 - 2AB + B^2) = 4AB
4AB = 4AB

{{clear}}

== Inserters ==
[[File:LimitItemsPlacedIntoAChest.png|left|400x400px]]
=== Limit items placed into a chest ===
* The [[Inserter]] is connected to the [[Wooden chest]] using a [[Red wire]].
* The inserter's enabled condition is '''Advanced Circuit < 10'''.
* In reality this means the inserter may place more than 10 Advanced circuits in the chest because it could pick up to 3 at once due to stack size bonuses.
* This effect can be even greater with Stack inserters because of their large carrying capacity.
* This technique still gives far greater control than limiting the inventory on the chest.
{{clear}}

=== Balanced chest insert ===
Goal: Load n chests with approximately the same number of items.
* Place n chests and n inserters.
* Place 1 [[Arithmetic combinator]]
* Set the combinator to take Each (yellow star) and divide by the negative number of chests. ie −n.
* Connect all chests to each other and to the input of the combinator using red wire.
* Connect all inserters to each other and to the output of the combinator using red wire.
* Connect each inserter to the box it inserts into with green wire.
* Set the enable condition on each inserter to be Everything (red star) < 0.

The combinator calculates the average number of items in the chests, and makes it negative. Each inserter gets the amount in the chest it is inserting to and adds the negative average, ie it calculates how many more than the average it has in its chest. Thus if that number is negative, it has less than the average in the chest and it enables.

Due to inserter stack bonus the count is not exact. If a precise count is needed, set the inserter stack size to 1.

{{clear}}

[[File:SmartOutpostUnloader.png|left|400x400px]]
=== Keeping outpost stocked with specified items ===
* This circuit keeps a [[Storage chest]] at an outpost stocked with customized levels of different items.
* For example you could keep an outpost stocked with 50 laser turrets and 200 piercing magazine rounds but not have to worry about it being over filled.
* The [[storage chest]] is attached to the input of the [[Arithmetic combinator]] (left side in the picture) with a [[Red wire]].
* Another couple of [[Red wire]]s join the output of the [[Arithmetic combinator]] (right side) to the [[constant combinator]] and to the [[stack filter inserter]].
* The [[Arithmetic combinator]] '''multiplies''' each input value (from the storage chest) by '''-1'''.
* Finally the filter stack inserter's mode of operation is set to '''Set filters'''.
* So the input to the [[stack filter inserter]] is '''<Constant combinator> - <Storage chest contents>''' and the filter is set to filter the item of greatest demand.
{{clear}}

[[File:SolarAccumalatorBalancer.png|left|400x400px]]

=== Balanced Solar panel / Accumulator Production ===
* This circuit balances production of [[Solar panel]]s and [[Accumulator]]s to a desired ratio in my case 24:20.
* The first [[Arithmetic combinator]] takes the number of accumulators in the chest and '''multiplies''' it by '''24'''.
* The second [[Arithmetic combinator]] takes the output of the first combinator and '''divides''' it by '''20'''.
* This gives us the number of accumulators that we can directly compare to the number of Solar panels in both inserters.
* If the number of accumulators is greater we enable the Solar panels inserter, if the number of Solar panels is greater we enable the accumulators inserter.
* However, if they are equal, neither machine does anything. So we add a single accumulator to one of the inserters using a constant combinator and a wire of the other color, therefore breaking the deadlock.
{{clear}}

== Sushi Belts ==
[[File:SushiScience1.png|left|400x400px]]
=== Reading Belt Design ===
* Six belts in a row are connected with Red wire and set to '''Read belts contents''' and '''Hold'''
* This [[Red wire]] is then connected to the inserters that insert onto the belt.
* Read hand contents is unselected for all inserters.
* Mode of operation is set to '''Enable/Disable''' on all inserters.
* The first inserter is enabled when '''Science pack 1 = 0'''
* The other inserters are set similarly for the other science packs.
{{clear}}

[[File:SushiScience2.png|left|400x400px]]
=== Memory Cell Design ===
* This circuit counts the number of items of each type on a looping belt by counting the numbers that are added and removed from the belt by inserters.
* Each inserter that takes items off the belt is connected together with Red wire and each of these inserters is set to '''Mode of operation none, Read hand content selected''' and '''Hand read mode pulse'''.
* These inserters are connected to the input of the left arithmetic combinator.
* The left [[Arithmetic combinator]] multiples '''each''' input by '''-1''' and outputs it to '''each'''.
* The right [[Arithmetic combinator]] is a '''memory cell''' as above.
* The memory cell's input is connected to the inserters that are placing items on the belt and the output of the left [[Arithmetic combinator]].
* The inserters that place items onto the belt have an enabled condition that is based on the number of items on the belt.
{{clear}}

== Splitters ==

(These recipes are redundant with the addition of priority splitter functionality in 0.16)
[[file:CondSplitter.png|left|400x400px]]
=== Conditional splitter ===
* This is the simplest circuit you can have for "controlling" a splitter.
* A signal X=1 is transmitted from off screen when the items need to be sent down the belt.
* The belt on the left is enabled when X=1.
* The belt on the right is enabled when X=0.
* The two belts are wired together and to a pole.
{{clear}}

[[File:PrioritySplitter.png|left|400x400px]]

=== Priority Splitter ===
* This circuit prioritizes items to the belt going of the screen to the left but will send items straight on if the belt to the left is backed up.
* Its not perfect and will leak some items but its good enough for most applications.
* The balancer means it will work even if the supply or demand is uneven.
* It is critical that the belts are setup as in this picture otherwise it may not work.
{{clear}}

== Power ==
[[File:SteamBackup.png|left|400x400px]]
=== Backup steam power ===
* The [[steam engine]]s are not directly connected to the power network. They are connected to the power network through a [[Power switch]].
* The [[power switch]] is connected to one of the [[accumulator]]s in the main network.
* The [[power switch]] turns on when A < 10. That is when the [[accumulator]]s are less than 10% full.
{{clear}}
=== Optimal usage of fuel for nuclear power ===
Unlike the normal steam power that adjusts fuel usage based on power usage, the [[Power_production#Nuclear_power|nuclear reactors]] spend fuel in fixed units of time. To be exact, the consumption of 1 fuel cell takes exactly 200 seconds.

Combined with the fact that creating the nuclear fuel cells are time consuming and expensive to create, it is therefore beneficial to optimize their use to match the actual consumed power.

[[File:NuclearCircuits.jpg]]

The above picture shows a setup with 4 reactors, that spend only 1 fuel cell each whenever steam runs low.

There are a few elements in this setup:

* Storage tank that provides the [[Steam]] signal. You should only read from one storage tank, and it should have pipe connections to all your other steam storage tanks.
* Chests containing [[Uranium_fuel_cell|Uranium fuel cells]] for the reactor.
* Output inserters that take [[Used_up_uranium_fuel_cell|Empty fuel cells]] from the reactor. This is connected to the storage tank to listen for the steam signal, and to the chests to listen for the uranium fuel cell signal. If the steam level is low and there are uranium fuel cells available, it removes the empty fuel cells from the reactor and sends an empty fuel cell signal (since "Read hand contents" is checked).
* Input inserters that put uranium fuel cells into the reactor. This is connected to the output inserters and listens for the empty fuel cell signal. The "Override stack size" is set to 1, so that it only inserts 1 fuel cell at a time.

Since this design uses empty fuel cells as a signal to fill the reactor, you need to manually insert 1 uranium fuel cell into the reactor to get it started.

== Latches ==
=== RS latch - single decider version ===
[https://forums.factorio.com/viewtopic.php?f=193&t=14556 This discussion] on the Factorio forums starts with the common 2 decider RS latch version, but the thread [https://forums.factorio.com/viewtopic.php?p=160896#p160896 goes on to explain] why this single decider version is better. In the thread, the latch is described as an SR latch. However, when both inputs are true, the latch will reset, so it is an RS latch.
==== Backup steam example ====
This example will turn on the steam generator when the Accumulator charge drops to 20%, but will "latch" (remember) the On state until the accumulator is charged to 90%.

Latching is used to introduce [[Wikipedia:hysteresis|hysteresis]] and avoid the power switch rapidly cycling on and off (as the accumulator falls to 19%, charges to 20%, falls to 19% and so on).
[[File:SR-01-Layout.png|left]]

 
<div class="toccolours mw-collapsible mw-collapsed" style="width:50em;">
Blueprint string for above backup steam example
<div class="mw-collapsible-content"><pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
0eNrFVk1vozAQ/SuVz1ABCaRBq5WqXntKjqsKOTBJR8IGGTtpFPHfd+w0HyU0G6pVewkxnnmemfdmzI4tSgO1QqlZumOYV7Jh6Z8da3AleWnf6W0NLGVrVNrQG49JLuyLvYU/Z63HUBbwxtKw9QZ4zs48o15P1CBObgXkWIDy80osUHJdqTOAUfviMZAaNcI+A7fYZtKIBSiK7YgjoEAjfCgh1wpzv65KoFPqqiHnStrzCdAPA49t6Rm1NrYOWjQY7QrY6FQZwcvyX1jJFajxEYrnuRGmdGW6DCe+jx1KcB9TDYl1raoyW8ArXyM5kFVldG10djObj6zdI0kKHp2Mdiy0PysFIM8pwYKldHyOKjeo3TI8y8Wup93tl7Yv3fiaOC6zjt6z9uk4VqDaR+rY7CvBO2ZGewUec1qiaobVxaE3mtseiwK7EjVXLsaU/SKPobWe7zHrLYVmpM6WqhIZSsJg6ZKXDQyiYkzF9Vhk9xUU3d3kNiaSQUwEB/l9Hw+uZg1YjGzYiPpA1+/vpKuHjk7fRNf7JrJTsZf05MLwoIFbzLvtOvlEFZNjKepqQ5poNqjz10s9jA6N+fk8Ohx/FMFXNXDqxeCC20F901vCJxN07UjVG9K4+x9YQp5M2LUZfbTpq+XDKRsNnG4cuULZcz089HZWD+D0a8Pz52bnNPgPzTj76dlJAnDfNenZp5fHSr4ACp/NZ3fPnHrkDt64qN31vwbVuFIn43GUjCdxHIVt+xcL2lBp</pre></div></div>
 
[[File:SR-02-Accumulator.png|left]]Accumulator outputs the current charge level as % on signal [[File:Signal-A.png]]
 
[[File:SR-03-RangeDeciders.png|left]]First decider outputs "Set" ([[File:Signal-S.png]] = 1) if Accumulator is less than 20%.
Second decider outputs "Reset" ([[File:Signal-R.png]] = 1) once Accumulator is more than 90% full.
 
[[File:SR-04-SRLatch.png|left]]
==== RS Latch configuration ====
'''The central decider and green feedback wire is the actual RS Latch.'''
It latches the Set signal [[File:Signal-S.png]] until the Reset signal [[File:Signal-R.png]] is received (and vice-versa). 
NB: the latch expects binary inputs ([[File:Signal-S.png]] & [[File:Signal-R.png]] must be 0 or 1) - this is why the previous two deciders are required. 
When both inputs are true, the reset signal takes priority and the latch resets. This means it is an RS latch instead of an SR latch.
 
[[File:SR-05-PowerSwitch.png|left]]The Power switch isolates the generator from the rest of the factory until [[File:Signal-S.png]] = 1
 
----

=== RS latch ===
[[File:SRLatch.png|left|400x400px]]
* This should be familiar to anyone with any background in electronics.
* The signal is set and reset with the [[constant combinator]]s on the left by setting an A=1 signal.
* The latch "remembers" which one was last set and the light stays on until another signal is received.
{{clear}}

[[File:SRlatchinaction.png|left|400x400px]]

=== Usage of RS latch ===
* Here is an example of how you could use an RS latch.
* The two extra [[Decider combinator]]s provide the set and reset conditions.
* Petroleum gas < 50 and petroleum gas > 100.
{{clear}}

[[File:BeltLatch.png|left|400x400px]]

=== Belt only latch ===
* This is the most compact latch I am aware of.
* To make it work you need to place '''3''' raw wood on the inside lane of the belt.
* I believe it will have higher latency than the combinator version but in most situations you will not notice the difference.
{{clear}}

== Displays ==
[[File:5digitDisplay.png|left|400x400px]]
=== Numerical Display ===
* Each digit is driven by its own [[Green wire]], that wire holds 15 signals one for each lamp used in the digit.
* [[Constant combinator]]s are used to define which lamp should light up for each value.
* Blueprint string including decoder [https://www.dropbox.com/s/5o13xuwthalzzfe/Brain2.txt?dl=0]
{{clear}}

[[File:BWDisplay.png|left|400x400px]]

=== Black and White Grid Display ===
* Each row has its own [[Red wire]] connection and within that row each light has a numbered signal 0-9.
* We turn each light on by just setting or clearing the relevant signal.
{{clear}}

[[File:MultiColoredDisplay.png|left|400x400px]]
=== Multicolor Display by DaveMcW ===
* To understand how this works, you first need to understand how color lights choose which color to light up when there are multiple colored signals.
* The [[lamp]] will light up with the colored signal that is greater than zero and earliest in this list: Red, Green, Blue, Yellow, Pink, Cyan, White.
* We have a [[Red wire]] per column, that wire has each of the colored signals on it at different values and a numbered signal for each row.
* There is a [[Arithmetic combinator]] for each cell that subtracts the "row" value from each of the colored signals.
* And this enables us to choose the color for each cell.
* Simple!
{{clear}}

== See Also ==
* [[Arithmetic combinator]]
* [[Constant combinator]]
* [[Decider combinator]]
* [[Circuit network]]