Official Factorio Wiki - User contributions [en]

Console

2023-11-04T15:48:00Z

Muppet9010: /* Access a mod's data */ correct mod name in text description to match example code

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

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

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

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

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

== Normal commands ==

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

== Multiplayer commands ==
{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| <message>
| Hello team!
| Console input that does not start with {{keybinding|/}} is shown as a chat message to your team.
| No
|-
| /admin
| /admin
| Opens the player management GUI.
| Yes
|-
| /admins
| /admins
| Prints a list of game admins.
| No
|-
| /ban <player> <reason>
| /ban xTROLLx Throwing grenades in base
| Bans the specified player.
| Yes
|-
| /bans
| /bans
| Prints a list of banned players.
| No
|-
| /banlist <add/remove/get/clear> <player>
| /banlist get
| Adds or removes a player from the banlist. Same as /ban or /unban.
| No
|-
| /config <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>
| 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.
|-
| /mc <command>
| Executes a Lua command (if allowed) and measures time it took.
|-
| /silent-command <command>
| Executes a Lua command (if allowed) without printing it to the console.
|-
| /sc <command>
| Executes a Lua command (if allowed) without printing it to the console.
|}

This is a very powerful feature, which also allows cheating, and as such <span style="color:#FF0000">achievements will be permanently disabled for the save</span> as soon as you use a script command.

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

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

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

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

There are several god-mode items available:

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

=== Where speakers are, who placed them ===
<syntaxhighlight lang="lua">
/c local speakers = game.player.surface.find_entities_filtered{force = game.player.force, type="programmable-speaker"}
for key, speaker in pairs(speakers) do
game.player.print(speaker.last_user.name .. " placed a speaker at [gps=" .. speaker.position.x .. "," .. 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>

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

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

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

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

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

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

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

=== 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 [[Prototype/LinkedBelt|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"].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 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>

== 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 character and destroy it:
<syntaxhighlight lang="lua">
/c game.player.character.destroy()
</syntaxhighlight>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

{{C|Technical}}

Types/RotatedAnimation

2022-12-26T23:27:48Z

Muppet9010: /* line_length */ clarify what the field is actually setting and re-organise existing description to be far more readable.

== Mandatory properties ==

=== direction_count ===
'''Type''': [[Types/uint32]]

The sequential animation instance is loaded equal to the entities direction within the direction_count setting.

Direction count to [[Types/Direction]] (animation sequence number):
*'''1''' - '''North''' (1)
*'''2''' - '''North''' (1), South (2)
*'''4''' - '''North''' (1), '''East''' (2), '''South''' (3), '''West''' (4)
*'''8''' - '''North''' (1), '''Northeast''' (2), '''East''' (3), '''Southeast''' (4), '''South''' (5), '''Southwest''' (6), '''West''' (7), '''Northwest''' (8)

== Optional properties ==

=== layers ===
'''Type''': [[Types/table]] of [[Types/RotatedAnimation]]

If this property is present, all RotatedAnimation definitions have to be placed as entries in the array, and they will all be loaded from there. Each item (RotatedAnimation definition) in the array may also have the <code>layers</code> property.

If this property is present, all other properties are ignored and the mandatory properties do not have to be defined.

Layers may not be an empty table.

=== hr_version ===
'''Type''': [[Types/RotatedAnimation]]

If this property exists and high resolution sprites are turned on, its contents are used to load the RotatedAnimation.

=== filename ===
'''Type''': [[Types/FileName]]

'''Default''': ""

Mandatory if <code>stripes</code> and <code>filenames</code> is not specified.

=== filenames ===
'''Type''': [[types/table]] of [[Types/FileName]]

'''Default''': ""

Only loaded if <code>stripes</code> is not present.

=== slice ===
'''Type''': [[Types/uint32]]

Mandatory if <code>filenames</code> is present.

=== lines_per_file ===
'''Type''': [[Types/uint32]]

Mandatory if <code>filenames</code> is present.

=== priority ===
'''Type''': [[Types/SpritePriority]]

'''Default''': "medium"

=== flags ===
'''Type''': [[Types/SpriteFlags]]

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

The width and height of the one frame. If this is an array, the first member of the array is the width and the second is the height. Otherwise the size is both width and height.

Width and height may only be in the range of 0-8192.

=== width ===
'''Type''': [[Types/SpriteSizeType]]

Mandatory if <code>size</code> is not given. Width of one frame in pixels, from 0-8192.

=== height ===
'''Type''': [[Types/SpriteSizeType]]

Mandatory if <code>size</code> is not given. Height of one frame in pixels, from 0-8192.

=== x ===
'''Type''': [[Types/SpriteSizeType]]

'''Default''': 0

Horizontal position of the animation in the source file in pixels.

=== y ===
'''Type''': [[Types/SpriteSizeType]]

'''Default''': 0

Vertical position of the animation in the source file in pixels.

=== position ===
'''Type''': [[Types/table]] of [[Types/SpriteSizeType]]

Loaded only when <code>x</code> and <code>y</code> are both 0. The first member of the array is x and the second is y.

=== shift ===
'''Type''': [[Types/vector]]

'''Default''': {0, 0}

=== scale ===
'''Type''': [[Types/double]]

'''Default''': 1

Values different than 1 specify the scale of the animation on default zoom.
Scale 2 means that the picture will be 2 times bigger on screen (and more pixelated).

=== draw_as_shadow ===
'''Type''': [[Types/bool]]

'''Default''': false

Only one of <code>draw_as_shadow</code>, <code>draw_as_glow</code> and <code>draw_as_light</code> can be true. <code>draw_as_shadow</code> takes precedence over <code>draw_as_glow</code> and <code>draw_as_light</code>.

=== draw_as_glow ===
'''Type''': [[Types/bool]]

'''Default''': false

Only one of <code>draw_as_shadow</code>, <code>draw_as_glow</code> and <code>draw_as_light</code> can be true. <code>draw_as_glow</code> takes precedence over <code>draw_as_light</code>.

Draws first as a normal sprite, and again as a light layer.<sup>[https://forums.factorio.com/91682]</sup>

=== draw_as_light ===
'''Type''': [[Types/bool]]

'''Default''': false

Only one of <code>draw_as_shadow</code>, <code>draw_as_glow</code> and <code>draw_as_light</code> can be true.

=== mipmap_count ===
'''Type''': [[Types/uint8]]

'''Default''': 0

Only loaded if this is an icon (has flag "group=icon" or "group=gui").

=== apply_runtime_tint ===
'''Type''': [[Types/bool]]

'''Default''': false

=== tint ===
'''Type''': [[Types/Color]]

'''Default''': {r=1, g=1, b=1, a=1} (white)

=== blend_mode ===
'''Type''': [[Types/BlendMode]]

'''Default''': "normal"''

=== load_in_minimal_mode ===
'''Type''': [[Types/bool]]

'''Default''': false

Minimal mode is entered when mod loading fails. You are in it when you see the gray box after (part of) the loading screen that tells you a mod error ([https://cdn.discordapp.com/attachments/340530709712076801/532315796626472972/unknown.png Example]). If you are a modder, you can just ignore this property.

=== premul_alpha ===
'''Type''': [[Types/bool]]

'''Default''': true

Whether alpha should be premultiplied.

=== generate_sdf ===
'''Type''': [[Types/bool]]

'''Default''': false

Unused.

=== run_mode ===
'''Type''': [[Types/string]]

'''Default''': "forward"

Possible values are:
*forward
*backward
*forward-then-backward

=== frame_count ===
'''Type''': [[Types/uint32]]

'''Default''': 1

Can't be 0.

=== line_length ===
'''Type''': [[Types/uint32]]

'''Default''': 0

Specifies how many pictures are on each horizontal line in the image file. 0 means that all the pictures are in one horizontal line.
Once the specified number of pictures are loaded from a line, the pictures from the next line are loaded.
This is to allow having longer animations loaded in to Factorio's graphics matrix than the game engine's width limit of 8192px per input file. The restriction on input files is to be compatible with most graphics cards.

=== animation_speed ===
'''Type''': [[Types/float]]

'''Default''': 1

Modifier of the animation playing speed, the default is 1, which means one animation frame per tick (60 fps).
The speed of playing can often vary depending on the usage (output of steam engine for example). Has to be greater than 0.

=== max_advance ===
'''Type''': [[Types/float]]

'''Default''': MAX_FLOAT

=== repeat_count ===
'''Type''': [[Types/uint8]]

'''Default''': 1

How many times to repeat the animation to complete an animation cycle. E.g. if one layer is 10 frames, a second layer of 1 frame would need repeat_count = 10 to match the complete cycle.

Can't be 0.

=== dice ===
'''Type''': [[Types/uint8]]

=== dice_x ===
'''Type''': [[Types/uint8]]

=== dice_y ===
'''Type''': [[Types/uint8]]

=== frame_sequence ===
'''Type''': [[Types/AnimationFrameSequence]]

=== still_frame ===
'''Type''': [[Types/uint32]]

'''Default''': 0

=== axially_symmetrical ===
'''Type''': [[Types/bool]]

'''Default''': false

If true, <code>direction_count</code> must be greater than 1.

=== counterclockwise ===
'''Type''': [[Types/bool]]

'''Default''': false

=== middle_orientation ===
'''Type''': [[Types/RealOrientation]]

'''Default''': 0.5

=== orientation_range ===
'''Type''': [[Types/float]]

'''Default''': 1

Automatically clamped to be between 0 and 1.

=== apply_projection ===
'''Type''': [[Types/bool]]

'''Default''': true

=== stripes ===
'''Type''': [[Types/table|table]] (array) of [[Types/Stripe|Stripe]]

{{Prototype property type usage|{{FULLPAGENAME}}}}

Types/PushBackTriggerEffectItem

2022-12-08T20:02:02Z

Muppet9010: Add functional description of effect.

The push back effect used by the [[discharge defense]].

Aims to push the target entity away from the source entity by the <code>distance</code> from the target entity's current position. Searches within double the <code>distance</code> from the pushed to position for the nearest non-colliding position for the target entity to be teleported too. If no valid non-colliding position is found or the target is not teleportable then no push back occurs.

Extends [[Types/TriggerEffectItem]].

== Mandatory properties ==
Inherits all properties from [[Types/TriggerEffectItem]].

=== distance ===
'''Type''': [[Types/float]]

Types/TriggerDelivery

2022-12-06T20:23:17Z

Muppet9010: /* source_effects */ Clarified that the target of the TriggerDelivery isn't accessible when used via source_effects. i.e. can't use a push-back as a source_effects of an attack as it receives the source as both ends of the push.

A [[types/table]]s. The table is loaded as one of the [[#Extensions]], depending on the value of the <code>type</code> key in the table.

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

Mandatory property. Either "instant", "projectile", "flame-thrower", "beam", "stream", or "artillery".
* If this is <code>"instant"</code>, that definition is loaded as a [[Types/InstantTriggerDelivery]],
* If this is <code>"projectile"</code>, that definition is loaded as a [[Types/ProjectileTriggerDelivery]],
* If this is <code>"flame-thrower"</code>, that definition is loaded as a [[Types/FlameThrowerExplosionTriggerDelivery]],
* If this is <code>"beam"</code>, that definition is loaded as a [[Types/BeamTriggerDelivery]],
* If this is <code>"stream"</code>, that definition is loaded as a [[Types/StreamTriggerDelivery]],
* If this is <code>"artillery"</code>, that definition is loaded as a [[Types/ArtilleryTriggerDelivery]].

== Extensions ==
* [[Types/InstantTriggerDelivery]]
* [[Types/ProjectileTriggerDelivery]]
* [[Types/FlameThrowerExplosionTriggerDelivery]]
* [[Types/BeamTriggerDelivery]]
* [[Types/StreamTriggerDelivery]]
* [[Types/ArtilleryTriggerDelivery]]

== Optional properties ==
=== source_effects ===
'''Type''': [[Types/TriggerEffect]]

Provides the source of the TriggerDelivery as as both the source and target to the [[Types/TriggerEffect]].

=== target_effects ===
'''Type''': [[Types/TriggerEffect]]

Types/DamageTriggerEffectItem

2022-08-28T23:17:19Z

Muppet9010: /* vaporize */

__NOTOC__Extends [[Types/TriggerEffectItem]].

== Mandatory properties ==
Inherits all properties from [[Types/TriggerEffectItem]].

=== damage ===
'''Type''': [[Types/DamagePrototype|DamagePrototype]]

== Optional properties ==

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

'''Default''': true

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

'''Default''': false

If <code>true</code> no corpse for killed entities will be created.

=== lower_distance_threshold ===
'''Type''': [[Types/uint16|uint16]]

'''Default''': max uint16

=== upper_distance_threshold ===
'''Type''': [[Types/uint16|uint16]]

'''Default''': max uint16

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

'''Default''': 1

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

'''Default''': 1

Types/AmmoType

2022-07-29T14:11:11Z

Muppet9010: /* range_modifier */ clarify that this affects the max range and not the min range.

==Basics==
Definition of actual parameters used in attack.

== Mandatory properties ==

=== category ===
'''Type''': [[Types/string]]

Name of a [[Prototype/AmmoCategory]]. Defines whether the attack will be affected by upgrades.

== Optional properties ==

=== action ===
'''Type''': [[Types/Trigger]]

Describes actions taken upon attack happening.

=== clamp_position ===
'''Type''': [[Types/bool]]

'''Default''': false

When true, the gun will be able to shoot even when the target is out of range. Only applies when target_type is position. The gun will fire at the maximum range in the direction of the target position. Defaults to false.

=== energy_consumption ===
'''Type''': [[Types/Energy]]

Energy consumption of a single shot, if applicable.

=== range_modifier ===
'''Type''': [[Types/double]]

'''Default''': 1

Affects the <code>range</code> value of the shooting gun prototype's <code>BaseAttackParameters</code> to give a modified maximum range. The <code>min_range</code> value of the gun is unaffected.

=== cooldown_modifier ===
'''Type''': [[Types/double]]

'''Default''': 1

=== consumption_modifier ===
'''Type''': [[Types/float]]

'''Default''': 1

=== target_type ===
'''Type''': [[Types/string]]

'''Default''': "entity"

Either "entity", "position" or "direction". If this is "entity", <code>clamp_position</code> is forced to be false.
"entity" fires at an entity, "position" fires directly at a position, "direction" fires in a direction.

Types/BaseAttackParameters

2022-07-29T13:11:13Z

Muppet9010: /* ammo_category */ description had a a typo saying this setting was mandatory if this setting was not given, rather than this setting was mandatory if the list version of the setting wasn't given.

The abstract base of all [[Types/AttackParameters|attack parameters]].

== Extensions ==
* [[Types/ProjectileAttackParameters]]
* [[Types/BeamAttackParameters]]
* [[Types/StreamAttackParameters]]

== Mandatory properties ==
=== range ===
'''Type''': [[Types/float]]

Before an entity can attack, the distance (in tiles) between the entity and target must be less than or equal to this.

=== cooldown ===
'''Type''': [[Types/float]]

Number of ticks in which it will be possible to shoot again. If < 1, multiple shots can be performed in one tick.

== Optional properties ==
=== min_range ===
'''Type''': [[Types/float]]

'''Default''': 0

The minimum distance (in tiles) between an entity and target. If a unit's target is less than this, the unit will attempt to move away before attacking. A [[Flamethrower turret]] does not move, but has a minimum range. Less than this, it is unable to target an enemy.

=== turn_range ===
'''Type''': [[Types/float]]

'''Default''': 1

If this is <= 0, it is set to 1. Arc from 0 to 1, so for example 0.25 is 90°. Used by the [[flamethrower turret]] in the base game. Arcs greater than 0.5 but less than 1 will be clamped to 0.5 as targeting in arcs larger than half circle is not implemented.[https://forums.factorio.com/94654]

=== fire_penalty ===
'''Type''': [[Types/float]]

'''Default''': 0

Used when searching for the nearest enemy, when this is > 0, enemies that aren't burning are preferred over burning enemies. Definition of "burning" for this: Entity has sticker attached to it, and the sticker has a [[Prototype/Sticker#spread_fire_entity|spread_fire_entity]] set.

=== rotate_penalty ===
'''Type''': [[Types/float]]

'''Default''': 0

A higher penalty will discourage turrets from targeting units that would take longer to turn to face.

=== health_penalty ===
'''Type''': [[Types/float]]

'''Default''': 0

A higher penalty will discourage turrets from targeting units with higher health. A negative penalty will encourage turrets to target units with higher health.

=== range_mode ===
'''Type''': [[Types/string]]

'''Default''': "center-to-center"

Either "center-to-center" or "bounding-box-to-bounding-box".

=== min_attack_distance ===
'''Type''': [[Types/float]]

'''Default''': <code>range</code>

If less than <code>range</code>, the entity will choose a random distance between <code>range</code> and <code>min_attack_distance</code> and attack from that distance.

=== damage_modifier ===
'''Type''': [[Types/float]]

'''Default''': 1

=== ammo_consumption_modifier ===
'''Type''': [[Types/float]]

'''Default''': 1

Must be greater than or equal to 0.

=== cooldown_deviation ===
'''Type''': [[Types/float]]

'''Default''': 0

Must be between 0 and 1.

=== warmup ===
'''Type''': [[Types/uint32]]

'''Default''': 0

Number of ticks it takes for the weapon to actually shoot after the order for shooting has been made. This also allows to "adjust" the shooting animation to the effect of shooting.

[[Types/CapsuleAction]]s cannot have attack_parameters with non-zero warmup.

=== lead_target_for_projectile_speed ===
'''Type''': [[Types/float]]

'''Default''': 0

Base game uses
<syntaxhighlight lang="lua">lead_target_for_projectile_speed = 0.2* 0.75 * 1.5, -- this is same as particle horizontal speed of flamethrower fire stream</syntaxhighlight>
Presumably this should be set to the projectile speed to make the unit/turret lead their projectiles.

=== movement_slow_down_cooldown ===
'''Type''': [[Types/float]]

'''Default''': <code>cooldown</code>

=== movement_slow_down_factor ===
'''Type''': [[Types/double]]

'''Default''': 1

=== ammo_type ===
'''Type''': [[Types/AmmoType]]

Can be mandatory.

=== activation_type ===
'''Type''': [[Types/string]]

'''Default''': "shoot"

One of "shoot", "throw", "consume" or "activate". Used in tooltips to set the tooltip category. It is also used to get the locale keys for activation instructions and speed of the action for the tooltip.

For example, an activation_type of "throw" will result in the tooltip category "thrown" and the tooltip locale keys "gui.instruction-to-throw" and "description.throwing-speed".

=== sound ===
'''Type''': [[Types/LayeredSound]]

Played once at the start of the attack if this is a [[Types/ProjectileAttackParameters]].

=== animation ===
'''Type''': [[Types/RotatedAnimation]]

=== cyclic_sound ===
'''Type''': [[Types/CyclicSound]]

Played during the attack.

=== use_shooter_direction ===
'''Type''': [[Types/bool]]

'''Default''': false

=== ammo_categories ===
'''Type''': [[Types/table]] (array) [[Types/string]]

Names of [[Prototype/AmmoCategory|Prototype/AmmoCategories]].

=== ammo_category ===
'''Type''': [[Types/string]]

The name of a [[Prototype/AmmoCategory]]. Mandatory if <code>ammo_type</code> and <code>ammo_categories</code> is not given, otherwise ignored.

Prototype/Entity

2021-12-17T13:05:15Z

Muppet9010:

{{Prototype parent|PrototypeBase}}
Abstract base of all entities in the game.
Entity is basically everything that can be on the map (except tiles).
For in game script access to entity, take a look at [http://lua-api.factorio.com/latest/LuaEntity.html LuaEntity]

{{Prototype TOC|''abstract''}}

== Extensions ==
<div class="factorio-list">
* [[Prototype/Arrow]] '''arrow'''
* [[Prototype/ArtilleryFlare]] '''artillery-flare'''
* [[Prototype/ArtilleryProjectile]] '''artillery-projectile'''
* [[Prototype/Beam]] '''beam'''
* [[Prototype/CharacterCorpse]] '''character-corpse'''
* [[Prototype/Cliff]] '''cliff'''
* [[Prototype/Corpse]] '''corpse'''
** [[Prototype/RailRemnants]] '''rail-remnants'''
* [[Prototype/DeconstructibleTileProxy]] '''deconstructible-tile-proxy'''
* [[Prototype/EntityGhost]] '''entity-ghost'''
* [[Prototype/EntityParticle]] '''particle''' (for migration, cannot be used)
** [[Prototype/LeafParticle]] '''leaf-particle''' (for migration, cannot be used)
* [[Prototype/EntityWithHealth]] <abstract>
** [[Prototype/Accumulator]] '''accumulator'''
** [[Prototype/ArtilleryTurret]] '''artillery-turret'''
** [[Prototype/Beacon]] '''beacon'''
** [[Prototype/Boiler]] '''boiler'''
** [[Prototype/BurnerGenerator]] '''burner-generator'''
** [[Prototype/Character]] '''character'''
** [[Prototype/Combinator]] <abstract>
*** [[Prototype/ArithmeticCombinator]] '''arithmetic-combinator'''
*** [[Prototype/DeciderCombinator]] '''decider-combinator'''
** [[Prototype/ConstantCombinator]] '''constant-combinator'''
** [[Prototype/Container]] '''container'''
*** [[Prototype/LogisticContainer]] '''logistic-container'''
**** [[Prototype/InfinityContainer]] '''infinity-container'''
** [[Prototype/CraftingMachine]] <abstract>
*** [[Prototype/AssemblingMachine]] '''assembling-machine'''
**** [[Prototype/RocketSilo]] '''rocket-silo'''
*** [[Prototype/Furnace]] '''furnace'''
** [[Prototype/ElectricEnergyInterface]] '''electric-energy-interface'''
** [[Prototype/ElectricPole]] '''electric-pole'''
** [[Prototype/EnemySpawner]] '''unit-spawner'''
** [[Prototype/Fish]] '''fish'''
** [[Prototype/FlyingRobot]] <abstract>
*** [[Prototype/CombatRobot]] '''combat-robot'''
*** [[Prototype/RobotWithLogisticInterface]] <abstract>
**** [[Prototype/ConstructionRobot]] '''construction-robot'''
**** [[Prototype/LogisticRobot]] '''logistic-robot'''
** [[Prototype/Gate]] '''gate'''
** [[Prototype/Generator]] '''generator'''
** [[Prototype/HeatInterface]] '''heat-interface'''
** [[Prototype/HeatPipe]] '''heat-pipe'''
** [[Prototype/Inserter]] '''inserter'''
** [[Prototype/Lab]] '''lab'''
** [[Prototype/Lamp]] '''lamp'''
** [[Prototype/LandMine]] '''land-mine'''
** [[Prototype/LinkedContainer]] '''linked-container'''
** [[Prototype/Market]] '''market'''
** [[Prototype/MiningDrill]] '''mining-drill'''
** [[Prototype/OffshorePump]] '''offshore-pump'''
** [[Prototype/Pipe]] '''pipe'''
*** [[Prototype/InfinityPipe]] '''infinity-pipe'''
** [[Prototype/PipeToGround]] '''pipe-to-ground'''
** [[Prototype/PlayerPort]] '''player-port'''
** [[Prototype/PowerSwitch]] '''power-switch'''
** [[Prototype/ProgrammableSpeaker]] '''programmable-speaker'''
** [[Prototype/Pump]] '''pump'''
** [[Prototype/Radar]] '''radar'''
** [[Prototype/Rail]] <abstract>
*** [[Prototype/CurvedRail]] '''curved-rail'''
*** [[Prototype/StraightRail]] '''straight-rail'''
** [[Prototype/RailSignalBase]] <abstract>
*** [[Prototype/RailChainSignal]] '''rail-chain-signal'''
*** [[Prototype/RailSignal]] '''rail-signal'''
** [[Prototype/Reactor]] '''reactor'''
** [[Prototype/Roboport]] '''roboport'''
** [[Prototype/SimpleEntity]] '''simple-entity'''
** [[Prototype/SimpleEntityWithOwner]] '''simple-entity-with-owner'''
** [[Prototype/SimpleEntityWithForce]] '''simple-entity-with-force'''
** [[Prototype/SolarPanel]] '''solar-panel'''
** [[Prototype/SpiderLeg]] '''spider-leg'''
** [[Prototype/StorageTank]] '''storage-tank'''
** [[Prototype/TrainStop]] '''train-stop'''
** [[Prototype/TransportBeltConnectable]] <abstract>
*** [[Prototype/LinkedBelt]] '''linked-belt'''
*** [[Prototype/Loader1x1]] '''loader-1x1'''
*** [[Prototype/Loader1x2]] '''loader'''
*** [[Prototype/Splitter]] '''splitter'''
*** [[Prototype/TransportBelt]] '''transport-belt'''
*** [[Prototype/UndergroundBelt]] '''underground-belt'''
** [[Prototype/Tree]] '''tree'''
** [[Prototype/Turret]] '''turret'''
*** [[Prototype/AmmoTurret]] '''ammo-turret'''
*** [[Prototype/ElectricTurret]] '''electric-turret'''
*** [[Prototype/FluidTurret]] '''fluid-turret'''
** [[Prototype/Unit]] '''unit'''
** [[Prototype/Vehicle]] <abstract>
*** [[Prototype/Car]] '''car'''
*** [[Prototype/RollingStock]] <abstract>
**** [[Prototype/ArtilleryWagon]] '''artillery-wagon'''
**** [[Prototype/CargoWagon]] '''cargo-wagon'''
**** [[Prototype/FluidWagon]] '''fluid-wagon'''
**** [[Prototype/Locomotive]] '''locomotive'''
*** [[Prototype/SpiderVehicle]] '''spider-vehicle'''
** [[Prototype/Wall]] '''wall'''
* [[Prototype/Explosion]] '''explosion'''
** [[Prototype/FlameThrowerExplosion]] '''flame-thrower-explosion'''
* [[Prototype/FireFlame]] '''fire'''
* [[Prototype/FluidStream]] '''stream'''
* [[Prototype/FlyingText]] '''flying-text'''
* [[Prototype/HighlightBoxEntity]] '''highlight-box'''
* [[Prototype/ItemEntity]] '''item-entity'''
* [[Prototype/ItemRequestProxy]] '''item-request-proxy'''
* [[Prototype/ParticleSource]] '''particle-source'''
* [[Prototype/Projectile]] '''projectile'''
* [[Prototype/ResourceEntity]] '''resource'''
* [[Prototype/RocketSiloRocket]] '''rocket-silo-rocket'''
* [[Prototype/RocketSiloRocketShadow]] '''rocket-silo-rocket-shadow'''
* [[Prototype/Smoke]] <abstract>
** [[Prototype/SimpleSmoke]] '''smoke''' (for migration, cannot be used)
** [[Prototype/SmokeWithTrigger]] '''smoke-with-trigger'''
* [[Prototype/SpeechBubble]] '''speech-bubble'''
* [[Prototype/Sticker]] '''sticker'''
* [[Prototype/TileGhost]] '''tile-ghost'''
</div>

== Mandatory properties ==
Inherits all properties from [[PrototypeBase]].

{{Prototype property|icons, icon, icon_size (IconSpecification)|[[Types/IconSpecification|IconSpecification]]}}
An icon is mandatory for entities that have at least one of these flags active: placeable-neutral, placeable-player, placeable-enemy.

The icon will be used in the editor building selection and the bonus gui.
<syntaxhighlight lang="lua">icon = "__base__/graphics/icons/wooden-chest.png"</syntaxhighlight>

== Optional properties ==

=== order ===
:''See [[PrototypeBase#order]]''
Inherited from [[PrototypeBase]].

The order string is taken from the items in <code>placeable_by</code> if they exist, or from an item that has its [[Prototype/Item#place_result|place_result]] set to this entity if it exists.

{{Prototype property|collision_box|[[Types/BoundingBox|BoundingBox]]|Empty=<nowiki>{{0, 0}, {0, 0}} means no collisions.</nowiki>|optional=true}}
Specification of the entity collision boundaries.

Empty collision box is used for smoke, projectiles, particles, explosions etc.
<syntaxhighlight lang="lua">collision_box = {{-0.4, -0.4}, {0.4, 0.4}}</syntaxhighlight>
The {0,0} coordinate in the collision box will match the entity position.

It should be near the center of the collision box, to keep correct entity drawing order. It must include the {0,0} coordinate.

Note, that for buildings, it is customary to leave 0.1 wide border between the edge of the tile and the edge of the building, this lets the player move between the building and electric poles/inserters etc.

{{Prototype property|collision_mask|[[Types/CollisionMask|CollisionMask]]|<nowiki>{"item-layer", "object-layer", "player-layer", "water-tile"}</nowiki>|optional=true}}

Two entities can collide only if they share a layer from the collision mask.

<div class="toccolours mw-collapsible mw-collapsed">
NOTE: '''Some entity types have their own default''' that differs from the above default. They are listed here:
<div class="mw-collapsible-content">
* [[Prototype/Arrow]] - no masks
* [[Prototype/ArtilleryFlare]] - no masks
* [[Prototype/ArtilleryProjectile]] - no masks
* [[Prototype/Beam]] - no masks
* [[Prototype/Car]] - <code>{"player-layer", "train-layer", "consider-tile-transitions"}</code>
* [[Prototype/Character]] - <code>{"player-layer", "train-layer", "consider-tile-transitions"}</code>
* [[Prototype/CharacterCorpse]] - no masks
* [[Prototype/Cliff]] - <code>{ "item-layer", "object-layer", "player-layer", "water-tile", "not-colliding-with-itself"}</code>
* [[Prototype/Corpse]] - no masks
* [[Prototype/DeconstructibleTileProxy]] - <code>{"ground-tile"}</code>
* [[Prototype/EntityGhost]] - <code>{"ghost-layer"}</code>
* [[Prototype/EntityParticle]] - no masks
* [[Prototype/Explosion]] - no masks
* [[Prototype/FireFlame]] - no masks
* [[Prototype/Fish]] - <code>{"ground-tile", "colliding-with-tiles-only"}</code>
* [[Prototype/FluidStream]] - no masks
* [[Prototype/FlyingRobot]] - no masks
* [[Prototype/FlyingText]] - no masks
* [[Prototype/Gate]] - <code>{"item-layer", "object-layer", "player-layer", "water-tile", "train-layer"}</code>
* [[Prototype/HeatPipe]] - <code>{"object-layer", "floor-layer", "water-tile"}</code>
* [[Prototype/HighlightBoxEntity]] - no masks
* [[Prototype/ItemEntity]] - <code>{"item-layer"}</code>
* [[Prototype/ItemRequestProxy]] - no masks
* [[Prototype/LandMine]] - <code>{"object-layer", "water-tile"}</code>
* [[Prototype/LinkedBelt]] - <code>{"object-layer", "item-layer", "transport-belt-layer", "water-tile"}</code>
* [[Prototype/Loader1x1]] - <code>{"object-layer", "item-layer", "transport-belt-layer", "water-tile"}</code>
* [[Prototype/Loader1x2]] - <code>{"object-layer", "item-layer", "transport-belt-layer", "water-tile"}</code>
* [[Prototype/ParticleSource]] - no masks
* [[Prototype/PlayerPort]] - <code>{"object-layer", "floor-layer", "water-tile"}</code>
* [[Prototype/Projectile]] - no masks
* [[Prototype/Rail]] - <code>{"item-layer", "object-layer", "rail-layer", "floor-layer", "water-tile"}</code>
* [[Prototype/RailSignalBase]] - <code>{"floor-layer", "rail-layer", "item-layer"}</code>
* [[Prototype/ResourceEntity]] - <code>{"resource-layer"}</code>
* [[Prototype/RollingStock]] - <code>{"train-layer"}</code>
* [[Prototype/Smoke]] - no masks
* [[Prototype/SpeechBubble]] - no masks
* [[Prototype/SpiderLeg]] - <code>{"player-layer", "rail-layer"}</code>
* [[Prototype/Splitter]] - <code>{"object-layer", "item-layer", "transport-belt-layer", "water-tile"}</code>
* [[Prototype/Sticker]] - no masks
* [[Prototype/TileGhost]] - <code>{"ghost-layer"}</code>
* [[Prototype/TransportBelt]] - <code>{"object-layer", "floor-layer", "transport-belt-layer", "water-tile"}</code>
* [[Prototype/UndergroundBelt]] - <code>{"object-layer", "item-layer", "transport-belt-layer", "water-tile"}</code>
* [[Prototype/Unit]] - <code>{"player-layer", "train-layer", "not-colliding-with-itself"}</code>
* [[Prototype/Vehicle]] - <code>{"player-layer", "train-layer"}</code>
</div></div>

{{Prototype property|map_generator_bounding_box|[[Types/BoundingBox|BoundingBox]]|The value of collision box.|optional=true}}
Used instead of the collision box during map generation. Allows space entities differently during map generation, for example if the box is bigger, the entities will be placed farther apart.

{{Prototype property|selection_box|[[Types/BoundingBox|BoundingBox]]|<nowiki>Empty = {{0, 0}, {0, 0}}</nowiki>|optional=true}}
Specification of the entity selection area.
When empty the entity will have no selection area (and thus is not selectable).
<syntaxhighlight lang="lua">selection_box = {{-0.5, -0.5}, {0.5, 0.5}}</syntaxhighlight>
The selection box is usually a little bit bigger than the collision box, for tilable entities (like buildings) it should match the tile size of the building.

{{Prototype property|drawing_box|[[Types/BoundingBox|BoundingBox]]|<nowiki>Empty = {{0, 0}, {0, 0}} (selection_box is used instead)</nowiki>|optional=true}}
Specification of space needed to see the whole entity.

This is used to calculate the correct zoom and positioning in the entity info gui.
<syntaxhighlight lang="lua">drawing_box = {{-0.5, -0.5}, {0.5, 0.5}}</syntaxhighlight>

{{Prototype property|sticker_box|[[Types/BoundingBox|BoundingBox]]|The value of collision box.|optional=true}}
Used to set the area of the entity that can have stickers on it, currently only used for units to specify the area where the green slow down stickers can appear.
It is optional and the collision box is used when not specified.
<syntaxhighlight lang="lua">sticker_box = {{-0.5, -0.5}, {0.5, 0.5}}</syntaxhighlight>

{{Prototype property|hit_visualization_box|[[Types/BoundingBox|BoundingBox]]|<nowiki>Empty = {{0, 0}, {0, 0}}</nowiki>|optional=true}}
Where beams should hit the entity. Useful if the bounding box only covers part of the entity (e.g. feet of the character) and beams only hitting there would look weird.

{{Prototype property|trigger_target_mask|[[Types/TriggerTargetMask|TriggerTargetMask]]|optional=true}}

{{Prototype property|flags|[[Types/EntityPrototypeFlags|EntityPrototypeFlags]]|optional=true}}

{{Prototype property|minable|[[Types/MinableProperties|MinableProperties]]|not minable|optional=true}}

{{Prototype property|subgroup|[[Types/string|string]]|optional=true}}
The name of the subgroup this entity should be sorted into in the map editor building selection.

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

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

{{Prototype property|selection_priority|[[Types/uint8|uint8]]|50|optional=true}}
The entity with the higher number is selectable before the entity with the lower number. When two entities have the same selection priority, the one with the highest [[Types/CollisionMask|collision mask]] (as determined by the order on that page) is selected.

{{Prototype property|remove_decoratives|[[Types/string|string]]|"automatic"|optional=true}}
Either "automatic", "true" or "false". Whether this entity should remove decoratives that collide with it when this entity is built. When set to "automatic", if the entity type is considered a building (e.g. an assembling machine or a wall) it will remove decoratives.

{{Prototype property|emissions_per_second|[[Types/double|double]]|0|optional=true}}
Amount of emissions created (positive number) or cleaned (negative number) every second by the entity.
This is passive, and it is independent concept of the emissions of machines, these are created actively depending on the power consumption.
Currently used just for trees.

<syntaxhighlight lang="lua">emissions_per_second = -0.001 -- cleaning effect of big tree</syntaxhighlight>

{{Prototype property|shooting_cursor_size|[[Types/double|double]]|optional=true}}
The cursor size used when shooting at this entity.

{{Prototype property|created_smoke|[[Types/CreateTrivialSmokeEffectItem|CreateTrivialSmokeEffectItem]]|The "smoke-building"-smoke|optional=true}}
The smoke that is shown when the entity is placed.

{{Prototype property|working_sound|[[Types/WorkingSound|WorkingSound]]|optional=true}}
Will also work on entities that don't actually do work.

{{Prototype property|created_effect|[[Types/Trigger|Trigger]]|optional=true}}
The effect/trigger that happens when the entity is placed.

{{Prototype property|build_sound|[[Types/Sound|Sound]]|optional=true}}

{{Prototype property|mined_sound|[[Types/Sound|Sound]]|optional=true}}

{{Prototype property|mining_sound|[[Types/Sound|Sound]]|optional=true}}

{{Prototype property|rotated_sound|[[Types/Sound|Sound]]|optional=true}}

{{Prototype property|vehicle_impact_sound|[[Types/Sound|Sound]]|optional=true}}
When playing this sound, the volume is scaled by the speed of the vehicle when colliding with this entity.

{{Prototype property|open_sound|[[Types/Sound|Sound]]|optional=true}}

{{Prototype property|close_sound|[[Types/Sound|Sound]]|optional=true}}

{{Prototype property|radius_visualisation_specification|[[Types/RadiusVisualisationSpecification|RadiusVisualisationSpecification]]|optional=true}}

{{Prototype property|build_base_evolution_requirement|[[Types/double|double]]|0|optional=true}}

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

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

{{Prototype property|fast_replaceable_group|[[Types/string|string]]|""|optional=true}}
This allows you to replace an entity that's already placed, with a different one in your inventory. For example, replacing a burner inserter with a fast inserter. The replacement entity can be a different rotation to the replaced entity and you can replace an entity with the same type.

This is simply a string, so any string can be used here. The entity that should be replaced simply has to use the same string here.

The ones the game uses are:

"container"
"furnace"
"transport-belt"
"electric-pole"
"steam-engine"
"inserter"
"long-handed-inserter"
"pipe" - has special directional replacement logic to prevent directional change during a replacement from pipe to underground pipe.
"assembling-machine"
"wall"
"loader"
"rail-signal"
"mining-drill"
"pumpjack"

{{Prototype property|next_upgrade|[[Types/string|string]]|optional=true}}
Name of the entity that will be automatically selected as the upgrade of this entity when using the [[upgrade planner]] without configuration.

This entity may not have 'not-upgradable' flag set and must be minable. This entity mining result must not contain item product with "hidden" flag set. Mining results with no item products are allowed. The entity may not be a [[Prototype/RollingStock]].<br>
The upgrade target entity needs to have the same bounding box, collision mask, and fast replaceable group as this entity. The upgrade target entity must have least 1 item that builds it that isn't hidden.

{{Prototype property|placeable_by|[[Types/ItemToPlace|ItemToPlace]] or [[Types/table|table]] of [[Types/ItemToPlace|ItemToPlace]]|optional=true}}
Item that when placed creates this entity. Determines which item is picked when "Q" (smart pipette) is used on the entity, determines which item is needed in a blueprint of this entity.

The item count specified here can't be larger than the stack size of that item.

{{Prototype property|remains_when_mined|[[Types/string|string]] or [[Types/table|table]] of [[Types/string|string]]|optional=true}}
The entity that remains when this one is mined, deconstructed or fast-replaced. The entity wont actually be spawned if it would collide with the entity that is in the process of being mined.

{{Prototype property|additional_pastable_entities|[[Types/table|table]] of [[Types/string|string]]|optional=true}}
Names of the entity prototypes this entity prototype can be pasted on to in addition to the standard supported types.
This is used to allow copying between types that aren't compatible on the C++ code side, by allowing mods to receive the [https://lua-api.factorio.com/latest/events.html#on_entity_settings_pasted on_entity_settings_pasted] event for the given entity and do the setting pasting via script.<br>
additional_pastable_entities = {"steel-chest", "iron-chest"}

{{Prototype property|tile_width|[[Types/uint32|uint32]]|calculated by the collision box width rounded up.|optional=true}}
Used to determine how the center of the entity should be positioned when building (unless the offgrid [[Types/EntityPrototypeFlags|flag]] is specified).
When the tile width is odd, the center will be in the center of the tile, when it is even, the center is on the tile transition.

{{Prototype property|tile_height|[[Types/uint32|uint32]]|calculated by the collision box height rounded up.|optional=true}}

{{Prototype property|autoplace|[[Types/AutoplaceSpecification|AutoplaceSpecification]]|nil (entity is not autoplacable)|optional=true}}
Used to specify the rules for placing this entity during map generation.

{{Prototype property|map_color|[[Types/Color|Color]]|optional=true}}

{{Prototype property|friendly_map_color|[[Types/Color|Color]]|optional=true}}

{{Prototype property|enemy_map_color|[[Types/Color|Color]]|optional=true}}

{{Prototype property|water_reflection|[[Types/WaterReflectionDefinition|WaterReflectionDefinition]]|optional=true}}
May also be defined inside <code>graphics_set</code> instead of directly in the entity prototype. This is useful for entities that use the a <code>graphics_set</code> property to define their graphics, because then all graphics can be defined in one place.<br>
Currently only renders for [[Prototype/EntityWithHealth]].[https://forums.factorio.com/100703]

== Example ==
<syntaxhighlight lang="lua">{
type = "container",
name = "wooden-chest",
icon = "__base__/graphics/icons/wooden-chest.png",
flags = {"placeable-neutral", "player-creation"},
minable = {mining_time = 1, result = "wooden-chest"},
max_health = 100,
corpse = "small-remnants",
collision_box = {{-0.35, -0.35}, {0.35, 0.35}},
fast_replaceable_group = "container",
selection_box = {{-0.5, -0.5}, {0.5, 0.5}},
inventory_size = 16,
open_sound = { filename = "__base__/sound/wooden-chest-open.ogg" },
close_sound = { filename = "__base__/sound/wooden-chest-close.ogg" },
vehicle_impact_sound = { filename = "__base__/sound/car-wood-impact.ogg", volume = 1.0 },
picture =
{
filename = "__base__/graphics/entity/wooden-chest/wooden-chest.png",
priority = "extra-high",
width = 46,
height = 33,
shift = {0.25, 0.015625}
},
circuit_wire_connection_point =
{
shadow =
{
red = {0.734375, 0.453125},
green = {0.609375, 0.515625},
},
wire =
{
red = {0.40625, 0.21875},
green = {0.40625, 0.375},
}
},
circuit_connector_sprites = get_circuit_connector_sprites({0.1875, 0.15625}, nil, 18),
circuit_wire_max_distance = 9
}</syntaxhighlight>

Types/RotatedAnimation

2021-12-16T23:08:42Z

Muppet9010: /* direction_count */

== Mandatory properties ==

=== direction_count ===
'''Type''': [[Types/uint32]]

The sequential animation instance is loaded equal to the entities direction within the direction_count setting. If the entity direction is outside of the configured direction_count then the North (1st) animation is shown.

Direction count to [[Types/Direction]] (animation sequence number):
*'''1''' - '''North''' (1)
*'''2''' - '''North''' (1), South (2)
*'''4''' - '''North''' (1), '''East''' (2), '''South''' (3), '''West''' (4)
*'''8''' - '''North''' (1), '''Northeast''' (2), '''East''' (3), '''Southeast''' (4), '''South''' (5), '''Southwest''' (6), '''West''' (7), '''Northwest''' (8)

== Optional properties ==

=== layers ===
'''Type''': [[Types/table]] of [[Types/RotatedAnimation]]

If this property is present, all RotatedAnimation definitions have to be placed as entries in the array, and they will all be loaded from there. Each item (RotatedAnimation definition) in the array may also have the <code>layers</code> property.

If this property is present, all other properties are ignored and the mandatory properties do not have to be defined.

Layers may not be an empty table.

=== hr_version ===
'''Type''': [[Types/RotatedAnimation]]

If this property exists and high resolution sprites are turned on, its contents are used to load the RotatedAnimation.

=== filename ===
'''Type''': [[Types/FileName]]

'''Default''': ""

Mandatory if <code>stripes</code> and <code>filenames</code> is not specified.

=== filenames ===
'''Type''': [[types/table]] of [[Types/FileName]]

'''Default''': ""

Only loaded if <code>stripes</code> is not present.

=== slice ===
'''Type''': [[Types/uint32]]

Mandatory if <code>filenames</code> is present.

=== lines_per_file ===
'''Type''': [[Types/uint32]]

Mandatory if <code>filenames</code> is present.

=== priority ===
'''Type''': [[Types/SpritePriority]]

'''Default''': "medium"

=== flags ===
'''Type''': [[Types/SpriteFlags]]

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

The width and height of the one frame. If this is an array, the first member of the array is the width and the second is the height. Otherwise the size is both width and height.

Width and height may only be in the range of 0-8192.

=== width ===
'''Type''': [[Types/SpriteSizeType]]

Mandatory if <code>size</code> is not given. Width of one frame in pixels, from 0-8192.

=== height ===
'''Type''': [[Types/SpriteSizeType]]

Mandatory if <code>size</code> is not given. Height of one frame in pixels, from 0-8192.

=== x ===
'''Type''': [[Types/SpriteSizeType]]

'''Default''': 0

Horizontal position of the animation in the source file in pixels.

=== y ===
'''Type''': [[Types/SpriteSizeType]]

'''Default''': 0

Vertical position of the animation in the source file in pixels.

=== position ===
'''Type''': [[Types/table]] of [[Types/SpriteSizeType]]

Loaded only when <code>x</code> and <code>y</code> are both 0. The first member of the array is x and the second is y.

=== shift ===
'''Type''': [[Types/vector]]

'''Default''': {0, 0}

=== scale ===
'''Type''': [[Types/double]]

'''Default''': 1

Values different than 1 specify the scale of the animation on default zoom.
Scale 2 means that the picture will be 2 times bigger on screen (and more pixelated).

=== draw_as_shadow ===
'''Type''': [[Types/bool]]

'''Default''': false

Only one of <code>draw_as_shadow</code>, <code>draw_as_glow</code> and <code>draw_as_light</code> can be true. <code>draw_as_shadow</code> takes precedence over <code>draw_as_glow</code> and <code>draw_as_light</code>.

=== draw_as_glow ===
'''Type''': [[Types/bool]]

'''Default''': false

Only one of <code>draw_as_shadow</code>, <code>draw_as_glow</code> and <code>draw_as_light</code> can be true. <code>draw_as_glow</code> takes precedence over <code>draw_as_light</code>.

Draws first as a normal sprite, and again as a light layer.<sup>[https://forums.factorio.com/91682]</sup>

=== draw_as_light ===
'''Type''': [[Types/bool]]

'''Default''': false

Only one of <code>draw_as_shadow</code>, <code>draw_as_glow</code> and <code>draw_as_light</code> can be true.

=== mipmap_count ===
'''Type''': [[Types/uint8]]

'''Default''': 0

Only loaded if this is an icon (has flag "group=icon" or "group=gui").

=== apply_runtime_tint ===
'''Type''': [[Types/bool]]

'''Default''': false

=== tint ===
'''Type''': [[Types/Color]]

'''Default''': {r=1, g=1, b=1, a=1} (white)

=== blend_mode ===
'''Type''': [[Types/BlendMode]]

'''Default''': "normal"''

=== load_in_minimal_mode ===
'''Type''': [[Types/bool]]

'''Default''': false

Minimal mode is entered when mod loading fails. You are in it when you see the gray box after (part of) the loading screen that tells you a mod error ([https://cdn.discordapp.com/attachments/340530709712076801/532315796626472972/unknown.png Example]). If you are a modder, you can just ignore this property.

=== premul_alpha ===
'''Type''': [[Types/bool]]

'''Default''': true

Whether alpha should be premultiplied.

=== generate_sdf ===
'''Type''': [[Types/bool]]

'''Default''': false

Unused.

=== run_mode ===
'''Type''': [[Types/string]]

'''Default''': "forward"

Possible values are:
*forward
*backward
*forward-then-backward

=== frame_count ===
'''Type''': [[Types/uint32]]

'''Default''': 1

Can't be 0.

=== line_length ===
'''Type''': [[Types/uint32]]

'''Default''': 0

Once the specified number of pictures is loaded, other pictures are loaded on other line.
This is to allow having longer animations in matrix, to avoid pictures with too big width.
The game engine limits the width of any input picture to 2048px, so it is compatible with most graphics cards.

=== animation_speed ===
'''Type''': [[Types/float]]

'''Default''': 1

Modifier of the animation playing speed, the default is 1, which means one animation frame per tick (60 fps).
The speed of playing can often vary depending on the usage (output of steam engine for example). Has to be greater than 0.

=== max_advance ===
'''Type''': [[Types/float]]

'''Default''': MAX_FLOAT

=== repeat_count ===
'''Type''': [[Types/uint8]]

'''Default''': 1

Can't be 0.

=== dice ===
'''Type''': [[Types/uint8]]

=== dice_x ===
'''Type''': [[Types/uint8]]

=== dice_y ===
'''Type''': [[Types/uint8]]

=== frame_sequence ===
'''Type''': [[Types/AnimationFrameSequence]]

=== still_frame ===
'''Type''': [[Types/uint32]]

'''Default''': 0

=== axially_symmetrical ===
'''Type''': [[Types/bool]]

'''Default''': false

If true, <code>direction_count</code> must be greater than 1.

=== counterclockwise ===
'''Type''': [[Types/bool]]

'''Default''': false

=== middle_orientation ===
'''Type''': [[Types/RealOrientation]]

'''Default''': 0.5

=== orientation_range ===
'''Type''': [[Types/float]]

'''Default''': 1

Automatically clamped to be between 0 and 1.

=== apply_projection ===
'''Type''': [[Types/bool]]

'''Default''': true

=== stripes ===
'''Type''': [[Types/table|table]] (array) of [[Types/Stripe|Stripe]]

{{Prototype property type usage|{{FULLPAGENAME}}}}

Locomotive

2021-06-28T14:49:03Z

Muppet9010: /* Driving controls */ clarify which key does left turn and which does right turn.

{{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, 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 (0.5 for any type of wagon including locomotives) 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 (left, right)
|{{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|Railway}}
{{C|Rolling stock}}

Types/EntityPrototypeFlags

2021-01-03T16:06:03Z

Muppet9010: /* "player-creation" */

Array ([[Types/table]]) of strings. The possible strings are listed below.

== "not-rotatable" ==
Can't be rotated before or after placing.

== "placeable-[force]" ==
*"placeable-player"
*"placeable-neutral"
*"placeable-enemy"
placeable neutral/player/enemy determine the default force when placing entities in the map editor and using the *AUTO* option for the force.

== "placeable-off-grid" ==
placeable-off-grid refers to the fact that most entities are placed on an invisible 'grid' within the world, entities with the placeable-off-grid flag do not have to line up with this grid (like trees and land-mines)

== "player-creation" ==
Makes it possible for the biter AI to target the entity as a distraction. Makes it possible to blueprint, deconstruct, and repair the entity (can be turned off again using the specific flags). Enables smoke to be created automatically when building the entity. Enables the entity to appear on the map/minimap.

== "building-direction-8-way" ==
Uses 45 degree angle increments when selecting direction.

== "filter-directions" ==
Used to automatically detect the proper direction, if possible. Used by base with the pump, train stop, and train signal.

== "fast-replaceable-no-build-while-moving" ==
Fast replace will not apply when building while moving.

== "breaths-air" ==
This is used to specify that the entity breathes air, and so is affected by poison (currently [[Poison_capsule|poison capsules]] are the only source).

== "not-repairable" ==
Used to specify that the entity can not be 'healed' by repair-packs (or construction robots with repair packs)

== "not-on-map" ==
The entity does not get drawn on the map.

== "not-blueprintable" ==
The entity can't be used in blueprints.

== "not-deconstructable" ==
The entity can't be deconstructed.

== "hidden" ==
Hides the entity from the bonus GUI (button above the map) and from the made in property of recipe tooltips.

== "hide-alt-info" ==
Hides the alt-info of an entity in alt-mode, for example the recipe icon.

== "fast-replaceable-no-cross-type-while-moving" ==
Do not fast replace over other entity types when building while moving.

== "no-gap-fill-while-building" ==

== "not-flammable" ==
Do not apply fire stickers to the entity.

== "no-automated-item-removal" ==

Prevents inserters and loaders from taking items from this entity.

== "no-automated-item-insertion" ==

Prevents inserters and loaders from inserting items into this entity.

== "no-copy-paste" ==

== "not-selectable-in-game" ==

== "not-upgradable" ==
The entity can't be selected by the [[upgrade planner]].

== "not-in-kill-statistics" ==
The entity is not shown in the kill statistics.

== Example ==
flags = {"placeable-neutral", "player-creation"}

Console

2020-09-07T16:58:23Z

Muppet9010: /* Using the console */ Expand the TAB part to be more complete.

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

=== Using the console ===
The console display can be toggled with the {{keybinding|/}} (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
|-
| /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 <span style="color:#FF0000">achievements will be permanently disabled for the save</span> as soon as you use a script command.

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Find player corpses ===
Pings player corpses on the map.
<syntaxhighlight lang="lua">
/c local found_corpses = game.player.surface.find_entities_filtered{type="character-corpse"}
for _,corpse in pairs(found_corpses) do
local 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

Prototype/SelectionTool

2020-05-03T21:46:34Z

Muppet9010: /* Mandatory properties */ selection_cursor_box_type - add default colors to values list

{{Prototype parent|Prototype/ItemWithLabel}}
Used in the base game as a base for the blueprint item and the deconstruction item.

{{Prototype TOC|selection-tool}}

== Extensions ==
* [[Prototype/BlueprintItem]] '''blueprint'''
* [[Prototype/CopyPasteTool]] '''copy-paste-tool'''
* [[Prototype/DeconstructionItem]] '''deconstruction-item'''
* [[Prototype/UpgradeItem]] '''upgrade-item'''

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

{{Prototype property|selection_color|[[Types/Color|Color]]}}
The color of the rectangle used when standard selection is done in-game.

{{Prototype property|alt_selection_color|[[Types/Color|Color]]}}
The color of the rectangle used when alt-selection is done in-game.

{{Prototype property|selection_mode|[[Types/table|table]] of [[Types/string|string]]}}
A list of selection mode flags that define how the selection tool selects things in-game.

Possible values are:
{| class="wikitable"
|-
! Flag !! meaning
|-
| blueprint || The normal rules for acceptable entities in blueprints
|-
| deconstruct || The normal rules for acceptable entities for deconstruction
|-
| cancel-deconstruct || The normal rules for acceptable entities for cancel deconstruction
|-
| items || Item entities
|-
| trees || Trees
|-
| buildable-type || Buildable entities as defined by the game
|-
| nothing || Nothing
|-
| items-to-place || The entity has an item that builds the entity
|-
| any-entity || Any entity
|-
| any-tile || Any tile
|-
| same-force || The entity force matches that of the player doing the selection
|-
| not-same-force || The entity force does not match that of the player doing the selection
|-
| friend || The entity force is friend to that of the player doing the selection
|-
| enemy || The entity force is enemy to that of the player doing the selection
|-
| upgrade || The normal rules for acceptable entities in upgrade planners
|-
| cancel-upgrade || The normal rules for acceptable entities for cancel upgrade
|-
| entity-with-health ||
|-
| entity-with-force ||
|-
| entity-with-owner ||
|}

{{Prototype property|alt_selection_mode|[[Types/table|table]] of [[Types/string|string]]}}
A list of selection mode flags that define how the selection tool alt-selects things in-game. Possible values are identical to normal selection_mode.

{{Prototype property|selection_cursor_box_type|[[Types/string|string]]}}
The type of cursor box used to render selection of entities/tiles when standard selecting.

Possible values are:
{| class="wikitable"
|-
! Flag !! meaning
|-
| entity || The normal entity selection box. Yellow by default.
|-
| electricity || The selection box used to specify electric poles an entity is connected to. Light blue by default.
|-
| copy || The selection box used when doing entity copy-paste. Green by default.
|-
| not-allowed || The selection box used when specifying colliding entities. Red by default.
|-
| pair || Light Blue by default.
|-
| logistics || Light Blue by default.
|-
| train-visualization || White by default.
|}

{{Prototype property|alt_selection_cursor_box_type|[[Types/string|string]]}}
The type of cursor box used to render selection of entities/tiles when alt selecting. Possible values are identical to normal selection_cursor_box_type.

== Optional properties ==

{{Prototype property|always_include_tiles|[[Types/bool|bool]]|false|optional=true}}
If tiles should be included in the selection regardless of entities also being in the selection. This is a visual only setting.

{{Prototype property|show_in_library|[[Types/bool|bool]]|false|optional=true}}
Whether this is shown in the blueprint library. Unused as of 0.18.13 as the ability to show any selection tools in the blueprint library was removed.

{{Prototype property|mouse_cursor|[[Types/string|string]]|"selection-tool-cursor"|optional=true}}
Name of a [[Prototype/MouseCursor]].

{{Prototype property|entity_filters|[[Types/table|table]] of [[Types/string|string]]|optional=true}}
Array of [[Prototype/Entity]] names.

{{Prototype property|alt_entity_filters|[[Types/table|table]] of [[Types/string|string]]|optional=true}}
Array of [[Prototype/Entity]] names.

{{Prototype property|entity_type_filters|[[Types/table|table]] of [[Types/string|string]]|optional=true}}

{{Prototype property|alt_entity_type_filters|[[Types/table|table]] of [[Types/string|string]]|optional=true}}

{{Prototype property|tile_filters|[[Types/table|table]] of [[Types/string|string]]|optional=true}}
Array of [[Prototype/Tile]] names.

{{Prototype property|alt_tile_filters|[[Types/table|table]] of [[Types/string|string]]|optional=true}}
Array of [[Prototype/Tile]] names.

{{Prototype property|entity_filter_mode|[[Types/string|string]]|"whitelist"|optional=true}}
One of "whitelist" and "blacklist".

{{Prototype property|alt_entity_filter_mode|[[Types/string|string]]|"whitelist"|optional=true}}
One of "whitelist" and "blacklist".

{{Prototype property|tile_filter_mode|[[Types/string|string]]|"whitelist"|optional=true}}
One of "whitelist" and "blacklist".

{{Prototype property|alt_tile_filter_mode|[[Types/string|string]]|"whitelist"|optional=true}}
One of "whitelist" and "blacklist".

Types/RenderLayer

2019-11-28T18:31:57Z

Muppet9010: add missing string convertible render layer

The render layer specifies the order of the sprite when rendering, most of the objects have it hardcoded in the source, but some are configurable.

The value is specified as [[Types/string]]

The order of acceptable values from lowest to highest:
* water-tile
* ground-tile
* tile-transition
* decals
* lower-radius-visualization
* radius-visualization
* transport-belt-integration
* resource
* building-smoke
* decorative
* ground-patch
* ground-patch-higher
* ground-patch-higher2
* remnants
* floor
* transport-belt
* transport-belt-endings
* corpse
* floor-mechanics
* item
* lower-object
* transport-belt-circuit-connector
* lower-object-above-shadow
* object
* higher-object-under
* higher-object-above
* item-in-inserter-hand
* wires
* wires-above
* entity-info-icon
* entity-info-icon-above
* explosion
* projectile
* smoke
* air-object
* air-entity-info-icon
* light-effect
* selection-box
* higher-selection-box
* collision-selection-box
* arrow
* cursor

{{Prototype property type usage|{{FULLPAGENAME}}}}

Prototype/Projectile

2019-11-23T16:06:32Z

Muppet9010: /* Optional properties */ add a note to hit_at_collision_position to elaborate on its effect

{{Prototype parent|Prototype/Entity}}
Entity with limited lifetime that can hit other entities and has triggers when this happens.

{{Prototype TOC|projectile}}

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

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

{{Prototype property|acceleration|[[Types/double|double]]}}

== Optional properties ==

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

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

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

{{Prototype property|hit_at_collision_position|[[Types/bool|bool]]|false|optional=true}}
When true the entity is hit at the position on its collision box the projectile first collides with. When false the entity is hit at its own position.

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

{{Prototype property|piercing_damage|[[Types/float|float]]|0|optional=true}}
Whenever an entity is hit by the projectile, this number gets reduced by the health of the entity. If the number is then below 0, the <code>final_action</code> is applied and the projectile destroyed. Otherwise, the projectile simply continues to its destination.

{{Prototype property|max_speed|[[Types/double|double]]|MAX_DOUBLE|optional=true}}
Must be greater than or equal to 0.

{{Prototype property|height|[[Types/double|double]]|1|optional=true}}

{{Prototype property|action|[[Types/Trigger|Trigger]]|optional=true}}
Executed when the projectile hits something.

{{Prototype property|final_action|[[Types/Trigger|Trigger]]|optional=true}}
Executed when the projectile hits something, after <code>action</code> and only if the entity that was hit was destroyed. The projectile is destroyed right after the final_action.

{{Prototype property|light|[[Types/LightDefinition|LightDefinition]]|optional=true}}

{{Prototype property|smoke|Array of [[Types/SmokeSource|SmokeSource]]|optional=true}}

{{Prototype property|hit_collision_mask|[[Types/CollisionMask|CollisionMask]]|<nowiki>{"player-layer", "train-layer"}</nowiki>|optional=true}}

{{Prototype property|shadow|[[Types/Animation|Animation]]|optional=true}}

Prototype/RollingStock

2019-11-04T22:13:22Z

Muppet9010: /* Mandatory properties */ add missing line after last change

{{Prototype parent|Prototype/Vehicle}}
The abstract base of all rolling stock.

{{Prototype TOC|''abstract''}}

== Extensions ==
* [[Prototype/ArtilleryWagon]] '''artillery-wagon'''
* [[Prototype/CargoWagon]] '''cargo-wagon'''
* [[Prototype/FluidWagon]] '''fluid-wagon'''
* [[Prototype/Locomotive]] '''locomotive'''

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

{{Prototype property|max_speed|[[Types/double|double]]}}

{{Prototype property|air_resistance|[[Types/double|double]]}}

{{Prototype property|joint_distance|[[Types/double|double]]}}
The length between this rolling stocks front and rear joints. Joints are the point where connection_distance is measured from when rolling stock are connected to one another. Wheels sprite are placed based on the joint position.

Maximum joint distance is 15.

Note: There needs to be border at least 0.2 between the bounding box edge and joint.

{{Prototype property|connection_distance|[[Types/double|double]]}}
The distance between the joint of this rolling stock and its connected rolling stocks joint.

{{Prototype property|pictures|[[Types/RotatedSprite|RotatedSprite]]}}

{{Prototype property|wheels|[[Types/RotatedSprite|RotatedSprite]]}}

{{Prototype property|vertical_selection_shift|[[Types/double|double]]}}

== Optional properties ==

{{Prototype property|drive_over_tie_trigger|[[Types/TriggerEffect|TriggerEffect]]|optional=true}}
Usually a sound to play when the rolling stock drives over a tie.

{{Prototype property|tie_distance|[[Types/double|double]]|10.0|optional=true}}

{{Prototype property|back_light|[[Types/LightDefinition|LightDefinition]]|optional=true}}

{{Prototype property|stand_by_light|[[Types/LightDefinition|LightDefinition]]|optional=true}}

{{Prototype property|horizontal_doors|[[Types/Animation|Animation]]|optional=true}}

{{Prototype property|vertical_doors|[[Types/Animation|Animation]]|optional=true}}

{{Prototype property|color|[[Types/Color|Color]]|optional=true}}

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

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

Prototype/RollingStock

2019-11-04T22:12:28Z

Muppet9010: /* Mandatory properties */ Add some information to joints and connection distances.

{{Prototype parent|Prototype/Vehicle}}
The abstract base of all rolling stock.

{{Prototype TOC|''abstract''}}

== Extensions ==
* [[Prototype/ArtilleryWagon]] '''artillery-wagon'''
* [[Prototype/CargoWagon]] '''cargo-wagon'''
* [[Prototype/FluidWagon]] '''fluid-wagon'''
* [[Prototype/Locomotive]] '''locomotive'''

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

{{Prototype property|max_speed|[[Types/double|double]]}}

{{Prototype property|air_resistance|[[Types/double|double]]}}

{{Prototype property|joint_distance|[[Types/double|double]]}}
The length between this rolling stocks front and rear joints. Joints are the point where connection_distance is measured from when rolling stock are connected to one another. Wheels sprite are placed based on the joint position.
Maximum joint distance is 15.

Note: There needs to be border at least 0.2 between the bounding box edge and joint.

{{Prototype property|connection_distance|[[Types/double|double]]}}
The distance between the joint of this rolling stock and its connected rolling stocks joint.

{{Prototype property|pictures|[[Types/RotatedSprite|RotatedSprite]]}}

{{Prototype property|wheels|[[Types/RotatedSprite|RotatedSprite]]}}

{{Prototype property|vertical_selection_shift|[[Types/double|double]]}}

== Optional properties ==

{{Prototype property|drive_over_tie_trigger|[[Types/TriggerEffect|TriggerEffect]]|optional=true}}
Usually a sound to play when the rolling stock drives over a tie.

{{Prototype property|tie_distance|[[Types/double|double]]|10.0|optional=true}}

{{Prototype property|back_light|[[Types/LightDefinition|LightDefinition]]|optional=true}}

{{Prototype property|stand_by_light|[[Types/LightDefinition|LightDefinition]]|optional=true}}

{{Prototype property|horizontal_doors|[[Types/Animation|Animation]]|optional=true}}

{{Prototype property|vertical_doors|[[Types/Animation|Animation]]|optional=true}}

{{Prototype property|color|[[Types/Color|Color]]|optional=true}}

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

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

Desynchronization

2019-08-10T23:12:09Z

Muppet9010: /* Comparing game state & save files */ clarify the less human readable numbers

{{Languages}}
A desynchronization (desync) is when during multiplayer a player's game becomes desynchronized from the Factorio server. Their game has become different from the server's game.

== What are desyncs ==

Desyncs can be caused either by a bug in the core Factorio game code or by a bug in a mod/scenario. They should not occur during regular play.

=== Factorio multiplayer architecture ===
Factorio multiplayer code uses deterministic lockstep to synchronize clients. This is a method of synchronizing a game from one computer to another by sending only the user inputs that control that game, rather than networking the state of the objects in the game itself. It means that all player's games need to simulate every single tick of the game identically. If any computer does something ever-so-slightly different, a desynchronization (desync) occurs. The game includes processes to ensure any issues with network traffic do not cause desyncs.

=== Player experience of desyncs ===
Upon a player's game detecting a desync to the server, it immediately disconnects from the server and re-downloads the save game. This download isn't to allow the player to play the game, but to obtain the server's current copy of the save game (map and game state) to include in a desync report. After the download is complete and a desync report has been generated the player is offered the options to view the report, quit or reconnect to the server to play.

[[File:Desync report notification.jpg]]

The desync report can be provided to either the mod/scenario makers or the Factorio game developers to help them resolve the bug.
Depending upon the exact cause of the desync, the player's game may be able to reconnect to the server to play, or they may find it immediately desyncs on reconnection.

=== Desync report ===
The desync report contains both the player's and server's copy of the save game (map and game state). The player's copy is from when the desync occurred and titled ''desynced-level''. With the server's copy being from when the automatic reconnection was made and titled ''reference-level.zip''. A copy of the players Factorio log file is included titled ''log.txt''. As the report contains two copies of the save game it may have a large file size. Furthermore, the save files that are made for the desync report contain more data than normal save files, further increasing their size.

The desync report does not state the cause of the desync but rather is a record of the game state at the time of the desync.

=== Next Steps ===
The next steps after a desync occurs is to start a desync investigation. In many situations restarting the server will work around the desync in the short term and allow all players to rejoin until the conditions for the bug to occur are re-created. However, a server restart isn't guaranteed success and may lead to no players being able to rejoin the server without desyncing.

== Desync Investigations ==
In most cases when desyncs occur and mods or scenarios are being used they are the cause and need to be handled first. If they are found to not be the cause then it should be reported as a [[#Desync_reporting_with_only_base_game|core Factorio desync error]]. In both cases identifying the activity that triggers the desync is an important step. For example, whether it is tied to a player's action or activity that happens in the game (i.e. a train arriving at a station) or is a time-related event. In some cases, the desync may not be reproducible and so only a code investigation can work towards a fix.

When desyncs occur and mods/scenarios are in the use there are 2 different approaches that can be taken to help get the issue fixed. The code investigation approach requires you to be familiar with Factorio modding and its coding rules. The less technical method is to identify the mod and activity that causes the desync through trial and error so it can be reported to the mod author.

=== Identifying desync causing mod through trial and error ===
This is a less technical method aiming to identify the mod and its activity that seems to cause the desync so it can be reported to the mod/scenario author. The activity that causes the desync should be established prior to these activities being done to confirm if they are having an impact. These steps may affect the gameplay and should be done on a test save.
* Removing any newly added mods and rolling back (returning to the previous version) any updated mods to see if the issue still occurs.
* Removing mods from the game to rule them out as the cause.
Once the desync can no longer be reproduced the suspected mod can be re-added/updated and the desync recreated to confirm the mod and activity are the cause of the desync. As these steps require the server to be restarted this may in itself fix any desyncs in the short term until the conditions for the bug to occur are re-created.

=== Code investigations with mods/scenarios involved ===
The desync report is a useful reference for investigating desyncs but it does not state the cause of the desync. Comparing the desync files and use of heavy mode can assist in identifying which mods and activities to review initially. Ideally, it is supplemented by an account of what was occurring and being done by players at the point of the desync occurring to assist with narrowing down the activities of code to review. However in many complicated scenarios this may not be known prior to the investigation.

==== Code that causes desyncs ====
There are a number of ways mod and scenario code can cause desyncs, such as due to incorrect variable scoping, requiring or API event handling. Examples of these can be found in [[Tutorial:Modding tutorial/Gangsir#Multiplayer_and_desyncs|Gangsir's modding tutorial multiplayer and desyncs section]], with the full technical definition of usage constraints for API events in the [https://lua-api.factorio.com/latest/Data-Lifecycle.html Factorio API data lifecycle]. Not all instances of non-compliance will lead to desyncs or errors, but most will. For this reason, it is recommended to always maintain compliance to avoid risk and time-consuming testing. Instances of non-compliance found should be raised to the code author.

==== Comparing game state & save files ====
The desync report files and heavy mode dumps contain a number of files that can be compared by any text comparison tool to look for differences. These files are generally sequelized dumps of Lua tables or c++ game objects and so are only partially human readable. The less human readable items can include floating point numbers serilaised (0x.HEXp+HEX) and ''magic'' unique identifier numbers for prototype instances in the c++ game state. These numbers and reference ids should generally be the same between files as the in-game entity they reference normally won't have changed between the 2 save game states being obtained.
When the data differs between files the source code of that mod/scenario must be examined for all interactions with that data item for any instances of non-compliance.

==== Examining the desync files ====
Within each savegame's zip in the desync report are a number of files that when compared can show data changes. As the server copy of the save is obtained after the desync there may be genuine differences between the files. So differences aren't hard evidence of the cause of a desync, but only a pointer on where to investigate further.

* script.dat - contains the scenario and mods [https://lua-api.factorio.com/latest/Global.html Factorio global tables]. Generally, the save's persistent data should be the same between the 2 saves. On rare occasions, there can be a difference due to how the information is written out to the file. Should a mod causes a player's game to desync it can cause the player's game to stop processing other mod activity mid tick. This can lead those mod's global tables to have differences between the player and the server copies despite having no code defects themselves.
* level_with_tags_tick_XXXX.dat - contains the current game state together with additional saving tags to aid human readability. This can show if entity states or chat messages differ. ''level.dat'' is the same information, but without the descriptive tags for data values.

==== Using heavy mode command ====
[[Console#Normal_commands|Heavy mode]] is an in-game option that can be enabled to make Factorio save and load the game every tick. This allows Factorio to highlight if there are any changes in the game state between the save and subsequent load. Should a state change occur, a message is shown in-game and the save and load game states recorded to a ''dumps'' folder in the players [[Application directory#User_data_directory|user data folder]].
Typically this process will trigger for incorrect changing of data as part of the on_load event or local/global variables being changed and not persisted. The recorded game state is a dump of the internal game state, including entities, but does not include the mod's global table. This allows the checking if an entity's state has become different between the load and save state.

This process can be used to partially test a mod for multiplayer compliance without the need of multiple players or a server.

=== Desync reporting of core Factorio game ===
If no mod or scenario were involved in the desync, the desync report and activity information should be posted to the [https://forums.factorio.com/53851 Factorio forums bug report section].

== See also ==
* [https://www.factorio.com/blog/post/fff-63 FFF 63] - How heavy mode works

[[Category:Technical]]

User:Muppet9010

2019-07-30T15:58:02Z

Muppet9010: Blanked the page

Command line parameters

2019-07-26T17:18:46Z

Muppet9010: --benchmark-verbose & --output-perf-stats try to clarify which metrics are available for each

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. This page pertains to version 0.17.59.

{| class="wikitable"
|+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.
|-
| --executable-path PATH
|Override autodetected __PATH__executable. Usually not needed except on very weird systems.
|}

{| class="wikitable"
|+ 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, --start-server-load-scenario or --generate-map-preview. See data/map-gen-settings.example.json
|-
| --map-gen-seed SEED
|Map generation seed for use with --create, --start-server-load-scenario or --generate-map-preview. Will override seed specified in map gen settings
|-
| --map-gen-seed-max SEED
|Map generation seed for use with --generate-map-preview to generate multiple previews using every second seed in the interval from map-gen-seed to map-gen-seed-max.
|-
| --map-settings FILE
|Map settings for use with --create or --start-server-load-scenario. See data/base/prototypes/map-settings.lua
|-
| --preset arg
|Name of the map generation preset to be used.
|-
| --enable-runtime-autoplace-modification
|Allows changing autoplace specifications runtime in non-multiplayer non-replay enabled games for debug purposes.
|-
| --generate-map-preview PATH
|Generate preview images of the map; PATH should name a PNG file or end with a '/' or '\' to indicate a directory.
|-
| --generate-map-preview-random COUNT
|Number of maps to generate with a random seed using --generate-map-preview.
|-
| --generate-tile-properties-csv CSVFILE
|Generate tile properties into a CSV file; can be used with --generate-map-preview
|-
| --map-preview-size SCALE
|Size (in pixels) of map preview (default: 1024)
|-
| --map-preview-scale SCALE
|Scale (meters per pixel) of map preview (default: 1)
|-
| --map-preview-offset X,Y
|Offset of the center of the map, in meters (default: 0,0)
|-
| --noise-outputs TAG,TAG...
|Indicate which variables of noise program to output
|-
| --slope-shading SHADEAMOUNT
|Apply elevation shading to map preview
|-
| --slope-shade-property SHADEPROP
|Property to apply slope shading to (default: elevation)
|-
| --report-quantities PROTOTYPE,...
|When generating map preview, report approximate quantities of the named entity prototypes
|-
| --threads THREADCOUNT
|Number of threads to use when generating map previews
|-
| --disable-migration-window
|Disables the gui that is shown when opening a save with migrated content
|-
| --start-server FILE
|start a multiplayer server
|-
| --start-server-load-scenario [MOD/]NAME
|start a multiplayer server and load the specified scenario. The scenario is looked for inside the given mod. If no mod is given, it is looked for in the top-level scenarios directory.
|-
| --start-server-load-latest
|start a multiplayer server and load the latest available save
|-
| --until-tick TICK
|run a save until given map tick
|-
| --benchmark FILE
|load save and run benchmark
|-
| --benchmark-ticks N
|number of ticks for benchmarking. Default is 1000 (default: 1000)
|-
| --benchmark-verbose LIST
|comma separated list of Update timings to output each tick. "all", "timestamp" as well as all other values seen in the debug show-time-usage view's Update section are allowed here. An empty string disabled verbose benchmarking. (default: )
|-
| --output-perf-stats FILE
|path of file to which game engine performance statistics measurements should be saved. Special tags {api}, {hw}, {time} and {tag} will be replaced.
|-
| --mp-connect ADDRESS
|start factorio and connect to address
|-
| --heavy
|run the game in heavy mode
|-
| --load-game FILE
|start Factorio and load a game in singleplayer
|-
| --benchmark-graphics FILE
|load save and run it with graphics for benchmark-ticks number of ticks as normal game would
|-
| --benchmark-frame FILE
|load save and benchmark graphics rendering of single frame (prepare + render) without updating the game
|-
| --force-opengl
|use OpenGL for rendering
|-
| --force-d3d
|use Direct3D for rendering
|-
| --d3d-adapter ID
|adapter which should be used to initialized Direct3D
|-
| --d3d-feature-level
|override feature level (11, 10.1, 10)
|-
| --dxgi-blit-model
|force Blit presentation mode
|-
| --debug-graphics
|enables debugging layer for graphics API. If DirectX is used DirectX SDK needs to be installed for this to work.
|-
| --fullscreen
|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
|-
| --force-graphics-preset arg
|accepted values: very-low, low, mac-with-low-ram, medium-with-low-vram, medium, high, very-high, extreme
|-
| --gfx-safe-mode
|resets some graphics settings to values that should work on most configurations
|-
| --low-vram
|sprites that are not put into sprite atlases won't be allocated as texture objects
|-
| --shader arg
|enable/disable shader postprocessing (saved to configuration)
|-
| --disable-audio
|Disable audio. Mainly for faster startup during development.
|-
| --disable-prototype-history bool
|Disables tracking which mod created/changed what prototype. Mainly for faster startup during development.
|-
| --window-size arg
|Desired window resolution. For example "1680x1050". Or "maximized"
|-
| --single-thread-loading
|Disables loading of sprites in multiple threads.
|}

{| class="wikitable"
|+ 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
|-
| --use-server-whitelist
|If the whitelist should be used.
|-
| --server-whitelist FILE
|Path to file with server whitelist.
|-
| --server-banlist FILE
|Path to file with server banlist.
|-
| --server-adminlist FILE
|Path to file with server adminlist.
|-
| --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.

=== Creating a map from custom settings ===

Sometimes it's useful to create a new game with map and/or map generator settings stored in a JSON file rather than going through the in-game map settings screen.
One reason is that by editing the settings directly it is possible to set settings outside the range normally available from the GUI.

To do this, Factorio is run from the command-line, and a JSON file containing the map generator settings and a JSON file containing map settings (if customizing them) are needed.

Example for custom generator settings:
<pre>{
"terrain_segmentation": 0.5,
"water": "2",
"width": 0,
"height": 0,
"starting_area": "normal",
"peaceful_mode": false,
"autoplace_controls":
{
"coal": {"frequency": 1, "size": 2, "richness": 0.5},
"copper-ore": {"frequency": "low", "size": "normal", "richness": "high"},
"crude-oil": {"frequency": "normal", "size": "normal", "richness": "normal"},
"enemy-base": {"frequency": "normal", "size": "normal", "richness": "normal"},
"iron-ore": {"frequency": "normal", "size": "normal", "richness": "normal"},
"stone": {"frequency": "normal", "size": 0, "richness": "normal"},
"uranium-ore": {"frequency": "normal", "size": "none", "richness": "normal"}
},

"cliff_settings":
{
"name": "cliff",
"cliff_elevation_0": 30,
"cliff_elevation_interval": 20,
"richness": 1
},

"property_expression_names":
{
"elevation": "0_16-elevation",
"temperature": "35"
},

"seed": null
}
</pre>

Note that this is the same format as [https://lua-api.factorio.com/latest/Concepts.html#MapGenSettings MapGenSettings] that are modifiable from Lua. Everything in the file is optional.

Creating a custom save:
<pre>
"C:\Program Files\Factorio\bin\x64\Factorio.exe" --create stuff-seed123.zip --map-gen-settings map-gen-settings.json --map-gen-seed 123
</pre>

Generating a map preview:
<pre>
"C:\Program Files\Factorio\bin\x64\Factorio.exe" --generate-map-preview preview-seed123.png --map-gen-settings map-gen-settings.json --map-gen-seed 123
</pre>

== See also ==
* [[Console]]

Debug mode

2019-07-26T17:12:37Z

Muppet9010: /* List of debug-options and their function */ add notes on the time_usage metric sections as there was nothing

{{Languages}}
The ''debug mode'' is used mainly by developers and modders to analyze the running state of the game. It can be enabled to show detailed information about the game world. The default key to enable debug mode is {{keybinding|F5}}.

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

== Activate the debug mode ==

There are 4 debug-levels:

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

== Configuring the debug mode ==

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

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

Command line parameters

2019-07-26T16:33:32Z

Muppet9010: correct --benchmark-verbose input expectation

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. This page pertains to version 0.17.59.

{| class="wikitable"
|+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.
|-
| --executable-path PATH
|Override autodetected __PATH__executable. Usually not needed except on very weird systems.
|}

{| class="wikitable"
|+ 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, --start-server-load-scenario or --generate-map-preview. See data/map-gen-settings.example.json
|-
| --map-gen-seed SEED
|Map generation seed for use with --create, --start-server-load-scenario or --generate-map-preview. Will override seed specified in map gen settings
|-
| --map-gen-seed-max SEED
|Map generation seed for use with --generate-map-preview to generate multiple previews using every second seed in the interval from map-gen-seed to map-gen-seed-max.
|-
| --map-settings FILE
|Map settings for use with --create or --start-server-load-scenario. See data/base/prototypes/map-settings.lua
|-
| --preset arg
|Name of the map generation preset to be used.
|-
| --enable-runtime-autoplace-modification
|Allows changing autoplace specifications runtime in non-multiplayer non-replay enabled games for debug purposes.
|-
| --generate-map-preview PATH
|Generate preview images of the map; PATH should name a PNG file or end with a '/' or '\' to indicate a directory.
|-
| --generate-map-preview-random COUNT
|Number of maps to generate with a random seed using --generate-map-preview.
|-
| --generate-tile-properties-csv CSVFILE
|Generate tile properties into a CSV file; can be used with --generate-map-preview
|-
| --map-preview-size SCALE
|Size (in pixels) of map preview (default: 1024)
|-
| --map-preview-scale SCALE
|Scale (meters per pixel) of map preview (default: 1)
|-
| --map-preview-offset X,Y
|Offset of the center of the map, in meters (default: 0,0)
|-
| --noise-outputs TAG,TAG...
|Indicate which variables of noise program to output
|-
| --slope-shading SHADEAMOUNT
|Apply elevation shading to map preview
|-
| --slope-shade-property SHADEPROP
|Property to apply slope shading to (default: elevation)
|-
| --report-quantities PROTOTYPE,...
|When generating map preview, report approximate quantities of the named entity prototypes
|-
| --threads THREADCOUNT
|Number of threads to use when generating map previews
|-
| --disable-migration-window
|Disables the gui that is shown when opening a save with migrated content
|-
| --start-server FILE
|start a multiplayer server
|-
| --start-server-load-scenario [MOD/]NAME
|start a multiplayer server and load the specified scenario. The scenario is looked for inside the given mod. If no mod is given, it is looked for in the top-level scenarios directory.
|-
| --start-server-load-latest
|start a multiplayer server and load the latest available save
|-
| --until-tick TICK
|run a save until given map tick
|-
| --benchmark FILE
|load save and run benchmark
|-
| --benchmark-ticks N
|number of ticks for benchmarking. Default is 1000 (default: 1000)
|-
| --benchmark-verbose LIST
|comma seperated list of timings to ouput each tick. "all", "timestamp" as well as all other values seen in the debug view are allowed here. An empty string disabled verbose benchmarking. (default: )
|-
| --output-perf-stats FILE
|path of file to which performance statistics measurements should be saved. Special tags {api}, {hw}, {time} and {tag} will be replaced.
|-
| --mp-connect ADDRESS
|start factorio and connect to address
|-
| --heavy
|run the game in heavy mode
|-
| --load-game FILE
|start Factorio and load a game in singleplayer
|-
| --benchmark-graphics FILE
|load save and run it with graphics for benchmark-ticks number of ticks as normal game would
|-
| --benchmark-frame FILE
|load save and benchmark graphics rendering of single frame (prepare + render) without updating the game
|-
| --force-opengl
|use OpenGL for rendering
|-
| --force-d3d
|use Direct3D for rendering
|-
| --d3d-adapter ID
|adapter which should be used to initialized Direct3D
|-
| --d3d-feature-level
|override feature level (11, 10.1, 10)
|-
| --dxgi-blit-model
|force Blit presentation mode
|-
| --debug-graphics
|enables debugging layer for graphics API. If DirectX is used DirectX SDK needs to be installed for this to work.
|-
| --fullscreen
|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
|-
| --force-graphics-preset arg
|accepted values: very-low, low, mac-with-low-ram, medium-with-low-vram, medium, high, very-high, extreme
|-
| --gfx-safe-mode
|resets some graphics settings to values that should work on most configurations
|-
| --low-vram
|sprites that are not put into sprite atlases won't be allocated as texture objects
|-
| --shader arg
|enable/disable shader postprocessing (saved to configuration)
|-
| --disable-audio
|Disable audio. Mainly for faster startup during development.
|-
| --disable-prototype-history bool
|Disables tracking which mod created/changed what prototype. Mainly for faster startup during development.
|-
| --window-size arg
|Desired window resolution. For example "1680x1050". Or "maximized"
|-
| --single-thread-loading
|Disables loading of sprites in multiple threads.
|}

{| class="wikitable"
|+ 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
|-
| --use-server-whitelist
|If the whitelist should be used.
|-
| --server-whitelist FILE
|Path to file with server whitelist.
|-
| --server-banlist FILE
|Path to file with server banlist.
|-
| --server-adminlist FILE
|Path to file with server adminlist.
|-
| --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.

=== Creating a map from custom settings ===

Sometimes it's useful to create a new game with map and/or map generator settings stored in a JSON file rather than going through the in-game map settings screen.
One reason is that by editing the settings directly it is possible to set settings outside the range normally available from the GUI.

To do this, Factorio is run from the command-line, and a JSON file containing the map generator settings and a JSON file containing map settings (if customizing them) are needed.

Example for custom generator settings:
<pre>{
"terrain_segmentation": 0.5,
"water": "2",
"width": 0,
"height": 0,
"starting_area": "normal",
"peaceful_mode": false,
"autoplace_controls":
{
"coal": {"frequency": 1, "size": 2, "richness": 0.5},
"copper-ore": {"frequency": "low", "size": "normal", "richness": "high"},
"crude-oil": {"frequency": "normal", "size": "normal", "richness": "normal"},
"enemy-base": {"frequency": "normal", "size": "normal", "richness": "normal"},
"iron-ore": {"frequency": "normal", "size": "normal", "richness": "normal"},
"stone": {"frequency": "normal", "size": 0, "richness": "normal"},
"uranium-ore": {"frequency": "normal", "size": "none", "richness": "normal"}
},

"cliff_settings":
{
"name": "cliff",
"cliff_elevation_0": 30,
"cliff_elevation_interval": 20,
"richness": 1
},

"property_expression_names":
{
"elevation": "0_16-elevation",
"temperature": "35"
},

"seed": null
}
</pre>

Note that this is the same format as [https://lua-api.factorio.com/latest/Concepts.html#MapGenSettings MapGenSettings] that are modifiable from Lua. Everything in the file is optional.

Creating a custom save:
<pre>
"C:\Program Files\Factorio\bin\x64\Factorio.exe" --create stuff-seed123.zip --map-gen-settings map-gen-settings.json --map-gen-seed 123
</pre>

Generating a map preview:
<pre>
"C:\Program Files\Factorio\bin\x64\Factorio.exe" --generate-map-preview preview-seed123.png --map-gen-settings map-gen-settings.json --map-gen-seed 123
</pre>

== See also ==
* [[Console]]

Console

2019-07-22T21:48:42Z

Muppet9010: /* World manipulation scripts */ add map charting 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 used for:

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

There are three types of commands:

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

__TOC__

=== Using the console ===
The console display can be toggled with the {{keybinding|/}} (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 chat.

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.

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 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
|-
| /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.
|-
| /c <command>
| Executes a Lua command.
|-
| /editor
| Toggles the map editor.
|-
| /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 <span style="color:#FF0000">achievements will be permanently disabled for the save</span> as soon as you use a script command.

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

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

=== Reveal all explored map ===

Revels all of the player's team's explored map.
<syntaxhighlight lang="lua">
/c game.player.force.rechart()
</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 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 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.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 ==

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

Types/EntityPrototypeFlags

2019-07-17T10:57:55Z

Muppet9010: /* "hidden" */ add removed from filter list

Array ([[Types/table]]) of strings. The possible strings are listed below.

== "not-rotatable" ==
Can't be rotated before or after placing.

== "placeable-[force]" ==
*"placeable-player"
*"placeable-neutral"
*"placeable-enemy"
placeable neutral/player/enemy determine the default force when placing entities in the map editor and using the *AUTO* option for the force.

== "placeable-off-grid" ==
placeable-off-grid refers to the fact that most entities are placed on an invisible 'grid' within the world, entities with the placeable-off-grid flag do not have to line up with this grid (like trees and land-mines)

== "player-creation" ==
Makes it possible for the biter AI to target the entity as a distraction. Makes it possible to blueprint, deconstruct, and repair the entity (can be turned off again using the specific flags). Enables smoke to be created automatically when building the entity.

== "building-direction-8-way" ==
Uses 45 degree angle increments when selecting direction.

== "filter-directions" ==
Used to automatically detect the proper direction, if possible. Used by base with the pump, train stop, and train signal.

== "fast-replaceable-no-build-while-moving" ==
Fast replace will not apply when building while moving.

== "breaths-air" ==
This is used to specify that the entity breaths air, and so is affected by poison (currently [[Poison_capsule|Poison Capsules]] are the only source).

== "not-repairable" ==
Used to specify that the entity can not be 'healed' by repair-packs (or construction robots with repair packs)

== "not-on-map" ==
The entity does not get drawn on the map.

== "not-blueprintable" ==
The entity can't be used in blueprints.

== "not-deconstructable" ==
The entity can't be deconstructed.

== "hidden" ==
Hides the entity from the bonus GUI (button above the map), from the made in property of recipe tooltips and from filter lists.

== "hide-alt-info" ==
Hides the alt-info of an entity in alt-mode, for example the recipe icon.

== "fast-replaceable-no-cross-type-while-moving" ==
Do not fast replace over other entity types when building while moving.

== "no-gap-fill-while-building" ==

== "not-flammable" ==
Do not apply fire stickers to the entity.

== "no-automated-item-removal" ==

Prevents inserters and loaders from taking items from this entity.

== "no-automated-item-insertion" ==

Prevents inserters and loaders from inserting items into this entity.

== "no-copy-paste" ==

== "not-selectable-in-game" ==

== "not-upgradable" ==
The entity can't be selected by the Upgrade Planner tool.

== Example ==
flags = {"placeable-neutral", "player-creation"}

Types/CollisionMask

2019-07-08T22:43:15Z

Muppet9010: /* "consider-tile-transitions" */ add an explanation

The collision mask is specified as an Array ([[Types/table]]) of strings. Every entry is a specification of one layer the object collides with or a special collision option.

== Layers ==
* ground-tile
* water-tile
* resource-layer
* doodad-layer
* floor-layer
* item-layer
* ghost-layer
* object-layer
* player-layer
* train-layer
* layer-11
* layer-12
* layer-13
* layer-14
* layer-15

Layer-11 through layer-15 are currently unused by the core game.

== Collision options ==
These are not collision masks, instead they control other aspects of collision, but they are still specified here.
=== "not-colliding-with-itself" ===
Any 2 entities that both have this option enabled on their prototype and have an identical collision mask layers list will not collide. Other collision mask options are not included in the identical layer list check. This does mean that 2 different prototypes with the same collision mask layers and this option enabled will not collide.

=== "consider-tile-transitions" ===

Uses the prototypes position rather than its collision box when doing collision checks with tile prototypes. Allows the prototype to overlap colliding tiles up until its center point.

=== "colliding-with-tiles-only" ===
Any prototype with this collision option will only be checked for collision with other prototype's collision masks if they are a tile.

== Default collision masks ==
The default collision masks of all entity types can be found [[Prototype/Entity#collision_mask|here]].

Example (Most common collision mask of buildings):
<syntaxhighlight lang="lua">collision_mask = { "item-layer", "object-layer", "player-layer", "water-tile"}</syntaxhighlight>

Prototype/Explosion

2019-07-05T22:53:30Z

Muppet9010: animation is mandatory and the game errors on startup for an explosion without one

== Basics ==
Prototype type: '''explosion'''

Extends [[Prototype/Entity]].

== Extensions ==
* [[Prototype/FlameThrowerExplosion]] '''flame-thrower-explosion'''

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

=== animations ===
'''Type''': [[Types/AnimationVariations]]

Must have at least 1 animation frame.

== Optional properties ==

=== sound ===
'''Type''': [[Types/Sound]]

=== rotate ===
'''Type''': [[Types/bool]]

'''Default''': false

=== beam ===
'''Type''': [[Types/bool]]

'''Default''': false

=== height ===
'''Type''': [[Types/float]]

'''Default''': 1

=== correct_rotation ===
'''Type''': [[Types/bool]]

'''Default''': false

=== smoke ===
'''Type''': [[Types/string]]

Name of a trivial-smoke prototype. Mandatory if <code>smoke_count</code> > 0.

=== smoke_count ===
'''Type''': [[Types/uint16]]

'''Default''': 0

=== smoke_slow_down_factor ===
'''Type''': [[Types/float]]

'''Default''': 0

=== light ===
'''Type''': [[Types/LightDefinition]]

Prototype/Explosion

2019-07-05T22:51:51Z

Muppet9010: sound isn't a mandatory property

== Basics ==
Prototype type: '''explosion'''

Extends [[Prototype/Entity]].

== Extensions ==
* [[Prototype/FlameThrowerExplosion]] '''flame-thrower-explosion'''

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

== Optional properties ==

=== sound ===
'''Type''': [[Types/Sound]]

=== animations ===
'''Type''': [[Types/AnimationVariations]]

Must have at least 1 animation frame.

=== rotate ===
'''Type''': [[Types/bool]]

'''Default''': false

=== beam ===
'''Type''': [[Types/bool]]

'''Default''': false

=== height ===
'''Type''': [[Types/float]]

'''Default''': 1

=== correct_rotation ===
'''Type''': [[Types/bool]]

'''Default''': false

=== smoke ===
'''Type''': [[Types/string]]

Name of a trivial-smoke prototype. Mandatory if <code>smoke_count</code> > 0.

=== smoke_count ===
'''Type''': [[Types/uint16]]

'''Default''': 0

=== smoke_slow_down_factor ===
'''Type''': [[Types/float]]

'''Default''': 0

=== light ===
'''Type''': [[Types/LightDefinition]]

Prototype/Shortcut

2019-07-01T14:47:57Z

Muppet9010: /* toggleable */ add hint on how this is actually used

==Basics==
Prototype type: '''shortcut'''

Definition for a shortcut in the shortcut bar of tools.

== Mandatory properties ==
Inherits all properties from [[Prototype]].

=== action ===
'''Type''': [[Types/string]]

One of "toggle-alt-mode", "undo", "copy", "cut", "paste", "import-string", "toggle-personal-roboport", "toggle-equipment-movement-bonus", "create-blueprint-item" and "lua".

=== icon ===
'''Type''': [[Types/Sprite]]

== Optional properties ==

=== item_to_create ===
'''Type''': [[Types/string]]

Name of a [[Prototype/Item]]. The item to create when clicking on a shortcut with the action set to "create-blueprint-item".

=== technology_to_unlock ===
'''Type''': [[Types/string]]

Name of a [[Prototype/Technology]]. The technology that must be researched before this shortcut can be used.

=== toggleable ===
'''Type''': [[Types/bool]]

'''Default''': false

Must be enabled for the Factorio API to be able to set the toggled state on the shortcut button, see [https://lua-api.factorio.com/latest/LuaPlayer.html#LuaPlayer.set_shortcut_toggled LuaPlayer.set_shortcut_toggled].

=== associated_control_input ===
'''Type''': [[Types/string]]

'''Default''': ""

Name of a custom input or vanilla control. Used to show the keybind in the tooltip of the shortcut.

=== small_icon ===
'''Type''': [[Types/Sprite]]

=== disabled_icon ===
'''Type''': [[Types/Sprite]]

=== disabled_small_icon ===
'''Type''': [[Types/Sprite]]

=== style ===
'''Type''': [[Types/string]]

'''Default''': "default"

One of "default", "blue", "red" and "green".

== Example ==

<syntaxhighlight lang="lua">{
type = "shortcut",
name = "give-deconstruction-planner",
order = "b[blueprints]-g[deconstruction-planner]",
action = "create-blueprint-item",
localised_name = {"shortcut.make-deconstruction-planner"},
technology_to_unlock = "construction-robotics",
item_to_create = "deconstruction-planner",
style = "red",
icon =
{
filename = "__base__/graphics/icons/shortcut-toolbar/new-deconstruction-planner-x32-white.png",
priority = "extra-high-no-scale",
size = 32,
scale = 1,
flags = {"icon"}
},
small_icon =
{
filename = "__base__/graphics/icons/shortcut-toolbar/new-deconstruction-planner-x24.png",
priority = "extra-high-no-scale",
size = 24,
scale = 1,
flags = {"icon"}
},
disabled_small_icon =
{
filename = "__base__/graphics/icons/shortcut-toolbar/new-deconstruction-planner-x24-white.png",
priority = "extra-high-no-scale",
size = 24,
scale = 1,
flags = {"icon"}
},
}</syntaxhighlight>

Types/CollisionMask

2019-06-22T16:38:18Z

Muppet9010: /* "colliding-with-tiles-only" */ add simple explanation to confirm behaviour.

The collision mask is specified as an Array ([[Types/table]]) of strings. Every entry is a specification of one layer the object collides with or a special collision option.

== Layers ==
* ground-tile
* water-tile
* resource-layer
* doodad-layer
* floor-layer
* item-layer
* ghost-layer
* object-layer
* player-layer
* train-layer
* layer-11
* layer-12
* layer-13
* layer-14
* layer-15

Layer-11 through layer-15 are currently unused by the core game.

== Collision options ==
These are not collision masks, instead they control other aspects of collision, but they are still specified here.
=== "not-colliding-with-itself" ===
Any 2 entities that both have this option enabled on their prototype and have an identical collision mask layers list will not collide. Other collision mask options are not included in the identical layer list check. This does mean that 2 different prototypes with the same collision mask layers and this option enabled will not collide.

=== "consider-tile-transitions" ===
=== "colliding-with-tiles-only" ===
Any prototype with this collision option will only be checked for collision with other prototype's collision masks if they are a tile.

== Default collision masks ==
The default collision masks of all entity types can be found [[Prototype/Entity#collision_mask|here]].

Example (Most common collision mask of buildings):
<syntaxhighlight lang="lua">collision_mask = { "item-layer", "object-layer", "player-layer", "water-tile"}</syntaxhighlight>

Prototype/AssemblingMachine

2019-06-21T18:12:29Z

Muppet9010: ingredient_count isn't mandatory any more

== Basics ==
Prototype type: '''assembling-machine'''

An assembling machine - like the assembling machines 1/2/3 in the game, but you can use your own recipe categories. Based on [[Prototype/CraftingMachine]].

== Extensions ==
* [[Prototype/RocketSilo]] '''rocket-silo'''

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

== Optional properties ==
=== fixed_recipe ===
'''Type''': [[Types/string]]

'''Default''': ""

The preset recipe of this machine. This machine does not show a recipe selection if this is set. The base game uses this for the [[rocket silo]].

=== gui_title_key ===
'''Type''': [[Types/string]]

'''Default''': ""

The locale key of the title of the GUI that is shown when the player opens the assembling machine.

=== ingredient_count ===
'''Type''': [[Types/uint8]]

'''Default''': 255

Sets the maximum number of ingredients this machine can craft with. Any recipe with more ingredients than this will be unavailable in this machine.

This only counts item ingredients, not fluid ingredients! This means if ingredient count is 2, and the recipe has 2 item ingredients and 1 fluid ingredient, it can still be crafted in the machine.

Prototype/Technology

2019-05-03T23:08:30Z

Muppet9010: /* unit */ add SPACE character

==Basics==
Prototype type: '''technology'''

More in [[Research]]

== General properties ==
Inherits all properties from [[Prototype]].

=== icons, icon, icon_size (IconSpecification) ===
'''Type''': [[Types/IconSpecification]]

=== name ===
:''See [[Prototype#name ]]''

Inherited from [[Prototype]]. If the name ends with <code>-number</code>, the number is ignored for localization purposes. E. g. if the name is <code>whatever-name-3</code>, the game looks for the <code>technology-name.whatever-name</code> localization. The technology tree will also show the number on the technology icon.

== Technology data ==
If the technology does not have a difficulty, this is located directly in the prototype. Otherwise, if the "normal" or "expensive" property exists, the technology has difficulty. Then, the technology data has to be specified for each difficulty instead of directly in the prototype. If at least one difficulty has technology data defined, the other difficulty can be set to false. This will give it the exact same properties as the difficulty that is defined.

=== upgrade ===
'''Type''': [[Types/bool]]

'''Default''': false

When set to true, and the technology contains several levels, only the relevant one is displayed in the technology screen.
<syntaxhighlight lang="lua"> {
type = "technology",
name = "physical-projectile-damage-2",
...
upgrade = "true"
}</syntaxhighlight>

=== enabled ===
'''Type''': [[Types/bool]]

'''Default''': true

=== hidden ===
'''Type''': [[Types/bool]]

'''Default''': false

Hides the technology from the tech screen.

=== unit ===
'''Type''': [[Types/table]] of properties:
* count — [[Types/double]] — How many units are needed. Must be positive. May not be specified if count_formula is specified.
* count_formula — [[Types/string]] — Formula that specifies how many units are needed per level of the infinite technology. May not be specified if count is specified. The formula is executed following the BODMAS order.
: Supported operators & characters:
: {| class="wikitable"
|-
! Operator !! meaning
|-
| + || Addition
|-
| - || Subtraction
|-
| * || Multiplication
|-
| ^ || Power, raise the preceding base number by the following exponent number
|-
| () || Brackets for order, supported nested brackets
|-
| l or L || The current level of the technology
|-
| Digits || Are treated as numbers
|-
| . || Decimal point in number
|-
| SPACE || Space characters are ignored
|}
* time — [[Types/double]] — How much time is needed per one unit, in lab with crafting speed 1 it is the number of seconds.
* ingredients — [[Types/table]] of [[Types/IngredientPrototype]] — list of ingredients needed for one units

:<syntaxhighlight lang="lua">
unit =
{
count_formula = "2^(L-6)*1000",
ingredients =
{
{"automation-science-pack", 1},
{"logistic-science-pack", 1},
{"chemical-science-pack", 1},
{"production-science-pack", 1},
{"utility-science-pack", 1},
{"space-science-pack", 1}
},
time = 60
}</syntaxhighlight>

=== max_level ===
'''Type''': [[Types/uint32]] or [[Types/string]]

'''Default''': Same as the level of the technology, which is 0 for non-upgrades, and the level of the upgrade for upgrades.

"infinite" for infinite technologies, otherwise uint.

=== prerequisites ===
'''Type''': [[Types/table]] of [[Types/string]]

List of technologies needed to be researched before this one can be researched.
prerequisites = {"explosives", "military-2"}

=== effects ===
'''Type''': [[Types/table]] of [http://lua-api.factorio.com/latest/Concepts.html#Modifier Modifier]

List of effects of the technology (applied when the technology is researched).

{
{
type = "unlock-recipe",
recipe = "land-mine"
}
}

Prototype/Technology

2019-05-03T23:00:07Z

Muppet9010: /* unit */ correct current technology characters

==Basics==
Prototype type: '''technology'''

More in [[Research]]

== General properties ==
Inherits all properties from [[Prototype]].

=== icons, icon, icon_size (IconSpecification) ===
'''Type''': [[Types/IconSpecification]]

=== name ===
:''See [[Prototype#name ]]''

Inherited from [[Prototype]]. If the name ends with <code>-number</code>, the number is ignored for localization purposes. E. g. if the name is <code>whatever-name-3</code>, the game looks for the <code>technology-name.whatever-name</code> localization. The technology tree will also show the number on the technology icon.

== Technology data ==
If the technology does not have a difficulty, this is located directly in the prototype. Otherwise, if the "normal" or "expensive" property exists, the technology has difficulty. Then, the technology data has to be specified for each difficulty instead of directly in the prototype. If at least one difficulty has technology data defined, the other difficulty can be set to false. This will give it the exact same properties as the difficulty that is defined.

=== upgrade ===
'''Type''': [[Types/bool]]

'''Default''': false

When set to true, and the technology contains several levels, only the relevant one is displayed in the technology screen.
<syntaxhighlight lang="lua"> {
type = "technology",
name = "physical-projectile-damage-2",
...
upgrade = "true"
}</syntaxhighlight>

=== enabled ===
'''Type''': [[Types/bool]]

'''Default''': true

=== hidden ===
'''Type''': [[Types/bool]]

'''Default''': false

Hides the technology from the tech screen.

=== unit ===
'''Type''': [[Types/table]] of properties:
* count — [[Types/double]] — How many units are needed. Must be positive. May not be specified if count_formula is specified.
* count_formula — [[Types/string]] — Formula that specifies how many units are needed per level of the infinite technology. May not be specified if count is specified. The formula is executed following the BODMAS order.
: Supported operators:
: {| class="wikitable"
|-
! Operator !! meaning
|-
| + || Addition
|-
| - || Subtraction
|-
| * || Multiplication
|-
| ^ || Power, raise the preceding base number by the following exponent number
|-
| () || Brackets for order, supported nested brackets
|-
| l or L || The current level of the technology
|-
| Digits || Are treated as numbers
|-
| . || Decimal point in number
|}
* time — [[Types/double]] — How much time is needed per one unit, in lab with crafting speed 1 it is the number of seconds.
* ingredients — [[Types/table]] of [[Types/IngredientPrototype]] — list of ingredients needed for one units

:<syntaxhighlight lang="lua">
unit =
{
count_formula = "2^(L-6)*1000",
ingredients =
{
{"automation-science-pack", 1},
{"logistic-science-pack", 1},
{"chemical-science-pack", 1},
{"production-science-pack", 1},
{"utility-science-pack", 1},
{"space-science-pack", 1}
},
time = 60
}</syntaxhighlight>

=== max_level ===
'''Type''': [[Types/uint32]] or [[Types/string]]

'''Default''': Same as the level of the technology, which is 0 for non-upgrades, and the level of the upgrade for upgrades.

"infinite" for infinite technologies, otherwise uint.

=== prerequisites ===
'''Type''': [[Types/table]] of [[Types/string]]

List of technologies needed to be researched before this one can be researched.
prerequisites = {"explosives", "military-2"}

=== effects ===
'''Type''': [[Types/table]] of [http://lua-api.factorio.com/latest/Concepts.html#Modifier Modifier]

List of effects of the technology (applied when the technology is researched).

{
{
type = "unlock-recipe",
recipe = "land-mine"
}
}

Prototype/Technology

2019-05-03T22:54:05Z

Muppet9010: /* unit */ added count_formula operators table, added misc other details and fuller unit example using existing format

==Basics==
Prototype type: '''technology'''

More in [[Research]]

== General properties ==
Inherits all properties from [[Prototype]].

=== icons, icon, icon_size (IconSpecification) ===
'''Type''': [[Types/IconSpecification]]

=== name ===
:''See [[Prototype#name ]]''

Inherited from [[Prototype]]. If the name ends with <code>-number</code>, the number is ignored for localization purposes. E. g. if the name is <code>whatever-name-3</code>, the game looks for the <code>technology-name.whatever-name</code> localization. The technology tree will also show the number on the technology icon.

== Technology data ==
If the technology does not have a difficulty, this is located directly in the prototype. Otherwise, if the "normal" or "expensive" property exists, the technology has difficulty. Then, the technology data has to be specified for each difficulty instead of directly in the prototype. If at least one difficulty has technology data defined, the other difficulty can be set to false. This will give it the exact same properties as the difficulty that is defined.

=== upgrade ===
'''Type''': [[Types/bool]]

'''Default''': false

When set to true, and the technology contains several levels, only the relevant one is displayed in the technology screen.
<syntaxhighlight lang="lua"> {
type = "technology",
name = "physical-projectile-damage-2",
...
upgrade = "true"
}</syntaxhighlight>

=== enabled ===
'''Type''': [[Types/bool]]

'''Default''': true

=== hidden ===
'''Type''': [[Types/bool]]

'''Default''': false

Hides the technology from the tech screen.

=== unit ===
'''Type''': [[Types/table]] of properties:
* count — [[Types/double]] — How many units are needed. Must be positive. May not be specified if count_formula is specified.
* count_formula — [[Types/string]] — Formula that specifies how many units are needed per level of the infinite technology. May not be specified if count is specified. The formula is executed following the BODMAS order.
: Supported operators:
: {| class="wikitable"
|-
! Operator !! meaning
|-
| + || Addition
|-
| - || Subtraction
|-
| * || Multiplication
|-
| ^ || Power, raise the preceding base number by the following exponent number
|-
| () || Brackets for order, supported nested brackets
|-
| a-z A-Z || The current level of the technology, any characters within the range can be used
|-
| Digits || Are treated as numbers
|-
| . || Decimal point in number
|}
* time — [[Types/double]] — How much time is needed per one unit, in lab with crafting speed 1 it is the number of seconds.
* ingredients — [[Types/table]] of [[Types/IngredientPrototype]] — list of ingredients needed for one units

:<syntaxhighlight lang="lua">
unit =
{
count_formula = "2^(L-6)*1000",
ingredients =
{
{"automation-science-pack", 1},
{"logistic-science-pack", 1},
{"chemical-science-pack", 1},
{"production-science-pack", 1},
{"utility-science-pack", 1},
{"space-science-pack", 1}
},
time = 60
}</syntaxhighlight>

=== max_level ===
'''Type''': [[Types/uint32]] or [[Types/string]]

'''Default''': Same as the level of the technology, which is 0 for non-upgrades, and the level of the upgrade for upgrades.

"infinite" for infinite technologies, otherwise uint.

=== prerequisites ===
'''Type''': [[Types/table]] of [[Types/string]]

List of technologies needed to be researched before this one can be researched.
prerequisites = {"explosives", "military-2"}

=== effects ===
'''Type''': [[Types/table]] of [http://lua-api.factorio.com/latest/Concepts.html#Modifier Modifier]

List of effects of the technology (applied when the technology is researched).

{
{
type = "unlock-recipe",
recipe = "land-mine"
}
}

Version history/0.17.0

2019-05-03T21:55:12Z

Muppet9010: added version 0.17.16

__NOTOC__

== 0.17.16 ==
Date: 19.03.2019

=== Changes ===

* Disabled vanilla pollution attacks in the NPE until after the final wave.
* Changing teams in PvP will try to preserve the current character. ([https://forums.factorio.com/68018 more])

=== Bugfixes ===

* Fixed alerts showing for trees and rocks in the NPE ([https://forums.factorio.com/65370 more])
* Fixed solid fuel not triggering "fuel furnace" quest item ([https://forums.factorio.com/67941 more])
* Potentially fixed scrap metal crash bug again ([https://forums.factorio.com/67821 more])
* Fixed that a fluid furnace revived from a ghost would not work. ([https://forums.factorio.com/67372 more])
* Fixed that launching tutorials could leave the running game in a broken state. ([https://forums.factorio.com/68046 more])
* Fixed that clearing the ghost cursor did not clear the hand in the quickbar. ([https://forums.factorio.com/68062 more])
* Fixed Compilatron blocking placement of burner inserter in NPE ([https://forums.factorio.com/68063 more])
* Fixing a bug from last version that allowed fluid mixing by setting a recipe in assembler. ([https://forums.factorio.com/68074 more])
* Different alert when unable to revive ghost due to fluid mixing by hand vs. by robot. ([https://forums.factorio.com/68074 more])
* Fixed spitters would not properly target construction robots that are blocked from fulfilling their task. ([https://forums.factorio.com/67886 more])
* Fixed a crash when joining Steam game invites while a multiplayer connection is in progress.
* Fixed that the "research finished" indicator would display the wrong technology level. ([https://forums.factorio.com/67864 more])
* Fixed a crash when removing the end rail of a temporary train order. ([https://forums.factorio.com/67926 more])
* Fixed that cargo wagon filters wouldn't get preserved in blueprint strings. ([https://forums.factorio.com/67641 more])

=== Scripting ===

* Fixed that printing the output of LuaProfiler anywhere except log(...) would cause a desync. Note: this means if the results are shown in things like player.print() they won't persist through save/load (but won't cause desyncs).
* Fixed Electric Pole smart coverage placement not building over other pole ghosts. ([https://forums.factorio.com/68083 more])

== 0.17.15 ==
Date: 18.03.2019

=== Changes ===

* Fixed that trains wouldn't depart for temporary stops when waiting at a station. ([https://forums.factorio.com/67811 more])
* Fixed that two headed train running out of fuel didn't trigger the out of fuel alert in one of the directions. ([https://forums.factorio.com/67820 more])
* Improved Compilatron's ability to select a free space when indicating structures by a factor of 16.6.
* The player must now wait for Compilatron to follow before being allowed to evacuate the first area of the NPE.
* The player must collect at least some of their structures before evacuating the first area of the NPE.
* Updated the player spawn after big biter attack in case the player wants to check how aggressive the biters are.
* Compilatron now has its own icon.
* Biters and worms in the NPE will now be aggressive except in special situations.

=== Gui ===

* It is now possible to scroll horizontally with a touch pad in the tech tree view. ([https://forums.factorio.com/66874 more])

=== Bugfixes ===

* Fixed bugged Compilatron speech in NPE when showing blocked miner.
* Turrets placed in the starting area will now be detected during the entrench step of the NPE. ([https://forums.factorio.com/67772 more])
* Fixed flamethrower turret range visualization was rendered in wrong layer. ([https://forums.factorio.com/67903 more])
* Fixed editing map gen settings in the map editor would crash the game. ([https://forums.factorio.com/67839 more])
* Fixed that robots would still try to deconstruct trains that left their network. ([https://forums.factorio.com/67916 more])
* Reduced screen tearing on Windows 7 when Aero is disabled. ([https://forums.factorio.com/67158 more])
* Fixed that converting games to scenarios and back could corrupt script global data. ([https://forums.factorio.com/66812 more])
* Fixed that disabling friendly fire prevented fish from healing. ([https://forums.factorio.com/67953 more])
* Fixed that LuaEntity::destroy({do_cliff_correction=true}) was ignored. ([https://forums.factorio.com/67837 more])
* Fixed toggle state of item selection buttons when clicked with item to fast-select. ([https://forums.factorio.com/67465 more])
* Fixed that the Q that cancels wire dragging also removed the hand from the quickbar. ([https://forums.factorio.com/67192 more])
* Fixed that selecting quickbar slot while dragging wire only cancelled the dragging, but had to be pressed again to select the slot. ([https://forums.factorio.com/67192 more])
* Fixed that modded fluid streams could crash the game in some situations. ([https://forums.factorio.com/67999 more])
* Fixed that keys blocked by textfield didn't include CONTROL + A (to select all), the same way as it is doing for (CONTROL + C/V/X). ([https://forums.factorio.com/67047 more])
* Fixed the double-click to clear functionality of number text field. ([https://forums.factorio.com/67949 more])
* Fixed a crash when migrating mods related to assembling machines and fluids. ([https://forums.factorio.com/67118 more])
* Fixed that exporting a blueprint to the library could crash the game. ([https://forums.factorio.com/67987 more])
* Fixed a crash when a modded assembler is built over a ghost of assembler with different rotation. ([https://forums.factorio.com/67732 more])
* Fixed damage technology migrations not migrating infinite technologies properly. ([https://forums.factorio.com/67731 more])
* Potentially fixed a Linux-specific bug where the game would react to key presses not intended for it. ([https://forums.factorio.com/66402 more])

=== Scripting ===

* Added LuaGameScript::create_profiler() which can be used to measure script performance.

== 0.17.14 ==
Date: 15.03.2019

=== Bugfixes ===

* Fixed that research queue setting in the New Map GUI wouldn't remember its value. ([https://forums.factorio.com/67370 more])
* Fixed a crash when hand replacing an assembler ghost with fluid mixing. ([https://forums.factorio.com/67732 more])
* Fixed migration of fluid-using modded mining drill.
* Fixed ten_minutes modifier bug in NPE.
* Fixed broken resetting of scenario context.

== 0.17.13 ==
Date: 15.03.2019

=== Changes ===

* Modified NPE quest structure to give the player more notice of impending attacks
* Added missing Steel plate recipe to NPE tech tree ([https://forums.factorio.com/67504 more])
* Removed unneeded Iron stick recipe from NPE
* Fast replacing between rail signal and rail chain signal will preserve circuit wire connection and relevant settings. ([https://forums.factorio.com/67682 more])

=== Bugfixes ===

* Fixed that the evolution pollution factor wasn't migrated properly. (pollution was increasing evolution 16.6 times faster than it should for existing saves).
* Fixed a crash when trying to assign invalid things to LuaPlayer::game_view_settings. ([https://forums.factorio.com/67682 more])
* Fixed that replays could trigger autosaves and take screenshots. ([https://forums.factorio.com/65901 more])
* Fixed that changing mod settings through Lua commands wouldn't trigger the settings-changed event. ([https://forums.factorio.com/66395 more])
* Fixed that /config didn't support name, description, or tags. ([https://forums.factorio.com/67463 more])
* Fixed a crash when using temporary stations. ([https://forums.factorio.com/67700 more])
* Fixed that drop-item into vehicles didn't work. ([https://forums.factorio.com/65948 more])
* Fixed that resizing the window while loading on 4k screens would cause the progress bar to not render. ([https://forums.factorio.com/65987 more])
* Fixed that the crafting queue GUI wouldn't show correctly when loading a save with crafting in progress. ([https://forums.factorio.com/66220 more])
* Fixed text box line wrapping didn't work correctly in most cases. ([https://forums.factorio.com/65437 more])
* Fixed a crash when re-joining a multiplayer game while the tips-and-tricks window is visible.
* Fixed a crash when opening the set-filter GUI on the ammo inventory of other player using the /open command.
* Fixed that the pollution generation of steel furnace wasn't what it was supposed compared to 0.16.
* Fixed that you could die during a cutscene and become a ghost when it ended. ([https://forums.factorio.com/67651 more])
* Fixed that you could die with required items in your inventory and make the NPE unwinnable. ([https://forums.factorio.com/65829 more])
* Fixed that some turrets wouldn't be detected by the quest objectives in the NPE. ([https://forums.factorio.com/66013 more])
* Fixed issue with detecting Steam engine on network in NPE ([https://forums.factorio.com/66717 more])
* Fixed biters getting stuck in massive clumps in NPE ([https://forums.factorio.com/66226 more])
* Fixed biters becoming frozen after arriving at target destination in NPE ([https://forums.factorio.com/66494 more])
* Fixed crash when mining scrap metal in NPE ([https://forums.factorio.com/65512 more])
* Fixed biters losing aggression after save/load during NPE ([https://forums.factorio.com/66410 more])
* Fixed some windows in the NPE having inconsistent header draggable textures ([https://forums.factorio.com/66295 more])
* Fixed build order for Compilatron in NPE so it is more successful ([https://forums.factorio.com/66703 more])
* Fixed set_active_quick_bar_page not updating the GUI. ([https://forums.factorio.com/66142 more])
* Fixed that waiting on temporary stop was reset every time other station was added. ([https://forums.factorio.com/6034 more])
* Fixed that blueprints with trains and rails still could snap the trains to different rails. ([https://forums.factorio.com/67384 more])
* Fixed LuaGameScript::take_screenshot with anti_alias = true would produce bad screenshots ([https://forums.factorio.com/67685 more])
* Fixed that snapping to position while building ghost didn't update the ghost position properly, leading to invisible entities in rare cases. ([https://forums.factorio.com/66908 more])
* Fixed a crash when destroying trains while in the paused map editor state. ([https://forums.factorio.com/67734 more])
* Fixed that recipes could be setup to produce > 1 count of items that are never meant to be stacked. ([https://forums.factorio.com/67736 more])
* Fixed that creating a new blueprint and pressing Q after it was setup removes it instead of putting it into inventory. ([https://forums.factorio.com/67737 more])
* Fixed LuaGameScript::take_screenshot with anti_alias = true would produce bad screenshots. ([https://forums.factorio.com/67685 more])
* Fixed Artillery targeting remote not showing the correct ability count in the quickbar. ([https://forums.factorio.com/65310 more])
* Fixed scrolling through blueprint book with Shift+mouse wheel on macOS. ([https://forums.factorio.com/67225 more])
* Fixed Artillery targeting remote not showing the correct ability count in the qickbar. ([https://forums.factorio.com/65310 more])
* Fixed that blueprint shortcuts in quickbar linked to the library wouldn't remember their orientation. ([https://forums.factorio.com/65716 more])

== 0.17.12 ==
Date: 14.03.2019

=== Features ===

* Added pollution tab to the production statistics.

=== Minor Features ===

* Spawner tooltip (including the pollution statistics), shows distribution of biters spawn for the current evolution factor with the pollution costs.
* Added attack modifier setting into the pollution section in the map generator. This modifies how much pollution is consumed by biters attacking. (default is 50% for deathworld presets)

=== Changes ===

* Pollution generation is now shown in the x/s format both on the entity and in the item/crafting slot.
* All statistics graphs apart from electricity use smoothing now.
* The Install Mods GUI will now automatically install required dependencies.
* Added graphics option "Render in native screen resolution" on macOS to workaround performance issues due to rendering on Retina displays. ([https://forums.factorio.com/66870 more])

=== Bugfixes ===

* Added another fixing migration of consistency related to undo.
* Fixed that inserters wouldn't copy the white list/black list setting during fast-replace. ([https://forums.factorio.com/67501 more])
* Fixed that building/removing signals forced train in disabled station to move from it. ([https://forums.factorio.com/67365 more])
* Fixed that the name of the "Undo" shortcut wouldn't show up in the shortcut selection list. ([https://forums.factorio.com/67464 more])
* Fixed that the blueprint book shortcut's tooltip wouldn't show the assigned key combination. ([https://forums.factorio.com/67447 more])
* Fixed search bar focus being lost when binding it to extra mouse buttons. ([https://forums.factorio.com/67517 more])
* Fixed that shortcut bar keyboard shortcuts would appear twice in the control settings if certain mods were installed. ([https://forums.factorio.com/67433 more])
* Fixed that backspacing text covered by unclosed rich text tags could leave them at the end of the string. ([https://forums.factorio.com/67376 more])
* Fixed that technology tooltip would show "unknown key" for technologies with no description. ([https://forums.factorio.com/67489 more])
* Fixed unable to close the menu when rebinding toggle menu from ESC. ([https://forums.factorio.com/67535 more])
* Fixed that modded GUI window frames always contained header filler. ([https://forums.factorio.com/66295 more])
* Fixed save file would contain two preview screenshots. ([https://forums.factorio.com/67543 more])
* Fixed typo in decoratives.lua. ([https://forums.factorio.com/67594 more])
* Fixed that cloning assembling machines wouldn't preserve the direction for some recipes. ([https://forums.factorio.com/67583 more])
* Fixed bug with typing certain characters on alternative keyboard layouts on windows. ([https://forums.factorio.com/67552 more])
* Fixed a crash of generators whose prototype changes to not use fluid anymore. ([https://forums.factorio.com/66595 more])
* Fixed some crashes related to changes of modded fluid recipes. ([https://forums.factorio.com/67277 more])
* Fixed NPE bug when Compilatron walks over the iron patch when he's about to build miners. ([https://forums.factorio.com/67553 more])
* Fixed switching to map view when holding placeable item in cursor would make the item icon invisible. ([https://forums.factorio.com/66180 more])
* Fixed cloning rocket silos with rockets wouldn't work correctly. ([https://forums.factorio.com/67635 more])
* Fixed broken and missing support of modded underground pipe connections. ([https://forums.factorio.com/65824 more])
* Fixed not being able to use the same key for some actions. ([https://forums.factorio.com/65128 more])
* Fixed that releasing Alt before D when pressing Alt+D would cause the character to walk.
* Fixed that order of items in the circuit network did not respect group and subgroups. ([https://forums.factorio.com/67548 more])

=== Modding ===

* Internal pollution values have been normalized, and they are now roughly 60 times less compared to what they were.

=== Scripting ===

* LuaPlayer::get_active_quick_bar_page now returns 1 based index.

== 0.17.11 ==
Date: 11. 03. 2019

=== Bugfixes ===

* Fixed that the process name was set to "Main" on Linux. ([https://forums.factorio.com/67355 more])
* Fixed a crash when closing GUIs with escape in some cases. ([https://forums.factorio.com/67428 more])
* Fixed a crash when mods set repair pack speeds or entity repair speed modifiers to negative values.
* Fixed that focus-search wouldn't work in the Recipe GUI or Map Editor. ([https://forums.factorio.com/67437 more])

== 0.17.10 ==
Date: 11. 03. 2019

=== Changes ===

* Terrain generator options are preserved by the map generator GUI unless explicitly changed.
* Changed landfilling result to be tile called "landfill" instead of tile called "grass-1". It looks the same for now, but it solves some unexpected behaviour. We might give it a custom graphics later on. ([https://forums.factorio.com/67282 more]) Existing blueprints containing "grass-1" will be migrated to the "landfill" tile.
* The game will load without an error when non-essential shaders fail to compile. ([https://forums.factorio.com/65107 more])
* When a player dies in the Wave defense, the free equipment will be removed from the corpse.

=== Minor Features ===

* "Make Blueprint", "Make Blueprint Book", "Make Deconstruction Planner", "Make Upgrade Planner", "Toggle Personal Roboport", and "Toggle Exoskeleton" functions are now accessible via keyboard shortcuts.

=== Bugfixes ===

* Fixed references to nonexistent noise expressions in map gen settings would crash the game.
* Fixed a crash when trying to read Lua drop-down font style names. ([https://forums.factorio.com/67379 more])
* Fixed a crash when trying to join a Steam game fails in some cases. ([https://forums.factorio.com/67366 more])
* Fixed crash related to latency hiding and undo.
* Fixed that map generation wouldn't always update to reflect modded noise expressions.
* Fixed a crash when the open GUI target would become invalidated during the same tick as autosave starting.
* Fixed that the repaired lab showed in the bonus GUI. ([https://forums.factorio.com/67320 more])
* Fixed NPE crash when Compilatron tried to place his chest. ([https://forums.factorio.com/67153 more])
* Fixed that Control+F didn't work in the trains GUI. ([https://forums.factorio.com/66253 more])
* Probably fixed GUI not responding to user input in some situations. ([https://forums.factorio.com/66210 more])
* Fixed scaling of some of the debug info text overlay. ([https://forums.factorio.com/67172 more])
* Fixed headless server would be stuck in reset loop when trying to apply an update. ([https://forums.factorio.com/67231 more])

=== Scripting ===

* Added LuaGuiElement::select_all and select methods that work for textfield and textbox.

== 0.17.9 ==
Date: 08. 03. 2019

=== Changes ===

* Disabling station with train waiting in it doesn't force the train to departure anymore so it works as it worked in 0.16. It looked like a useful change for 0.17, but we can control train conditions by circuit network and there are some nice and simple use cases were ruined by trains being forced to departure when the stop is disabled. ([https://forums.factorio.com/65109 more])
* Changed expensive version of assembling machine 2 recipe to match the normal version better. ([https://forums.factorio.com/65570 more])

=== Minor Features ===

* Added map editor support to delete items.

=== Bugfixes ===

* Fixed pipette making error sound in latency state even though you have enough items. ([https://forums.factorio.com/67002 more])
* Fixed that technologies would sometimes disappear from the technology list when added to the research queue. ([https://forums.factorio.com/65879 more])
* Fixed problems related to circuit network connection inconsistency related to undo. ([https://forums.factorio.com/67071 more])
* Fixed NPE issue where Compilatron could destroy essential buildings. ([https://forums.factorio.com/67031 more])
* Fixed NPE crash when Compilatron tells you to pick up scrap. ([https://forums.factorio.com/66241 more])
* Fixed that he bonus GUI wouldn't show personal equipment. ([https://forums.factorio.com/65618 more])
* Fixed using special-item tags would cause desyncs. ([https://forums.factorio.com/66311 more])
* Fixed NPE crash when Compilatron tries to point at an object that doesn't exist any more. ([https://forums.factorio.com/65162 more])
* Fixed Local errors in scenarios would crash the game when viewing scenarios in the GUI. ([https://forums.factorio.com/66716 more])
* Fixed that reviving and underground belt could sometimes change it's direction. ([https://forums.factorio.com/67026 more])
* Fixed a crash when using modded recipes in furnaces with fluids. ([https://forums.factorio.com/66271 more])
* Fixed that the active-version selector in the mods GUI didn't work. ([https://forums.factorio.com/66941 more])
* Fixed that randomizing map seed didn't have any effect after an exchange string was loaded. ([https://forums.factorio.com/65555 more])
* Fixed that resources wouldn't be rendered correctly in the map preview. ([https://forums.factorio.com/66525 more])
* Fixed miscalculation of peak influence in autoplace specifications with more than 2 peaks. ([https://forums.factorio.com/67040 more])
* Layout fix related to technology gui. ([https://forums.factorio.com/66868 more])
* Fixed crash when running out of space in physical texture used for streaming. High detail textures will be evicted instead. ([https://forums.factorio.com/66563 more])
* Fixed that mod settings could get scrambled/reset when adding removing or changing mods. ([https://forums.factorio.com/66669 more])
* Fixed that you could open blueprint books/armor multiple times. ([https://forums.factorio.com/67096 more])
* Fixed that the train inactivity wait condition time was limited to 120 seconds. ([https://forums.factorio.com/66974 more])
* Fixed a crash when exiting the game through the "X" button from a tutorial. ([https://forums.factorio.com/65270 more])
* Fixed the shadows of some GUIs when circuit network window is shown. ([https://forums.factorio.com/67119 more])
* Fixed menu background image would be scaled with poor quality. ([https://forums.factorio.com/67109 more])
* Fixed crash related to beam creation when the source or target is removed in the process. ([https://forums.factorio.com/67110 more])
* Fixed a hand logic related to loading a save with different mod settings which results in to the cursor being item removed.
* Fixed being unable to clear "X"(missing blueprint) icon from the quickbar. ([https://forums.factorio.com/67114 more])
* Fixed that train two stations of the same name in the train schedule could crash the game. ([https://forums.factorio.com/67066 more])
* Fixed consistency check for signal state of train on the way. ([https://forums.factorio.com/67052 more])
* Fixed issues with pipes disconnected w/o reason. Added stricter checks for new occurrences. ([https://forums.factorio.com/67057 more])

=== Scripting ===

* Added LuaSurface::min_brightness read/write.
* Added LuaEntity::get_connected_rails(), get_rail_segment_entity(), get_rail_segment_end(), get_rail_segment_length(), and get_rail_segment_overlaps().

== 0.17.8 ==
Date: 07. 03. 2019

=== Bugfixes ===

* Fixed modded multiplayer games would incorrectly show a mod-mismatch error (again). ([https://forums.factorio.com/66957 more])
* Fixed queued GUIs didn't work correctly. ([https://forums.factorio.com/66963 more])
* Fixed that terrain selectors other than 'elevation' messed with the water/island controls ([https://forums.factorio.com/66932 more])
* Fixed PvP running on_init when it was already initialised. ([https://forums.factorio.com/66970 more])
* Fixed that replacing an underground pipe by a pipe could cause fluid mixing in a special situation. ([https://forums.factorio.com/66888 more])
* Fixed that upgrading entities with the upgrade planner would erase the last-user. ([https://forums.factorio.com/67019 more])
* Fixed a crash in the update mods GUI.
* Fixed incorrect styling in the update mods GUI in some cases.
* Fixed crash when loading a save during a cutscene when following a unit. ([https://forums.factorio.com/67022 more])

== 0.17.7 ==
Date: 06. 03. 2019

=== Bugfixes ===

* Fixed game.players[#] would be treated as game.players[tostring(#)].
* Fixed inserter/mining drill interaction indications would still render for mined-in-latency-state entities.
* Fixed inserter/mining drill interaction indications wouldn't render in some cases and would ignore ghosts in some but not all cases.
* Fixed that the game would incorrectly think some mods wouldn't be required when joining multiplayer games even though they are.
* Fixed some key bindings not working correctly until game restart. ([https://forums.factorio.com/66631 more])
* Fixed a crash when changing entity ghosts with wire connections through the upgrade planner. ([https://forums.factorio.com/66861 more])
* Fixed that the prevent-robots-from-working-because-i-am-driving-too-fast logic still wouldn't work in some cases. ([https://forums.factorio.com/66190 more])
* Fixed that highly nested recipes would freeze the game. ([https://forums.factorio.com/66626 more])
* Fixed a crash when loading saves that contain connected cliffs that will be removed due to mod migrations/removals. ([https://forums.factorio.com/66637 more])
* Fixed statistics graphs crashing when releasing shift with a tooltip active. ([https://forums.factorio.com/66910 more])
* Fixed rendering of tile transitions on Sandy Bridge iGPUs for real this time. ([https://forums.factorio.com/65628 more])
* Fixed that it was possible to add a blueprint to other player's shared blueprints. ([https://forums.factorio.com/66438 more])
* Fixed that undo was not preserving ghost entity module requests. ([https://forums.factorio.com/66638 more])
* Fixed that undo was not preserving circuit connections. ([https://forums.factorio.com/66419 more])
* Fixed that un-researching technology wouldn't update GUIs correctly. ([https://forums.factorio.com/66522 more])
* Fixed PvP scenarios created in 0.16 and loaded in 0.17. ([https://forums.factorio.com/66420 more])
* Fixed PvP script error from bad migration data checking. ([https://forums.factorio.com/66876 more])
* Fixed that blueprint that was meant to disappear on Q did not after selecting and cancelling selection. ([https://forums.factorio.com/66004 more])
* Fixed persisting tooltips in the technology gui. ([https://forums.factorio.com/66176 more])
* Fixed set_quick_bar_slot not refreshing item counts in the quickbar. ([https://forums.factorio.com/66150 more])
* Fixed layouting in train configure gui with very long station names. ([https://forums.factorio.com/66841 more])
* Fixed layouting in train configure gui with too long condition translations. ([https://forums.factorio.com/66654 more])
* Squashed labels get a tooltip with the full text in a similar fashion as buttons.
* Fixed that research queue setting wouldn't export to map exchange string properly. ([https://forums.factorio.com/65417 more])
* Fixed incorrect primary screen index in graphics options GUI.
* Fixed some cases of fluid mixing related to underground pipes.
* Fixed crash related to productivity bonus and a catalyst. (When the catalyst count covers all the ingredient count). ([https://forums.factorio.com/66882 more])
* Fixed that the reset button wouldn't update after importing a map exchange string. ([https://forums.factorio.com/66608 more])
* Fixed messed up research in the NPE ([https://forums.factorio.com/66871 more])

=== Scripting ===

* Added LuaControl::ghost_cursor read/write.

== 0.17.6 ==
Date: 05. 03. 2019

=== Changes ===

* Updated map-gen-settings.example.json to use numeric multipliers, include cliff richness, and demonstrate expression overrides. ([https://forums.factorio.com/66694 more])
* It is not possible to fast-replace pipe to ground by another that is in an orthogonal direction.
* Changed mining productivity cost to 2500 increase per level to fix that the last change was actually making it 5 times less expensive towards infinity. Lower levels are cheaper on the other hand.

=== Bugfixes ===

* Fixed of loading of saves before 0.17.
* Fixed crash related to conflicting undo in multiplayer. ([https://forums.factorio.com/65656 more])
* Fixed crash related to temporary stops and destroyed rails on the path that were already passed by the train. ([https://forums.factorio.com/65540 more])
* Fixed yet another train pathing crash. ([https://forums.factorio.com/65545 more])
* Fixed the hand logic for god-mode controller. ([https://forums.factorio.com/66619 more])
* Fixed, that the hand logic could force an item to filtered slot that doesn't match it. ([https://forums.factorio.com/66610 more])
* Fixed, that filtered inventory could ignore the hand when sorting or transferring in some cases. ([https://forums.factorio.com/65612 more])
* Fixed overly generous migration of mining productivity research. ([https://forums.factorio.com/66708 more])
* Right panel sizing fixes.
* starting_area (size multiplier) in map gen settings JSON can be represented by a number.
* Fixed crash related to removing technology from the research queue. ([https://forums.factorio.com/66790 more])
* Fixed that driving backwards in vehicles wouldn't trigger the prevent-robots-from-working-because-i-am-driving-too-fast logic. ([https://forums.factorio.com/66777 more])
* Fixed crash during startup on macOS 10.12 or older with GeForce GPU. ([https://forums.factorio.com/65145 more])
* Attempt to fix tile transition rendering on Sandy Bridge iGPUs. ([https://forums.factorio.com/66035 more])
* Fixed a performance problem related to undo in multiplayer. ([https://forums.factorio.com/66235 more])
* Fixed upgrading ghost splitters wouldn't copy the splitter settings. ([https://forums.factorio.com/65346 more])
* Fixed a couple of situations where fast replacing underground pipe could cause fluid mixing. ([https://forums.factorio.com/66085 more])
* Fixed align in the blueprint library. ([https://forums.factorio.com/66789 more])
* Fixed a crash when loading modded saves related to fluidbox removal in assembling machines.
* Fixed blueprint preview would be drawn out of its bounds. ([https://forums.factorio.com/66050 more])
* Fixed the featured technology cost for upgrade technologies when the research queue is not enabled. ([https://forums.factorio.com/66713 more]).
* Fixed that search in the technology GUI would be cancelled by selecting a new research. ([https://forums.factorio.com/66775 more])
* Fixed a crash on destroying an entity with fluid energy source. ([https://forums.factorio.com/66517 more])
* Fixed a crash when deconstructing trains with inserters trying to put into them. ([https://forums.factorio.com/66614 more])
* Fixed layout of circuit and logistic control windows. ([https://forums.factorio.com/66531 more])
* Fixed that trying to join a multiplayer game too quickly would lead to a mods-mismatch error. ([https://forums.factorio.com66834 more])
* Fixed that behemoth biters didn't have resistance to acid (as all other biters have).
* Fixed NPE saves technologies were messed up by a migration in 0.17.5. ([https://forums.factorio.com/66714 more])
* Fixed NPE issue where compi smashing a building would lead to a crash in migrated saves. ([https://forums.factorio.com/66767 more])
* Fixed that it wasn't possible to access the game menu when the game was paused in multiplayer with the technology screen open. ([https://forums.factorio.com/65223 more])

=== Scripting ===

* Added LuaItemPrototype::mapper_count read.

== 0.17.5 ==
Date: 04. 03. 2019

=== Bugfixes ===

* Fixed crash related to train waypoints and very short train paths. ([https://forums.factorio.com/66095 more])
* Fixed wrong entity info positioning when all other things in the right container are disabled. ([https://forums.factorio.com/65088 more])
* Fixed Wave defense victory not being triggered in some cases.
* Fixed Wave defense victory message being printed on every rocket launch.
* Fixed restarting the game after sync-mods-with-save would fail to auto-load some saves on Windows. ([https://forums.factorio.com/66338 more])
* Fixed PvP error when loading 0.16 versions of the scenario. ([https://forums.factorio.com/66108 more])
* Fixed selection in blueprint preview would have an offset if UI scale was not 100%. ([https://forums.factorio.com/65557 more])
* Fixed pie slice used as progress indicator in crafting queue wasn't rendering for small angles. ([https://forums.factorio.com/66079 more])
* Fixed that the /time command would give back the wrong time played.
* Fixed rendered terrain would increasingly get corrupted during movement when using 16bit rendering mode on some OpenGL drivers. ([https://forums.factorio.com/65691 more])
* Fixed player.get_quick_bar_slot causing a crash for some values. ([https://forums.factorio.com/65917 more])
* Fixed controls were lagging when application window was receiving lot of events it didn't recognize on macOS or Linux. ([https://forums.factorio.com/65179 more])
* Fixed "Wait for V-Sync" graphics option was not working on macOS 10.14 Mojave.
* Fixed crash logs were missing stack traces on macOS.
* Adjusted the Supply Challenge requirements to make sense. ([https://forums.factorio.com/66291 more])
* Fixed a crash when reviving entities through the Lua API.
* Fixed NPE crash on biter commands during rebuild quest. ([https://forums.factorio.com/66586 more])
* Fixed NPE crash during cutscene if player left entity ghosts in the starting area. ([https://forums.factorio.com/66424 more])
* Fixed NPE crash on sending biters if you plaster half the map with furnaces (yes, seriously). ([https://forums.factorio.com/66369 more])
* Fixed NPE bug where Compilatron would sometimes not continue after players put the required items in his chest. ([https://forums.factorio.com/66528 more])
* Fixed that technology slot tooltip didn't reflect the cost of the selected technology in the queue.
* Fixed NPE confusing flying text at startup. ([https://forums.factorio.com/66317 more])
* Fixed that the train passed wait condition time was limited to 120 seconds. ([https://forums.factorio.com/66043 more])
* Fixed hand not disappearing from the quickbar in some situations. ([https://forums.factorio.com/66019 more])
* Fixed a crash related to the research queue. ([https://forums.factorio.com/66172 more])
* Fixed that the research queue could show incorrect research levels. ([https://forums.factorio.com/66144 more])
* Horizontal layouting fix of the mods gui. ([https://forums.factorio.com/66217 more])
* Fixed that the island related changes in the terrain settings in map generator gui weren't updated if the island preset was preselected. ([https://forums.factorio.com/65722 more])
* Fixed that custom Lua-defined shortcuts would desync the game. ([https://forums.factorio.com/66556 more])
* Fixed a crash when player is not given when using surface.deconstruct_area(). ([https://forums.factorio.com/66426 more])
* Fixed loading of blueprints containing rail temporary stations.

=== Modding ===

* Added SelectionToolPrototype flag "nothing".
* Made resource autoplace helper functions usable from mods. ([https://forums.factorio.com/66584 more])
* Added LogisticContainerPrototype::landing_location_offset.

=== Balancing ===

* Changed mining productivity technology to add 10% in one level instead of 2%, increased the formula from 100 * level to 500 * level and removed some of the low level intermediate levels.

=== Changes ===

* Blueprinting tools are no longer shown in the quickbar filter selection. ([https://forums.factorio.com/66088 more])

== 0.17.4 ==
Date: 01. 03. 2019

=== Bugfixes ===
* Fixed crashes related to Lua errors. ([https://forums.factorio.com/66007 more])
* Fixed a crash when opening the fluid wagon GUI in the map editor. ([https://forums.factorio.com/66067 more])
* Fixed that pressing "back" on the login prompt in the other settings GUI would exit the other settings GUI. ([https://forums.factorio.com/65643 more])
* Fixed that robots could get stuck when trying to upgrade in some cases. ([https://forums.factorio.com/65816 more])
* Fixed that the tooltips for tooltip times where backwards. ([https://forums.factorio.com/65085 more])
* Fixed Lua commands wouldn't work show help correctly. ([https://forums.factorio.com/66022 more])
* Fixed portable fusion reactor and rocketry tech pre-requisites - added military science pack. ([https://forums.factorio.com/66080 more])
* Fixed uranium processing tech pre-requisites - added sulfur processing. ([https://forums.factorio.com/66060 more])
* Removed ghost buildability consistency check until we properly integrate building of ghosts into the fluid mixing prevention logic.
* Fixed crash related to train pathfinding. ([https://forums.factorio.com/65950 more])
* Fixed layouting of Map Generator gui when the preview is shown. ([https://forums.factorio.com/65959 more])
* Fixed issues with rich text tags referencing entities that have no icon.
* Fixed crash related to moving blueprints from game blueprints to player blueprints. ([https://forums.factorio.com/66091 more])
* Fixed crash related listing all players while while processing event of player being removed.
* Fixed a crash related to research that would continue even though the research queue is empty. ([https://forums.factorio.com/66057 more])
* Fixed Compilatron placing a chest on top of things. ([https://forums.factorio.com/65924 more])
* Fixed crash during quest to reactivate assembler in NPE. ([https://forums.factorio.com/66122 more])
* Fixed that script render text would scale with GUI scale. ([https://forums.factorio.com/65982 more])

=== Modding ===
* Made MiningDrillPrototype::radius_visualisation_picture tintable.

== 0.17.3 ==
Date: 28. 02. 2019

=== Changes ===
* Disabled target leading for flamethrower turrets until it can be made better. ([https://forums.factorio.com/65152 more])
* Changed train pathfinding in a way, that it can find path that ends in the same segment where it started. This worked only for the trivial case of all path of one segment before.

=== Bugfixes ===
* Fixed possible crash related to browsing in the mods gui.
* Fixed that turning off exoskeletons didn't work correctly in multiplayer.
* Fixed shaking of blueprint preview in blueprint book tooltip. ([https://forums.factorio.com/65594 more])
* Fixed the wrong detection of changed autosave interval in other settings. ([https://forums.factorio.com/65626 more])
* Fixed /help *command* would print a number instead of the help message. ([https://forums.factorio.com/65695 more])
* Fixed a crash when dying with the locomotive GUI open. ([https://forums.factorio.com/65705 more])
* Fixed a crash when using sprite variation sheets with mismatched frame counts. ([https://forums.factorio.com/65634 more])
* Fixed that the admin-only portions of the whitelist command where not localised correctly. ([https://forums.factorio.com/65792 more])
* Fixed building underground pipe between pipes with different fluids. ([https://forums.factorio.com/65607 more])
* Fixed visual direction of fluid flow. ([https://forums.factorio.com/65486 more])
* Fixed dead-dry-hairy-tree and dry-hairy sprite shifting in normal resolution. ([https://forums.factorio.com/65593 more])
* Fixed PvP error when changing enabled mods. ([https://forums.factorio.com/65652 more])
* Fixed number pad Enter key-bindings would be converted to normal Enter when restarting the game. ([https://forums.factorio.com/65568 more])
* Fixed small worms having fluid consumption. ([https://forums.factorio.com/65870 more])
* Fixed that copy-paste of fluid recipes would sometimes not reset fluid box contents. ([https://forums.factorio.com/65609 more])
* Fixed that double-clicking a technology in the tree view wouldn't start research. ([https://forums.factorio.com/65335 more])
* Fixed pipes that would sometimes be too noisy. ([https://forums.factorio.com/65670 more])
* Fixed that you could build multiple underground belts on top of each-other. ([https://forums.factorio.com/65828 more])
* Fixed tightspot level 5 was unbeatable. ([https://forums.factorio.com/65629 more])
* Added workaround for GPU accelerated texture compression producing corrupted textures. ([https://forums.factorio.com/65336 more])
* Fixed that the technology window scroll position would keep getting reset. ([https://forums.factorio.com/65160 more])
* Fixed that the current research panel would not update in multiplayer if some other player changed the research. ([https://forums.factorio.com/65185 more])
* Fixed terrain not being rendered when using OpenGL and any game overlay was enabled. ([https://forums.factorio.com/65096 more])

=== Modding ===
* Added LoaderPrototype::structure_render_layer with default value "lower-object". ([https://forums.factorio.com/65627 more])

== 0.17.2 ==
Date: 27. 02. 2019

=== Changes ===
* Reverted default renderer on Windows to Direct3D on all configurations.
* All infinite technologies have Space science pack as a pre-requisite.
* Added textual error message when player tries to clean cursor but it isn't possible as inventory is full.
* Added /unlock-shortcut-bar console command to unlock all shortcuts at once. This command does not disable achievements.
* Keyboard shortcut for in-game undo feature will default to Ctrl+W on AZERTY keyboard layouts. ([https://forums.factorio.com/65083 more])
* Control settings will revert to defaults when starting the game with pre-0.17.2 config with AZERTY keyboard layout.

=== Bugfixes ===

* Fixed Join Game through Steam Friend would fail to connect to a game with an error saying Steam Networking is disabled.
* Fixed LuaGameScript::take_technology_screenshot() would crash the game.
* Fixed a crash when trying to use async-saving when hosting multiplayer games on Windows. ([https://forums.factorio.com/65146 more])
* Fixed electric mining drill coverage area visualization was not drawn correctly. ([https://forums.factorio.com/65249 more])
* Fixed missing sprites on DirectX on GPUs supporting only feature level 10.0. ([https://forums.factorio.com/65263 more])
* Fixed that the GUI would be hidden if the game was saved and loaded while the technology GUI was open. ([https://forums.factorio.com/65274 more])
* Fixed a crash related to non gun/weapon items getting into the gun/weapon inventories. ([https://forums.factorio.com/65339 more])
* Fixed a crash when bringing up the escape menu in multiplayer while in the middle of using blueprints/deconstruction. ([https://forums.factorio.com/65256 more])
* Fixed a crash when mining ghosts built in the latency state. ([https://forums.factorio.com/65361 more])
* Fixed every incremental change of sound volume would save the full config file. ([https://forums.factorio.com/65318 more])
* Fixed that the category dropdown in the install mods GUI would only work the first time it was used. ([https://forums.factorio.com/65398 more])
* Fixed that mod thumbnails in zipped mods wouldn't show in the mods GUI. ([https://forums.factorio.com/65419 more])
* Fixed pre-requisites for the first tier of all upgrade technologies so that the required science packs are unlocked first. ([https://forums.factorio.com/65379 more])
* Fixed electric inserter technology description in the tutorial. ([https://forums.factorio.com/65229 more])
* Fixed that the undo shortcut tooltip didn't reflect latency hiding values and invalid entries filtering.
* Fixed a desync when deconstructing item request proxies in the latency state. ([https://forums.factorio.com/65420 more])
* Fixed crash related to the hand logic and switching controllers. ([https://forums.factorio.com/65330 more])
* Fixed a crash when lamp with non-electrical energy source (modded) is viewed in the blueprint preview/tooltip.
* Fixed that read-only multi-line text boxes wouldn't wrap text. ([https://forums.factorio.com/65413 more])
* Fixed that the fast and express loader entity icons had the wrong colors. ([https://forums.factorio.com/65347 more])
* Fixed that the autosave interval setting was off by one. ([https://forums.factorio.com/65373 more])
* Fixed map preview would not be cleared to black before preview is generated on some PCs. ([https://forums.factorio.com/65423 more])
* Fixed that active blueprint in a book was not preserved when using the book directly from the blueprint library. ([https://forums.factorio.com/65258 more])
* Fixed that the tutorial specific assembler was shown in the "made in in" row in the crafting queue tooltip. ([https://forums.factorio.com/65447 more])
* Fixed that the map type selection changed done by reset or changing the preset didn't update the sliders properly. ([https://forums.factorio.com/65077 more])
* Fixed a rare issue with migration of fluid mixing in a modded save. ([https://forums.factorio.com/65137 more])
* Fixed that the provided map-gen-settings.example.json contained invalid settings. ([https://forums.factorio.com/65311 more])
* Fixed that checking for updates could crash the game. ([https://forums.factorio.com/65264 more])
* Solved, that blueprint library link from quickbar appeared as an empty slot when the target blueprint wasn't available anymore and it wasn't possible to assign a new item to it.
* Fixed PvP scenario error when updating space race frame with no silos present. ([https://forums.factorio.com/65492 more])
* Fixed drawing of some wires and wire shadows ([https://forums.factorio.com/65469 more])
* Fixed a possibility to mix fluid through fast replacing / upgrading a pipe with underground pipe. ([https://forums.factorio.com/65298 more])
* Fixed drawing of some wires and wire shadows. ([https://forums.factorio.com/65469 more])
* Fixed crash when opening the map generator preview for the first time with invalid settings. ([https://forums.factorio.com/65434 more])

=== Modding ===
* Renamed EntityPrototypeFlag "hide-from-bonus-gui" to "hidden" and made it also hide entities from the made in property of recipe tooltips.

== 0.17.1 ==
Date: 26. 02. 2019
=== Modding ===
* Added shortcut bar shortcut type that fires Lua events, for use in mods
=== Scripting ===
* Added LuaPlayer::is_shortcut_toggled, LuaPlayer::is_shortcut_available, LuaPlayer::set_shortcut_toggled, LuaPlayer::set_shortcut_available
* Added on_lua_shortcut event.
=== Bugfixes ===
* Missing description.json in the campaign folder results into the folder being ignored instead of a crash.
* Fixed crash when trying to rotate quickbars with a controller that doesn't have it.
* Fixed crash when trying to open surface map generation settings.
* Fixed possible crash related to copy paste and multiplayer.
* Fixed it wasn't possible to use capital 'Z' in save name. ([https://forums.factorio.com/65075 more])
* Fixed the infinity chest graphics.
* Fixed that the boiler didn't rotate in blueprints.
* Fixed that the bait chest showed in the upgrade planner.
* Fixed high CPU usage when using steam networking.

== 0.17.0 ==
Date: 26. 02. 2019
=== Major Features ===
* New quickbar (more in Gui section)
* Added shortcut bar that allows quick access to certain game features, such as toggling alt mode, creating blueprints, or turning off personal roboport
* New gui style with final version of some parts of the GUI (More in Gui section)
* Added clipboard functionality. (Control + C, Control + X, Control + V activate appropriate tools) Shift + mouse wheel allows to cycle the clipboard history.
* Added undo functionality (Control + Z). Supports manual entity building and by blueprints and manual mining and usage of deconstruction planner.
* Reworked the Map Editor so it's now part of the standard game and can be toggled at will using the '/editor' command.
* Support for mod synchronisation when joining multiplayer game. Works as long as the used mods are on the mod portal.
* Fight changes. Enemy projectiles are dodgeable and slowdown/damage the target over time. They also leave splashes on ground that have the same effect.
* Rich text tags. These tags can be used almost anywhere: Chat, station names, save names, custom ui and probably a few places we didn't think of.
** They allow changing color, font, images and location/blueprint/armor/station/locomotive linking through chat. (More in features)
* Fluid mixing prevention. Actions that fail as they would lead to fluid mixing (like building a pipe, changing recipe, rotating etc.) produce an error message as flying text.
* Replaced First steps campaign with Introduction campaign, available from the Start campaign menu.
=== Features ===
* Trains can be blueprinted and deconstructed.
* Trains can be given temporary stations (by Control+clicking the map). Temporary station is automatically removed once the train departures from it.
* Train stops without conditions work as waypoints. (the train doesn't stop at those)
* Added Passenger present and Passenger not present wait condition to the train conditions.
* If building of entity/blueprint fails, the reason of it is pinged as flying text.
* Map pings. Ctrl+Alt+click on the map to show a ping in all players maps at that location.
* Basic image tags format is [img=<image path>] where image path can use item, entity, technology, recipe, item-group, fluid tile, virtual signal achievement or utility icon.
** For example [img=item/iron-plate] or [img=item.iron-plate]. The "." instead of "/" usage is to make it usable in save names.
** Additionally, items/entities/technologies/recipe/item-group/fluid/tile/virtual signal or achievement can be linked directly by [item=iron-plate], [recipe=iron-plate], or [entity=small-biter] to provide tooltip for the appropriate object.
* Blueprint/special item tags.
** Shift clicking the icon in chat will create an item and place it in the cursor.
** Format is [special-item=blueprint string], eg: [special-item=0eNp1jtEKwjAMRX9l5rnCxkShvyIi3YxboU1Lm4lj9N9N54sv5iFwL/eeZIPBLRiTJQa9gR0DZdDXDbKdyLjq8RoRNFhGDwrI+Ko4GcoxJD4O6BiKAksPfIPuyk0BElu2+CXtYr3T4gdMEvjHUBBDllqgelVQrYJVdqnE/br+eVaBM1ITb0bnQvNMwTc8YzPOhiZ0YTpI5oUp78BL33YnmbY/l/IBb4pSQQ==].
** These tags also work with deconstruction and upgrade planners.
* Map ping tags: Created by shift-clicking the ground/map when the chat is open. Format is [gps=x,y], eg [gps=10,30] will show a map ping in all players maps at location 10,30.
** Clicking the icon in chat will open the map on the specified location.
* Font tags: Format is [font=debug-mono]mono text[/font].
* Color tags: Format is [color=1,0,0]red text[/font]
* Fast replacing pipes by pipes to ground similar to underground belts.
* When multiple versions of the same mod are installed you can select which version you want to use.
* The sync mods with save/multiplayer game feature can now sync mod startup settings as well as mods.
* Added support to import and export permissions.
* Closing opened items (blueprint books/armor) now remembers what GUI you previously had open.
* Filter inserters can be set to whitelist or blacklist filters.
* Added belt immunity equipment.
* Added upgrade planner.
* Added steam networking support for steam users.
* Added RGB support for Logitech hardware.
* Robots can blow up cliffs.
* Wave defense scenario has been reworked to support multiple rounds and a procedurally generated map.
* Added a research queue that becomes available after the player has finished the game by launching a rocket with satellite.
=== Minor Features ===
* Warning icon for automated trains that are out of fuel.
* Added 250 and 1000 hours precision intervals into statistics.
* Using deconstruction planner is incorporated in the latency hiding.
* Changed personal roboports so they won't send construction robots if you're driving in a vehicle that they can't keep up with or if in a train in automatic mode.
* Added an option to ignore mouse events when using accessibility zoom feature on macOS.
* Added support to change multiplayer config settings runtime.
* Added support to edit the whitelist, banlist, and admin list when hosting a multiplayer game.
* Added the Admin GUI (openable through /admin in the console) to manage multiplayer players.
* Landfill can be built by robots and be included in blueprints.
* Blueprint items taken from blueprint library will not move to player inventory when Q is pressed, but can be moved to any slot explicitly. (Same as with clipboard items)
* When selecting any item to the cursor from some of the player inventories. As long as the item is being held, hand icon is shown on the slot it was taken from. The hand prevents any other item to be inserted into the slot as long as the player cursor isn't cleared.
* When holding radar in cursor, area covered by existing radars is also highlighted on minimap.
* Configurable (in gui), the count of rolling stocks shown in the train visualization.
* Added two levels of shallow water tiles (only placed by map editor, not generated). Enemies and vehicles can travel over shallow water.
=== Graphics ===
* New graphics for:
** accumulator
** biters, spitters, worms, spawners
** chests
** electric poles and substation
** map edge transitions
** rocket silo
** transport belts, underground belts, splitters and transport belt circuit connector
** trees
** turrets (gun, flamethrower and laser)
** walls and gates
* laser turrets, personal laser defense and distractor robots now use new laser beams.
* Highlighting inserters that would interact with selected/previewed entity.
* Showing shield bars above health bar for relevant entities.
* Single vertical pipe is shorter.
=== Gui ===
* New final versions of several important GUI screens (Quick bar, Train Schedule, Load/Save Game, Settings, Map Generator, Research, Mods)
** Other screens than the mentioned ones (more than 100) have inconsistencies and will be updated in future minor updates.
* The quickbar is no longer an inventory, instead it can only hold shortcuts it items in inventory or blueprint library.
** The quickbar now has 10 pages of shortcuts.
** Player inventory increased by 20 slots to compensate. Toolbelt research further increases the player inventory.
* In the map, station and tag selection is now visualized by the standard Factorio selection box graphics instead of highlighting.
* Added interface option: When selecting a buildable item from the quickbar or when using the pipette tool, if you have no items of that type, a ghost will be placed in the cursor instead.
* When something is not buildable (manual or blueprint building), the reason of why it isn't buildable is shown as flying text over the cursor when the build is attempted.
* Only compatible results of a furnace are manually placeable in the result slot. (Mainly to avoid confusion of new players)
=== Optimisations ===
* Modernized and optimized rendering backend. The game now uses DirectX 11 or OpenGL 3.3 Core and requires DirectX 10 class graphics card.
* DirectX backend doesn't keep backup of all sprites in RAM anymore.
* Added high quality texture compression to reduce amount of video memory consumed by the game and increase overall rendering performance.
* Added texture streaming so that adding more sprites does not necessarily increase GPU requirements.
* Improved game startup performance when using a large amount of technologies with deep dependency trees (it's now 67,000 times faster).
* Optimized rendering of logistic overlay when zoomed in to map. ([https://forums.factorio.com/60659 more])
* Optimized rendering of turret ranges when zoomed in to map. ([https://forums.factorio.com/58991 more])
=== Changes ===
* Resource generation changed significantly:
** The starting area contains only iron, copper, coal and stone, in very predictable amounts. Uranium and oil are excluded from the starting area.
** Resource generation settings now have a much more dramatic effect. Increased the number of steps for each setting.
** Ore patches are slightly less frequent but richer.
** There will be a more balanced amount of resources within a large enough region.
** Many other small tweaks.
* Biter generation changed significantly:
** Biter richness slider removed, biter placement is only configured by size and frequency settings.
** Biter generation settings now have a much more dramatic effect. Increased the number of steps for each setting.
** Biter bases will increase in size, frequency and number of worms depending on the distance from player spawn.
** Worm size increases depending on the distance from player spawn.
** Small biter bases are now closer to the player spawn.
** At large distances from player spawn, biter base frequency is lower than before but biter bases are larger.
** Other small tweaks.
* Terrain generation changed significantly:
** Water is generated as large lakes instead of swamps.
** Tile generation improved. Tile placement respects biomes better.
** More predictable cliff placement.
** Better controls in the map generator GUI for water, tiles and cliffs.
* New map terrain type selectable: Island. Launch the rocket with only a limited amount of resources available on the map.
* Default resolution of the game is now 1920x1080.
* Increased player reach from 6 to 10.
* Inserters are putting science packs to the lab even when there is no research in progress or when the research doesn't need that particular pack.
* Default_request_amount removed in all places where it was used. Default logistic request is 1 stack, unless changed by the setting "Default request is 1".
* All personal equipment stack sizes changed to 20.
* Placing a tile will now clear any tile ghosts at that position. ([https://forums.factorio.com/59721 more])
* It is allowed to use unicode characters in save names.
* Recipes that have more ingredients than the assembling machine allows are now shown as red instead of not present when selecting the recipe.
* When the "Made in" row is shown in the recipe tooltip, player icon is added to the list when it is craftable by player.
* Increased ghost time to live of ghosts from 1 hour to 1 week.
* Since the catalysts have been tweaked, the kovarex enrichment process can now be used together with productivity module.
* Tile construction jobs are being handled by robots separately from entity building jobs, to prevent entity ghosts not being built due to large number of tile ghosts.
* Switched key bindings from key codes to scan codes. This solves an issue with bad default key bindings on layouts that are not similar to US QWERTY (ie. AZERTY).
* Armor no longer uses durability and all armor now has a stack size of 1.
* Manually putting modules into machines that are requesting modules from the logistic network will reduce the modules requested.
* Increased maximum train stop length from 50 to 100 characters so it can fit at least 3 tags in most cases.
* Items consumed by hand crafting are counted in item production statistics.
* Added --disable-migration-window command-line option to disable the "migrated content" gui.
* Removed tile properties debug overlay.
* Command-line map preview generator now shows biter nests.
* Items sent in a rocket are counted in item production statistics. ([https://forums.factorio.com/62606 more])
* Removed pickaxes and replaced them with research effects.
* Removed Wood from the game (And raw wood renamed to Wood).
* Added rotation smoothing to biters.
* Chests and wooden power poles are no longer usable as fuel.
* Burner efficiency is set to 100% for all entities and fuel value is halved to simplify calculations. This should not change game balance.
* Removed the hardness/mining power mechanics, we just have a mining speed and mining time now.
* Manual mining speed times of various entities will differ a bit, but probably not in a noticeable way.
* Stone and other ore mining speed has been unified to be 1 (apart uranium ore, which is 2 and shown as 200% mining time)
* Mining drill speed is now shown in the form of <x>/s (0.25/s for burner mining drill, 0.5/s for electric mining drill), the relative mining speeds of the mining machines have been decreased a little so the numbers are rounded nicely (0.28 -> 0.25 and 0.525 -> 0.5).
* Renamed the whitelist and banlist to server-whitelist and server-banlist.
* Added server-adminlist that's used to determine which people are admins when hosting any multiplayer game. This is synced both ways when hosting any game.
* Removed "admins" from the multiplayer server-settings file - they're now handled through server-adminlist.
* "Z" (drop item) will drop single items into what ever entity is selected instead of only dropping on the ground.
* Stickers can by applied onto cars and tanks now.
* Changed the chat gray-out mechanism. It always greyed-out after 5 seconds to 70% alpha, and then stayed depending on the setting. Now it stays 100% and only greys out away in the last 2 seconds.
* Placing entities or paths removes tree stumps and biter corpses.
* Removed New Hope campaign.
=== Balancing ===
* Technology pre-requisites tweaked so the unlocked item(s) always have all the ingredients already unlocked as well. This means many small changes.
* Science pack names changed:
** Science pack -> Automation science pack
** Science pack 2 -> Logistic science pack
** Science pack 3 -> Chemical science pack
** High-tech science pack -> Utility science pack
** Military, Production and Space science pack names remain the same.
* Science pack recipes changed:
** Military science pack now requires 1x Piercing rounds magazine, 1x Grenade, 2x Wall.
** Chemical science pack now requires 3x Advanced circuit, 2x Engine unit, 1x Solid fuel.
** Chemical science pack now crafts in pairs.
** Production science pack now requires 1x Electric furnace, 1x Productivity module, 30x Rail.
** Production science pack now produces in groups of 3. Crafting time rescaled to match.
** Utility science pack now requires 2x Processing unit, 1x Flying robot frame, 3x Low density structure.
** Utility science pack now produces in groups of 3. Crafting time rescaled to match.
* Some technologies more clearly split between Production and Utility science packs:
** Production science pack:
*** Effect transmission
*** All level 3 modules
*** Kovarex enrichment process & Nuclear fuel reprocessing
*** Worker robot capacity 2
** Utility science pack:
*** Logistic system
*** Worker robot speed 3
*** Military 4 and weapon unlocks/upgrades
*** Power armor mk2 and Portable fusion reactor
** Both Production and Utility science packs are required only for Rocket silo, Atomic bomb and some high-tier upgrades.
* Every science pack now has a technology to unlock it. Some technology prerequisites changed slightly. Space science pack technology unlocks the Satellite.
* Rocket fuel, Low density structure and Rocket control unit are unlocked by their own technologies.
* The game is won by launching a rocket, the Satellite is only for getting Space science packs.
* Swapped sorting order of Military science pack and Chemical science packs because Military science pack does not need oil.
* Nuclear power technology split to Uranium processing and Nuclear power.
* Nuclear fuel reprocessing technology cost reduced from 1500 to 50.
* Lubricant technology added (pre-requisite for Electric engine and Logistics 3)
* Fast and Filter inserters are unlocked by their own technology with a pre-requisite of Electronics.
* Automation 2 is a pre-requisite for Fluid handling. (Assembling machine 1 can't handle fluids)
* Engine is a pre-requisite for Fluid handling. (Pump needs Engines to craft it)
* Pump is now unlocked by Fluid handling. (was Engine)
* Fluid handling is a pre-requisite for Oil processing.
* Item spacing on transport belts changed from 0.28 tiles to 0.25 tiles, giving a transport belts throughput of 15/30/45 (basic/fast/express) items per second.
* Iron plate, copper plate and stone brick crafting time reduced from 3.5 to 3.2, steel plate crafting time reduced from 17.5 to 16.
* Coal liquefaction now produces 90 Heavy oil, 20 Light oil and 10 Petroleum gas, consuming 25 Heavy oil, 10 Coal and 50 Steam. (Gaining much more Heavy oil, less Light oil and Petroleum gas)
* Low density structure now requires 2x Steel plate, 20x Copper plate, 5x Plastic bar.
* Low density structure crafting time reduced from 30 to 20.
* Medium and Big power pole recipes now use iron sticks.
* Train stop recipe now uses iron sticks.
* Programmable speaker recipe now uses iron sticks.
* Lamp recipe iron sticks ingredient changed to copper cables.
* Defender capsule recipe now requires flying robot frames.
* Rebalanced assembling machine 1,2 and 3 power consumption and pollution - higher tiers eat more power, but produce less pollution.
* Assembling machine 2 recipe changed to require 2x Steel plate instead of 9x Iron plate.
* Automation 2 now requires Automation and Logistic science packs.
* Chemical plant crafting speed has been changed to 1. Some chemical plant recipes now take less time.
* Centrifuge crafting speed changed to 1.
* Portable solar panels have Modular armor as pre-requisite.
* Portable solar panel power output changed from 10kW to 30kW, recipe tweaked to require less Solar panels but more Advanced circuits.
* Low-tier personal equipment has Portable solar panels as a pre-requisite so you could possibly utilize the equipment when it is unlocked.
* Some high tier personal equipment (Energy shield mk2, Battery mk2, Personal laser defense and Discharge defense) have Power armor technology as pre-requisite.
* Some high tier equipment recipes now require Low Density Structures. (Energy shield mk2, Battery mk2, Roboport mk2, Portable fusion reactor, Power armor mk2, Personal laser defense)
* Locomotive fuel consumption doubled.
* Relative fuel value of nuclear fuel doubled.
* Relative fuel value of rocket fuel decreased by 10.6%, relative value of solid fuel decreased by 4%.
=== Combat Balancing ===
* All military damage/shooting speed upgrade technologies merged into 7 technologies:
** Physical projectile damage 1-6 + infinite
*** level 1-4: bullets, gun turrets, shotgun shells
*** level 5+: previous levels and cannon shells
** Refined flammables 1-6 + infinite
*** flamethrower turret, handheld flamethrower
** Stronger explosives 1-6 + infinite
*** level 1: grenades
*** level 2: previous level and land mines
*** level 3: previous levels and rockets
** Energy weapons damage 1-6 + infinite
*** level 1-3: laser turrets, personal laser defense
*** level 4: previous level and distractor robots
*** level 5+: previous levels and destroyer robots
** Weapon shooting speed 1-7
*** affecting: bullets, gun turrets, shotgun shells, tank cannon shells, rockets
** Laser turret shooting speed
** Artillery shell shooting speed
** Artillery shell range
* Personal laser defense damage reduced, power consumption reduced and it is now influenced by Laser and electric beam intensity upgrades.
* Modular Armor technology pre-requisite changed from Modules to Advanced Electronics.
* Power Armor Mk2 technology pre-requisite changed from modules to Military 4.
* Power Armor Mk2 recipe changed from 5x level 3 to 25x level 2 modules (to avoid requiring Production science pack) and added electric engine units.
* From the start maximum follower count is 5 instead of 1. Level 3 of maximum follower count gives +5 instead of +10 to compensate.
* Atomic bomb recipe now requires Rocket control units instead of Processing units.
* Behemoth worm added.
* Worms and spitters use new "stream" attack now.
** Attacks predict target position and shoot there.
** Flamethrower turret now predicts target position as well.
** Acid splashes are created on the ground, dealing damage and slowing.
** Slow effect received from different spitter/worm tiers stacks.
** Worm shooting range is generally longer.
** Rocket launcher range increased from 22 to 36 to outrange medium worms.
** Worm and behemoth spitter attacks are large enough to damage neighbouring buildings.
** All enemies have 100% acid resistance.
* Changed spawner pollution absorption logic so that all the pollution on a chunk doesn't build up un-spent in a single spawner.
* Removed damage bonus of tank machine gun.
=== Bugfixes ===
* Fixed that canceling production in assembling machine did return the products in progress.
* Fixed biters were unable to run against movement of belts.
* Tutorial GUI updates correctly after finishing a tutorial. ([https://forums.factorio.com/55010 more])
* Chest GUI updates correctly when changed indirectly. ([https://forums.factorio.com/55194 more])
* Changing train mode by a script updates the train GUI. ([https://forums.factorio.com/20316 more])
* Fixed that tertiary was spelled "terciary" in the usage_priority. ([https://forums.factorio.com/58317 more])
* Fixed construction robots would not give up module delivery when they didn't manage to get any modules. ([https://forums.factorio.com/59483 more])
* Fixed issues with syncing mods to saves, when you don't already have the mod downloaded. ([https://forums.factorio.com/59271 more])
* Entities affected by beacons now only show effect sources/receivers that have an effect. ([https://forums.factorio.com/60064 more])
* Fixed furnaces wouldn't respect recipe module limitations correctly. ([https://forums.factorio.com/60975 more])
* Fixed a crash when migrating blueprint book inventory sizes while they're in assembling machines that are being removed due to migration. ([https://forums.factorio.com/61001 more])
* Fixed character.direction read didn't work correctly. ([https://forums.factorio.com/61039 more])
* Fixed a crash when removing mods that add/change rolling stock entities. ([https://forums.factorio.com/61048 more])
* Fixed script error in construction bot tutorial when deconstructing area. ([https://forums.factorio.com/61045 more])
* Fixed Lua API methods to insert items didn't work correctly for entities that can hold items above the stack limit. ([https://forums.factorio.com/59872 more])
* Fixed that the closing sound of other GUIs was too loud when the technology GUI popped up when a research finished. ([https://forums.factorio.com/61049 more])
* Fixed that layered icons using shift wouldn't render correctly. ([https://forums.factorio.com/60327 more])
* Fixed that running out of disk space could crash the game in some cases. ([https://forums.factorio.com/61161 more])
* Fixed burner energy sources wouldn't always be able to output the full energy amount. ([https://forums.factorio.com/61174 more])
* Fixed that transport belt circuit conditions wouldn't copy correctly in blueprints sometimes. ([https://forums.factorio.com/61218 more])
* Fixed that limited/limiting upload speed could lead to an exponential soft lock in the upload process. ([https://forums.factorio.com/61281 more])
* Fixed a desync related to cars on belts. ([https://forums.factorio.com/61304 more])
* Fixed that crafting machines could be rotated diagonally using scripts. ([https://forums.factorio.com/61717 more])
* Fixed that tooltips of unlocked recipes in technology preview didn't have the "made in" info even if it is not craftable by the player.
* Fixed recipes that consumed or produced > stack size of some item didn't work correctly.
* Fixed that game.reload_script() could cause desyncs when used in multiplayer.
* Fixed LuaScript::get_event_handler() didn't handle large numbers correctly. ([https://forums.factorio.com/61752 more])
* Fixed AutoplaceSettings map_gen_settings didn't always work when defined through script. ([https://forums.factorio.com/61754 more])
* Fixed a crash when using LuaEntity::get_train_stop_trains(). ([https://forums.factorio.com/61743 more])
* Fixed a crash when using LuaGameScript::create_entity() related to making ghosts of ghosts. ([https://forums.factorio.com/61605 more])
* Fixed setting entity healing_per_tick negative resulted in invincible entities. ([https://forums.factorio.com/61492 more])
* Fixed that shadows wouldn't always render in the train camera. ([https://forums.factorio.com/61286 more])
* Fixed health bars on large entities wouldn't render correctly. ([https://forums.factorio.com/61495 more])
* Fixed trains would collide with item-requester-proxy. ([https://forums.factorio.com/61842 more])
* Fixed train GUI buttons would lose too much quality graphics quality was set to Extra low. ([https://forums.factorio.com/61618 more])
* Fixed a bug related to mining drills with > 100% productivity. ([https://forums.factorio.com/61440 more])
* Fixed invalid optional dependencies wouldn't be highlighted correctly. ([https://forums.factorio.com/61951 more])
* Fixed a crash when reading player.vehicle during the driving driving changed state event when triggered by the vehicle dying. ([https://forums.factorio.com/61942 more])
* Fixed that beams would render 1 tile above their location when using a position source. ([https://forums.factorio.com/62471 more])
* Fixed furnaces with input items and output fluids could get deadlocked. ([https://forums.factorio.com/62434 more])
* Fixed when player teleported, renderer would draw all tiles between old and new position. ([https://forums.factorio.com/62635 more])
* Fixed that frame count limits weren't enforced and would lead to a crash in several places. ([https://forums.factorio.com/62648 more])
* Fixed a crash when the player port respawned a character without a connected player ([https://forums.factorio.com/62707 more])
* Fixed that the market did not show the prices for some offers ([https://forums.factorio.com/62682 more])
* Fixed that the "save replay" button would always show on the game finished screen even when it wouldn't work. ([https://forums.factorio.com/62733 more])
* Fixed that filters would get copied between storage chests and requester chests. ([https://forums.factorio.com/61219 more])
* Fixed error message given when loader entity prototype was defined with too many filters. ([https://forums.factorio.com/62839 more])
* Fixed that fast replacing a train stop did not copy the name or color. ([https://forums.factorio.com/62966 more])
* Ghost rails are now also considered when auto-selecting rail signal direction. ([https://forums.factorio.com/58655 more])
* Fixed that the high-resolution car animation would shake. ([https://forums.factorio.com/62454 more])
* Fixed errors in the mod settings stage wouldn't prompt to disable the erroring mod(s). ([https://forums.factorio.com/62447 more])
* Fixed that crafting machines didn't work correctly with non-square bounding boxes. ([https://forums.factorio.com/63027 more])
* Fixed that pasting train schedules did not dispatch trains waiting at a station that is not part of the new schedule. ([https://forums.factorio.com/61143 more])
* Fixed possible crash when rendering a fish due to bad migration on fish prototype change. ([https://forums.factorio.com/63515 more])
* Fixed that LuaGuiElement::zoom on minimaps would be rendered as zoom * 32.
* Fixed crash when detecting VRAM size on macOS. ([https://forums.factorio.com/63770 more])
* Fixed LuaEntity::infinity_filters write didn't work. ([https://forums.factorio.com/63954 more])
* Fixed that setting active on combinators would lead to desyncs. ([https://forums.factorio.com/63335 more])
* Fixed that shift+click building blueprints didn't work correctly regarding tiles. ([https://forums.factorio.com/63849 more])
* Fixed that construction robots could get stuck trying to repair things. ([https://forums.factorio.com/63800 more])
* Fixed inventory highlights didn't work correctly when the game was paused while active. ([https://forums.factorio.com/64047 more])
* Fixed a crash related to trains being forced to re-path when a stop is disabled. ([https://forums.factorio.com/63900 more])
* Fixed that wire distance was ignored in some cases when connecting non-electric-pole entities. ([https://forums.factorio.com/62146 more])
* Fixed that equipment grids wouldn't fit on screen if too large. ([https://forums.factorio.com/61662 more])
* Fixed that the SelectSignal GUI wouldn't sort mixed-type signals correctly. ([https://forums.factorio.com/62463 more])
* Fixed map generator would align entities to grid differently than manual building. ([https://forums.factorio.com/63408 more])
* Fixed sprites in 16-bit depth per channel PNG would load as empty images on macOS. ([https://forums.factorio.com/64105 more])
* Fixed that furnaces with mixed input could get stuck. ([https://forums.factorio.com/61406 more])
* Fixed text duplication on research completion in the bonus GUI. ([https://forums.factorio.com/64608 more])
* Fixed that LuaSurface::find_entities_filtered{position} wouldn't find entities with zero-sized bounding boxes. ([https://forums.factorio.com/63270 more])
* Fixed that mod console commands would treat every command with the same help key as aliasing each other. ([https://forums.factorio.com/64581 more])
* Fixed LuaGameScript::remove_path would log an error if path didn't exist. ([https://forums.factorio.com/64873 more])
* Fixed cars and tanks had a slightly smaller collision box when not facing north. ([https://forums.factorio.com/63842 more])
* Fixed inserter interaction with cars depended on rotation and on distance from map origin. ([https://forums.factorio.com/62854 more])
* Fixed "InRangePredicate only accepts direction without diagonals" error. ([https://forums.factorio.com/62375 more])
* Fixed when teleporting all tiles between old and new position would be rendered, causing performance problems. ([https://forums.factorio.com/62635 more])
* Force space between spawners and worms in biter bases so they don't get stuck so much.
* Fixed trivial-smoke would be rendered for some time after its lifetime ended.
=== Modding ===
* Added a new entity type "infinity-pipe" that automatically adds/removes fluid from itself; similar to the infinity-chest.
* Added a new entity type "heat-interface" that automatically sets its own temperature.
* Added "void" energy_source type which makes any entity using the type not require power.
* Added CraftingMachinePrototype::show_recipe_icon which changes if the recipe icon is shown in alt-mode.
* Added "stop" AI command, which tells the unit to just stop moving where it is. Takes a "ticks_to_wait" parameter, after which it returns to normal.
* Added LuaGuiElement type "list-box".
* Added Entity prototype flags "no-automated-item-removal" and "no-automated-item-insertion".
* Added support for hidden optional dependencies via '(?) mod-name'.
* Added SelectionToolPrototype flags "not-same-force", "friend", and "enemy".
* Added SelectionToolPrototype optional filters: entity_filters, entity_type_filters, tile_filters, entity_filter_mode, and tile_filter_mode.
* Added SelectionToolPrototype optional filters: alt_entity_filters, alt_entity_type_filters, alt_tile_filters, alt_entity_filter_mode, and alt_tile_filter_mode.
* Added support to set wire_count on wires to define how many items are needed to connect 2 entities.
* Added UnitPrototype::ai_settings, which allows overriding default biter behavior.
* Added a spectator controller type that can view anything but can't change anything.
* Added GeneratorPrototype::burner to allow making an entity that burns fuel and produces power.
* Added ticks_to_wait parameter to wander ai command.
* Added Entity prototype property "next_upgrade".
* Added support to set draw_copper_wires and draw_circuit_wires for any entity that uses wires.
* Added optional "min_working_temperature" and "default_temperature" to heat buffer prototype.
* Added optional technology prototype property "hidden".
* Added optional fluid prototype property "hidden".
* Added "fluid" energy_source type can be used for both fuel-value based fluids, and heat capacity based fluids configured the same was as the generator entity.
* Added ReactorPrototype::scale_energy_usage to allow making a heat source that stops consuming fuel when max temperature is reached.
* Added EnemySpawnerPrototype::min_darkness_to_spawn and max_darkness_to_spawn.
* Added optional beam prototype properties random_end_animation_rotation and transparent_start_end_animations.
* Added rotation_speed value to Unit prototype.
* Added support for arbitrary non-circular references to named noise expressions.
* Added "spot-noise" noise function.
* Added "if-else-chain" and "literal-boolean" noise expression types.
* Added "cutscene" controller.
* Added "speech-bubble" entity.
* Added ResourceEntityPrototype::randomize_visual_position.
* Added EquipmentGridPrototype::locked.
* Added DamageType::hidden.
* Added optional draw_cargo property to construction robot and logistic robot prototypes.
* Added optional fluid_product to production achievement prototypes.
* Added UnitPrototype::affected_by_tiles.
* Added LuaStyle::stretch_image_to_widget_size, only applies to "sprite" widget styles.
* Added optional EntityPrototype::map_generator_bounding_box.
* Added EntityPrototypeFlag "not-upgradable".
* Added EntityPrototypeFlags "no-copy-paste" and "not-selectable-in-game".
* Added ItemPrototypeFlags "only-in-cursor", "not-stackable", "can-extend-inventory", "primary-place-result" and "mod-openable".
* Added BeamPrototype::target_offset and random_target_offset.
* Added TilePrototype::tint. Tile tint is packed to RGB 565 without alpha.
* Added "mouse-cursor" definitions for overriding system mouse cursor in selection tools.
* Changed radars so they support dynamic energy source types.
* Changed ItemWithInventoryPrototype flag "when_manually_filtered" to "when-manually-filtered".
* Changed SelectionToolPrototype flag "matches-force" to "same-force".
* Changed the maximum number of surfaces from 255 to 4,294,967,295.
* Changed migration scripts so they run in the context of the mod that created them.
* Changed TilePrototype::decorative_removal_probability default value to 0 (it was 1).
* Changed ReactorPrototype::burner to ReactorPrototype::energy_source to allow heat sources with alternate energy types.
* Changed ElectricEnergyInterfacePrototype::enable_gui to gui_mode.
* Changed EnemySpawnerPrototype::result_units to support any type of entity.
* Changed recipes to support having no results by setting results = {}.
* Lua scripts can now use require("__mod-name__.file") syntax.
* AutoplaceSpecifications can now be defined in terms of probability_expression and richness_expression as an alternative to peaks.
* property_expression_name values can be numeric constants.
* All autoplace controls are now available as noise expression variables.
* energy_per_movement and energy_per_rotation of inserter is now specified in energy format (aka "5KJ") instead of just a number.
* Increased limit for size of spritesheet to 8196px (regardless of sprite resolution settings). Maximal size of single sprite is 2048px in normal resolution and 4096px in high resolution. Smaller spritesheets can utilize parallel decompression better.
* Removed the "default-" prefix from core NamedNoiseExpressions; property_expression_names in MapGenSettings simply override the expression named by the key.
* Removed ItemPrototypeFlags "goes-to-main-inventory" and "goes-to-quickbar".
=== Scripting ===
* Added LuaRendering accessed via the lua global "rendering".
* Added LuaEntity::get_infinity_pipe_filter() and set_infinity_pipe_filter().
* Added LuaEntity::recipe_locked read/write for assembling machines.
* Added LuaRailPath.
* Added LuaTrain::path read.
* Added LuaEntity::connected_rail read.
* Added previous_direction to the on_player_rotated_entity event.
* Added LuaItemStack::deconstruct_area() and cancel_deconstruct_area().
* Added LuaSurface::deconstruct/cancel_deconstruct optional parameters skip_fog_of_war and item.
* Added LuaEntity::clone().
* Added LuaSurface::clone_area().
* Added LuaSurface::clone_entities().
* Added LuaGameScript::auto_save().
* Added LuaEntity::neighbours support for power switches, wall-connectable entities, and reactors.
* Added LuaFluidBoxPrototype.
* Added LuaEntityPrototype::fluidbox_prototypes read.
* Added LuaGameScript::take_technology_screenshot().
* Added LuaSurface::clear().
* Added LuaSurface::solar_power_multiplier read/write.
* Added on_pre_surface_cleared and on_surface_cleared events.
* Added on_pre_chunk_deleted and on_chunk_deleted events.
* Added on_chart_tag_added, on_chart_tag_modified, and on_chart_tag_removed events.
* Added LuaGameScript::styles read.
* Added LuaEntity::crafting_speed read.
* Added LuaTrain::max_forward_speed and max_backward_speed read.
* Added on_train_schedule_changed event.
* Added LuaForce::previous_research read/write.
* Added LuaSurface::find_decoratives_filtered().
* Added LuaEntity::inserter_filter_mode read/write.
* Added LuaEntity::neighbour_bonus read.
* Added LuaEntityPrototype::neighbour_bonus and neighbour_collision_increase read.
* Added LuaEntityPrototype::container_distance, belt_distance and belt_length read.
* Added LuaGameScript::table_to_json() and LuaGameScript::json_to_table().
* Added events on_player_banned, on_player_kicked, and on_player_unbanned.
* Added event on_rocket_launch_ordered.
* Added LuaItemPrototype::wire_count read.
* Added LuaRecipePrototype::main_product read.
* Added LuaEntity::get_fluid_count(), get_fluid_contents(), remove_fluid(), insert_fluid(), and clear_fluid_inside().
* Added LuaEntity::silent_revive().
* Added LuaFluidBox::get_prototype().
* Added LuaSurface::request_path().
* Added LuaGameScript::reload_mods().
* Added on_player_toggled_alt_mode, on_player_repaired_entity, and on_player_fast_transferred events.
* Added on_game_created_from_scenario event.
* Added on_surface_renamed event.
* Added on_ai_command_completed event, which can be used to detect command completion and failure/success.
* Added "pathfind_flags" parameter to "go_to_location" AI command.
* Added "radius" and "wander_in_group" parameters to "wander" AI command.
* Added "radius" parameter to "go_to_location" AI command.
* Added support for mods to change their own mod settings runtime.
* Added LuaEntityPrototype::next_upgrade read.
* Added optional parameters to LuaSurface::create_entity, LuaEntity::destroy and LuaEntity::revive to raise the associated script events.
* Added support to run console commands in a specific mod context via: /c __mod-name__ *command*.
* Added LuaTechnologyPrototype::hidden read.
* Added LuaFluidPrototype::hidden read.
* Added LuaSurface::get_map_exchange_string().
* Added LuaGameScript::get_map_exchange_string().
* Added LuaFlowStatistics::get_flow_count().
* Added LuaEntity::trains_in_block read.
* Added LuaGameScript::get_player().
* Added LuaGameScript::get_surface().
* Added LuaGameScript::set_wait_for_screenshots_to_finish().
* Added LuaGuiElement::resize_to_sprite (read/write).
* Added LuaGroup::localised_name read.
* Added SpritePath::equipment.
* Added LuaEquipmentGridPrototype::background_color read.
* Added LuaItemPrototype::reload_time read.
* Added highlight-box entity that can be passed a "bounding_box" or "source" entity parameter to display a highlight box around an area or entity.
* Added LuaEntityPrototype::is_building read.
* Added LuaEntityPrototype::automated_ammo_count read.
* Added LuaEntity::get_beam_source(), set_beam_source(), get_beam_target() and set_beam_target().
* Added LuaSurface::get_closest().
* Added LuaSurface::get_total_pollution().
* Added LuaPlayer::create_local_flying_text().
* Added LuaEntityPrototype::darkness_for_all_lamps_on and darkness_for_all_lamps_off read.
* Added LuaEntity::status read.
* Added LuaLogisticNetwork::robots, construction_robots, logistic_robots read.
* Added LuaGameScript::get_train_stops(), LuaSurface::get_train_stops(), and LuaForce::get_train_stops().
* Added LuaEntityPrototype::min_darkness_to_spawn and max_darkness_to_spawn read.
* Added "loot" to the on_entity_died event.
* Added LuaTrain::go_to_station().
* Added support to set quality when using LuaGameScript::take_screenshot.
* Added LuaForce::evolution_factor_by_pollution, evolution_factor_by_time, and evolution_factor_by_killing_spawners read/write.
* Added optional create_build_effect_smoke parameter to LuaSurface::create_entity.
* Added LuaEntity::drop_target/pickup_target write.
* Added LuaEntity::ghost_has_flag().
* Added runtime editable speed attribute to Unit.
* Added LuaSurface::get_starting_area_radius().
* Added LuaItemPrototype::robot_action read.
* Added LuaEntity::enable_logistics_while_moving read/write.
* Added optional render_player_index parameter for flying-text and simple-entities to LuaSurface::create_entity.
* Added LuaEntity::render_player read/write.
* Added LuaEntity::render_to_forces read/write.
* Added LuaGameScript::disable_tutorial_triggers().
* Added LuaEntity::get_radius() and LuaEntityPrototype::radius read.
* Added LuaEntity::get_health_ratio().
* Added LuaSurface::find_units().
* Added LuaTransportLine::output_lines read.
* Added LuaEntity::pump_rail_target read.
* Added LuaTrain::get_rails().
* Added LuaEquipmentGridPrototype::locked read.
* Added LuaForce::index read.
* Added direction to LuaSurface::count/find_entities_filtered.
* Added collision_mask to LuaSurface::count/find_entities_filtered.
* Added LuaEntity::clear_market_items().
* Added LuaEntityPrototype::cliff_explosive_prototype read.
* Added LuaDamagePrototype::hidden read.
* Added LuaControl::character_running_speed read.
* Added LuaEntityPrototype::draw_cargo read.
* Added LuaPlayer::use_from_cursor().
* Added LuaGameScript::autosave_enabled variable, that can be used to disable autosaving.
* Added LuaEntity::ai_settings read.
* Added LuaAISettings::destroy_when_commands_fail. When true, units will be destroyed when repeatedly failing to execute commands.
* Added LuaAISettings::allow_try_return_to_spawner. When true, units will try to return to a spawner when they are idle.
* Added LuaAISettings::do_separation. When true, units will try to separate themselves from nearby friendly units.
* Added LuaEntity::moving. Returns true if the unit is moving.
* Added on_unit_group_created, on_unit_added_to_group, and on_unit_removed_from_group events.
* Added LuaEntity::create_build_effect_smoke.
* Added LuaEntityPrototype::vision_distance read.
* Added LuaPlayer::open_map(), zoom_to_world() and close_map().
* Added LuaPlayer::render_mode read.
* Added LuaPlayer::map_view_settings write.
* Added LuaStyle::top_margin, right_margin, bottom_margin and left_margin read/write.
* Added LuaStyle::use_header_filler, natural_width and natural_height read/write.
* Added LuaStyle::extra_padding_when_activated read/write.
* Added LuaStyle::extra_top_margin_when_activated, extra_bottom_margin_when_activated, extra_left_margin_when_activated and extra_right_margin_when_activated read/write.
* Added LuaEntity::electric_network_id read.
* Added LuaControl::character_additional_mining_categories read/write.
* Added LuaGameScript::draw_resource_selection read/write.
* Added LuaForce::get_hand_crafting_disabled_for_recipe() and set_hand_crafting_disabled_for_recipe().
* Added LuaEntityPrototype::map_generator_bounding_box read.
* Added LuaEntity::release_from_spawner().
* Added on_cutscene_waypoint_reached, on_entity_cloned, on_area_cloned, on_marked_for_upgrade, on_cancelled_upgrade, on_post_entity_died, on_pre_player_removed, on_pre_robot_exploded_cliff, on_robot_exploded_cliff, on_script_path_request_finished, on_surface_imported, on_player_toggled_map_editor events.
* Added LuaEntity::timeout read/write.
* Added LuaEntity::highlight_box_type and highlight_box_blink_interval read/write.
* Added LuaEntity::order_upgrade(), cancel_upgrade() and to_be_upgraded().
* Added LuaEntity::research_queue_enabled read/write.
* Added LuaGameScript::get_active_entities_count().
* Added LuaGameScript::ticks_played read.
* Added LuaGameScript::tick_paused and ticks_to_run read/write.
* Added LuaItemPrototype::infinite read.
* Added LuaItemStack::clear_upgrade_item(), get_mapper(), set_mapper().
* Added LuaItemStack::is_upgrade_item read.
* Added LuaLogisticCell::logistics_connection_distance read.
* Added LuaLogisticNetwork::select_pickup_point() and select_drop_point().
* Added LuaPlayer::jump_to_cutscene_waypoint().
* Added LuaUnitGroup::group_number read.
* Changed LuaEntity::destroy() to accept a table of arguments.
* Changed LuaEntity::revive() to accept a table of arguments.
* Changed the player_used_capsule event so it's fired after the capsule item is consumed from the cursor.
* Changed LuaEntity::splitter_filter, splitter_input_priority, and splitter_output_priority so they also work on ghosts.
* Changed LuaSurface::destroy_decoratives() to take filters similar to find_entities_filtered.
* Changed LuaEntityPrototype::items_to_place_this and LuaTilePrototype::items_to_place_this to return an array of SimpleItemStack.
* Changed most LuaEntity properties/functions to also work on ghosts.
* Changed on_player_crafted_item item_stack to allow editing the stack before it's put into the player inventory.
* Changed LuaSurface::regenerate_entity()/regenerate_decorative() to treat "nil" as "all" for the autoplace list.
* Changed LuaEquipmentPrototype::energy_source to return a LuaElectricEnergySourcePrototype.
* Changed sound definition, so it can contain "aggregation" even when it doesn't contain "variations".
* Renamed LuaEntity::get_infinity_filter(), set_infinity_filter(), and infinity_filters to get_infinity_container_filter(), set_infinity_container_filter(), and infinity_container_filters.
* Renamed on_canceled_deconstruction event to on_cancelled_deconstruction.
* Fixed the spelling of LuaForce::max_successful_attempts_per_tick_per_construction_queue.
* LuaSurface::find_entities/filtered now accepts a zero sized bounding box as "find everything that collides with this point".
* CustomSprite now scales to the size of the sprite if a manual size isn't defined.
* It's possible to specify "frame_sequence" in animation definition as array of frame numbers that should be played in given order.
* Removed LuaStyle::visible, LuaGuiElement::visible is used instead.
* Removed LuaSurface::get_tile_properties().
* Removed LuaCustomChartTag::orientation and target.
* Removed LuaFluidPrototype::pressure_to_speed_ratio and flow_to_energy_ratio.

{{VersionNav}}

Prototype/EntityWithHealth

2019-05-02T19:24:08Z

Muppet9010: /* max_health */ add that must be greater than 0

==Basics==
This type is abstract and cannot be created directly.

The common properties of all entities with health in the game.
Extends the [[Prototype/Entity]]

== Extensions ==
<div class="factorio-list">
* [[Prototype/Accumulator]] '''accumulator'''
* [[Prototype/ArtilleryTurret]] '''artillery-turret'''
* [[Prototype/Beacon]] '''beacon'''
* [[Prototype/Boiler]] '''boiler'''
* [[Prototype/Character]] '''character'''
* [[Prototype/Combinator]] <abstract>
** [[Prototype/ArithmeticCombinator]] '''arithmetic-combinator'''
** [[Prototype/DeciderCombinator]] '''decider-combinator'''
* [[Prototype/ConstantCombinator]] '''constant-combinator'''
* [[Prototype/Container]] '''container'''
** [[Prototype/LogisticContainer]] '''logistic-container'''
*** [[Prototype/InfinityContainer]] '''infinity-container'''
* [[Prototype/CraftingMachine]] <abstract>
** [[Prototype/AssemblingMachine]] '''assembling-machine'''
*** [[Prototype/RocketSilo]] '''rocket-silo'''
** [[Prototype/Furnace]] '''furnace'''
* [[Prototype/ElectricEnergyInterface]] '''electric-energy-interface'''
* [[Prototype/ElectricPole]] '''electric-pole'''
* [[Prototype/EnemySpawner]] '''unit-spawner'''
* [[Prototype/Fish]] '''fish'''
* [[Prototype/FlyingRobot]] <abstract>
** [[Prototype/CombatRobot]] '''combat-robot'''
** [[Prototype/RobotWithLogisticInterface]] <abstract>
*** [[Prototype/ConstructionRobot]] '''construction-robot'''
*** [[Prototype/LogisticRobot]] '''logistic-robot'''
* [[Prototype/Gate]] '''gate'''
* [[Prototype/Generator]] '''generator'''
* [[Prototype/HeatInterface]] '''heat-interface'''
* [[Prototype/HeatPipe]] '''heat-pipe'''
* [[Prototype/Inserter]] '''inserter'''
* [[Prototype/Lab]] '''lab'''
* [[Prototype/Lamp]] '''lamp'''
* [[Prototype/LandMine]] '''land-mine'''
* [[Prototype/Market]] '''market'''
* [[Prototype/MiningDrill]] '''mining-drill'''
* [[Prototype/OffshorePump]] '''offshore-pump'''
* [[Prototype/Pipe]] '''pipe'''
** [[Prototype/InfinityPipe]] '''infinity-pipe'''
* [[Prototype/PipeToGround]] '''pipe-to-ground'''
* [[Prototype/PlayerPort]] '''player-port'''
* [[Prototype/PowerSwitch]] '''power-switch'''
* [[Prototype/ProgrammableSpeaker]] '''programmable-speaker'''
* [[Prototype/Pump]] '''pump'''
* [[Prototype/Radar]] '''radar'''
* [[Prototype/Rail]] <abstract>
** [[Prototype/CurvedRail]] '''curved-rail'''
** [[Prototype/StraightRail]] '''straight-rail'''
* [[Prototype/RailSignalBase]] <abstract>
** [[Prototype/RailChainSignal]] '''rail-chain-signal'''
** [[Prototype/RailSignal]] '''rail-signal'''
* [[Prototype/Reactor]] '''reactor'''
* [[Prototype/Roboport]] '''roboport'''
* [[Prototype/SimpleEntity]] '''simple-entity'''
* [[Prototype/SimpleEntityWithOwner]] '''simple-entity-with-owner'''
* [[Prototype/SimpleEntityWithForce]] '''simple-entity-with-force'''
* [[Prototype/SolarPanel]] '''solar-panel'''
* [[Prototype/StorageTank]] '''storage-tank'''
* [[Prototype/TrainStop]] '''train-stop'''
* [[Prototype/TransportBeltConnectable]] <abstract>
** [[Prototype/Loader]] '''loader'''
** [[Prototype/Splitter]] '''splitter'''
** [[Prototype/TransportBelt]] '''transport-belt'''
** [[Prototype/UndergroundBelt]] '''underground-belt'''
* [[Prototype/Tree]] '''tree'''
* [[Prototype/Turret]] '''turret'''
** [[Prototype/AmmoTurret]] '''ammo-turret'''
** [[Prototype/ElectricTurret]] '''electric-turret'''
** [[Prototype/FluidTurret]] '''fluid-turret'''
* [[Prototype/Unit]] '''unit'''
* [[Prototype/Vehicle]] <abstract>
** [[Prototype/Car]] '''car'''
** [[Prototype/RollingStock]] <abstract>
*** [[Prototype/ArtilleryWagon]] '''artillery-wagon'''
*** [[Prototype/CargoWagon]] '''cargo-wagon'''
*** [[Prototype/FluidWagon]] '''fluid-wagon'''
*** [[Prototype/Locomotive]] '''locomotive'''
* [[Prototype/Wall]] '''wall'''
</div>

== Properties ==
=== max_health ===
'''Type''': [[Types/float]]

'''Default''': 10

The unit health can never go over the maxmum. Default health of units on creation is set to max. Must be greater than 0.
max_health = 50

=== healing_per_tick ===
'''Type''': [[Types/float]]

'''Default''': 0

The amount of health cured by tick naturally.
Works only on active entities. (Todo explain)
healing_per_tick = 0.01

=== repair_speed_modifier ===
'''Type''': [[Types/float]]

'''Default''': 1

=== dying_explosion ===
'''Type''': [[Types/string]]

The entity that is spawned in place of this one when it dies.

=== dying_trigger_effect ===
'''Type''': [[Types/TriggerEffect]]

=== loot ===
'''Type''': [[Types/Loot]]

The loot is dropped on the ground when the entity is killed.
<syntaxhighlight lang="lua">loot =
{
{
count_max = 10,
count_min = 2,
item = "stone",
probability = 1
}
}</syntaxhighlight>

=== resistances ===
'''Type''': [[Types/Resistances]]

'''See''': [[Damage]]
<syntaxhighlight lang="lua">resistances =
{
{
type = "fire",
percent = 80
},
{
type = "explosion",
percent = 30
}
}</syntaxhighlight>

=== attack_reaction ===
'''Type''': [[Types/AttackReaction]]

'''Default''': Empty

=== repair_sound ===
'''Type''': [[Types/Sound]]

'''Default''': Utility sound (defaultManualRepair)

=== alert_when_damaged ===
'''Type''': [[Types/bool]]

'''Default''': true

=== hide_resistances ===
'''Type''': [[Types/bool]]

'''Default''': true

=== create_ghost_on_death ===
'''Type''': [[Types/bool]]

'''Default''': true

=== corpse ===
'''Type''': [[Types/string]] or [[Types/table]] of [[Types/string]]s

'''Default''': Empty

Specifies the name(s) of the [[Prototype/Corpse]] entity to be used when this entity dies.

=== integration_patch ===
'''Type''': [[Types/Sprite4Way]]

Sprite drawn on ground under the entity to make it feel more integrated into the ground.

== Example ==
<syntaxhighlight lang="lua">{
type = "container",
name = "wooden-chest",
icon = "__base__/graphics/icons/wooden-chest.png",
flags = {"placeable-neutral", "player-creation"},
minable = {mining_time = 1, result = "wooden-chest"},
max_health = 100,
corpse = "small-remnants",
collision_box = {{-0.35, -0.35}, {0.35, 0.35}},
fast_replaceable_group = "container",
selection_box = {{-0.5, -0.5}, {0.5, 0.5}},
inventory_size = 16,
open_sound = { filename = "__base__/sound/wooden-chest-open.ogg" },
close_sound = { filename = "__base__/sound/wooden-chest-close.ogg" },
vehicle_impact_sound = { filename = "__base__/sound/car-wood-impact.ogg", volume = 1.0 },
picture =
{
filename = "__base__/graphics/entity/wooden-chest/wooden-chest.png",
priority = "extra-high",
width = 46,
height = 33,
shift = {0.25, 0.015625}
},
circuit_wire_connection_point =
{
shadow =
{
red = {0.734375, 0.453125},
green = {0.609375, 0.515625},
},
wire =
{
red = {0.40625, 0.21875},
green = {0.40625, 0.375},
}
},
circuit_connector_sprites = get_circuit_connector_sprites({0.1875, 0.15625}, nil, 18),
circuit_wire_max_distance = 9
}</syntaxhighlight>

Flamethrower turret

2019-04-30T18:01:05Z

Muppet9010: add reference to target priority as it is unique compared to other turrets

{{Languages}}
{{:Infobox:Flamethrower turret}}

'''Flamethrower turrets''' work similarly to the [[Flamethrower]], setting [[enemies]] and the ground on fire and doing damage over time. Unlike gun and laser turrets, they have a limited firing arc, and should therefore should be placed at choke points or behind walls. They can use crude, heavy, or light oil as ammunition, which must be provided via a pipe connected to the turret. Flamethrower turrets gain a damage bonus depending on the type of oil supplied to them. This bonus is multiplicative, it stacks with the bonus damage from research.

{| class="wikitable"
! Ammunition !! Effect
|-
|{{IconLink|Crude oil}} ||100% Damage
|-
|{{IconLink|Heavy oil}} ||105% Damage
|-
|{{IconLink|Light oil}} ||110% Damage
|}

Unlike the laser and gun turrets, flamethrower turrets do not have a instantaneously hitting projectile, instead firing a stream of flame directly at where the target was at the time of firing. This means that they have a tendency to miss the targeted biter in an attacking group, instead hitting the ones behind.

Flamethrower turrets are very powerful because biters and spitters do not have fire resistance and the total 3000 damage dealt to ignited enemies is a guaranteed death sentence for anything in the game. An enemy unit is ignited if it is hit directly by a flame stream. Flamethrower turrets will target the closest non ignited enemy and then once all enemies within range are ignited they will target the closest enemy.

The bonus technologies and fuel damage bonus for the flamethrower turret improve the contact damage and damage dealt by fire on the ground. However, they do not affect the damage dealt to ignited enemies, which always lasts 30 seconds and deals 100 damage per second.

Flamethrower turrets create fire on the ground which lasts 2 seconds by default. If the turret keeps firing at that spot, the fire will last up to 30 seconds and its damage is increased up to 6 times, depending on how long the turret keeps firing at that spot.

== History ==

{{history|0.13.0|
*Introduced.
*Damage upgrade technology introduced.}}

== See also ==

* [[Gun turret]]
* [[Laser turret]]

{{CombatNav}}
{{C|Defense}}

Types/BaseAttackParameters

2019-04-30T17:51:03Z

Muppet9010: /* min_attack_distance */ add description from API doc

The abstract base of all attack parameters.

== Extensions ==
* [[Types/ProjectileAttackParameters]]
* [[Types/BeamAttackParameters]]
* [[Types/StreamAttackParameters]]

== Mandatory properties ==
=== range ===
'''Type''': [[Types/float]]

=== cooldown ===
'''Type''': [[Types/float]]

Number of ticks in which it will be possible to shoot again. If < 1, multiple shots can be performed in one tick.

== Optional properties ==
=== min_range ===
'''Type''': [[Types/float]]

'''Default''': 0

=== turn_range ===
'''Type''': [[Types/float]]

'''Default''': 1

If this is <= 0, it is set to 1.

=== fire_penalty ===
'''Type''': [[Types/float]]

'''Default''': 0

Used when searching for the nearest enemy, when this is > 0, enemies that aren't burning are preferred over burning enemies. Definition of "burning" for this: Entity has sticker attached to it, and the sticker has a [[Prototype/Sticker#spread_fire_entity|fire_spread_entity]] set.

=== min_attack_distance ===
'''Type''': [[Types/float]]

'''Default''': <code>range</code>

If less than <code>range</code>, the entity will choose a random distance between <code>range</code> and <code>min_attack_distance</code> and attack from that distance.

=== damage_modifier ===
'''Type''': [[Types/float]]

'''Default''': 1

=== warmup ===
'''Type''': [[Types/uint32]]

'''Default''': 0

Number of ticks it takes for the weapon to actually shoot after the order for shooting has been made. This also allows to "adjust" the shooting animation to the effect of shooting.

=== movement_slow_down_factor ===
'''Type''': [[Types/double]]

'''Default''': 1

=== movement_slow_down_cooldown ===
'''Type''': [[Types/float]]

'''Default''': <code>cooldown</code>

=== ammo_type ===
'''Type''': [[Types/AmmoType]]

Can be mandatory.

=== ammo_category ===
'''Type''': [[Types/string]]

The name of a [[Prototype/AmmoCategory]]. Mandatory if <code>ammo_type</code> is not given, otherwise ignored.

=== sound ===
'''Type''': [[Types/Sound]]

=== animation ===
'''Type''': [[Types/RotatedAnimation]]

=== cyclic_sound ===
'''Type''': [[Types/CyclicSound]]

Flamethrower turret

2019-04-30T17:24:16Z

Muppet9010: clarify wording across page

{{Languages}}
{{:Infobox:Flamethrower turret}}

'''Flamethrower turrets''' work similarly to the [[Flamethrower]], setting [[enemies]] and the ground on fire and doing damage over time. Unlike gun and laser turrets, they have a limited firing arc, and should therefore should be placed at choke points or behind walls. They can use crude, heavy, or light oil as ammunition, which must be provided via a pipe connected to the turret. Flamethrower turrets gain a damage bonus depending on the type of oil supplied to them. This bonus is multiplicative, it stacks with the bonus damage from research.

{| class="wikitable"
! Ammunition !! Effect
|-
|{{IconLink|Crude oil}} ||100% Damage
|-
|{{IconLink|Heavy oil}} ||105% Damage
|-
|{{IconLink|Light oil}} ||110% Damage
|}

Unlike the laser and gun turrets, flamethrower turrets do not have a instantaneously hitting projectile, instead firing a stream of flame directly at where the target was at the time of firing. This means that they have a tendency to miss the targeted biter in an attacking group, instead hitting the ones behind.

Flamethrower turrets are very powerful because biters and spitters do not have fire resistance and the total 3000 damage dealt to ignited enemies is a guaranteed death sentence for anything in the game. An enemy unit is ignited if it is hit directly by a flame stream.

The bonus technologies and fuel damage bonus for the flamethrower turret improve the contact damage and damage dealt by fire on the ground. However, they do not affect the damage dealt to ignited enemies, which always lasts 30 seconds and deals 100 damage per second.

Flamethrower turrets create fire on the ground which lasts 2 seconds by default. If the turret keeps firing at that spot, the fire will last up to 30 seconds and its damage is increased up to 6 times, depending on how long the turret keeps firing at that spot.

== History ==

{{history|0.13.0|
*Introduced.
*Damage upgrade technology introduced.}}

== See also ==

* [[Gun turret]]
* [[Laser turret]]

{{CombatNav}}
{{C|Defense}}

User:Muppet9010

2019-04-30T17:10:58Z

Muppet9010: word tweak

{{Languages}}
{{:Infobox:Flamethrower turret}}

'''Flamethrower turrets''' work similarly to the [[Flamethrower]], setting [[enemies]] and the ground on fire and doing damage over time. Unlike gun and laser turrets, they have a limited firing arc, and should therefore should be placed at choke points or behind walls. They can use crude, heavy, or light oil as ammunition, which must be provided via a pipe connected to the turret. Flamethrower turrets gain a damage bonus depending on the type of oil supplied to them. This bonus is multiplicative, it stacks with the bonus damage from research.

{| class="wikitable"
! Ammunition !! Effect
|-
|{{IconLink|Crude oil}} ||100% Damage
|-
|{{IconLink|Heavy oil}} ||105% Damage
|-
|{{IconLink|Light oil}} ||110% Damage
|}

Unlike the laser and gun turrets, flamethrower turrets do not have a instantaneously hitting projectile, instead firing a stream of flame directly at where the target was at the time of firing. This means that they have a tendency to miss the targeted biter in an attacking group, instead hitting the ones behind.

Flamethrower turrets are very powerful because biters and spitters do not have fire resistance and the total 3000 damage dealt to ignited enemies is a guaranteed death sentence for anything in the game. An enemy unit is ignited if it is hit directly by a flame stream.

The bonus technologies and fuel damage bonus for the flamethrower turret improve the contact damage and damage dealt by fire on the ground. However, they do not affect the damage dealt to ignited enemies, which always lasts 30 seconds and deals 100 damage per second.

Flamethrower turrets create fire on the ground which lasts 2 seconds by default. If the turret keeps firing at that spot, the fire will last up to 30 seconds and its damage is increased up to 6 times, depending on how long the turret keeps firing at that spot.

== History ==

{{history|0.13.0|
*Introduced.
*Damage upgrade technology introduced.}}

== See also ==

* [[Gun turret]]
* [[Laser turret]]

{{CombatNav}}
{{C|Defense}}

User:Muppet9010

2019-04-30T17:08:55Z

Muppet9010: tweaks and additions to clarify some points and behaviour.

{{Languages}}
{{:Infobox:Flamethrower turret}}

'''Flamethrower turrets''' work similarly to the [[Flamethrower]], setting [[enemies]] and the ground on fire and doing damage over time. Unlike gun and laser turrets, they have a limited firing arc, and should therefore should be placed at choke points or behind walls. They can use crude, heavy, or light oil as ammunition, which must be provided via a pipe connected to the turret. Flamethrower turrets gain a damage bonus depending on the type of oil supplied to them. This bonus is multiplicative, it stacks with the bonus damage from research.

{| class="wikitable"
! Ammunition !! Effect
|-
|{{IconLink|Crude oil}} ||100% Damage
|-
|{{IconLink|Heavy oil}} ||105% Damage
|-
|{{IconLink|Light oil}} ||110% Damage
|}

Unlike the laser and gun turrets, flamethrower turrets do not have a instantaneously seeking projectile, instead firing a stream of flame directly at where the target was at the point of firing. This means that they have a tendency to miss the targeted biter in an attacking group, instead hitting the ones behind.

Flamethrower turrets are very powerful because biters and spitters do not have fire resistance and the total 3000 damage dealt to ignited enemies is a guaranteed death sentence for anything in the game. An enemy unit is ignited if it is hit directly by a flame stream.

The bonus technologies and fuel damage bonus for the flamethrower turret improve the contact damage and damage dealt by fire on the ground. However, they do not affect the damage dealt to ignited enemies, which always lasts 30 seconds and deals 100 damage per second.

Flamethrower turrets create fire on the ground which lasts 2 seconds by default. If the turret keeps firing at that spot, the fire will last up to 30 seconds and its damage is increased up to 6 times, depending on how long the turret keeps firing at that spot.

== History ==

{{history|0.13.0|
*Introduced.
*Damage upgrade technology introduced.}}

== See also ==

* [[Gun turret]]
* [[Laser turret]]

{{CombatNav}}
{{C|Defense}}

User:Muppet9010

2019-04-30T16:54:16Z

Muppet9010: current flamethrower page

{{Languages}}
{{:Infobox:Flamethrower turret}}

'''Flamethrower turrets''' work similarly to the [[Flamethrower]], setting [[enemies]] on fire and doing damage over time. Unlike gun and laser turrets, they have a limited firing arc, and should therefore should be placed at choke points or behind walls. They can use crude, heavy, or light oil as ammunition, which must be provided via a pipe connected to the turret. Flamethrower turrets gain a damage bonus depending on the type of oil supplied to them. This bonus is multiplicative, it stacks with the bonus damage from research.

{| class="wikitable"
! Ammunition !! Effect
|-
|{{IconLink|Crude oil}} ||100% Damage
|-
|{{IconLink|Heavy oil}} ||105% Damage
|-
|{{IconLink|Light oil}} ||110% Damage
|}

Unlike the laser and gun turrets, flamethrower turrets do not have a seeking projectile, instead firing directly at where the biters was at the point of firing. This means that they have a tendency to miss the first row of biters. Flamethrower turrets are very powerful because biters and spitters do not have fire resistance and the total 3000 dealt to ignited enemies is a guaranteed death sentence for anything in the game.

The bonus technologies and fuel damage bonus for the flamethrower turret improve the contact damage and damage dealt by fire on the ground. However, they do not affect the damage dealt to ignited enemies, this fire always lasts 30 seconds and always deals 100 damage per second.

Flamethrower turrets create fire on the ground which lasts 2 seconds by default. If the turret keeps firing at that spot, the fire will last up to 30 seconds and its damage is increased up to 6 times, depending on how long the turret keeps firing at that spot.

== History ==

{{history|0.13.0|
*Introduced.
*Damage upgrade technology introduced.}}

== See also ==

* [[Gun turret]]
* [[Laser turret]]

{{CombatNav}}
{{C|Defense}}

Flamethrower turret

2019-04-30T16:25:19Z

Muppet9010: correct maths: 30 * 100 = 30,000, not 3,000

{{Languages}}
{{:Infobox:Flamethrower turret}}

'''Flamethrower turrets''' work similarly to the [[Flamethrower]], setting [[enemies]] on fire and doing damage over time. Unlike gun and laser turrets, they have a limited firing arc, and should therefore should be placed at choke points or behind walls. They can use crude, heavy, or light oil as ammunition, which must be provided via a pipe connected to the turret. Flamethrower turrets gain a damage bonus depending on the type of oil supplied to them. This bonus is multiplicative, it stacks with the bonus damage from research.

{| class="wikitable"
! Ammunition !! Effect
|-
|{{IconLink|Crude oil}} ||100% Damage
|-
|{{IconLink|Heavy oil}} ||105% Damage
|-
|{{IconLink|Light oil}} ||110% Damage
|}

Unlike the laser and gun turrets, flamethrower turrets do not have a seeking projectile, instead firing directly at where the biters was at the point of firing. This means that they have a tendency to miss the first row of biters. Flamethrower turrets are very powerful because biters and spitters do not have fire resistance and the total 30,000 dealt to ignited enemies is a guaranteed death sentence for anything in the game.

The bonus technologies and fuel damage bonus for the flamethrower turret improve the contact damage and damage dealt by fire on the ground. However, they do not affect the damage dealt to ignited enemies, this fire always lasts 30 seconds and always deals 100 damage per second.

Flamethrower turrets create fire on the ground which lasts 2 seconds by default. If the turret keeps firing at that spot, the fire will last up to 30 seconds and its damage is increased up to 6 times, depending on how long the turret keeps firing at that spot.

== History ==

{{history|0.13.0|
*Introduced.
*Damage upgrade technology introduced.}}

== See also ==

* [[Gun turret]]
* [[Laser turret]]

{{CombatNav}}
{{C|Defense}}

Railway

2019-04-23T16:38:40Z

Muppet9010: /* Connection to OpenTTD */ typos and grammar

{{Languages}}
:''For the research see [[Railway (research)]]''

'''The Railway''' is one of the main transport methods in Factorio. Although the installation of such a network can be complicated, and requires a large amount of resource and space, it is faster and more efficient than [[Belt transport system|belts]] and [[Logistic network|robot logistics]], especially over large distances.

Railway construction, however, is not understood instantly. It takes some time to learn the basics, such as automating transportation. Learning how to manage and maintain upkeep of a larger train network takes time and experience.

== Infrastructure ==

To build a railway, tracks (also called rails) must be built for the train to ride on. Typically, this is done via the [[rail planner]], but can also be done manually. Bear in mind that rails are placed on a two-tile grid, so a rail cannot be moved by only one tile.

=== Minimum manually operated railway ===
As a minimum a manually operated railway has to consist of:
* [[Rail]]s (tracks)
* [[Locomotive]]s

Locomotives can be entered and then manually operated by standing next to them and pressing the {{Key|ENTER}} button.

=== Switches ===
* There is no visual representation of a working switch, however the rails will appear to merge. Using the rail planner, the player must place a [[rail]] overlapping an existing rail to form a switch. Switches are forks in tracks that allow a train to pick between two directional options.
* The crossing of two straight tracks is not usable as switch, as trains have a limited turning radius. They do, however, connect [[Rail signal| signal blocks]] which helps prevent collisions.
* Parallel tracks do not interact with each other. However, switching from one track to the other can require extra resources if they are too close together; the track must turn away from the other parallel track and then turn back to it. This can create complicated networks of signals and, as such, one should generally not build parallel tracks unless they are spaced adequately. (Generally, 2 track widths apart works well)

[[File:fff-140-controlled-gates.gif|thumb|An example of a safe railway crossing.]]
=== Crossing tracks ===

'''Be careful when crossing tracks! Trains are one of the highest damaging entities in the game, and will kill most players instantly on contact.'''

A checklist of proper track crossing etiquette:

# Zoom out, so that you can see a train coming.
# Look left, then right.
# Check for signals nearby: If a [[rail signal]] suddenly jumps from green to red or green to yellow, a train is coming. Do not cross.
# Avoid walking near the tracks, as you do not need to be fully on the tracks to get hit.
# While it is possible to get into/out of a train while it is moving, a miss can cost your life. The sides of the train can still deal damage, as well as the player being able to slip between two rail cars.
# Heavy [[Energy shield|shields]] can be used to reduce the damage taken. In extreme cases, it is possible to stop a train with your body. This will require several shield modules to not be instantly killed, and will drain a large amount of the suit's energy.
# All entities with health will take damage getting hit by a train, so take care not to leave a [[car]] or [[tank]] on the tracks. However, this includes hostile forces!
# Trains far from a [[train stop]] will be traveling at (near) max speed, so take extra precaution when crossing and zoom out further. Trains near a [[train stop]] or signal will slow down to stop, and will be traveling slower. Trains of different configurations will also move slower or faster.

A safe railroad crossing like the example shown in the picture can be built. This works by restricting access to the tracks when an oncoming train has the rails reserved. When the player is on the rails, the signals are reserved by the [[circuit network]], and the train must stop and wait until the player leaves the tracks. When a player is inside the area crossing the tracks, the train gates are closed so the player can't get on the tracks outside the crossing. This is to completely ensure a safe crossing, and is often used on servers.

{{clear}}

== Trains ==
Train components:

{| class="wikitable"
|{{Imagelink|Locomotive}} || {{Imagelink|Cargo wagon}} || {{Imagelink|Fluid wagon}} || {{Imagelink|Artillery wagon}}
|}

[[File:Railway-assemble-train.png|thumb|left|300px|Placing a [[Cargo wagon]] so it is attached to the train.]]

* A train consists of at least one locomotive.
* Trains can have more than one locomotive, and any number of [[wagon]]s.
* Locomotives can be '''manually''' driven forwards or backwards, however, they are generally slower going backwards. The left and right movement keys are used to change direction at switches.
* Trains can only drive forwards automatically. An automatic train can drive forwards and backwards when two locomotives facing different directions are connected to the train.
* A train needs [[fuel]] to drive. Fuel can be added by inserters when the train is in manual mode or parked at a station, not when waiting at a signal or standing on automatic mode.

The locomotives' inventory is only used for [[fuel]]. To transport items or fluids [[cargo wagon]]s and/or [[fluid wagon]]s have to be attached to the train. To attach rolling stock, whether a wagon or a locomotive, the player may either prepare to place one near an existing train, where a green graphic will show the player that the stock will be attached, showing a connection between the train and the new stock. Alternatively, the player may manually connect rolling stock to trains with the rolling stock connect key, if the cargo wagon was placed far away from a train. Rolling stock can likewise be disconnected with the rolling stock disconnect key. The cargo wagons can be filled or emptied manually or by up to twelve adjacent [[Inserters]] (six on each side), while fluid wagons can be filled or emptied with up to three [[pump]]s, which will automatically connect to the nipples on top.

{{clear}}

== Stations ==
[[File:station-example-1.png|thumb|right|256px|A very minimal train station.]]
Station Components:
{| class="wikitable"
|{{Imagelink|Train stop}} || {{Imagelink|Straight rail|Rail|Rails}} || {{Imagelink|Inserter|Inserters}} or {{Imagelink|pump|pump|Pumps}}
|}

A '''train station''' is a combination of at least one [[train stop]] plus a [[storage]] and/or distribution system, used to fill or empty [[cargo wagon]]s and/or [[fluid wagon]]s, load [[fuel]] into the [[Locomotive|locomotive(s)]], load ammunition into [[artillery wagon]]s, or repair trains.

'''Don't mix up ''train stations'' with ''train stops''.''' A train station is a concept, whereas a [[train stop]] is an item.

[[Inserter]]s placed next to train tracks are used to load/unload trains at train stops. Inserters are the only way to automatically get items out of and into cargo and artillery wagons; pumps are the only way to automatically get fluids into and out of fluid wagons.

{{clear}}

== Signals ==
{| class="wikitable"
| {{Imagelink|Rail signal}} || {{Imagelink|Rail chain signal}}
|}

Rail signals are used to employ multiple trains automatically without the danger of trains crashing into each other. Rail signals split the network into blocks and ensure that only one train can be in every block at any time. Note that driving a train manually ignores all signals; so it is possible for automatic trains to crash into the player if the player ignores red/yellow signals. Always beware of automatic trains and give them the right of way.

The [[Tutorial:Train signals|train signals tutorial]] contains an in-depth explanation of rail signals, blocks and deadlocks.

=== Basic Signaling Rules ===
* There can only be one train in a block at any time. A train spanning multiple blocks occupies them all.
* A red signal means that the following block is occupied by a train.
* A yellow signal means that a train is approaching and already has the approval to enter the following block.
* [[Rail signal]]s separate a new block and reflect its state: green - free, yellow - reserved, red - occupied
* [[Rail chain signal]]s separate a new block and reflect the state of the next [[rail signal]](s): see above, blue - at least one of the paths is blocked, but not all
* A train can only pass a signal on the right of the track, or if there is a signal on both sides on the same rail segment. Of course, manual driving overrides this.

== Automated transport ==
[[File:locomotive_gui.png|thumb|300px|The wait condition tab in the locomotive's GUI.]]

Trains set on "Automatic" choose their destination stop and route on departure, and after waiting at a chain signal for five seconds, and when their destination stop disables itself by circuit condition. They choose the shortest route using a [[Railway/Train_path_finding|path finding algorithm]] that will get them to an enabled train stop with the right name, taking penalties for any apparent-at-the-time delays into account. If no such train stop exists they will skip the stop and go on to the next.

This section covers items used to make trains automatically transport items between stations. The player should be familiar with creating a rail system.

First, the player has to setup a rail system with at least two train stops, which are placed in the right-hand side of the expected train arrival direction. By hovering over the train stop with the mouse you see the positions of the vehicles for better setting up the train station (including (un)loading machinery, refueling/repair installations).

When you set up the train schedule (see below) and fuel the train, you can start the train on it's schedule by switching from manual to automatic driving mode.

=== Train schedule ===
The player can set up a list of train stations in the upper window. The train will route to stops in the given order, if it's at the end it will continue with the first. Currently, it's not possible to make a one-time schedule. Stations can be added by clicking button 2 (see picture). A pop-up appears with a list of all stop names. If you select one, another pop-up appears for you to select a wait condition.

Wait conditions are used to tell the train when to leave the station. There are 7 types of wait conditions:
* '''Time passed'''
* '''Inventory full''' – All inventories of the train are full.
* '''Inventory empty''' – Same as above, but empty.
* '''Item count''' – The train (all cargoes summed) contains a specific amount of a certain item.
* '''Circuit condition''' – The train stop is connectable to the [[circuit network]], so the signals can used for wait conditions.
* '''Inactivity''' – No items were added or removed for the specified amount of seconds.
* '''Fluid count''' – The train (all fluid wagons summed) contains a specific amount of a certain fluid.
* '''Passenger present''' - At least one [[player]] is inside any part of the train.
* '''Passenger not present''' - No players are inside any part of the train.

Hereafter the word "term" is used to describe ''one'' type of wait condition, and the words "wait condition" are used to describe the whole set of terms (it turns a bit into maths).

If you add more than one term, you can change the connection of those using the logical operators AND and OR (button 7). An AND condition will result in true if all terms are true. An OR condition will return true if at least one of the terms is true.

When mixing AND and OR terms, the logic is grouped by the OR terms. When evaluating the wait condition, the first term is evaluated along with all AND terms immediately following up to but excluding the next occurring OR term. If they all evaluate true, the wait condition evaluates true. Otherwise, evaluation continues with that next occurring OR term and all AND terms immediately following it, up to the next OR term. This continues until either an OR group evaluates true and the wait condition is satisfied, or all terms have been checked.

==== Examples ====
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Expand for examples
<div class="mw-collapsible-content">
Wait until full, up to 30 seconds:

<pre>
Full cargo inventory
OR 30 seconds passed
</pre>

Wait until cargo full, ''or'' circuit condition Oil > 3000:

<pre>
Full cargo inventory
OR Circuit condition - Oil > 3000
</pre>

Wait until empty, ''and'' 30 seconds passed, ''and'' 5 seconds of inactivity:

<pre>
Empty cargo inventory
AND 30 seconds passed
AND 5 seconds of inactivity
</pre>

Wait until iron ore is low, ''or'' copper ore is low ''and'' at least 30 seconds passed:

<pre>
Cargo: Iron ore < 500
AND 30 seconds passed
OR Cargo: Copper ore < 500
AND 30 seconds passed
</pre>

Factorio's wait condition logic is read as disjunctive normal form ([https://en.wikipedia.org/wiki/Disjunctive_normal_form DNF]), and so this last example is processed as (note the parenthesis):

<pre>((Cargo: Iron ore < 500 AND 30 seconds passed) OR (Cargo: Copper ore < 500 AND 30 seconds passed))</pre>

Which is the same as this:

<pre>((Cargo: Iron ore < 500 OR Cargo: Copper ore < 500) AND 30 seconds passed)</pre>

Unfortunately, there is no way to write that shorter form in the current UI.
</div></div>

=== Troubleshooting ===

Below are some things to verify if a rail system or train is not working.

* Is the train fueled? Ensure that the locomotive has [[fuel]] of some kind.
* Misplaced or non-functional switches? Ensure that the train can plan a path through the switches.
* Another train on the same [[Railway#Block|block]]? Make sure the path of the train is unobstructed.
* Train stops placed correctly? Make sure that the yellow arrows when hovering on the stop point towards the end or exit of the stop.
* Is the train allowed to enter signals from the right direction? Are the signals set correctly?
* If a track is supposed to be two-way, the rail signals should be opposite each other. You can verify they match up by hovering the cursor over one. For a matched pair, it will show the other.

==== No path ====
When trains cannot reach the target, a "no path" symbol pops up over the locomotive. Check:
* Can the train reach its current destination by '''only driving forward'''? Build turning slopes or place a locomotive at both ends of a train!
* Are the train stops standing in the right direction? Train stops must be on the right hand side of the track.
* If you use rail signals, check that the signals are all allowing traffic in the correct direction.
* Check for interruptions in the train tracks, drive to the station manually to check there are no rail parts missing. Especially near junctions these can be hard to spot if missing.

If you are still having problems, consider:
* Driving the train manually, and as you pass each switch, try switching to automatic. When it works, you will know the rough area of the problem.
[http://imgur.com/a/Nq2Yk A pictorial summary of typical problems].

== Achievements ==
{{Achievement|trans-factorio-express}}

== Connection to [https://www.openttd.org/ OpenTTD] ==
Factorio's railway system offers the same type of advanced railway design as [https://wiki.openttd.org/Signals#Pre-signals≈ block entry pre-signals and block exit pre-signals do in Open Transport Tycoon Deluxe].

== See also ==
* [[Tutorial:Train signals]]
* [[Railway/Train_path_finding]]
* [[Locomotive]]
* [[Cargo wagon]]

Railway

2019-04-23T16:36:35Z

Muppet9010: /* Connection to OpenTTD */ correct to OTTD pre-signals reference

{{Languages}}
:''For the research see [[Railway (research)]]''

'''The Railway''' is one of the main transport methods in Factorio. Although the installation of such a network can be complicated, and requires a large amount of resource and space, it is faster and more efficient than [[Belt transport system|belts]] and [[Logistic network|robot logistics]], especially over large distances.

Railway construction, however, is not understood instantly. It takes some time to learn the basics, such as automating transportation. Learning how to manage and maintain upkeep of a larger train network takes time and experience.

== Infrastructure ==

To build a railway, tracks (also called rails) must be built for the train to ride on. Typically, this is done via the [[rail planner]], but can also be done manually. Bear in mind that rails are placed on a two-tile grid, so a rail cannot be moved by only one tile.

=== Minimum manually operated railway ===
As a minimum a manually operated railway has to consist of:
* [[Rail]]s (tracks)
* [[Locomotive]]s

Locomotives can be entered and then manually operated by standing next to them and pressing the {{Key|ENTER}} button.

=== Switches ===
* There is no visual representation of a working switch, however the rails will appear to merge. Using the rail planner, the player must place a [[rail]] overlapping an existing rail to form a switch. Switches are forks in tracks that allow a train to pick between two directional options.
* The crossing of two straight tracks is not usable as switch, as trains have a limited turning radius. They do, however, connect [[Rail signal| signal blocks]] which helps prevent collisions.
* Parallel tracks do not interact with each other. However, switching from one track to the other can require extra resources if they are too close together; the track must turn away from the other parallel track and then turn back to it. This can create complicated networks of signals and, as such, one should generally not build parallel tracks unless they are spaced adequately. (Generally, 2 track widths apart works well)

[[File:fff-140-controlled-gates.gif|thumb|An example of a safe railway crossing.]]
=== Crossing tracks ===

'''Be careful when crossing tracks! Trains are one of the highest damaging entities in the game, and will kill most players instantly on contact.'''

A checklist of proper track crossing etiquette:

# Zoom out, so that you can see a train coming.
# Look left, then right.
# Check for signals nearby: If a [[rail signal]] suddenly jumps from green to red or green to yellow, a train is coming. Do not cross.
# Avoid walking near the tracks, as you do not need to be fully on the tracks to get hit.
# While it is possible to get into/out of a train while it is moving, a miss can cost your life. The sides of the train can still deal damage, as well as the player being able to slip between two rail cars.
# Heavy [[Energy shield|shields]] can be used to reduce the damage taken. In extreme cases, it is possible to stop a train with your body. This will require several shield modules to not be instantly killed, and will drain a large amount of the suit's energy.
# All entities with health will take damage getting hit by a train, so take care not to leave a [[car]] or [[tank]] on the tracks. However, this includes hostile forces!
# Trains far from a [[train stop]] will be traveling at (near) max speed, so take extra precaution when crossing and zoom out further. Trains near a [[train stop]] or signal will slow down to stop, and will be traveling slower. Trains of different configurations will also move slower or faster.

A safe railroad crossing like the example shown in the picture can be built. This works by restricting access to the tracks when an oncoming train has the rails reserved. When the player is on the rails, the signals are reserved by the [[circuit network]], and the train must stop and wait until the player leaves the tracks. When a player is inside the area crossing the tracks, the train gates are closed so the player can't get on the tracks outside the crossing. This is to completely ensure a safe crossing, and is often used on servers.

{{clear}}

== Trains ==
Train components:

{| class="wikitable"
|{{Imagelink|Locomotive}} || {{Imagelink|Cargo wagon}} || {{Imagelink|Fluid wagon}} || {{Imagelink|Artillery wagon}}
|}

[[File:Railway-assemble-train.png|thumb|left|300px|Placing a [[Cargo wagon]] so it is attached to the train.]]

* A train consists of at least one locomotive.
* Trains can have more than one locomotive, and any number of [[wagon]]s.
* Locomotives can be '''manually''' driven forwards or backwards, however, they are generally slower going backwards. The left and right movement keys are used to change direction at switches.
* Trains can only drive forwards automatically. An automatic train can drive forwards and backwards when two locomotives facing different directions are connected to the train.
* A train needs [[fuel]] to drive. Fuel can be added by inserters when the train is in manual mode or parked at a station, not when waiting at a signal or standing on automatic mode.

The locomotives' inventory is only used for [[fuel]]. To transport items or fluids [[cargo wagon]]s and/or [[fluid wagon]]s have to be attached to the train. To attach rolling stock, whether a wagon or a locomotive, the player may either prepare to place one near an existing train, where a green graphic will show the player that the stock will be attached, showing a connection between the train and the new stock. Alternatively, the player may manually connect rolling stock to trains with the rolling stock connect key, if the cargo wagon was placed far away from a train. Rolling stock can likewise be disconnected with the rolling stock disconnect key. The cargo wagons can be filled or emptied manually or by up to twelve adjacent [[Inserters]] (six on each side), while fluid wagons can be filled or emptied with up to three [[pump]]s, which will automatically connect to the nipples on top.

{{clear}}

== Stations ==
[[File:station-example-1.png|thumb|right|256px|A very minimal train station.]]
Station Components:
{| class="wikitable"
|{{Imagelink|Train stop}} || {{Imagelink|Straight rail|Rail|Rails}} || {{Imagelink|Inserter|Inserters}} or {{Imagelink|pump|pump|Pumps}}
|}

A '''train station''' is a combination of at least one [[train stop]] plus a [[storage]] and/or distribution system, used to fill or empty [[cargo wagon]]s and/or [[fluid wagon]]s, load [[fuel]] into the [[Locomotive|locomotive(s)]], load ammunition into [[artillery wagon]]s, or repair trains.

'''Don't mix up ''train stations'' with ''train stops''.''' A train station is a concept, whereas a [[train stop]] is an item.

[[Inserter]]s placed next to train tracks are used to load/unload trains at train stops. Inserters are the only way to automatically get items out of and into cargo and artillery wagons; pumps are the only way to automatically get fluids into and out of fluid wagons.

{{clear}}

== Signals ==
{| class="wikitable"
| {{Imagelink|Rail signal}} || {{Imagelink|Rail chain signal}}
|}

Rail signals are used to employ multiple trains automatically without the danger of trains crashing into each other. Rail signals split the network into blocks and ensure that only one train can be in every block at any time. Note that driving a train manually ignores all signals; so it is possible for automatic trains to crash into the player if the player ignores red/yellow signals. Always beware of automatic trains and give them the right of way.

The [[Tutorial:Train signals|train signals tutorial]] contains an in-depth explanation of rail signals, blocks and deadlocks.

=== Basic Signaling Rules ===
* There can only be one train in a block at any time. A train spanning multiple blocks occupies them all.
* A red signal means that the following block is occupied by a train.
* A yellow signal means that a train is approaching and already has the approval to enter the following block.
* [[Rail signal]]s separate a new block and reflect its state: green - free, yellow - reserved, red - occupied
* [[Rail chain signal]]s separate a new block and reflect the state of the next [[rail signal]](s): see above, blue - at least one of the paths is blocked, but not all
* A train can only pass a signal on the right of the track, or if there is a signal on both sides on the same rail segment. Of course, manual driving overrides this.

== Automated transport ==
[[File:locomotive_gui.png|thumb|300px|The wait condition tab in the locomotive's GUI.]]

Trains set on "Automatic" choose their destination stop and route on departure, and after waiting at a chain signal for five seconds, and when their destination stop disables itself by circuit condition. They choose the shortest route using a [[Railway/Train_path_finding|path finding algorithm]] that will get them to an enabled train stop with the right name, taking penalties for any apparent-at-the-time delays into account. If no such train stop exists they will skip the stop and go on to the next.

This section covers items used to make trains automatically transport items between stations. The player should be familiar with creating a rail system.

First, the player has to setup a rail system with at least two train stops, which are placed in the right-hand side of the expected train arrival direction. By hovering over the train stop with the mouse you see the positions of the vehicles for better setting up the train station (including (un)loading machinery, refueling/repair installations).

When you set up the train schedule (see below) and fuel the train, you can start the train on it's schedule by switching from manual to automatic driving mode.

=== Train schedule ===
The player can set up a list of train stations in the upper window. The train will route to stops in the given order, if it's at the end it will continue with the first. Currently, it's not possible to make a one-time schedule. Stations can be added by clicking button 2 (see picture). A pop-up appears with a list of all stop names. If you select one, another pop-up appears for you to select a wait condition.

Wait conditions are used to tell the train when to leave the station. There are 7 types of wait conditions:
* '''Time passed'''
* '''Inventory full''' – All inventories of the train are full.
* '''Inventory empty''' – Same as above, but empty.
* '''Item count''' – The train (all cargoes summed) contains a specific amount of a certain item.
* '''Circuit condition''' – The train stop is connectable to the [[circuit network]], so the signals can used for wait conditions.
* '''Inactivity''' – No items were added or removed for the specified amount of seconds.
* '''Fluid count''' – The train (all fluid wagons summed) contains a specific amount of a certain fluid.
* '''Passenger present''' - At least one [[player]] is inside any part of the train.
* '''Passenger not present''' - No players are inside any part of the train.

Hereafter the word "term" is used to describe ''one'' type of wait condition, and the words "wait condition" are used to describe the whole set of terms (it turns a bit into maths).

If you add more than one term, you can change the connection of those using the logical operators AND and OR (button 7). An AND condition will result in true if all terms are true. An OR condition will return true if at least one of the terms is true.

When mixing AND and OR terms, the logic is grouped by the OR terms. When evaluating the wait condition, the first term is evaluated along with all AND terms immediately following up to but excluding the next occurring OR term. If they all evaluate true, the wait condition evaluates true. Otherwise, evaluation continues with that next occurring OR term and all AND terms immediately following it, up to the next OR term. This continues until either an OR group evaluates true and the wait condition is satisfied, or all terms have been checked.

==== Examples ====
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Expand for examples
<div class="mw-collapsible-content">
Wait until full, up to 30 seconds:

<pre>
Full cargo inventory
OR 30 seconds passed
</pre>

Wait until cargo full, ''or'' circuit condition Oil > 3000:

<pre>
Full cargo inventory
OR Circuit condition - Oil > 3000
</pre>

Wait until empty, ''and'' 30 seconds passed, ''and'' 5 seconds of inactivity:

<pre>
Empty cargo inventory
AND 30 seconds passed
AND 5 seconds of inactivity
</pre>

Wait until iron ore is low, ''or'' copper ore is low ''and'' at least 30 seconds passed:

<pre>
Cargo: Iron ore < 500
AND 30 seconds passed
OR Cargo: Copper ore < 500
AND 30 seconds passed
</pre>

Factorio's wait condition logic is read as disjunctive normal form ([https://en.wikipedia.org/wiki/Disjunctive_normal_form DNF]), and so this last example is processed as (note the parenthesis):

<pre>((Cargo: Iron ore < 500 AND 30 seconds passed) OR (Cargo: Copper ore < 500 AND 30 seconds passed))</pre>

Which is the same as this:

<pre>((Cargo: Iron ore < 500 OR Cargo: Copper ore < 500) AND 30 seconds passed)</pre>

Unfortunately, there is no way to write that shorter form in the current UI.
</div></div>

=== Troubleshooting ===

Below are some things to verify if a rail system or train is not working.

* Is the train fueled? Ensure that the locomotive has [[fuel]] of some kind.
* Misplaced or non-functional switches? Ensure that the train can plan a path through the switches.
* Another train on the same [[Railway#Block|block]]? Make sure the path of the train is unobstructed.
* Train stops placed correctly? Make sure that the yellow arrows when hovering on the stop point towards the end or exit of the stop.
* Is the train allowed to enter signals from the right direction? Are the signals set correctly?
* If a track is supposed to be two-way, the rail signals should be opposite each other. You can verify they match up by hovering the cursor over one. For a matched pair, it will show the other.

==== No path ====
When trains cannot reach the target, a "no path" symbol pops up over the locomotive. Check:
* Can the train reach its current destination by '''only driving forward'''? Build turning slopes or place a locomotive at both ends of a train!
* Are the train stops standing in the right direction? Train stops must be on the right hand side of the track.
* If you use rail signals, check that the signals are all allowing traffic in the correct direction.
* Check for interruptions in the train tracks, drive to the station manually to check there are no rail parts missing. Especially near junctions these can be hard to spot if missing.

If you are still having problems, consider:
* Driving the train manually, and as you pass each switch, try switching to automatic. When it works, you will know the rough area of the problem.
[http://imgur.com/a/Nq2Yk A pictorial summary of typical problems].

== Achievements ==
{{Achievement|trans-factorio-express}}

== Connection to [https://www.openttd.org/ OpenTTD] ==
Factorio's railway system offers the same type of advanced railway design as [https://wiki.openttd.org/Signals#Pre-signals≈ Block Entry Pre-signal and Block Exit pre-signal pre-singals in Open Transport Tycoon Deluxe].

== See also ==
* [[Tutorial:Train signals]]
* [[Railway/Train_path_finding]]
* [[Locomotive]]
* [[Cargo wagon]]

Prototype/MapGenPresets

2019-04-20T21:50:22Z

Muppet9010: move example to own header to avoid confusion on its scope. added min/max counts to presets and prototype

== Basics ==
Prototype type: '''map-gen-presets'''

The available map gen presets. Only 1 instance of this prototype can exist.

== Mandatory properties ==

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

Must be "map-gen-presets".

=== name ===
'''Type''': [[Types/string]]

Name of the map-gen-presets. Must be "default" since only one instances of this prototype can be defined.

== Presets ==
Presets are defined as uniquely named properties of the prototype with a value of [[Types/MapGenPreset]]. 0 or more named presets can be specified within the prototype.

== Example ==
Example full prototype.
<syntaxhighlight lang="lua">
{
type = "map-gen-presets",
name = "default",
["marathon"] =
{
order = "c",
basic_settings =
{
property_expression_names = {},
},
advanced_settings =
{
difficulty_settings =
{
recipe_difficulty = defines.difficulty_settings.recipe_difficulty.expensive,
technology_difficulty = defines.difficulty_settings.technology_difficulty.expensive,
technology_price_multiplier = 4
}
}
},
["island"] =
{
order = "g",
basic_settings =
{
property_expression_names =
{
elevation = "0_17-island",
},
autoplace_controls = {},
terrain_segmentation = 1,
}
}
}</syntaxhighlight>

Prototype/DontUseEntityInEnergyProductionAchievement

2019-04-20T21:23:54Z

Muppet9010: excluded and include both support a string or a table of strings

== Basics ==
Prototype type: '''dont-use-entity-in-energy-production-achievement'''

This prototype definition is used for receiving an achievement when the player finishes the game without receiving energy from a specific energy source. This is an extension of [[Prototype/Achievement]].
== Properties ==
=== last_hour_only ===
'''Type''': [[Types/bool]]

'''Default''': false

=== minimum_energy_produced ===
'''Type''': [[Types/Energy]]

'''Default''': 0W

=== excluded ===
'''Type''': [[Types/string]] or [[Types/table]] of [[Types/string]]

This will '''not''' disable the achievement, if this entity is placed, and you have received any amount of power from it.

excluded = {"steam-engine", "steam-turbine"},

=== included ===
'''Type''': [[Types/string]] or [[Types/table]] of [[Types/string]]

This will disable the achievement, if this entity is placed, and you have received any amount of power from it. If you finish the game without receiving power from this entity, you receive the achievement.

included = "solar-panels",

Prototype/MapGenPresets

2019-04-20T21:01:06Z

Muppet9010: /* Presets */ updated example to be from base game as per Bilka's request

== Basics ==
Prototype type: '''map-gen-presets'''

The available map gen presets.

== Mandatory properties ==

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

Must be "map-gen-presets".

=== name ===
'''Type''': [[Types/string]]

Name of the map-gen-presets. Must be "default" since only one instances of this prototype can be defined.

== Presets ==
Presets are defined as uniquely named properties of the prototype with a value of [[Types/MapGenPreset]].

Example:
<syntaxhighlight lang="lua">
{
type = "map-gen-presets",
name = "default",
["marathon"] =
{
order = "c",
basic_settings =
{
property_expression_names = {},
},
advanced_settings =
{
difficulty_settings =
{
recipe_difficulty = defines.difficulty_settings.recipe_difficulty.expensive,
technology_difficulty = defines.difficulty_settings.technology_difficulty.expensive,
technology_price_multiplier = 4
}
}
},
["island"] =
{
order = "g",
basic_settings =
{
property_expression_names =
{
elevation = "0_17-island",
},
autoplace_controls = {},
terrain_segmentation = 1,
}
}
}</syntaxhighlight>

Prototype/MapGenPresets

2019-04-20T20:49:56Z

Muppet9010: /* Presets */ add Example

Prototype/MapGenPresets

2019-04-20T20:48:18Z

Muppet9010: clarify presets as a special thing as they are defined so differently to all other prototype properties.

Types/CollisionMask

2019-04-14T12:51:34Z

Muppet9010: /* "not-colliding-with-itself" */ clarify after developer response and further testing

The collision mask is specified as an Array ([[Types/table]]) of strings. Every entry is a specification of one layer the object collides with or a special collision option.

== Layers ==
* ground-tile
* water-tile
* resource-layer
* doodad-layer
* floor-layer
* item-layer
* ghost-layer
* object-layer
* player-layer
* train-layer
* layer-11
* layer-12
* layer-13
* layer-14
* layer-15

Layer-11 through layer-15 are currently unused by the core game.

== Collision options ==
These are not collision masks, instead they control other aspects of collision, but they are still specified here.
=== "not-colliding-with-itself" ===
Any 2 entities that both have this option enabled on their prototype and have an identical collision mask layers list will not collide. Other collision mask options are not included in the identical layer list check. This does mean that 2 different prototypes with the same collision mask layers and this option enabled will not collide.

=== "consider-tile-transitions" ===
=== "colliding-with-tiles-only" ===

== Default collision masks ==
The default collision masks of all entity types can be found [[Prototype/Entity#collision_mask|here]].

Example (Most common collision mask of buildings):
<syntaxhighlight lang="lua">collision_mask = { "item-layer", "object-layer", "player-layer", "water-tile"}</syntaxhighlight>