Official Factorio Wiki - User contributions [en]

Console

2017-01-20T12:22:54Z

Zx64: Update command line options to 0.14.21

{{Languages}}

== Overview ==
The in-game console is used for:

* chatting with other players
* running commands / scripts / cheats
* occasional status updates

There are three types of command:

* '''Multiplayer''' - message filtering, banning users, etc.
* '''Information''' - display various information about the game
* '''Scripting/Cheating''' - run small Lua scripts (but they <span style="color:#FF0000">disable achievements for the save game</span>)

=== Using the console ===
The console display can be toggled with the '''/''' (slash) or '''~''' (tilde) keys.

You can customise the keys via '''Options Menu -> Keyboard -> Toggle Lua console'''.

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

When console is closed, only the most recent messages/commands will be displayed, but they will gradually fade away (opening the console will immediately redisplay all recent messages).

You can set the fade out time via '''Options Menu -> Other Settings -> Message Delay'''.

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

In [https://forums.factorio.com/viewtopic.php?f=3&t=32389 Factorio 0.14.5 and later], you can clear the console with the '''/clear''' command.

=== Console history ===

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

Use the '''up arrow''' and '''down arrow''' keys to scroll through the console history.

Use the '''left arrow''' and '''right arrow''' keys to cursor through the currently displayed message or command, which you can edit (delete, insert, etc.) and resend (by pressing '''Return''').

In [https://forums.factorio.com/viewtopic.php?f=3&t=32389 Factorio 0.14.5 and later], the '''Tab''' key will autocomplete commands and player ids.

== Multiplayer Chat ==

Send private message to specific player with '''/whisper''' (or '''/w'''):

/whisper <playerId> <message>

Reply to the most recently received private message with '''/reply''' (or '''/r'''):

/reply <message>

In [https://forums.factorio.com/viewtopic.php?f=3&t=32248 Factorio 0.14.4 and later], group chat works like this:

hello my team!

/s hello all players!
/shout same as /s

In Factorio 0.14.3 and earlier, group chat worked like this:

hello all players!

/team hello my team!

These are just the main chat features - there are also options for banning, ignoring and muting players; see the console '''/help''' for a full list.

== Commands ==
To see a list of all available commands, enter '''/help''' (or '''/h''') in to the console. The available commands will depend on Factorio version and game setup.

/help

In [https://forums.factorio.com/viewtopic.php?f=3&t=32248 Factorio 0.14.4 and later], the '''/help''' command will just display a list of commands - to get full details for a command add the command name (without slash) after '''/help''' (or '''/h'''), for example if you want help on the '''/evolution''' command, you'd type:

/h evolution

=== Scripting and cheat commands ===
You can run Lua script commands via the console. It works similarly to any command line interface or the JavaScript console for your browser.

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

To run a script, prefix it with '''/command''' (or '''/c'''), for example:

/c game.player.print 'hello me!'

If you're in a multiplayer game, the command will be echoed to all other players (so they can see if you're cheating).

In [https://forums.factorio.com/viewtopic.php?p=203991#p203991 Factorio 0.14.5 and later], multiplayer server admins can use '''/silent-command''' (only via RCON/server console) instead of '''/c''' to avoid the command being echoed to all players.

/silent-command game.player.print 'only admins can use (and see) silent commands'

Mod developers can also take advantage of the special '''/measured-command''' which is like '''/c''' but will time how long the command takes to run. This is very useful for performance tuning your scripts.

/measured-command game.player.print 'how much time does this take to run?'

The game ignores newlines when pasting "scriptlets" in the console. This means they can be written in a human readable form in an editor and copy/pasted into the console, making understanding and editing a bit easier.

You can essentially fire any Lua command here, just as you would from a Lua program - Factorio [[Mods]] are merely Lua commands. Therefore you don't necessarily need "cheats" active per-se, as the console allows you full access to the game's internals. You only need a familiarity with the commands and types, as shown in the below examples and the [[Modding]] section.

==Basic Command Examples==

=== Large Screenshots ===

This is how you would take a large HD screenshot. As usual, replace the X and Y with the values you wish.

The file is put into a folder called "script-output", which is located in the same location as the mods folder. These pictures can be quite large.

/c game.take_screenshot{resolution = {x = XPOS, y = YPOS}}

or (showing guis like open chests)

/c game.take_screenshot{showgui = true, resolution = {x = XPOS, y = YPOS}}

or (Show alt info)

/c game.take_screenshot{show_entity_info = true, resolution = {x = XPOS, y = YPOS}}

=== Use it as calculator ===

/c game.player.print(1234 * 5678)

=== Mine faster ===

/c game.player.force.manual_mining_speed_modifier=1000

=== Craft faster ===

/c game.player.force.manual_crafting_speed_modifier=1000

=== Unlock and Research all Technology ===

/c game.player.force.research_all_technologies()

Undo this with:

for _, tech in pairs(game.player.force.technologies) do tech.researched=false end

=== Reset any modifiers to default ===
This includes Tech and speed alterations.

/c game.player.force.reset()

=== Zoom beyond normal bounds ===
Note that zooming too far out can cause performance hits. Be careful.

/c game.player.zoom = 0.1

== Inventory Manipulation ==

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

=== Add items to the player's inventory ===
Replace iron-plate with the internal name of the item desired.

/c game.player.insert{name="iron-plate", count=100}

=== Cheat mode ===
Allows for infinite free crafting. Disable by replacing true with false.

/c game.player.cheat_mode=true

== World Manipulation ==

=== Turn off night ===
Enables eternal day.
/c game.surfaces[1].always_day=true

=== Change Game Speed ===
0.5 is half speed, 1 is default, 2 is double speed, etc. 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.

/c game.speed = X

=== Freeze Time Passage ===
Stops the advancement of the time if true is passed, or unfreezes it if false is passed.

/c game.player.surface.freeze_daytime(BOOL)

=== Add new resource patch ===
This creates a new 5x5 patch of resources, centered on the player character. For resources other than stone, just change "stone" to "iron-ore", "copper-ore", or "coal"

/c local surface = game.player.surface;
for y=-2,2 do
for x=-2,2 do
surface.create_entity({name="stone", amount=5000, position={game.player.position.x+x, game.player.position.y+y}})
end
end

=== Add new oil patch ===
This creates 16 crude oil patches in a 4x4 square that is easy to blueprint.

/c for y=0,3 do
for x=0,3 do
game.player.surface.create_entity({name="crude-oil", amount=50000, position={game.player.position.x+x*5, game.player.position.y+y*5}})
end
end

=== Count Entities ===
Counts all entities whose name includes the string in local entity.

/c
local entity = "belt"

local surface = game.player.surface
local count = 0
for c in surface.get_chunks() do
for key, ent in pairs(surface.find_entities_filtered({area={{c.x * 32, c.y * 32}, {c.x * 32 + 32, c.y * 32 + 32}}, force= game.player.force})) do
if string.find(ent.name,entity) then
count = count + 1
end
end
end
game.player.print(count)

== Enemy/Evolution ==
=== Check how far the biters have evolved ===
Note that commands that do not start with "/c" do not disable achievements.
/evolution

=== Set evolution factor ===
Ranges from 0 (new game) to 1.

/c game.evolution_factor=X

=== Disable time-based evolution & increases pollution-based evolution ===
/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

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 and worms, spawners will not be killed.
/c game.forces["enemy"].kill_all_units()

=== Kill all enemies ===
This will kill all biters, bases and worms. Anything that is an enemy will be completely destroyed. This only affects enemies in the explored world, so any unexplored parts of the map which still need to be generated will still have enemies.

/c local surface = game.player.surface
for c in surface.get_chunks() do
for key, entity in pairs(surface.find_entities_filtered({area={{c.x * 32, c.y * 32}, {c.x * 32 + 32, c.y * 32 + 32}}, force= "enemy"})) do
entity.destroy()
end
end

=== Enable peaceful mode ===
Peaceful mode prevents biter attacks until provoked. Substitute false for true to disable.
/c game.player.surface.peaceful_mode = true

=== Disable biter expansion ===
This prevents biters from creating new spawners.
/c game.map_settings.enemy_expansion.enabled = false

== Player Character ==
Commands concerning the player directly.
=== Get Player Position ===
Prints coordinates of your current position.

/c game.player.print({"", "(", game.player.position.x, ", ", game.player.position.y, ")"})

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

/c game.player.teleport({X, Y})

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

=== Spawn a player character ===
This is useful for escaping god mode. (see [[Console#Enable_god_mode]].) This will spawn a new player at the spawn point of the world, and connect your controls to it.

/c game.player.character = game.player.surface.create_entity{name="player", position = {0,0}, force = game.forces.player}

=== Change Player color ===
Note that commands that do not start with "/c" do not disable achievements. Replace COLOR with the name of a color.
/color COLOR

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

/c game.player.character = nil

Then, hover the mouse over the useless player and destroy it by typing:

/c game.player.selected.destroy()

To undo

/c game.player.create_character()

== Research ==
=== Enable faster research ===
/c game.player.force.laboratory_speed_modifier = 1
1 is normal speed, 2 is double speed 3 is triple etc. I think it goes up to 100.

=== Enabling specific technologies ===
[http://www.factorioforums.com/forum/viewtopic.php?f=18&t=6633 Enabling technologies] (forums)
/c game.player.force.technologies['electric-energy-distribution-1'].researched=true
/c game.player.force.technologies['steel-processing'].researched=true

=== Enabling specific recipes ===
/c game.player.force.recipes["electric-energy-interface"].enabled = true
/c game.player.force.recipes["rocket-silo"].enabled = true

=== Finish research immediately ===
/c for name,technology in pairs(game.player.force.technologies) do technology.researched=technology.enabled end

== Command Line Parameters ==
'''As of Game Version 0.14.21'''

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

General options:
-h [ --help ] display help
--version show version information
-v [ --verbose ] enable verbose logging
-c [ --config ] PATH config file to use
--no-log-rotation don't rotate log file
--mod-directory PATH Mod directory to use

Running options:
-s [ --map2scenario ] arg map to scenario conversion
-m [ --scenario2map ] arg scenario to map conversion
--apply-update arg immediately apply update package
--create FILE create a new map
--map-gen-settings FILE Map generation settings for use with
--create. See data/map-gen-settings.exampl
e.json
--start-server FILE start a multiplayer server
--start-server-load-scenario FILE start a multiplayer server and load the
specified scenario
--start-server-load-latest start a multiplayer server and load the
latest available save
--until-tick TICK run a save until given map tick
--mp-connect ADDRESS start factorio and connect to address
--load-game FILE start Factorio and load a game in
singleplayer
--benchmark FILE load save and run benchmark
--benchmark-ticks N (=1,000) number of ticks for benchmarking. Default
is 1000
--force-opengl use OpenGL for rendering
--force-d3d use Direct3D for rendering

Server options:
--port N network port to use
--bind ADDRESS[:PORT] IP address (and optionally port) to bind
to
--rcon-port N Port to use for RCON
--rcon-password PASSWORD Password for RCON
--server-settings FILE Path to file with server settings. See
data/server-settings.example.json

=== Multiplayer ===

--start-server SAVE

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

--mp-load-game SAVE

SAVE is the filename of the save file. For instance, for saves/MySave.zip: ./factorio --mp-load-game MySave.zip

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

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

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

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

== See also ==

* http://lua-api.factorio.com/latest/ - Factorio API reference for latest version
* http://lua-api.factorio.com/ - links to specific versions of API reference
[[Category:Console]]

Talk:Map generator

2017-01-20T12:12:47Z

Zx64: Created page with "I think all references to terrain segmentation should be removed - it was just water frequency with a different name in older builds according to https://forums.factorio.com/v..."

I think all references to terrain segmentation should be removed - it was just water frequency with a different name in older builds according to https://forums.factorio.com/viewtopic.php?p=235907#p235907
[[User:Zx64|Zx64]] ([[User talk:Zx64|talk]]) 12:12, 20 January 2017 (UTC)

Map generator

2017-01-20T12:03:19Z

Zx64: Update screenshot of map generator settings to version 0.14.21

{{Languages}}
World generation is, in short, a number of settings which define what the world will look like once generated. This can dramatically alter gameplay- a new player is advised to start with the default settings before deciding to change their world.

==How it works==
: [[File:MapGeneratorOverview01421.png]]
A more technical explanation of world generation mechanics is that the map generator generates most parts of the world with an algorithm named "Perlin Noise". In short, it works a bit like the waves in the sea.

[[File:Water-ocean-waves-sea-high-resolution-pictures.jpg|thumb|left|300px]]

{{Clear}}

Everything above a defined level defines the existing (or non-existing) features of some type of terrain. The player should also know that the map is not generated at game start. Only the parts they see are generated, everything else is not. The map will be generated gradually as the player explores more terrain. See below for more technical details.

{{Clear}}

The following image shows an example how the world generator might create a new map.

[[File:Default_123456789.png|thumb|left| World generation on default settings with map seed 123456789]]

<div style="clear: both"></div>

===Settings on the top row===
====Frequency====
This is '''not''', how frequent ore, coal, oil etc. is, instead determining the number of individual deposits the player will encounter.

This defines the wavelength of the wave-generators used by the Perlin Noise algorithm above, but not the total size of all the waves.

What this means is that frequency doesn't modify the amount of resources on a tile, instead modifying the area of each deposit. If the player decreases frequency then each of the deposits has less resources in total (because it covers less area), but per tile of a deposit there will be the same number of resources. Additionally, changing frequency doesn't affect the average amount of resources in a limited map, only their distribution.

''High frequency'':

* For terrain segmentation: Many different types of terrain, forest, desert and swamp could be within 10 tiles or less. Recommended for players interested in the different biomes of the world.
* For resources: Patches of resources are very common but frequently small and wear out quickly. Recommended for players who are willing to constantly reset equipment in exchange for a constant supply of resources.

''Low frequency'':

* For terrain segmentation: Big landscapes, vast areas typically only with forests. Recommended for players who want to consistently experience what they have near their spawn point.
* For resources: Resource patches are fairly rare but almost always very large and rich in resources. Recommended for players who don't want to move equipment often or who prefer to explore the world. Also promotes train use.

In short: Low terrain segmentation means large areas with same terrain. High terrain segmentation is the opposite, the terrain changing nature often. Typically huge forests vs. lots of small woods.

This also causes enemy bases to appear more often using the same distribution rules as ores and biomes- however, this can lead to rapid [[Enemies|enemy]] expansion due to the much higher number of nest clusters.

====Size====

This defines the size of generated ore patches and water through defining "levels." It increases the average diameter of ore patches and lakes, allowing one to adjust the size of both of these.

It's as simple as it seems- Small size would mean small ore patches and water masses, large means large ore patches and water masses. Note that this is effected by frequency, though it is presumably able to increase the total ore and water of the world where frequency simply re-balances it.

Finally, this causes [[Enemies|enemy bases]] to spawn larger, though bases created through the "natural process" of expansion are going to adhere to different rules.

The following table shows how the frequency and size settings affects the generation of ore patches. For more detail, open the images in a new tab.

{| class="wikitable"
|+Generation of iron patches on different frequency and size settings
!Frequency \ Size
!Very small
!Small
!Medium
!Big
!Very big

|-
!Very low
|[[File:Iron_freq_very_low_size_very_small.png|frameless|150x150px]]
|[[File:Iron_freq_very_low_size_small.png|frameless|150x150px]]
|[[File:Iron_freq_very_low_size_medium.png|frameless|150x150px]]
|[[File:Iron_freq_very_low_size_big.png|frameless|150x150px]]
|[[File:Iron_freq_very_low_size_very_big.png|frameless|150x150px]]

|-
!Low
|[[File:Iron_freq_low_size_very_small.png|frameless|150x150px]]
|[[File:Iron_freq_low_size_small.png|frameless|150x150px]]
|[[File:Iron_freq_low_size_medium.png|frameless|150x150px]]
|[[File:Iron_freq_low_size_big.png|frameless|150x150px]]
|[[File:Iron_freq_low_size_very_big.png|frameless|150x150px]]

|-
!Normal
|[[File:Iron_freq_normal_size_very_small.png|frameless|150x150px]]
|[[File:Iron_freq_normal_size_small.png|frameless|150x150px]]
|[[File:Iron_freq_normal_size_medium.png|frameless|150x150px]]
|[[File:Iron_freq_normal_size_big.png|frameless|150x150px]]
|[[File:Iron_freq_normal_size_very_big.png|frameless|150x150px]]

|-
!High
|[[File:Iron_freq_high_size_very_small.png|frameless|150x150px]]
|[[File:Iron_freq_high_size_small.png|frameless|150x150px]]
|[[File:Iron_freq_high_size_medium.png|frameless|150x150px]]
|[[File:Iron_freq_high_size_big.png|frameless|150x150px]]
|[[File:Iron_freq_high_size_very_big.png|frameless|150x150px]]

|-
!Very high
|[[File:Iron_freq_very_high_size_very_small.png|frameless|150x150px]]
|[[File:Iron_freq_very_high_size_small.png|frameless|150x150px]]
|[[File:Iron_freq_very_high_size_medium.png|frameless|150x150px]]
|[[File:Iron_freq_very_high_size_big.png|frameless|150x150px]]
|[[File:Iron_freq_very_high_size_very_big.png|frameless|150x150px]]

|}

====Richness====

This defines the actual content of each generated ore patch, oil field, and [[Enemies]]' base drops, through changing the "height" of the wave. Note that with bases this does not make them more difficult, but rather increases the [[Alien artifact]] yield.

{| class="wikitable"
|+Resources in ore patches on different richness settings
!Very poor
!Poor
!Regular
!Rich
!Very rich

|-
|[[File:Iron_richness_very_poor.jpg|150x150px|thumb|Resources to mine: 22k]]
|[[File:Iron_richness_poor.jpg|150x150px|thumb|Resources to mine: 32k]]
|[[File:Iron_richness_regular.jpg|150x150px|thumb|Resources to mine: 45k]]
|[[File:Iron_richness_good.jpg|150x150px|thumb|Resources to mine: 64k]]
|[[File:Iron_richness_very_good.jpg|150x150px|thumb|Resources to mine: 90k]]

|}

===The left column===

* Terrain segmentation: How often the terrain changes between biomes. This can include water, so beware of lower settings as they can limit world size artificially.
* Water: How [[water]] is generated on each map. Be warned: since water is currently impassible except over lighter regions of water, this can potentially create very small or hard to navigate maps.
* Copper, Stone, Coal, Crude oil: Resources required to progress in the game. See above for more detailed explanations about each of these changes.
* Enemy bases: How many and how large starting bases are. Note that new bases are created over time, making low enemy base counts somewhat less significant.

===Starting area===

This is a value defining a special area around the central coordinates of the map which will have different ore frequency, etc, from the rest of the map. Generally, this results in at least one confirmed ore source, always results in a water source, and always removes biter nests from spawning for an area around spawn. The settings of this area usually guarantee better starting conditions, although conditions may vary- the player may spawn completely isolated from the rest of the world!

The player may choose to make this area small or remove it entirely, however, this is not recommended as this opens the possibility of spawning in an impossible situation, or even in a biter nest. Many members of the community do this to increase challenge of the game.

It is generally a good idea for the player to explore a bit outside this area before they begin to build. While this area will almost always appear very fertile, it's possible that map generation will have made a situation where it is impossible to beat the game, such as missing [[oil]], too many biters to defend, etc.

{| class="wikitable"
|+World generations on different starting area settings
!Very small
!Small
!Medium
!Big
!Very big

|-
|[[File:Starting_area_very_small.png|frameless|150x150px]]
|[[File:Starting_area_small.png|frameless|150x150px]]
|[[File:Starting_area_medium.png|frameless|150x150px]]
|[[File:Starting_area_big.png|frameless|150x150px]]
|[[File:Starting_area_very_big.png|frameless|150x150px]]
|}

===Peaceful mode===
The [[Enemies]] don't begin fights, only responding if the player hits them. This can be also switched on during the game- look into [[Console|Console commands]].

===Map-width and -height===
If the player limits the width and/or height they may generate maps with finite resources and area. This is recommended for multiplayer servers running on weaker machines or players seeking extra challenge. Another option is to make the world infinite in only one axis, this is commonly referred to as a ''ribbon world''.

===Map seed / Map Exchange String===

Definitions and terminology:

; Map Seed:
: Random number generator seed
; Map Exchange String
: All settings for the map creation (Map Seed, settings for resources, settings for size, etc.)

====Map Seed====
This is the starting value for the random number generator that Factorio uses for generating the world. Know that 'random number' is really a misnomer in Factorio and on computers in general, as they aren't really random, instead being calculated with complicated algorithms that require a seed as startng value (For more detail, see http://en.wikipedia.org/wiki/Random_seed).

So even with the same map-exchange string but a different seed maps can change dramatically, or appear very similar. It's up to chance. In order to get a true copy of a world, giving the map-exchange string and allowing the string to fill out the seed is important.

====Map Exchange String====
A string generally looks like so:

>>>AAALABAABgADAwYAAAAEAAAAY29hbAMDAgoAAABjb3BwZXItb3Jl
AwMCCQAAAGNydWRlLW9pbAMDAgoAAABlbmVteS1iYXNlAwMCCAAAAGl
yb24tb3JlAwMCBQAAAHN0b25lAwMCORcrDUQ7AACMCwAAAAAAAAAAAA
ADAFR8w0Q=<<<

It is a string of good length that begins with >>> and ends with <<<. Many facilities exist within the community for sharing exchange strings. The map exchange string can be used in the map-generator: there is an extra field where the player can paste this string into. On windows computers, this may be done by selecting a string, right-clicking or pressing Control + C, then put it into the string field for the world generator with Control + V.

If you wish to retrieve the map-exchange string from your world:

In the Load Game dialog select the game whose string you want, then click the Map Exchange String button in the lower left corner. When the string pops up, highlight it with your mouse and press Control-C to copy it. (Command-C on Mac.) You can now paste it in the map generator to create a copy of that world, or send it to a friend.

For a technical description of the map exchange string, see [[Map Exchange String Format]].

==Generation==

The map generator (world generator) is based on a modified [http://en.wikipedia.org/wiki/Perlin_noise Perlin noise algorithm].
A [[Types/AutoplaceSpecification#Noise|more detailed description]] is in the API documentation.

From the [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=8016&p=63691#p63561 article which describes the generation]:
: [[File:Factorio-Perlin-Noise.png]]
Top: Normal settings, Middle: The same, but with higher '''frequency''' (note the same curve, but more condensed shape), Down: Same as top, but higher level = increased '''size'''.

The blue wavy line is an internal noise function, black line is a "level" that is used to determine resource placement, red lines are actual placed resources. The high frequency refers mainly to the noise function. Increasing the frequency increases count of resource fields and decreases their size and distance between them. This mechanism is used all through the map generation in factorio, with some adjustments. The map generator works tile by tile, so the resources are placed on a tile x if f(x) > 0. The amount of resources on the tile is given by f(x) * richness.

==Generating new Chunks==

A map is endless by default, though its size can be limited by height and width - see above. Because it is technically endless, the whole map isn't generated from the start. A new [[Chunk]] of map is generated only when needed, similar to other procedurally generated world games.

===Generating Invisible Chunks (Fog of War)===

Outside of the visible chunk area, an invisible area of about 3 chunks wide is generated, as a preloading mechanism, and for biters to be able to see the player. Invisible chunks are also generated if pollution is generated heavily; the game generates (invisible) chunks as it needs to spread the pollution into the area.

===Charting (Make Invisible Chunks Visible on Map)===

As long as a chunk is invisible, the part of the players map stays black. This changes when a chunk is '''[[Radar#Charting|charted]]''', which means when it is "touched" by radar. Either the players internal radar, which is always available and continaully charts chunks around the player, or the '''[[Radar]]''' entity. When a visible chunk is generated there might be other chunks also invisibly generated.

An invisible chunk is eventually not made visible, even if you are so close, that you are able to see it in the character view (a black fog of war). This is, because of the above rule: a chunk is made visible, if it is touched by radar. Not character visibility. The players radar (or any radar) needs to be in range of that chunk to make it visible.

=== Exploring ===

If the player arrives at the current visible borders the needed chunks are generated. As the [[player]] explores, a radius of about 3 chunks are continually loaded around them. As this can take a while on lower end machines, it is possible to outrun the world generator and end up in 'limbo' with no entities around the player. Staying still for a while will allow the generator to catch up.

=== Maximum Map Size and used Memory===

The map size is limited to 2000 x 2000 kilometers (a quadrat with 2,000,000 tiles side-length, an area of 4,000,000,000,000 quadrat-tiles). This is between the size of India and Australia. It would take around 240 [[game-second|game-minutes]] (=4 hours) by train to reach that border from the center. This means that the world is essentially endless.

Because only chunks are generated around the area that is revealed by radar, it is with current computers possible to reach that border. This is, because the needed memory size of the map is limited only by the generated number of chunks in the game. Which is not so much if you allocate just a small stripe of land.

The generated chunks are mapped and stored in the player's RAM, which is the limiting factor.

==See also==
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=7331 The Map Generator hates your guts, or dude where is my coal?]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=7924&p=63517#p63517 Some technical info]
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=8624&p=69156#p69156 Temperature based biome-model] (how trees are placed)
* [http://www.factorioforums.com/forum/viewtopic.php?f=6&t=1593 Thread about definition of map map exchange string/seed]
* [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=6447&p=50336#p50318 Definition of string and seed]

Game modes and options

2017-01-20T11:59:08Z

Zx64: Add list of included scenarios and campaigns as of 0.14.21

{{Languages}}

This page is a list of all current game-modes in Factorio.

* Singleplayer
: The base game. Play alone, building your base and defending it from the enemy native life!
* [[Multiplayer]]
: Play Factorio with friends and build your factory together.
* Scenario mode
: Play pre-built scenarios made by users or the developers. Included with the base game:
:: Freeplay - Normal single player - launch a satellite to win.
:: Sandbox - Free-form play, various cheats available to skip to the stage you want to build.
:: Supply Challenge - Timed challenge to produce and deliver specified items for each level.
:: Team Production - Multiplayer challenge scenario where teams compete on randomised tasks including item production or research.
* Campaign
: Play the set of scenarios that come with the game by default. The closest thing to a story Factorio has.
:: First steps - Tutorial on various entry level mechanics like crafting and mining.
:: New hope - Carrying on from where First Steps ends, you search for the crashed ship's computer.
:: Transport belt madness - Test your belt layout skills by connecting chests on a small island
:: Tight spot - Buy land and machines, sell your final product.

Factorio:Wiki rules

2017-01-20T11:38:39Z

Zx64: One more "screenshoot" fix

{{Languages}}
This page is used for contributors on this wiki. This page also contains some guidance for potential contributors.

== Get an account ==

Just follow the instructions for registering. It takes normally one or two days to be added, because every user is added by hand to avoid spam. If after a week your account is not accepted, please email Wube's support.

If you need more rights to the wiki (deletion, moving...) you need to ask the developers directly, or ask in the forum board. Additionally, you may also ask an admin, if one is active at the time. Note that higher permissions are very rarely given out.

== Understanding the wiki ==

This Wiki is hosted by Wube, a development company that develops Factorio. This Wiki is run by the community, with small influence from the developers.

== Official rules ==

Below are the community guidelines for the Official Factorio Wiki. Infringing upon any of these rules will result in either a warning or a temporary/permanent ban, depending on the circumstances. These rules are not final, and are subject to change.

* Language
** The default language is American English. All pages must have an English version, and should be translated English -> Other. Use of country-specific slang must be avoided, except for localization reasons.
** Any other language has no right to obtain a page name which collides with English.
** No other language has the right to use a page name which means the same or something different in another language.
** Language pages when translated should use the English name with the language code appended to the end of the name. For example, "Transport belt" when translated to German should be named "Transport belt/de".

* Typo control
** Please use the "Show preview" button to view your changes before saving them, to allow yourself to catch incorrect links and typos, and improper formatting.
** Please correct all typos found, even if changing the sentence layout is necessary. Comprehension is important.
** Run a spell check of the article to catch spelling errors.

* Conduct
** Be respectful to all editors, and readers. '''All forms of hate are not tolerated''', and will result in a warning and ban.
** '''All forms of vandalism and spam are not tolerated''', and violators will be banned without question.
** Do not edit-war. If a user overwrites your change and you disagree, do not edit the page back and forth, discuss it on the talk page of the page in question.
** This ties into the above rule, but assume good faith. If a wiki editor makes a mistake due to human error, the fact that they are new to the community, or any other honest reason, fellow wiki community members must assume good faith. Rather than insulting, berating, or lashing out at the editor, community members should approach situations like these with a helpful and understanding attitude.
** Wiki talk pages are for discussion of their respective page '''only'''. Please keep all discussion of in-game mechanics to the forums or subreddit, the links to which are in the sidebar. An article's talk page is intended for discussion or questions regarding the article's content. It is not a forum for casual discussion. Game suggestions, personal stories, shout-outs, etc. will be removed.
** When making comments or asking questions on a talk page, be sure to sign the end with four tildes (<nowiki>~~~~</nowiki>)
** Always remain civil during discussions.
** While the Wiki can be easily reverted in the event of a mistake, please try to avoid creating work for others.
** Registered users are expected to use a single account for all editing under most circumstances. The use of more than one account by a single individual is known as "sockpuppeting", and is a very high offense. A second account can be used in certain rare circumstances by longtime established, trusted users. Some valid reasons to use a second account may include those below. In those cases, it must be made absolutely clear that the accounts are operated by the same individual.
*** Technical testing
*** Bot (automated) accounts
*** Administrators who want to use non-admin accounts in less secure editing situations.
** Refrain from using profanity unless it is used within a direct quotation.

* Page layout guidelines
** Typically, a page will start with a short intro, then the content of the page, a history section, and a "see also" section. Please follow this when creating content pages. Categories should be used sparingly.
** Please use sane formatting, and do not Capitalize Words Like This.
** Do not overuse '''bold''', ''italics'', or <span style="color:#00FF00">colorful text.</span>
** If possible, clean white-space from the ends of lines. Many editors can do this for you. Emacs, Notepad++, Sublime Text, and Vim are recommended.
** Avoid creating unnecessary pages. If the info you are trying to add is related to an entity in-game, please place the info on that entity's page, and so on and so forth.
** The Wiki follows the ''stable branch of the game''. Changes concerning the experimental branch should only be put into place late in the development cycle of the branch, right before it is pushed to stable.
** [[Upcoming features]] should be referenced with a link to a comment or image posted by a member of Factorio's development staff.
** Edit in an “encyclopedia” style, avoiding use of the first person or any personal bias.
** Do not create circular links, I.e. do not link a page to itself.
** If making a comment to other editors is necessary, place the comment in comment delimiters, <pre></pre> so it cannot be seen by users.

* The History section
** Bugs must not be placed in the update history section of a page, except for very significant instances. Instead, please document bugs in the bug sections of the official forums.
** While a history section is not required for information pages such as [[Railway]], all content pages concerning entities or mechanics of the game should have a history, taken from the changelog file provided with a standard Factorio install.
** Trivia is allowed, as long as it does not contain personal opinion and is not conjecture.

== Contributing to the wiki ==

This wiki is the work of a team. The goal is for people to add information or bring it into better context, do videos, or design the layout of the pages, with the end goal to provide an easy place for beginners to Factorio to gain information.

The team communicates through the talk-pages ("Discussion" tab at the top) or through the forum. It's very important to check recent changes ("View History" tab at the top of the page). History will show you all the changes people have made to the page. Additionally, checking "Recent Changes" on the sidebar is also recommended.

(BTW: You can change the shown results in preferences!)

There are different jobs you can do. This list goes from simple to complex.

=== Corrector ===

Read through the pages (of your language) and correct mistakes or bad language usage. If it sounds ugly then change it. If you're new to wikis it might be difficult at first, but keep at it and you'll learn to do more. :)

=== Translator ===

Take an English page, copy the content into a sub-page (see below for an explanation) and translate it to your language. Please only translate if you speak the language very fluently or natively.

=== News-maker ===

There is also the [[News]]-page. Just add new links as new interesting information comes out. The rest is explained in the page as comments. Don't add stuff that isn't news. Before you add any, ask yourself: If I was looking at this from the future, would it still be relevant? Most of the time, blog posts from the Factorio team are denoted on the news page.

=== Designer ===

This is about the look and feel of this wiki.

Deep knowledge of Mediawiki's template system is not really needed, but will help. For the beginning just try to understand how the current templates work. Make your own test-page in your user-space and try to program around. It can be really fun because this task is more or less like programming. If you need assistance, be sure to check the "help" link on the sidebar of the Wiki, as it can give lots of information about the markup of the Mediawiki language.

Look here for some help: http://www.mediawiki.org/wiki/Help:Contents

=== Architect ===

The wiki is created in an agile process: writing, reading, testing. :) If you find out that this process is somehow inefficient, for example the changes are in the wrong place, then you need to change the wiki in general.

So, the job of an architect is to bring the existing pages into the right context by adding some new pages and/or renaming existing pages, and then changing the links to the pages. And sometimes old stuff must be deleted. '''Please do not make large changes without consulting an admin'''.

=== Other ===

So, if you have an idea:
* '''Don't be afraid: There is nothing which you can really break, the wiki has a version history.
* If you are still afraid: You can use the a test page in your home-space. That's the page beginning with "User:<your user name>". You can add a sub-page like "User:<your user name>/MyTests". Ask others what they think about it. Communicate!
* Begin with slight changes. The others will watch (the "Recent changes") and help you out. If after a week or two is no response/follow up change, your change was good. Keep going, make bigger changes.

== Basic ==

* Read the wiki pages. It is important to learn by example.
** If you don't like something, change it.
** If you find typos, change it.
** If you find something is described wrong, change it.
** If someone disagrees about it, try to work it out on the talk pages or on the forums.

== Advanced ==

* Add missing information in the right places.
: In most cases this is easy, but sometimes can be really difficult. Ask for help if you're unsure.

* If you find that a topic belongs to two pages, then don't copy the information into the two pages, but create a new page and link them.

* Use the correct choice of words.
: Factorio has a set of words which have a fixed meaning. For example: An entity can be mined, an item can be picked up. Getting entity and item mixed up means something different! Ask the users if you are unsure which is which.

* A picture says more than a thousand words.
: Use pictures if possible. In some cases use GIFs! See below.

* You can also go to the [[Wiki To-do List]] and see if there is a job you like.

=== Existing discussions ===

In descending order of date:

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2047

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3205

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2429

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2255

== Translations ==

For translating the in-game texts, the dev-team uses https://crowdin.com/project/factorio

=== So what do I need to do now? ===

* If you want to translate a page, then don't rename the page, just add a "/" and the [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes standard macro-language-code] to the page name.
: "Inserters" becomes "Inserters/fr" for France, "Inserters/ru" for Russian etc.
* If you are working on a page which has a translated page name then rename (Move) it! Search the original page name, add the language-code (see above), and move it to the new page name. A redirect is automatically left for the old page name!

(More to explain, language macro, see main-page at top right)

== Pictures ==

=== Picture formats ===

For making things simple we should use only formats based on 100. This is to avoid different sized pics which look staggered. This is especially important for the width, for the height it is not that much of a problem. For example: 200x200, 300x100, 400x232. For existing pics (old pics use often a width of 256 px) reduce the text to 200 px (and analogous).

* (100 - 200) x (100-300) px
: For flowing with the text, pictures which explain the text, the browser can embed this into it's own rendering. You can put them left or right, the text should flow around.
* (400 - 600) x (100 - 600) px
: Something like a banner. A big picture which stays alone in its line. You may put simply a ":" in front of it to indent the picture and keep it away from flowing text.
* 300 x 300 px
: This is especially good for gif animations. Gif animations cannot be reduced in size, because Mediawiki re-renders the picture and the result is the first frame of the gif! See for example these pics: http://www.factorioforums.com/wiki/index.php?limit=200&ilsearch=Mpstark&user=&title=Special%3AListFiles
* The biggest format for flowing text should be: 600x600px

=== Making pictures out of the game ===

Do's:

* Take pictures at day! [[Lua/Game#alwaysday|Turn on daylight]]! Use night or dawn only if you need to explain something that only works at night (for example, the lights).
* Turn off clouds! The shadows in GIF-animations are not useful.
* Steam/smoke is also not that useful.
* Use god mode! [[Lua/Player#controllertype]]. You can move anywhere on the map and your character won't be in the picture.
* You can [[Lua/Game#speed|slowdown the game]] to find the right moment for the picture. Slowdown is also useful if you use Gifcam, which makes Screenshots in 30 frames/sec only.
* You can also use the [[Lua/Game#peacefulmode]] to be not disturbed by the natives.
* You can stop the game in the right moment using SHIFT-SPACE key. That also blends the grid in.
* Learn how to use the [[Debug mode]] to add relevant information into the picture.
* Go into the highest zoom level you possibly can without missing any vital information.
* A good in-game picture should be rebuilt so that only the relevant entities/items are shown. Anything in the photo other than what you're trying to show/explain is unnecessary.

Dont's:

* Don't take pictures of clutter! The only stuff in the photo should be the stuff you're trying to show. The Exception to Clutter: If you're showing what a fully finished factory or setup might look like.
* Don't just take a screenshot. Try to remove all unneeded information from the picture.
* Try to make a picture without the character, except if to show something; then face the character toward it.

See http://www.factorioforums.com/forum/viewtopic.php?f=6&t=2472 for more.

== Taking Screenshots, animations and videos==

=== Taking Screenshots ===

* It's possible to take [[Lua/Game#takescreenshot|screenshots out of the game]]! The [http://www.youtube.com/watch?v=9yDZM0diiYc second trailer] is made like so. See http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5591
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5591 Calculate screenshot dimensions].

==== Optimizing the picture before upload ====

* Cut as much as possible/nice.
* Resolution should not normally be higher than 600x600 px. Use multiple photos or ask a trusted wiki user if you need a much larger photo.
* ''Do not add text to the photos'' Write any needed text outside the photo on the wiki. You cannot search text that is in a photo and users might not find what they are looking for.
* Sharpen the pictures. For the wiki it looks a lot better to sharpen the pictures once or twice.

Factorio:Wiki rules

2017-01-20T11:38:04Z

Zx64: Fix "screenshoots" typo

{{Languages}}
This page is used for contributors on this wiki. This page also contains some guidance for potential contributors.

== Get an account ==

Just follow the instructions for registering. It takes normally one or two days to be added, because every user is added by hand to avoid spam. If after a week your account is not accepted, please email Wube's support.

If you need more rights to the wiki (deletion, moving...) you need to ask the developers directly, or ask in the forum board. Additionally, you may also ask an admin, if one is active at the time. Note that higher permissions are very rarely given out.

== Understanding the wiki ==

This Wiki is hosted by Wube, a development company that develops Factorio. This Wiki is run by the community, with small influence from the developers.

== Official rules ==

Below are the community guidelines for the Official Factorio Wiki. Infringing upon any of these rules will result in either a warning or a temporary/permanent ban, depending on the circumstances. These rules are not final, and are subject to change.

* Language
** The default language is American English. All pages must have an English version, and should be translated English -> Other. Use of country-specific slang must be avoided, except for localization reasons.
** Any other language has no right to obtain a page name which collides with English.
** No other language has the right to use a page name which means the same or something different in another language.
** Language pages when translated should use the English name with the language code appended to the end of the name. For example, "Transport belt" when translated to German should be named "Transport belt/de".

* Typo control
** Please use the "Show preview" button to view your changes before saving them, to allow yourself to catch incorrect links and typos, and improper formatting.
** Please correct all typos found, even if changing the sentence layout is necessary. Comprehension is important.
** Run a spell check of the article to catch spelling errors.

* Conduct
** Be respectful to all editors, and readers. '''All forms of hate are not tolerated''', and will result in a warning and ban.
** '''All forms of vandalism and spam are not tolerated''', and violators will be banned without question.
** Do not edit-war. If a user overwrites your change and you disagree, do not edit the page back and forth, discuss it on the talk page of the page in question.
** This ties into the above rule, but assume good faith. If a wiki editor makes a mistake due to human error, the fact that they are new to the community, or any other honest reason, fellow wiki community members must assume good faith. Rather than insulting, berating, or lashing out at the editor, community members should approach situations like these with a helpful and understanding attitude.
** Wiki talk pages are for discussion of their respective page '''only'''. Please keep all discussion of in-game mechanics to the forums or subreddit, the links to which are in the sidebar. An article's talk page is intended for discussion or questions regarding the article's content. It is not a forum for casual discussion. Game suggestions, personal stories, shout-outs, etc. will be removed.
** When making comments or asking questions on a talk page, be sure to sign the end with four tildes (<nowiki>~~~~</nowiki>)
** Always remain civil during discussions.
** While the Wiki can be easily reverted in the event of a mistake, please try to avoid creating work for others.
** Registered users are expected to use a single account for all editing under most circumstances. The use of more than one account by a single individual is known as "sockpuppeting", and is a very high offense. A second account can be used in certain rare circumstances by longtime established, trusted users. Some valid reasons to use a second account may include those below. In those cases, it must be made absolutely clear that the accounts are operated by the same individual.
*** Technical testing
*** Bot (automated) accounts
*** Administrators who want to use non-admin accounts in less secure editing situations.
** Refrain from using profanity unless it is used within a direct quotation.

* Page layout guidelines
** Typically, a page will start with a short intro, then the content of the page, a history section, and a "see also" section. Please follow this when creating content pages. Categories should be used sparingly.
** Please use sane formatting, and do not Capitalize Words Like This.
** Do not overuse '''bold''', ''italics'', or <span style="color:#00FF00">colorful text.</span>
** If possible, clean white-space from the ends of lines. Many editors can do this for you. Emacs, Notepad++, Sublime Text, and Vim are recommended.
** Avoid creating unnecessary pages. If the info you are trying to add is related to an entity in-game, please place the info on that entity's page, and so on and so forth.
** The Wiki follows the ''stable branch of the game''. Changes concerning the experimental branch should only be put into place late in the development cycle of the branch, right before it is pushed to stable.
** [[Upcoming features]] should be referenced with a link to a comment or image posted by a member of Factorio's development staff.
** Edit in an “encyclopedia” style, avoiding use of the first person or any personal bias.
** Do not create circular links, I.e. do not link a page to itself.
** If making a comment to other editors is necessary, place the comment in comment delimiters, <pre></pre> so it cannot be seen by users.

* The History section
** Bugs must not be placed in the update history section of a page, except for very significant instances. Instead, please document bugs in the bug sections of the official forums.
** While a history section is not required for information pages such as [[Railway]], all content pages concerning entities or mechanics of the game should have a history, taken from the changelog file provided with a standard Factorio install.
** Trivia is allowed, as long as it does not contain personal opinion and is not conjecture.

== Contributing to the wiki ==

This wiki is the work of a team. The goal is for people to add information or bring it into better context, do videos, or design the layout of the pages, with the end goal to provide an easy place for beginners to Factorio to gain information.

The team communicates through the talk-pages ("Discussion" tab at the top) or through the forum. It's very important to check recent changes ("View History" tab at the top of the page). History will show you all the changes people have made to the page. Additionally, checking "Recent Changes" on the sidebar is also recommended.

(BTW: You can change the shown results in preferences!)

There are different jobs you can do. This list goes from simple to complex.

=== Corrector ===

Read through the pages (of your language) and correct mistakes or bad language usage. If it sounds ugly then change it. If you're new to wikis it might be difficult at first, but keep at it and you'll learn to do more. :)

=== Translator ===

Take an English page, copy the content into a sub-page (see below for an explanation) and translate it to your language. Please only translate if you speak the language very fluently or natively.

=== News-maker ===

There is also the [[News]]-page. Just add new links as new interesting information comes out. The rest is explained in the page as comments. Don't add stuff that isn't news. Before you add any, ask yourself: If I was looking at this from the future, would it still be relevant? Most of the time, blog posts from the Factorio team are denoted on the news page.

=== Designer ===

This is about the look and feel of this wiki.

Deep knowledge of Mediawiki's template system is not really needed, but will help. For the beginning just try to understand how the current templates work. Make your own test-page in your user-space and try to program around. It can be really fun because this task is more or less like programming. If you need assistance, be sure to check the "help" link on the sidebar of the Wiki, as it can give lots of information about the markup of the Mediawiki language.

Look here for some help: http://www.mediawiki.org/wiki/Help:Contents

=== Architect ===

The wiki is created in an agile process: writing, reading, testing. :) If you find out that this process is somehow inefficient, for example the changes are in the wrong place, then you need to change the wiki in general.

So, the job of an architect is to bring the existing pages into the right context by adding some new pages and/or renaming existing pages, and then changing the links to the pages. And sometimes old stuff must be deleted. '''Please do not make large changes without consulting an admin'''.

=== Other ===

So, if you have an idea:
* '''Don't be afraid: There is nothing which you can really break, the wiki has a version history.
* If you are still afraid: You can use the a test page in your home-space. That's the page beginning with "User:<your user name>". You can add a sub-page like "User:<your user name>/MyTests". Ask others what they think about it. Communicate!
* Begin with slight changes. The others will watch (the "Recent changes") and help you out. If after a week or two is no response/follow up change, your change was good. Keep going, make bigger changes.

== Basic ==

* Read the wiki pages. It is important to learn by example.
** If you don't like something, change it.
** If you find typos, change it.
** If you find something is described wrong, change it.
** If someone disagrees about it, try to work it out on the talk pages or on the forums.

== Advanced ==

* Add missing information in the right places.
: In most cases this is easy, but sometimes can be really difficult. Ask for help if you're unsure.

* If you find that a topic belongs to two pages, then don't copy the information into the two pages, but create a new page and link them.

* Use the correct choice of words.
: Factorio has a set of words which have a fixed meaning. For example: An entity can be mined, an item can be picked up. Getting entity and item mixed up means something different! Ask the users if you are unsure which is which.

* A picture says more than a thousand words.
: Use pictures if possible. In some cases use GIFs! See below.

* You can also go to the [[Wiki To-do List]] and see if there is a job you like.

=== Existing discussions ===

In descending order of date:

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2047

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3205

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2429

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2255

== Translations ==

For translating the in-game texts, the dev-team uses https://crowdin.com/project/factorio

=== So what do I need to do now? ===

* If you want to translate a page, then don't rename the page, just add a "/" and the [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes standard macro-language-code] to the page name.
: "Inserters" becomes "Inserters/fr" for France, "Inserters/ru" for Russian etc.
* If you are working on a page which has a translated page name then rename (Move) it! Search the original page name, add the language-code (see above), and move it to the new page name. A redirect is automatically left for the old page name!

(More to explain, language macro, see main-page at top right)

== Pictures ==

=== Picture formats ===

For making things simple we should use only formats based on 100. This is to avoid different sized pics which look staggered. This is especially important for the width, for the height it is not that much of a problem. For example: 200x200, 300x100, 400x232. For existing pics (old pics use often a width of 256 px) reduce the text to 200 px (and analogous).

* (100 - 200) x (100-300) px
: For flowing with the text, pictures which explain the text, the browser can embed this into it's own rendering. You can put them left or right, the text should flow around.
* (400 - 600) x (100 - 600) px
: Something like a banner. A big picture which stays alone in its line. You may put simply a ":" in front of it to indent the picture and keep it away from flowing text.
* 300 x 300 px
: This is especially good for gif animations. Gif animations cannot be reduced in size, because Mediawiki re-renders the picture and the result is the first frame of the gif! See for example these pics: http://www.factorioforums.com/wiki/index.php?limit=200&ilsearch=Mpstark&user=&title=Special%3AListFiles
* The biggest format for flowing text should be: 600x600px

=== Making pictures out of the game ===

Do's:

* Take pictures at day! [[Lua/Game#alwaysday|Turn on daylight]]! Use night or dawn only if you need to explain something that only works at night (for example, the lights).
* Turn off clouds! The shadows in GIF-animations are not useful.
* Steam/smoke is also not that useful.
* Use god mode! [[Lua/Player#controllertype]]. You can move anywhere on the map and your character won't be in the picture.
* You can [[Lua/Game#speed|slowdown the game]] to find the right moment for the picture. Slowdown is also useful if you use Gifcam, which makes Screenshots in 30 frames/sec only.
* You can also use the [[Lua/Game#peacefulmode]] to be not disturbed by the natives.
* You can stop the game in the right moment using SHIFT-SPACE key. That also blends the grid in.
* Learn how to use the [[Debug mode]] to add relevant information into the picture.
* Go into the highest zoom level you possibly can without missing any vital information.
* A good in-game picture should be rebuilt so that only the relevant entities/items are shown. Anything in the photo other than what you're trying to show/explain is unnecessary.

Dont's:

* Don't take pictures of clutter! The only stuff in the photo should be the stuff you're trying to show. The Exception to Clutter: If you're showing what a fully finished factory or setup might look like.
* Don't just take a screenshot. Try to remove all unneeded information from the picture.
* Try to make a picture without the character, except if to show something; then face the character toward it.

See http://www.factorioforums.com/forum/viewtopic.php?f=6&t=2472 for more.

== Taking Screenshots, animations and videos==

=== Taking Screenshots ===

* It's possible to take [[Lua/Game#takescreenshot|screenshots out of the game]]! The [http://www.youtube.com/watch?v=9yDZM0diiYc second trailer] is made like so. See http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5591
* [http://www.factorioforums.com/forum/viewtopic.php?f=18&t=5591 Calculate screenshoot dimensions].

==== Optimizing the picture before upload ====

* Cut as much as possible/nice.
* Resolution should not normally be higher than 600x600 px. Use multiple photos or ask a trusted wiki user if you need a much larger photo.
* ''Do not add text to the photos'' Write any needed text outside the photo on the wiki. You cannot search text that is in a photo and users might not find what they are looking for.
* Sharpen the pictures. For the wiki it looks a lot better to sharpen the pictures once or twice.