Official Factorio Wiki - User contributions [en]

Console

2025-07-07T03:54:42Z

Oconnor664: mention quality in the add items section

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

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

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

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

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

== Normal commands ==

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

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

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

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

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

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

There are several god-mode items available:

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

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

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

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

== World manipulation scripts ==

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

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

=== Hide revealed map ===

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

=== Reveal all generated map ===

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

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

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

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

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

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

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

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

=== Completely turn off pollution ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Add new water patch ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

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

=== Kill all nearby enemies ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

{{C|Modding}}

Aquilo

2024-11-12T19:08:54Z

Oconnor664: mention other Aquilo unlocks

{{Languages}}
{{Stub}}
{{About/Space age}}
[[File:aquilo_preview.png|210px|right]]'''Aquilo''' a desolate, freezing ocean planet. Its surface consists solely of a vast ocean of liquid ammonia, with the occasional floating iceberg.
=== Required Research ===
{{NavboxIconLink|Planet_discovery_Aquilo_(research)|Planet Discovery Aquilo}}

=== Exclusive items ===
The following items are unlocked on Aquilo:
*{{NavboxIconLink|Cryogenic plant}}{{SA}}
*{{NavboxIconLink|Cryogenic science pack}}{{SA}}
*{{NavboxIconLink|Fusion generator}}{{SA}}
*{{NavboxIconLink|Fusion reactor}}{{SA}}
*{{NavboxIconLink|Railgun turret}}{{SA}}
*{{NavboxIconLink|Railgun}}{{SA}}
*{{NavboxIconLink|Captive biter spawner}}{{SA}}
*{{NavboxIconLink|Portable fusion reactor}}

==Space routes==
{{NavboxIconLink|Aquilo}} is connected to 2 other planets, {{NavboxIconLink|Gleba}}{{SA}} and {{NavboxIconLink|Fulgora}}{{SA}}, along with the {{NavboxIconLink|Solar system edge}}{{SA}}

{| class="wikitable"
|+ Planet Distance
|-
! Planet !! Distance (km)
|-
| {{NavboxIconLink|Gleba}}{{SA}}|| 30,000
|-
| {{NavboxIconLink|Fulgora}}{{SA}}|| 30,000
|-
| {{NavboxIconLink|Solar system edge}}{{SA}}|| 100,000
|}

Asteroid rate graphs:

{| class="wikitable" style="text-align:center;"
|-
| [[File:Asteroid_chart_Gleba_Aquilo.png]] Space route from {{NavboxIconLink|Gleba }} to {{NavboxIconLink|Aquilo}}
| [[File:Asteroid_chart_Fulgora_Aquilo.png]] Space route from {{NavboxIconLink|Fulgora}} to {{NavboxIconLink|Aquilo}}
| [[File:Asteroid_chart_Aquilo_Solar_System_Edge.png]] Space route from {{NavboxIconLink|Aquilo}} to {{NavboxIconLink|Solar system edge}}
|}

Graph legend:
<table class="wikitable">
<tr>
<th>Asteroid type</th>
<th>Chunk</th>
<th>Medium</th>
<th>Big</th>
</tr>
<tr>
<td>[[File:Metallic asteroid chunk.png|32px]] Metallic</td>
<td>● Blue</td>
<td>● Red</td>
<td>● Cyan</td>
</tr>
<tr>
<td>[[File:Carbonic asteroid chunk.png|32px]] Carbonic</td>
<td>● Orange</td>
<td>● Yellow</td>
<td>● Brown</td>
</tr>
<tr>
<td>[[File:Oxide asteroid chunk.png|32px]] Oxide</td>
<td>● Green</td>
<td>● Magenta</td>
<td>● Purple</td>
</tr>
</table>

==Orbit==

===Properties===
{| class="wikitable"
|-
! Property !! Value
|-
| Solar Power || 60%
|-
|}

{| class="wikitable"
|+ Asteroid Spawning Types
|-
! [[Asteroids| Asteroid]] Type !! Spawn Ratio
|-
| {{NavboxIconLink|Metallic asteroid chunk}} {{SA}}|| 1
|-
| {{NavboxIconLink|Carbonic asteroid chunk}} {{SA}}|| 2
|-
| {{NavboxIconLink|Oxide asteroid chunk}} {{SA}}|| 20
|-
| {{NavboxIconLink|Promethium asteroid chunk}} {{SA}}|| 0
|}

{| class="wikitable"
|+ Asteroid Spawning Sizes
|-
! [[Asteroids| Asteroid]] Size !! Spawn %
|-
| Chunk|| .10
|-
| Medium|| 0
|-
| Big || 0.25
|-
| Huge || 0
|}

'''Note:'''
*Chunks spawn at Nauvis at 1.25%
*Huge Asteroids only spawn past [[Aquilo]]{{SA}}

==Surface==

===Properties===
{| class="wikitable"
|+ Gleba Surface Properties
|-
! Property !! Value
|-
| Pollutant Type || None
|-
| Day Night Cycle || 20 Minutes
|-
| Magnetic Field|| 10
|-
| Solar Power || 01%
|-
| Pressure || 300
|-
| Gravity || 15
|}

=== Natural Resources ===
In terms of directly exploitable natural resources, Aquilo has:
* {{NavboxIconLink|Ammoniacal solution}}{{SA}}
* {{NavboxIconLink|Lithium brine}}{{SA}}
* {{NavboxIconLink|Fluorine}}{{SA}}
* {{NavboxIconLink|Crude oil}}

With crude oil being the only non-exclusive resource to Aquilo, excluding ice obtained from [[Lithium Ice Formation]].

Stone, iron and copper (and coal if desired) need to be imported from other planets as Aquilo lacks ways to obtain these from the environment.

== Access to basic resources ==

* {{NavboxIconLink|Water}} can be obtained via {{NavboxIconLink|Ammoniacal solution separation}} and {{NavboxIconLink|Ice melting}}
* {{NavboxIconLink|Stone}} is not available and must be shipped in from other planets
* {{NavboxIconLink|Iron ore}} is not available and must be shipped in from other planets
* {{NavboxIconLink|Copper ore}} is not available and must be shipped in from other planets
* {{NavboxIconLink|Coal}} is not available and must be shipped in from other planets
* {{NavboxIconLink|Crude oil}} can be obtained using pumpjacks as normal

== Mechanics ==
=== Freezing ===
Aquilo is brutally cold. Most entities will freeze and stop working unless heated by a [[heat pipe]] in an adjacent tile. Heat can be generated by the [[nuclear reactor]] or [[heating tower]]. Buildings also cannot be placed on the surface of the iceberg itself; [[concrete]] (or its variants) must be placed underneath as an insulator. The harshly low temperature will also make [[construction robot]]s and [[logistic robot]]s much weaker, making them consume 5 times more power than normal.

Aquilo is also far from the sun, and so [[solar panel]]s only output at 1% of their rate on Nauvis, or 0.6 kW during the day.

== Gallery ==
<gallery widths="300px" heights="200px">
aquilo_landscape.png|Example landscape of Aquilo.
aquilo_landscape_main_menu.png|Aquilo seen on the expansion's title screen.
</gallery>

== See also ==
* {{NavboxIconLink|Fulgora}}{{SA}}
* {{NavboxIconLink|Gleba}} {{SA}}
* {{NavboxIconLink|Vulcanus}} {{SA}}

== Trivia ==
* In mythology, Aquilo is the Roman god of the north wind, storms, and winter.

== History ==
{{history|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

{{C|Planets}}
{{SpaceNav}}

Gleba

2024-11-12T19:06:38Z

Oconnor664: mention module unlocks on Gleba

{{Languages}}
{{Stub}}
{{About/Space age}}
[[File:gleba_preview.png|210px|right]]'''Gleba''' is a moist, agricultural planet with fungal hills and swampy lowlands.

It is home to the [[pentapods]]{{SA}}, which are spider-like [[enemies]] who are attracted to the scent of biological processing, similar to the way that [[Nauvis]] creatures negatively respond to [[pollution]]. One of the most prominent traits of Gleba is that nearly everything takes a biological form.
=== Required Research ===
{{NavboxIconLink|Planet_discovery_Gleba_(research)|Planet Discovery Gleba}}

=== Exclusive Items ===
The following items are unlocked on Gleba:
* {{NavboxIconLink|Agricultural tower}} {{SA}}
* {{NavboxIconLink|Heating tower}} {{SA}}
* {{NavboxIconLink|Biochamber}} {{SA}}
* {{NavboxIconLink|Biolab}} {{SA}}
* {{NavboxIconLink|Stack inserter}} {{SA}}
* {{NavboxIconLink|Rocket turret}} {{SA}}
* {{NavboxIconLink|Spidertron}}
* {{NavboxIconLink|Productivity module 3}}
* {{NavboxIconLink|Efficiency module 3}}

==Space routes==
{{NavboxIconLink|Gleba}} is connected to 4 other planets: {{NavboxIconLink|Nauvis}}, {{NavboxIconLink|Vulcanus}}{{SA}}, {{NavboxIconLink|Fulgora}}{{SA}}, and {{NavboxIconLink|Aquilo}}{{SA}}.

{| class="wikitable"
|+ Planet Distance
|-
! Planet !! Distance (km)
|-
| {{NavboxIconLink|Nauvis}}|| 15,000
|-
| {{NavboxIconLink|Vulcanus}}{{SA}}|| 15,000
|-
| {{NavboxIconLink|Fulgora}}{{SA}}|| 15,000
|-
| {{NavboxIconLink|Aquilo}} {{SA}}|| 30,000
|}

Asteroid rate graphs:

{| class="wikitable" style="text-align:center;"
|-
| [[File:Asteroid_chart_Nauvis_Gleba.png]] Space route from {{NavboxIconLink|Nauvis}} to {{NavboxIconLink|Gleba}}
| [[File:Asteroid_chart_Vulcanus_Gleba.png]] Space route from {{NavboxIconLink|Vulcanus}} to {{NavboxIconLink|Gleba}}
|-
| [[File:Asteroid_chart_Gleba_Fulgora.png]] Space route from {{NavboxIconLink|Gleba }} to {{NavboxIconLink|Fulgora}}
| [[File:Asteroid_chart_Gleba_Aquilo.png]] Space route from {{NavboxIconLink|Gleba }} to {{NavboxIconLink|Aquilo}}
|}

Graph legend:
<table class="wikitable">
<tr>
<th>Asteroid type</th>
<th>Chunk</th>
<th>Medium</th>
<th>Big</th>
</tr>
<tr>
<td>[[File:Metallic asteroid chunk.png|32px]] Metallic</td>
<td>● Blue</td>
<td>● Red</td>
<td>● Cyan</td>
</tr>
<tr>
<td>[[File:Carbonic asteroid chunk.png|32px]] Carbonic</td>
<td>● Orange</td>
<td>● Yellow</td>
<td>● Brown</td>
</tr>
<tr>
<td>[[File:Oxide asteroid chunk.png|32px]] Oxide</td>
<td>● Green</td>
<td>● Magenta</td>
<td>● Purple</td>
</tr>
</table>

==Orbit==

===Properties===
{| class="wikitable"
|-
! Property !! Value
|-
| Solar Power || 200%
|-
|}

{| class="wikitable"
|+ Asteroid Spawning Types
|-
! [[Asteroids| Asteroid]] Type !! Spawn Ratio
|-
| {{NavboxIconLink|Metallic asteroid chunk}} {{SA}}|| 2
|-
| {{NavboxIconLink|Carbonic asteroid chunk}} {{SA}}|| 5
|-
| {{NavboxIconLink|Oxide asteroid chunk}} {{SA}}|| 1
|-
| {{NavboxIconLink|Promethium asteroid chunk}} {{SA}}|| 0
|}

{| class="wikitable"
|+ Asteroid Spawning Sizes
|-
! [[Asteroids| Asteroid]] Size !! Spawn %
|-
| Chunk|| .30
|-
| Medium|| .25
|-
| Big || 0
|-
| Huge || 0
|}

'''Note:'''
*Chunks spawn at Nauvis at 1.25%
*Huge Asteroids only spawn past [[Aquilo]]{{SA}}

==Surface==

===Properties===
{| class="wikitable"
|+ Gleba Surface Properties
|-
! Property !! Value
|-
| Pollutant Type || Spores
|-
| Day Night Cycle || 10 Minutes
|-
| Magnetic Field|| 10
|-
| Solar Power || 50%
|-
| Pressure || 2000
|-
| Gravity || 20
|}

===Biomes===

Gleba hosts multiple biomes.

'''Deep water'''
An impassable

'''Shallows'''
A walkable murky water, filled with watercanes.
'''Green lowlands'''

'''Red lowlands'''

'''Green midlands'''

'''Red midlands'''

'''Highlands'''

== Mechanics ==
=== {{NavboxIconLink|Spoilage}} ===
Most biological products on Gleba are "spoilable". A spoilable item has an inherent timer attached to it, which begins at the item's creation. When the timer reaches 0, the item is transformed into [[spoilage]],{{SA}} with a few exceptions. This process is inevitable and cannot be stopped.

The exact time differs per item, ranging anywhere from a few minutes to 2 hours. This means that item throughput is more important than ever on Gleba, and buffering a large stockpile is ineffective, as items can spoil within containers.

When crafting with spoilable items, the final product will inherit the freshness value of the ingredients. The three exceptions are [[Iron Bacteria|iron]] and [[copper bacteria]] cultivation, [[pentapod eggs]] and [[fish]] breeding, whose recipes will always result in a 100% fresh product, regardless of the freshness of the ingredients.

When crafting with two different spoilable items of different freshness values, like in the [[agricultural science pack]]{{SA}} and [[bioflux]]{{SA}} recipes, the final product's freshness is determined by the average of the ingredients' freshness.

The agricultural science pack does spoil, which will gradually decrease its research value, so the player is incentivized to build a fast space platform to bring them back to Nauvis.

Spoilable items are used as ingredients in a few non-spoilable items, such as the [[biochamber]]{{SA}}. In these, the freshness value of the ingredients do not matter in the product being produced.

{| class="wikitable"
|+ Spoilable Item Times
|-
! Item !! Time !! Special effect on spoiling
|-
| {{imagelink|Agricultural science pack|space-age=yes}} || 1 hour ||
|-
| {{imagelink|Biter egg|space-age=yes}} || 30 minute || Spawns a Big Biter
|-
| {{imagelink|Bioflux|space-age=yes}} || 2 hours ||
|-
| {{imagelink|Copper bacteria|space-age=yes}} || 1 minute || Turns into [[copper ore]]
|-
| {{imagelink|Raw fish}} || 2 hours, 5 minutes, 50 seconds ||
|-
| {{imagelink|Iron bacteria|space-age=yes}} || 1 minute || Turns into [[iron ore]]
|-
| {{imagelink|Jelly|space-age=yes}} || 4 minutes ||
|-
| {{imagelink|Jellynut|space-age=yes}} || 1 hour ||
|-
| {{imagelink|Nutrients|space-age=yes}} || 5 minutes ||
|-
| {{imagelink|Pentapod egg|space-age=yes}} || 15 minutes || Spawns a wriggler
|-
| {{imagelink|Yumako|space-age=yes}} || 1 hour ||
|-
| {{imagelink|Yumako mash|space-age=yes}} || 3 minutes ||
|-
|}

== Access to basic resources ==

* {{NavboxIconLink|Water}} is readily available using offshore pumps
* {{NavboxIconLink|Stone}} can be mined from patches on the surface as normal
* {{NavboxIconLink|Iron ore}} can be obtained from {{NavboxIconLink|Iron bacteria}}, which can be cultivated in a {{NavboxIconLink|Biochamber}} using {{NavboxIconLink|Iron bacteria cultivation}}
* {{NavboxIconLink|Copper ore}} can be obtained from {{NavboxIconLink|Copper bacteria}}, which can be cultivated in a biochamber using {{NavboxIconLink|Copper bacteria cultivation}}
* {{NavboxIconLink|Coal}} can be obtained via {{NavboxIconLink|Coal synthesis}}
* {{NavboxIconLink|Crude oil}} is not available. However:
** {{NavboxIconLink|Plastic bar}}s can be obtained from {{NavboxIconLink|Bioplastic}}
** {{NavboxIconLink|Sulfur}} can be obtained from {{NavboxIconLink|Biosulfur}}
** {{NavboxIconLink|Lubricant}} can be obtained from {{NavboxIconLink|Biolubricant}}
** {{NavboxIconLink|Rocket fuel}} can be obtained from {{NavboxIconLink|Rocket fuel from jelly}}
** {{NavboxIconLink|Heavy oil}} can be obtained using {{NavboxIconLink|Coal liquefaction}}, if the initial heavy oil is shipped in from another planet

== See also ==
* {{NavboxIconLink|Aquilo}} {{SA}}
* {{NavboxIconLink|Fulgora}}{{SA}}
* {{NavboxIconLink|Nauvis}}
* {{NavboxIconLink|Vulcanus}} {{SA}}

== Gallery ==
<gallery widths="300px" heights="200px">
gleba_landscape.png|Example landscape of Gleba.
</gallery>

== Trivia ==
* In biology, a gleba is a fleshy, spore-filled inner mass of some fungi like the puffball.
* During development, Gleba was once named ''Bacchus'', after the Roman god of fertility, orchards, and vegetation.

== History ==
{{history|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

{{C|Planets}}
{{SpaceNav}}

Fulgora

2024-11-12T19:04:31Z

Oconnor664: mention other Fulgora unlocks

{{Languages}}
{{Stub}}
{{About/Space age}}
[[file:fulgora_preview.png|210px|right]]'''Fulgora''' is a new barren desert planet. Its surface is split between island-like plateaus, and deep oilsands. During the night, the planet is ravaged by lightning storms, damaging buildings.
=== Required Research ===
{{NavboxIconLink|Planet_discovery_Fulgora_(research)|Planet Discovery Fulgora}}

=== Exclusive Items ===
The following items are unlocked on Fulgora:
* [[File:Electromagnetic science pack (research).png|32px]] [[Electromagnetic science pack]]{{SA}}
* [[File:electromagnetic_plant.png|32px]] [[Electromagnetic plant]]{{SA}}
* [[File:Lightning collector.png|32px]] [[Lightning collector]]{{SA}}
* [[File:Lightning rod.png|32px]] [[Lightning rod]]{{SA}}
* [[File:Recycler.png|32px]] [[Recycler]]{{SA}}
* [[File:Tesla turret.png|32px]] [[Tesla turret]]{{SA}}

The following items are unlocked on Fulgora but can be crafted elsewhere:
* [[Mech armor]]
* [[Personal battery MK3]]
* [[Energy shield MK2]]
* [[Personal roboport MK2]]
* [[Quality module 3]]

==Space routes==
{{NavboxIconLink|Fulgora}} is connected to 3 other planets: {{NavboxIconLink|Nauvis}}, {{NavboxIconLink|Gleba}}{{SA}}, and {{NavboxIconLink|Aquilo}}{{SA}}.

{| class="wikitable"
|+ Planet Distance
|-
! Planet !! Distance (km)
|-
| {{NavboxIconLink|Nauvis}}|| 15,000
|-
| {{NavboxIconLink|Gleba}}{{SA}}|| 15,000
|-
| {{NavboxIconLink|Aquilo}}{{SA}}|| 30,000
|}

Asteroid rate graphs:

{| class="wikitable" style="text-align:center;"
|-
| [[File:Asteroid_chart_Nauvis_Fulgora.png]] Space route from {{NavboxIconLink|Nauvis}} to {{NavboxIconLink|Fulgora}}
| [[File:Asteroid_chart_Gleba_Fulgora.png]] Space route from {{NavboxIconLink|Gleba }} to {{NavboxIconLink|Fulgora}}
| [[File:Asteroid_chart_Fulgora_Aquilo.png]] Space route from {{NavboxIconLink|Fulgora}} to {{NavboxIconLink|Aquilo}}
|}

Graph legend:
<table class="wikitable">
<tr>
<th>Asteroid type</th>
<th>Chunk</th>
<th>Medium</th>
<th>Big</th>
</tr>
<tr>
<td>[[File:Metallic asteroid chunk.png|32px]] Metallic</td>
<td>● Blue</td>
<td>● Red</td>
<td>● Cyan</td>
</tr>
<tr>
<td>[[File:Carbonic asteroid chunk.png|32px]] Carbonic</td>
<td>● Orange</td>
<td>● Yellow</td>
<td>● Brown</td>
</tr>
<tr>
<td>[[File:Oxide asteroid chunk.png|32px]] Oxide</td>
<td>● Green</td>
<td>● Magenta</td>
<td>● Purple</td>
</tr>
</table>

==Orbit==

===Properties===
{| class="wikitable"
|-
! Property !! Value
|-
| Solar Power || 120%
|-
|}

{| class="wikitable"
|+ Asteroid Spawning Types
|-
! [[Asteroids| Asteroid]] Type !! Spawn Ratio
|-
| {{NavboxIconLink|Metallic asteroid chunk}} {{SA}}|| 4
|-
| {{NavboxIconLink|Carbonic asteroid chunk}} {{SA}}|| 3
|-
| {{NavboxIconLink|Oxide asteroid chunk}} {{SA}}|| 1
|-
| {{NavboxIconLink|Promethium asteroid chunk}} {{SA}}|| 0
|}

{| class="wikitable"
|+ Asteroid Spawning Sizes
|-
! [[Asteroids| Asteroid]] Size !! Spawn %
|-
| Chunk|| .25
|-
| Medium|| .25
|-
| Big || 0
|-
| Huge || 0
|}

'''Note:'''
*Chunks spawn at Nauvis at 1.25%
*Huge Asteroids only spawn past [[Aquilo]]{{SA}}

==Surface==

===Properties===
{| class="wikitable"
|+ Gleba Surface Properties
|-
! Property !! Value
|-
| Pollutant Type || None
|-
| Day Night Cycle || 3 Minutes
|-
| Magnetic Field|| 99
|-
| Solar Power || 20%
|-
| Pressure || 800
|-
| Gravity || 8
|}

== Biomes ==
Fulgora is split between two distinct biomes.
* '''Plateaus''' are islands dotted around the landscape. They are the only biome where factories can be built. Some plateaus are home to [[alien ruins]], which have rudimentary lightning rods, which can protect your buildings until unlocking your own lightning rods. Other plateaus hold [[scrap]]{{SA}}, Fulgora's sole resource.
* '''Oilsands''' are the lowlands between the plateaus. No buildings can be built in them except for [[rail support]]s{{SA}}. You can walk through them, but occasional oilpatches will slow you to a crawl. An [[offshore pump]] can be placed on the edge of oilsands to produce an unlimited amount of [[heavy oil]].

=== Terrain ===
Fulgoran terrain is mainly composed of oillands, on which nothing except for [[rail support]]s can be built. Traversal by foot across the oillands is possible, but slow. The oillands are further divided into deep and shallow areas, with deep areas slowing down player movement even further and not even allowing for rail supports to be built without research. 

However, the oillands are also scattered with islands of various sizes, on which normal construction is possible. At first, these are the only place on Fulgora where factories can be built, as [[foundation]] for building on top of the oillands requires research that can not be performed until much later.

The islands come in three size classes:
* Small islands with high amounts of resources, but with little room to build on
* Medium islands with lower amounts of resources, and with sufficient room for a small factory
* Large islands with no resources, but with enough room to build the main part of a medium-sized factory

It is possible for two or more islands to overlap, potentially creating an even larger island that does have local resources. However, most islands are detached, meaning that transport between islands will have to occur by train. In many cases, the distance between two islands is also too vast for [[roboport]]s or [[big electric pole]]s to reach, thus requiring local [[logistic network|logistic]] and [[electric system|electric networks]] to be built, as neither roboports nor power poles can be built on the oillands without [[foundation]].

== Mechanics ==
=== Lightning ===
During [[time|nighttime]], dense thunderstorms occur on Fulgora, with frequent lightning strikes occurring across the surface. Lightning will strike each chunk once, every 10 seconds or so ( lightnings_per_chunk_per_tick = 1 / (60 * 10), --cca once per chunk every 10 seconds (600 ticks) )

If a lightning strike is set to occur near a [[lightning rod]], [[lightning collector]], or [[fulgoran lightning attractor]], then the lightning will always hit said entity, rendering the lightning harmless. However, if such an entity can not be found, the lightning will strike where it occurs, causing damage to nearby entities.

Lightning will target entities based on priority first and then random for any entity not on the priority list (Higher priority gets hit first)
{| class="wikitable"
|+ Lightning priority
|-
! Entity !! Priority Value
|-
| {{NavboxIconLink|Lightning collector}}{{SA}} || 10,000
|-
| {{NavboxIconLink|Lightning rod}}{{SA}} || 1,000
|-
| {{NavboxIconLink|Fulgoran ruin vault}} || 95
|-
| {{NavboxIconLink|Fulgoran ruin colossal}} || 94
|-
| {{NavboxIconLink|Fulgoran ruin huge}} || 93
|-
| {{NavboxIconLink|Fulgoran ruin big}} || 92
|-
| {{NavboxIconLink|Fulgoran ruin medium}} || 91
|}

The following items have a priority of 1
* {{NavboxIconLink|pipe}}
* {{NavboxIconLink|pump}}
* {{NavboxIconLink|offshore pump}}
* {{NavboxIconLink|electric poles}}
* {{NavboxIconLink|power switch}}
* {{NavboxIconLink|logistic robot}}
* {{NavboxIconLink|construction robot}}
* Anything with the "Metal" impact soundset
 
The following entities cannot be struck by the lightning
* {{NavboxIconLink|Rail support}}
* {{NavboxIconLink|Rail}}
* {{NavboxIconLink|Rail ramp}}
* {{NavboxIconLink|Rail signal}}
* {{NavboxIconLink|Rail chain signal}}
* {{NavboxIconLink|Locomotive}}
* {{NavboxIconLink|Artillery wagon}}
* {{NavboxIconLink|Cargo wagon}}
* {{NavboxIconLink|Fluid wagon}}
* {{NavboxIconLink|Wall}}
* {{NavboxIconLink|tree}}
* Any item that counts as rock for "filtered destruction" (I assume this means recycler)

When a [[lightning rod]] or a [[lightning collector]] is struck by lightning, it will generate a brief but powerful burst of electric energy, which can be utilized by connecting it to the [[electric system|electric network]]. With enough [[accumulator]]s to last during daytime or between lightning strikes, this can serve as the factory's main power source.

With this, lightning on Fulgora become both a curse and a blessing: Players must keep their factory covered by lightning rods or collectors to avoid damage, and nighttime exploration becomes dangerous and risky. However, to an established base, lightning become a convenient source of electric energy, which is especially important given the weak [[solar panel|solar output]] on Fulgora's surface and the difficulty of setting up a global electric network on Fulgora before [[foundation]] becomes available.

=== Natural resources ===
Aside from numerous items that can be collected by mining ancient ruins, only two "natural" resources occur on Fulgora, those being [[heavy oil]] and [[scrap]].

Heavy oil can be obtained in infinite and non-diminishing amounts by placing an [[offshore pump]] on the shore of an island, allowing it to collect heavy oil directly from the oillands.

Scrap is found in deposits on small and medium sized islands, as if it were an ore. However, in stark contrast to most other natural resources, scrap is not directly processed into a single basic resource like [[iron plate|iron]] or [[copper plate]]s using traditional production methods. Rather, it is [[recycler|recycled]] to produce a variety of items: 
*{{NavboxIconLink|Ice}} {{SA}}
*{{NavboxIconLink|Stone}}
*{{NavboxIconLink|Holmium ore}} {{SA}}
*{{NavboxIconLink|Concrete}}
*{{NavboxIconLink|Solid fuel}}
*{{NavboxIconLink|Steel plate}}
*{{NavboxIconLink|Copper_cable|Copper Cable}}
*{{NavboxIconLink|Iron gear wheel}}
*{{NavboxIconLink|battery}}
*{{NavboxIconLink|Advanced circuit}}
*{{NavboxIconLink|Processing unit}}
*{{NavboxIconLink|Low density structure}}

Since this list includes intermediate products, such as [[processing unit]]s, but no iron or copper plates, players are often forced to further recycle many of these items in order to obtain their ingredients. Players are thus left with the decision of what items to recycle, all while having to avoid clobbering their belts with unused resources. 

== Access to basic resources ==

* {{NavboxIconLink|Water}} can be obtained from {{NavboxIconLink|Ice}} via {{NavboxIconLink|Ice melting}}
* {{NavboxIconLink|Stone}} comes from recycling {{NavboxIconLink|Scrap}}
* {{NavboxIconLink|Iron ore}} is not available, but {{NavboxIconLink|Iron plate}} and {{NavboxIconLink|Concrete}} can be obtained by recycling {{NavboxIconLink|Scrap}}
* {{NavboxIconLink|Copper ore}} is not available, but {{NavboxIconLink|Copper plate}} can be obtained by recycling {{NavboxIconLink|Scrap}}
* {{NavboxIconLink|Coal}} cannot be obtained and must be shipped in from other planets. However:
** {{NavboxIconLink|Plastic bar}}s can be obtained by by recycling {{NavboxIconLink|Scrap}}
* {{NavboxIconLink|Crude oil}} is not available, but {{NavboxIconLink|Heavy oil}} is readily available using offshore pumps

== Gallery ==
<gallery widths="300px" heights="200px">
fulgora_landscape.png|Example landscape of Fulgora.
</gallery>

== Trivia ==
* The planet's ruins suggest that an unknown civilization once existed there before the game's events.
* In mythology, Fulgora is the Roman personification of lightning, and a shieldmaiden to the god of thunder, Jupiter.

== See also ==
* {{NavboxIconLink|Aquilo}} {{SA}}
* {{NavboxIconLink|Vulcanus}}{{SA}}
* {{NavboxIconLink|Gleba}} {{SA}}

== History ==
{{history|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

{{C|Planets}}
{{SpaceNav}}

Vulcanus

2024-11-12T19:01:31Z

Oconnor664: mention other Vulcanus unlocks

{{Languages}}
{{Stub}}
{{About/Space age}}
[[File:volcanus_preview.png|210px|right]]'''Vulcanus''' is a hot volcanic planet with mountainous volcanoes, rivers of lava, plains of ash, and sulfuric acid geysers. 

It is home to [[Demolisher|demolishers]]{{SA}}, a large boss‐like [[Enemies|enemy]] that defends its territory. There's no [[pollution]] on Vulcanus.
=== Required Research ===
{{NavboxIconLink|Planet discovery Vulcanus (research)|Planet discovery Vulcanus}}

=== Exclusive Recipes ===
The following items and recipes can only be crafted/run on Vulcanus:
* [[File:Metallurgic science pack.png|32px]] [[Metallurgic science pack]] {{SA}}
* [[File:Foundry.png|32px]] [[Foundry]] {{SA}}
* [[File:Big mining drill.png|32px]] [[Big mining drill]] {{SA}}
* [[File:Turbo transport belt.png|32px]] [[Turbo transport belt]] {{SA}}
* [[File:Turbo underground belt.png|32px]] [[Turbo underground belt]] {{SA}}
* [[File:Turbo splitter.png|32px]] [[Turbo splitter]] {{SA}}
* [[File:Acid neutralisation.png|32px]] [[Acid neutralisation]] {{SA}}

The following items and recipes are unlocked on Vulcanus but can be crafted elsewhere:

* [[Artillery turret]]
* [[Artillery wagon]]
* [[Coal liquefaction]]
* [[Speed module 3]]

==Space routes==
{{NavboxIconLink|Vulcanus}} is connected to 2 other planets: {{NavboxIconLink|Nauvis}} and {{NavboxIconLink|Gleba}}{{SA}}.

{| class="wikitable"
|+ Planet Distance
|-
! Planet !! Distance (km)
|-
| {{NavboxIconLink|Nauvis}}|| 15,000
|-
| {{NavboxIconLink|Gleba}}{{SA}}|| 15,000
|-
|}

Asteroid rate graphs:

{| class="wikitable" style="text-align:center;"
|-
| [[File:Asteroid_chart_Nauvis_Vulcanus.png]] Space route from {{NavboxIconLink|Nauvis}} to {{NavboxIconLink|Vulcanus}}
| [[File:Asteroid_chart_Vulcanus_Gleba.png]] Space route from {{NavboxIconLink|Vulcanus}} to {{NavboxIconLink|Gleba}}
|}

Graph legend:
<table class="wikitable">
<tr>
<th>Asteroid Type</th>
<th>Chunk</th>
<th>Medium</th>
</tr>
<tr>
<td>[[File:Metallic asteroid chunk.png|32px]] [[Asteroids|Metallic]] {{SA}}</td>
<td>● Blue</td>
<td>● Red</td>
</tr>
<tr>
<td>[[File:Carbonic asteroid chunk.png|32px]] [[Asteroids|Carbonic]] {{SA}}</td>
<td>● Orange</td>
<td>● Yellow</td>
</tr>
<tr>
<td>[[File:Oxide asteroid chunk.png|32px]] [[Asteroids|Oxide]] {{SA}}</td>
<td>● Green</td>
<td>● Magenta</td>
</tr>
</table>

==Orbit==

===Properties===
{| class="wikitable"
|-
! Property !! Value
|-
| Solar Power || 600%
|-
|}

{| class="wikitable"
|+ Asteroid Spawning Types
|-
! [[Asteroids| Asteroid]] Type !! Spawn Ratio
|-
| {{NavboxIconLink|Metallic asteroid chunk}} {{SA}}|| 5
|-
| {{NavboxIconLink|Carbonic asteroid chunk}} {{SA}}|| 2
|-
| {{NavboxIconLink|Oxide asteroid chunk}} {{SA}}|| 1
|-
| {{NavboxIconLink|Promethium asteroid chunk}} {{SA}}|| 0
|}

{| class="wikitable"
|+ Asteroid Spawning Sizes
|-
! [[Asteroids| Asteroid]] Size !! Spawn %
|-
| Chunk|| .20
|-
| Medium|| .25
|-
| Big || 0
|-
| Huge || 0
|}

'''Note:'''
*Chunks spawn at Nauvis at 1.25%
*Huge Asteroids only spawn past [[Aquilo]]{{SA}}

==Surface==

===Properties===
{| class="wikitable"
|+ Gleba Surface Properties
|-
! Property !! Value
|-
| Pollutant Type || Spores
|-
| Day Night Cycle || 1.5 Minutes
|-
| Magnetic Field|| 25
|-
| Solar Power || 400%
|-
| Pressure || 4000
|-
| Gravity || 40
|}

== Biomes ==
Vulcanus has three distinct biomes.
* '''Ashlands''' are plateaus speckled with sparse vegetation and deposits of [[coal]]. They are home to leafless alien trees. They are relatively free of cliffs and lava, making them ideal for building.
* '''Lava basins''' are filled with winding lava rivers. Within them are deposits of [[tungsten ore]]{{SA}}, which can only be mined using the big mining drill.
* '''Mountains''' are large volcanoes, covered in cliffs and with a large lava pool at their center. They are home to [[sulfuric acid]] geysers and [[calcite]]{{SA}}. 

==Demolisher Territories==

Native to Vulcanus are the giant centipede-like enemies known as "demolishers".

Demolishers have well-defined territories. On the map, these territories are outlined by an opaque, bright red line and the inside is marked by diagonal, translucent, red lines. Only one demolisher will spawn per territory, and the territories themselves do not overlap. However, they are tightly packed, as they follow a Voronoi-like pattern. At the start of the game, only Vulcanus' starting area is not inside a demolisher's territory.

When left alone, a demolisher will patrol the border of its territory. However, if players build inside of a demolisher's territory, it will soon make a beeline towards these buildings with the intent of destroying them. Building inside of a demolisher's territory is therefore extremely risky and dangerous.

The death of a demolisher is permanent, as they only spawn during world generation. Likewise, upon the death of a demolisher, its territory permanently becomes free for the player to use, as other demolishers will not try to expand their territories.

== Access to basic resources ==

* {{NavboxIconLink|Water}} can be obtained via {{NavboxIconLink|Acid neutralisation}} and {{NavboxIconLink|Steam condensation}}
* {{NavboxIconLink|Stone}} is a byproduct of processing {{NavboxIconLink|Lava}} into molten iron/copper
* {{NavboxIconLink|Iron ore}} is not available, but {{NavboxIconLink|Iron plate}} and {{NavboxIconLink|Concrete}} may be obtained from {{NavboxIconLink|Molten iron}}
* {{NavboxIconLink|Copper ore}} is not available, but {{NavboxIconLink|Copper plate}} may be obtained from {{NavboxIconLink|Molten copper}}
* {{NavboxIconLink|Coal}} can be mined from patches on the surface as normal
* {{NavboxIconLink|Crude oil}} is not available, but {{NavboxIconLink|Heavy oil}} can be obtained via {{NavboxIconLink|Simple coal liquefaction}}

== See also ==
* {{NavboxIconLink|Aquilo}} {{SA}}
* {{NavboxIconLink|Fulgora}}{{SA}}
* {{NavboxIconLink|Gleba}} {{SA}}

== Gallery==
<gallery widths="300px" heights="200px">
vulcanis_landscape.png|Example of Vulcanus' landscape.
</gallery>

== Trivia ==
* In mythology, Vulcanus (also spelt Vulcan), is the Roman god of fire, metalworking, and the forge

== History ==
{{history|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

{{C|Planets}}
{{SpaceNav}}

Console

2023-09-09T04:28:44Z

Oconnor664: increase running speed

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

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

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

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

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

== Normal commands ==

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

== Multiplayer commands ==

{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| <message>
| Hello team!
| Console input that does not start with {{keybinding|/}} is shown as a chat message to your team.
| No
|-
| /admin
| /admin
| Opens the player management GUI.
| Yes
|-
| /admins
| /admins
| Prints a list of game admins.
| No
|-
| /ban <player> <reason>
| /ban xTROLLx Throwing grenades in base
| Bans the specified player.
| Yes
|-
| /bans
| /bans
| Prints a list of banned players.
| No
|-
| /banlist <add/remove/get/clear> <player>
| /banlist get
| Adds or removes a player from the banlist. Same as /ban or /unban.
| No
|-
| /config <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 achievements will be permanently disabled for the save as soon as you use a script command.

== Basic example scripts ==

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

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

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

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

=== Run faster ===
<syntaxhighlight lang="lua">
/c game.player.character_running_speed_modifier=3
</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
game.player.force.set_saved_technology_progress(tech, 0)
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 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, 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>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== 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 Resource Spawner Overhaul:
<syntaxhighlight lang="lua">
/c __rso-mod__ 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>

== See also ==

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

Console

2021-12-26T20:38:22Z

Oconnor664: list more god-mode items

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

The in-game console can be used for:

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

There are three types of commands:

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

__TOC__

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

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

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

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

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

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

== Normal commands ==

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

== Multiplayer commands ==

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

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

== Basic example scripts ==

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

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

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

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

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

Undo this with the command in the next section.

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

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

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

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

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

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

== Inventory manipulation scripts ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Enemy/evolution scripts ==

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

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

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

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

=== Kill all enemies ===
This will kill all biters, bases and worms. Anything that is an enemy will be completely destroyed. This only affects enemies in the 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 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