Official Factorio Wiki - User contributions [en]

Console

2019-02-26T23:01:16Z

Tincopper2: speaker map list command

{{Languages}}
== Overview ==
The '''Console''' is Factorio's command-line interface.

The in-game console is used for:

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

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)

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

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

Note that the console can also accept raw Lua code as well as game commands.

=== Console history ===

The console has an inbuilt history; it's a bit like a text editor where only one line of text is displayed at a time.

Use the {{keybinding|↑}} and {{keybinding|↓}} keys to scroll through the console history.

Use the {{keybinding|←}} and {{keybinding|→}} keys to cursor through the currently displayed message or command, which you can edit (delete, insert, etc.) and resend (by pressing '''Return''').

The {{keybinding|Tab}} key will auto-complete commands and player ids.

== 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 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.
| 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 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
|-
| /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
|-
| /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 thats what I see
| Sends a message to the specified player.
| No
|-
| /w <player> <message>
| /w AzureDiamond thats 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
|-
| /c <command>
| Executes a Lua command.
|-
| /command <command>
| Executes a Lua command.
|-
| /measured-command <command>
| Executes a Lua command and measures time it took.
|-
| /silent-command <command>
| Executes a Lua command 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>

=== Cancel current research ===
Cancels the current research.
<syntaxhighlight lang="lua">
/c game.player.force.current_research = nil
</syntaxhighlight>

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

Add a powerful armor with equipment and some tools for construction:
<syntaxhighlight lang="lua">
/c local player = game.player
player.insert{name="power-armor-mk2", count = 1}
local p_armor = player.get_inventory(5)[1].grid
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "personal-roboport-mk2-equipment"})
p_armor.put({name = "night-vision-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
player.insert{name="construction-robot", count = 25}
player.insert{name="blueprint", count = 3}
player.insert{name="deconstruction-planner", count = 1}
player.insert{name="steel-axe", count = 10}
</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 game.forces.player.chart(game.player.surface, {{x = -2000, y = -2000}, {x = 2000, y = 2000}})
</syntaxhighlight>
Change 150 to the desired radius, higher values take longer.

=== 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.surfaces[1].find_entities_filtered{area = {{-1000, -1000}, {1000, 1000}}, force = "player", 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>

=== 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 local surface = game.player.surface
for c in surface.get_chunks() do
surface.destroy_decoratives({{c.x*32, c.y*32}, {c.x*32+32, c.y*32+32}})
end</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 autoplace = surface.map_gen_settings.autoplace_controls
autoplace[resource].size = "very-high"
autoplace[resource].frequency = "very-high"
autoplace[resource].richness = "very-high"
surface.map_gen_settings.autoplace_controls = autoplace</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 radius = 250
local surface=game.player.surface
local pp = game.player.position
local cnt = 0
for key, entity in pairs(surface.find_entities_filtered({force="enemy"})) do
if entity.position.x > pp.x - radius and entity.position.x < pp.x + radius
and entity.position.y > pp.y - radius and entity.position.y < pp.y + radius then
cnt = cnt+1
entity.destroy()
end
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 6.
<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 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
</syntaxhighlight>

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

== Command line parameters ==
'''As of Game Version 0.15.13'''

Command line parameters can be used to set settings in the command line before the game launches, this is useful mainly for advanced users or server hosts.

General options:
-h [ --help ] display help
--version show version information
-v [ --verbose ] enable verbose logging
-c [ --config ] PATH config file to use
--no-log-rotation don't rotate log file
--mod-directory PATH Mod directory to use
--check-unused-prototype-data Print a warning for all prototype values that were not accessed

Running options:
-s [ --map2scenario ] arg map to scenario conversion
-m [ --scenario2map ] arg scenario to map conversion
--apply-update arg immediately apply update package
--create FILE create a new map
--map-gen-settings FILE Map generation settings for use with --create. See data/map-gen-settings.example.json
--map-settings FILE Map settings for use with --create. See data/base/prototypes/map-settings.lua
--preset arg Name of the map generation preset to be used.
--generate-map-preview FILE Generate preview images of the map
--map-preview-size SCALE (=1,024) Size (in pixels) of map preview
--map-preview-scale SCALE (=1) Scale (meters per pixel) of map preview
--map-preview-offset X,Y (=0,0) Offset of the center of the map, in meters
--start-server FILE start a multiplayer server
--start-server-load-scenario FILE start a multiplayer server and load the specified scenario
--start-server-load-latest start a multiplayer server and load the latest available save
--until-tick TICK run a save until given map tick
--mp-connect ADDRESS start factorio and connect to address
--load-game FILE start Factorio and load a game in singleplayer
--benchmark FILE load save and run benchmark
--benchmark-ticks N (=1,000) number of ticks for benchmarking. Default is 1000
--force-opengl use OpenGL for rendering
--force-d3d use Direct3D for rendering
--fullscreen BOOL start game in windowed mode (saved to configuration)
--max-texture-size N maximal size of texture that the game can use (saved to configuration). Should be power of two greater than 2048
--graphics-quality arg accepted values: normal, low, very-low
--video-memory-usage arg accepted values: all, high, medium, low
--gfx-safe-mode resets some graphics settings to values that should work on most configurations
--shader arg enable/disable shader postprocessing (saved to configuration)
--disable-audio Disable audio. Mainly for faster startup during development.

Server options:
--port N network port to use
--bind ADDRESS[:PORT] IP address (and optionally port) to bind to
--rcon-port N Port to use for RCON
--rcon-password PASSWORD Password for RCON
--server-settings FILE Path to file with server settings. See data/server-settings.example.json
--server-whitelist FILE Path to file with server whitelist.
--server-banlist FILE Path to file with server banlist.
--console-log FILE Path to file where a copy of the server's log will be stored
--server-id FILE Path where server ID will be stored or read from

=== Multiplayer ===

--start-server SAVE

Will start a Headless (Dedicated) server, with no GUI.

--mp-connect ADDRESS
ADDRESS is the IP:port of the remote host. Port is optional.
Examples:

./factorio --mp-connect 192.168.1.101
./factorio --mp-connect 192.168.1.101:2345

As above, port can be specified by placing the port number after a colon in the address.

--map2scenario SAVE
Converts a save game to a User Scenario, allows saved game state to be loaded into map editor.
Assuming that save game name is "foo.zip", executing './factorio --map2scenario s1' will result in Factorio loading, opening the save file, and saving the scenario into the scenario folder.

== 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.x, game.player.position.y).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 ==

* http://lua-api.factorio.com/latest/ - Factorio API reference for latest version

Fluid system

2017-05-17T23:20:31Z

Tincopper2:

{{Languages}}
'''Liquids''' (''[[Liquids#Notes|note]]'') are non-solid [[items]], examples including water and oil.

==Behavior==

Liquids can only exist inside [[pipe]]s and certain buildings, meaning they cannot be carried by the player, moved using [[inserters]], dropped on the ground, or even dumped in a lake. They are counted in continuous fractions, rather than discrete integers. Liquids can be silently destroyed by removing buildings or pipes, mixing types of liquid, or at the input of a [[steam engine]].

== Types ==

{| class="wikitable"

| {{imagelink|water|Water}} || Used in creating [http://www.factorioforums.com/wiki/index.php?title=Electric_network electricity] and used in combination with other liquids.
|-
| {{imagelink|crude-oil|Crude Oil}} || Extracted from [[Oil Field]]s by [[Pumpjack]]s and can be converted to [[Petroleum Gas]], [[Light Oil]], and [[Heavy Oil]].
|-
| {{imagelink|petroleum-gas|Petroleum Gas}} || Converted from [[Crude Oil]]. Used to create various items.
|-
| {{imagelink|light-oil|Light Oil}} || Converted from [[Crude Oil]]. Used to create various items. Can be converted into [[Petroleum Gas]].
|-
| {{imagelink|heavy-oil|Heavy Oil}} || Converted from [[Crude Oil]]. Can be converted to [[Light Oil]] and [[Lubricant]].
|-
| {{imagelink|sulfuric-acid|Sulfuric Acid}} || Converted from [[Sulfur]], [[Iron Plate]]s, and [[Water]]. Can be used to create various items.
|-
| {{imagelink|lubricant|Lubricant}} || Converted from [[Heavy Oil]]. Used mainly to create [[Express transport belt]]s and [[Engine]]s.
|-
|}

== Machines ==

{| class="wikitable"

| {{imagelink|oil-refinery|Oil refinery}} || Converts [[Crude oil]] into [[Heavy oil]], [[Light oil]], and [[Petroleum gas]].
|-
| {{imagelink|chemical-plant|Chemical plant}} || Changes liquid to other forms as well as crafting some recipes that require liquids.
|-
| {{imagelink|pumpjack|Pumpjack}} || Extracts [[Crude oil]] from Oil fields.
|-
| {{imagelink|boiler|Boiler}} || When [[fuel|fueled]] increases the temperature of water flowing through.
|-
| {{imagelink|steam-engine|Steam engine}} || Uses heated water to generate [[Electric system|electricity]].
|-
|}

== Piping ==


''Piping'' is the most common way to move liquids in factorio.

Key entities used in piping and general liquid/gas handling:

{| class="wikitable"

| {{imagelink|pipe|Pipe}} || Used to direct the flow of liquids.
|-
| {{imagelink|pipe-to-ground|Pipe-to-ground}} || Used to cross other pipes or belts.
|-
| {{imagelink|storage-tank|Storage tank}} || Stores liquids for later use.
|-
| {{imagelink|pump|Offshore pump}} || Provides [[Water]] extracted from a water tile.
|-
| {{imagelink|small-pump|Small pump}} || Moves fluids from its input to its output when powered and prevents the opposite from happening always.
|-
|}

=== Pressure and throughput ===

Liquid will move in pipes from high pressure to low pressure. The pressure of a liquid in a pipe can be seen through the pipe window. A pipe with high pressure will show itself nearly full, a pipe with low pressure will show a small trickle of the liquid.

==Flow mechanics==
{{Main|Liquids/Pipe physics}}
All types of liquid have the same properties, like their fluidity, density, and heat capacity.

==Using water to generate power==
{{Main|Liquids/Hot|Power Production}}
Liquids can be used to generate power.

==Oil processing==
{{Main|Oil processing}}

==History==

Water was the first liquid to be added to the game. In [[Version0.9|v0.9]] the [[oil processing]] system, and therefore new liquids, including crude oil and petroleum gas, were added.

==See also==

* [[Liquids/Hot|Hot liquids]]
* [[Liquids/Pipe physics|Pipe physics]]

==Notes==

#"Fluids" is the proper term for the concept this article is about, as it explains the properties and uses of both liquids and gases.

{{C|Liquid network}}

Oil processing

2017-05-14T02:15:58Z

Tincopper2: 0.15.10 update

{{Languages}}
{{sublinks}}
Oil processing is a large part of Factorio. It was introduced in v0.9. Oil processing may refer to [[Oil processing (research)|the researched technology\\, the recipe used in the [[oil refinery]], or the overall workings of oil.

The values shown here are accurate for version 0.15. In 0.14, anything that produces, consumes, or stores any fluid does so at 1/10th of the quantities listed here. Solid items and ratios are unaffected; this is essentially just a cosmetic change of the displayed units.

== Beginner ==
=== Tutorial ===
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7975 Oil Tutorial], http://youtu.be/uL1eLmOSftw

=== Technologies ===
{| class="wikitable"
! Technology !! Description
|-
| {{icontech|oil-gathering||Oil processing (research)}} [[Oil processing (research)|Oil processing]] || Allows the player to set up a basic facility to mine, process, and use oil.
|-
| {{icontech|sulfur||Sulfur processing}} [[Sulfur processing]] || A prerequisite for the research of the [[Battery]], which is used in a handful items later on, including the [[Science pack 3]].
|-
| {{icontech|plastics||Plastics}} [[Plastics]] || The [[Plastic bar]] is an ingredient in the [[Advanced circuit]], which is used often later on.
|-
| {{icontech|fluid-handling||Fluid handling}} [[Fluid handling]] || Allows better control over your liquids, with the [[Storage Tank]] and [[Small Pump]].
|-
| {{icontech|advanced-oil-processing-tech||Advanced oil processing (research)}} [[Advanced oil processing (research)|Advanced oil processing]] || Gives you a new recipe for use in the [[Oil refinery]], allowing you to get more useful products from your [[Crude Oil]].
|-
| {{icontech|coal liquefaction (research)||Coal liquefaction (research)}} [[Coal liquefaction (research)|Coal liquefaction]] || Gives you a refinery recipe to turn excess coal into oil products. Introduced in version 0.15.0.
|-
| {{icontech|flammables||Flammables}} [[Flammables]] {{icontech|flame-thrower||Flame thrower}} [[Flame thrower]] || Gives you access to the [[Flamethrower]] and [[Flamethrower ammo]]
|-
|}

==Recipes==
There are various recipes that can be done regarding [[Oil processing]]. They are listed below.
{|class="wikitable"
!colspan="4"|After researching {{icontech|oil-gathering||Oil processing (research)}} [[Oil processing (research)|Oil processing]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|basic-oil-processing|Basic oil processing}} || {{icon|crude-oil|100|Crude Oil}} {{icon|time icon|5|Time}} || {{icon|oil-refinery||Oil refinery}} || {{icon|heavy-oil|30|Heavy oil}} {{icon|light-oil|30|Light oil}} {{icon|petroleum-gas|40|Petroleum gas}}
|-
| {{imagelink|solid-fuel-from-heavy-oil|Solid fuel}} || {{icon|heavy-oil|20|Heavy oil}} {{icon|time icon|3|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|solid-fuel|1|Solid fuel}}
|-
| {{imagelink|solid-fuel-from-light-oil|Solid fuel}} || {{icon|light-oil|10|Light oil}} {{icon|time icon|3|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|solid-fuel|1|Solid fuel}}
|-
| {{imagelink|solid-fuel-from-petroleum-gas|Solid fuel}} || {{icon|petroleum-gas|20|Petroleum gas}} {{icon|time icon|3|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|solid-fuel|1|Solid fuel}}
|-
| {{imagelink|lubricant|Lubricant}} || {{icon|heavy-oil|10|Heavy oil}} {{icon|time icon|1|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|lubricant|10|Lubricant}}
|-
!colspan="4"|After researching {{icontech|advanced-oil-processing-tech||Advanced oil processing (research)}} [[Advanced oil processing (research)|Advanced oil processing]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|advanced-oil-processing|Advanced oil processing}} || {{icon|crude-oil|100|Crude Oil}} {{icon|water|50|Water}} {{icon|time icon|5|Time}} || {{icon|oil-refinery||Oil refinery}} || {{icon|heavy-oil|10|Heavy oil}} {{icon|light-oil|45|Light oil}} {{icon|petroleum-gas|55|Petroleum gas}}
|-
| {{imagelink|heavy-oil-cracking|Heavy oil cracking}} || {{icon|heavy-oil|40|Heavy oil}} {{icon|water|30|Water}} {{icon|time icon|5|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|light-oil|30|Light oil}}
|-
| {{imagelink|light-oil-cracking|Light oil cracking}} || {{icon|light-oil|30|Light oil}} {{icon|water|30|Water}} {{icon|time icon|5|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|petroleum-gas|20|Petroleum gas}}
|-
!colspan="4"|After researching {{icontech|fluid-handling||Fluid handling}} [[Fluid handling]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|fill-crude-oil-barrel|Fill crude oil barrel}} || {{icon|barrel-empty|1|Empty barrel}} {{icon|crude-oil|250|Crude Oil}} {{icon|time icon|1|Time}} || {{icon|assembling-machine-2||Assembling machine 2}} or {{icon|assembling-machine-3||Assembling machine 3}} || {{icon|crude-oil-barrel|1|Crude oil barrel}}
|-
| {{imagelink|empty-crude-oil-barrel|Empty crude oil barrel}} || {{icon|crude-oil-barrel|1|Crude oil barrel}} {{icon|time icon|1|Time}} || {{icon|assembling-machine-2||Assembling machine 2}} or {{icon|assembling-machine-3||Assembling machine 3}} || {{icon|barrel-empty|1|Empty barrel}} {{icon|crude-oil|250|Crude Oil}}
|-
!colspan="4"|After researching {{icontech|sulfur||Sulfur processing}} [[Sulfur processing]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|sulfur|Sulfur}} || {{icon|water|30|Water}} {{icon|petroleum-gas|30|Petroleum gas}} {{icon|time icon|1|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|sulfur|2|Sulfur}}
|-
| {{imagelink|sulfuric-acid|Sulfuric Acid}} || {{icon|iron-plate|1|Iron plate}} {{icon|sulfur|5|Sulfur}} {{icon|water|100|Water}} {{icon|time icon|1|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|sulfuric-acid|50|Sulfuric Acid}}
|-
!colspan="4"|After researching {{icontech|Advanced-electronics-research||Advanced electronics}} [[Advanced electronics]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|processing-unit|Processing unit}} || {{icon|electronic-circuit|20|Electronic circuit}} {{icon|advanced-circuit|2|Advanced circuit}} {{icon|sulfuric-acid|5|Sulfuric acid}} {{icon|time icon|15|Time}} || {{icon|assembling-machine-2||Assembling machine 2}} or {{icon|assembling-machine-3||Assembling machine 3}} || {{icon|processing-unit|1|Processing unit}}
|-
!colspan="4"|After researching {{icontech|Battery-research||Battery (research)}} [[Battery (research)|Battery]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|battery|Battery}} || {{icon|iron-plate|1|Iron plate}} {{icon|copper-plate|1|Copper plate}} {{icon|sulfuric-acid|20|Sulfuric acid}} {{icon|time icon|5|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|battery|1|Battery}}
|-
!colspan="4"|After researching {{icontech|plastics||Plastics}} [[Plastics]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|plastic-bar|Plastics}} || {{icon|coal|1|Coal}} {{icon|petroleum-gas|30|Petroleum gas}} {{icon|time icon|1|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|plastic-bar|2|Plastic bar}}
|-
!colspan="4"|After researching {{icontech|flammables||Flammables}} [[Flammables]] and {{icontech|flame-thrower||Flame thrower}} [[Flame thrower]]:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|flame-thrower-ammo|Flamethrower ammo}} || {{icon|iron-plate|5|Iron plate}} {{icon|heavy-oil|25|Heavy oil}} {{icon|light-oil|25|Light oil}} {{icon|time icon|3|Time}} || {{icon|chemical-plant||Chemical plant}} || {{icon|flame-thrower-ammo|1|Flamethrower ammo}}
|-
!colspan="4"|After researching {{icontech|coal liquefaction||}} [[Coal liquefaction (research)|Coal liquefaction]], added in 0.15.0:
|-
! Process !! Input !! Machine !! Output
|-
| {{imagelink|coal liquefaction|Coal liquefaction (research)|Coal liquefaction}} || {{icon|coal|10|Coal}} {{icon|heavy-oil|25|Heavy oil}} {{icon|steam|50|Steam}} {{icon|time icon|5|Time}} || {{icon|oil-refinery||Oil refinery}} || {{icon|heavy-oil|35|Heavy oil}} {{icon|light-oil|15|Light oil}} {{icon|petroleum-gas|20|Petroleum gas}}
|}

==Mechanics & Usage==
To extract, process and use oil and its connected products, research, as shown above, is needed.

===Overview===
[[File:Example-Oil-Refining.png|thumb|256px|Crude oil being drilled and refined.]] [[File:Example-Oil-Cracking.png|thumb|256px|Oil being cracked into lower forms.]] [[File:Example-Oil-Usage.png|thumb|256px|Oil being used to create plastic and batteries.]]
[[Pumpjack]]s need to be placed on top of the middle of the oil well. Given [[Electric network|electricity]] (90kW, upgradeable), [[Pumpjack]]s will produce a certain amount of [[Crude oil]] per second, shown on the right, at the bottom of the information panel. Over time this value will decrease down to a minimum of 0.1 oil/s, providing infinite oil at a very low rate.

All liquids can be transported by [[Pipe]]s, only Crude oil can be filled into [[Barrel]]s and moved with the [[Railway network]] or other [[vehicle]]s.

The Crude Oil then needs to be refined in an [[Oil refinery]]. The Oil refinery also needs Power provided by an [[Electric network]]. It has a much higher demand, at 420kW, but it is also upgradeable. The oil refinery needs to have a recipe set (see above for available recipes). Once it is set, the inputs and outputs show what needs to be, and what will be supplied. You cannot move the locations of these, only rotate the entire machine. Make sure that the products have somewhere to go (preferably [[Storage Tank|Storage Tanks]]), as the refinery will stop production of all products if one product output is full.

Now you have the three basic products. [[Heavy Oil]], [[Light Oil]] and [[Petroleum Gas]]. Both Heavy Oil and Light Oil can be cracked to the next lower type in a [[Chemical plant]] (recipe above). This is useful if you've got lots of Light Oil, but are lacking in [[Petroleum Gas]] (A common problem).

From here, after some research, you can use the oil products to create various products. They are all listed above.

=== Tips ===
* [[Lubricant]]
** If you run your Heavy Oil pipe from the refineries past a Lubricant-making Chemical Plant before sending it to the cracking Chemical Plants, you can be sure that the Lubricant production will have priority over cracking.
** Most games will only ever need one lubricant-producing Chemical Plant and one Storage Tank for the lubricant.
** Since Lubricant is only used for blue belts and electric engines, and the only other use of Heavy Oil is flamethrower ammo (production of which is either best placed in your oil refinery or elided entirely) and cracking into Light Oil (the Heavy Oil to [[Solid fuel]] production ratio is terrible compared to cracking it first), you may want to consider placing your production of robots and belt assembly nearby your oil refineries, so lubricant doesn't need to be sent as far.

=== Items to handle fluids ===
{| class="wikitable"
|-
| {{imagelink|pumpjack|Pumpjack}} || Pumpjacks mine the Crude Oil from the [[Oil field|oil fields]], and let you move it by Pipe.
|-
| {{imagelink|oil-refinery|Oil refinery}} || Refines Crude Oil into basic oil products (Heavy/Light Oil and Petroleum Gas).
|-
| {{imagelink|chemical-plant|Chemical plant}} || Like the Assembling machine, used to automate processing of liquids and crafting.
|-
| {{imagelink|storage-tank|Storage Tank}} || Stores up to 25000 units of any liquid.
|-
| {{imagelink|pump|Pump}} || Allows you to pump liquids from one area to another. Used inline (between pipes). Also used to pump fluids into [[fluid wagon]]s.
|-
| {{imagelink|offshore-pump|Offshore pump}} || Allows you to pump water up from a body of water.
|-
| {{imagelink|assembling-machine-2|Assembling machine 2}} {{imagelink|assembling-machine-3|Assembling machine 3}} || Allows you to craft items using liquids, used mainly for Barrels.
|-
| {{imagelink|pipe|Pipe}} || Allows transporting of liquids from one location to another.
|-
| {{imagelink|pipe-to-ground|Pipe to ground}} || A Pipe, but under the ground, acting similar to [[Underground belts]].
|-
| {{imagelink|boiler|Boiler}} || Transforms [[water]] into [[steam]].
|-
| {{imagelink|steam-engine|Steam engine}} || Destroys any fluid it receives. Can be used as a flare stack, a wasteful way to get rid of unused oil-products.
|-
| {{imagelink|fluid_wagon|Fluid wagon}} || Carries up to 75000 units of liquid by rail, in three tanks of 25000 each.
|}

== Advanced ==

=== Optimal ratio to produce petroleum gas ===
The optimal ratio is the ratio of buildings in which they can all work without jamming or having inactive superfluous. For example, when you apply '''1''' Oil Refinery to the optimal Advanced oil processing ratio [5 : 1 : 7], you get ['''1''' : 0.20 : 1.4]. Round that up to get ['''1''' : 1 : 2], which means:
* 1 Oil Refinery on Advanced oil processing
* 1 Chemical plant on Heavy oil cracking
* 2 Chemical plants on Light oil cracking

The setup above will not jam, but it will have temporarily inactive buildings. If you round down, it will no longer have inactive buildings, but it will jam (over time).

This can be sped up with modules, but to prevent jams or inactive buildings, it is recommended to speed everything up evenly. When slowing down (by using [[Productivity module]]s) you are better off experimenting on altering the ratio or the speed on certain buildings, since these ratios are only mathematically correct if all the buildings have the same speed, and have 100% productivity (so no added bonuses).

Calculating the optimal ratios is relatively challenging, since not all of the durations of the processes are the same (the crafting speed of a chemical plant is 1.25, but the refinery's is 1.0). If this were not taken in account, it will lead to (temporarily) inactive buildings, which is not optimal.

==== Basic oil processing ====
{| class="wikitable"
! Ratio !! Building !! Process !! Recipe
|-

| 5 || {{imagelink|oil-refinery|Oil refinery}} || {{imagelink|basic-oil-processing|Basic oil processing}} || {{icon|time icon|5|Time}}{{icon|crude-oil|100|Crude Oil}} → {{icon|heavy-oil|30|Heavy Oil}}{{icon|light-oil|30|Light Oil}}{{icon|petroleum-gas|40|Petroleum Gas}}
|-
| 3 || {{imagelink|chemical-plant|Chemical plant}} || {{imagelink|heavy-oil-cracking|Heavy oil cracking}} || {{icon|time icon|5|Time}}{{icon|water|30|Water}}{{icon|heavy-oil|40|Heavy Oil}} → {{icon|light-oil|30|Light Oil}}
|-
| 7 || {{imagelink|chemical-plant|Chemical plant}} || {{imagelink|light-oil-cracking|Light oil cracking}} || {{icon|time icon|5|Time}}{{icon|water|30|Water}}{{icon|light-oil|30|Light Oil}} → {{icon|petroleum-gas|20|Petroleum Gas}}
|-
|}

{| class="wikitable"
! Buildings !! Input/s !! Output/s
|-
| {{icon|oil-refinery|5|Oil Refinery}} {{icon|chemical-plant|10|Chemical plant}} || {{icon|water|75|Water}} {{icon|crude-oil|100|Crude Oil}} || {{icon|petroleum-gas|93|Petroleum Gas}}

|}

==== Advanced oil processing ====
{| class="wikitable"
! Ratio !! Building !! Process !! Recipe
|-

| 5 || {{imagelink|oil-refinery|Oil refinery}} || {{imagelink|advanced-oil-processing|Advanced oil processing}} || {{icon|time icon|5|Time}}{{icon|water|50|Water}}{{icon|crude-oil|100|Crude Oil}} → {{icon|heavy-oil|10|Heavy Oil}}{{icon|light-oil|45|Light Oil}}{{icon|petroleum-gas|55|Petroleum Gas}}
|-
| 1 || {{imagelink|chemical-plant|Chemical plant}} || {{imagelink|heavy-oil-cracking|Heavy oil cracking}} || {{icon|time icon|5|Time}}{{icon|water|30|Water}}{{icon|heavy-oil|40|Heavy Oil}} → {{icon|light-oil|30|Light Oil}}
|-
| 7 || {{imagelink|chemical-plant|Chemical plant}} || {{imagelink|light-oil-cracking|Light oil cracking}} || {{icon|time icon|5|Time}}{{icon|water|30|Water}}{{icon|light-oil|30|Light Oil}} → {{icon|petroleum-gas|20|Petroleum Gas}}
|-
|}
{| class="wikitable"
! Buildings !! Input/s !! Output/s
|-
| {{icon|oil-refinery|5|Oil Refinery}} {{icon|chemical-plant|8|Chemical plant}} || {{icon|water|110|Water}} {{icon|crude-oil|100|Crude Oil}} || {{icon|petroleum-gas|108|Petroleum Gas}}

|}

=== Crude oil transport ===
[[File:Pumping_station.jpg|thumb|256px|Autonomus installation for manual pickup of [[Crude oil barrel]]s.]]
Since oil fields practically can deplete, new sources will be demanded. There are many different ways to overcome this problem:
* Pipes/Belts
* Manual pick-up
* Trains
* Robots (Troublesome over long distances)

== See also ==
* [[Liquids]]
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=7057 Oil Production: What is more efficient?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=7636 What to do with oil?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7842 Dump valve/Open pipe?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=8832 I did the Math on Oil Production]

Radar

2017-05-10T19:30:42Z

Tincopper2: Grammar

{{Languages}}
{{:Radar/infobox}}
The radar triggers charting of the map of the force it belongs to.

It can be used to provide a small area of remote vision on the map; it also allows periodic scanning of distant chunks around it. The Radar has a high [[Electric network|power]] demand (300kW) so a radar indirectly contributes to [[Pollution]] when powered by [[Boiler]]s and [[Steam engine|steam engines]]. The radar will be attacked by enemies that come within very close range, like turrets, due to its status as a military building, but will not attract biters from long range like polluting structures do. The radar will show enemy lifeforms and structures, as well as [[trains]], [[cars]], and other [[player]]s in the scanned area.

== Nearby Pulse Scanning ==

The Radar continuously charts an area of 7x7 [[Chunk]]s (224x224 [[Tile]]s), centered on the chunk the radar occupies. This nearby area is updated as a single pulse approximately every second. At reduced power levels, this nearby pulse scan will take longer, which can lead to 'blinking' on the player's map similar to the long range scan. This is particularly noticeable at dawn and dusk on solar powered radar stations.

At 20% power the radar will pulse about every 4 seconds which will still keep the nearby area continuously lit on the map, but will provide reduced detail. 20% power can be achieved by a single [[solar panel]], or by using one isolating accumulator for every 5 radars.

== Long Range Survey Scanning ==

The Radar charts one distant [[Chunk]] every time the sector scanning progress bar fills. This will take 33.333 seconds, if the Radar is receiving full power. Mouse-over or click-open the radar details to see this progress bar. Long range scanning is visible on the map as a single chunk lighting up for several seconds, then slowly darkening.

* It scans the unexplored chunks first, represented by the black areas on the map. Note that it also generates the chunks if they weren't generated at the time of the scan.
* One chunk scan takes 10 MJ of energy to complete. Since the Radar draws 300 kW of power, it takes 10 MJ / 300 kW = 33.333 seconds to scan one chunk.
* This is done in an 29x29 chunks around the Radar, excluding the nearby 7x7 chunks.
** With a total number of 797 chunks (29x29 - 7x7), it takes one radar '''7 hours 20 minutes''' to complete one full scan cycle.
* If everything is already explored it continues to scan by re-scanning the longest-ago scanned chunk within range.
* Multiple radars will share long-range chunks, reducing the amount of time it takes to complete long-range survey scanning.
** This is a smart process, meaning that the radars will not scan chunks currently being scanned by other radars.

'''It is possible that a new alien nest will appear in a previously scanned chunk; just because you don't see it on the map, doesn't mean it is not there.

== Coverage ==

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

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

== Charting ==

If a [[chunk]] is '''scanned''' by a radar or player, the image of that chunk that is copied into the map of the players of this surface force (every force has it's own map).

This procedure is called "charting".

=== Charting Process ===

If the contents of a chunk changes between two ticks, the content of that chunk is "charted" into the map. The map is just a bitmap, a picture. See below. You can see the entities moving, you can see enemies walking. Every entity is represented by one or more pixels. Not every entity is drawn. Users can recognize what is drawn because of the color.

Charting of several chunks that change each tick might have an impact on game performance, manifesting in the form of lowered UPS or FPS.

=== Charting Decay Time / Fog of War ===

Once a scan for a chunk is triggered, it keeps actively charted for '''10 seconds'''. This effect can also be seen in the map of the chunk highlighted and dims within 10 seconds to a greyed out version of the chunk.

If charting is not repeated within the 10 seconds, the charting process stops for this chunk after 10 seconds and is not longer updated. What you see after that time is the last charted picture for that chunk (also called "fog of war").

=== Charting of Vehicles ===

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

Vehicles are shown as a circle, with an arrow pointing in the direction that they're facing.

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

The [[World_generator#Generating_new_Chunks|World Generator]] creates a "border" of invisible chunks around each chunk, that becomes active at some time. Active chunks are those that become charted or those that are active because the pollution spreads onto them.

== History ==

{{history|0.12.17|
* Updated icons.}}

{{history|0.11.11|
* Radar ignores chunks outside the map radius.}}

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

{{history|0.9.0|
* Halved radar electricity consumption.}}

{{history|0.7.3|
* Radar continues refreshing chunks after all chunks in range have been discovered.}}

{{history|0.5.1|
* New Graphics}}

{{history|Unknown, presumed 0.1.0|
* Introduced}}

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

{{CombatNav}}

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

Infobox:Personal laser defense

2017-05-09T19:37:04Z

Tincopper2:

{{Infobox
|expensive-total-raw = Time, 410 + Battery, 60 + Copper plate, 500 + Iron plate, 200 + Processing unit, 1 + Steel plate, 105
| category = Items
|stack-size=20
| category-name = Item
|speed = 5/second
|damage = 15 electric
|range = 20 tiles
|dimensions = 2x2
|energy = 200kJ
|recipe = Time, 10 + Laser turret, 5 + Processing unit, 1 + Steel plate, 5
|total-raw = Time, 235 + Battery, 60 + Copper plate, 150 + Iron plate, 100 + Processing unit, 1 + Steel plate, 105
|required-technologies =Personal laser defense (research)
|producers =Manual + Assembling machine 2 + Assembling machine 3
}}<noinclude>[[Category:Infobox page]]</noinclude>

Infobox:Personal laser defense

2017-05-03T00:09:57Z

Tincopper2: Added info (from 0.15)

{{Infobox
| category = Items
|stack-size=20
| category-name = Item
|speed = 5/second
|damage = 15 electric
|range = 20 tiles
|dimensions = 2x2
|electricity = 200kJ
|recipe =Time, 10 + Steel plate, 5 + Laser turret, 5 + Processing unit, 1
|total-raw =Time, 598 + sulfuric acid, 120.5 + iron plate, 184 + copper plate, 270 + plastic bar, 4 + Steel plate, 105
|required-technologies =Personal laser defense (research)
|producers =Manual + Assembling machine 2 + Assembling machine 3
}}<noinclude>[[Category:Infobox page]]</noinclude>

Personal laser defense

2017-05-02T23:59:29Z

Tincopper2: False information

{{Languages}}
{{:Personal laser defense/infobox}}

<onlyinclude>
The [[Personal laser defense]] is a module insertable into [[Modular armor]] that provides a basic laser defense system.

It automatically targets and fires at nearby [[Enemies]], and, unlike hand-held weapons, doesn't slow the player down when firing. It consumes power after it fires (to recharge), so it doesn't necessarily need [[Battery|batteries]].

Damage and attack speed are static and are under the electric ammo type, it does not benefit from any other upgrades.

The Personal laser defense will fire at enemies nearby even if the player is inside a [[vehicle]].
</onlyinclude>

== See also ==
* [[Modular armor]]
* [[Discharge defense]]

[[Category: Items]]
[[Category: Equipment]]

{{CombatNav}}