Official Factorio Wiki - User contributions [en]

Console

2025-12-05T18:41:24Z

DaveMcW: Rename global to storage

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

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

== Normal commands ==

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

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

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

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

== Basic example scripts ==

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

=== Zoom beyond normal bounds ===
Note that zooming too far out can cause performance hits. Be careful.
<syntaxhighlight lang="lua">
/c game.player.zoom=0.1
</syntaxhighlight>
In freeplay, the farthest you can zoom out is 0.3. In the map editor, it is 0.1. Smaller zoom values will be clamped.

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

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

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

Undo this with the command in the next section.

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

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

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

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

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

There are several god-mode items available:

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

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

Adding [[Quality|higher quality]] items looks like this:
<syntaxhighlight lang="lua">
/c game.player.insert{name="iron-plate", quality="legendary", count=100}
</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>

=== Add new water patch ===

This creates a small pond in a 4x2 square.
<syntaxhighlight lang="lua">
/c
local waterTiles = {}
for y=2,4 do
for x=-2,2 do
table.insert(waterTiles, {name="water", position={game.player.position.x+x, game.player.position.y+y}})
end
game.player.surface.set_tiles(waterTiles)
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/MapGenSize.html 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/MapGenSize.html 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>

=== Deactivate cars and tanks ===
The [[car]] and [[tank]] can be used like larger, 2x3 chests, but doing this at a large scale can have a negative performance impact. Deactivating them reduces their performance impact, though it also prevents them from being driven or moved by belts.

Deactivate selected car or tank (hover with mouse then enter command):
<syntaxhighlight lang="lua">
/c game.player.selected.active = false
</syntaxhighlight>

Deactivate all cars and tanks on surface:
<syntaxhighlight lang="lua">
/c for _, v in pairs(game.player.surface.find_entities_filtered{type="car"}) do
v.active = false
end
</syntaxhighlight>

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Enable ghosts for destroyed entities ===
This is normally unlocked through researching [[construction robotics (research)]], but this command unlocks it independent of the research.
<syntaxhighlight lang="lua">
/c game.player.force.create_ghost_on_entity_death = true
</syntaxhighlight>

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

=== Access a mod's data ===
If the first word of the command is __mod-name__ it will run in the context of the mod with the same name. For instance, this command prints the data from the Even Distribution mod:
<syntaxhighlight lang="lua">
/c __even-distribution__ game.player.print(serpent.dump(storage))
</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 helpers.write_file("mods.txt", serpent.block(script.active_mods))
</syntaxhighlight>

=== Exporting production statistics ===
Export production statistics out of the game into external JSON files.

<syntaxhighlight lang="lua">/c local timescales = {
[defines.flow_precision_index.five_seconds] = "5s",
[defines.flow_precision_index.one_minute] = "1min",
[defines.flow_precision_index.ten_minutes] = "10min",
[defines.flow_precision_index.one_hour] = "1h",
[defines.flow_precision_index.ten_hours] = "10h",
[defines.flow_precision_index.fifty_hours] = "50h",
[defines.flow_precision_index.two_hundred_fifty_hours] = "250h",
[defines.flow_precision_index.one_thousand_hours] = "1000h"
}
for surface_name, _ in pairs(game.surfaces) do
local flowdata = game.player.force.get_item_production_statistics(surface_name)
for timescale_index, timescale_name in pairs(timescales) do
local tbl = {}
local totals = flowdata.input_counts
for item_name, _ in pairs(totals) do
local row = {item_name}
for i = 1, 300 do
table.insert(row, flowdata.get_flow_count{name=item_name, category="input", precision_index=timescale_index, sample_index=i, count=true})
end
table.insert(tbl, row)
end
helpers.write_file("stats-" .. surface_name .. "-" .. timescale_name .. ".json", helpers.table_to_json(tbl), false)
end
end
game.player.print("Export done")</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}}

Pollution

2025-05-25T22:43:29Z

DaveMcW: /* Trees */ Copy changes from tree article

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

Pollution is represented as an abstract "cloud", updated [[Map_structure#Chunk|per chunk]] every 64 [[Time#Ticks|ticks]] (which is 4 ticks more than a game-second). It is visible on the map if the "pollution" setting is on, and appears as a blocky red cloud.

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

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

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

== Pollution spread ==

As soon as a chunk has reached 15.0 pollution it starts spreading in all four cardinal directions at a rate of 2% per 64 ticks. Pollution can generate new chunks if it needs to spread to them.

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

== Pollution dissipation==

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

== Native life ==
Pollution attracts [[Enemies#Biters|biters]] to the Player's factory. Biters who find themselves in a polluted area will attempt to reach the source of pollution and destroy it. Any [[water]] near the source of pollution will turn green, which is a visual-only effect. The effect can be turned off by disabling animated water in the graphics settings.

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

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

This also applies to [[Enemies#Wrigglers|pentapods]]{{SA}} on [[Gleba]]{{SA}}.

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

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

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

Fire on the ground and burning trees produce 0.3 pollution per minute.

=== [[Space Age]]{{SA}} polluters ===

{| class="wikitable"
! Structure !! Pollution per minute at full power
|-
| {{Imagelink|Foundry}}
| 6
|-
| {{Imagelink|Electromagnetic plant}}
| 4
|-
| {{Imagelink|Cryogenic plant}}
| 6
|-
| {{Imagelink|Recycler}}
| 2
|-
| {{Imagelink|Big mining drill}}
| 40
|-
| {{Imagelink|Heating tower}}
| 100
|-
| {{Imagelink|Biolab}}
| 8
|-
| {{Imagelink|Crusher}}
| 1
|-
|}

=== De-polluters ===

==== Spawners ====
Every 64 ticks, spawners absorb pollution until they have absorbed more than 3 times the amount needed to send the [[Enemies#Creatures|most expensive unit]] at the current evolution level.

If they have not absorbed more than that threshold, they will absorb 20 + 0.01 * [chunk's pollution] and check the threshold again.

Note that absorbing pollution is not for spawning biters, but for sending biters to an attack group. Spawners will spawn enemies regardless of pollution absorption until they reach their spawn limit.

[[Captive biter spawner]]s {{SA}} absorb 1 pollution per minute. Captive spawners which have decayed to the wild type use the rules above for pollution absorption.

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

{| class="wikitable"
! Tile !! Pollution per tile per second !! Pollution per chunk per minute
|-
| Water, green water, deep water, deep green water, shallow water, mud water || -0.000025 || -1.536
|-
| Grass 1-4 || -0.000018 || -1.10592
|-
| Dirt 1-7, dry dirt || -0.000018 || -1.10592
|-
| Red desert 0-3 || -0.000015 || -0.9216
|-
| Sand 1-3 || -0.000015 || -0.9216
|-
| Nuclear ground || -0.0000125 || -0.768
|-
| Path tiles (Stone bricks, concrete etc), landfill || 0 || 0
|-
| Special tiles (Lab tiles, tutorial grid, Water Wube) || 0 || 0
|-
| Out of map || -0.0001 || -6.144
|-
|}

==== Trees ====

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

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

==== Biochambers{{SA}} ====

The [[biochamber]] "generates" negative pollution, at a base rate of -1 per minute. This effectively means that the building removes pollution while active.

This pollution value works like any other building, including how it scales with energy consumption. That is, if a module affects its energy consumption, the pollution is proportionately higher as well. However, because the base rate is negative, the Biochamber "generates" more negative pollution. [[Productivity module]]s and their direct pollution increase work in a similar way, boosting the negative pollution of the building even more.

== Spores {{SA}} ==

Spores are a unique form of pollution generated on Gleba. They are made when [[yumako tree]]s or [[jellystem]]s are harvested (not destroyed). Spores do not attract biters, but rather attract pentapods. Spores are consumed by most tiles. They are displayed as green squares on the map. All machines '''do not''' make spores, with the only exception being the [[agricultural tower]].

[[File:Spores on map.png|250px|thumb|right|Spores]]

{| class="wikitable"
! Entity !! Spores generated !! Generates spores
|-
| {{Imagelink|Yumako tree}}
| 15
| Per harvest
|-
| {{Imagelink|Jellystem}}
| 15
| Per harvest
|-
| {{Imagelink|Agricultural tower}}
| 4
| Always
|-
|}
:
:
:

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

== History ==
{{history|2.0.43|
* Trees no longer take damage from spores nor absorb spores as a result of taking pollution damage.
* Gleba wetlands, lowlands, and water tiles now absorb 3 times as many spores as other tiles.}}

{{history|2.0.7|
* Greatly increased default tile pollution absorption. (Out of map x10, water and nuclear ground x5, rest roughly x2.5)}}

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

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

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

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

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

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

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

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

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

{{C|Main}}

Console

2025-04-26T15:21:21Z

DaveMcW: /* Normal commands */ Add space age alerts

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

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

== Normal commands ==

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

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

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

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

== Basic example scripts ==

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

=== Zoom beyond normal bounds ===
Note that zooming too far out can cause performance hits. Be careful.
<syntaxhighlight lang="lua">
/c game.player.zoom=0.1
</syntaxhighlight>
In freeplay, the farthest you can zoom out is 0.3. In the map editor, it is 0.1. Smaller zoom values will be clamped.

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

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

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

Undo this with the command in the next section.

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

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

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

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

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

There are several god-mode items available:

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Add new water patch ===

This creates a small pond in a 4x2 square.
<syntaxhighlight lang="lua">
/c
local waterTiles = {}
for y=2,4 do
for x=-2,2 do
table.insert(waterTiles, {name="water", position={game.player.position.x+x, game.player.position.y+y}})
end
game.player.surface.set_tiles(waterTiles)
end
</syntaxhighlight>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<syntaxhighlight lang="lua">
/c helpers.write_file("mods.txt", serpent.block(script.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}}

Tree

2025-03-11T03:51:27Z

DaveMcW: Add damage percentage

{{Languages}}
{{:Infobox:Tree}}
'''Trees''' are plants in Factorio. They can be mined for [[wood]], and are the only source of it. Trees are obstacles to construction and must be cleared to provide building space, but they also reduce [[pollution]], so take care not to remove more than necessary. Currently, trees cannot be replanted in the vanilla version of the game, though they can be in {{SA}} [[Space Age]]. While [[Nauvis]] has standard Earth-like trees, [[Gleba]]{{SA}} also has alien tree-like structures. [[Vulcanus]]{{SA}} contains ashland trees, which yield small amounts of carbon when destroyed.

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

== Good methods to remove trees ==

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

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

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

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

== Pollution removal ==

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

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

== Agriculture ==
{{About/Space age}}
Trees can be grown on Nauvis by planting [[tree seed]]s, either manually or via the [[agricultural tower]]. Grown trees take 10 minutes to reach full maturity, and they will yield 4 [[wood]] when harvested. The agricultural tower will automatically harvest mature trees in its range, replanting them if they have available seeds.

Tree seeds are produced from [[wood processing]]. 2 wood can be converted into one seed. Because mature trees yield 4 wood, if all wood produced from harvesting mature trees is processed, the seed supply will increase. Tree seeds are [[Fuel#Burnable_fuel|burnable fuel]] fuel and thus can be disposed of easily.

Growing trees can be used to create renewable barriers against pollution spread. Note that the agriculture tower cannot grow seeds as densely as a player can manually plant them. The tower will always put two tiles of empty space between each tree.

==Gallery==
<gallery widths="250px" heights="190px">
File:gleba_trees.png|Tree-like plants on Gleba.
File:Vulcanus_trees.png|Ashland trees on Vulcanus.
</gallery>

== History ==

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

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

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

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

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

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

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

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

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

== See also ==

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

{{EnvironmentNav}}

Infobox:Processing unit

2025-01-01T06:07:24Z

DaveMcW: Remove satellite from space age mod

{{Infobox
|prototype-type = item
|internal-name = processing-unit
|category = Intermediate products
|stack-size=100
|rocket-capacity=300 (3 {{Translation|stacks}})
|recipe = Time, 10 + Advanced circuit, 2 + Electronic circuit, 20 + Sulfuric acid, 5
|total-raw = Time, 54 + Copper plate, 40 + Iron plate, 24 + Plastic bar, 4 + Sulfuric acid, 5
|required-technologies = Processing unit
|producers = Assembling machine 2 + Assembling machine 3 + Electromagnetic plant
|consumers = Atomic bomb + Cargo landing pad + Discharge defense + Efficiency module 2 + Efficiency module 3 + Energy shield MK2 + Exoskeleton + Portable fission reactor + Personal battery MK2 + Personal laser defense + Personal roboport MK2 + Power armor + Power armor MK2 + Productivity module 2 + Productivity module 3 + Rocket part + Rocket silo + Satellite + Speed module 2 + Speed module 3 + Spidertron + Utility science pack
|changed-by-space-age-mod = yes
|space-age-consumers = Artillery turret + Artillery wagon + Asteroid collector + Atomic bomb + Capture bot rocket + Cargo bay + Cargo landing pad + Cryogenic plant + Discharge defense + Electromagnetic plant + Efficiency module 2 + Efficiency module 3 + Energy shield MK2 + Exoskeleton + Mech armor + Personal battery MK2 + Personal laser defense + Personal roboport MK2 + Portable fission reactor + Power armor + Power armor MK2 + Productivity module 2 + Productivity module 3 + Quality module 2 + Quality module 3 + Quantum processor + Recycler + Rocket part + Rocket silo + Rocket turret + Space platform starter pack + Speed module 2 + Speed module 3 + Spidertron + Stack inserter + Tesla turret + Thruster + Turbo splitter + Utility science pack
}}<noinclude>
[[Category:Infobox page]]
</noinclude>

Infobox:Quality module 2

2024-12-05T00:46:17Z

DaveMcW: Remove electromagnetic plant from base mod producers

{{Infobox
|space-age = yes
|prototype-type = module
|internal-name = quality-module-2
|category = Production
|stack-size = 50
|speed = -5%
|quality = {{Quality|+2%|+2.6%|+3.2%|+3.8%|+5%}}
|recipe = Time, 30 + Advanced circuit, 5 + Processing unit, 5 + Quality module, 4
|total-raw = Time, 352.5 + Copper plate, 155 + Iron plate, 70 + Plastic bar, 50 + Processing unit, 5
|required-technologies = Quality module 2 (research)
|producers = Assembling machine + Player
|consumers = Quality module 3

|changed-by-space-age-mod=yes
|space-age-recipe = Time, 30 + Advanced circuit, 5 + Processing unit, 5 + Quality module, 4
|space-age-total-raw = Time, 352.5 + Copper plate, 155 + Iron plate, 70 + Plastic bar, 50 + Processing unit, 5
|space-age-producers = Assembling machine + Electromagnetic plant + Player

}}<noinclude>
[[Category:Infobox page]]
</noinclude>

Infobox:Quality module 3

2024-12-05T00:44:22Z

DaveMcW: Update base mod producers

{{Infobox
|space-age = yes
|prototype-type = module
|internal-name = quality-module-3
|category = Production
|stack-size = 50
|speed = -5%
|quality = {{Quality|+2.5%|+3.2%|+4%|+4.7%|+6.2%}}
|recipe = Time, 60 + Advanced circuit, 5 + Processing unit, 5 + Quality module 2, 4
|total-raw = Time, 1500 + Iron plate, 290 + Copper plate, 645 + Plastic bar, 210 + Processing unit, 25
|required-technologies = Quality module 3 (research)
|producers = Assembling machine + Player

|changed-by-space-age-mod=yes
|space-age-recipe = Time, 60 + Advanced circuit, 5 + Processing unit, 5 + Superconductor, 1 + Quality module 2, 4
|space-age-total-raw = Time, 1500 + Iron plate, 290 + Copper plate, 645 + Plastic bar, 210 + Processing unit, 25 + Superconductor, 1
|space-age-producers = Assembling machine + Electromagnetic plant + Player

}}<noinclude>
[[Category:Infobox page]]
</noinclude>

Infobox:Quality module 3

2024-12-04T02:23:12Z

DaveMcW: Add base recipe which is available with only the Quality mod.

{{Infobox
|space-age = yes
|prototype-type = module
|internal-name = quality-module-3
|category = Production
|stack-size = 50
|speed = -5%
|quality = {{Quality|+2.5%|+3.2%|+4%|+4.7%|+6.2%}}
|recipe = Time, 60 + Advanced circuit, 5 + Processing unit, 5 + Quality module 2, 4
|total-raw = Time, 1500 + Iron plate, 290 + Copper plate, 645 + Plastic bar, 210 + Processing unit, 25
|required-technologies = Quality module 3 (research)
|producers = Assembling machine + Electromagnetic plant + Player

|changed-by-space-age-mod=yes
|space-age-recipe = Time, 60 + Advanced circuit, 5 + Processing unit, 5 + Superconductor, 1 + Quality module 2, 4
|space-age-total-raw = Time, 1500 + Iron plate, 290 + Copper plate, 645 + Plastic bar, 210 + Processing unit, 25 + Superconductor, 1
|space-age-producers = Assembling machine + Electromagnetic plant + Player

}}<noinclude>
[[Category:Infobox page]]
</noinclude>

Circuit network

2021-12-04T09:51:21Z

DaveMcW: Delete old tutorial link

{{Languages}}
'''Circuit networks''' are built using [[Red wire|red]] or [[green wire]], and enable the control of receivers, based upon information broadcast onto the network by connected senders. Most senders are storage devices, and broadcast their information onto a specific channel, based on the item or liquid the storage device contains. Each circuit network contains a channel for every kind of item, as well as 48 extra [[#Virtual signals|virtual signals]] which act as user-definable channels. 'Everything', 'Anything' and 'Each' are also available wildcards.

[[File:shared_circuit_network.png|thumb|600px|right|Two circuit networks shared over one [[small electric pole]].]]

== Usage ==
=== Send information ===
Senders broadcast the amount of items or fluids they contain or other data definable by the player. Each amount is broadcast as a numeric value on a 'channel' corresponding to the item. For example, a Storage Tank containing 1000 Crude Oil will broadcast 1000 on the Crude Oil channel.

The channels are separated from each other, so each network can simultaneously carry a number for each item and fluid in the game, and for each of the extra user-defined channels (digits 0-9, letters A-Z, and 9 different colors). All unused channels have the value zero.

Multiple broadcasts of the same item or fluid are additive: If there are two connected Storage Tanks with 1000 Crude Oil each, the value of the Crude Oil channel within the network will be 2000.

All wires of the same color which are connected together by junctions form a network, i.e. they will pass their signals to each other. For example, if two red wires are connected to the same combinator input, each wire receives the content from the other. This can result in feedback if care is not taken; see Feedback (under [[#Combinators|arithmetic combinator]], below) for discussion.

Numbers are in the signed 32 bit integer range, i.e. from -2147483648 to 2147483647 inclusive, and are encoded in [https://en.wikipedia.org/wiki/Two%27s_complement two's complement representation]. The numbers wrap around on overflow, so e.g. 2147483647 + 10 becomes -2147483639. When entering a number in a combinator it can appear to exceed the 32 bit limit until the GUI is closed, at which point the number will overflow/underflow. [https://forums.factorio.com/58419]

=== Control devices ===
Receivers can use broadcast information, in most cases to enable/disable the device. They can either compare results between different channels, or compare a channel to a specific value.

Receiving devices sum all signals from each wire connected to them, even red and green wires. For example, if an inserter is connected to a red wire carrying a signal for 20 copper plates and a green wire with 10 copper plates, the input signal set for that receiver will be 30 copper plates.

Multiple wires of the same color will share & sum their signals. For example, 3 chests A, B and C connected in a row (A -> B -> C) with green wire will output the sum of their contents along any green wire connected to any of the chests. However, if a red wire connects chest A to an inserter, that inserter will only be given the contents of A as its input signal.

== Devices ==

Each device that is able to be connected to a circuit network has a [[File:Circuit network panel.png]] icon located in the top right corner of its info pane. Clicking this icon will display the available circuit network options for that device (note: a red or green wire must be connected, otherwise the message "not connected" will display instead). Clicking the [[File:Logistic network panel.png]] icon next to it, the device can be connected to a logistic network if in range of one, which also allows conditions to be set.

Conditions can be set for both circuit (signals of red and green wires are summed) and logistic network, which will together act as a logical AND.

The following devices can be connected to a circuit network:

{| class="wikitable mw-collapsible"
|-
! Icon !! Name !! Possible output signals !! Possible control options
|-
| {{Icon|Transport belt||Transport belts}} || [[Transport belts]] || Transport belts can send their content to the circuit network.
*''Pulse mode'': The signal is sent for only 1 tick when the item enters the belt.
*''Hold mode'': The signal is sent continuously as long as the items are on the belt.
|| Transport belts can be enabled on a condition.
|-
| {{Icon|Inserter||Inserters}} || [[Inserters]] || All inserters can send their held items to the circuit network.
*''Pulse mode'': The signal is sent for only 1 tick when the item is picked up.
*''Hold mode'': The signal is sent continuously as long as the inserter is holding the item.
|| All inserters can be enabled on a condition. The inserter stack size can also be overridden from a control signal (configurable).
|-
| {{Icon|Filter inserter}} || [[Filter inserter]] || Same as above. || The filter inserters can additionally set their filters from the circuit network: up to 5 items whose corresponding signal has a positive value are whitelisted.
|-
| {{Icon|Wooden chest||Chests}} || [[Chests]] || All chests can send their contents to the circuit network. Logistic chests additionally send their contents to the [[logistic network]]. ||
|-
| {{Icon|Requester chest}} || [[Requester chest]] || Same as above. || Its requested items can be set by the circuit network.
|-
| {{Icon|Storage tank}} || [[Storage tank]] || The storage tank can send its fluid content to the circuit network. ||
|-
| {{Icon|Gate}} || [[Gate]] || Gates can send a signal to the circuit network.
*''Default'': Player detected = [[File:Signal-G.png|16px]]
|| Gates can be opened on a condition.
|-
| {{Icon|Rail signal}} || [[Rail signal]] || Rail signals can send their state to the circuit network.
*''Default'': [[File:Signal-Red.png|16px]][[File:Signal-Yellow.png|16px]][[File:Signal-Green.png|16px]]
Note: If red due to circuit network, does NOT output red signal
|| Rail signals can be set to red on a condition.
|-
| {{Icon|Rail chain signal}} || [[Rail chain signal]] || Rail chain signals can send their state to the circuit network.
*''Default'': [[File:Signal-Red.png|16px]][[File:Signal-Yellow.png|16px]][[File:Signal-Green.png|16px]][[File:Signal-Blue.png|16px]]
||
|-
| {{Icon|Train stop}} || [[Train stop]] || Train stations can send the contents of a stopped train to the circuit network as well as read a unique train identifier code. The amount of trains going to the train stop can be read by the circuit network. When reading the content of a stopped train, fluid amounts are rounded down to the nearest integer, except when the fluid amount is < 1, then it is is rounded to 1.
*''Default'': Train Count (en route) = [[File:Signal-C.png|16px]]
*''Default'': Stopped Train ID = [[File:Signal-T.png|16px]]
|| Train stations can send the contents of the circuit network to the train to use it for wait conditions, as well as enable/disable the stop itself. The maximum amount of trains that can go to the train stop ("train limit") can be set by the circuit network.
*''Default'': Set Limit = [[File:Signal-L.png|16px]]
|-
| {{Icon|Accumulator}} || [[Accumulator]] || It can send its charge level in percent to the circuit network.
*''Default'': Charge % = [[File:Signal-A.png|16px]]
||
|-
| {{Icon|Roboport}} || [[Roboport]] || It can send its logistic network contents and/or its robot statistics to the circuit network. The signals used for robot statistics are configurable.
*''Default'': Available Logistics Bots = [[File:Signal-X.png|16px]]
*''Default'': Total Logistics Bots = [[File:Signal-Y.png|16px]]
*''Default'': Available Construction Bots = [[File:Signal-Z.png|16px]]
*''Default'': Total Construction Bots = [[File:Signal-T.png|16px]]
||
|-
| {{Icon|Burner mining drill}} || [[Mining drill]]s || All mining drills can send the expected resources, either from the drill itself or from the whole ore patch the drill is on. || Mining drills can be enabled on a condition.
|-
| {{Icon|Pumpjack}} || [[Pumpjack]] || It can output the current oil mining rate. || It can be enabled on a condition.
|-
| {{Icon|Power switch}} || [[Power switch]] || || Power switches can connect power networks on a condition.
|-
| {{Icon|Programmable speaker}} || [[Programmable speaker]] || || Shows alerts and plays sounds based on circuit network signals. It can be used to make simple tunes.
|-
| {{Icon|Lamp}} || [[Lamp]] || || The lamp can be enabled on a condition. If it receives color signals, it can set the given color.
|-
| {{Icon|Offshore pump}} || [[Offshore pump]] || || The offshore pump can be enabled on a condition.
|-
| {{Icon|Pump}} || [[Pump]] || || The pump can be enabled on a condition.
|}

== Physical network structure ==
A circuit network consists only of those devices connected together with the same color wire. Wire can be strung directly from device to device, or across any intervening power poles. Wire length is limited by its previous connection.

Note that each connected set of wires forms a separate network. For example, it's entirely possible to have four red-wire networks and three green-wire networks. If red and green wires happen to touch the same power pole or device, the red and green networks will remain separate and will not link up. However, two red cables or two green cables will link if they touch. Use different colored cables to separate networks in close proximity.

* To connect wires or cables to a power pole, simply click on one entity, then on the base of the power pole.
* To erase a wire or cable connection, place the same color wire over an existing connection. You don't get the wire/cable back.
* To remove '''all''' connections from a power pole, shift-click on the pole. The first shift-click will remove all electrical connections, and the second will remove all red and green wires. You don't get the wires back.
* When connecting to a [[arithmetic combinator]] or [[decider combinator]], take care to connect the wire to the correct input or output side. Use "Show details" mode to see the orientation of the combinator.
* Hovering the mouse cursor over an item will highlight all wires which connect to the item.
* Hovering the mouse cursor over a power pole which is part of a network will display the signals on its network. Some items like combinators will also display their input and output signals when hovered over.

== Combinators ==
Combinators can function as both receiving and sending devices and allow more advanced functions to be used on a circuit network.

*The [[constant combinator]] broadcasts up to 20 values on any of the channels for whatever networks it is connected to. (You cannot currently specify whether a value should be on the red or green channel; if you need different values, use two combinators, one for each color wire.) You can use any item channel or any of the [[#Virtual signals|virtual signal]] channels.
**Note that using two of the 20 slots to broadcast values on the '''same''' channel is the same as broadcasting the sum of the two values from one slot.
*The [[arithmetic combinator]] performs arithmetic operations on input values and broadcasts the result to the specified output channel. The input and output channels can be any item channel or any of the virtual signal channels.
** Connecting: The arithmetic combinator connects to a red or green network on its '''input''' side (the terminals are set into the main body and look like spark plugs) and performs an arithmetic calculation which is broadcast into the specified channel on its '''output''' side (the output wires appear to stretch out a bit from the body of the device).
** Feedback: Note that the input network and the output network '''are not the same network'''. Connecting the output network back to the input network will result in a feedback loop. For example, adding 1 to the value for copper plates and broadcasting it as copper plates is an action that results in an infinite loop if output is connected back to input. The value for copper plates will rapidly (but not instantly) shoot upward. (The rate at which it climbs is determined by the current tick rate.) This technique can be combined with decider combinator logic to make electronic clocks, gates, and other systems.
** Each: This combinator can use the 'Each' signal for both input and output, in which case '''all''' non-zero input channels will have the combinator's operation performed and broadcast on the output side. Having Each signals for input and output and using a non-changing operation (like adding zero) is equivalent to having a 'one-way' wire; all the information from the input network is copied to the output network, but the reverse is not true.
**Multi-network: The arithmetic combinator can be joined to both red and green networks on the input side and will sum their inputs.
*The [[decider combinator]] functions much like an arithmetic combinator, but is designed to compare values. Essentially, it is a conditional. In terms of connecting, feedback, and the Each signal it functions as specified above. In addition, it can handle the Everything and Anything signals, and performs more complex functions than summing when attached to multiple networks. See the [[decider combinator]] page for more details on how to use this.

== Virtual signals ==
[[File:Virtual Signals dialog box.png|thumb|Virtual Signals available for use in the circuit network]]
Virtual signals are special non-item signals. Other than the three logic signals, virtual signals do not behave differently from item signals.

48 virtual signals can be sent over a network. They include the digits zero through nine, the letters A through Z, a check-mark, dot and info icon, and the colors red, green, blue, yellow, magenta, cyan, white, gray and black.

=== Logic signals ===
[[File:logic_signals.png|300px|thumb|The icons of the three logic signals]]
Three of the virtual signals cannot be sent over a network but apply special logic to multiple signals.

==== Everything ====
''Everything'' can be used on the left side in conditionals. The condition will be true when the condition is true for each input signal. The condition is also true if there are no signals. This means that the ''everything'' signal behaves as [[:Wikipedia:universal quantification|universal quantification]].

The output of a [[decider combinator]] may also use ''everything'', unless the input is set to ''each''. When used, the combinator will output signal on every channel with non-zero input as long as the condition is true; the value will either be the input value or 1, depending on the corresponding setting.

==== Anything ====
''Anything'' can be used on the left side of conditions. It will be false when there are no inputs. The condition will be true when the condition is true for at least one signal. This means the ''anything'' signal behaves as [[:Wikipedia:existential quantification|existential quantification]].

When used in both the input and output of a decider combinator, ''anything'' will return one of the signals that matched.

==== Each ====
''Each'' can only be used in left input side and output of [[decider combinator|decider]] and [[arithmetic combinator|arithmetic]] combinators. The signal can only be used as an output when also used as an input. When used in both the input and output, it makes a combinator perform its action on each input signal individually. The combinator will output the sum of each of the actions if only used in the input.

== Tutorials ==
*'''[[Tutorial:Circuit network cookbook]]''' - ''Example-heavy tutorials; for beginners who want to get to know and use the benefits of the circuit network.''

== Logistic network ==
The logistic network used by [[logistic robot]]s is essentially a third network (a wireless one), along with the green and red wired networks. The logistic network is based on proximity to a central [[roboport]].

Some devices can also be connected to the logistic network. If a device has conditions set for circuit and for logistic network, it will become activated if both conditions are true.

See the [[logistic network]] and [[roboport]] articles for more information.

== History ==

{{history|0.15.0|
* Significantly improved circuit network performance. Up to 25 times less CPU usage and 10% less memory usage.
* Added the Programmable Speaker: it shows alerts and plays sounds based on circuit network signals. It can be used to make simple songs.
* Train Stop can output the contents of the stopped train's cargo.
* Train Stop can be disabled using the circuit network. Trains will skip disabled Train Stops, allowing simple train control.
* Mining Drills can be turned on and off using the circuit network. They can also output the remaining expected resources.
* Pumpjacks can be turned on and off using the circuit network. They can also output the current oil mining rate.
* Added Modulo, Power, Left Bit Shift, Right Bit Shift, Bitwise AND, Bitwise OR and Bitwise XOR to the Arithmetic Combinator.
* Added additional operators to the Decider Combinator and Circuit Conditions.}}

{{history|0.13.0|
* Many machines are now connectible to the circuit network.
* Wire disconnecting is incorporated into the latency hiding.
* Wires are now highlighted on entity mouseover.
* Reduced memory usage of circuit network.}}

{{history|0.12.33|
* Fluid values are rounded to the closest value instead of rounding down when transmitted to circuit network.}}

{{history|0.12.1|
* One can copy paste circuit network conditions between the [[inserter]], [[lamp]], [[pump]] and [[offshore pump]]. }}

{{history|0.12.0|
* Improvements to circuit network connection, one can connect multiple wires of the same color to the same entity.
* The [[lamp]], [[storage tank]], [[pump]] and [[offshore pump]] can be connected to the circuit network.
}}

{{history|0.10.0|
* [[Blueprint]]s copy circuit network connections.}}

{{history|0.8.3|
* Circuit network contents info has colored slots to specify the network it represents.}}

{{history|0.1.0|
* Introduced}}

[[Category: Circuit network]]

Circuit network

2021-12-04T09:49:27Z

DaveMcW: Delete old tutorial link

{{Languages}}
'''Circuit networks''' are built using [[Red wire|red]] or [[green wire]], and enable the control of receivers, based upon information broadcast onto the network by connected senders. Most senders are storage devices, and broadcast their information onto a specific channel, based on the item or liquid the storage device contains. Each circuit network contains a channel for every kind of item, as well as 48 extra [[#Virtual signals|virtual signals]] which act as user-definable channels. 'Everything', 'Anything' and 'Each' are also available wildcards.

[[File:shared_circuit_network.png|thumb|600px|right|Two circuit networks shared over one [[small electric pole]].]]

== Usage ==
=== Send information ===
Senders broadcast the amount of items or fluids they contain or other data definable by the player. Each amount is broadcast as a numeric value on a 'channel' corresponding to the item. For example, a Storage Tank containing 1000 Crude Oil will broadcast 1000 on the Crude Oil channel.

The channels are separated from each other, so each network can simultaneously carry a number for each item and fluid in the game, and for each of the extra user-defined channels (digits 0-9, letters A-Z, and 9 different colors). All unused channels have the value zero.

Multiple broadcasts of the same item or fluid are additive: If there are two connected Storage Tanks with 1000 Crude Oil each, the value of the Crude Oil channel within the network will be 2000.

All wires of the same color which are connected together by junctions form a network, i.e. they will pass their signals to each other. For example, if two red wires are connected to the same combinator input, each wire receives the content from the other. This can result in feedback if care is not taken; see Feedback (under [[#Combinators|arithmetic combinator]], below) for discussion.

Numbers are in the signed 32 bit integer range, i.e. from -2147483648 to 2147483647 inclusive, and are encoded in [https://en.wikipedia.org/wiki/Two%27s_complement two's complement representation]. The numbers wrap around on overflow, so e.g. 2147483647 + 10 becomes -2147483639. When entering a number in a combinator it can appear to exceed the 32 bit limit until the GUI is closed, at which point the number will overflow/underflow. [https://forums.factorio.com/58419]

=== Control devices ===
Receivers can use broadcast information, in most cases to enable/disable the device. They can either compare results between different channels, or compare a channel to a specific value.

Receiving devices sum all signals from each wire connected to them, even red and green wires. For example, if an inserter is connected to a red wire carrying a signal for 20 copper plates and a green wire with 10 copper plates, the input signal set for that receiver will be 30 copper plates.

Multiple wires of the same color will share & sum their signals. For example, 3 chests A, B and C connected in a row (A -> B -> C) with green wire will output the sum of their contents along any green wire connected to any of the chests. However, if a red wire connects chest A to an inserter, that inserter will only be given the contents of A as its input signal.

== Devices ==

Each device that is able to be connected to a circuit network has a [[File:Circuit network panel.png]] icon located in the top right corner of its info pane. Clicking this icon will display the available circuit network options for that device (note: a red or green wire must be connected, otherwise the message "not connected" will display instead). Clicking the [[File:Logistic network panel.png]] icon next to it, the device can be connected to a logistic network if in range of one, which also allows conditions to be set.

Conditions can be set for both circuit (signals of red and green wires are summed) and logistic network, which will together act as a logical AND.

The following devices can be connected to a circuit network:

{| class="wikitable mw-collapsible"
|-
! Icon !! Name !! Possible output signals !! Possible control options
|-
| {{Icon|Transport belt||Transport belts}} || [[Transport belts]] || Transport belts can send their content to the circuit network.
*''Pulse mode'': The signal is sent for only 1 tick when the item enters the belt.
*''Hold mode'': The signal is sent continuously as long as the items are on the belt.
|| Transport belts can be enabled on a condition.
|-
| {{Icon|Inserter||Inserters}} || [[Inserters]] || All inserters can send their held items to the circuit network.
*''Pulse mode'': The signal is sent for only 1 tick when the item is picked up.
*''Hold mode'': The signal is sent continuously as long as the inserter is holding the item.
|| All inserters can be enabled on a condition. The inserter stack size can also be overridden from a control signal (configurable).
|-
| {{Icon|Filter inserter}} || [[Filter inserter]] || Same as above. || The filter inserters can additionally set their filters from the circuit network: up to 5 items whose corresponding signal has a positive value are whitelisted.
|-
| {{Icon|Wooden chest||Chests}} || [[Chests]] || All chests can send their contents to the circuit network. Logistic chests additionally send their contents to the [[logistic network]]. ||
|-
| {{Icon|Requester chest}} || [[Requester chest]] || Same as above. || Its requested items can be set by the circuit network.
|-
| {{Icon|Storage tank}} || [[Storage tank]] || The storage tank can send its fluid content to the circuit network. ||
|-
| {{Icon|Gate}} || [[Gate]] || Gates can send a signal to the circuit network.
*''Default'': Player detected = [[File:Signal-G.png|16px]]
|| Gates can be opened on a condition.
|-
| {{Icon|Rail signal}} || [[Rail signal]] || Rail signals can send their state to the circuit network.
*''Default'': [[File:Signal-Red.png|16px]][[File:Signal-Yellow.png|16px]][[File:Signal-Green.png|16px]]
Note: If red due to circuit network, does NOT output red signal
|| Rail signals can be set to red on a condition.
|-
| {{Icon|Rail chain signal}} || [[Rail chain signal]] || Rail chain signals can send their state to the circuit network.
*''Default'': [[File:Signal-Red.png|16px]][[File:Signal-Yellow.png|16px]][[File:Signal-Green.png|16px]][[File:Signal-Blue.png|16px]]
||
|-
| {{Icon|Train stop}} || [[Train stop]] || Train stations can send the contents of a stopped train to the circuit network as well as read a unique train identifier code. The amount of trains going to the train stop can be read by the circuit network. When reading the content of a stopped train, fluid amounts are rounded down to the nearest integer, except when the fluid amount is < 1, then it is is rounded to 1.
*''Default'': Train Count (en route) = [[File:Signal-C.png|16px]]
*''Default'': Stopped Train ID = [[File:Signal-T.png|16px]]
|| Train stations can send the contents of the circuit network to the train to use it for wait conditions, as well as enable/disable the stop itself. The maximum amount of trains that can go to the train stop ("train limit") can be set by the circuit network.
*''Default'': Set Limit = [[File:Signal-L.png|16px]]
|-
| {{Icon|Accumulator}} || [[Accumulator]] || It can send its charge level in percent to the circuit network.
*''Default'': Charge % = [[File:Signal-A.png|16px]]
||
|-
| {{Icon|Roboport}} || [[Roboport]] || It can send its logistic network contents and/or its robot statistics to the circuit network. The signals used for robot statistics are configurable.
*''Default'': Available Logistics Bots = [[File:Signal-X.png|16px]]
*''Default'': Total Logistics Bots = [[File:Signal-Y.png|16px]]
*''Default'': Available Construction Bots = [[File:Signal-Z.png|16px]]
*''Default'': Total Construction Bots = [[File:Signal-T.png|16px]]
||
|-
| {{Icon|Burner mining drill}} || [[Mining drill]]s || All mining drills can send the expected resources, either from the drill itself or from the whole ore patch the drill is on. || Mining drills can be enabled on a condition.
|-
| {{Icon|Pumpjack}} || [[Pumpjack]] || It can output the current oil mining rate. || It can be enabled on a condition.
|-
| {{Icon|Power switch}} || [[Power switch]] || || Power switches can connect power networks on a condition.
|-
| {{Icon|Programmable speaker}} || [[Programmable speaker]] || || Shows alerts and plays sounds based on circuit network signals. It can be used to make simple tunes.
|-
| {{Icon|Lamp}} || [[Lamp]] || || The lamp can be enabled on a condition. If it receives color signals, it can set the given color.
|-
| {{Icon|Offshore pump}} || [[Offshore pump]] || || The offshore pump can be enabled on a condition.
|-
| {{Icon|Pump}} || [[Pump]] || || The pump can be enabled on a condition.
|}

== Physical network structure ==
A circuit network consists only of those devices connected together with the same color wire. Wire can be strung directly from device to device, or across any intervening power poles. Wire length is limited by its previous connection.

Note that each connected set of wires forms a separate network. For example, it's entirely possible to have four red-wire networks and three green-wire networks. If red and green wires happen to touch the same power pole or device, the red and green networks will remain separate and will not link up. However, two red cables or two green cables will link if they touch. Use different colored cables to separate networks in close proximity.

* To connect wires or cables to a power pole, simply click on one entity, then on the base of the power pole.
* To erase a wire or cable connection, place the same color wire over an existing connection. You don't get the wire/cable back.
* To remove '''all''' connections from a power pole, shift-click on the pole. The first shift-click will remove all electrical connections, and the second will remove all red and green wires. You don't get the wires back.
* When connecting to a [[arithmetic combinator]] or [[decider combinator]], take care to connect the wire to the correct input or output side. Use "Show details" mode to see the orientation of the combinator.
* Hovering the mouse cursor over an item will highlight all wires which connect to the item.
* Hovering the mouse cursor over a power pole which is part of a network will display the signals on its network. Some items like combinators will also display their input and output signals when hovered over.

== Combinators ==
Combinators can function as both receiving and sending devices and allow more advanced functions to be used on a circuit network.

*The [[constant combinator]] broadcasts up to 20 values on any of the channels for whatever networks it is connected to. (You cannot currently specify whether a value should be on the red or green channel; if you need different values, use two combinators, one for each color wire.) You can use any item channel or any of the [[#Virtual signals|virtual signal]] channels.
**Note that using two of the 20 slots to broadcast values on the '''same''' channel is the same as broadcasting the sum of the two values from one slot.
*The [[arithmetic combinator]] performs arithmetic operations on input values and broadcasts the result to the specified output channel. The input and output channels can be any item channel or any of the virtual signal channels.
** Connecting: The arithmetic combinator connects to a red or green network on its '''input''' side (the terminals are set into the main body and look like spark plugs) and performs an arithmetic calculation which is broadcast into the specified channel on its '''output''' side (the output wires appear to stretch out a bit from the body of the device).
** Feedback: Note that the input network and the output network '''are not the same network'''. Connecting the output network back to the input network will result in a feedback loop. For example, adding 1 to the value for copper plates and broadcasting it as copper plates is an action that results in an infinite loop if output is connected back to input. The value for copper plates will rapidly (but not instantly) shoot upward. (The rate at which it climbs is determined by the current tick rate.) This technique can be combined with decider combinator logic to make electronic clocks, gates, and other systems; see [[Tutorial:Combinator tutorial|Combinator Tutorial]] for advanced techniques.
** Each: This combinator can use the 'Each' signal for both input and output, in which case '''all''' non-zero input channels will have the combinator's operation performed and broadcast on the output side. Having Each signals for input and output and using a non-changing operation (like adding zero) is equivalent to having a 'one-way' wire; all the information from the input network is copied to the output network, but the reverse is not true.
**Multi-network: The arithmetic combinator can be joined to both red and green networks on the input side and will sum their inputs.
*The [[decider combinator]] functions much like an arithmetic combinator, but is designed to compare values. Essentially, it is a conditional. In terms of connecting, feedback, and the Each signal it functions as specified above. In addition, it can handle the Everything and Anything signals, and performs more complex functions than summing when attached to multiple networks. See the [[decider combinator]] page for more details on how to use this.

== Virtual signals ==
[[File:Virtual Signals dialog box.png|thumb|Virtual Signals available for use in the circuit network]]
Virtual signals are special non-item signals. Other than the three logic signals, virtual signals do not behave differently from item signals.

48 virtual signals can be sent over a network. They include the digits zero through nine, the letters A through Z, a check-mark, dot and info icon, and the colors red, green, blue, yellow, magenta, cyan, white, gray and black.

=== Logic signals ===
[[File:logic_signals.png|300px|thumb|The icons of the three logic signals]]
Three of the virtual signals cannot be sent over a network but apply special logic to multiple signals.

==== Everything ====
''Everything'' can be used on the left side in conditionals. The condition will be true when the condition is true for each input signal. The condition is also true if there are no signals. This means that the ''everything'' signal behaves as [[:Wikipedia:universal quantification|universal quantification]].

The output of a [[decider combinator]] may also use ''everything'', unless the input is set to ''each''. When used, the combinator will output signal on every channel with non-zero input as long as the condition is true; the value will either be the input value or 1, depending on the corresponding setting.

==== Anything ====
''Anything'' can be used on the left side of conditions. It will be false when there are no inputs. The condition will be true when the condition is true for at least one signal. This means the ''anything'' signal behaves as [[:Wikipedia:existential quantification|existential quantification]].

When used in both the input and output of a decider combinator, ''anything'' will return one of the signals that matched.

==== Each ====
''Each'' can only be used in left input side and output of [[decider combinator|decider]] and [[arithmetic combinator|arithmetic]] combinators. The signal can only be used as an output when also used as an input. When used in both the input and output, it makes a combinator perform its action on each input signal individually. The combinator will output the sum of each of the actions if only used in the input.

== Tutorials ==
*'''[[Tutorial:Circuit network cookbook]]''' - ''Example-heavy tutorials; for beginners who want to get to know and use the benefits of the circuit network.''

== Logistic network ==
The logistic network used by [[logistic robot]]s is essentially a third network (a wireless one), along with the green and red wired networks. The logistic network is based on proximity to a central [[roboport]].

Some devices can also be connected to the logistic network. If a device has conditions set for circuit and for logistic network, it will become activated if both conditions are true.

See the [[logistic network]] and [[roboport]] articles for more information.

== History ==

{{history|0.15.0|
* Significantly improved circuit network performance. Up to 25 times less CPU usage and 10% less memory usage.
* Added the Programmable Speaker: it shows alerts and plays sounds based on circuit network signals. It can be used to make simple songs.
* Train Stop can output the contents of the stopped train's cargo.
* Train Stop can be disabled using the circuit network. Trains will skip disabled Train Stops, allowing simple train control.
* Mining Drills can be turned on and off using the circuit network. They can also output the remaining expected resources.
* Pumpjacks can be turned on and off using the circuit network. They can also output the current oil mining rate.
* Added Modulo, Power, Left Bit Shift, Right Bit Shift, Bitwise AND, Bitwise OR and Bitwise XOR to the Arithmetic Combinator.
* Added additional operators to the Decider Combinator and Circuit Conditions.}}

{{history|0.13.0|
* Many machines are now connectible to the circuit network.
* Wire disconnecting is incorporated into the latency hiding.
* Wires are now highlighted on entity mouseover.
* Reduced memory usage of circuit network.}}

{{history|0.12.33|
* Fluid values are rounded to the closest value instead of rounding down when transmitted to circuit network.}}

{{history|0.12.1|
* One can copy paste circuit network conditions between the [[inserter]], [[lamp]], [[pump]] and [[offshore pump]]. }}

{{history|0.12.0|
* Improvements to circuit network connection, one can connect multiple wires of the same color to the same entity.
* The [[lamp]], [[storage tank]], [[pump]] and [[offshore pump]] can be connected to the circuit network.
}}

{{history|0.10.0|
* [[Blueprint]]s copy circuit network connections.}}

{{history|0.8.3|
* Circuit network contents info has colored slots to specify the network it represents.}}

{{history|0.1.0|
* Introduced}}

[[Category: Circuit network]]

Tutorials

2021-12-04T09:48:45Z

DaveMcW: /* Circuit network */ Delete old tutorial link

{{Languages}}
This page lists tutorials that can be found here on the wiki. They range from guides for the very first steps in the game to in-depth modding tutorials.

== The first steps and the first base ==
These tutorials aim to guide the player through the first steps of the game and provide an idea of how a base could look like.

* [[Tutorial:Quick start guide|Quick start guide]] - Guides through the first steps of the game, from mining the first piece of ore to automating the first science pack.
* [[Tutorial:Main bus|Main bus]] - A type of base organization that is well suited for beginners.
* [[Tutorial:Keyboard shortcuts|Keyboard shortcuts]] - A collection of useful keyboard shortcuts.

== Power production ==
These tutorials take an in-depth look at individual topics related to [[power production]].

* [[Tutorial:Applied power math|Applied power math]]
* [[Tutorial:Nuclear power|Nuclear power]]
* [[Tutorial:Producing power from oil|Producing power from oil]]

== Circuit network ==
These tutorials take a closer look at the [[circuit network]] and present usage examples.

* [[Tutorial:Circuit network cookbook|Circuit network cookbook]] - Example-heavy tutorial; for beginners who want to get to know and use the benefits of the circuit network.

== Miscellaneous ==

* [[Tutorial:Train signals|Train signals]]
* [[Tutorial:Transport use cases|A comparison of the different means of transport]]

== Modding tutorials ==
{{:Tutorial:Modding tutorial}}

Main Page/Expert

2021-12-04T09:48:05Z

DaveMcW: Delete old tutorial link

* [[Mining|Mining mechanics]]
* [[Circuit network]]
** [[Tutorial:Circuit network cookbook|Circuit network cookbook]]
* [[Debug mode|Debug modes]]
* [[Console]]
* [[Modding]]
** [[Prototype definitions]]
* [[Map editor]]
* [[Balancer mechanics]]
* [[Units|Physical units]]
** [[Energy and work]]

<noinclude>
{{Languages}}
{{C|Main}}
</noinclude>

Arithmetic combinator

2021-12-04T09:47:43Z

DaveMcW: Delete old tutorial link

{{Languages}}
{{:Infobox:Arithmetic combinator}}
The arithmetic combinator is part of the [[circuit network]] and one of three types of combinators available in the game (along with the [[constant combinator]] and [[decider combinator]]). Each arithmetic combinator can perform any one of the following mathematical operations on signals, and will show the corresponding symbol on its top:

[[File:arith_combinator_anim.png]]

* addition (+)
* subtraction (−)
* multiplication (*)
* division (/)
* modulo (%)
* exponentiation (^)
* left bit shift (<<)
* right bit shift (>>)
* bitwise AND (&)
* bitwise OR (|)
* bitwise XOR (^)

The arithmetic combinator accepts two input connections (red and green wires), and sends its output to both output connections. The input wires connect to the nubs on the left side of the sprite in the sidebar, while the outputs connect to the right side.

[[File:Arithmetic_combinator_gui.png|350px|GUI of the Arithmetic Combinator.]] 

== Function ==
The internal logic process has three steps:

# All input signals on the red and green wires are summed within the combinator.
# The specified operation is performed on the selected signal(s).
# The result of this operation is output as the selected output signal.

The left operand of the operation can be any single signal or the [[Virtual signals#Each|''each'' virtual signal]], and the right operand can be any single signal or a constant value.

If the left operand is a single signal, the output must be a single signal. The operation is performed on the values of the chosen left and right signals, and the result is sent to the output on the specified signal.

If the left operand is the ''each'' signal, then the output can be a single signal or the ''each'' signal. If the output is the ''each'' signal, then the operation is performed individually on the value of each input signal along with the value of the right operand, and each result is sent to the output on the same signal. If the output is a single signal, the operation is done on each of the input signals, the individual results are all added together, and that result is sent to the output on the specified signal.

== Notes on operations ==
When using '''division''', the result is truncated:
* 21 / 10 = 2
* 19 / 10 = 1
* −21 / 10 = −2
* −19 / 10 = −1
* 21 / −10 = −2
* 19 / −10 = −1
* −21 / −10 = 2
* −19 / −10 = 1

'''Modulo''', indicated using % as it is in most programming languages, is the remainder after division. For example, 13 % 3 is 1 (13 = 4 * 3 + 1). This can, for example, be combined with truncated division as described above to separate out individual digits of a number for use in building visual indicators:
* (24321 / 10000) % 10 = 2
* (24321 / 1000) % 10 = 4
* (24321 / 100) % 10 = 3
* (24321 / 10) % 10 = 2
* (24321 / 1) % 10 = 1

Negating the left operand of a modulo negates the result, while negating the right operand does nothing:
* 13 % 3 = 1
* 13 % −3 = 1
* −13 % 3 = −1
* −13 % −3 = −1

'''Left bit shift''' and '''Right bit shift''' are not arithmetic. Instead these options deals with numbers in the [[:Wikipedia:Binary_number|binary]] state. The 0's and 1's that make up a number are shifted in the specified direction which can result in a completely different number, due to the change in the binary value.

[[File:Bitshiftleft.png|none|thumb|200px|Example of a 'left bit shift'.]]

== History ==
{{history|0.15.0|
* Added Modulo, Power, Left Bit Shift, Right Bit Shift, Bitwise AND, Bitwise OR and Bitwise XOR to the Arithmetic Combinator.}}

{{history|0.13.0|
* Connected wires are highlighted when hovering over a combinator connected to the [[circuit network]].
* Combinators show input and output in alt mode.
* More virtual signals for combinators.
* Constant combinator can be rotated.
* Decider combinator "input count" option makes the combinator copy the count of the specified output signal from the input signals, instead of copying the count from the condition.
* New combinator graphics. }}

{{history|0.12.5|
* Combinators now emit light.}}

{{history|0.12.2|
* Combinators no longer turn off when no wires are connected.}}

{{history|0.12.0|
* Introduced}}

==See Also==
*[[Decider combinator]]
*[[Constant combinator]]
*[[Circuit network]]
*[[Tutorial:Circuit network cookbook|Circuit network cookbook]]

{{LogisticsNav}}
{{C|Circuit network}}

Decider combinator

2021-12-04T09:47:17Z

DaveMcW: Delete old tutorial link

{{Languages}}
{{:Infobox:Decider combinator}}

The Decider combinator is part of the circuit network and one of three types of combinators available in the game (with the other two being the [[constant combinator]] and [[arithmetic combinator]]). It is used to make comparisons of signals on the network. Signals can be compared using the following:

[[File:decider_combinator_anim.png]]

*"is greater than" (>)
*"is less than" (<)
*"greater than or equal to" (>=)
*"less than or equal to" (<=)
*"is equal to" (=)
*"is not equal to" (!=)

As shown in the picture below showing the GUI, the signal on the left is bring compared to that of the right.

[[File:decider_combinator_gui.png|350px|GUI of the decider combinator.]]

== Function ==
The internal logic process has three steps:

# Values for each individual input signal(s) (items of the same name) on the red and green wires are summed within the combinator.
# The decider combinator GUI specifies a "first" input signal, a comparison (>, <, =, >=, <=, !=), and a "second" input signal or constant.
# If the comparison returns true, the output is one or more signals with a value of 1 or the unchanged input value(s), or a single signal carrying either a sum of input signals or the number of passed tests. ([[#output_table|see table below]])

The decider combinator can handle [[Circuit network#Logic signals|logic signals]].

Further notes:

* Using the Everything output with "Input count" will pass all non-zero input values to the output as long as the condition is true. Using the Everything output with "1" will output 1 ONLY for all non-zero inputs.
* The Each input will re-apply the comparison for each input signal individually, and will pass the selected output for each input that passes the conditional.
* The Everything input functions as a logical AND, and will return true only if ALL non-zero inputs pass the conditional, and returns true if there are no inputs at all (so "everything ≠ 0" always passes).
* The Anything input functions as a logical OR, and will return true if ANY non-zero input passes the conditional, and returns false if there are no inputs at all (so "anything = 0" always fails). If used for output, Anything will return one of the signals that matched.
* When "Input Count" is selected the output will match the input for the selected signal if the first parameter is not Each. If the first parameter is Each then "Input Count" refers to the value of the input signal that is currently being iterated, so the result will be the sum of all inputs if the output signal is not Each. If the output signal is also Each then every input signal that passes the test is simply forwarded while those that fail the test are discarded.

The following table shows how different combinations of the first input parameter and the output can be used.

{| class="wikitable" style="text-align: center"
|+Different output results when the test passes
|-
! ↓Output  Input→ !! Each !! Anything, Everything, or a specific signal
|-
!style="text-align: left"| Everything: 1
|rowspan="2"| - || every input signal is forwarded but set to 1
|-
!style="text-align: left"| Everything: Input count
| every input signal is forwarded
|-
!style="text-align: left"| Specific signal: 1
| number of input signals† || the specific signal with value 1
|-
!style="text-align: left"| Specific signal: Input count
| sum of inputs† || the specific signal is forwarded
|-
!style="text-align: left"| Each: 1
| each input signal† is forwarded but set to 1 ||rowspan="2"| -
|-
!style="text-align: left"| Each: Input count
| each input signal† is forwarded
|-
!style="text-align: left"| Anything: 1
|rowspan="2"| - || one input signal† is forwarded but set to 1
|-
!style="text-align: left"| Anything: Input count
| one input signal† is forwarded
|-
|}

† signals that passed the test only

With both the arithmetic and decider combinator, there is one tick (60th of a second) of latency before the output signal is ready to be used as an input into a circuit network.

== History ==
{{history|1.1.13|
* Decider combinator can output an Anything signal, which returns exactly one matching signal.}}

{{history|0.15.0|
* Added additional operators to the Decider Combinator and Circuit Conditions.}}

{{history|0.13.0|
* Connected wires are highlighted when hovering over a combinator connected to the [[circuit network]].
* Combinators show input and output in alt mode.
* More virtual signals for combinators.
* Constant combinator can be rotated.
* Decider combinator "input count" option makes the combinator copy the count of the specified output signal from the input signals, instead of copying the count from the condition.
* New combinator graphics. }}

{{history|0.12.5|
* Combinators now emit light.}}

{{history|0.12.2|
* Combinators no longer turn off when no wires are connected.}}

{{history|0.12.0|
* Introduced}}

== See Also ==
* [[Arithmetic combinator]]
* [[Constant combinator]]
* [[Circuit network]]
* [[Tutorial:Circuit network cookbook|Circuit network cookbook]]

{{LogisticsNav}}
{{C|Circuit network}}

Constant combinator

2021-12-04T09:45:31Z

DaveMcW: Delete old tutorial link

{{Languages}}
{{:Infobox:Constant combinator}}

The constant combinator is part of the circuit network and one of three types of combinators available in the game (the other two being the [[arithmetic combinator]] and [[decider combinator]]). It constantly outputs the selected signal(s) to all connected wire networks without the need for a specific input, and can be turned on/off in the GUI manually. Most common uses include testing of composed circuitry or changing some user-defined settings by broadcasting a kind of a switching signal.

If the output of a combinator is desired to be switched on/off remotely or automatically, it is recommended to channel its output through a decider combinator. Unlike the other two combinators, the constant combinator does not require electricity to function.

[[File:constant_combinator_gui.png|350px|GUI of the constant combinator.]]

== History ==

{{history|0.13.0|
* Connected wires are highlighted when hovering over a combinator connected to the [[circuit network]].
* Combinators show input and output in alt mode.
* More virtual signals for combinators.
* Constant combinator can be rotated.
* Decider combinator "input count" option makes the combinator copy the count of the specified output signal from the input signals, instead of copying the count from the condition.
* New combinator graphics. }}

{{history|0.12.5|
* Combinators now emit light.}}

{{history|0.12.2|
* Combinators no longer turn off when no wires are connected.}}

{{history|0.12.0|
* Introduced}}

== See Also ==
* [[Arithmetic combinator]]
* [[Decider combinator]]
* [[Circuit network]]
* [[Tutorial:Circuit network cookbook|Circuit network cookbook]]

{{LogisticsNav}}
{{C|Circuit network}}

Stronger explosives (research)

2021-08-30T04:33:04Z

DaveMcW: Fix level 7 formula

{{Languages}}{{:Infobox:Stronger explosives (research)}}
'''Stronger explosives (research)''' affects the damage of grenades, rockets and landmines.

{| class="wikitable"
! colspan = 2 |
! colspan = 2 | {{Icon|Grenade}}{{Icon|Cluster grenade}}
! colspan = 2 | {{Icon|Land mine}}
! colspan = 2 | {{Icon|Rocket}}{{Icon|Explosive rocket}}{{Icon|Atomic bomb}}
|-
! Technology !! Cost !! Per Level !! Cumulative !!Per level !! Cumulative !! Per level !! Cumulative
|-
| {{Icontech|Stronger explosives (research)|1}} Stronger explosives 1 || {{Icon|Time|30}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} ✖ <big>100</big> || 25% || 25% || || || ||
|-
| {{Icontech|Stronger explosives (research)|2}} Stronger explosives 2 || {{Icon|Time|30}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} {{Icon|Military science pack|1}} ✖ <big>200</big> || 20% || 45% || 20% || 20% || ||
|-
| {{Icontech|Stronger explosives (research)|3}} Stronger explosives 3 || {{Icon|Time|60}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} {{Icon|Military science pack|1}} {{Icon|Chemical science pack|1}} ✖ <big>300</big> || 20% || 65% || 20% || 40% || 30% || 30%
|-
| {{Icontech|Stronger explosives (research)|4}} Stronger explosives 4 || {{Icon|Time|60}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} {{Icon|Military science pack|1}} {{Icon|Chemical science pack|1}} {{Icon|Utility science pack|1}} ✖ <big>400</big> || 20% || 85% || 20% || 60% || 40% || 70%
|-
| {{Icontech|Stronger explosives (research)|5}} Stronger explosives 5 || {{Icon|Time|60}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} {{Icon|Military science pack|1}} {{Icon|Chemical science pack|1}} {{Icon|Utility science pack|1}} ✖ <big>500</big> || 20% || 105% || 20% || 80% || 50% || 120%
|-
| {{Icontech|Stronger explosives (research)|6}} Stronger explosives 6 || {{Icon|Time|60}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} {{Icon|Military science pack|1}} {{Icon|Chemical science pack|1}} {{Icon|Utility science pack|1}} ✖ <big>600</big> || 20% || 125% || 20% || 100% || 60% || 180%
|-
| {{Icontech|Stronger explosives (research)|7-∞}} Stronger explosives 7-∞ || {{Icon|Time|60}} {{Icon|Automation science pack|1}} {{Icon|Logistic science pack|1}} {{Icon|Military science pack|1}} {{Icon|Chemical science pack|1}} {{Icon|Utility science pack|1}} {{Icon|Space science pack|1}} ✖ <big>{{Key|2^(Level-7)*1000}}</big> (eg. 1000 for level 7, 2000 for level 8) || 20% per level || 125% + <pre class="keyboard-key">20%*(Level-6)</pre> || 20% per level || 100% + <pre class="keyboard-key">20%*(Level-6)</pre> || 50% per level || 180% + <pre class="keyboard-key">50%*(Level-6)</pre>
|}
== See also ==
* [[Research]]
* [[Technologies]]

{{TechNav}}

Armor

2021-07-11T21:58:57Z

DaveMcW: /* Quick summary */ Armor now goes in bottom left slot

{{Languages}}{{disambiguation}}

== Quick summary ==
Armor can placed in the armor slot at the bottom left of the screen to reduce the amount of damage the player receives. The more advanced types of armor can also accommodate [[equipment modules]].

----

''Armor'' may refer to:

* {{imagelink|Light armor}}
* {{imagelink|Heavy armor}}
* {{imagelink|Modular armor}}
* {{imagelink|Power armor}}
* {{imagelink|Power armor MK2}}

Military units and structures

2021-07-03T21:40:45Z

DaveMcW: /* Military structures */ Use unit-spawner prototype name

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

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

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

__TOC__

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

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

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

Types/StyleSpecification

2021-06-18T02:03:42Z

DaveMcW: Add tooltip property

A [[types/table|table]], used as a value in [[Prototype/GuiStyle]], named by the key that is used there. Prototype/GuiStyle loads one of the extensions of this prototype, depending on the specified <code>type</code>.

== Extensions ==
* [[Types/ActivityBarStyleSpecification]] '''activity_bar_style'''
* [[Types/EmptyWidgetStyleSpecification]] '''empty_widget_style'''
** [[Types/CameraStyleSpecification]] '''camera_style'''
** [[Types/MinimapStyleSpecification]] '''minimap_style'''
* [[Types/DropDownStyleSpecification]] '''dropdown_style'''
* [[Types/FlowStyleSpecification]] '''flow_style'''
* [[Types/FrameStyleSpecification]] '''frame_style'''
* [[Types/GlowStyleSpecification]] '''glow_style'''
* [[Types/GraphStyleSpecification]] '''graph_style'''
* [[Types/HorizontalFlowStyleSpecification]] '''horizontal_flow_style'''
* [[Types/ImageStyleSpecification]] '''image_style'''
* [[Types/LabelStyleSpecification]] '''label_style'''
* [[Types/LineStyleSpecification]] '''line_style'''
* [[Types/ListBoxStyleSpecification]] '''list_box_style'''
* [[Types/ProgressBarStyleSpecification]] '''progressbar_style'''
* [[Types/ScrollBarStyleSpecification]] <abstract>
** [[Types/HorizontalScrollBarStyleSpecification]] '''horizontal_scrollbar_style'''
** [[Types/VerticalScrollBarStyleSpecification]] '''vertical_scrollbar_style'''
* [[Types/ScrollPaneStyleSpecification]] '''scroll_pane_style'''
* [[Types/SliderStyleSpecification]] '''slider_style'''
** [[Types/DoubleSliderStyleSpecification]] '''double_slider_style'''
* [[Types/SpeechBubbleStyleSpecification]] '''speech_bubble_style'''
* [[Types/StyleWithClickableGraphicalSetSpecification]] <abstract>
** [[Types/ButtonStyleSpecification]] '''button_style'''
*** [[Types/TechnologySlotStyleSpecification]] '''technology_slot_style'''
** [[Types/CheckBoxStyleSpecification]] '''checkbox_style'''
** [[Types/RadioButtonStyleSpecification]] '''radiobutton_style'''
* [[Types/SwitchStyleSpecification]] '''switch_style'''
* [[Types/TabbedPaneStyleSpecification]] '''tabbed_pane_style'''
* [[Types/TableStyleSpecification]] '''table_style'''
* [[Types/TabStyleSpecification]] '''tab_style'''
* [[Types/TextBoxStyleSpecification]] '''textbox_style'''
* [[Types/VerticalFlowStyleSpecification]] '''vertical_flow_style'''

== Mandatory properties ==

=== type ===
'''Type''': [[Types/string|string]]

The type of one of the above listed extensions, this style specification is then loaded as that extension.

== Optional properties ==

=== parent ===
'''Type''': [[Types/string|string]]

Name of a [[Types/StyleSpecification]]. This style specification inherits all property values from the parent style specification. 
It is recommended to always set the parent style to at least the basic vanilla style. If no parent is set, some style properties become mandatory and behavior may be unexpected, such as an element not showing up because its size defaults to 0.

=== horizontal_align ===
'''Type''': [[Types/string|string]]

'''Default''': "left"

Either "left", "center" or "right".

=== vertical_align ===
'''Type''': [[Types/string|string]]

'''Default''': "top"

Either "top", "center" or "bottom".

=== ignored_by_search ===
'''Type''': [[Types/bool|bool]]

=== never_hide_by_search ===
'''Type''': [[Types/bool|bool]]

=== horizontally_stretchable ===
'''Type''': [[Types/StretchRule|StretchRule]]

'''Default''': "auto"

=== vertically_stretchable ===
'''Type''': [[Types/StretchRule|StretchRule]]

'''Default''': "auto"

=== horizontally_squashable ===
'''Type''': [[Types/StretchRule|StretchRule]]

'''Default''': "auto"

=== vertically_squashable ===
'''Type''': [[Types/StretchRule|StretchRule]]

'''Default''': "auto"

=== natural_size ===
'''Type''': [[Types/uint32|uint32]] or [[Types/table|table]] of [[Types/uint32|uint32]]

If this is an array, the first member of the array is <code>natural_width</code> and the second is <code>natural_height</code>. Otherwise the size is both <code>natural_width</code> and <code>natural_height</code>.

=== size ===
'''Type''': [[Types/uint32|uint32]] or [[Types/table|table]] of [[Types/uint32|uint32]]

If this is an array, the first member of the array is <code>width</code> and the second is <code>height</code>. Otherwise the size is both <code>width</code> and <code>height</code>.

=== width ===
'''Type''': [[Types/uint32|uint32]]

Sets <code>minimal_width</code>, <code>maximal_width</code> and <code>natural_width</code>.

=== minimal_width ===
'''Type''': [[Types/uint32|uint32]]

'''Default''': 0

Minimal width ensures, that the widget will never be smaller than than that size. It can't be squashed to be smaller.

=== maximal_width ===
'''Type''': [[Types/uint32|uint32]]

'''Default''': 0

Maximal width ensures, that the widget will never be bigger than than that size. It can't be stretched to be bigger.

=== natural_width ===
'''Type''': [[Types/uint32|uint32]]

'''Default''': 0

Natural width specifies the width of the element tries to have, but it can still be squashed/stretched to have a smaller or bigger size.

=== height ===
'''Type''': [[Types/uint32|uint32]]

Sets <code>minimal_height</code>, <code>maximal_height</code> and <code>natural_height</code>.

=== minimal_height ===
'''Type''': [[Types/uint32|uint32]]

'''Default''': 0

Minimal height ensures, that the widget will never be smaller than than that size. It can't be squashed to be smaller.

=== maximal_height ===
'''Type''': [[Types/uint32|uint32]]

'''Default''': 0

Maximal height ensures, that the widget will never be bigger than than that size. It can't be stretched to be bigger.

=== natural_height ===
'''Type''': [[Types/uint32|uint32]]

'''Default''': 0

Natural height specifies the height of the element tries to have, but it can still be squashed/stretched to have a smaller or bigger size.

=== padding ===
'''Type''': [[Types/int16|int16]]

Sets <code>top_padding</code>, <code>right_padding</code>, <code>bottom_padding</code> and <code>left_padding</code>.

=== top_padding ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== right_padding ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== bottom_padding ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== left_padding ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== margin ===
'''Type''': [[Types/int16|int16]]

Sets <code>top_margin</code>, <code>right_margin</code>, <code>bottom_margin</code> and <code>left_margin</code>.

=== top_margin ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== right_margin ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== bottom_margin ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== left_margin ===
'''Type''': [[Types/int16|int16]]

'''Default''': 0

=== effect ===
'''Type''': [[Types/string|string]]

=== effect_opacity ===
'''Type''': [[Types/float|float]]

'''Default''': 1.0

=== tooltip ===
'''Type''': [[Types/LocalisedString|LocalisedString]]

== Example ==
Example of adding a custom style via [[Prototype/GuiStyle]], in this case a [[Types/FrameStyleSpecification]]:
<syntaxhighlight lang="lua">data.raw["gui-style"]["default"]["custom_style_for_a_frame"] =
{
type = "frame_style",
parent = "frame",
use_header_filler = false,
drag_by_title = false
}</syntaxhighlight>

Prototype/Roboport

2021-05-14T17:30:09Z

DaveMcW: charging_offsets is only used if charging_station_count is equal to zero

{{Prototype parent|Prototype/EntityWithHealth}}
A [[roboport]].

{{Prototype TOC|roboport}}

== Mandatory properties ==
This prototype inherits all the properties from [[Prototype/EntityWithHealth]].

{{Prototype property|energy_source|[[Types/EnergySource|EnergySource]]}}
The roboport's energy source. Must be an electric or void energy source.

{{Prototype property|energy_usage|[[Types/Energy|Energy]]}}
The amount of energy the roboport uses when idle.

{{Prototype property|recharge_minimum|[[Types/Energy|Energy]]}}

{{Prototype property|robot_slots_count|[[Types/ItemStackIndex|ItemStackIndex]]}}
The number of robot slots in the roboport.

{{Prototype property|material_slots_count|[[Types/ItemStackIndex|ItemStackIndex]]}}
The number of repair pack slots in the roboport.

{{Prototype property|base|[[Types/Sprite|Sprite]]}}

{{Prototype property|base_patch|[[Types/Sprite|Sprite]]}}

{{Prototype property|base_animation|[[Types/Animation|Animation]]}}
The animation played when the roboport is idle.

{{Prototype property|door_animation_up|[[Types/Animation|Animation]]}}

{{Prototype property|door_animation_down|[[Types/Animation|Animation]]}}

{{Prototype property|request_to_open_door_timeout|[[Types/uint32|uint32]]}}

{{Prototype property|recharging_animation|[[Types/Animation|Animation]]}}
The animation played at each charging point when a robot is charging there.

{{Prototype property|spawn_and_station_height|[[Types/float|float]]}}
Presumably states the height of the charging stations and thus an additive offset for the charging_offsets.

{{Prototype property|charge_approach_distance|[[Types/float|float]]}}
Presumably, the distance from the roboport at which robots will wait to charge.

{{Prototype property|logistics_radius|[[Types/float|float]]}}
Can't be negative.

{{Prototype property|construction_radius|[[Types/float|float]]}}
Can't be negative.

{{Prototype property|charging_energy|[[Types/Energy|Energy]]}}
The amount of energy that is given to a robot per tick.

== Optional properties ==

{{Prototype property|open_door_trigger_effect|[[Types/TriggerEffect|TriggerEffect]]|optional=true}}

{{Prototype property|close_door_trigger_effect|[[Types/TriggerEffect|TriggerEffect]]|optional=true}}

{{Prototype property|default_available_logistic_output_signal|[[Types/SignalIDConnector|SignalIDConnector]]|optional=true}}

{{Prototype property|default_total_logistic_output_signal|[[Types/SignalIDConnector|SignalIDConnector]]|optional=true}}

{{Prototype property|default_available_construction_output_signal|[[Types/SignalIDConnector|SignalIDConnector]]|optional=true}}

{{Prototype property|default_total_construction_output_signal|[[Types/SignalIDConnector|SignalIDConnector]]|optional=true}}

{{Prototype property|circuit_wire_connection_point|[[Types/WireConnectionPoint|WireConnectionPoint]]|optional=true}}

{{Prototype property|circuit_wire_max_distance|[[Types/double|double]]|0|optional=true}}
The maximum circuit wire distance for this entity.

{{Prototype property|draw_copper_wires|[[Types/bool|bool]]|true|optional=true}}

{{Prototype property|draw_circuit_wires|[[Types/bool|bool]]|true|optional=true}}

{{Prototype property|circuit_connector_sprites|[[Types/CircuitConnectorSprites|CircuitConnectorSprites]]|optional=true}}

{{Prototype property|spawn_and_station_shadow_height_offset|[[Types/float|float]]|0|optional=true}}

{{Prototype property|draw_logistic_radius_visualization|[[Types/bool|bool]]|true|optional=true}}

{{Prototype property|draw_construction_radius_visualization|[[Types/bool|bool]]|true|optional=true}}

{{Prototype property|recharging_light|[[Types/LightDefinition|LightDefinition]]|optional=true}}
The light emitted when charging a robot.

{{Prototype property|charging_station_count|[[Types/uint32|uint32]]|0|optional=true}}

{{Prototype property|charging_distance|[[Types/float|float]]|0.0|optional=true}}

{{Prototype property|charging_station_shift|[[Types/vector|vector]]|optional=true}}

{{Prototype property|charging_threshold_distance|[[Types/float|float]]|1.0|optional=true}}

{{Prototype property|robot_vertical_acceleration|[[Types/float|float]]|0.01|optional=true}}

{{Prototype property|stationing_offset|[[Types/vector|vector]]|optional=true}}
The offset from the centre of the roboport at which robots will enter and exit.

{{Prototype property|robot_limit|[[Types/ItemCountType|ItemCountType]]|max uint|optional=true}}
How many robots can exist in the network (cumulative).

{{Prototype property|robots_shrink_when_entering_and_exiting|[[Types/bool|bool]]|false|optional=true}}

{{Prototype property|charging_offsets|[[Types/table|table]] of [[Types/vector|vector]]|optional=true}}
The offsets from the centre of the roboport at which robots will charge. Only used if charging_station_count is equal to zero.

{{Prototype property|logistics_connection_distance|[[Types/float|float]]|optional=true}}
Must be >= <code>logistics_radius</code>.

Prototype/SimpleEntityWithForce

2020-11-26T19:02:43Z

DaveMcW: picture is a Sprite4Way in version 1.1.

{{Prototype parent|Prototype/EntityWithHealth}}
This entity will be a priority target for units/turrets, who will choose to attack it even if it does not block their path. Use [[Prototype/SimpleEntityWithOwner]] for entities that are only attacked when they block enemies.

{{Prototype TOC|simple-entity-with-force}}

== Optional properties ==
This prototype inherits all the properties from [[Prototype/EntityWithHealth]].

{{Prototype property|render_layer|[[Types/RenderLayer|RenderLayer]]|"object"|optional=true}}

{{Prototype property|secondary_draw_order|[[Types/int8|int8]]|0|optional=true}}

{{Prototype property|random_animation_offset|[[Types/bool|bool]]|false|optional=true}}

{{Prototype property|random_variation_on_create|[[Types/bool|bool]]|true|optional=true}}
Whether a random graphics variation is chosen when placing the entity/creating it via script/creating it via map generation. If this is false, the entity will use the first variation instead of a random one.

{{Prototype property|pictures|[[Types/SpriteVariations|SpriteVariations]]|optional=true}}
Must have one of 'picture', 'pictures' or 'animations' defined.

{{Prototype property|picture|[[Types/Sprite4Way|Sprite4Way]]|optional=true}}
Must have one of 'picture', 'pictures' or 'animations' defined.

{{Prototype property|animations|[[Types/AnimationVariations|AnimationVariations]]|optional=true}}
Must have one of 'picture', 'pictures' or 'animations' defined.

Prototype/SimpleEntityWithOwner

2020-11-26T19:01:42Z

DaveMcW: picture is a Sprite4Way in version 1.1.

{{Prototype parent|Prototype/EntityWithHealth}}
Has a force, but unlike [[Prototype/SimpleEntityWithForce]] it is only attacked if the biters get stuck on it.

{{Prototype TOC|simple-entity-with-owner}}

== Optional properties ==
This prototype inherits all the properties from [[Prototype/EntityWithHealth]].

{{Prototype property|render_layer|[[Types/RenderLayer|RenderLayer]]|"object"|optional=true}}

{{Prototype property|secondary_draw_order|[[Types/int8|int8]]|0|optional=true}}

{{Prototype property|random_animation_offset|[[Types/bool|bool]]|false|optional=true}}

{{Prototype property|random_variation_on_create|[[Types/bool|bool]]|true|optional=true}}
Whether a random graphics variation is chosen when placing the entity/creating it via script/creating it via map generation. If this is false, the entity will use the first variation instead of a random one.

{{Prototype property|pictures|[[Types/SpriteVariations|SpriteVariations]]|optional=true}}
Must have one of 'picture', 'pictures' or 'animations' defined.

{{Prototype property|picture|[[Types/Sprite4Way|Sprite4Way]]|optional=true}}
Must have one of 'picture', 'pictures' or 'animations' defined.

{{Prototype property|animations|[[Types/AnimationVariations|AnimationVariations]]|optional=true}}
Must have one of 'picture', 'pictures' or 'animations' defined.

{{Prototype property|force_visibility|[[Types/ForceCondition|ForceCondition]]|"all"|optional=true}}

Console

2020-11-24T00:38:28Z

DaveMcW: /* Normal commands */ Add tips commands

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

Use the {{keybinding|↑}} and {{keybinding|↓}} keys to scroll through the console history. The {{keybinding|Tab}} key 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 100
| Changes your color. Can either be one of the pre-defined colors or [[:Wikipedia:RGBA_color_space|RGBA value]] in the format of “# # # #”. Available colors: default, red, green, blue, orange, yellow, pink, purple, white, black, gray, brown, cyan, acid.
| No
|-
| /evolution
| /evolution
| Prints info about the alien evolution factor.
| No
|-
| /help [command]
| /help
| Prints a list of available commands, the optional argument can specify the command that should be described.
| No
|-
| /h [command]
| /h
| Same as /help.
| No
|-
| /mute-programmable-speaker <mute/unmute> <local/everyone>
| /mute-programmable-speaker mute local
| Mutes or unmutes the global sounds created by the Programmable Speaker. Use “local” to mute just the local client. Admins can use “everyone” to mute the sounds for everyone on the server.
| No
|-
| /perf-avg-frames <number>
| /perf-avg-frames 100
| Number of ticks/updates used to average performance counters. Default is 100. Value of 5-10 is recommended for fast convergence, but numbers will jitter more rapidly.
| No
|-
| /permissions
| /permissions
| Opens the permissions GUI.
| Yes
|-
| /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
|-
| /toggle-rockets-sent-gui
| /toggle-rockets-sent-gui
| Toggles if the rockets sent button is shown in the upper left corner of the screen.
| No
|-
| /unlock-shortcut-bar
| /unlock-shortcut-bar
| Unlocks all [[shortcut bar]] items, 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
|-
| /banlist <add/remove/get/clear> <player>
| /banlist get
| Adds or removes a player from the banlist. Same as /ban or /unban.
| No
|-
| /config <get/set> <option> <value>
| /config set password hunter2
| Gets or sets various multiplayer game settings. Available configs are: afk-auto-kick, allow-commands, allow-debug-settings, autosave-interval, autosave-only-on-server, ignore-player-limit-for-returning-players, max-players, max-upload-speed, only-admins-can-pause, password, require-user-verification, visibility-lan, visibility-public.
| Yes
|-
| /delete-blueprint-library <player>
| /delete-blueprint-library everybody confirm
| Deletes the blueprint library storage for the given offline player from the save file. Enter “everybody confirm” to delete the storage of all offline players.
| Yes
|-
| /demote <player>
| /demote AzureDiamond
| Demotes the player from admin.
| Yes
|-
| /ignore <player>
| /ignore Cthon98
| Prevents the chat from showing messages from this player. Admin messages are still shown.
| No
|-
| /ignores
| /ignores
| Prints a list of ignored players.
| No
|-
| /kick <player> <reason>
| /kick xTROLLx Throwing grenades in base
| Kicks the specified player.
| Yes
|-
| /mute <player>
| /mute Cthon98
| Prevents the player from saying anything in chat.
| Yes
|-
| /mutes
| /mutes
| All players that are muted (can’t talk in chat).
| No
|-
| /open <player>
| /open AzureDiamond
| Opens another player’s inventory.
| Yes
|-
| /o <player>
| /o AzureDiamond
| Same as /open.
| Yes
|-
| /players [online/o/count/c]
| /players
| Prints a list of players in the game. (parameter online/o, it prints only players that are online, count/c prints only count)
| No
|-
| /promote <player>
| /promote AzureDiamond
| Promotes the player to admin.
| Yes
|-
| /purge <player>
| /purge Cthon98
| Clears all the messages from this player from the chat log.
| Yes
|-
| /reply <message>
| /reply oh, really?
| Replies to the last player that whispered to you.
| No
|-
| /r <message>
| /r oh, really?
| Same as /reply.
| No
|-
| /server-save
| /server-save
| Saves the game on the server in a multiplayer game.
| Yes
|-
| /shout <message>
| /shout Hello world!
| Sends a message to all players including other forces.
| No
|-
| /s <message>
| /s Hello world!
| Same as /shout.
| No
|-
| /swap-players <player> [player]
| /swap-players AzureDiamond
| Swaps your character with the given player’s character, or if two players are given swaps the two player characters.
| Yes
|-
| /unban <player>
| /unban xTROLLx
| Unbans the specified player.
| Yes
|-
| /unignore <player>
| /unignore Cthon98
| Allows the chat to show messages from this player.
| No
|-
| /unmute <player>
| /unmute Cthon98
| Allows the player to talk in chat again.
| Yes
|-
| /whisper <player> <message>
| /whisper AzureDiamond that's what I see
| Sends a message to the specified player.
| No
|-
| /w <player> <message>
| /w AzureDiamond that's what I see
| Same as /whisper.
| No
|-
| /whitelist <add/remove/get/clear> [player]
| /whitelist get
| Adds or removes a player from the whitelist, where only whitelisted players can join the game. Enter nothing for “player” when using “get” to print a list of all whitelisted players. An empty whitelist disables the whitelist functionality allowing anyone to join.
| No
|}

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

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

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== 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(game.get_filtered_entity_prototypes{{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>

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Research scripts ==

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

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

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

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

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

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

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

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

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

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

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

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

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

== See also ==

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

Types/ImageStyleSpecification

2020-11-11T13:54:55Z

DaveMcW: Add example

Extension of [[Types/StyleSpecification]]. 
Style specification type: '''image_style'''

== Optional properties ==
Inherits all properties from [[Types/StyleSpecification]].

=== graphical_set ===
'''Type''': [[Types/ElementImageSet|ElementImageSet]]

=== stretch_image_to_widget_size ===
'''Type''': [[Types/bool|bool]]

== Example ==
data.raw["gui-style"]["default"]["stretchy-sprite"] = {
type = "image_style",
vertically_stretchable = "on",
horizontally_stretchable = "on",
stretch_image_to_widget_size = true,
}

Fluid system

2020-10-24T03:07:18Z

DaveMcW: /* Pipelines */ The pipes table is the most popular section of this article, there is no reason to hide it.

{{Languages}}
'''Fluids''' are non-solid items, such as [[water]] and [[oil]]. They can normally only exist inside entities for fluid handling (like [[pipe]]s), and buildings that have fluids as input ingredients or products (like an [[oil refinery]]).

== Fluids ==
[[File:fluids_gui.png|thumb|300px|right|"Fluids" tab on the [[production statistics]] screen.]]
The following fluids are available in-game:

: {{Imagelink|Water}} {{Imagelink|Crude oil}} {{Imagelink|Petroleum gas}} {{Imagelink|Light oil}} {{Imagelink|Heavy oil}} {{Imagelink|Lubricant}} {{Imagelink|Sulfuric acid}} {{Imagelink|Steam}}

== Mechanics ==
Fluids cannot be carried by the player, moved using [[inserters]], dropped on the ground, nor stored in chests, unless the fluids are stored in [[barrel]]s. They cannot be spilled or even dumped in a lake, and are counted in continuous fractions, rather than discrete integers. 
When the player picks up a structure that contains fluids, the contained fluid will try to flow into connected structures and any excess fluid that does not fit is destroyed.

=== Storage ===

In the game, fluid is held in entities that behave as vessels (fluid boxes) of a defined size (volume). The vessels automatically connect to each other if their inputs/outputs are adjacent (pipes connect to all directions) and allow fluids to flow between them.

The '''volume''' of fluid contained in a fluid box is a value between 0 and the maximum volume. For instance, the pipe can hold 100 units of fluid, therefore the value in the pipe can be a number between 0 and 100. The '''level''' of fluid in a given entity is manifested by a percentage of the entity's maximum volume that is being occupied by a fluid. It can be observed in pipes and tanks; they have windows through which the fluid is seen at a certain level, or perhaps even as just a small trickle.

=== Fluid mixing ===
[[File:Pipe_GUI.png|right|frame|GUI of a pipe inside a fluid system containing mixed fluids. Clicking the trash can icon next to a fluid will flush that fluid from the system.]]
The game will prevent players from accidentally mixing fluids when placing most buildings, e.g. [[pipe]]s containing different fluids cannot be placed directly next to each other. However, not every possible case of fluid mixing is considered, so the player may still mix fluids accidentally or by purposely working around the building restrictions. A fluid system containing mixed fluids can be cleared of the undesired fluids in the GUI of a pipe or [[storage tank]] that is part of that fluid system. Fluids that are flushed from pipes or storage tanks are deleted permanently.

In a fluid system that contains mixed fluids, the alt-mode fluids icons on its pipes/storage tanks will reflect the fluid that is contained in that specific structure. So, it may look like a fluid system only contains one fluid when looking at the alt-mode icons, when in reality it contains multiple fluids which are located in some other connected structures. The GUI of a connected pipe or storage tank will always show all fluids contained in the fluid system. 
This means that if the game disallows connecting two pipes that look like they contain the same fluid with "Cannot connect systems with different fluids", one of the fluid systems contains multiple fluids. This can solved easily by opening the GUIs of the pipes that the game refuses to connect which will show the extra fluid and allow flushing it from the fluid system.

=== Flow ===

All connected tanks and pipes are treated as a single vessel in that ''the level of fluid must be equal in all parts'', to even out pressure exacted by a higher fluid level on smaller ones. This is why level is also often referred to as ''pressure'', even though pressure is actually caused by a difference in level between two entities. All flow of fluid that happens between pipes is to achieve this balance (pumps practically ignore it and buildings disrupt it; more on that further below). The flow rate between pipes is dependent on pressure (the difference in level between the adjacent entities), it becomes slower as pipes even their levels out.

Coming back to how the 'level' is defined, this also means that all connected pipes and tanks attempt to even out to the same percentage of their respective volumes. For example, if 12 550 units of fluid are left to flow into a storage tank of 25 000-unit capacity with one pipe of 100-unit capacity connected, there will be 12 500 units in the storage tank and 50 units in the pipe, both being filled to the same '''percentage''' (50%) of their capacities, even though the amounts themselves are obviously unequal.

Machines that produce fluids put them in their output slots, which are related to a specifically labeled output pipe socket somewhere on the machine (pressing Alt reveals the labels). The slot will attempt to empty itself into the entity connected to the machine's socket, unless it is full, or contains a non-matching fluid. Machines that consume fluids also have an accordingly labeled pipe input socket. If an entity containing the correct fluid is connected to it, the machine will start behaving like a pipe that can never be filled, meaning the fluid from connected pipes and tanks drains into the machine at a fixed rate, until the machine's input slot is full. There may be machines that have pipe sockets for both input and output (like a [[electric mining drill|drill]] placed over [[uranium ore]]). They then drain the fluid for themselves first, and once full, behave as a regular pipe that attempts to even out its level with adjacent entitites. If there are multiple output/input sockets for one fluid on a machine, their activity is distributed to them equally unless some of them are blocked/full.

=== Temperature ===
Temperature is currently only relevant in heating water as a medium for power generation. Even though all fluids in the game have a temperature value, it is generally the default 15°C.

Energy, whether harnessed from [[fuel]] in [[boiler]]s, or from [[Nuclear power (research)|nuclear power]] through [[heat exchanger]]s, can be used to turn [[water]] to [[steam]], being a [[Energy and work|liquid form of work]]. Steam holds energy at a ratio of 0.2 kJ per °C per unit. In other words: 0.2 kJ of work is necessary to heat a unit of steam by one °C. Since steam/water is set to have a maximum temperature of 1000°C and minimum of 15°C, the most work that can be done on one unit is 197 kJ.

In practice, this is barely utilized in a great variety: Boilers only output steam of 165°C temperature, and heat exchangers only output 500°C hot steam, never hotter, never colder; if insufficient energy is supplied, the heaters do not output steam altogether. The steam also does not grow colder over time. Using the 165°C steam in a [[steam engine]] has the same effect as using it in a [[steam turbine]], although it is impractical, since turbines are made to consume 500°C (superheated) steam, generating proportionally more power. All of this makes for no need of exact calculations.

== Transport ==
Fluids can be transported through pipelines, barrels, or railway. It is generally practical to use piping for short-distance distribution to machines (or barrelling, if there is need to use belts), and railway transportation for longer distances.

=== Pipelines ===
[[File:pipes_carrying_fluids.png|thumb|312px|Eight pipelines, each carrying a different fluid.]]

'''[[Pipe|Pipes]]''' are the most basic way to channel fluids from A to B. They automatically connect to any adjacent pipe and can do so to all four cardinal directions simultaneously. [[Pipe to ground|Underground pipes]] only work in two opposite directions, linking to another underground pipe on one side, and to another entity on the other. If a pipe section becomes too long without using pumps, all fluid inside it will be "spread thin", resulting in very slow flow and preventing machines to use its contents effectively. '''[[Storage tank|Tanks]]''' behave the same as pipes, except their volume is much greater, which can cause this inconvenience over a much smaller distance if multiple tanks are used. Underground pipes can help alleviate this issue; although they can connect a distance of up to 10 tiles, their volume is always equivalent to two pipes.

'''[[Pump]]s''' use electrical power to transfer fluids in one direction very quickly. They also block any back-flow, which means they can pressurize a section of piping, filling it as much as possible. This is very useful to counteract the "thin spread" outlined above, among other things. They can also be disabled using the [[circuit network]] which stops fluid flow through the pump.

The table below shows how fast will fluid flow in a pipeline with a certain frequency of pumps. If a higher flow rate is desired, pumps should be placed more frequently. Because underground pipes only count as 2 regular pipes in terms of volume, a full-length section only counts as two pipes in this table, if a pump is placed between each underground section. Placing a filled storage tank before a pump ensures maximum possible flow rate and is therefore a suitable start of any pipeline.

{| class="wikitable mw-collapsible"
|-
! Number of pipes between two pumps !! Maximum flow  (u/sec)
|-
| 0 (pump to pump) || 12000
|-
| 0 (tank to pump) || 12000
|-
| 0 (pump to tank) || 12000
|-
| 0 (pump to boiler to pump) || 12000
|-
| 0 (pump to 2 boilers to pump) || 6000
|-
| 1 || 6000
|-
| 2 || 3000
|-
| 3 || 2250
|-
| 7 || 1500
|-
| 12 || 1285
|-
| 17 || 1200
|-
| 20 || 1169
|-
| 30 || 1112
|-
| 50 || 1067
|-
| 100 || 1033
|-
| 150 || 1022
|-
| 200 || 1004
|-
| 261 || 800
|-
| 300 || 707
|-
| 400 || 546
|-
| 500 || 445
|-
| 600 || 375
|-
| 800 || 286
|-
| 1000 || 230
|-
|}

=== Barrels ===
'''[[Barrel]]s''' are used by [[Assembling machine]]s to effectively "bottle" fluids into an item that can be handled like any other item; carried in an inventory, placed in chests and handled by [[Inserters]]. This allows the player to transport fluids via the [[belt transport system]] and the [[logistic network]]. Assembling machines are also used to empty the barrels, depositing their contents to pipes and leaving an empty barrel for another use.

=== Railway ===

'''[[Railway]]''' is another method of transporting fluids, and can be conducted in two ways: Either the fluids are directly pumped into a [[fluid wagon]], or they are poured into barrels and loaded into [[cargo wagon]]s. Both methods have their distinct differences: The cargo wagon can hold different types of fluid barrels, however the fluid wagon can hold more fluid (25k versus 20k) and can be emptied and filled in mere seconds, at speeds inserters with barrels require an inadequate expenditure of resources to match; while [[Stack inserter]]s can transfer barrels quickly, machines for barreling fluids are slow.[https://forums.factorio.com/viewtopic.php?f=5&t=48185] On the other hand, the fluids can be barreled/unbarreled while trains are en route.

==See also==

* [[Oil processing]]
* [[Power production]]
* [https://forums.factorio.com/viewtopic.php?f=18&t=19851 In-depth post about fluid mechanics]
* [https://www.reddit.com/r/factorio/comments/6w9kwi/factorio_and_fluid_mechanics_science_facts_myths/ Another in-depth examination of fluid mechanics]
* [https://forums.factorio.com/viewtopic.php?f=5&t=46030 How many pumps after how many pipes for how much throughput]

Console

2020-06-03T01:58:16Z

DaveMcW: /* Modding tools */ Access a mod's data

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

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

== Normal commands ==

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

== Multiplayer commands ==

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

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

=== Create new force and change your force to new one ===
This creates new force with specified name, than you get this new force.
<syntaxhighlight lang="lua">
/c game.player.force = game.create_force("new_force_name")
</syntaxhighlight>

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

== Research scripts ==

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

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

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

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

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

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

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

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

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

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

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

== See also ==

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

Console

2020-06-03T01:56:15Z

DaveMcW: /* Modding tools */ Access a mod's private data

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

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

== Normal commands ==

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

== Multiplayer commands ==

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

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

=== Create new force and change your force to new one ===
This creates new force with specified name, than you get this new force.
<syntaxhighlight lang="lua">
/c game.player.force = game.create_force("new_force_name")
</syntaxhighlight>

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

== Research scripts ==

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

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

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

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

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

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

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

=== Access a mod's private 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 private data from Resource Spawner Overhaul:
<syntaxhighlight lang="lua">
/c __rso-mod__ game.player.print(serpent.dump(global))
</syntaxhighlight>

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

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

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

== See also ==

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

Console

2020-06-03T01:50:23Z

DaveMcW: /* Scripting and cheat commands */

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

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

== Normal commands ==

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

== Multiplayer commands ==

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

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

=== Create new force and change your force to new one ===
This creates new force with specified name, than you get this new force.
<syntaxhighlight lang="lua">
/c game.player.force = game.create_force("new_force_name")
</syntaxhighlight>

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

== Research scripts ==

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

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

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

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

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

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

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

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

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

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

== See also ==

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

Console

2020-06-03T01:49:49Z

DaveMcW: /* Scripting and cheat commands */ Updated description

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

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

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

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

== Normal commands ==

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

== Multiplayer commands ==

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

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

=== Create new force and change your force to new one ===
This creates new force with specified name, than you get this new force.
<syntaxhighlight lang="lua">
/c game.player.force = game.create_force("new_force_name")
</syntaxhighlight>

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

== Research scripts ==

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

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

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

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

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

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

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

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

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

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

== See also ==

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

Military units and structures

2020-04-12T12:45:39Z

DaveMcW: /* Military structures */ Fix typo

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

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

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

__TOC__

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

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

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

Military units and structures

2020-01-23T23:35:16Z

DaveMcW:

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

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

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

__TOC__

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

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

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

Military units and structures

2020-01-23T16:48:51Z

DaveMcW: In Factorio 0.18.0 biters and spitters no longer attack construction/logistic robots.

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

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

There are a few exceptions:
* [[Artillery turret]]s and [[Artillery wagon]]s will not attack any units.
* Biters and spitters will not attack [[construction robot]]s or [[logistic robot]]s.

__TOC__

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

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

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

Locomotive

2020-01-23T16:42:20Z

DaveMcW: In version 0.18.1 biters no longer target rails

{{Languages}}
{{:Infobox:Locomotive}}

The '''Locomotive''' is the engine for movement of [[Railway|trains]] over [[Railway#Tracks|track]]. Trains are useful for moving large amounts of items over large distances.

Locomotives are also good vehicles for the player to reach fixed destinations, as they are considerably faster than the [[car]] or [[tank]]. Naturally they do not have the same freedom of movement, however, as they are confined to the track. They can be set up to travel automatically between [[train stop]]s, or be controlled manually, even if the [[player]] is in a [[cargo wagon]] attached to the train, rather than the controlling locomotive itself. Automatic trains can also use [[rail signal]]s and [[rail chain signal]]s to designate different or changing paths on a railway, as well as manage multiple trains on multiple or intertwining tracks.

Locomotives are [[burner devices]] and require [[fuel]] to run; the more powerful the fuel used, the faster the locomotive's acceleration and top speed will be. [[Solid fuel]], [[rocket fuel]] and [[nuclear fuel]] will give +20%, +80% and +150% acceleration respectively, and provide +5%, +15% and +15% for top speed respectively. Multiple locomotives can be used on a single train to increase its speed.

While locomotives can be assembled by hand, the [[engine unit]] for it require [[Assembling machine|automated construction]] to build, so it cannot be built from raw materials by hand. The color of the locomotive can be customized.

== Connecting/Disconnecting a locomotive ==
[[File:locomotive_gui.png|thumb|right|200px|Locomotive GUI]]

To connect locomotives, cargo wagons or [[fluid wagon]]s to each other, either place the cars next to each other on the track (there will be an outlined green connection), or connect an already existing disconnected car by driving the locomotive near the car and press {{Keybinding|G}} by default. To disconnect the last car in a train, press {{Keybinding|V}} by default.

== Defense ==
Locomotives in transit can usually crash through everything in its way (including biters, [[car|other]] [[tank|vehicles]], and the player). However, if the locomotive is moving too slowly, or the target is too tough, it will stop the train instead. If the locomotive hits an [[enemy]], the enemies will fight back and try to destroy it.

[[Construction robot]]s are a good way to automatically repair damage at train stations.

[[File:train_kills_biters.gif|frame|none|Train killing three big biters.]]

== Maximum speed ==
The maximum speed that a locomotive can get to depends on the train that it is pulling. The speed of an accelerating, fully fueled, train is calculated every tick by the game with the following formula:

train_speed = max(0, abs(train_speed) - train_friction_force ÷ train_weight)
train_speed = train_speed + (10 × number_of_locomotives_in_moving_direction × fuel_acceleration_bonus ÷ train_weight)
train_speed = train_speed × (1 - air_resistance_of_front_rolling_stock ÷ (train_weight ÷ 1000))

Where train_friction_force is the summed up friction of each wagon and locomotive and train_weight is the summed up weight of each wagon and locomotive, see their individual pages for the weight values. The friction and air resistance of wagons and locomotives can be found in their prototypes. The calculated train_speed is capped to <code>max_speed = 1.2 * fuel_top_speed_multiplier</code>.

== Fuel duration (in seconds) ==

{| class="wikitable"
|-
! 1 item of !! Burning time in seconds
|-
| {{Icon|Wood}} || 3.33
|-
| {{Icon|Coal}} || 6.67
|-
| {{Icon|Solid fuel}} || 20
|-
| {{Icon|Rocket fuel}} || 166.67
|-
| {{Icon|Nuclear fuel}} || 2016.67
|}

== Driving controls ==
''These are the default bindings. They can be changed in the Options menu.''
{|
|Enter/Exit
|{{Keybinding|enter}}
|-
|Accelerate
|{{Keybinding|W}}
|-
|Decelerate/Reverse
|{{Keybinding|S}}
|-
|Pick which fork to take at junction
|{{Keybinding|A}},{{Keybinding|D}}
|-
|Connect/Disconnect rolling stock
|{{Keybinding|G}},{{Keybinding|V}}
|}

== Achievements ==
Locomotives are directly connected to the following achievements:
{{Achievement|getting-on-track}}
{{Achievement|getting-on-track-like-a-pro}}
{{Achievement|watch-your-step}}

== Gallery ==
<gallery widths=320px>
File:trains_colors.png|The player among different colored locomotives.
</gallery>

== History ==
{{history|0.17.0|
* Locomotive fuel consumption doubled.}}

{{history|0.16.0|
* Locomotive will show train ID in its tooltip. The ID can be used in circuit network conditions.}}

{{history|0.15.19|
* Locomotive snaps to a train stop when placing the first locomotive next to the train stop.}}

{{history|0.15.7|
* Inserters will no longer take fuel from locomotives and instead will take the burnt result items if the locomotive fuel uses that system.}}

{{history|0.15.0|
* Renamed "diesel-locomotive" to "locomotive"}}

{{history|0.14.0|
* Added support for equipment grids in locomotives.}}

{{history|0.13.0|
* New locomotive graphics.
* Can now be colored.
* Trains are now regular size in horizontal and vertical orientations.
}}

{{history|0.12.1|
* Trains that are moving automatically cannot be rotated.}}

{{history|0.12.0|
* Now show contents in tooltip.}}

{{history|0.11.18|
* Increased the crafting cost of the cargo wagon and locomotive.
* Removing and merging the locomotive of a train without any additional locomotives doesn't clear the schedule anymore.
}}

{{history|0.11.6|
* Copy paste can now be used for train schedules.}}

{{history|0.10.2|
* Now recalculates path on rotation.}}

{{history|0.10.0|
* Backer names are used for locomotives.}}

{{history|0.9.0|
* Recipe change}}

{{history|0.5.0|
* Train can find the path backward when it has locomotives in the back
* New locomotive graphics.
* Locomotive + wagon + rails are more expensive.
}}

{{history|0.4.1|
* Smooth (precise) rolling stock placement.
* Rotating while building affects the direction of the rolling stock.
* Rolling stocks can be disconnected from both sides.
}}

{{history|0.4.0|
* Locomotive uses fuel.
* Locomotive and Car are minable
* Easier riding in locomotive and car (accelerate vs. brake vs. reverse)
* Automated train transportation. Trains can be given schedule to go to Train Stops (named after backers).
}}

{{history|0.2.8|
* Now shows health bar below locomotive.}}

{{history|0.2.1|
* Now emits light if active.}}

{{history|0.1.0|
* Introduced}}

==See also==
* [[Railway]]
* [[Cargo wagon]]
* [[Fluid wagon]]

{{LogisticsNav}}
{{C|Transport}}

Locomotive

2019-12-17T10:06:38Z

DaveMcW: /* Defense */

{{Languages}}
{{:Infobox:Locomotive}}

The '''Locomotive''' is the engine for movement of [[Railway|trains]] over [[Railway#Tracks|track]]. Trains are useful for moving large amounts of items over large distances.

Locomotives are also good vehicles for the player to reach fixed destinations, as they are considerably faster than the [[car]] or [[tank]]. Naturally they do not have the same freedom of movement, however, as they are confined to the track. They can be set up to travel automatically between [[train stop]]s, or be controlled manually, even if the [[player]] is in a [[cargo wagon]] attached to the train, rather than the controlling locomotive itself. Automatic trains can also use [[rail signal]]s and [[rail chain signal]]s to designate different or changing paths on a railway, as well as manage multiple trains on multiple or intertwining tracks.

Locomotives are [[burner devices]] and require [[fuel]] to run; the more powerful the fuel used, the faster the locomotive's acceleration and top speed will be. [[Solid fuel]], [[rocket fuel]] and [[nuclear fuel]] will give +20%, +80% and +150% acceleration respectively, and provide +5%, +15% and +15% for top speed respectively. Multiple locomotives can be used on a single train to increase its speed.

While locomotives can be assembled by hand, the [[engine unit]] for it require [[Assembling machine|automated construction]] to build, so it cannot be built from raw materials by hand. The color of the locomotive can be customized.

== Connecting/Disconnecting a locomotive ==
[[File:locomotive_gui.png|thumb|right|200px|Locomotive GUI]]

To connect locomotives, cargo wagons or [[fluid wagon]]s to each other, either place the cars next to each other on the track (there will be an outlined green connection), or connect an already existing disconnected car by driving the locomotive near the car and press {{Keybinding|G}} by default. To disconnect the last car in a train, press {{Keybinding|V}} by default.

== Defense ==
Locomotives in transit can usually crash through everything in its way (including biters, [[car|other]] [[tank|vehicles]], and the player). However, if the locomotive is moving too slowly, or the target is too tough, it will stop the train instead. If the locomotive hits an [[enemy]], the enemies will fight back and try to destroy the train and the rails.

[[Construction robot]]s are a good way to automatically repair damage at train stations.

[[File:train_kills_biters.gif|frame|none|Train killing three big biters.]]

== Maximum speed ==
The maximum speed that a locomotive can get to depends on the train that it is pulling. The speed of an accelerating train can be calculated with the following formula:

train_speed = max(0, abs(train_speed) - train_friction_force ÷ train_weight)
train_speed = train_speed + (10 × number_of_locomotives_in_moving_direction × fuel_acceleration_bonus ÷ train_weight)
train_speed = train_speed × (1 - air_resistance_of_front_rolling_stock ÷ (train_weight ÷ 1000))

Where train_friction_force is the summed up friction of each wagon and locomotive and train_weight is the summed up weight of each wagon and locomotive, see their individual pages for the weight values. The calculated train_speed is capped to <code>max_speed = 1.2 * fuel_top_speed_multiplier</code>.

== Fuel duration (in seconds) ==

{| class="wikitable"
|-
! 1 item of !! Burning time in seconds
|-
| {{Icon|Wood}} || 3.33
|-
| {{Icon|Coal}} || 6.67
|-
| {{Icon|Solid fuel}} || 20
|-
| {{Icon|Rocket fuel}} || 166.67
|-
| {{Icon|Nuclear fuel}} || 2016.67
|}

== Driving controls ==
''These are the default bindings. They can be changed in the Options menu.''
{|
|Enter/Exit
|{{Keybinding|enter}}
|-
|Accelerate
|{{Keybinding|W}}
|-
|Decelerate/Reverse
|{{Keybinding|S}}
|-
|Pick which fork to take at junction
|{{Keybinding|A}},{{Keybinding|D}}
|-
|Connect/Disconnect rolling stock
|{{Keybinding|G}},{{Keybinding|V}}
|}

== Achievements ==
Locomotives are directly connected to the following achievements:
{{Achievement|getting-on-track}}
{{Achievement|getting-on-track-like-a-pro}}
{{Achievement|watch-your-step}}

== Gallery ==
<gallery widths=320px>
File:trains_colors.png|The player among different colored locomotives.
</gallery>

== History ==
{{history|0.17.0|
* Locomotive fuel consumption doubled.}}

{{history|0.16.0|
* Locomotive will show train ID in its tooltip. The ID can be used in circuit network conditions.}}

{{history|0.15.19|
* Locomotive snaps to a train stop when placing the first locomotive next to the train stop.}}

{{history|0.15.7|
* Inserters will no longer take fuel from locomotives and instead will take the burnt result items if the locomotive fuel uses that system.}}

{{history|0.15.0|
* Renamed "diesel-locomotive" to "locomotive"}}

{{history|0.14.0|
* Added support for equipment grids in locomotives.}}

{{history|0.13.0|
* New locomotive graphics.
* Can now be colored.
* Trains are now regular size in horizontal and vertical orientations.
}}

{{history|0.12.1|
* Trains that are moving automatically cannot be rotated.}}

{{history|0.12.0|
* Now show contents in tooltip.}}

{{history|0.11.18|
* Increased the crafting cost of the cargo wagon and locomotive.
* Removing and merging the locomotive of a train without any additional locomotives doesn't clear the schedule anymore.
}}

{{history|0.11.6|
* Copy paste can now be used for train schedules.}}

{{history|0.10.2|
* Now recalculates path on rotation.}}

{{history|0.10.0|
* Backer names are used for locomotives.}}

{{history|0.9.0|
* Recipe change}}

{{history|0.5.0|
* Train can find the path backward when it has locomotives in the back
* New locomotive graphics.
* Locomotive + wagon + rails are more expensive.
}}

{{history|0.4.1|
* Smooth (precise) rolling stock placement.
* Rotating while building affects the direction of the rolling stock.
* Rolling stocks can be disconnected from both sides.
}}

{{history|0.4.0|
* Locomotive uses fuel.
* Locomotive and Car are minable
* Easier riding in locomotive and car (accelerate vs. brake vs. reverse)
* Automated train transportation. Trains can be given schedule to go to Train Stops (named after backers).
}}

{{history|0.2.8|
* Now shows health bar below locomotive.}}

{{history|0.2.1|
* Now emits light if active.}}

{{history|0.1.0|
* Introduced}}

==See also==
* [[Railway]]
* [[Cargo wagon]]
* [[Fluid wagon]]

{{LogisticsNav}}
{{C|Transport}}

File:Compilatron.png

2019-12-17T08:51:40Z

DaveMcW:

Military units and structures

2019-12-17T08:25:53Z

DaveMcW: /* Military structures */ Added wiki links and force

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

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

Military structures, but not units, will also automatically be attacked by [[artillery turret]]s and [[artillery wagon]]s.

__TOC__

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

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

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

Military units and structures

2019-12-17T08:10:56Z

DaveMcW: /* Military units */ Added wiki links and force

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

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

Military structures, but not units, will also automatically be attacked by [[artillery turret]]s and [[artillery wagon]]s.

__TOC__

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

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

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

Tutorial

2019-12-17T08:05:08Z

DaveMcW: Added Compilatron image

{{Languages}}
The ''campaign'' gamemode is Factorio's equivalent of a story mode. Campaigns are pre-generated levels where the [[player]] must accomplish some preset task, such as scanning the surroundings, [[research]]ing a certain technology, or providing a certain amount of resources into a chest. Upon completion, a game finish report is given, similar to freeplay, where kills and completion time are tallied. Completing the campaigns is not necessary to play freeplay.

== Playing the campaign ==
[[File:Campaign_menu_screen.png|thumb|right|The menu to enter a Campaign.]]

To play a campaign, select '''Play''' from the title screen, then '''Start campaign'''. Select a campaign, and level, if applicable.

The campaign will load, and instructions will be displayed to the player. Then, the player may complete the task. For an added challenge, attempt to complete the campaign as fast as possible.

== Types of campaigns ==

There are a few different types of campaigns in Factorio. These types include:

=== Introduction ===

:''After crash landing on this alien world you will need to explore the area, harvest local resources and automate producing the items you need to survive.''

This campaign has only 1 level, called "Arrival". The Introduction is included with the demo.

[[File:Compilatron_large.png|thumb|right|Compilatron.]]

The Introduction explains basic concepts like mining, crafting automation, research and enemies. The player has to automate [[automation science pack]]s, build a radar and is then attacked by [[enemies|biters]]. To escape the biters, the player moves to a new base location where they have to set up [[power production]], automate more products and fight off an increasing amount of enemies while researching some technologies. During this journey, the player is accompanied by a robot companion called "Compilatron" which gives some goals to the player and offers assistance in the from of placing some buildings to improve mining automation.

=== Main campaign ===

There are plans to add a longer running campaign to the game. It is described as "guided freeplay" in [https://factorio.com/blog/post/fff-291 Friday Facts #291 - New Campaign].

=== Transport belt madness ===

So many chests and such a small island. Can you connect the chests without your head spinning?

=== Tight spot ===

Little space, limited resources and a fixed amount of time. Buy land and machines and sell your final product.

== See also ==

* [[Multiplayer]]

File:Compilatron.png

2019-12-17T07:46:53Z

DaveMcW:

Military units and structures

2019-12-11T16:19:55Z

DaveMcW: resolved prototype inheritance

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

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

Military buildings, but not units, will also be attacked by [[Artillery_turret|artillery turrets]] and [[Artillery_wagon|artillery wagons]].

__TOC__

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

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

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

Military units and structures

2019-12-11T15:18:34Z

DaveMcW: plural artillery turrets

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

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

Military buildings, but not units, will also be attacked by [[Artillery_turret|artillery turrets]] and [[Artillery_wagon|artillery wagons]].

__TOC__

== Modding ==
Military units and buildings are identified by a hard coded flag on certain prototypes (and their children). This cannot be changed by [[modding]]. The military prototypes are listed in the tables below.

== Military units ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Player.png|center]]
| Player
| [[Prototype/Character|Character]]
|-
| [[File:Defender_capsule.png|center]]
| Defender capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Distractor_capsule.png|center]]
| Distractor capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Destroyer_capsule.png|center]]
| Destroyer capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Construction_robot.png|center]]
| Construction robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Logistic_robot.png|center]]
| Logistic robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Land_mine.png|center]]
| Land mine
| [[Prototype/LandMine|LandMine]]
|-
| [[File:small_biter.png|center|64px]]
| Small biter
| [[Prototype/Unit|Unit]]
|-
| [[File:small_spitter.png|center|72px]]
| Small spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_biter.png|center|64px]]
| Medium biter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_spitter.png|center|72px]]
| Medium spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_biter.png|center|64px]]
| Big Biter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_spitter.png|center|72px]]
| Big spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_biter.png|64px]]
| Behemoth biter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_spitter.png|center|72px]]
| Behemoth spitter
| [[Prototype/Unit|Unit]]
|}

== Military buildings ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Gun_turret.png|center]]
| Gun turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Flamethrower_turret.png|center]]
| Flamethrower turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Laser_turret.png|center]]
| Laser turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Artillery_turret.png|center]]
| Artillery turret
| [[Prototype/ArtilleryTurret|ArtilleryTurret]]
|-
| [[File:Radar.png|center]]
| Radar
| [[Prototype/Radar|Radar]]
|-
| [[File:Small_worm.png|center|50px]]
| Small worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Medium_worm.png|center|50px]]
| Medium worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Big_worm.png|center|50px]]
| Big worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Behemoth_worm.png|center|50px]]
| Behemoth worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Biter_nest.png|center|50px]]
| Biter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
| [[File:Spitter_nest.png|center|50px]]
| Spitter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
|
| Player port
| [[Prototype/PlayerPort|PlayerPort]]
|-
|
| SimpleEntityWithForce
| [[Prototype/SimpleEntityWithForce|SimpleEntityWithForce]]
|}

Military units and structures

2019-12-11T15:15:40Z

DaveMcW: Clean up intro

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

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

Military buildings, but not units, will also be attacked by [[artillery turret]] and [[artillery wagon]].

__TOC__

== Modding ==
Military units and buildings are identified by a hard coded flag on certain prototypes (and their children). This cannot be changed by [[modding]]. The military prototypes are listed in the tables below.

== Military units ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Player.png|center]]
| Player
| [[Prototype/Character|Character]]
|-
| [[File:Defender_capsule.png|center]]
| Defender capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Distractor_capsule.png|center]]
| Distractor capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Destroyer_capsule.png|center]]
| Destroyer capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Construction_robot.png|center]]
| Construction robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Logistic_robot.png|center]]
| Logistic robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Land_mine.png|center]]
| Land mine
| [[Prototype/LandMine|LandMine]]
|-
| [[File:small_biter.png|center|64px]]
| Small biter
| [[Prototype/Unit|Unit]]
|-
| [[File:small_spitter.png|center|72px]]
| Small spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_biter.png|center|64px]]
| Medium biter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_spitter.png|center|72px]]
| Medium spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_biter.png|center|64px]]
| Big Biter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_spitter.png|center|72px]]
| Big spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_biter.png|64px]]
| Behemoth biter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_spitter.png|center|72px]]
| Behemoth spitter
| [[Prototype/Unit|Unit]]
|}

== Military buildings ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Gun_turret.png|center]]
| Gun turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Flamethrower_turret.png|center]]
| Flamethrower turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Laser_turret.png|center]]
| Laser turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Artillery_turret.png|center]]
| Artillery turret
| [[Prototype/ArtilleryTurret|ArtilleryTurret]]
|-
| [[File:Radar.png|center]]
| Radar
| [[Prototype/Radar|Radar]]
|-
| [[File:Small_worm.png|center|50px]]
| Small worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Medium_worm.png|center|50px]]
| Medium worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Big_worm.png|center|50px]]
| Big worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Behemoth_worm.png|center|50px]]
| Behemoth worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Biter_nest.png|center|50px]]
| Biter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
| [[File:Spitter_nest.png|center|50px]]
| Spitter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
|
| Player port
| [[Prototype/PlayerPort|PlayerPort]]
|-
|
| SimpleEntityWithForce
| [[Prototype/SimpleEntityWithForce|SimpleEntityWithForce]]
|}

Military units and structures

2019-12-11T15:15:14Z

DaveMcW:

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

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

Military buildings, but not units, will also be attacked by [[Artillery turret]] and [[Artillery wagon]].

__TOC__

== Modding ==
Military units and buildings are identified by a hard coded flag on certain prototypes (and their children). This cannot be changed by [[modding]]. The military prototypes are listed in the tables below.

== Military units ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Player.png|center]]
| Player
| [[Prototype/Character|Character]]
|-
| [[File:Defender_capsule.png|center]]
| Defender capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Distractor_capsule.png|center]]
| Distractor capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Destroyer_capsule.png|center]]
| Destroyer capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Construction_robot.png|center]]
| Construction robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Logistic_robot.png|center]]
| Logistic robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Land_mine.png|center]]
| Land mine
| [[Prototype/LandMine|LandMine]]
|-
| [[File:small_biter.png|center|64px]]
| Small biter
| [[Prototype/Unit|Unit]]
|-
| [[File:small_spitter.png|center|72px]]
| Small spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_biter.png|center|64px]]
| Medium biter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_spitter.png|center|72px]]
| Medium spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_biter.png|center|64px]]
| Big Biter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_spitter.png|center|72px]]
| Big spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_biter.png|64px]]
| Behemoth biter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_spitter.png|center|72px]]
| Behemoth spitter
| [[Prototype/Unit|Unit]]
|}

== Military buildings ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Gun_turret.png|center]]
| Gun turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Flamethrower_turret.png|center]]
| Flamethrower turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Laser_turret.png|center]]
| Laser turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Artillery_turret.png|center]]
| Artillery turret
| [[Prototype/ArtilleryTurret|ArtilleryTurret]]
|-
| [[File:Radar.png|center]]
| Radar
| [[Prototype/Radar|Radar]]
|-
| [[File:Small_worm.png|center|50px]]
| Small worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Medium_worm.png|center|50px]]
| Medium worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Big_worm.png|center|50px]]
| Big worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Behemoth_worm.png|center|50px]]
| Behemoth worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Biter_nest.png|center|50px]]
| Biter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
| [[File:Spitter_nest.png|center|50px]]
| Spitter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
|
| Player port
| [[Prototype/PlayerPort|PlayerPort]]
|-
|
| SimpleEntityWithForce
| [[Prototype/SimpleEntityWithForce|SimpleEntityWithForce]]
|}

Multiplayer

2019-12-11T14:37:31Z

DaveMcW: /* PvP */ Add link to military building article

{{Languages}}
In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

[[File:multiplayer_game_night.png|thumb|250px|A multiplayer game.]]Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.
** Make sure you configure your router's port forwarding correctly for port '''34197'''.
** Make sure your router does not [https://doc.pfsense.org/index.php/Static_Port randomize the source port] on packets outbound from '''34197'''. Some routers do this and require [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 additional configuration] to prevent it.
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

''See [[Console#Command_line_parameters]] for more command line parameters.''

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

==== Basic installation ====

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

==== Additional configuration ====

You can use a [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script can also simplify updating the server when combined with a [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

Additionally, if you plan to enable mods on your server a mod updater script can greatly simplify this process. Here are several existing options, or you can write your own!
* [https://github.com/pdemonaco/factorio-mod-updater Python Mod Updater]
* [https://github.com/astevens/factorio-mod-updater Ruby Mod Updater]

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/color r g b a
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[military units and buildings]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics.
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Player

2019-12-11T14:30:26Z

DaveMcW: Add link to military building article

{{Languages}}{{:Infobox:Player}}
Factorio is played from the angled top down perspective of the ''player''.

The ''physical representation'' (or the '''Engineer''') of the player is the ''character'', who is always at the center of view. In multiplayer, player characters will appear in different colors. Color can be set manually with the <code>/color</code> command, see [[Console#Change_Player_color|Console]]. These colors transfer to any entered [[car]] or [[tank]], depending on which player is driving them. These colors also transfer to [[gun turret]]s, [[laser turret]]s or [[gate]]s, depending on who they were placed by.

The character is '''part of the player''' and represents the physical existence of the player in the game-world. In technical terms: A character is just one property of the [[player]], and it is the only that can be controlled at a time.

The character's maximum [[Damage|health]] is 250 (without energy shields). The character's main inventory has 80 slots (without bonuses from [[Power_armor|power armor]], [[Toolbelt_(research)|toolbelt research]], or [[Character_logistic_trash_slots_(research)|logistic trash slots]]). Similar to the stationary radar, the character constantly reveals an area of 5×5 [[Map_structure#Chunk|chunks]], centered on the chunk the character occupies.

== Distinction between player and character ==

[[File:twoplayers.png|thumb|right|180x180px|Two different color characters in multiplayer.]]

Technically the player is only the "player-view". The player is unlike the ''character'', (the little person that runs around on the ground) The character is part of the player, but the player is not just the character.

You can for example play in god-mode (such as in the sandbox game mode). In that mode you don't have a character, only a player.

In other words, the Player is a term that encompasses both the internal code that defines a player, and the entity in game that interacts with machines/rocks/trees, which is the ''character''. While this distinction is important for modding and understanding the game's core, the terms can be used interchangeably for most conversations. For the purpose of this article, "player" will be used.

== World interaction ==
The player has six primary ways of interacting with the world:

# Crafting items personally from resources using the craft menu (Default open key: E)
# Placing entities or [[tile]]s by selecting them from the inventory or quickbar (Default: Left Mouse Button)
## Opening contextual menus for entities like [[Assembling machine|Assembly Machines]] or [[Chests]], using the same button
## Removing an entity from the world, returning it to your inventory (Default: '''Hold''' Right Mouse Button)
# Harvesting resources from a resource entity (Default: '''Hold''' RMB)
# Picking up non-placed items from the ground and placing them in your inventory (Default: Hold/press F)
# Firing weapons at [[Military_units_and_buildings|enemies]] (Default: Press or hold Spacebar depending on weapon)
# Passively with a flashlight that automatically turns on during the night time (which transfers to headlights if the player is in a vehicle.)

''For more key-bindings, see [[Keyboard bindings]]''

Note: The player can do that only, if his character owns the abilities for this. For example: He cannot fire a weapon, cause he has no weapons-slots.

== Death ==
When a player is killed, it leaves behind a corpse that lasts 15 minutes and contains all items that were located in the player's inventory, quickbar, trash slots, and equipment slots. 10 seconds after being killed, the player respawns at the center of the world.


== Quickbar and shortcut bar ==
{{Main|Quickbar}}
The quickbar is a user interface component for creating links to items that are always visible at the bottom of the screen. Once created they can be quickly selected at any time without needing to open the inventory. It shows between one and four bars from a set of ten available, each containing 10 slots. Clicking any filled slot will place the chosen item in the player's hand if available in the inventory.

{{Main|Shortcut bar}}
The shortcut bar is a group of icons for accessing regularly used features such as obtaining [[blueprint]]s and [[deconstruction planner]]s with a simple mouse click. It is always visible at the bottom of the screen, appearing to the right of the quickbar. The icons can be hidden and their order can be changed. A maximum of 12 icons can be visible at one time.

[[File:Quickbar and shortcut bar.png]]

== Gallery ==
<gallery mode="packed" heights=120px>
File:playerportrait.png|Portrait of the player character; seen when selecting the "First steps" campaign.
File:All_armor.png|The player character in every type of armor.
File:Multicolor_all.png|Different possible colors of players, cars, tanks, gun turrets and laser turrets. (Pre 0.17)
File:Playerflashlight.png|The player character's flashlight during the night.
File:dead_player.png|The player's corpse.
</gallery>

== History ==

{{history|0.13.14|
* Surplus items from crafting are again available for crafting other items. For example, crafting two green circuits will no longer result in two extra copper wires in the player's inventory. This only applies to items that are automatically crafted as a prerequisite; items the player has explicitly requested to craft will not be used to satisfy the dependencies of any further orders.}}

{{history|0.13.0|
* Armors have inventory size bonuses (10 for modular armor, 20 for power armor, 30 for power armor mk2).}}

{{history|0.12.1|
* Changed fast inventory transfer from the main player inventory so ctrl+clicking empty slots doesn't move items to the logistic trash slots.}}

{{history|0.12.0|
* New muzzle flash graphics.}}

{{history|0.11.4|
* Improved player running animation.}}

{{history|0.11.0|
* New player animation, depends on armor}}

{{history|0.10.9|
* Mining a chest now fails instead of spilling items onto the ground.}}

{{history|0.9.0|
* Player gets a separate warning icon when a building is destroyed.
* Recipe gui contains recipes not craftable by player (however, their tooltip shows machines where they can be crafted).}}

{{history|0.8.0|
* Player now starts with 1 [[burner mining drill]] and one [[stone furnace]] in the freeplay.
* The player can repair structures using [[repair pack]]s.}}

{{history|0.7.0|
* Player moves slower while shooting.}}

{{history|0.6.0|
* Added the ability for the player to request items directly from logistic robots.}}

{{history|0.5.0|
*Player picks all items in range when picking items on the ground, instead of 1 per tick
* Shooting particles added}}

{{history|0.4.0|
* Player slides around corners}}

{{history|0.2.8|
* Player no longer collides with [[Underground belt]].
* Added auto-targeting for guns.}}

{{history|0.2.1|
* Added warning message when the player tries to build in an invalid position.}}

{{history|0.2.0|
* Screen reddens when taking damage
* Character animations added}}

{{history|0.1.0|
* Introduced}}

== See also ==
* [[Armor]]
* [[Weapons]]
* [[Multiplayer]]

Artillery wagon

2019-12-11T14:28:15Z

DaveMcW: Add link to military building article

{{Languages}}{{:Infobox:Artillery wagon}}
The '''artillery wagon''' is an end-game wagon added in game version 0.16 mounting a [https://en.wikipedia.org/wiki/Railway_gun rail cannon] that can be added to a train. It fires [[artillery shell]]s, relatively slow-moving projectiles that explore chunks of terrain they travel across. The wagon gun has both automatic and manual (even longer-ranged) firing modes. Projectiles have sufficient damage to destroy spawners and any type of worm with a single hit, and have a modest area of effect. Infinitely-stacking research upgrades are available for range and firing speed, but not damage.

The [[artillery turret]] is essentially the same weapon, but deployed as a static structure like other turrets.

== Mechanics ==
Artillery wagons have a massive range, outranging fixed fortifications by a factor of 10 or more. In automatic mode, when the train is stopped, the artillery wagon will automatically scan for [[Military_units_and_buildings|enemy buildings]] (spawners and worms) and shoot at them. Automatic mode cannot target mobile units (biters and spitters); shells do, however, damage mobile units in the vicinity of impact normally.

In manual mode, a [[Artillery targeting remote|special item]] is used to point-and-click anywhere in the world, map, or zoomed-in map; each click corresponds to one shell delivered to that location, so long as any working artillery turrets and / or wagons are in range. Targeting remotes show the number of fire-ready (loaded and, for wagons, stationary) artillery pieces in range of cursor position when held. Manual fire can be ordered on unexplored areas; shells will explore all chunks they travel across (but no surrounding chunks).

Range in automatic mode is 224 tiles (7 chunks); in manual mode, 560 tiles (17.5 chunks). Infinite [[Artillery shell range (research)|research]] is available to increase range, at +30% of base range per level, applied to both automatic and manual range.

== Limitations ==
Aside from the considerable expense of research and assembly for both wagons and shells, there are certain considerations that make these wagons unwise as a full replacement for traditional base defenses, despite their phenomenal range and the advantage of mobility.

Artillery shelling will antagonize enemy mobile units in the vicinity of the impact into rushing the wagon's location at time of firing, regardless of their normal "aggro radius". Artillery wagons are relatively slow-firing, although infinite [[Artillery shell shooting speed (research)|research]] is available to improve firing speed, at +100% per level, affecting both wagons and stationary turrets and applying to both automatic and manual mode. They also cannot target mobile units in automatic mode. Importantly, artillery has a ''minimum'' range as well, which is 32 tiles.

Together, these limitations mean that an artillery wagon needs to be defended, or else moved around rapidly, in the latter case decreasing its value as base defense. For defense, any conventional approach such as walls, gun, laser, and / or flamethrower turrets, or the personal intervention of the player will do. However, players should keep in mind that extensive shelling of large biter-infested areas will produce massive attack waves centered on the position of the artillery piece at time of firing, and should plan close-range defenses accordingly.

Logistic considerations are also important, as artillery shells have a stack size of 1, meaning any-size container can only hold a modest supply and an inserter will only ever move a single shell at a time. Players may wish to consider assembling near artillery wagon stops if practical. The wagon itself can hold a supply of 100 shells (while artillery turrets only hold 15), providing a portable magazine of some size that can be towed around with the weapon without external storage.

== Train properties ==
The artillery wagon can fire while stopped at a train stop, but '''not''' when stopped at a red signal or when moving. When a train with an artillery wagon is stopped at a train stop, aiming and shooting counts as activity for the purposes of "X seconds of inactivity" departure conditions in the train's schedule. This includes the time that the wagon spends scanning the area around it to find enemies, which is done at 1 chunk per tick. Only when it has scanned all chunks and did not find an enemy it will count as inactive.

When part of a manual-mode (player-driven) train, artillery wagons will fire whenever the train is stopped, regardless of where it was stopped.

Artillery wagons weigh as much as 4 [[Cargo wagon|regular wagons]] (or 2 [[locomotive]]s) for the purposes of train acceleration calculations. Fortunately, [[nuclear fuel]] provides a massive 250% boost to acceleration (compared to 180% for rocket fuel, the next best type), making it an attractive fuel for artillery trains.

== Logistics ==
In addition to firing them, artillery wagons can be used to transport shells from place to place. Inserters will both load and unload artillery wagons in the same manner as they would any other wagon, with the obvious difference that artillery wagons can only take artillery shells as cargo. However, each artillery wagon can hold 100 shells, while a regular cargo wagon only holds 40.

Thus, artillery wagons are the most space-efficient method of transporting artillery shells by rail. They are not, however, the most mass-efficient one, as an artillery wagon weighs 4 times as much as a regular wagon, but holds only 2.5 times as many shells. Thus, if train length is not a concern but acceleration and / or fuel efficiency is, regular wagons are superior for transporting shells.

Furthermore, players need to keep in mind that an artillery wagon's auto-fire behavior cannot be turned off in any way, and wagons will auto-fire whenever the usual conditions (see above) are met. In cleared, defended areas, however, they can reliably function as shell transport wagons.

== Trivia ==
* [https://en.wikipedia.org/wiki/Railway_gun Large rail-transported cannon] were built in the late 19th and early 20th century, up until and including World War II. The larger models were heavy and very slow firing and took many hours to set up, but had a greater range and power per shot than any other weapon in existence at the time (considerably greater than battleship-size naval guns, for example). The advent of rocketry, as well as large bomber planes capable of deploying multi-ton bombs, eventually made these guns obsolete.
** Perhaps the best-known examples were the [https://en.wikipedia.org/wiki/Big_Bertha_(howitzer) ''Dicke Bertha''] (Big Bertha, literally "Fat Bertha") and the [https://en.wikipedia.org/wiki/Schwerer_Gustav ''Schwerer Gustav''] (Heavy Gustav), the largest gun ever fired.

== History ==

{{history|0.16.0|
* Introduced}}

== See also ==

* [https://www.factorio.com/blog/post/fff-220 Friday Facts #220 - The best Friday Facts ever]
* [[Artillery turret]]
* [[Artillery shell]]
* [[Artillery targeting remote]]
* [[Locomotive]]
* [[Railway]]

{{LogisticsNav}}
{{C|Transport}}

Artillery turret

2019-12-11T14:26:25Z

DaveMcW:

{{Languages}}{{:Infobox:Artillery turret}}
The artillery turret is a super-long-range static defense structure added in game version 0.16. It fires [[Artillery shell|artillery shells]], relatively slow-moving projectiles that explore chunks of terrain they travel across. The turret has both automatic and manual (even longer-ranged) firing modes. Projectiles have sufficient damage to destroy spawners and any type of worm with a single hit, and have a modest area of effect. Infinitely-stacking research upgrades are available for range and firing speed, but not damage.

The [[Artillery wagon|artillery wagon]] is essentially the same weapon, only mounted on a train car and therefore mobile.

== Mechanics ==
Artillery turrets have a massive range, outranging other fixed fortifications by a factor of 10 or more. There are no special limits on how many may be built or where and, being ammunition-based, these turrets do not require electric power to operate.

In automatic mode, they function much the same as other turrets, automatically scanning for valid targets within range and firing on them. Automatic mode can only target [[Military_units_and_buildings|enemy buildings]] (spawners and worms), not mobile units (biters and spitters); shells do, however, damage mobile units in the vicinity of impact normally.

In manual mode, an [[Artillery targeting remote]] is used to point-and-click anywhere in the world, map, or zoomed-in map; each click corresponds to one shell delivered to that location, so long as any working artillery turrets and / or wagons are in range. Targeting remotes show the number of fire-ready (loaded and, for wagons, stationary) artillery pieces in range of cursor position when held. Manual fire can be ordered on unexplored areas; shells will explore all chunks they travel across (but no surrounding chunks).

Range in automatic mode is 224 tiles (7 chunks); in manual mode, 560 tiles (17.5 chunks). Infinite [[Artillery shell range (research)|research]] is available to increase range, at +30% of base range per level, applied to both automatic and manual range.

== Limitations ==
Aside from the considerable expense of research and assembly for both turrets and shells, there are certain considerations that make a base defense based purely on these turrets unwise, despite their phenomenal range.

Artillery shelling will antagonize enemy mobile units in the vicinity of the impact into rushing the turret emplacement, regardless of their normal "aggro radius". Artillery turrets are relatively slow-firing, although infinite [[Artillery shell shooting speed (research)|research]] is available to improve firing speed, at +100% per level, affecting both stationary turrets and wagons and applying to both automatic and manual mode. They also cannot target mobile units in automatic mode. Importantly, artillery has a ''minimum'' range as well, which is 32 tiles.

Together, these limitations mean that an artillery turret needs to be defended by other means. Any conventional approach such as walls, gun, laser, and / or flamethrower turrets, or the personal intervention of the player will do. However, players should keep in mind that extensive shelling of large biter-infested areas will produce massive attack waves centered on the position of the artillery piece at time of firing, and should plan close-range defenses accordingly.

Logistic considerations are also important, as artillery shells have a stack size of 1, meaning any-size container can only hold a modest supply and an inserter will only ever move a single shell at a time. Players may wish to consider on-site assembly for permanent and semi-permanent emplacements. The turret itself can hold 15 shells, and the wagon version can hold a full 100, providing a buffer of some size in the event supply is interrupted.

== History ==

{{history|0.16.0|
* Introduced}}

== See also ==
* [[Artillery wagon]]
* [[Artillery shell]]
* [[Artillery targeting remote]]

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

Military units and structures

2019-12-11T14:19:08Z

DaveMcW: /* Military units */ Added worms

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

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

Military buildings, but not units, will also be attacked by:
* [[Artillery turret]]
* [[Artillery wagon]]

__TOC__

== Modding ==
Military units and buildings are identified by a hard coded flag on certain prototypes (and their children). This cannot be changed by [[modding]]. The military prototypes are listed in the tables below.

== Military units ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Player.png|center]]
| Player
| [[Prototype/Character|Character]]
|-
| [[File:Defender_capsule.png|center]]
| Defender capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Distractor_capsule.png|center]]
| Distractor capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Destroyer_capsule.png|center]]
| Destroyer capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Construction_robot.png|center]]
| Construction robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Logistic_robot.png|center]]
| Logistic robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Land_mine.png|center]]
| Land mine
| [[Prototype/LandMine|LandMine]]
|-
| [[File:small_biter.png|center|64px]]
| Small biter
| [[Prototype/Unit|Unit]]
|-
| [[File:small_spitter.png|center|72px]]
| Small spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_biter.png|center|64px]]
| Medium biter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_spitter.png|center|72px]]
| Medium spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_biter.png|center|64px]]
| Big Biter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_spitter.png|center|72px]]
| Big spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_biter.png|64px]]
| Behemoth biter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_spitter.png|center|72px]]
| Behemoth spitter
| [[Prototype/Unit|Unit]]
|}

== Military buildings ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Gun_turret.png|center]]
| Gun turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Flamethrower_turret.png|center]]
| Flamethrower turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Laser_turret.png|center]]
| Laser turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Artillery_turret.png|center]]
| Artillery turret
| [[Prototype/ArtilleryTurret|ArtilleryTurret]]
|-
| [[File:Radar.png|center]]
| Radar
| [[Prototype/Radar|Radar]]
|-
| [[File:Small_worm.png|center|50px]]
| Small worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Medium_worm.png|center|50px]]
| Medium worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Big_worm.png|center|50px]]
| Big worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Behemoth_worm.png|center|50px]]
| Behemoth worm
| [[Prototype/Turret|Turret]]
|-
| [[File:Biter_nest.png|center|50px]]
| Biter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
| [[File:Spitter_nest.png|center|50px]]
| Spitter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
|
| Player port
| [[Prototype/PlayerPort|PlayerPort]]
|-
|
| SimpleEntityWithForce
| [[Prototype/SimpleEntityWithForce|SimpleEntityWithForce]]
|}

Military units and structures

2019-12-11T14:04:47Z

DaveMcW: Add TOC

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

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

Military buildings, but not units, will also be attacked by:
* [[Artillery turret]]
* [[Artillery wagon]]

__TOC__

== Modding ==
Military units and buildings are identified by a hard coded flag on certain prototypes (and their children). This cannot be changed by [[modding]]. The military prototypes are listed in the tables below.

== Military units ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Player.png|center]]
| Player
| [[Prototype/Character|Character]]
|-
| [[File:Defender_capsule.png|center]]
| Defender capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Distractor_capsule.png|center]]
| Distractor capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Destroyer_capsule.png|center]]
| Destroyer capsule
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Construction_robot.png|center]]
| Construction robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Logistic_robot.png|center]]
| Logistic robot
| [[Prototype/FlyingRobot|FlyingRobot]]
|-
| [[File:Land_mine.png|center]]
| Land mine
| [[Prototype/LandMine|LandMine]]
|-
| [[File:small_biter.png|center|64px]]
| Small biter
| [[Prototype/Unit|Unit]]
|-
| [[File:small_spitter.png|center|72px]]
| Small spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_biter.png|center|64px]]
| Medium biter
| [[Prototype/Unit|Unit]]
|-
| [[File:medium_spitter.png|center|72px]]
| Medium spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_biter.png|center|64px]]
| Big Biter
| [[Prototype/Unit|Unit]]
|-
| [[File:big_spitter.png|center|72px]]
| Big spitter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_biter.png|64px]]
| Behemoth biter
| [[Prototype/Unit|Unit]]
|-
| [[File:behemoth_spitter.png|center|72px]]
| Behemoth spitter
| [[Prototype/Unit|Unit]]
|}

== Military buildings ==
{| class="wikitable"
|-
! Picture !! Name !! Prototype
|-
| [[File:Gun_turret.png|center]]
| Gun turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Flamethrower_turret.png|center]]
| Flamethrower turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Laser_turret.png|center]]
| Laser turret
| [[Prototype/Turret|Turret]]
|-
| [[File:Artillery_turret.png|center]]
| Artillery turret
| [[Prototype/ArtilleryTurret|ArtilleryTurret]]
|-
| [[File:Radar.png|center]]
| Radar
| [[Prototype/Radar|Radar]]
|-
| [[File:Biter_nest.png|center|50px]]
| Biter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
| [[File:Spitter_nest.png|center|50px]]
| Spitter spawner
| [[Prototype/EnemySpawner|EnemySpawner]]
|-
|
| Player port
| [[Prototype/PlayerPort|PlayerPort]]
|-
|
| SimpleEntityWithForce
| [[Prototype/SimpleEntityWithForce|SimpleEntityWithForce]]
|}

Enemies

2019-12-11T13:51:44Z

DaveMcW: /* Defense */ Add link to military building article

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

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

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

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

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

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

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

|}

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

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

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

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

Resistances:
*Explosion: 0/30%
|}

===Worms===

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

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

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

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

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

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

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

==Nests==

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

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

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

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

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

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

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

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

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

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

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

/evolution

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

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

=== Methods of increasing ===

The evolution factor is increased by three kinds of events:

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

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

The default settings are:

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

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

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

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

=== Spawn chances by evolution factor ===

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

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

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

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

'''Notes'''

* Data from version 0.16.51.

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

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

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

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

'''Comments'''

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

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

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

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

'''Computation of actual evolution factor'''

The actual EF can be computed as follow :

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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