Official Factorio Wiki - User contributions [en]

Settings

2024-11-21T22:36:38Z

Mwls: Create page for describing how Factorio settings work, and document the existence of hidden settings

{{stub}}

== Hidden settings ==

Factorio supports a number of hidden configuration options that are not normally shown in the GUI. They can be accessed by holding CTRL + ALT when clicking the "Settings" button in the pause menu, which will cause a new button labeled "The rest" to appear.

These settings may be experimental and may not be validated for safety, so change them at your own risk.

{| class="wikitable"
|+ Notable hidden settings
|-
! Name !! Default !! Description
|-
| autosave-slots || 3 || How many autosaves to keep on a rolling basis
|-
| non-blocking-saving || false || Only works on Mac and Linux. When set to true, saves do not cause to game to pause. [https://forums.factorio.com/viewtopic.php?t=57464]
|-
| technology-gui-pauses-game || true || By setting to false, the game will no longer pause in single player when opening the technology tree.
|}

Console

2024-11-04T08:32:09Z

Mwls: /* Scripting and cheat commands */ Expanded /cheat command

{{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 <span style="color:#FF0000">disable achievements for the save game</span>)

__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
|-
| /enable-research-queue
| /enable-research-queue
| Enables the [[research]] queue.
| Yes
|-
| /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 <span style="color:#FF0000">achievements will be permanently disabled for the save</span> 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 = "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>

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

Inserters

2023-02-06T08:47:27Z

Mwls: /* Chest to splitter */ Add second image example

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

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

== Types of inserters ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Inserter Throughput==

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

{{BlueprintString|bp-string=0eNrtXF1v4kYU/SuRq75UkMz32GhbKY996FvfuivkwBCsBYNss20U8d87NiHAwMVzHdjsKKtIURzb1zPn3K85Y3iOHmYrsyyyvIoGz9HYlKMiW1bZIo8G0V8mLVeFKW+yvDRFZYqbalosVo/T5aq6WeVj+49xNpmYwuTVzWiRj7P6xvL2c/45n1bVshzc3f2bfc1uJ+moWhTZ4na0mN/9+WKs/GX71/DvV7Of86gXZdZWGQ3+eY7K7DFPZ/XIqqelsUPKKjO3V+TpvD4qq3T0tb8dXbS2t9pR/RcN6LrXenNaZNV0bqps1LfDesjy1I5xzwZbf+lFdmZ2UmYzmubgaZiv5g/2aQPaYqoXLRdltsHyObIW+/pW9qIn+we3jxlnhRltzopeZKdcFYvZ8MFM02+ZvdvesjM73KFbn5hkRVkNj+b3LSuqlf3PDp/miv59PavS1DZqQxa1mm1KetFiaYr0he07e99iVVkSUJbX62bw+WYuzfBo/asw433QMnvE7ZVZMVplVXNI11/svQy4mEp7el3z6MDO0LCr94HdpKPpHvI4uvaZ+fSpAzWbpyPYkUfs9KLHwpi8hUa2o/Hk5VQBRHI0kfJHjp9frx4/1GWod3Ca8RYm2HH8neJFoHnhHzuvKUxea1g6BbtEw85+5jUPdtj5qNFgnlO4PMcEQKxCE0s/dp4T5xnjtIUJ6Zfn9Osot5M9zwrZsmLjbn2aiUk2qzvb070rBA6JGmurGuw+JVonXFEWtzSzkDV6YI3HgjLC2V5XizHGDowlhBCaaLqzxlHW+J41O0+uBY2ZeDUmUMbEwdCojmWSiD1rEmVNHnKQCE05FztrCmVN7VljVHAWJ/vGNMqYPhialDROmIjJq7UYZS0+sKY4lbFgUr1aS1DWkgNrzP5IHu9ZowRl7v7kVHfWNoHftZ89zCKJX5KIscmbfOxeiFJMM8Qh2BMs7PRnL+TBDtzsuLy1dTucAczVLvcyyrEZZWNTnOVNvLDWlNQ93tRp3l5Mvo20NH+qpln+uMk221gh9cF8mRbNQAfRHx0IqSFvjC6fhk0eG06KxXyY5dZKNJiks9JAbJ1mhZ/XSNgRaRC9nms/iha12MfuVeOWXjVpiSPPMkTRqpfY71XbA+tSvLxEwBEzfXrIzG9dowsXPwTMaqfC6ehqh0zlSRaHFOojlnT7mmL7xPlibIaLyXAPxT0lrjDpeDhNN5hXdkAWmapYmd0VzcnmstpS46rdgQSnvhOPynk6m/Vn6Xx5Yi0Vb+dNt/P2G4cg0IN38sncjLPVvG9m1mJho2S5mJlzQyDgENo1uKYK2ieb7HH6sFg1Sz/Ge5x+OTVG5QeOPgIHdIrXWO0QquR8/fsUoUKNnY8dGkPEaT9Q1PcBhV4UFJpAs46RrkCuOmt22Vkrh3wBNosJkvzrwsAvC4N2YYCkX0b8YJBBJgaIfEb9Zi261goNPZgh4b6u14nLwk1cr4P23xjHlkzRqWTy8y2yaK+otrjz5FRFZZ7tBg8xcOT5ispAXqUfKCzEisrAoFZIVwipojLhkC+hPphpJPkhVVQmXRigdQjz7K9oiImBg+R7tlOkY0WV0Ds5nCDhDqqixq7XQTu9nGIrKulUUdX5ihq/oaJyv96IhBg3SYu8A9LKvTChIdZTDoa0wDlCSOWUu9RLSJ3gEkd9SNWUcxcFSK3gqsueDv2eezqvOy8/yHaO327N2a0B5blnw/1aPhZkqwMGZoybdEgNB3eFIwUJRzxBNhy8m+jd8uap1m9QxQXBbRkQXM9K3aWTAN97pbiB4LcuHFahBbxgOHH4ur4tLyuKus20gLouwXHa8HVRUJfeF3BQgNowIXC+cN3kri+KgnDbMAWJO0LifIEG1IYJtw1TUM0TCqdbh5QXmOsLAkRB47YNkPWCHenTUFcsYhwd13XK+LJO6W7hKRCFBEcHfhPH6TUg8UsSnAAcVHS4dEhoU01SnP4bUtVkri9I8LM0DOcLIVVN6faRGmpoJcf5QkhVUx6tQcCIEDhtOqS8wF1fkNCaQkrc1gC2aroNrYRaOalwdIRUNaW71tRggtI4OvAbNc5AoFWWjFEyb1DB4bKhwNYhQam8IdVM7nqCgqqFIihPCKpkuqKDhpbbiqI8IaiK6aZoDdUKxTrI/cRV+9n3VPv5ETaXVvvrl6lxkafObzcqhnk3XQnfr2fw3TZQHKWgB5X53XhXYLyLDq5O39XVXWx+7/YZl4tta6mWN7/dzYG2T2+fuv4kdRLlvyH1kcqVBDUkhimF27NgSPUFBF/jZGl2VfSTy2pfwleQVTFOlr4uCveXRUEei/OekqBKcMIoC6i0iNjXOTTBCaPY0ITQ1xSnfYUUmpL5qj6a4bSvkEJT8mMF0FN30BynvoQUmlJ5O4fAqS/I0AS1Ly1RS+yQIlMR39WlVqgldkiBqeixzuDZyGndYSHC3nUhwi6w5r7vuOJ+2wpZ4FYs51fm9Uf8e29bymjcy2whJWUlT+cFC1nzdayDvS+g7UWz9MHYMUbbb4a9eUxXj/VrbN9MUW48PKZCJ0xLQbkkcr3+HxANddo=}}

===Chest to chest===

'''Note:''' Experimental data from 0.18

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

===Chest to belt===

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

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

'''Note:''' Experimental data from 0.18

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

===Chest to splitter===

When an inserter drops items onto the side of a perpendicular splitter, it always is considered to do so on the input side, enabling the splitter to move half of the items to the other belt (assuming that the splitter filter/priority settings allow it to do so and that there is available space on both belts). This allows the inserter to drop its items twice as fast. A fully upgraded stack inserter can drop twelve items onto an express splitter every 38 ticks (18.95 items/second) instead of the usual 52.

[[File:Inserter to splitter comparison.png|621px|thumb|center|By inserting onto the side of a splitter, a fully-upgraded stack inserter can fill 84% of an express belt lane instead of the usual 62%.]]

[[File:Inserter belt saturation.png|414px|thumb|center|Three stack inserters can saturate an express belt if one of them inserts onto a splitter.]]

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

'''Note:''' Experimental data from 0.18

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

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

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

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

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

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

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

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

'''Note:''' Experimental data from 0.18

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

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

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

{{C|Inserters}}

Bulk inserter

2023-02-06T08:17:42Z

Mwls: Simplify timing information (since full numbers are on linked page); remove misleading statement (since 3 inserters can fully saturate a blue belt when using a splitter)

{{Languages}}
{{:Infobox:Stack inserter}}
The '''stack inserter''' is an electric inserter that can move multiple items at the same time. Moving at the speed of the [[Fast inserter]], it transfers multiple items per cycle to give it a material flow advantage at the cost of additional power consumption.

When transferring between chests or [[cargo wagon]]s it picks up and drops off the entire stack of items instantly. When picking up from or dropping off items onto a [[transport belt]] a stack inserter needs to grab or drop each item individually, increasing the time between arm swings and lowering its potential throughput. In these cases, however, the stack inserter still has higher throughput than a [[fast inserter]] because it swings back and forth less often. The throughput from [[Inserters#Chest_to_chest|chest to chest]] for a fully upgraded stack inserter is 27.69 items per second, but only 13.85 items/s from [[Inserters#Chest_to_belt|chest to express belt]].

== Stack size ==

The stack size is increased by the [[Inserter capacity bonus (research)]] technology. The stack size can be overridden to set how many items it picks up at one time, with the maximum being the highest research level currently unlocked.
{| class="wikitable"
! Inserter capacity bonus
! Stack size bonus
! Total stack size
|- align="center"
| align="left"| none || 0 || 2
|- align="center"
| align="left"| 1 || +1 || 3
|- align="center"
| align="left"| 2 || +1 || 4
|- align="center"
| align="left"| 3 || +1 || 5
|- align="center"
| align="left"| 4 || +1 || 6
|- align="center"
| align="left"| 5 || +2 || 8
|- align="center"
| align="left"| 6 || +2 || 10
|- align="center"
| align="left"| 7 || +2 || 12
|-
|}

== History ==
{{history|0.15.0|
* Added stack inserter override feature.}}

{{history|0.13.7|
* Updated stack inserter tech icon.}}

{{history|0.13.6|
* Now unlocked by their own research.}}

{{history|0.13.0|
* Introduced}}

== See also ==
* [[Stack filter inserter]]
* [[Electric system]]
* [[Inserters]]

{{LogisticsNav}}
{{C|Inserters}}

Tutorial:Circuit network cookbook

2023-01-18T23:36:39Z

Mwls: /* Set train routing */ Mostly remove section because dynamic train limits are generally more recommended than enabling/disabling stations. The content can be rewritten but in the meantime I wanted to avoid leading people astray and I couldn't find a great concise existing tutorial to link people to

''This is a '''beginners''' tutorial. See also the [[Circuit network]] page for an overview over the circuit network and the [[Tutorial:Combinator tutorial]] for an advanced tutorial.''
{{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 in "Alt-mode"" in the Interface/Alt-mode settings has to be checked and "Alt-mode" has to be turned on.

== Lights ==
[[File:LightWiredToChest.png|border|left|430px]]

=== Lamp showing chest content condition ===

This is one of 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 ====
<div style="margin-left:440px;">
* The lamp is connected to the chest.
* The lamp is set to light if the chest contain less than 10 empty barrels.

==== To set the light condition ====
* Open the lamp (left click on it).
* Set the input to barrels.
* Set the operator to < (less than).
* Set the constant number:
** Left click on the constant number
** Move the slider until 10 is shown, or edit the value box directly.
** Press set.

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

The drawback with this scenario is that the lamp has a white light , and is therefore difficult to differentiate from an ordinary lamp at night.
</div>
{{clear}}

[[File:ConditionalLights.png|border|left|430px]]

=== Conditional Lights ===
<div style="margin-left:440px;">
* 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.

In this setup you can connect the storage tank to the lamps directly.
</div>
{{clear}}

[[File:ColoredLights.png|border|left|430px]]

=== Colored Lights ===
<div style="margin-left:440px;">
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 [[lamp]] and the [[Storage tank]] you need:
# Add the arithmetic combinator.
# Connect the [[storage tank]] with the input of the arithmetic combinator.
# Connect the output of the [[arithmetic combinator]] with the lamp.
# Set up the arithmetic combinator:
## Setting the input to petroleum Gas + 0 (the constant 0 not the signal 0)
## Set the output to the pink signal (on the bottom row of the last tab of signals.)
# Set up the [[lamp]]:
## Select the "Use colors" check box on the lamp.
## Set the condition to the pink signal, and what value you want (i.e. > 100)
</div>
{{clear}}

== Oil Setups ==
Balancing the production of petroleum gas, light oil and heavy oil is one of the most important use cases of the circuit network.

[[File:LgtOilCracking.png|border|left|430px]]

=== Light Oil Cracking ===
<div style="margin-left:440px;">
* This circuit provides balanced light oil and petroleum gas production by cracking excess light oil into gas.
* The [[pump]] is connected to the [[storage tank]] by a [[red wire]].
* The pump has an enabled condition set to '''Light Oil > 20000'''.
</div>
{{clear}}

[[File:HvyOilCracking.png|border|left|430px]]

=== Heavy Oil Cracking ===
<div style="margin-left:440px;">
* This circuit extends on the previous circuit by adding optional heavy oil cracking to provide lubricant etc.
* The pump has an enabled condition set to '''Heavy oil > 20000'''.
</div>
{{clear}}

=== Alternative Setup for Cracking and Lubricant Production ===
This setup compares different fluid levels to each other instead of checking fixed values. It offers some guarantees such as petroleum gas being produced when you have light oil to spare, and light oil not being cracked when you have plenty of petroleum gas, and similar rules for heavy oil cracking and lubricant production.

[[File:oil-single-cct.png|border|left|430px]]

<div style="margin-left:440px;">
It takes 4 steps:

# Have a fluid tank for heavy oil, light oil, petroleum gas, and lubricant. For each fluid, make sure to connect the tank via pipes to every location where the fluid is being produced or consumed.
# For each chemical plant (or each row of them, if you use rows) add a pump to the non-water fluid input pipe to make it possible to block the flow. Note: Alternatively, the blocking pumps could be added to the chemical plant output pipes, but there is no need to add pumps to both inputs and outputs.
# Connect every pump and every fluid tank to a single circuit network of red (or green) wire. The resulting circuit network will know about the fluid level in every storage tank and pass this information to every pump.
# For each connected pump set the circuit “enable condition” to "[input fluid] > [output fluid]" , for its respective chemical plant recipe. E.g. set "heavy oil > light oil" for the heavy oil cracking input pump, set "heavy oil > lubricant" for the lubricant production input pump, and set "light oil > petroleum gas" for the light oil cracking input pump.

Done! Now all the pumps will move to equalize the fluid levels to each other. This will prevent fluid system deadlocks where you have plenty of one fluid but you are unable to make any of the other.
</div>
{{clear}}

== Misc ==
[[file:MulitipleChestsAndPoles.png|border|left|430px]]

=== Multiple Storages ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:ConstantComb.png|border|left|430px]]

=== Constant Combinator ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:ThisASign.png|border|left|430px]]

=== Constant Combinator Signs (Words) ===
<div style="margin-left:440px;">
* 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.
* Note that to see these letters, Alt-mode must be on and the Interface setting “Show combinator settings in “Alt-Mode”” must also be enabled.
</div>
{{clear}}

[[File:constant_combinator_signs2.png|border|left|430px]]

=== Constant Combinator Signs (Managing Belts) ===
<div style="margin-left:440px;">
* Somewhat similar to the previous example, constant combinator signals can be used with belts to help indicate what items should be on which belts. This is extremely useful when sharing blueprints, as it's possible for blueprints to be shared albeit with no indication on which items are meant for which belts.
</div>
{{clear}}

[[File:MemoryCell.png|border|left|430px]]

=== Memory Cell / Counter ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

== Inserters ==
[[File:LimitItemsPlacedIntoAChest.png|border|left|430px]]

=== Limit items placed into a chest ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:BalancedChestInsert.png|border|left|430px]]

=== Balanced chest insert ===
<div style="margin-left:440px;">
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, i.e. 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.
</div>
{{clear}}

[[File:SmartOutpostUnloader.png|border|left|430px]]

=== Keeping outpost stocked with specified items ===
<div style="margin-left:440px;">
* 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 for the first item by inventory order.
</div>
{{clear}}

[[File:SolarAccumalatorBalancer.png|border|left|430px]]

=== Balanced Solar panel / Accumulator Production ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

== Sushi Belts ==
[[File:SushiScience1.png|border|left|430px]]

=== Reading Belt Design ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:SushiScience2.png|border|left|430px]]

=== Memory Cell Design ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

== Power ==
[[File:SteamBackup.png|border|left|430px]]

=== Backup steam power ===
<div style="margin-left:440px;">
* 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.
</div>
{{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:Nuke.png|border|left|430px]]
<div style="margin-left:440px;">
This picture shows a setup with 4 reactors, that spend only 1 fuel cell each whenever steam runs low.<br>
''Note: The GUI in the image above has been altered to make sure all important info fits within the image size.''

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]]s for the reactor.
* Output inserter that takes [[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 inserter that put uranium fuel cells into the reactor. This is connected to the output inserter 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.
* If you are using multiple reactors you should only wire one output inserter to one steam tank, and then connect all input inserters to the single output inserter. This will synchronize fuel insertion to maximize the reactor neighbour heat bonus. The other reactors can have "dumb" output inserters that remove [[Used_up_uranium_fuel_cell|empty fuel cells]] immediately.

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.
</div>
{{clear}}

=== Prioritize usage of uranium towards nuclear fuel production ===
Because a continuous supply of [[nuclear fuel]] is critical to maintaining a [[nuclear reactor]], the circuit network can be used to set up a system where [[uranium-235]] and [[uranium-238]] are conserved for the production of nuclear fuel before other uses.

[[File:Nuclear Fuel Circuit Network.png|border|left|430px]]
<div style="margin-left:440px;">

Using a [[splitter]], divert the two types of uranium onto two parallel conveyors, with an [[inserter]] positioned to gather uranium from each conveyor (a [[long handed inserter]] will be needed for the far belt). Each of these inserters deposits their load into a container, from which two more inserters deliver the contents to an [[assembly machine]] making nuclear fuel. An inserter delivers the produced fuel to a third container, from which inserter(s) delivers the fuel to your nuclear reactor. Wire the two inserters gathering from the conveyors to the container each of them is delivering to, and to the tile of conveyor immediately after the tile the inserter is gathering from. Set each inserter's enable condition to "less than or equal to X amount of uranium", using the appropriate type of uranium the inserter is gathering and X being the number of reserve uranium desired (optimally, one uranium-235 and nineteen uranium-238, the amount needed to produce nuclear fuel; the amount may be increased if a greater stockpile is desired). Set each conveyor's enable condition to "greater than or equal to X amount of uranium" in the same manner. Finally, connect the inserters delivering uranium to the assembly machine up to the container the assembly machine is delivering nuclear fuel to, and set each of their enable conditions to "nuclear fuel = 0 (the enable condition can be set to "less than or equal to X amount of nuclear fuel" if a larger stockpile is desired).

This set-up accomplishes the following:

* When there is sufficient nuclear fuel and uranium stockpiled, the inserters will deactivate and the conveyors activate, allowing the uranium to continue down the conveyors to other facilities.
* When the nuclear fuel stockpile hits zero (or decreases below the desired amount), the inserters delivering to the assembly machine will activate and deliver uranium to resume production of nuclear fuel until quota is reached again.
* When there is not enough uranium stockpiled to produce a batch of nuclear fuel, the inserters gathering uranium will activate and and resume gathering uranium until they reach their quota. The conveyors carrying uranium will stop past the inserters, cutting off other facilities from that type of uranium until its respective inserter reaches quota.
* The assembly machine will only be provided with uranium when the stockpile of nuclear fuel hits zero (or decreases below the desired amount), preventing over-production of nuclear fuel and thus over-consumption of uranium.
</div>
{{clear}}

== Railway network ==
=== Set train routing ===
The circuit network can be used to allow deeper micromanagement of [[train]]s. Circuits can be used to adjust train limits for [[Train stop|stops]], effectively disabling a stop when a resource is not available for loading, or if an unloading station already has more than enough of a resource. Note that adjusting train limits runs into fewer problems than fully enabling/disabling stops; see [https://factorio.com/blog/post/fff-361 Friday Facts #361 - Train stop limit, Tips and tricks] and the [[Train stop]] page for additional information about using train limits.

=== Player safety ===
The circuit network can be used to ensure the player's safety when crossing train tracks so they do not get hit. Place [[gate]]s at designated crossing areas and connect an adjacent [[wall]] to [[rail signal]]s near the gate. Set the gate to "read sensor" and the signal to "close signal" with the condition being the signal the gate sends out being "1". This means that when the gate is closed, the signal will be green and trains can pass freely, but when the player approaches the gate and it opens for them, the train signal will be turned red and trains will be stopped until the player clears the area.

Alternatively, this system can be reversed - by setting the gate to "open gate" and the train signal set to "read signal", the gate will remain open normally and will close when a train is approaching, preventing the player from crossing until it is safe.

In lieu of gates, the player can connect a [[programmable speaker]] to the train signals to broadcast a warning siren when a train is approaching the area.

== 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|850px|left]]
{{clear}}
{{BlueprintString|bp-string=0eNrFVk1vozAQ/SuVz1ABCaRBq5WqXntKjqsKOTBJR8IGGTtpFPHfd+w0HyU0G6pVewkxnnmemfdmzI4tSgO1QqlZumOYV7Jh6Z8da3AleWnf6W0NLGVrVNrQG49JLuyLvYU/Z63HUBbwxtKw9QZ4zs48o15P1CBObgXkWIDy80osUHJdqTOAUfviMZAaNcI+A7fYZtKIBSiK7YgjoEAjfCgh1wpzv65KoFPqqiHnStrzCdAPA49t6Rm1NrYOWjQY7QrY6FQZwcvyX1jJFajxEYrnuRGmdGW6DCe+jx1KcB9TDYl1raoyW8ArXyM5kFVldG10djObj6zdI0kKHp2Mdiy0PysFIM8pwYKldHyOKjeo3TI8y8Wup93tl7Yv3fiaOC6zjt6z9uk4VqDaR+rY7CvBO2ZGewUec1qiaobVxaE3mtseiwK7EjVXLsaU/SKPobWe7zHrLYVmpM6WqhIZSsJg6ZKXDQyiYkzF9Vhk9xUU3d3kNiaSQUwEB/l9Hw+uZg1YjGzYiPpA1+/vpKuHjk7fRNf7JrJTsZf05MLwoIFbzLvtOvlEFZNjKepqQ5poNqjz10s9jA6N+fk8Ohx/FMFXNXDqxeCC20F901vCJxN07UjVG9K4+x9YQp5M2LUZfbTpq+XDKRsNnG4cuULZcz089HZWD+D0a8Pz52bnNPgPzTj76dlJAnDfNenZp5fHSr4ACp/NZ3fPnHrkDt64qN31vwbVuFIn43GUjCdxHIVt+xcL2lBp}}
{{clear}}
[[File:SR-02-Accumulator.png|left]]Accumulator outputs the current charge level as % on signal [[File:Signal-A.png|21px]]
{{clear}}
[[File:SR-03-RangeDeciders.png|left]]First decider outputs "Set" ([[File:Signal-S.png|21px]] = 1) if Accumulator is less than 20%.
Second decider outputs "Reset" ([[File:Signal-R.png|21px]] = 1) once Accumulator is more than 90% full.
{{clear}}
[[File:SR-04-SRLatch.png|left]]

==== RS Latch configuration ====
'''The central decider and green feedback wire is the actual RS Latch.'''
It latches the Set signal [[File:Signal-S.png|21px]] until the Reset signal [[File:Signal-R.png|21px]] is received (and vice-versa).<br />
NB: the latch expects binary inputs ([[File:Signal-S.png|21px]] & [[File:Signal-R.png|21px]] must be 0 or 1) - this is why the previous two deciders are required.<br />
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.
<br clear=all>
[[File:SR-05-PowerSwitch.png|left]]The Power switch isolates the generator from the rest of the factory until [[File:Signal-S.png|21px]] = 1
<br clear=all>
----

[[File:SRLatch.png|border|left|430px]]

=== RS latch ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:SRlatchinaction.png|border|left|430px]]

=== Usage of RS latch ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:BeltLatch.png|border|left|430px]]

=== Belt only latch ===
<div style="margin-left:440px;">
* To make it work, '''3''' pieces of raw wood must be placed on the inside lane of the belt.
* It will have higher latency than the combinator version, but in most situations you will not notice the difference.
</div>
{{clear}}

== Displays ==
[[File:5digitDisplay.png|border|left|430px]]

=== Numerical Display ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:BWDisplay.png|border|left|430px]]

=== Black and White Grid Display ===
<div style="margin-left:440px;">
* 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.
</div>
{{clear}}

[[File:MultiColoredDisplay.png|border|left|430px]]

=== Multicolor Display by DaveMcW ===
<div style="margin-left:440px;">
* 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!
</div>
{{clear}}

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

Inserters

2023-01-17T20:44:16Z

Mwls: Add description of inserter-onto-splitter performance

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

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

== Types of inserters ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Inserter Throughput==

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

{{BlueprintString|bp-string=0eNrtXF1v4kYU/SuRq75UkMz32GhbKY996FvfuivkwBCsBYNss20U8d87NiHAwMVzHdjsKKtIURzb1zPn3K85Y3iOHmYrsyyyvIoGz9HYlKMiW1bZIo8G0V8mLVeFKW+yvDRFZYqbalosVo/T5aq6WeVj+49xNpmYwuTVzWiRj7P6xvL2c/45n1bVshzc3f2bfc1uJ+moWhTZ4na0mN/9+WKs/GX71/DvV7Of86gXZdZWGQ3+eY7K7DFPZ/XIqqelsUPKKjO3V+TpvD4qq3T0tb8dXbS2t9pR/RcN6LrXenNaZNV0bqps1LfDesjy1I5xzwZbf+lFdmZ2UmYzmubgaZiv5g/2aQPaYqoXLRdltsHyObIW+/pW9qIn+we3jxlnhRltzopeZKdcFYvZ8MFM02+ZvdvesjM73KFbn5hkRVkNj+b3LSuqlf3PDp/miv59PavS1DZqQxa1mm1KetFiaYr0he07e99iVVkSUJbX62bw+WYuzfBo/asw433QMnvE7ZVZMVplVXNI11/svQy4mEp7el3z6MDO0LCr94HdpKPpHvI4uvaZ+fSpAzWbpyPYkUfs9KLHwpi8hUa2o/Hk5VQBRHI0kfJHjp9frx4/1GWod3Ca8RYm2HH8neJFoHnhHzuvKUxea1g6BbtEw85+5jUPdtj5qNFgnlO4PMcEQKxCE0s/dp4T5xnjtIUJ6Zfn9Osot5M9zwrZsmLjbn2aiUk2qzvb070rBA6JGmurGuw+JVonXFEWtzSzkDV6YI3HgjLC2V5XizHGDowlhBCaaLqzxlHW+J41O0+uBY2ZeDUmUMbEwdCojmWSiD1rEmVNHnKQCE05FztrCmVN7VljVHAWJ/vGNMqYPhialDROmIjJq7UYZS0+sKY4lbFgUr1aS1DWkgNrzP5IHu9ZowRl7v7kVHfWNoHftZ89zCKJX5KIscmbfOxeiFJMM8Qh2BMs7PRnL+TBDtzsuLy1dTucAczVLvcyyrEZZWNTnOVNvLDWlNQ93tRp3l5Mvo20NH+qpln+uMk221gh9cF8mRbNQAfRHx0IqSFvjC6fhk0eG06KxXyY5dZKNJiks9JAbJ1mhZ/XSNgRaRC9nms/iha12MfuVeOWXjVpiSPPMkTRqpfY71XbA+tSvLxEwBEzfXrIzG9dowsXPwTMaqfC6ehqh0zlSRaHFOojlnT7mmL7xPlibIaLyXAPxT0lrjDpeDhNN5hXdkAWmapYmd0VzcnmstpS46rdgQSnvhOPynk6m/Vn6Xx5Yi0Vb+dNt/P2G4cg0IN38sncjLPVvG9m1mJho2S5mJlzQyDgENo1uKYK2ieb7HH6sFg1Sz/Ge5x+OTVG5QeOPgIHdIrXWO0QquR8/fsUoUKNnY8dGkPEaT9Q1PcBhV4UFJpAs46RrkCuOmt22Vkrh3wBNosJkvzrwsAvC4N2YYCkX0b8YJBBJgaIfEb9Zi261goNPZgh4b6u14nLwk1cr4P23xjHlkzRqWTy8y2yaK+otrjz5FRFZZ7tBg8xcOT5ispAXqUfKCzEisrAoFZIVwipojLhkC+hPphpJPkhVVQmXRigdQjz7K9oiImBg+R7tlOkY0WV0Ds5nCDhDqqixq7XQTu9nGIrKulUUdX5ihq/oaJyv96IhBg3SYu8A9LKvTChIdZTDoa0wDlCSOWUu9RLSJ3gEkd9SNWUcxcFSK3gqsueDv2eezqvOy8/yHaO327N2a0B5blnw/1aPhZkqwMGZoybdEgNB3eFIwUJRzxBNhy8m+jd8uap1m9QxQXBbRkQXM9K3aWTAN97pbiB4LcuHFahBbxgOHH4ur4tLyuKus20gLouwXHa8HVRUJfeF3BQgNowIXC+cN3kri+KgnDbMAWJO0LifIEG1IYJtw1TUM0TCqdbh5QXmOsLAkRB47YNkPWCHenTUFcsYhwd13XK+LJO6W7hKRCFBEcHfhPH6TUg8UsSnAAcVHS4dEhoU01SnP4bUtVkri9I8LM0DOcLIVVN6faRGmpoJcf5QkhVUx6tQcCIEDhtOqS8wF1fkNCaQkrc1gC2aroNrYRaOalwdIRUNaW71tRggtI4OvAbNc5AoFWWjFEyb1DB4bKhwNYhQam8IdVM7nqCgqqFIihPCKpkuqKDhpbbiqI8IaiK6aZoDdUKxTrI/cRV+9n3VPv5ETaXVvvrl6lxkafObzcqhnk3XQnfr2fw3TZQHKWgB5X53XhXYLyLDq5O39XVXWx+7/YZl4tta6mWN7/dzYG2T2+fuv4kdRLlvyH1kcqVBDUkhimF27NgSPUFBF/jZGl2VfSTy2pfwleQVTFOlr4uCveXRUEei/OekqBKcMIoC6i0iNjXOTTBCaPY0ITQ1xSnfYUUmpL5qj6a4bSvkEJT8mMF0FN30BynvoQUmlJ5O4fAqS/I0AS1Ly1RS+yQIlMR39WlVqgldkiBqeixzuDZyGndYSHC3nUhwi6w5r7vuOJ+2wpZ4FYs51fm9Uf8e29bymjcy2whJWUlT+cFC1nzdayDvS+g7UWz9MHYMUbbb4a9eUxXj/VrbN9MUW48PKZCJ0xLQbkkcr3+HxANddo=}}

===Chest to chest===

'''Note:''' Experimental data from 0.18

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

===Chest to belt===

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

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

'''Note:''' Experimental data from 0.18

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

===Chest to splitter===

When an inserter drops items onto the side of a perpendicular splitter, it always is considered to do so on the input side, enabling the splitter to move half of the items to the other belt (assuming that the splitter filter/priority settings allow it to do so and that there is available space on both belts). This allows the inserter to drop its items twice as fast. A fully upgraded stack inserter can drop twelve items onto an express splitter every 38 ticks (18.95 items/second) instead of the usual 52.

[[File:Inserter to splitter comparison.png|621px|thumb|center|By inserting onto the side of a splitter, a fully-upgraded stack inserter can fill 84% of an express belt lane instead of the usual 62%.]]

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

'''Note:''' Experimental data from 0.18

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

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

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

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

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

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

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

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

'''Note:''' Experimental data from 0.18

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

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

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

{{C|Inserters}}