Official Factorio Wiki - User contributions [en]

Talk:Fusion reactor

2026-04-04T10:42:53Z

DRY411S:

The panel on the right of this page is using the generic word 'Drain' for power consumption by the reactor. Stricty, this not correct. The way the reactor works, it consumes power proportional to the plasma it is producing, i.e. proportional to the generator output.

At rest, the reactor has zero drain.

When the generators are generating 10MW because that's all the factory needs, the reactor consumes 1MW.

Only when the generators are producing 100MW does the reactor consume 10MW.

Talk:Fusion reactor

2026-04-04T09:42:59Z

DRY411S: Created page with "The panel on the right of this page is using the generic word 'Drain' for power consumption by the reactor. Stricty, this not correct. The way the reactor works, it consumes power proportion to the plasma it is producing, i.e. proportional to the generator output. At rest, the reactor has zero drain. When the generators are generating 10MW because that's all the factory needs, the reactor consumes 1MW. Only when the generators are producing 100MW does the reactor consum..."

The panel on the right of this page is using the generic word 'Drain' for power consumption by the reactor. Stricty, this not correct. The way the reactor works, it consumes power proportion to the plasma it is producing, i.e. proportional to the generator output.

At rest, the reactor has zero drain.
When the generators are generating 10MW because that's all the factory needs, the reactor consumes 1MW.
Only when the generators are producing 100MW does the reactor consume 10MW.

Achievements

2025-05-09T11:12:52Z

DRY411S: Clarification about multiplayer. The 50% online constraint is per map.

{{Languages}}
'''Achievements''' are given to the player when certain events happen or criteria is fulfilled. Some achievements are meant to make the player feel invested in the game. Others are meant to guide the player to use different strategies and optional game mechanics. Achievements are available in both the [http://store.steampowered.com/app/427520/ Steam] and standalone versions. There are 88 achievements available: 59 in the base game, and an additional 29 when using [[Space Age]]{{SA}}.

== Disabling achievements ==
[[File:achievement_list.png|thumb|200px|right|Achievement list in-game.]]Achievements can only be unlocked in the default game mode, called ''Freeplay''. Any scenarios, such as the [[tutorial]] or [[scenario system|custom scenarios]] disable achievements. Furthermore, using script or cheat commands in the [[Console#Scripting_and_cheat_commands|console]] disables achievements, however the user will be warned about this the first time they try to run such a command. Within the freeplay game, enabling peaceful mode, enabling no enemies mode or setting enemy base frequency or size for [[Nauvis]] to anything lower than default, disables the following achievements:
* There is no spoon
* No time for chitchat
* Raining bullets
* Steam all the way
* Keeping your hands clean
* It stinks and they don't like it
* It stinks and they do like it{{SA}}
* Get off my lawn{{SA}}
* Work around the clock{{SA}}
* Express delivery{{SA}}

Any other changes to map generation or using the [[debug mode]]s does not disable achievements.

A separate instance of achievements will be used when mods are installed and earned achievements will not register with Steam. In multiplayer, achievements can only be earned if the player has spent more than 50% of the time online on the map where the achievement is being awarded.

Re-enabling achievements again can be achieved by editing the binary data of a save. ([https://forums.factorio.com/58077 reference])

== List of base game achievements ==
The search function of a browser may be used to find a specific achievement faster. This is usually {{keybinding|Ctrl|F}}


{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|automate-this}}
| If placing an assembling machine 1 is bypassed by handcrafting and only a [[assembling machine 2]] is placed, placing that assembler will ''not'' unlock this achievement.
|
|-
| {{Achievement|getting-on-track}}
| The locomotive must be placed on [[rail]]s, not just crafted.
|
|-
| {{Achievement|arachnophilia}}
|
| Arachnophilia means "love of spiders".
|-
| {{Achievement|eco-unfriendly}}
|
|
|-
| {{Achievement|steam-power}}
|
|
|-
| {{Achievement|solar-power}}
|
|
|-
| {{Achievement|nuclear-power}}
|
|
|-
| {{Achievement|crafting-with-speed}}
|
|
|-
| {{Achievement|crafting-with-efficiency}}
|
|
|-
| {{Achievement|crafting-with-productivity}}
|
|
|-
| {{Achievement|smoke-me-a-kipper-i-will-be-back-for-breakfast}}
|
| This line was spoken by Ace Rimmer from the British sci-fi comedy show ''Red Dwarf''.
|-
| {{Achievement|it-stinks-and-they-dont-like-it}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|The line "He stinks and I don't like him" was spoken by comedian Jim Norton in the 2002 film Spider-Man. It became a regular sound drop on the radio program Opie and Anthony, where Norton was third mic.
|-
| {{Achievement|automated-construction}}
|
|
|-
| {{Achievement|you-are-doing-it-right}}
|
|
|-
| {{Achievement|automated-cleanup}}
|
|
|-
| {{Achievement|you-have-got-a-package}}
|
|
|-
| {{Achievement|delivery-service}}
|
|
|-
| {{Achievement|trans-factorio-express}}
|
| Refers to the ''Trans-Europ Express'', an international passenger railway company that served west and central Europe from 1957 to 1995.
|-
| {{Achievement|watch-your-step}}
|
|
|-
| {{Achievement|golem}}
| It is possible to get this achievement by getting hit by a moving locomotive, while having a sufficient amount of energy shields.
|
|-
| {{Achievement|mining-with-determination}}
|
|
|-
| {{Achievement|getting-on-track-like-a-pro}}
|
|
|-
| {{Achievement|mass-production-1}}
|
|
|-
| {{Achievement|mass-production-2}}
|
|
|-
| {{Achievement|mass-production-3}}
| The number of circuits manufactured towards the Mass production 1, 2 and 3 achievements are accumulated across different maps. They do not have to be made on a single map.
|
|-
| {{Achievement|circuit-veteran-1}}
|
|
|-
| {{Achievement|circuit-veteran-2}}
|
|
|-
| {{Achievement|circuit-veteran-3}}
|
|
|-
| {{Achievement|computer-age-1}}
|
|
|-
| {{Achievement|computer-age-2}}
|
|
|-
| {{Achievement|computer-age-3}}
|
|
|-
| {{Achievement|iron-throne-1}}
|
| These three achievements refer to the Iron Throne, a large throne in the fantasy novel series ''A Song of Ice and Fire'' made from many swords fused together with dragonfire.
|-
| {{Achievement|iron-throne-2}}
|
|
|-
| {{Achievement|iron-throne-3}}
|
|
|-
| {{Achievement|solaris}}
| The electric network may not have any electricity producers besides solar panels connected to it.
| ''Solaris'' is a 1961 philosophical sci-fi novel written by Stanisław Lem, and a Unix-based computer operating system.
|-
| {{Achievement|research-with-automation}}
|
|
|-
| {{Achievement|research-with-logistics}}
|
|
|-
| {{Achievement|research-with-chemicals}}
|
|
|-
| {{Achievement|research-with-military}}
|
|
|-
| {{Achievement|research-with-production}}
|
|
|-
| {{Achievement|research-with-utility}}
|
|
|-
| {{Achievement|research-with-space}}
|
|
|-
| {{Achievement|tech-maniac}}
| Completing infinite technologies of any level is not required. All non-infinite levels of technologies that have infinite continuations are still required (for example, it requires only first 6 levels of [[physical projectile damage (research)|physical projectile damage]]). The achievement's condition is checked when any technology (finite or infinite) is researched.
|
|-
| {{Achievement|pest-control}}
|
|
|-
| {{Achievement|steamrolled}}
|
| 'Steamroll' generally refers to a multiplayer match in which one team is performing significantly better than the other.
|-
| {{Achievement|pyromaniac}}
|
|
|-
| {{Achievement|run-forrest-run}}
|
| This line was spoken by Jenny Curran in the 1994 drama film ''Forrest Gump''.
|-
| {{Achievement|terraformer}}
|
|
|-
| {{Achievement|destroyer-of-worlds}}
|
| A variation of a quote from physicist J. Robert Oppenheimer upon his invention of the atomic bomb.
|-
| {{Achievement|minions}}
| This achievement requires follower robot count level 11 for a total of 100 robots. 6 rocket launches are needed to obtain the space science packs to get to and research level 11.
|
|-
| {{Achievement|art-of-siege}}
|
|
|-
| {{Achievement|keeping-your-hands-clean}}
| This achievement becomes disabled if you manually destroy a [[Enemies#Nests|spawner]] before destroying one using artillery. Destroying worms are allowed. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|lazy-bastard}}
| In multiplayer, the crafts of all players are counted towards this achievement. The minimum amount of items crafted by hand is 101 if the player uses the stone furnace in the starting inventory to craft the boiler necessary to power a lab for the [[automation (research)]].
|
|-
| {{Achievement|steam-all-the-way}}
| Only ''placing'' solar panels breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|raining-bullets}}
| Only ''placing'' laser turrets breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|logistic-network-embargo}}
|
|
|-
| {{Achievement|no-time-for-chitchat}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|there-is-no-spoon}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
| This line was spoken by Spoon Boy in the 1999 sci-fi action film ''The Matrix''.
|-
| {{Achievement|so-long-and-thanks-for-all-the-fish}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Send a [[raw fish]] into space via [[rocket silo|rocket]].}}
| The last message left by the dolphins before leaving Earth in ''The Hitchhiker's Guide to the Galaxy''. Also the name of the fourth book in the series.
|}

== List of Space Age expansion achievements ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|fusion-power}}
|
|
|-
| {{Achievement|reach-for-the-stars}}
|
|
|-
| {{Achievement|visit-fulgora}}
|
|
|-
| {{Achievement|visit-gleba}}
|
|
|-
| {{Achievement|visit-vulcanus}}
|
|
|-
| {{Achievement|visit-aquilo}}
|
|
|-
| {{Achievement|make-it-better}}
|
|
|-
| {{Achievement|crafting-with-quality}}
|
|
|-
| {{Achievement|second-star-to-the-right-and-straight-on-till-morning}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
| The directions to the island of Never Land, as told in the various adaptations of the character Peter Pan
Also the last order Captain Kirk gives to the Enterprise in ''Star Trek VI: The Undiscovered Country''
|-
| {{Achievement|it-stinks-and-they-do-like-it}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
Spores are affected by the pollution map settings, disabling pollution when generating the map will prevent you from earning this achievement.
|
|-
| {{Achievement|get-off-my-lawn}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
| Quote from Gran Torino movie.
|-
| {{Achievement|shattered-planet-1}}
|
|
|-
| {{Achievement|shattered-planet-2}}
|
|
|-
| {{Achievement|shattered-planet-3}}
|
|
|-
| {{Achievement|research-with-metallurgics}}
|
|
|-
| {{Achievement|research-with-agriculture}}
|
|
|-
| {{Achievement|research-with-electromagnetics}}
|
|
|-
| {{Achievement|research-with-cryogenics}}
|
|
|-
| {{Achievement|research-with-promethium}}
|
|
|-
| {{Achievement|rush-to-space}}
| This achievement becomes disabled if you finish researching [[Production_science_pack_(research)|production science]] or [[Utility_science_pack_(research)|utility science]]
|
|-
| {{Achievement|if-it-bleeds}}
|
| Arnold Schwarzenegger quote from Predator (1987) movie.
|-
| {{Achievement|we-need-bigger-guns}}
|
| Quote from Split Second movie.
|-
| {{Achievement|size-doesnt-matter}}
|
| Wink wink.
|-
| {{Achievement|look-at-my-shiny-rare-armor}}
|
|
|-
| {{Achievement|todays-fish-is-trout-a-la-creme}}
|
| This line was spoken by a machine dispensing said fish in the British sci-fi comedy show ''Red Dwarf.''
|-
| {{Achievement|my-modules-are-legendary}}
|
|
|-
| {{Achievement|no-room-for-more}}
|
|
|-
| {{Achievement|work-around-the-clock}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
|
|-
| {{Achievement|express-delivery}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
|
|}

== History ==
{{History|2.0.31|
* Disabled achievements "It stinks and they don't like it", "It stinks and they do like it", and "Get off my lawn" in peaceful mode and no enemies mode.
}}

{{History|2.0.9|
* Logistic network embargo achievement now have different condition for base game and [[space age]]{{SA}}.
}}

{{History|2.0.7|
* Added new achievements.
}}

{{History|0.13.0|
* Introduced.
}}

== See also ==
* [[Console]]
* [https://www.factorio.com/blog/post/fff-125 Friday Facts #125 - Achievements]

{{C|Main}}

Achievements

2025-05-09T11:08:41Z

DRY411S:

{{Languages}}
'''Achievements''' are given to the player when certain events happen or criteria is fulfilled. Some achievements are meant to make the player feel invested in the game. Others are meant to guide the player to use different strategies and optional game mechanics. Achievements are available in both the [http://store.steampowered.com/app/427520/ Steam] and standalone versions. There are 88 achievements available: 59 in the base game, and an additional 29 when using [[Space Age]]{{SA}}.

== Disabling achievements ==
[[File:achievement_list.png|thumb|200px|right|Achievement list in-game.]]Achievements can only be unlocked in the default game mode, called ''Freeplay''. Any scenarios, such as the [[tutorial]] or [[scenario system|custom scenarios]] disable achievements. Furthermore, using script or cheat commands in the [[Console#Scripting_and_cheat_commands|console]] disables achievements, however the user will be warned about this the first time they try to run such a command. Within the freeplay game, enabling peaceful mode, enabling no enemies mode or setting enemy base frequency or size for [[Nauvis]] to anything lower than default, disables the following achievements:
* There is no spoon
* No time for chitchat
* Raining bullets
* Steam all the way
* Keeping your hands clean
* It stinks and they don't like it
* It stinks and they do like it{{SA}}
* Get off my lawn{{SA}}
* Work around the clock{{SA}}
* Express delivery{{SA}}

Any other changes to map generation or using the [[debug mode]]s does not disable achievements.

A separate instance of achievements will be used when mods are installed and earned achievements will not register with Steam. In multiplayer, achievements can only be earned if the player has spent more than 50% of the time online.

Re-enabling achievements again can be achieved by editing the binary data of a save. ([https://forums.factorio.com/58077 reference])

== List of base game achievements ==
The search function of a browser may be used to find a specific achievement faster. This is usually {{keybinding|Ctrl|F}}


{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|automate-this}}
| If placing an assembling machine 1 is bypassed by handcrafting and only a [[assembling machine 2]] is placed, placing that assembler will ''not'' unlock this achievement.
|
|-
| {{Achievement|getting-on-track}}
| The locomotive must be placed on [[rail]]s, not just crafted.
|
|-
| {{Achievement|arachnophilia}}
|
| Arachnophilia means "love of spiders".
|-
| {{Achievement|eco-unfriendly}}
|
|
|-
| {{Achievement|steam-power}}
|
|
|-
| {{Achievement|solar-power}}
|
|
|-
| {{Achievement|nuclear-power}}
|
|
|-
| {{Achievement|crafting-with-speed}}
|
|
|-
| {{Achievement|crafting-with-efficiency}}
|
|
|-
| {{Achievement|crafting-with-productivity}}
|
|
|-
| {{Achievement|smoke-me-a-kipper-i-will-be-back-for-breakfast}}
|
| This line was spoken by Ace Rimmer from the British sci-fi comedy show ''Red Dwarf''.
|-
| {{Achievement|it-stinks-and-they-dont-like-it}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|The line "He stinks and I don't like him" was spoken by comedian Jim Norton in the 2002 film Spider-Man. It became a regular sound drop on the radio program Opie and Anthony, where Norton was third mic.
|-
| {{Achievement|automated-construction}}
|
|
|-
| {{Achievement|you-are-doing-it-right}}
|
|
|-
| {{Achievement|automated-cleanup}}
|
|
|-
| {{Achievement|you-have-got-a-package}}
|
|
|-
| {{Achievement|delivery-service}}
|
|
|-
| {{Achievement|trans-factorio-express}}
|
| Refers to the ''Trans-Europ Express'', an international passenger railway company that served west and central Europe from 1957 to 1995.
|-
| {{Achievement|watch-your-step}}
|
|
|-
| {{Achievement|golem}}
| It is possible to get this achievement by getting hit by a moving locomotive, while having a sufficient amount of energy shields.
|
|-
| {{Achievement|mining-with-determination}}
|
|
|-
| {{Achievement|getting-on-track-like-a-pro}}
|
|
|-
| {{Achievement|mass-production-1}}
|
|
|-
| {{Achievement|mass-production-2}}
|
|
|-
| {{Achievement|mass-production-3}}
| The number of circuits manufactured towards the Mass production 1, 2 and 3 achievements are accumulated across different maps. They do not have to be made on a single map.
|
|-
| {{Achievement|circuit-veteran-1}}
|
|
|-
| {{Achievement|circuit-veteran-2}}
|
|
|-
| {{Achievement|circuit-veteran-3}}
|
|
|-
| {{Achievement|computer-age-1}}
|
|
|-
| {{Achievement|computer-age-2}}
|
|
|-
| {{Achievement|computer-age-3}}
|
|
|-
| {{Achievement|iron-throne-1}}
|
| These three achievements refer to the Iron Throne, a large throne in the fantasy novel series ''A Song of Ice and Fire'' made from many swords fused together with dragonfire.
|-
| {{Achievement|iron-throne-2}}
|
|
|-
| {{Achievement|iron-throne-3}}
|
|
|-
| {{Achievement|solaris}}
| The electric network may not have any electricity producers besides solar panels connected to it.
| ''Solaris'' is a 1961 philosophical sci-fi novel written by Stanisław Lem, and a Unix-based computer operating system.
|-
| {{Achievement|research-with-automation}}
|
|
|-
| {{Achievement|research-with-logistics}}
|
|
|-
| {{Achievement|research-with-chemicals}}
|
|
|-
| {{Achievement|research-with-military}}
|
|
|-
| {{Achievement|research-with-production}}
|
|
|-
| {{Achievement|research-with-utility}}
|
|
|-
| {{Achievement|research-with-space}}
|
|
|-
| {{Achievement|tech-maniac}}
| Completing infinite technologies of any level is not required. All non-infinite levels of technologies that have infinite continuations are still required (for example, it requires only first 6 levels of [[physical projectile damage (research)|physical projectile damage]]). The achievement's condition is checked when any technology (finite or infinite) is researched.
|
|-
| {{Achievement|pest-control}}
|
|
|-
| {{Achievement|steamrolled}}
|
| 'Steamroll' generally refers to a multiplayer match in which one team is performing significantly better than the other.
|-
| {{Achievement|pyromaniac}}
|
|
|-
| {{Achievement|run-forrest-run}}
|
| This line was spoken by Jenny Curran in the 1994 drama film ''Forrest Gump''.
|-
| {{Achievement|terraformer}}
|
|
|-
| {{Achievement|destroyer-of-worlds}}
|
| A variation of a quote from physicist J. Robert Oppenheimer upon his invention of the atomic bomb.
|-
| {{Achievement|minions}}
| This achievement requires follower robot count level 11 for a total of 100 robots. 6 rocket launches are needed to obtain the space science packs to get to and research level 11.
|
|-
| {{Achievement|art-of-siege}}
|
|
|-
| {{Achievement|keeping-your-hands-clean}}
| This achievement becomes disabled if you manually destroy a [[Enemies#Nests|spawner]] before destroying one using artillery. Destroying worms are allowed. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|lazy-bastard}}
| In multiplayer, the crafts of all players are counted towards this achievement. The minimum amount of items crafted by hand is 101 if the player uses the stone furnace in the starting inventory to craft the boiler necessary to power a lab for the [[automation (research)]].
|
|-
| {{Achievement|steam-all-the-way}}
| Only ''placing'' solar panels breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|raining-bullets}}
| Only ''placing'' laser turrets breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|logistic-network-embargo}}
|
|
|-
| {{Achievement|no-time-for-chitchat}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|there-is-no-spoon}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
| This line was spoken by Spoon Boy in the 1999 sci-fi action film ''The Matrix''.
|-
| {{Achievement|so-long-and-thanks-for-all-the-fish}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Send a [[raw fish]] into space via [[rocket silo|rocket]].}}
| The last message left by the dolphins before leaving Earth in ''The Hitchhiker's Guide to the Galaxy''. Also the name of the fourth book in the series.
|}

== List of Space Age expansion achievements ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|fusion-power}}
|
|
|-
| {{Achievement|reach-for-the-stars}}
|
|
|-
| {{Achievement|visit-fulgora}}
|
|
|-
| {{Achievement|visit-gleba}}
|
|
|-
| {{Achievement|visit-vulcanus}}
|
|
|-
| {{Achievement|visit-aquilo}}
|
|
|-
| {{Achievement|make-it-better}}
|
|
|-
| {{Achievement|crafting-with-quality}}
|
|
|-
| {{Achievement|second-star-to-the-right-and-straight-on-till-morning}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
| The directions to the island of Never Land, as told in the various adaptations of the character Peter Pan
Also the last order Captain Kirk gives to the Enterprise in ''Star Trek VI: The Undiscovered Country''
|-
| {{Achievement|it-stinks-and-they-do-like-it}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
Spores are affected by the pollution map settings, disabling pollution when generating the map will prevent you from earning this achievement.
|
|-
| {{Achievement|get-off-my-lawn}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
| Quote from Gran Torino movie.
|-
| {{Achievement|shattered-planet-1}}
|
|
|-
| {{Achievement|shattered-planet-2}}
|
|
|-
| {{Achievement|shattered-planet-3}}
|
|
|-
| {{Achievement|research-with-metallurgics}}
|
|
|-
| {{Achievement|research-with-agriculture}}
|
|
|-
| {{Achievement|research-with-electromagnetics}}
|
|
|-
| {{Achievement|research-with-cryogenics}}
|
|
|-
| {{Achievement|research-with-promethium}}
|
|
|-
| {{Achievement|rush-to-space}}
| This achievement becomes disabled if you finish researching [[Production_science_pack_(research)|production science]] or [[Utility_science_pack_(research)|utility science]]
|
|-
| {{Achievement|if-it-bleeds}}
|
| Arnold Schwarzenegger quote from Predator (1987) movie.
|-
| {{Achievement|we-need-bigger-guns}}
|
| Quote from Split Second movie.
|-
| {{Achievement|size-doesnt-matter}}
|
| Wink wink.
|-
| {{Achievement|look-at-my-shiny-rare-armor}}
|
|
|-
| {{Achievement|todays-fish-is-trout-a-la-creme}}
|
| This line was spoken by a machine dispensing said fish in the British sci-fi comedy show ''Red Dwarf.''
|-
| {{Achievement|my-modules-are-legendary}}
|
|
|-
| {{Achievement|no-room-for-more}}
|
|
|-
| {{Achievement|work-around-the-clock}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
|
|-
| {{Achievement|express-delivery}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
|
|}

== History ==
{{History|2.0.31|
* Disabled achievements "It stinks and they don't like it", "It stinks and they do like it", and "Get off my lawn" in peaceful mode and no enemies mode.
}}

{{History|2.0.9|
* Logistic network embargo achievement now have different condition for base game and [[space age]]{{SA}}.
}}

{{History|2.0.7|
* Added new achievements.
}}

{{History|0.13.0|
* Introduced.
}}

== See also ==
* [[Console]]
* [https://www.factorio.com/blog/post/fff-125 Friday Facts #125 - Achievements]

{{C|Main}}

Achievements

2025-05-09T11:05:36Z

DRY411S: Clarification that the mass production achievements are cumulative.

{{Languages}}
'''Achievements''' are given to the player when certain events happen or criteria is fulfilled. Some achievements are meant to make the player feel invested in the game. Others are meant to guide the player to use different strategies and optional game mechanics. Achievements are available in both the [http://store.steampowered.com/app/427520/ Steam] and standalone versions. There are 88 achievements available: 59 in the base game, and an additional 29 when using [[Space Age]]{{SA}}.

== Disabling achievements ==
[[File:achievement_list.png|thumb|200px|right|Achievement list in-game.]]Achievements can only be unlocked in the default game mode, called ''Freeplay''. Any scenarios, such as the [[tutorial]] or [[scenario system|custom scenarios]] disable achievements. Furthermore, using script or cheat commands in the [[Console#Scripting_and_cheat_commands|console]] disables achievements, however the user will be warned about this the first time they try to run such a command. Within the freeplay game, enabling peaceful mode, enabling no enemies mode or setting enemy base frequency or size for [[Nauvis]] to anything lower than default, disables the following achievements:
* There is no spoon
* No time for chitchat
* Raining bullets
* Steam all the way
* Keeping your hands clean
* It stinks and they don't like it
* It stinks and they do like it{{SA}}
* Get off my lawn{{SA}}
* Work around the clock{{SA}}
* Express delivery{{SA}}

Any other changes to map generation or using the [[debug mode]]s does not disable achievements.

A separate instance of achievements will be used when mods are installed and earned achievements will not register with Steam. In multiplayer, achievements can only be earned if the player has spent more than 50% of the time online.

Re-enabling achievements again can be achieved by editing the binary data of a save. ([https://forums.factorio.com/58077 reference])

== List of base game achievements ==
The search function of a browser may be used to find a specific achievement faster. This is usually {{keybinding|Ctrl|F}}


{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|automate-this}}
| If placing an assembling machine 1 is bypassed by handcrafting and only a [[assembling machine 2]] is placed, placing that assembler will ''not'' unlock this achievement.
|
|-
| {{Achievement|getting-on-track}}
| The locomotive must be placed on [[rail]]s, not just crafted.
|
|-
| {{Achievement|arachnophilia}}
|
| Arachnophilia means "love of spiders".
|-
| {{Achievement|eco-unfriendly}}
|
|
|-
| {{Achievement|steam-power}}
|
|
|-
| {{Achievement|solar-power}}
|
|
|-
| {{Achievement|nuclear-power}}
|
|
|-
| {{Achievement|crafting-with-speed}}
|
|
|-
| {{Achievement|crafting-with-efficiency}}
|
|
|-
| {{Achievement|crafting-with-productivity}}
|
|
|-
| {{Achievement|smoke-me-a-kipper-i-will-be-back-for-breakfast}}
|
| This line was spoken by Ace Rimmer from the British sci-fi comedy show ''Red Dwarf''.
|-
| {{Achievement|it-stinks-and-they-dont-like-it}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|The line "He stinks and I don't like him" was spoken by comedian Jim Norton in the 2002 film Spider-Man. It became a regular sound drop on the radio program Opie and Anthony, where Norton was third mic.
|-
| {{Achievement|automated-construction}}
|
|
|-
| {{Achievement|you-are-doing-it-right}}
|
|
|-
| {{Achievement|automated-cleanup}}
|
|
|-
| {{Achievement|you-have-got-a-package}}
|
|
|-
| {{Achievement|delivery-service}}
|
|
|-
| {{Achievement|trans-factorio-express}}
|
| Refers to the ''Trans-Europ Express'', an international passenger railway company that served west and central Europe from 1957 to 1995.
|-
| {{Achievement|watch-your-step}}
|
|
|-
| {{Achievement|golem}}
| It is possible to get this achievement by getting hit by a moving locomotive, while having a sufficient amount of energy shields.
|
|-
| {{Achievement|mining-with-determination}}
|
|
|-
| {{Achievement|getting-on-track-like-a-pro}}
|
|
|-
| {{Achievement|mass-production-1}}
|
|
|-
| {{Achievement|mass-production-2}}
|
|
|-
| {{Achievement|mass-production-3}}
| The number of circuits manufactured towards the Mass production 1, 2 and 3 achievements are accumulated across different saves. They do not have to be made on a single map.
|
|-
| {{Achievement|circuit-veteran-1}}
|
|
|-
| {{Achievement|circuit-veteran-2}}
|
|
|-
| {{Achievement|circuit-veteran-3}}
|
|
|-
| {{Achievement|computer-age-1}}
|
|
|-
| {{Achievement|computer-age-2}}
|
|
|-
| {{Achievement|computer-age-3}}
|
|
|-
| {{Achievement|iron-throne-1}}
|
| These three achievements refer to the Iron Throne, a large throne in the fantasy novel series ''A Song of Ice and Fire'' made from many swords fused together with dragonfire.
|-
| {{Achievement|iron-throne-2}}
|
|
|-
| {{Achievement|iron-throne-3}}
|
|
|-
| {{Achievement|solaris}}
| The electric network may not have any electricity producers besides solar panels connected to it.
| ''Solaris'' is a 1961 philosophical sci-fi novel written by Stanisław Lem, and a Unix-based computer operating system.
|-
| {{Achievement|research-with-automation}}
|
|
|-
| {{Achievement|research-with-logistics}}
|
|
|-
| {{Achievement|research-with-chemicals}}
|
|
|-
| {{Achievement|research-with-military}}
|
|
|-
| {{Achievement|research-with-production}}
|
|
|-
| {{Achievement|research-with-utility}}
|
|
|-
| {{Achievement|research-with-space}}
|
|
|-
| {{Achievement|tech-maniac}}
| Completing infinite technologies of any level is not required. All non-infinite levels of technologies that have infinite continuations are still required (for example, it requires only first 6 levels of [[physical projectile damage (research)|physical projectile damage]]). The achievement's condition is checked when any technology (finite or infinite) is researched.
|
|-
| {{Achievement|pest-control}}
|
|
|-
| {{Achievement|steamrolled}}
|
| 'Steamroll' generally refers to a multiplayer match in which one team is performing significantly better than the other.
|-
| {{Achievement|pyromaniac}}
|
|
|-
| {{Achievement|run-forrest-run}}
|
| This line was spoken by Jenny Curran in the 1994 drama film ''Forrest Gump''.
|-
| {{Achievement|terraformer}}
|
|
|-
| {{Achievement|destroyer-of-worlds}}
|
| A variation of a quote from physicist J. Robert Oppenheimer upon his invention of the atomic bomb.
|-
| {{Achievement|minions}}
| This achievement requires follower robot count level 11 for a total of 100 robots. 6 rocket launches are needed to obtain the space science packs to get to and research level 11.
|
|-
| {{Achievement|art-of-siege}}
|
|
|-
| {{Achievement|keeping-your-hands-clean}}
| This achievement becomes disabled if you manually destroy a [[Enemies#Nests|spawner]] before destroying one using artillery. Destroying worms are allowed. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|lazy-bastard}}
| In multiplayer, the crafts of all players are counted towards this achievement. The minimum amount of items crafted by hand is 101 if the player uses the stone furnace in the starting inventory to craft the boiler necessary to power a lab for the [[automation (research)]].
|
|-
| {{Achievement|steam-all-the-way}}
| Only ''placing'' solar panels breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|raining-bullets}}
| Only ''placing'' laser turrets breaks the requirement of this achievement, simply crafting them does not disqualify the player from earning the achievement. Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|logistic-network-embargo}}
|
|
|-
| {{Achievement|no-time-for-chitchat}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
|
|-
| {{Achievement|there-is-no-spoon}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
| This line was spoken by Spoon Boy in the 1999 sci-fi action film ''The Matrix''.
|-
| {{Achievement|so-long-and-thanks-for-all-the-fish}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Send a [[raw fish]] into space via [[rocket silo|rocket]].}}
| The last message left by the dolphins before leaving Earth in ''The Hitchhiker's Guide to the Galaxy''. Also the name of the fourth book in the series.
|}

== List of Space Age expansion achievements ==

{| class="wikitable"
|-
! style="min-width:350px" | Achievement !! Notes !! Trivia
|-
| {{Achievement|fusion-power}}
|
|
|-
| {{Achievement|reach-for-the-stars}}
|
|
|-
| {{Achievement|visit-fulgora}}
|
|
|-
| {{Achievement|visit-gleba}}
|
|
|-
| {{Achievement|visit-vulcanus}}
|
|
|-
| {{Achievement|visit-aquilo}}
|
|
|-
| {{Achievement|make-it-better}}
|
|
|-
| {{Achievement|crafting-with-quality}}
|
|
|-
| {{Achievement|second-star-to-the-right-and-straight-on-till-morning}}
| {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
| The directions to the island of Never Land, as told in the various adaptations of the character Peter Pan
Also the last order Captain Kirk gives to the Enterprise in ''Star Trek VI: The Undiscovered Country''
|-
| {{Achievement|it-stinks-and-they-do-like-it}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
Spores are affected by the pollution map settings, disabling pollution when generating the map will prevent you from earning this achievement.
|
|-
| {{Achievement|get-off-my-lawn}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings.
| Quote from Gran Torino movie.
|-
| {{Achievement|shattered-planet-1}}
|
|
|-
| {{Achievement|shattered-planet-2}}
|
|
|-
| {{Achievement|shattered-planet-3}}
|
|
|-
| {{Achievement|research-with-metallurgics}}
|
|
|-
| {{Achievement|research-with-agriculture}}
|
|
|-
| {{Achievement|research-with-electromagnetics}}
|
|
|-
| {{Achievement|research-with-cryogenics}}
|
|
|-
| {{Achievement|research-with-promethium}}
|
|
|-
| {{Achievement|rush-to-space}}
| This achievement becomes disabled if you finish researching [[Production_science_pack_(research)|production science]] or [[Utility_science_pack_(research)|utility science]]
|
|-
| {{Achievement|if-it-bleeds}}
|
| Arnold Schwarzenegger quote from Predator (1987) movie.
|-
| {{Achievement|we-need-bigger-guns}}
|
| Quote from Split Second movie.
|-
| {{Achievement|size-doesnt-matter}}
|
| Wink wink.
|-
| {{Achievement|look-at-my-shiny-rare-armor}}
|
|
|-
| {{Achievement|todays-fish-is-trout-a-la-creme}}
|
| This line was spoken by a machine dispensing said fish in the British sci-fi comedy show ''Red Dwarf.''
|-
| {{Achievement|my-modules-are-legendary}}
|
|
|-
| {{Achievement|no-room-for-more}}
|
|
|-
| {{Achievement|work-around-the-clock}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
|
|-
| {{Achievement|express-delivery}}
| Disabled when using no enemies, peaceful mode or lower than default enemy base frequency or size settings. {{spoiler|button-text=Spoiler! Click to view.|message=Travel to or past the Solar System Edge.}}
|
|}

== History ==
{{History|2.0.31|
* Disabled achievements "It stinks and they don't like it", "It stinks and they do like it", and "Get off my lawn" in peaceful mode and no enemies mode.
}}

{{History|2.0.9|
* Logistic network embargo achievement now have different condition for base game and [[space age]]{{SA}}.
}}

{{History|2.0.7|
* Added new achievements.
}}

{{History|0.13.0|
* Introduced.
}}

== See also ==
* [[Console]]
* [https://www.factorio.com/blog/post/fff-125 Friday Facts #125 - Achievements]

{{C|Main}}

Talk:Artillery wagon

2024-01-05T09:55:46Z

DRY411S: Perhaps some qualification needed about targetting worms

I suggest that the text about artillery wagons 'one shotting' worms needs some qualification. Whilst this is true of auto targetting, it's not always true of manual targetting, since you cannot be 100% certain that you have targetted the worm centrally.

Tutorial talk:Nuclear power

2023-01-10T16:15:09Z

DRY411S:

Apperantly there are multiple tutorials. Although there is no link from this page to the [[Tutorial]] page. Is it an idea to link to the Tutorial page? I am doubting in which format this is best implemented. Perhaps a section "See Also" ? --[[User:Hayertjez|Hayertjez]] ([[User talk:Hayertjez|talk]]) 13:57, 2 August 2018 (UTC)

:I support linking pages like [[power production]] and other power related tutorials in a see also section, but what kind of relevance do tutorials in general have for one specific tutorial? -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:18, 2 August 2018 (UTC)

::Seemingly there is a reference on the landing page to the tutorials. But I overlook that catergory because I do not consider myself a "Beginner" After visiting the nuclear power tutorial page I thought, there could be more tutorials but where?. So I removed :Nulcear_Power from the Nuclear power URL to see if there are more tutorials available, and they where. Then I thought is there a category Tutorials or so but could not find them. So I posted this message to think about a better guidance to the Tutorials (even if the content is not so much for beginners). Perhaps it is good the way it is and my finding of the page tutorials is too special to adjust the current setup. {{Unsigned|Hayertjez|14:54, 2 August 2018‎}}

:::Thanks for the info. I have added a see also section that includes a link to the overview page, I hope it's what you were looking for. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:48, 2 August 2018 (UTC)
:::: Great, I hope this helps future users. Also thanks for considering my feedback. --[[User:Hayertjez|Hayertjez]] ([[User talk:Hayertjez|talk]]) 06:45, 3 August 2018 (UTC)

== Possible error in [[Tutorial:Nuclear_power#Always_on.21|Always on]] section ==

<blockquote>Since exchanges produce 120 steam/second and a tank holds 25k steam, a tank will keep 208 seconds worth of heat exchanger.</blockquote>

If I understand correctly, the numbers should be "103 steam/second" and "242.5 seconds". [[User:Diraria|Diraria]] ([[User talk:Diraria|talk]]) 18:31, 15 June 2019 (UTC)
:From what I know, you are right, so please correct the page :) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 18:34, 15 June 2019 (UTC)

== Error in the raw resource cost ==

The section "Raw resource cost of running a single reactor (late game)" contains an error. It assume all U235 will be produced by Kovarex enrichment. In fact, some U235 will be produced by ore processing, and that reduces the resource cost a little. By my calculations, the cost of running one reactor for one second is not 0.08 uranium ore per second as stated, but 40/507 ≈ 0.0789 uranium ore per second. I did not correct the calculations because I believe adding this level of detail is more likely to confuse than clarify. However, for correctness, I think it is necessary to document that the 0.08 ore per second is an approximation, so I added a note to that effect.

== How is the power/distance table for heat pipes calculated? ==

I built a setup with a 70 tile long heat pipe outgoing from a 80 MW reactor and one heat exchanger at the last pipe. There were still 857°C incoming. How is your table calculated? It is not clear how heat exchangers act there. Is it necessary to change all of the reactors heat performance into steam and then the last exchangers should be placed at most at the given distance?

--[[User:DRY411S|DRY411S]] ([[User talk:DRY411S|talk]]) 16:15, 10 January 2023 (UTC) I really don't understand this table either.

Talk:Processing unit

2022-04-04T15:02:41Z

DRY411S: /* Define factory in the wiki */

== About the ratio edit ==

It's not correct as it stands. The article says "factories", and a "factory" is the black box where the corresponding item pops out. How the factory achieves this, and what's inside that factory, isn't relevant. So the ratio change is wrong. A ratio of 5:6:5 (green factories:red factories:blue factories) was and is correct for this point of view.

If you change "factory" into "assembling machine", it would be correct, because you need green assembling machines to produce red circuits. So the new ratio 6:5:5 is correct for (green assembling machines:red assembling machines:blue assembling machines). If seen this way, all assembling machines define one big blue factory and no separate green or red factories.

Since the articles about the other circuits also speak of factories and don't count the intermediates needed within them (otherwise you need more copper cable factories for the advanced circuit), I suggest to revert to the previous ratio to keep things consistent. One doesn't always build green circuits on the spot within a red or blue circuit factory - often if not usually it comes preproduced from a bus, outside the "factory".
[[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 14:37, 4 April 2022 (UTC)

== Define factory in the wiki ==

I suggested an edit here because I thought the ratios were incorrect. There has been a counter suggestion
that they are correct because the page refers to ''factories'', whereas I was referring to ''assembling'' ''machines''.

I don't believe that the definition of factory claimed here is understood. It certainly isn't defined anywhere in the wiki.

For example is a processing unit factory, 1 assembling machine, or 5 machines? Should the page instead reference 1 green 'factory' and 1.2 red factories per blue factory?

This isn't helped because just before the definition of ratios, assembling machines are referenced.

Talk:Processing unit

2022-04-04T14:54:59Z

DRY411S: /* Define factory in the wiki */ new section

Processing unit

2022-04-02T13:29:45Z

DRY411S: Ratio is 6:6:5 green:red:blue not 5:6:5

{{languages}}
{{:Infobox:Processing unit}}

The '''Processing Unit''' (or "blue circuit") is the third tier of circuit, and is used in many late game recipes, mainly for making [[utility science pack]]s, [[module]]s, modular armor and its equipment, and the [[rocket silo]] and parts for the rocket.

The ratios of assembling machines to craft this item are:

; Normal mode:
* 6 [[Electronic circuit]] factories + 6 [[Advanced circuit]] factories + 0.05 [[Sulfuric acid]] plants → 5 ''Processing Unit'' factories

; Expensive mode:
* 6 [[Electronic circuit]] factories + 6 [[Advanced circuit]] factories + 0.10 [[Sulfuric acid]] plants → 5 ''Processing Unit'' factories

== Achievements ==
{{Achievement|computer-age-1}}
{{Achievement|computer-age-2}}
{{Achievement|computer-age-3}}

== History ==

{{history|0.9.0|
* Introduced}}

{{IntermediateNav}}
{{C|Components}}

User:DRY411S

2018-02-25T13:25:00Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system GUI is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI. (Click on the thumbnail for the full size version, which takes you away from this page.)

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. New players who join a multiplayer server are placed in the default group (unless any mods place them in a different group). The default group has all permissions enabled at the start of a new multiplayer game.

At this point, with the permissions GUI open, groups can be removed, added, cloned or edited by clicking on one of the icons in the top left of the GUI.

'''Note:''' The default group cannot be removed, but it can be edited.

Selecting a group from the list and clicking on the 'Edit selected group' icon opens the permission settings gui. (Click on the thumbnail for the full size version, which takes you away from this page.)

[[File:Permissionsettings.PNG|239px|none|left|link={{filepath:Permissionsettings.PNG}}|The Permissions settings GUI. Click for full size image]]

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, there is no localisation, and English is always used (as at version 0.16.25)

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T11:38:28Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system GUI is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI. (Click on the thumbnail for the full size version, which takes you away from this page.)

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. New players who join a multiplayer server are placed in the default group (unless any mods place them in a different group). The default group has all permissions enabled at the start of a new multiplayer game.

At this point, with the permissions GUI open, groups can be removed, added, cloned or edited by clicking on one of the icons in the top left of the GUI.

'''Note:''' The default group cannot be removed, but it can be edited.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, there is no localisation, and English is always used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T11:16:06Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system GUI is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI. (Click on the thumbnail for the full size version, which takes you away from this page.)

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, there is no localisation, and English is always used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T11:15:25Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system GUI is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI. Click on the thumbnail for the full size version, which takes you away from this page.[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, there is no localisation, and English is always used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T11:12:31Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI. Click on the thumbnail for the full size version, which takes you away from this page.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, there is no localisation, and English is always used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:59:21Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, there is no localisation, and English is always used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:58:39Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, ther is no localisation, and English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:57:38Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI, are only available to admins, regardless of the group. Other permissions do not affect how a player interacts with the online game, but are used by mods to establish whether certain events will be received by players.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'station', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players different roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints
* Anti-grief. Disable player permissions to mine, and limit the use of the deconstruction planner to be rocks and trees only

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:48:29Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console ''by admins only''
<pre>/permissions</pre>

This opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI relate to mods that might access the permissions system, rather than how a player interacts with the online game.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected.

In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:47:18Z

DRY411S: /* Console Commands for player management */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console
<pre>/permissions</pre>

This opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI relate to mods that might access the permissions system, rather than how a player interacts with the online game.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected.

In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:44:20Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console
<pre>/permissions</pre>

This opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled.

This is slightly misleading, as some of the permissions presented in the in-game GUI relate to mods that might access the permissions system, rather than how a player interacts with the online game.

The permissions are listed in the GUI in the alphabetic order of their defines.action-item.<name> rather than grouping according to what parts of the game are affected.

In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:40:00Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console by typing the command /permissions which opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog. Click for full size image]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled. This is slightly misleading, as some of the permissions that are enabled relate to be able to modify the permissions system, but only admins can access the system!

The permissions are listed in the GUI in the alphabetic order of their defines.action-item name rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:35:25Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console by typing the command /permissions which opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|link={{filepath:Permissionsgui.PNG}}|The Main Permissions GUI Dialog]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled. This is slightly misleading, as some of the permissions that are enabled relate to be able to modify the permissions system, but only admins can access the system!

The permissions are listed in the GUI in the alphabetic order of their defines.action-item name rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:31:35Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console by typing the command /permissions which opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|none|left|The Main Permissions GUI Dialog]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled. This is slightly misleading, as some of the permissions that are enabled relate to be able to modify the permissions system, but only admins can access the system!

The permissions are listed in the GUI in the alphabetic order of their defines.action-item name rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:26:44Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console by typing the command /permissions which opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|thumb|left|The Main Permissions GUI Dialog]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled. This is slightly misleading, as some of the permissions that are enabled relate to be able to modify the permissions system, but only admins can access the system!

The permissions are listed in the GUI in the alphabetic order of their defines.action-item name rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:21:01Z

DRY411S: /* The Permissions System */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console by typing the command /permissions which opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|thumb|The Main Permissions GUI Dialog]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled. This is slightly misleading, as some of the permissions that are enabled relate to be able to modify the permissions system, but only admins can access the system!

The permissions are listed in the GUI in the alphabetic order of their defines.action-item name rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T10:17:42Z

DRY411S: /* Multiplayer Admin Features */

An old grey bloke who likes fiddling about with computers.

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Where a / is used between < and > braces this indicates a list of options that can be used. Anywhere else where the < and > braces are used, you may type any text.

Print a list of game admins
<pre>/admins</pre>
Ban a player.
<pre>/ban <player> <reason></pre>
:The <reason> is stored where?
To manage the banned list
<pre>/banlist <add/remove/get/clear> <player></pre>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players

Print a list of banned players (is the same as /banlist get)
<pre>/bans</pre>
Delete the blueprint library storage for the player (if offline) from the save file.
<pre>/delete-blueprint-library <player></pre>
:If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed

Demote a player from being an admin
<pre>/demote <player></pre>
Forcibly disconnect a player from the server ''but do not ban them''
<pre>/kick <player> <reason></pre>
:The <reason> is stored where?
Open another player's inventory
<pre>/open <player></pre>
Open the Permissions GUI. See this link
<pre>/permissions</pre>
Promote a player to admin
<pre>/promote <player></pre>
:Clear all the messages by a player from the chat log
<pre>/purge <player></pre>
Swap player characters
<pre>/swap-players <player1> <player2></pre>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
Unban a player
<pre>/unban <player></pre>
Whitelist management. If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
<pre>/whitelist <add/remove/get/clear> <player></pre>
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
In multiplayer, factorio has a system that allows:
* Groups to created
* Permissions to be assigned to groups
* Players to be placed in one of the groups

In game, the permissions system is accessed at the console by typing the command /permissions which opens the permissions system GUI.

[[File:Permissionsgui.PNG|320px|thumb|left|The Main Permissions GUI Dialog]]

At the start of a multiplayer game, all players, including admins, are placed in a default group called 'default'. The default group has all permissions enabled. This is slightly misleading, as some of the permissions that are enabled relate to be able to modify the permissions system, but only admins can access the system!

The permissions are listed in the GUI in the alphabetic order of their defines.action-item name rather than grouping according to what parts of the game are affected. In this GUI, English is ALWAYS used (as at version 0.16.25)

'''Tip:''' Use the search system in the GUI to find permissions that belong together. Use searches like 'research', 'craft', 'blueprint', 'train', 'signal', 'combinator', 'deconstruct'.

By creating groups, assigning permissions to groups, and placing players into those groups, it is possible to give players roles in a multiplayer game. Examples include (but are limited to):

* Spectators. Players who can only walk and not interact in any other may with the map
* Train drivers. Players who can lay rails, signals, stations, connect and disconnect rolling stock, and give train orders
* Scientists. Start, and cancel research
* Architects. Design, import, export and place blueprints

=== Chatting with other players ===
stub

User:DRY411S

2018-02-25T09:56:34Z

DRY411S: /* Console Commands for player management */

User:DRY411S

2018-02-25T09:40:12Z

DRY411S: /* Console Commands for player management */

User:DRY411S

2018-02-25T09:27:44Z

DRY411S:

Multiplayer

2018-02-25T09:27:27Z

DRY411S: /* Chatting with other players */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

User:DRY411S

2018-02-25T09:26:57Z

DRY411S:

Multiplayer

2018-02-25T09:26:36Z

DRY411S: /* Multiplayer Admin Features */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T13:20:55Z

DRY411S: /* Console Commands for server and game management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/open <player>
:Opens another player's inventory
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:39:53Z

DRY411S: /* Multiplayer Admin Features */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/open <player>
:Opens another player's inventory
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:39:00Z

DRY411S: /* Console Commands for server and game management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/open <player>
:Opens another player's inventory
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:38:36Z

DRY411S: /* Console Commands for server and game management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/open <player>
:Opens another player's inventory
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/perf-avg-frames
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:26:09Z

DRY411S: /* Console Commands for player management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/open <player>
:Opens another player's inventory
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/perf-avg-frames
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:25:54Z

DRY411S: /* Console Commands for player management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;open <player>
:Opens another player's inventory
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/perf-avg-frames
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:24:26Z

DRY411S: /* Console Commands for server and game management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/perf-avg-frames
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:21:59Z

DRY411S: /* Player Groups and Permissions */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/open
/perf-avg-frames
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== The Permissions System ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:20:07Z

DRY411S: Amended pre-amble to include the Admin features section

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, how to join one, and the Multiplayer Admin features for managing other users and the server. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/open
/perf-avg-frames
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:14:56Z

DRY411S: /* Console Commands for server and game management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/measured-command
/open
/perf-avg-frames
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:11:45Z

DRY411S: /* Console Commands for player management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/delete-blueprint-library <player>
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/delete-blueprint-library
/measured-command
/open
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T12:04:16Z

DRY411S: /* Console Commands for player management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
;/admins
:Prints a list of game admins
;/ban <player> <reason>
:Bans the specified player. The <reason> is stored where?
;/banlist <add/remove/get/clear>
:add - is the same as /ban <player> <reason>
:remove - is the same as /unban <player>
:get - prints a list of banned players
:clear - unbans all banned players
;/bans
:prints a list of banned players (is the same as /banlist get)
;/demote <player>
:Demotes the player from being an admin
;/kick <player> <reason>
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where?
;/permissions
:Opens the permissions GUI. See this link
;/promote <player>
:Promotes the player to admin
;/purge <player>
:Clears all the messages by this user from the chat log
;/swap-players <player1> <player2>
:If player2 is empty, swaps your character with the given players character
:If player2 is not empty, swaps the two player characters
;/unban <player>
:Unbans the specified player
;/whitelist <add/remove/get/clear> <player>
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
:add - Adds the player to a whitelist
:remove - Removes the player from the whitelist
:get - prints the whitelist
:clear - empties the whitelist. Any player can join the game.

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/delete-blueprint-library
/measured-command
/open
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T11:43:37Z

DRY411S: /* Console Commands for player management */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
;/admins
:stub
;/ban
:stub
;/banlist
:stub
;/bans
:stub
;/demote
:stub
;/kick
:stub
;/permissions
:stub
;/promote
:stub
;/purge
:stub
;/swap-players
:stub
;/whitelist
:stub

=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/delete-blueprint-library
/measured-command
/open
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T11:36:32Z

DRY411S: /* Admin Console Commands */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Console Commands for player management ===
/admins
/ban
/banlist
/bans
/demote
/kick
/permissions
/promote
/purge
/swap-players
/whitelist
=== Console Commands for server and game management ===
/alerts (admin only?)
/config
/delete-blueprint-library
/measured-command
/open
/seed (admin only?)
/server-save
/silent-command
/toggle-heavy-mode
/help

=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T11:25:27Z

DRY411S: /* Chatting with other players */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Admin Console Commands ===
stub
=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
=== Chatting with other players ===
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T11:24:56Z

DRY411S: Stub for chatting

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Admin Console Commands ===
stub
=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.
== Chatting with other players ==
stub

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}

Multiplayer

2018-02-24T11:23:02Z

DRY411S: /* Multiplayer Features */

{{Languages}}

In addition to being a single-player game, Factorio also supports multiplayer, allowing many players to cooperate and assist each other, or work against each other in pvp. This page documents how to set up a multiplayer game, and how to join one. By default, multiplayer games run the CO-OP [[Game modes and options|freeplay scenario]] where all players work together to launch a rocket with a satellite into space. Other scenarios, including PvP maps, are available for download from the [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Maps and Scenarios forum].

== Setting Up a Multiplayer Game ==

Multiplayer games can be joined, hosted while playing, or hosted by a dedicated server. Multiplayer games can be advertised to other players on the same LAN or worldwide.

Use the ''Multiplayer'' button in the ''Play'' menu to start playing a multiplayer game, choose ''New'' or ''Load'' or ''Scenarios'' to host and play, or ''Browse'' or ''Play on LAN'' to connect to an already-running game. The host can also choose not to advertise the game at all, in which case you'll need the server's (public or otherwise reachable) IP address; you can then ''Connect'' directly to that to join the game.

Notes and tips:

* All game instances need the installation of ''exactly the same'' game-versions and mods.
* Factorio servers use port '''34197'''. The port can be changed in the [[Application directory|config]] file.
* Factorio uses '''UDP only'''. Make sure you configure your router's port forwarding correctly. (The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.)
** Make sure there is no firewall or anti-virus blocking the UDP-packets.
* The hard limit for the number of players is [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. However, practical limit for this is much lower, popular streamers have managed slightly over a hundred players.

=== Dedicated/Headless server ===

As of Factorio version 0.12.0 onwards, a dedicated (or headless) server can be started using the --start-server command line option. You can run factorio --help to get a list of all command-line arguments that Factorio accepts.

In the headless mode:
* Graphics are not initialized (faster start up, less memory usage, works on completely headless servers)
* Game starts immediately and loads a save given as a parameter to the command
* The server has no character in game
* Game is paused while there are no players connected (though this can be overridden using the no-auto-pause option in the server-settings.json)
* Saves the game on exit (and autosaves normally)

''0.13 onwards expects --start-server to be followed by a path to a save file.''

You will need to create your save file before you start the server, as the dedicated server REQUIRES a save file to be provided. This can easily be done using the --create command-line argument. For example:

<pre>
./bin/x64/factorio --create ./saves/my-save.zip # This creates a new save, as if by clicking the New Game button in the GUI
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/my-save.zip # This starts a server that will host the file created on the previous line
</pre>

There are several JSON configuration files that factorio can make use of to change the server and map settings:
* '''map-gen-settings''' to set parameters used by the map generator such as width and height, ore patch frequency and size, etc. (Added in 0.13)
* '''map-settings''' to control pollution spread, biter expansion and evolution, and more (Added in 0.15)
* '''server-settings''' which consolidated several command-line options into a single file (Added in 0.14.12)
Example files for each of these parameters are included in the data subdirectory.

The --map-gen-settings and --map-settings options must be used with the --create option when you create a new map. For example:
<pre>./bin/x64/factorio --create saves/my-save.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Starting the factorio server requires you to specify the location of the server-settings.json file. By default this is in the factorio data folder. For example to start factorio using the most recent saved map, you would run:

<pre>./bin/x64/factorio --start-server-load-latest --server-settings ./data/server-settings.json</pre>

To start a server and a client on the same computer you need to launch the client with the following launch option:
<pre>--no-log-rotation</pre>

=== Setting up a Linux Factorio server ===

'''Note:''' Factorio now requires <tt>glibc</tt> version 2.18, but CentOS/RHEL 7 only ship with version 2.17 so this guide will no longer work without [https://forums.factorio.com/viewtopic.php?t=54654#p324493 manually compiling <tt>glibc</tt> 2.18].

This step-by-step guide has been verified on fresh CentOS 7 and RHEL 7 installs but should be applicable with little to no changes on most distributions.

The guide assumes you will install the headless server under '''/opt/factorio''', adjust paths according to your own setup. We will also suggest that you run the Factorio server as a separate user to harden security of your setup.

Note that there are two distinct packages for Linux that can be used to run a headless server. First is the usual Linux download, that contains the full game. The other is the special [https://www.factorio.com/download-headless/stable headless package]. The headless package does not contain any files irrelevant for a pure server, such as graphics and sounds. It is also not linked against libraries that may not be present on a server machine, such as Xlib, libGL or libasound. This option should be selected if running in a 3rd party hosted server.

This guide does not handle firewall/port forwarding since this can be done in various ways on Linux (make sure to read up how this is done as a Linux admin on your particular distribution)

You can use the [https://github.com/Bisa/factorio-init Linux factorio-init script] to start/stop your headless server in a much better way. The script will ensure you only ever use the most recent save when your server starts (even if that was an auto-save) while also letting you set a number of other settings like Autosave frequency and Latency settings. This script will also simplify updating the server when combined with the [https://github.com/narc0tiq/factorio-updater Linux factorio-updater script].

* Download the selected package -- either full game or the headless package -- and upload the Linux tar.gz or tar.xz package to your server /tmp
* Extract the package in /tmp to /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # Use the correct file name. It includes the factorio version number
$sudo tar -xJf /tmp/factorio.tar.xz # if you downloaded a .tar.xz file (ver 0.15.x)</pre>

* Add a new user to your system and assign ownership of the factorio dir to it (please, do not run as the root user, sudo may be needed)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Try the binary
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

As long as it fails saying it cannot find/open the savename.zip you are set! Just upload a save from your own computer and put it in the /opt/factorio/saves directory, or use the --create ./saves/newgame.zip argument.

=== How to list a server-hosted game on the matching server ===

In order to publish the game to the matching server, Factorio needs to be given some more information than just the save file location. These information are provided in a ''server settings file''.

To create a server settings file, look at the example file located in '''data/server-settings.example.json''' in the Factorio [[Application directory]]. The recommended way is to make a copy of this example file and edit the copy.

The following values can be changed:
; Name: This will be the name under which the server will be listed in the server browser
; Description: A brief description of your server
; Tags: A list of game tags
; Max Players: Allows you to limit the number of players that can be connected to the server at the same time. If you want no limit, just set max_players to 0.
* Visibility for server browser: May be either public, LAN or hidden.
** Public: The server will appear in the public server list. This requires the login credentials below to be filled in.
** LAN: The server will not appear in the public server list, but will be available through the Play On LAN button
** Hidden: Clients will have to connect using the server's IP address
* User credentials using a username and password or authentication token (found on the factorio website or in the player-data.json): These are necessary if you wish to make the server public. Otherwise, they can be left empty.
** For security reasons it is recommended to use authentication token as this document is stored as plain text. Though it should be noted that an authentication token is a sensitive piece of information as well, and you are well-advised to keep it secret.
* Server Password
** Field name is game_password
* Whether to verify user identity
(There are additional values in v0.14 of factorio.)

=== Technical Implementation Details ===

Notes about some technical details surrounding multiplayer have been published by the development team in several Friday Facts blog posts:

* [http://www.factorio.com/blog/post/fff-76 Lock step architecture]
* [http://www.factorio.com/blog/post/fff-99 Client-server connections]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introduced in 0.13]

=== More Guides ===

* [https://www.chef.io/blog/2016/03/21/building-a-factorio-multiplayer-server-on-digital-ocean/ How to set up Factorio server with cookbook]
* [http://youtube.com/watch?v=MqsqRWNsbPM How To set up a Factorio Multiplayer Server | Guide | Tutorial], by Teaspoon
* [https://forums.factorio.com/viewtopic.php?f=53&t=6720 Tips to connect in multiplayer], by Nondre

=== Miscellaneous Tips ===
* The key for [[Console|Console commands]] is also used initiate chat in multiplayer. To execute a command instead of chatting, you need to type ''/c'' before the command. Commands executed are ''visible to all players''. Additionally, the multiplayer game must have been started with commands allowable for commands to work.
* Set the player's color using the command
/c game.players["player_name"].color = {r=0.7, g=0.5, b=0.1, a=0.9}
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use the right-most column on http://prideout.net/archive/colors.php to convert colors to rgb numbers). a is alpha channel aka transparency of the color to the base texture.

== Joining a Multiplayer game ==

As of version 0.13, players no longer necessarily have to port-forward to play with others. Players may join each other through Steam, or by just the port-forwarded host.

Players wishing to join a game may do so in multiple ways:

* Joining by directly inputting a public IP and port into Factorio.
* Selecting the server from the active public server menu.
* Joining through Steam's services.
* Playing a local LAN game.

It is recommended that players use voice chat (TeamSpeak, Discord, Mumble) because you need to talk a lot to coordinate connections, building, handling attacks, etc. TeamSpeak servers are posted in the [https://forums.factorio.com/viewforum.php?f=53 multiplayer forum]. The public Discord of the Factorio community can be found [https://discord.gg/yGQWgy5 here].

=== Joining by IP ===

To join a multiplayer game by IP, you will need to know the public IP of a valid server. You can find this through social media, websites, or by word of mouth. After acquiring the IP and port, simply go to play -> Multiplayer -> Connect to server, and provide all the information it asks for.

If the server has been set up correctly to accept public connections, you should be able to join the game.

=== Joining via server list ===

Factorio's devs keep a list of all public servers that declare themselves to the service, allowing players to join directly through Factorio. Most of these servers will be password-requiring, but many completely public servers can be connected to. To join via server list, go to Play -> Multiplayer -> Browse public games. Provide your Factorio.com login if asked, and a list of public servers will appear. Simply select one.

=== Joining through Steam ===

Steam provides a "game invite" system, simply use that to join. You can find more info about how to use steam in it's documentation. ''This is the most recommended way for the average player to use multiplayer with their friends, as it allows Steam to handle everything''.

=== Joining a local LAN game ===

If you have some friends on the same internet connection as you (in the same building or network), you may play a LAN game. Simply go to Play -> Multiplayer -> Play on LAN.

=== Finding Other Players ===

* Use the [https://forums.factorio.com/viewforum.php?f=53 multiplayer board in the forum].
* Many players use other software like Evolve to meet other players. This also has the "advantage" of creating a virtual LAN among the players. See down under software.
* Some also use [https://forums.factorio.com/viewtopic.php?f=5&t=9136 Steam] to find other players.
* There is an external [http://serverlist.lgms.nl/ server browser] with various search options.
* Tell your friends to buy Factorio, then play with them!

=== Connecting to a Server Behind NAT ===

Factorio requires that the server (in client-server mode) have a publicly accessible IP address or that all players are on the same LAN. If you are behind NAT, you must set up port forwarding ([[Multiplayer#Playing_over_LAN_.2F_Internet|see above]] for port number) or use virtual LAN software such as Hamachi or Evolve.

Multiplayer games will be launched in client-server mode (also [http://www.factorio.com/blog/post/fff-99 multiplayer forwarding] mode). In this mode, all clients send their network traffic to the server and the server forwards the traffic to the other clients. The advantage of this is that it allows games where some players are inside a LAN and others are outside. The disadvantage may be slightly more lag as packets must travel an extra hop (through the server).

* [https://forums.factorio.com/viewtopic.php?f=53&t=6393 Forwarding ports without logging into your router]
* [https://forums.factorio.com/viewtopic.php?f=53&t=7714 A guide for connecting with Evolve]
* [http://steamcommunity.com/sharedfiles/filedetails/?id=653628496 A guide for connecting with Hamachi]

== Multiplayer Admin Features ==
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.

Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands) that they can use. Others are invoked through the Permissions GUI (link needed)
=== Admin Console Commands ===
stub
=== Player Groups and Permissions ===
stub

== PvP ==

In PvP mode, players can be on different forces. Each force can have one (free-for-all) or more players (teams). Each force has its own independent research progression. Additionally, each force's [[Turret|turrets]] and [[Combat Robot Capsules|combat bots]] will attack other players as enemies, unless a cease fire is set. Note that, depending on the scenario, cease fires may be unidirectional — setting a cease fire with an opposing force does not guarantee a cease fire from them in return.

To start a PvP game, you can select the 'PvP' scenario from the 'Play' menu, or download a custom scenario which also supports PvP.

After downloading a PvP scenario, you need to move it to your application directory, and create the multiplayer game using the scenario.

# Download the scenario and place the scenario directory in the ''scenarios'' directory within your [[Application_directory#Directory_locations_by_OS_and_installation_method|user data directory]].
# Launch Factorio
# Click ''Play''
# Click ''Multiplayer''
# Click ''Scenario''
# Choose the PvP scenario you want and click ''Create''
# Choose latency and other settings, then click ''Play''
# Other players can now join the game

=== Forces ===

Forces can be manually created via the console. This allows any map/scenario to be used for PvP. This may not be as convenient as a pre-made PvP scenario, as there will be no way for players to turn on/off cease fires other than through the console.

Each created force has its own research progression and different forces may attack each other.

The console commands for setting up and controlling forces are below:

<pre>
game.create_force("Name")
--Creates the force "Name"

game.players["Player_name"].force = game.forces["Name"]
--Sets this player to the new force

game.forces["Name"].set_cease_fire("Other_force_name", true)
--Sets the new force ceasefire to the "other force"

game.forces["Name"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Sets the spawn position of the force

game.print(#game.forces)
--Prints the number of forces

for name, force in pairs (game.forces) do
game.print(name)
end
--Prints the name of all the forces
</pre>

The ability of players and entities belonging to one force to interact with structures belonging to another, non-friendly force is limited. However, some types of interactions are still possible:

;Manual pickup from belts
: Players can pick up items traveling along a transport belt that belongs to an opposing force. Note however that this can't be automated: Inserters will ''not'' take items from an opposing force's belts.
;Belt network connection
: Belts will connect to each other regardless of force membership, so it's possible to extend an opposing force's belt line, and items will flow to them. It is also possible to side-load into, and place items onto (with inserters) an opposing force's belt line.
;Fluid network connection
: Pipes (and storage tanks, and pumps, &c) will connect to each other regardless of force membership. For example, it's possible to pump fluids out of or into a storage tank belonging to an opposing force.
;Cable and wire connection
: Players can freely connect and disconnect [[Copper_cable|Copper cable]]s and [[Green_wire|Red/Green wire]]s from any entity that supports them, regardless of force membership. Electricity does not belong to a specific force, and it's possible to power structures with electricity from an opposing force's generators. Similarly, it's possible to read and write signals into a [[Circuit_network|Circuit network]] consisting mostly of an opposing force's devices.

== History ==

=== Narrative history ===

Because of the potentially immense amount of activity on a map, the game engine utilizes a [https://www.factorio.com/blog/post/fff-76 lock step architecture]. All instances of the game run full simulations of the entire world and only player actions are transferred across the network.

Multiplayer games were introduced to Factorio with version 0.11.0. The only connection method available was peer-to-peer mode which meant every player had to be able to directly communicate with every other player. In version 0.12.4, a client-server mode of communication was introduced in which the server (either a dedicated one or the player who hosted the game) relays messages to all peers. This means that direct connection between all players is no longer necessary. As of version 0.13, P2P connecting is completely removed.

As of version 0.12.0, the game features "latency hiding" mechanics where the game simulates some of the player's actions locally to make some common interactions (such as moving the player's character) more fluid. Latency hiding is enabled by default, but it can be enabled or disabled in Options → Other → Enable multiplayer latency hiding. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it. It is recommended to keep this on, as many actions will be very stuttery on a low end internet connection.

=== Version history ===

Maintainer note: The following history may not be fully up to date, or comprehensive. Factorio's multiplayer has undergone a great deal of small changes since its inception, however this history will provide a rough overview.

{{history|0.14.14|
* Added multiplayer server option "Autosave only on server".
* Deconstructing/canceling deconstruction sets the "last user" on an entity.
* Decreased the size of connection accept message with lot of mod which could help some people with 50+ mod multiplayer games.
}}

{{history|0.14.13|
* Reconnecting to multiplayer game that the player is already in (due to being dropped, most often) instantly closes the previous connection and connects the player.}}

{{history|0.14.11|
* Multiplayer user names can only consist of letters, and <code> -_. </code> characters.}}

{{history|0.14.10|
* Disabled 32bit (x86) multiplayer. All hosts and members must be running the 64bit (x86_64) version of the game.}}

{{history|0.14.8|
* More than 10 players in one game will reduce the rate the game is saved to the server.}}

{{history|0.14.6|
* Username is now set to username setting, not email.}}

{{history|0.14.5|
* Added AFK Auto kick interval to multiplayer host settings (with never as default).}}

{{history|0.14.3|
* When save of scenario is loaded in multiplayer, it's scenario is saved in user scenarios.
* Added <code>/time</code> command to print the current map age.
* Added option to host multiplayer game with scenario (it only had new game/load game there).
}}

{{history|0.14.2|
* Can specify limit of upload speed when hosting.}}

{{history|0.14.0|
* Server doesn't stop/slow down the game when some client is too slow, stops communicating or saves the game longer than the server.
* Players automatically quit game after 3 desyncs.
* Removed the option to enable/disable latency hiding, it is always on on clients (and off on the server).
}}

{{history|0.13.10|
* Server stdout messages now contain time stamps and message-type tags}}

{{history|0.13.2|
* Limit multiplayer player name to 60 characters.}}

{{history|0.13.0|
* Improved Multiplayer game UX
* Server games are published to the server and clients can browse existing games.
* Removed multiplayer peer-to-peer mode.
* Building sound is played also for other players in multiplayer.
}}

{{history|0.12.31|
* Human readable error notice when multiplayer connection wasn't successful. (https://forums.factorio.com/23132)
* Improved map download speed when connecting to multiplayer game.}}

{{history|0.12.30|
* Mod checksums are calculated when the game starts and are compared with other peers when joining a multiplayer game. This is to ensure everyone has exactly the same mod in order to prevent desyncs caused by local changes made to mod files.}}

{{history|0.12.28|
* Added --port to specify which network port the game should use, when hosting with --start-server or --mp-load-game.}}

{{history|0.12.27|
* The report of different mods when trying to connect to multiplayer game is now scroll-able when needed.
* Better message when the server leaves a multiplayer game}}

{{history|0.12.11|
* Added --no-auto-pause: When running as a server, --no-auto-pause will prevent stopping the game when no players are connected.}}

{{history|0.12.9|
* Added resume button to multiplayer game menu}}

{{history|0.12.7|
*New command line options for the headless server: --disallow-commands and --peer-to-peer}}

{{history|0.12.5|
* Multiplayer broadcast (heartbeats) is done via a single message when not using peer2peer.
* Further optimizations in size of the Multiplayer heartbeat (message sent every tick).
* LatencyState is suspended when player is killed (and waiting for respawn) in Multiplayer.
}}

{{history|0.12.4|
* Simple mechanism for multiplayer relaying via the server.
* Less annoying glitches when running and shooting in multiplayer with latency hiding.}}

{{history|0.12.0|
* Multiplayer latency hiding (gives impression that some common tasks are performed immediately)
* Factorio can run as a dedicated server without graphics (http://www.factorioforums.com/wiki/index.php?title=Multiplayer#Headless_server).
* Basic PvP: New forces can now be created and merged back together; a cease-fire can be agreed upon between forces
* IPv6 support for multiplayer.
* DNS names can be used when connecting to multiplayer game.
* Player's logistic filters are now remembered after respawn in multiplayer
* Smaller multiplayer heartbeat packet size.
}}

{{history|0.11.19|
* Multiplayer dropping threshold is doubled during map upload / download.}}

{{history|0.11.17|
* Autosaves in multiplayer are performed at the same time by all clients (interval is set by hosting player).
* Progress bar is shown when non-responsive peers are about to be dropped from the game in the Multiplayer.
* Progress bar is shown when other peers in multiplayer are saving map.}}

{{history|0.11.16|
* Revived character (after dying in multiplayer) are placed on the spawn point instead of the center of the map.}}

{{history|0.11.2|
* Mods that don't affect game state are not needed to be synchronized when playing multiplayer game or replaying game.}}

{{history|0.11.0|
* Introduced}}