Official Factorio Wiki - User contributions [en]

Factorio:About/es

2023-12-30T14:38:45Z

LagExpress: /* See also */ ops xd

{{Languages}}{{Translation verification|revisionID=194184}}

<onlyinclude>Factorio es un juego en el cual construyes y mantienes fábricas. Tendrás que extraer recursos, investigar tecnologías, construir infraestructura, automatizar la producción y luchar contra enemigos.

Comenzarás cortando arboles y extrayendo minerales, construyendo cintas transportadoras y brazos mecánicos a mano, pero en poco tiempo tu fábrica puede llegar a convertirse en una megaindustria, con gigantes plantas solares, refinando y craqueando petróleo, produciendo y desplegando ejércitos de robots logísticos y de construcción, todo esto para satisfacer tus necesidades de recursos. Sin embargo, esta dura explotación del los recursos del planeta no les va a sentar nada bien a los nativos locales, por lo que deberás estar preparado para defender tu vida y tu imperio mecánico.

Une fuerzas con otros jugadores en el modo cooperativo [[Multiplayer/es|Multijugador]], crea enormes fábricas, colabora y delega tareas entre tú y tus amigos. <includeonly>'''[[Factorio:About/es|... leer más ...]]'''</includeonly></onlyinclude>

Añade mods para divertirte más, desde pequeños mods que cambian pequeñas cosas, hasta algunos que cambian completamente la dinámica del juego. Factorio proporciona un completo Soporte Mod que ha permitido a los creadores de contenido de todo el mundo, crear interesantes diseños e innovadoras características nuevas. Mientras que el corazón de la jugabilidad se encuentra en el modo libre, existen una serie de interesantes desafíos en forma de Packs de escenario, desponibles como DLC gratuito. Si no te acaba de convencer ningún mapa, puedes crear el tuyo propio en el juego mediante el Editor de Mapas; coloca entidades, enemigos e incluso terreno de cualquier forma que puedas imaginar a tu antojo, e incluso añade tu propio Script para hacer más interesante la jugabilidad.

__TOC__

== Hoja de ruta ==
La [[Roadmap|Hoja de ruta]] es una descripción de los objetivos futuros para el desarrollo de Factorio. Se puede consultar para descubrir lo que los desarrolladores de Factorio tienen reservado para el juego.

Echa un vistazo a [http://www.factorio.com/blog El blog oficial]; Factorio Friday Facts (FFFs) se han convertido en una característica semanal y proporcionan buena información sobre el futuro próximo del juego.

== Stats ==

* Definición: Factorio es un juego sci-fi sandbox.
* Fecha de salida al público: Mediados de 2012

== Historia ==
* 1 de abril de 2014: [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3026 Entrevista a Michal Kovarik en CanardPC]
* 29 de julio de 2013: [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1120 Entrevista con el desarrollador]
* 5 de febrero de 2013: [http://steamcommunity.com/sharedfiles/filedetails/?id=125195010 Campaña Steam Greenlight]
** Lanzado en Steam Early access el 25 de febrero de 2016. Los desarrolladores esperan un lanzamiento completo (es decir, 1.0) en verano de 2018.
** 14 de agosto de 2020: Lanzamiento de la versión 1.0.

=== ¿En qué está inspirado el juego? ===
* [[wikipedia:Dwarf Fortress|Dwarf Fortress]]
* [[wikipedia:Transport Tycoon|Transport Tycoon]]-like games, especially [[wikipedia:OpenTTD|OpenTTD]]
* [[wikipedia:Minecraft|Minecraft]] (especialmente el [https://www.curseforge.com/minecraft/mc-mods/buildcraft BuildCraft mod])
* [[wikipedia:Civilization (series)|Civilization series]]
* [[wikipedia:SpaceChem|SpaceChem]]
* [[wikipedia:Creeper_World#Creeper_World_3:_Arc_Eternal|Creeper World 3]]
* [[wikipedia:Terraria|Terraria]]
* [[wikipedia:Starbound|Starbound]]
* [http://grobots.sourceforge.net/ Grobots]
* [[wikipedia:RimWorld|RimWorld]]
* [[wikipedia:DayZ (video game)|DayZ]]
* [[wikipedia:FTL: Faster Than Light|FTL: Faster Than Light]]
* [http://unclaimedworld-game.com/ Unclaimed World]
* [https://www.coolmathgames.com/0-into-space Into Space] (se mencionó brevemente que el juego incluirá elementos de allí)
* [https://yogscast.fandom.com/wiki/Dig-N-Rig Dig-N-Rig]

== Vea también ==
* [http://www.indiegogo.com/projects/factorio Campaña de Indiegogo]
Recaudó 21.626 euros, comenzó el 31 de enero de 2013 y finalizó el 3 de marzo de 2013.
* [http://www.bay12forums.com/smf/index.php?topic=122388.0 Foro de Dwarf Fortress]
* [[wikipedia:Factorio|Página de Factorio en Wikipedia]]

{{C|Main}}

Factorio:About/es

2023-12-30T14:36:30Z

LagExpress: updated translation to match current version

{{Languages}}{{Translation verification|revisionID=194184}}

<onlyinclude>Factorio es un juego en el cual construyes y mantienes fábricas. Tendrás que extraer recursos, investigar tecnologías, construir infraestructura, automatizar la producción y luchar contra enemigos.

Comenzarás cortando arboles y extrayendo minerales, construyendo cintas transportadoras y brazos mecánicos a mano, pero en poco tiempo tu fábrica puede llegar a convertirse en una megaindustria, con gigantes plantas solares, refinando y craqueando petróleo, produciendo y desplegando ejércitos de robots logísticos y de construcción, todo esto para satisfacer tus necesidades de recursos. Sin embargo, esta dura explotación del los recursos del planeta no les va a sentar nada bien a los nativos locales, por lo que deberás estar preparado para defender tu vida y tu imperio mecánico.

Une fuerzas con otros jugadores en el modo cooperativo [[Multiplayer/es|Multijugador]], crea enormes fábricas, colabora y delega tareas entre tú y tus amigos. <includeonly>'''[[Factorio:About/es|... leer más ...]]'''</includeonly></onlyinclude>

Añade mods para divertirte más, desde pequeños mods que cambian pequeñas cosas, hasta algunos que cambian completamente la dinámica del juego. Factorio proporciona un completo Soporte Mod que ha permitido a los creadores de contenido de todo el mundo, crear interesantes diseños e innovadoras características nuevas. Mientras que el corazón de la jugabilidad se encuentra en el modo libre, existen una serie de interesantes desafíos en forma de Packs de escenario, desponibles como DLC gratuito. Si no te acaba de convencer ningún mapa, puedes crear el tuyo propio en el juego mediante el Editor de Mapas; coloca entidades, enemigos e incluso terreno de cualquier forma que puedas imaginar a tu antojo, e incluso añade tu propio Script para hacer más interesante la jugabilidad.

__TOC__

== Hoja de ruta ==
La [[Roadmap|Hoja de ruta]] es una descripción de los objetivos futuros para el desarrollo de Factorio. Se puede consultar para descubrir lo que los desarrolladores de Factorio tienen reservado para el juego.

Echa un vistazo a [http://www.factorio.com/blog El blog oficial]; Factorio Friday Facts (FFFs) se han convertido en una característica semanal y proporcionan buena información sobre el futuro próximo del juego.

== Stats ==

* Definición: Factorio es un juego sci-fi sandbox.
* Fecha de salida al público: Mediados de 2012

== Historia ==
* 1 de abril de 2014: [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3026 Entrevista a Michal Kovarik en CanardPC]
* 29 de julio de 2013: [http://www.factorioforums.com/forum/viewtopic.php?f=5&t=1120 Entrevista con el desarrollador]
* 5 de febrero de 2013: [http://steamcommunity.com/sharedfiles/filedetails/?id=125195010 Campaña Steam Greenlight]
** Lanzado en Steam Early access el 25 de febrero de 2016. Los desarrolladores esperan un lanzamiento completo (es decir, 1.0) en verano de 2018.
** 14 de agosto de 2020: Lanzamiento de la versión 1.0.

=== ¿En qué está inspirado el juego? ===
* [[wikipedia:Dwarf Fortress|Dwarf Fortress]]
* [[wikipedia:Transport Tycoon|Transport Tycoon]]-like games, especially [[wikipedia:OpenTTD|OpenTTD]]
* [[wikipedia:Minecraft|Minecraft]] (especialmente el [https://www.curseforge.com/minecraft/mc-mods/buildcraft BuildCraft mod])
* [[wikipedia:Civilization (series)|Civilization series]]
* [[wikipedia:SpaceChem|SpaceChem]]
* [[wikipedia:Creeper_World#Creeper_World_3:_Arc_Eternal|Creeper World 3]]
* [[wikipedia:Terraria|Terraria]]
* [[wikipedia:Starbound|Starbound]]
* [http://grobots.sourceforge.net/ Grobots]
* [[wikipedia:RimWorld|RimWorld]]
* [[wikipedia:DayZ (video game)|DayZ]]
* [[wikipedia:FTL: Faster Than Light|FTL: Faster Than Light]]
* [http://unclaimedworld-game.com/ Unclaimed World]
* [https://www.coolmathgames.com/0-into-space Into Space] (se mencionó brevemente que el juego incluirá elementos de allí)
* [https://yogscast.fandom.com/wiki/Dig-N-Rig Dig-N-Rig]

== See also ==
* [http://www.indiegogo.com/projects/factorio Campaña de Indiegogo]
Recaudó 21.626 euros, comenzó el 31 de enero de 2013 y finalizó el 3 de marzo de 2013.
* [http://www.bay12forums.com/smf/index.php?topic=122388.0 Foro de Dwarf Fortress]
* [[wikipedia:Factorio|Página de Factorio en Wikipedia]]

{{C|Main}}

Multiplayer/es

2023-12-30T13:48:53Z

LagExpress: fully translated page

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
*'''Alojar una partida guardada''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
*'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
*'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
*'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas públicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas fácil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así:
<code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

== Unirse a una partida multijugador ==

A partir de la versión 0.13, los jugadores ya no necesariamente tienen que hacer un reenvío de puertos para jugar con otros. Los jugadores pueden unirse entre sí a través de Steam, o simplemente por el host con reenvío de puerto.

Los jugadores que deseen unirse a una partida pueden hacerlo de varias maneras:

* Unirse ingresando directamente una IP pública y puerto en Factorio.
* Seleccionando el servidor desde la lista de partidas públicas.
* Unirse a través de los servicios de Steam.
* Jugando desde una partida local en LAN.

=== Unirse por IP ===

Para unirse a una partida multijugador por IP, necesitarás conocer la IP pública de un servidor válido. Puedes encontrar esto a través de las redes sociales, sitios web, o de boca en boca. Después de adquirir la IP y el puerto, simplemente ve a Multijugador -> Conectar con dirección, y proporciona toda la información que te pide.

Si el servidor ha sido configurado correctamente para aceptar conexiones públicas, deberías poder unirte a la partida.

=== Unirse a través de la lista de partidas publicas ===

Los desarrolladores de Factorio mantienen una lista de todos los servidores públicos que se declaran al servicio, permitiendo a los jugadores unirse directamente a través de Factorio. La mayoría de estos servidores requerirán contraseña, pero te puedes unir muchos servidores que son completamente públicos. Para unirse a través de la lista de partidas públicas, ve a Multijugador -> Buscar partidas públicas. Proporciona tu inicio de sesión de Factorio.com si es solicitado, y aparecerá una lista de servidores públicos. Simplemente selecciona uno.

=== Unirse a través de Steam ===

Steam proporciona un sistema de "invitación a juego", simplemente usa eso para unirte. Puedes encontrar más información sobre cómo usar Steam en su documentación. ''Esta es la forma más recomendada para que el jugador promedio use el multijugador con sus amigos, ya que permite que Steam se encargue de todo''.

=== Unirse a una partida local en LAN ===

Si tienes algunos amigos en la misma conexión a Internet que tú (en el mismo edificio o red), puedes jugar una partida en LAN. Simplemente ve a Jugar -> Multijugador -> Buscar partidas LAN.

=== Conectarse a un servidor detrás de una NAT ===

Factorio requiere que el servidor (en modo cliente-servidor) tenga una dirección IP accesible al público o que todos los jugadores estén en la misma LAN. Si estás detrás de NAT, debes configurar el reenvío de puertos o usar software de LAN virtual como Hamachi o Radmin.

Las partidas multijugador se lanzarán en modo cliente-servidor (también [modo de reenvío multijugador](http://www.factorio.com/blog/post/fff-99)). En este modo, todos los clientes envían su tráfico de red al servidor y el servidor reenvía el tráfico a los otros clientes. La ventaja de esto es que permite partidas donde algunos jugadores están dentro de una LAN y otros están fuera. La desventaja puede ser un poco más de retraso ya que los paquetes deben viajar un salto extra (a través del servidor).

* [Reenvío de puertos sin iniciar sesión en tu router](https://forums.factorio.com/viewtopic.php?f=53&t=6393)
* [Una guía para conectarse con Hamachi](http://steamcommunity.com/sharedfiles/filedetails/?id=653628496)

== PvP ==

En el modo PvP, los jugadores pueden estar en diferentes fuerzas. Cada fuerza puede tener un jugador (todos contra todos) o varios jugadores (equipos). Cada fuerza tiene su propia progresión de investigación independiente. Además, las [[Military units and structures/es|Unidades y estructuras militares]] de cada fuerza atacarán a otros jugadores como enemigos, a menos que se establezca un alto el fuego. Ten en cuenta que, dependiendo del escenario, los altos el fuego pueden ser unidireccionales: establecer un alto el fuego con una fuerza opuesta no garantiza un alto el fuego de ellos a cambio.

Para iniciar una partida PvP, puedes seleccionar el escenario 'PvP' desde el menú 'Jugar', o descargar un escenario personalizado que también admita PvP.

Después de descargar un escenario PvP, debes moverlo al directorio de la aplicación, y crear la partida multijugador usando el escenario.

# Descarga el escenario y coloca el directorio del escenario en el directorio ''scenarios'' dentro de tu [[Application_directory#Directory_locations_by_OS_and_installation_method|directorio de datos de usuario]].
# Ejecuta Factorio
# Click ''Multijugador''
# Selecciona el ''Escenario''
# Elige el escenario PvP que quieras y haz clic en ''Crear''
# Elige la latencia y otras opciones, luego haz clic en ''Jugar''
# Ahora los otros jugadores pueden unirse a la partida

=== Fuerzas ===

Las fuerzas se pueden crear manualmente a través de la consola. Esto permite que cualquier mapa/escenario se pueda usar para PvP. Esto puede no ser tan conveniente como un escenario PvP pre-hecho, ya que no habrá forma de activar/desactivar los altos al fuego más que a través de la consola.

Cada fuerza creada tiene su propia progresión de investigación y diferentes fuerzas pueden atacarse entre sí.

Los comandos de la consola para configurar y controlar las fuerzas son los siguientes:

<pre>
game.create_force("Nombre")
--Crea la fuerza "Nombre"

game.players["Nombre_del_jugador"].force = game.forces["Nombre"]
--Establece que este jugador pertenece a la fuerza "Nombre"

game.forces["Nombre"].set_cease_fire("Nombre_de_otra_fuerza", true)
--Sets the new force ceasefire to the "other force"
--Establece el alto al fuego hacia la fuerza "Nombre_de_otra_fuerza"

game.forces["Nombre"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Establece la posición de aparición de la fuerza

game.print(#game.forces)
--Imprime el número de fuerzas

for name, force in pairs (game.forces) do
game.print(name)
end
--Imprime el nombre de todas las fuerzas
</pre>

La capacidad de interactuar de los jugadores y las entidades pertenecientes a una fuerza con las estructuras pertenecientes a otra fuerza no amigable es limitada. Sin embargo, algunos tipos de interacciones aún son posibles:

;Recogida manual de las cintas
: Los jugadores pueden recoger objetos que viajen por una cinta de transporte que pertenezca a una fuerza contraria. Tenga en cuenta, sin embargo, que esto no se puede automatizar: Los insertadores ''no'' levantaran objetos de las cintas de una fuerza contraria.
;Conexión a la red de cintas
: Las cintas se conectarán entre sí independientemente de la fuerza a la que pertenezcan, por lo que es posible extender la línea de cintas de una fuerza contraria, y los objetos fluirán hacia ellos. También es posible cargar lateralmente y colocar objetos (con insertadores) en la línea de cintas de una fuerza contraria.
;Conexion a la red de fluidos
: Las tuberías (y los tanques de almacenamiento, las bombas, &c) se conectarán entre sí independientemente de la fuerza a la que pertenezcas. Por ejemplo, es posible bombear fluidos desde o hacia un tanque de almacenamiento perteneciente a una fuerza opuesta.
;Robar energía
: Los jugadores pueden extraer energía de la red eléctrica de una fuerza contraria, construyendo estructuras dentro del área de cobertura de un poste de energía perteneciente a una fuerza contraria. Los postes eléctricos que construyas junto a un poste eléctrico perteneciente a una fuerza contraria se conectarán automáticamente a él, pero será imposible conectarlos o desconectarlos manualmente.

== Historia ==

=== Historia narrativa ===

Debido a la cantidad potencialmente inmensa de actividad en un mapa, el motor del juego utiliza una [https://www.factorio.com/blog/post/fff-76 arquitectura lock step]. Todas las instancias del juego ejecutan simulaciones completas de todo el mundo y sólo las acciones de los jugadores se transfieren a través de la red.

Las partidas multijugador se introdujeron en Factorio con la versión 0.11.0. El único método de conexión disponible era el modo peer-to-peer, lo que significaba que cada jugador tenía que ser capaz de comunicarse directamente los demás jugadores. En la versión 0.12.4, se introdujo un modo de comunicación cliente-servidor en el que el servidor (ya sea uno dedicado o el jugador que albergaba el juego) retransmite mensajes a todos los compañeros. Esto significa que ya no es necesaria la conexión directa entre todos los jugadores. A partir de la versión 0.13, la conexión P2P desaparece por completo.

A partir de la versión 0.12.0, el juego incorpora la mecánica de "ocultación de latencia", que simula localmente algunas de las acciones del jugador para hacer más fluidas algunas interacciones habituales (como mover el personaje del jugador). No todas las acciones forman parte de la ocultación de latencia, sobre todo la conducción de coches o trenes y los disparos.

=== Historial de versiones ===

Nota del mantenedor: El siguiente historial puede no estar totalmente actualizado o no ser exhaustivo. El multijugador de Factorio ha sufrido una gran cantidad de pequeños cambios desde su creación, sin embargo este historial proporcionará una visión general.

{{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.
* 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}}

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T13:46:24Z

LagExpress:

User:LagExpress/Multiplayer/es

2023-12-30T13:42:14Z

LagExpress: /* History */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
*'''Alojar una partida guardada''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
*'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
*'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
*'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así:
<code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

== Unirse a una partida multijugador ==

A partir de la versión 0.13, los jugadores ya no necesariamente tienen que hacer un reenvío de puertos para jugar con otros. Los jugadores pueden unirse entre sí a través de Steam, o simplemente por el host con reenvío de puerto.

Los jugadores que deseen unirse a una partida pueden hacerlo de varias maneras:

* Unirse ingresando directamente una IP pública y puerto en Factorio.
* Seleccionando el servidor desde la lista de partidas publicas.
* Unirse a través de los servicios de Steam.
* Jugando desde una partida local en LAN.

=== Unirse por IP ===

Para unirse a una partida multijugador por IP, necesitarás conocer la IP pública de un servidor válido. Puedes encontrar esto a través de las redes sociales, sitios web, o de boca en boca. Después de adquirir la IP y el puerto, simplemente ve a Multijugador -> Conectar con dirección, y proporciona toda la información que te pide.

Si el servidor ha sido configurado correctamente para aceptar conexiones públicas, deberías poder unirte a la partida.

=== Unirse a través de la lista de partidas publicas ===

Los desarrolladores de Factorio mantienen una lista de todos los servidores públicos que se declaran al servicio, permitiendo a los jugadores unirse directamente a través de Factorio. La mayoría de estos servidores requerirán contraseña, pero te puedes unir muchos servidores que son completamente públicos. Para unirse a través de la lista de partidas publicas, ve a Multijugador -> Buscar partidas públicas. Proporciona tu inicio de sesión de Factorio.com si es solicitado, y aparecerá una lista de servidores públicos. Simplemente selecciona uno.

=== Unirse a través de Steam ===

Steam proporciona un sistema de "invitación a juego", simplemente usa eso para unirte. Puedes encontrar más información sobre cómo usar Steam en su documentación. ''Esta es la forma más recomendada para que el jugador promedio use el multijugador con sus amigos, ya que permite que Steam se encague de todo''.

=== Unirse a una partida local en LAN ===

Si tienes algunos amigos en la misma conexión a Internet que tú (en el mismo edificio o red), puedes jugar una partida en LAN. Simplemente ve a Jugar -> Multijugador -> Buscar partidas LAN.

=== Conectarse a un servidor detrás de una NAT ===

Factorio requiere que el servidor (en modo cliente-servidor) tenga una dirección IP accesible al público o que todos los jugadores estén en la misma LAN. Si estás detrás de NAT, debes configurar el reenvío de puertos o usar software de LAN virtual como Hamachi o Radmin.

Las partidas multijugador se lanzarán en modo cliente-servidor (también [modo de reenvío multijugador](http://www.factorio.com/blog/post/fff-99)). En este modo, todos los clientes envían su tráfico de red al servidor y el servidor reenvía el tráfico a los otros clientes. La ventaja de esto es que permite partidas donde algunos jugadores están dentro de una LAN y otros están fuera. La desventaja puede ser un poco más de retraso ya que los paquetes deben viajar un salto extra (a través del servidor).

* [Reenvío de puertos sin iniciar sesión en tu router](https://forums.factorio.com/viewtopic.php?f=53&t=6393)
* [Una guía para conectarse con Hamachi](http://steamcommunity.com/sharedfiles/filedetails/?id=653628496)

== 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 [[Military units and structures]] 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

== PvP ==

En el modo PvP, los jugadores pueden estar en diferentes fuerzas. Cada fuerza puede tener un jugador (todos contra todos) o varios jugadores (equipos). Cada fuerza tiene su propia progresión de investigación independiente. Además, las [[Military units and structures/es|Unidades y estructuras militares]] de cada fuerza atacarán a otros jugadores como enemigos, a menos que se establezca un alto el fuego. Ten en cuenta que, dependiendo del escenario, los altos el fuego pueden ser unidireccionales: establecer un alto el fuego con una fuerza opuesta no garantiza un alto el fuego de ellos a cambio.

Para iniciar una partida PvP, puedes seleccionar el escenario 'PvP' desde el menú 'Jugar', o descargar un escenario personalizado que también admita PvP.

Después de descargar un escenario PvP, debes moverlo al directorio de la aplicación, y crear la partida multijugador usando el escenario.

# Descarga el escenario y coloca el directorio del escenario en el directorio ''scenarios'' dentro de tu [[Application_directory#Directory_locations_by_OS_and_installation_method|directorio de datos de usuario]].
# Ejecuta Factorio
# Click ''Multijugador''
# Selecciona el ''Escenario''
# Elige el escenario PvP que quieras y haz clic en ''Crear''
# Elige la latencia y otras opciones, luego haz clic en ''Jugar''
# Ahora los otros jugadores pueden unirse a la partida

=== Fuerzas ===

Las fuerzas se pueden crear manualmente a través de la consola. Esto permite que cualquier mapa/escenario se pueda usar para PvP. Esto puede no ser tan conveniente como un escenario PvP pre-hecho, ya que no habrá forma de activar/desactivar los altos al fuego más que a través de la consola.

Cada fuerza creada tiene su propia progresión de investigación y diferentes fuerzas pueden atacarse entre sí.

Los comandos de la consola para configurar y controlar las fuerzas son los siguientes:

<pre>
game.create_force("Nombre")
--Crea la fuerza "Nombre"

game.players["Nombre_del_jugador"].force = game.forces["Nombre"]
--Establece que este jugador pertenece a la fuerza "Nombre"

game.forces["Nombre"].set_cease_fire("Nombre_de_otra_fuerza", true)
--Sets the new force ceasefire to the "other force"
--Establece el alto al fuego hacia la fuerza "Nombre_de_otra_fuerza"

game.forces["Nombre"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Establece la posición de aparición de la fuerza

game.print(#game.forces)
--Imprime el número de fuerzas

for name, force in pairs (game.forces) do
game.print(name)
end
--Imprime el nombre de todas las fuerzas
</pre>

La capacidad de interactuar de los jugadores y las entidades pertenecientes a una fuerza con las estructuras pertenecientes a otra fuerza no amigable es limitada. Sin embargo, algunos tipos de interacciones aún son posibles:

;Recogida manual de las cintas
: Los jugadores pueden recoger objetos que viajen por una cinta de transporte que pertenezca a una fuerza contraria. Tenga en cuenta, sin embargo, que esto no se puede automatizar: Los insertadores ''no'' levantaran objetos de las cintas de una fuerza contraria.
;Conexión a la red de cintas
: Las cintas se conectarán entre sí independientemente de la fuerza a la que pertenezcan, por lo que es posible extender la línea de cintas de una fuerza contraria, y los objetos fluirán hacia ellos. También es posible cargar lateralmente y colocar objetos (con insertadores) en la línea de cintas de una fuerza contraria.
;Conexion a la red de fluidos
: Las tuberías (y los tanques de almacenamiento, las bombas, &c) se conectarán entre sí independientemente de la fuerza a la que pertenezcas. Por ejemplo, es posible bombear fluidos desde o hacia un tanque de almacenamiento perteneciente a una fuerza opuesta.
;Robar energía
: Los jugadores pueden extraer energía de la red eléctrica de una fuerza contraria, construyendo estructuras dentro del área de cobertura de un poste de energía perteneciente a una fuerza contraria. Los postes eléctricos que construyas junto a un poste eléctrico perteneciente a una fuerza contraria se conectarán automáticamente a él, pero será imposible conectarlos o desconectarlos manualmente.

== Historia ==

=== Historia narrativa ===

Debido a la cantidad potencialmente inmensa de actividad en un mapa, el motor del juego utiliza una [https://www.factorio.com/blog/post/fff-76 arquitectura lock step]. Todas las instancias del juego ejecutan simulaciones completas de todo el mundo y sólo las acciones de los jugadores se transfieren a través de la red.

Las partidas multijugador se introdujeron en Factorio con la versión 0.11.0. El único método de conexión disponible era el modo peer-to-peer, lo que significaba que cada jugador tenía que ser capaz de comunicarse directamente los demás jugadores. En la versión 0.12.4, se introdujo un modo de comunicación cliente-servidor en el que el servidor (ya sea uno dedicado o el jugador que albergaba el juego) retransmite mensajes a todos los compañeros. Esto significa que ya no es necesaria la conexión directa entre todos los jugadores. A partir de la versión 0.13, la conexión P2P desaparece por completo.

A partir de la versión 0.12.0, el juego incorpora la mecánica de "ocultación de latencia", que simula localmente algunas de las acciones del jugador para hacer más fluidas algunas interacciones habituales (como mover el personaje del jugador). No todas las acciones forman parte de la ocultación de latencia, sobre todo la conducción de coches o trenes y los disparos.

=== Historial de versiones ===

Nota del mantenedor: El siguiente historial puede no estar totalmente actualizado o no ser exhaustivo. El multijugador de Factorio ha sufrido una gran cantidad de pequeños cambios desde su creación, sin embargo este historial proporcionará una visión general.

{{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.
* 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}}

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T13:25:42Z

LagExpress: /* Forces */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
*'''Alojar una partida guardada''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
*'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
*'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
*'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así:
<code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

== Unirse a una partida multijugador ==

A partir de la versión 0.13, los jugadores ya no necesariamente tienen que hacer un reenvío de puertos para jugar con otros. Los jugadores pueden unirse entre sí a través de Steam, o simplemente por el host con reenvío de puerto.

Los jugadores que deseen unirse a una partida pueden hacerlo de varias maneras:

* Unirse ingresando directamente una IP pública y puerto en Factorio.
* Seleccionando el servidor desde la lista de partidas publicas.
* Unirse a través de los servicios de Steam.
* Jugando desde una partida local en LAN.

=== Unirse por IP ===

Para unirse a una partida multijugador por IP, necesitarás conocer la IP pública de un servidor válido. Puedes encontrar esto a través de las redes sociales, sitios web, o de boca en boca. Después de adquirir la IP y el puerto, simplemente ve a Multijugador -> Conectar con dirección, y proporciona toda la información que te pide.

Si el servidor ha sido configurado correctamente para aceptar conexiones públicas, deberías poder unirte a la partida.

=== Unirse a través de la lista de partidas publicas ===

Los desarrolladores de Factorio mantienen una lista de todos los servidores públicos que se declaran al servicio, permitiendo a los jugadores unirse directamente a través de Factorio. La mayoría de estos servidores requerirán contraseña, pero te puedes unir muchos servidores que son completamente públicos. Para unirse a través de la lista de partidas publicas, ve a Multijugador -> Buscar partidas públicas. Proporciona tu inicio de sesión de Factorio.com si es solicitado, y aparecerá una lista de servidores públicos. Simplemente selecciona uno.

=== Unirse a través de Steam ===

Steam proporciona un sistema de "invitación a juego", simplemente usa eso para unirte. Puedes encontrar más información sobre cómo usar Steam en su documentación. ''Esta es la forma más recomendada para que el jugador promedio use el multijugador con sus amigos, ya que permite que Steam se encague de todo''.

=== Unirse a una partida local en LAN ===

Si tienes algunos amigos en la misma conexión a Internet que tú (en el mismo edificio o red), puedes jugar una partida en LAN. Simplemente ve a Jugar -> Multijugador -> Buscar partidas LAN.

=== Conectarse a un servidor detrás de una NAT ===

Factorio requiere que el servidor (en modo cliente-servidor) tenga una dirección IP accesible al público o que todos los jugadores estén en la misma LAN. Si estás detrás de NAT, debes configurar el reenvío de puertos o usar software de LAN virtual como Hamachi o Radmin.

Las partidas multijugador se lanzarán en modo cliente-servidor (también [modo de reenvío multijugador](http://www.factorio.com/blog/post/fff-99)). En este modo, todos los clientes envían su tráfico de red al servidor y el servidor reenvía el tráfico a los otros clientes. La ventaja de esto es que permite partidas donde algunos jugadores están dentro de una LAN y otros están fuera. La desventaja puede ser un poco más de retraso ya que los paquetes deben viajar un salto extra (a través del servidor).

* [Reenvío de puertos sin iniciar sesión en tu router](https://forums.factorio.com/viewtopic.php?f=53&t=6393)
* [Una guía para conectarse con Hamachi](http://steamcommunity.com/sharedfiles/filedetails/?id=653628496)

== 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 [[Military units and structures]] 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

== PvP ==

En el modo PvP, los jugadores pueden estar en diferentes fuerzas. Cada fuerza puede tener un jugador (todos contra todos) o varios jugadores (equipos). Cada fuerza tiene su propia progresión de investigación independiente. Además, las [[Military units and structures/es|Unidades y estructuras militares]] de cada fuerza atacarán a otros jugadores como enemigos, a menos que se establezca un alto el fuego. Ten en cuenta que, dependiendo del escenario, los altos el fuego pueden ser unidireccionales: establecer un alto el fuego con una fuerza opuesta no garantiza un alto el fuego de ellos a cambio.

Para iniciar una partida PvP, puedes seleccionar el escenario 'PvP' desde el menú 'Jugar', o descargar un escenario personalizado que también admita PvP.

Después de descargar un escenario PvP, debes moverlo al directorio de la aplicación, y crear la partida multijugador usando el escenario.

# Descarga el escenario y coloca el directorio del escenario en el directorio ''scenarios'' dentro de tu [[Application_directory#Directory_locations_by_OS_and_installation_method|directorio de datos de usuario]].
# Ejecuta Factorio
# Click ''Multijugador''
# Selecciona el ''Escenario''
# Elige el escenario PvP que quieras y haz clic en ''Crear''
# Elige la latencia y otras opciones, luego haz clic en ''Jugar''
# Ahora los otros jugadores pueden unirse a la partida

=== Fuerzas ===

Las fuerzas se pueden crear manualmente a través de la consola. Esto permite que cualquier mapa/escenario se pueda usar para PvP. Esto puede no ser tan conveniente como un escenario PvP pre-hecho, ya que no habrá forma de activar/desactivar los altos al fuego más que a través de la consola.

Cada fuerza creada tiene su propia progresión de investigación y diferentes fuerzas pueden atacarse entre sí.

Los comandos de la consola para configurar y controlar las fuerzas son los siguientes:

<pre>
game.create_force("Nombre")
--Crea la fuerza "Nombre"

game.players["Nombre_del_jugador"].force = game.forces["Nombre"]
--Establece que este jugador pertenece a la fuerza "Nombre"

game.forces["Nombre"].set_cease_fire("Nombre_de_otra_fuerza", true)
--Sets the new force ceasefire to the "other force"
--Establece el alto al fuego hacia la fuerza "Nombre_de_otra_fuerza"

game.forces["Nombre"].set_spawn_position({x = 10, y = 20}, game.surfaces[1])
--Establece la posición de aparición de la fuerza

game.print(#game.forces)
--Imprime el número de fuerzas

for name, force in pairs (game.forces) do
game.print(name)
end
--Imprime el nombre de todas las fuerzas
</pre>

La capacidad de interactuar de los jugadores y las entidades pertenecientes a una fuerza con las estructuras pertenecientes a otra fuerza no amigable es limitada. Sin embargo, algunos tipos de interacciones aún son posibles:

;Recogida manual de las cintas
: Los jugadores pueden recoger objetos que viajen por una cinta de transporte que pertenezca a una fuerza contraria. Tenga en cuenta, sin embargo, que esto no se puede automatizar: Los insertadores ''no'' levantaran objetos de las cintas de una fuerza contraria.
;Conexión a la red de cintas
: Las cintas se conectarán entre sí independientemente de la fuerza a la que pertenezcan, por lo que es posible extender la línea de cintas de una fuerza contraria, y los objetos fluirán hacia ellos. También es posible cargar lateralmente y colocar objetos (con insertadores) en la línea de cintas de una fuerza contraria.
;Conexion a la red de fluidos
: Las tuberías (y los tanques de almacenamiento, las bombas, &c) se conectarán entre sí independientemente de la fuerza a la que pertenezcas. Por ejemplo, es posible bombear fluidos desde o hacia un tanque de almacenamiento perteneciente a una fuerza opuesta.
;Robar energía
: Los jugadores pueden extraer energía de la red eléctrica de una fuerza contraria, construyendo estructuras dentro del área de cobertura de un poste de energía perteneciente a una fuerza contraria. Los postes eléctricos que construyas junto a un poste eléctrico perteneciente a una fuerza contraria se conectarán automáticamente a él, pero será imposible conectarlos o desconectarlos manualmente.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T12:48:02Z

LagExpress: /* Consejos Varios */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
*'''Alojar una partida guardada''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
*'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
*'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
*'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así:
<code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

== Unirse a una partida multijugador ==

A partir de la versión 0.13, los jugadores ya no necesariamente tienen que hacer un reenvío de puertos para jugar con otros. Los jugadores pueden unirse entre sí a través de Steam, o simplemente por el host con reenvío de puerto.

Los jugadores que deseen unirse a una partida pueden hacerlo de varias maneras:

* Unirse ingresando directamente una IP pública y puerto en Factorio.
* Seleccionando el servidor desde la lista de partidas publicas.
* Unirse a través de los servicios de Steam.
* Jugando desde una partida local en LAN.

=== Unirse por IP ===

Para unirse a una partida multijugador por IP, necesitarás conocer la IP pública de un servidor válido. Puedes encontrar esto a través de las redes sociales, sitios web, o de boca en boca. Después de adquirir la IP y el puerto, simplemente ve a Multijugador -> Conectar con dirección, y proporciona toda la información que te pide.

Si el servidor ha sido configurado correctamente para aceptar conexiones públicas, deberías poder unirte a la partida.

=== Unirse a través de la lista de partidas publicas ===

Los desarrolladores de Factorio mantienen una lista de todos los servidores públicos que se declaran al servicio, permitiendo a los jugadores unirse directamente a través de Factorio. La mayoría de estos servidores requerirán contraseña, pero te puedes unir muchos servidores que son completamente públicos. Para unirse a través de la lista de partidas publicas, ve a Multijugador -> Buscar partidas públicas. Proporciona tu inicio de sesión de Factorio.com si es solicitado, y aparecerá una lista de servidores públicos. Simplemente selecciona uno.

=== Unirse a través de Steam ===

Steam proporciona un sistema de "invitación a juego", simplemente usa eso para unirte. Puedes encontrar más información sobre cómo usar Steam en su documentación. ''Esta es la forma más recomendada para que el jugador promedio use el multijugador con sus amigos, ya que permite que Steam se encague de todo''.

=== Unirse a una partida local en LAN ===

Si tienes algunos amigos en la misma conexión a Internet que tú (en el mismo edificio o red), puedes jugar una partida en LAN. Simplemente ve a Jugar -> Multijugador -> Buscar partidas LAN.

=== Conectarse a un servidor detrás de una NAT ===

Factorio requiere que el servidor (en modo cliente-servidor) tenga una dirección IP accesible al público o que todos los jugadores estén en la misma LAN. Si estás detrás de NAT, debes configurar el reenvío de puertos o usar software de LAN virtual como Hamachi o Radmin.

Las partidas multijugador se lanzarán en modo cliente-servidor (también [modo de reenvío multijugador](http://www.factorio.com/blog/post/fff-99)). En este modo, todos los clientes envían su tráfico de red al servidor y el servidor reenvía el tráfico a los otros clientes. La ventaja de esto es que permite partidas donde algunos jugadores están dentro de una LAN y otros están fuera. La desventaja puede ser un poco más de retraso ya que los paquetes deben viajar un salto extra (a través del servidor).

* [Reenvío de puertos sin iniciar sesión en tu router](https://forums.factorio.com/viewtopic.php?f=53&t=6393)
* [Una guía para conectarse con Hamachi](http://steamcommunity.com/sharedfiles/filedetails/?id=653628496)

== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T12:47:33Z

LagExpress: /* Joining a Multiplayer game */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
*'''Alojar una partida guardada''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
*'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
*'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
*'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así: <code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

== Unirse a una partida multijugador ==

A partir de la versión 0.13, los jugadores ya no necesariamente tienen que hacer un reenvío de puertos para jugar con otros. Los jugadores pueden unirse entre sí a través de Steam, o simplemente por el host con reenvío de puerto.

Los jugadores que deseen unirse a una partida pueden hacerlo de varias maneras:

* Unirse ingresando directamente una IP pública y puerto en Factorio.
* Seleccionando el servidor desde la lista de partidas publicas.
* Unirse a través de los servicios de Steam.
* Jugando desde una partida local en LAN.

=== Unirse por IP ===

Para unirse a una partida multijugador por IP, necesitarás conocer la IP pública de un servidor válido. Puedes encontrar esto a través de las redes sociales, sitios web, o de boca en boca. Después de adquirir la IP y el puerto, simplemente ve a Multijugador -> Conectar con dirección, y proporciona toda la información que te pide.

Si el servidor ha sido configurado correctamente para aceptar conexiones públicas, deberías poder unirte a la partida.

=== Unirse a través de la lista de partidas publicas ===

Los desarrolladores de Factorio mantienen una lista de todos los servidores públicos que se declaran al servicio, permitiendo a los jugadores unirse directamente a través de Factorio. La mayoría de estos servidores requerirán contraseña, pero te puedes unir muchos servidores que son completamente públicos. Para unirse a través de la lista de partidas publicas, ve a Multijugador -> Buscar partidas públicas. Proporciona tu inicio de sesión de Factorio.com si es solicitado, y aparecerá una lista de servidores públicos. Simplemente selecciona uno.

=== Unirse a través de Steam ===

Steam proporciona un sistema de "invitación a juego", simplemente usa eso para unirte. Puedes encontrar más información sobre cómo usar Steam en su documentación. ''Esta es la forma más recomendada para que el jugador promedio use el multijugador con sus amigos, ya que permite que Steam se encague de todo''.

=== Unirse a una partida local en LAN ===

Si tienes algunos amigos en la misma conexión a Internet que tú (en el mismo edificio o red), puedes jugar una partida en LAN. Simplemente ve a Jugar -> Multijugador -> Buscar partidas LAN.

=== Conectarse a un servidor detrás de una NAT ===

Factorio requiere que el servidor (en modo cliente-servidor) tenga una dirección IP accesible al público o que todos los jugadores estén en la misma LAN. Si estás detrás de NAT, debes configurar el reenvío de puertos o usar software de LAN virtual como Hamachi o Radmin.

Las partidas multijugador se lanzarán en modo cliente-servidor (también [modo de reenvío multijugador](http://www.factorio.com/blog/post/fff-99)). En este modo, todos los clientes envían su tráfico de red al servidor y el servidor reenvía el tráfico a los otros clientes. La ventaja de esto es que permite partidas donde algunos jugadores están dentro de una LAN y otros están fuera. La desventaja puede ser un poco más de retraso ya que los paquetes deben viajar un salto extra (a través del servidor).

* [Reenvío de puertos sin iniciar sesión en tu router](https://forums.factorio.com/viewtopic.php?f=53&t=6393)
* [Una guía para conectarse con Hamachi](http://steamcommunity.com/sharedfiles/filedetails/?id=653628496)

== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T12:33:13Z

LagExpress:

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
*'''Alojar una partida guardada''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
*'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
*'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
*'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así: <code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T12:16:10Z

LagExpress:

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así: <code>[ "usuario1", "usuario2" ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T12:14:54Z

LagExpress: /* Miscellaneous Tips */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== Consejos Varios ===
* La tecla para los [[Console/es|comandos de consola]] también se utiliza para iniciar el chat en multijugador. Para ejecutar un comando en lugar de chatear, necesitas escribir ''/c'' antes del comando. Los comandos ejecutados son ''visibles para todos los jugadores''. Además, la partida multijugador debe haberse iniciado con "permitir comandos" para que los comandos funcionen.
* Establece el color del jugador usando el comando
/color r g b
r, g y b son para rojo, verde y azul respectivamente (los valores posibles están entre 0 y 1, usa [https://www.w3schools.com/colors/colors_converter.asp este sitio] para convertir los colores a números rgb).

* Para darte acceso de administrador, necesitas crear un archivo server-adminlist.json en el mismo directorio que factorio-current.log. El archivo debe contener una lista de administradores, así: <code>[ “usuario1”, “usuario2” ]</code>

Este archivo se creará si promueves a un jugador a través de la consola.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T12:01:31Z

LagExpress: /* DNS SRV Records */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== Registros DNS SRV ===
Factorio admite [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ Registros DNS SRV] desde la versión 1.1.67.

Esto hace mas facil tener varios servidores de Factorio en un mismo host y permitir que los usuarios se conecten a ellos con subdominios distintos en lugar de tener que ingresar números de puerto.

El nombre del servicio es <code>_factorio</code> y solo admite el protocolo <code>_udp</code>.

'''Ejemplo:'''

<pre>
Dominio: wube.software
IP: 192.0.2.2
Puerto: 34197

Registro DNS:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Ahora cuando un cliente de Factorio se conecte a wube.software se conectará en realidad a srv-target.wube.software:34197

'''Captura de pantalla de ejemplo:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Entradas del registro:'''

* Factorio registrará un mensaje “DNS SRV lookup returned […]” cuando encuentre un registro SRV para el dominio proveído
* Con el registro detallado, Factorio también registrará “DNS SRV lookup for [domain] didn’t return any usable records” cuando no haya ningún registro SRV

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T11:46:49Z

LagExpress:

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== Cómo publicar en el servidor de emparejamiento una partida alojada en un servidor ===

Para publicar la partida en el servidor de emparejamiento, Factorio necesita recibir más información que solo la ubicación del archivo de guardado. Esta información se proporciona en un ''archivo de configuración del servidor''.

Para crear un archivo de configuración del servidor, mira el archivo de ejemplo ubicado en '''data/server-settings.example.json''' en el [[Application directory|Directorio de la aplicación]] de Factorio. La forma recomendada es hacer una copia de este archivo de ejemplo y editar la copia.

Los siguientes valores pueden ser cambiados:
; Name: Este será el nombre bajo el cual el servidor aparecerá en la lista de partidas publicas.
; Description: Una descripción de tu servidor. Puede contener hasta 5000 caracteres. [https://factorio.com/blog/post/fff-304 MP server description].
; Tags: Una lista de etiquetas de juego.
; Max Players: Te permite limitar el número de jugadores que pueden estar conectados al servidor al mismo tiempo. Si no quieres límite, simplemente establece max_players en 0.
* Visibilidad para el buscador de partidas publicas: Puede ser público, LAN u oculto.
** Public: El servidor aparecerá en la lista de servidores públicos. Esto requiere que se completen las credenciales de inicio de sesión a continuación.
** LAN: El servidor no aparecerá en la lista de servidores públicos, pero estará disponible a través del botón Jugar en LAN.
** Hidden: Los clientes tendrán que conectarse usando la dirección IP del servidor.
* Credenciales de usuario utilizando un nombre de usuario y contraseña o token de autenticación (encontrado en el sitio web de factorio o en player-data.json); Estos son necesarios si deseas hacer público el servidor. De lo contrario, pueden dejarse vacíos.
** Por razones de seguridad, se recomienda usar el token de autenticación ya que este documento se almacena como texto plano. Aunque se debe tener en cuenta que un token de autenticación también es una información sensible, y se te aconseja mantenerlo en secreto.
* Contraseña del servidor
** El nombre del campo es game_password
* Si verificar o no la identidad del usuario
(Hay valores adicionales en la v0.14 de factorio.)

=== Detalles técnicos de la implementación ===

El equipo de desarrollo ha publicado notas sobre algunos detalles técnicos relacionados con el modo multijugador en varias entradas del blog Friday Facts:

* [http://www.factorio.com/blog/post/fff-76 Arquitectura lock step]
* [http://www.factorio.com/blog/post/fff-99 Conexiones cliente-servidor]
* [http://www.factorio.com/blog/post/fff-143 NAT punching, introducido en 0.13]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-30T11:02:57Z

LagExpress:

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/headless ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o headless) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo headless:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

=== Configurando un servidor de Factorio en Linux ===

'''Nota:''' Factorio ahora require <tt>glibc</tt> versión 2.18, pero CentOS/RHEL 7 solo viene con la versión 2.17 por lo que esta guía ya no funcionara sin [https://forums.factorio.com/viewtopic.php?t=54654#p324493 compilar manualmente <tt>glibc</tt> 2.18].

Esta guía paso a paso ha sido verificada en instalaciones nuevas de CentOS 7 y RHEL 7, pero debería ser aplicable con pocas o ninguna modificación en la mayoría de las distribuciones.

Esta guía asume que instalarás el servidor headless en '''/opt/factorio''', ajusta las rutas según tu propia configuración. También sugerimos que ejecutes el servidor de Factorio como un usuario separado para fortalecer la seguridad de tu instalación.

Ten en cuenta que hay dos paquetes distintos para Linux que se pueden usar para ejecutar un servidor headless. El primero es la descarga habitual de Linux, que contiene el juego completo. El otro es el [https://www.factorio.com/download paquete especial headless]. El paquete headless no contiene archivos que son irrelevantes para un servidor puro, como gráficos y sonidos. Tampoco está vinculado a bibliotecas que pueden no estar presentes en una máquina de servidor, como Xlib, libGL o libasound. Esta opción debe seleccionarse si se ejecuta en un servidor alojado por terceros.

Esta guía no toca el tema del firewall/reenvío de puertos ya que esto se puede hacer de varias maneras en Linux (asegúrate de leer cómo se hace esto como administrador de Linux en tu distribución).

==== Instalación básica ====

* Descarga el paquete seleccionado, ya sea el juego completo o el paquete headless, y sube el paquete Linux tar.gz o tar.xz al directorio /tmp de tu servidor.
* Extrae el paquete en /tmp a /opt/factorio
<pre>
$cd /opt/

$sudo tar -xzf /tmp/factorio.tar.gz # utiliza el nombre de archivo correcto, Incluye el número de versión de factorio.
$sudo tar -xJf /tmp/factorio.tar.xz # si descargaste un archivo .tar.xz (ver 0.15.x)</pre>

* Agrega un nuevo usuario a tu sistema y asigna la propiedad del directorio factorio a el mismo (por favor, no lo ejecutes como usuario root, puede ser necesario sudo)
<pre>
$useradd factorio
$chown -R factorio:factorio /opt/factorio</pre>

* Prueba el binario
<pre>
$su factorio
$/opt/factorio/bin/x64/factorio --start-server savename</pre>

¡Mientras falle diciendo que no puede encontrar/abrir savename.zip estás listo! Solo sube una partida desde tu propia computadora y colócala en el directorio /opt/factorio/saves, o usa el argumento --create ./saves/newgame.zip.

=== 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-28T20:50:32Z

LagExpress: fixed typo

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige una partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuración]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos (apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/sin cabeza ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o sin cabeza) utilizando el parámetro ''--start-server'' en la línea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo sin cabeza:
* No se inicializan los gráficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la línea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la línea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la línea de comandos.''

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

==== Basic installation ====

* 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-28T20:44:14Z

LagExpress: /* Dedicated/Headless server */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige un partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuracion]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos(apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== Servidor dedicado/sin cabeza ===

A partir de la versión 0.12.0 de Factorio, se puede iniciar un servidor dedicado (o sin cabeza) utilizando el parámetro ''--start-server'' en la linea de comandos. Puedes utilizar el parámetro --help para obtener una lista completa de los parámetros que Factorio acepta.

En el modo sin cabeza:
* No se inicializan los graficos (inicia más rápido, consume menos memoria, funciona en servidores sin interfaz gráfica)
* El juego comienza inmediatamente y carga el archivo de guardado que se ha colocado como argumento en los parámetros
* El servidor no tiene personaje en el juego
* El juego se pausa mientras no hay jugadores conectados (aunque esto puede ser anulado usando la opción no-auto-pause en el archivo server-settings.json)
* La partida se guarda al salir (y se guarda automáticamente de forma normal)

''A partir de la versión 0.13 se espera que --start-server sea seguido por una ruta a un archivo de guardado.''

Necesitaras crear tu archivo de guardado antes de iniciar el servidor, ya que el servidor dedicado REQUIERE que se proporcione un archivo de guardado. Esto se puede hacer fácilmente utilizando el parámetro de la linea de comandos ''--create''. Por ejemplo:

<pre>
./bin/x64/factorio --create ./saves/partida.zip # Esto crea un nuevo archivo de guardado como si hubieras hecho click en el botón ''Nuevo Juego'' en la interfaz grafica
</pre>

<pre>
./bin/x64/factorio --start-server ./saves/partida.zip # Esto inicia un servidor que alojará el archivo creado con el comando anterior
</pre>

Hay varios archivos de configuración JSON que Factorio puede utilizar para cambiar la configuración del servidor y del mapa:
* '''map-gen-settings''' para establecer parámetros utilizados por el [[Map generator/es|generador de mapas]] como ancho y alto, frecuencia y tamaño de los parches de mineral, etc. (Añadido en versión 0.13)
* '''map-settings''' para controlar la propagación de la contaminación, la expansión y evolución de los biters, y más (Añadido en la versión 0.15)
* '''server-settings''' consolida múltiples opciones de la linea de comandos en un solo archivo (Añadido en la versión 0.14.12)
Los archivos de ejemplo para cada uno de estos parámetros están incluidos en el subdirectorio ''data'', y también son visibles en el GitHub de Wube aquí: https://github.com/wube/factorio-data

Los parámetros --map-gen-settings y --map-settings deben ser utilizados junto a --create cuando creas un nuevo mapa. Por ejemplo:

<pre>./bin/x64/factorio --create saves/partida.zip --map-gen-settings my-map-gen-settings.json --map-settings my-map-settings.json</pre>

Iniciar el servidor de factorio requiere que especifiques la ubicación del archivo server-settings.json que se encuentra por defecto en la carpeta ''data'' de factorio. Por ejemplo para iniciar factorio utilizando la partida más reciente, ejecutarías:

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

En Windows puede ser útil iniciar el servidor con un archivo ''.bat''. El archivo debe poseer el siguiente contenido:

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

''Mira [[Command_line_parameters]] para más parámetros de la linea de comandos.''

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

==== Basic installation ====

* 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-28T19:49:20Z

LagExpress: /* Setting Up a Multiplayer Game */

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Configurando una partida multijugador ==

[[File:multiplayer_game_night.png|thumb|250px|Una partida multijugador.]]Es posible unirse a una partida multijugador, alojarla mientras juegas o alojarla en un servidor dedicado. Las partidas multijugador pueden ser anunciadas a otros jugadores en la misma red LAN o globalmente.

Para comenzar a jugar una partida multijugador, selecciona el botón Multijugador del menú principal. Luego, elige una de estas opciones para alojar y jugar:

'''Albergar una nueva partida''': Especifica el escenario deseado, ajusta la configuración del [[Map generator/es|generador de mapas]], y establece las etiquetas del servidor. Las etiquetas del servidor determinan cómo se anunciará tu partida a otros jugadores. Puedes elegir entre:
** '''Público''': Tu partida aparecerá en la lista de partidas públicas.
** '''Steam''': Habilita o deshabilita la función “Unirse al juego” a través de Steam.
** '''LAN''': Tu partida aparecerá en tu red local.
'''Alojar una partida guardado''': Elige un partida guardada de la lista y establece las etiquetas del servidor como se indicó anteriormente.

Para unirte a una partida existente, elige una de estas opciones:
'''Buscar partidas públicas''': Busca y únete a cualquier partida pública que cumpla con tus criterios.
'''Buscar partidas LAN''': Únete a cualquier partida que se aloje en tu red local.
'''Conectar con dirección''': Únete a cualquier partida ingresando la dirección IP del servidor. Esta opción es útil si el anfitrión no utiliza ninguna etiqueta de servidor.

Notas y consejos:

* Todas las instancias del juego deben ser ''exactamente iguales'' teniendo la misma version del juego y mods.
* Los servidores de Factorio usan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuracion]].
* Factorio utiliza '''Sólo UDP'''. El juego crea su su propia capa de "entrega confiable" basada en el protocolo UDP para lidiar con problemas de reordenamiento de pérdida y reordenamiento de paquetes.
** Asegúrate de configurar correctamente el reenvío de puertos(apertura de puertos/port forwarding) de tu router para el puerto '''34197'''.
** Asegúrate de que tu router no [https://doc.pfsense.org/index.php/Static_Port aleatorice el puerto de origen] en los paquetes salientes desde el '''34197'''. Algunos routers lo hacen y requieren [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 una configuración adicional] para evitarlo.
** Asegúrate de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* El límite duro para el número de jugadores es [https://forums.factorio.com/viewtopic.php?f=53&t=6481&p=50661#p50586 65,535]. Sin embargo, el límite práctico para esto es mucho menor, algunos streamers populares han logrado conectar a cientos de jugadores en una misma partida.

=== 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, and are also visible on Wube's github here: https://github.com/wube/factorio-data

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>

On windows, it may be useful to start the server with a .bat file. The bat file should have the following content:

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

''See [[Command_line_parameters]] for more command line parameters.''

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

==== Basic installation ====

* 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress

2023-12-28T19:22:19Z

LagExpress:

EN:

[https://wiki.factorio.com/User:LagExpress/Multiplayer Multiplayer]

ES:

[https://wiki.factorio.com/User:LagExpress/Main_Page/es Main Page]

[https://wiki.factorio.com/User:LagExpress/Multiplayer/es Multijugador]

User:LagExpress/Multiplayer

2023-12-28T19:20:44Z

LagExpress: Revised multiplayer guide.

{{Languages}}
[[File:players_colored_preview.png|190px|right]]In addition to being a single-player game, Factorio also supports multiplayer, allowing many [[player]]s 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 ==

[[File:multiplayer_game_night.png|thumb|250px|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.

To start playing a multiplayer game, select the Multiplayer button from the main menu. Then, choose one of these options to host and play:

* '''Host new game''': Specify the desired scenario, adjust the [[Map generator|map generator]] settings, and set the server tags. The server tags determine how your game will be advertised to other players. You can choose from:
** '''Public''': Your game will be listed on the public games list.
** '''Steam''': Enables or disables the "Join Game" feature through steam.
** '''LAN''': Your game will be listed on your local network.
* '''Host saved game''': Pick a saved game from the list and set the server tags as above.

To join an existing game, choose one of these options:

* '''Browse''': Search for and join any public game that meets your criteria.
* '''Play on LAN''': Join any game that is hosted on your local network.
* '''Connect''': Join any game by entering the server’s IP address. This option is useful if the host does not use any server tags.

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'''. The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.
** Make sure you configure your router's port forwarding correctly for port '''34197'''.
** Make sure your router does not [https://doc.pfsense.org/index.php/Static_Port randomize the source port] on packets outbound from '''34197'''. Some routers do this and require [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 additional configuration] to prevent it.
** 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 to get well 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, and are also visible on Wube's github here: https://github.com/wube/factorio-data

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>

On windows, it may be useful to start the server with a .bat file. The bat file should have the following content:

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

''See [[Command_line_parameters]] for more command line parameters.''

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

==== Basic installation ====

* 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer

2023-12-28T19:15:59Z

LagExpress: Created page with "{{Languages}} rightIn 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 freeplay scenario w..."

{{Languages}}
[[File:players_colored_preview.png|190px|right]]In addition to being a single-player game, Factorio also supports multiplayer, allowing many [[player]]s 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 ==

[[File:multiplayer_game_night.png|thumb|250px|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'''. The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.
** Make sure you configure your router's port forwarding correctly for port '''34197'''.
** Make sure your router does not [https://doc.pfsense.org/index.php/Static_Port randomize the source port] on packets outbound from '''34197'''. Some routers do this and require [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 additional configuration] to prevent it.
** 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 to get well 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, and are also visible on Wube's github here: https://github.com/wube/factorio-data

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>

On windows, it may be useful to start the server with a .bat file. The bat file should have the following content:

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

''See [[Command_line_parameters]] for more command line parameters.''

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

==== Basic installation ====

* 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

User:LagExpress/Multiplayer/es

2023-12-28T04:15:52Z

LagExpress: updated to current page version, this is a WIP

{{Languages}}{{Translation verification|revisionID=194241}}
{{DISPLAYTITLE:Multijugador|noerror}}
[[File:players_colored_preview.png|190px|right]]Además del modo para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo a muchos [[player/es|Jugador]]es cooperar y ayudarse mutuamente, o trabajar en contra de cada uno en PvP. Esta página documenta cómo configurar una partida multijugador, cómo unirse a una, y las funciones de administración para gestionar tanto el servidor como a otros [[player/es|Jugador]]es. Por defecto, las partidas multijugador ejecutan el escenario de juego cooperativo [[Game modes and options/es|Modo libre]] donde todos los [[player/es|Jugador]]es trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas PvP, están disponibles para descargar desde el [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 foro de Mapas y Escenarios].

== Setting Up a Multiplayer Game ==

[[File:multiplayer_game_night.png|thumb|250px|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'''. The game builds its own "reliable delivery" layer built on UDP to deal with packet loss and reordering issues.
** Make sure you configure your router's port forwarding correctly for port '''34197'''.
** Make sure your router does not [https://doc.pfsense.org/index.php/Static_Port randomize the source port] on packets outbound from '''34197'''. Some routers do this and require [https://forum.pfsense.org/index.php?PHPSESSID=3k4h9n5o2tksgqv910fknf7qt7&topic=142188.msg798594#msg798594 additional configuration] to prevent it.
** 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 to get well 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, and are also visible on Wube's github here: https://github.com/wube/factorio-data

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>

On windows, it may be useful to start the server with a .bat file. The bat file should have the following content:

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

''See [[Command_line_parameters]] for more command line parameters.''

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

==== Basic installation ====

* 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 description of your server. May contain up to 5000 characters. [https://factorio.com/blog/post/fff-304 MP server description]
; 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]

=== DNS SRV Records ===
Factorio supports [https://www.cloudflare.com/learning/dns/dns-records/dns-srv-record/ DNS SRV records] since 1.1.67.

This makes it easier to have multiple Factorio servers on a single host and allow users to connect to them with distinct subdomains instead of having to enter port numbers.

The service name is <code>_factorio</code> and it only supports <code>_udp</code> protocol.

'''Example:'''

<pre>
Domain: wube.software
IP: 192.0.2.2
Port: 34197

DNS records:
srv-target IN A 192.0.2.2
_factorio._udp IN SRV 0 0 34197 srv-target.wube.software.
</pre>

Now a Factorio client connecting to wube.software will actually connect to srv-target.wube.software:34197

'''Example screenshot:'''

[[File:Screenshot of SRV record settings Cloudflare dashboard.png]]

'''Log Entries:'''

* Factorio will log a "DNS SRV lookup returned [...]" message when it found a SRV record for the given domain
* With verbose logging Factorio will also log "DNS SRV lookup for [domain] didn't return any usable records" when there's no SRV record

=== 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
/color r g b
r, g and b are for red, green and blue respectively (possible values are between 0 and 1, use [https://www.w3schools.com/colors/colors_converter.asp this site] to convert colors to rgb numbers).
* To give yourself admin access, you need to create a server-adminlist.json in the same directory as factorio-current.log. The file should contain a list of admins, like so: <code>[ "user1", "user2" ]</code>

This file will be created if you promote a player through the console.

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

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

=== 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 [[Military units and structures]] 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.
;Power leeching
: Players can draw power from an opposing force's electric network, by building structures inside the coverage area of a power pole belonging to an opposing force. Power poles that you build next to a power pole belonging to an opposing force will automatically connect to it, but will be impossible to connect or disconnect manually.

== 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. Not every action is a part of latency hiding – most notably, car or train driving and shooting are not a part of it.

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

{{C|Main}}

Main Page/es

2023-12-28T01:26:54Z

LagExpress: Use hr steel axe instead of iron axe + added link "Materials and recipes/es"

{{Languages}}
{{DISPLAYTITLE:Wiki Oficial de Factorio|noerror}}__NOTOC__[[Image:Factorio-logo.png|center|461px|link=https://factorio.com/]]


Bienvenidos a la wiki oficial de Factorio, la fuente oficial de documentación de Factorio™. 
{{NUMBEROFACTIVEUSERS}} editores activos (de {{NUMBEROFUSERS}} registrados) están actualmente manteniendo [[Special:Statistics|{{NUMBEROFARTICLES}} artículos]] y [[Special:ListFiles|{{NUMBEROFFILES}} imágenes]].


{| style="width: 100%; border-spacing: 8px;"
{{ContentCell|66%|
|{{:Factorio:About/es}}
}}
{{ContentCell|34%|[[File:Steel axe.png|link=|32px]] [http://www.factorio.com/buy Obtén el juego]|{{:Main Page/Get the game‎/es}}
}}
|-
{{ContentCell|66%|[[File:Lab.png|link=|32px]] [[News|Blog del desarrollador: Factorio Friday Facts]]|{{:News}}
}}
{{ContentCell|34%|[[File:Assembling machine 3.png|link=|32px]] Últimas actualizaciones|{{:Main_Page/Latest_versions}}
}}
|}

==== El juego ====

{| style="width: 100%; border-spacing: 8px;"
{{ContentCell|33%|[[File:Transport belt.png|link=|32px]] Principiantes | {{:Main_Page/Beginners/es}}
}}
{{ContentCell|33%|[[File:Fast transport belt.png|link=|32px]] Avanzados | {{:Main_Page/Advanced/es}}
}}
{{ContentCell|34%|[[File:Express transport belt.png|link=|32px]] Expertos | {{:Main_Page/Expert/es}}
}}
|}
{| style="width: 100%; border-spacing: 8px; margin-top: -8px;"
{{ContentCell|100%|[[Materials and recipes/es|Materiales y recetas]]|{{Inventory}}
}}
|}

==== Información Adicional ====
{| style="width: 100%; border-spacing: 8px;"
{{ContentCell|33%|[[File:Processing unit.png|link=|32px]] Nuevo contenido|{{:Main_Page/New_content/es}}
}}
{{ContentCell|33%|[[File:Questionmark.png|32px|link=]] Preguntas Frecuentes|{{:Main_Page/Frequently asked questions/es}}|
[[File:Repair pack.png|link=|32px]] Contribuir a la wiki|{{:Main_Page/Contribute/es}}
}}
{{ContentCell|34%|[[File:Behemoth spitter icon.png|link=|32px]] Comunidad|{{:Main_Page/Community/es}}
}}
|}

__NOEDITSECTION__

{{C|Main}}

Main Page/Get the game/es

2023-12-27T20:23:08Z

LagExpress: Updated game status and added Nintendo eShop as a purchase platform

Factorio fue lanzado oficialmente. El juego puede ser comprado en su [https://www.factorio.com/buy sitio web oficial], [http://store.steampowered.com/app/427520/ Steam], [https://www.gog.com/game/factorio GOG], la [https://www.humblebundle.com/store/factorio Humble Store] y la [https://www.nintendo.com/store/products/factorio-switch/ Nintendo eShop]. También hay una [https://www.factorio.com/demo demo] disponible.

<noinclude>
{{Languages}}
{{C|Main}}
</noinclude>

Steel furnace/es

2019-04-29T16:02:33Z

LagExpress: Created page with "{{Languages}} {{:Infobox:Steel furnace}} El '''horno de acero''' es el segundo nivel de los hornos. Comparado con el horno de piedra, funde al doble de v..."

{{Languages}}
{{:Infobox:Steel furnace}}

El '''horno de acero''' es el segundo nivel de los hornos. Comparado con el [[stone furnace/es|horno de piedra]], funde al doble de velocidad y por lo tanto hace un uso mas eficiente del combustible proveído, el horno de acero es comparable con el [[electric furnace/es|horno eléctrico]] en términos de velocidad para fundir, no obstante este ultimo puede hacer uso de [[module/es|módulo]]s(así como [[electric system/es|electricidad]]) para mejorar aun mas las capacidades del horno.

== Colocación ==

Un horno de acero puede reemplazar a un [[stone furnace/es|horno de piedra]] sin minar el [[stone furnace/es|horno de piedra]] primero. Esto se puede hacer haciendo clic en el [[stone furnace/es|horno de piedra]] con el '''horno de acero''' en la mano del jugador. Esto también mueve todos los objetos del horno de piedra hacia el nuevo horno.

== Salida ==

{| class="wikitable"
! rowspan="2" | Resource
! {{Imagelink|Stone furnace}}
! {{Imagelink|Steel furnace}}
! {{Imagelink|Electric furnace}}
|-
| '''Consumo de carbón''': 0.0225/seg
| '''Consumo de carbón''': 0.0225/seg
|
|-
! scope="row" | Iron
| {{Icon|Iron plate|0.3125}} 0.3125/seg
| {{Icon|Iron plate|0.625}} 0.625/seg
| {{Icon|Iron plate|0.625}} 0.625/seg
|-
! scope="row" | Copper
| {{Icon|Copper plate|0.3125}} 0.3125/seg
| {{Icon|Copper plate|0.625}} 0.625/seg
| {{Icon|Copper plate|0.625}} 0.625/seg
|-
! scope="row" | Stone brick
| {{Icon|Stone brick|0.3125}} 0.3125/seg
| {{Icon|Stone brick|0.625}} 0.625/seg
| {{Icon|Stone brick|0.625}} 0.625/seg
|-
! scope="row" | Steel plate
| {{Icon|Steel plate|0.0625}} 0.0625/seg
| {{Icon|Steel plate|0.125}} 0.125/seg
| {{Icon|Steel plate|0.125}} 0.125/seg
|}

{{ProductionNav}}
{{C|Furnaces}}

Crafting/es

2019-04-28T23:28:15Z

LagExpress: /* Creación automatizada */ ingredient limits removed from the assembly machine description

{{Languages}}
El proceso de 'Creación' es producir un producto final a partir de productos de entrada utilizando una receta. El [[player/es|jugador]] o las [[Assembling machine/es|máquinas de ensamblaje]] pueden crear. La fundición se logra utilizando [[furnace/es|hornos]]. Dado que el jugador no puede realizar la fundición directamente, es imposible crear algunos objetos directamente a partir de recursos en bruto. Algunas recetas incluso mas allá de los recursos en bruto pueden requerir una máquina de ensamblaje.

Al principio del juego, es fácil hacer todo manualmente, pero a medida que el juego avanza la creación manual se hace cada ves una forma menos eficiente de crear. Los productos que requieren líquidos y algunos otros (tales como los motores) no pueden ser creados manualmente. Esto es para incentivar la automatización

== Logros ==
{{Achievement|lazy-bastard}}

== Creación manual ==
[[File:crafting_queue_anim.gif|left]]
La creación manual es la forma de fabricación mas básica, es realizada directamente desde el inventario del jugador. Para crear un objeto manualmente, abre el inventario del jugador (Tecla Predeterminada {{keybinding|e}}), y selecciona un objeto a crear manualmente en la derecha. Clic izquierdo para uno, clic derecho para cinco, y mayús + clic para crear la máxima cantidad posible. Si la imagen del objeto se encuentra en gris, asegurate de tener los materiales necesarios para crear el objeto, si no tienes los recursos, te lo mostrara resaltado en texto rojo si pasas el cursor sobre el producto. Los materiales que no tienes pero que pueden ser creados se te mostraran resaltados en texto naranja, y será una cadena de creación para completar la creación del producto que seleccionaste. Esta es la ventaja sobre la creación automatizada utilizando maquinas, las cuales no crean automáticamente los ingredientes intermedios.

Mientras creas manualmente, aparecerán iconos en la esquina inferior izquierda de la pantalla, la cual mostrara la operación de creación actual. Cuando un objeto es seleccionado para su creación, los recursos serán removidos del inventario del jugador preventivamente. Si la operación es cancelada, los recursos regresaran en su totalidad al inventario del jugador

Para cancelar una operación de creación manual desde la cola en la parte inferior izquierda de la pantalla, haga clic con el botón izquierdo (para cancelar una operación), haga clic con el botón derecho (para cancelar cinco operaciones) o haga clic izquierdo con la tecla Mayús presionada para cancelar la creación de ese producto. Esto es útil si accidentalmente colocas en la cola el producto equivocado, o demasiados productos. Todos los materiales tomados para fabricar el artículo serán devueltos a su inventario. La creación manual se puede cancelar en cualquier momento, pero los productos intermedios ya creados no se reintegraran ni eliminaran.

== Creación automatizada ==

La creación automatizada se realiza fuera del inventario del jugador, permitiendo la producción de múltiples productos simultáneamente, en sincronía armónica. Aquí es donde la mayor parte de la producción debe llevarse a cabo.

Las estructuras clave en la creación automatizada son:
{| class="wikitable"
!colspan=2| Extracción de recursos
|-
| {{Imagelink|Burner mining drill}} {{Imagelink|Electric mining drill}} || Extrae recursos [[Mining/es|mineros]].
|-
| {{Imagelink|Offshore pump}} || Extrae [[water/es|agua]] de los lagos.
|-
| {{imagelink|Pumpjack}} || Extrae [[crude oil/es|petróleo crudo]] de yacimientos petroleros.
|-
!colspan=2| Hornos
|-
| {{Imagelink|Stone furnace}} {{Imagelink|Steel furnace}} {{Imagelink|Electric furnace}} || Procesan los minerales en bruto a su estado metálico, mediante un proceso de fundición.
|-
!colspan=2| Producción
|-
| {{imagelink|Assembling machine 1}} || No puede manipular ingredientes líquidos.
|-
| {{imagelink|Assembling machine 2}} || Puede manipular recetas con ingredientes líquidos.
|-
| {{imagelink|Assembling machine 3}} || Puede manipular recetas que requieren ingredientes líquidos.
|-
| {{Imagelink|Oil refinery}} {{Imagelink|Chemical plant}} || Procesa [[crude oil/es|petróleo crudo]] y otros fluidos.
|-
| {{imagelink|Centrifuge}} || Procesa el [[uranium ore/es|mineral de uranio]] en productos intermedios más útiles.
|}

== Básico ==
Como una introducción a la creación, crearemos algunas placas de hierro

'''Tarea''': Crear [[iron plate/es|placas de hierro]].

Pasos:
# Coloca una [[burner mining drill/es|perforadora a vapor]] sobre una un campo de [[Iron ore/es|menas de hierro]]. Este es un parche plateado que es bastante común.
# Coloca un [[Furnace/es|horno]] directamente en frente de la salida (presiona {{keybinding|Alt}} para mostrar la flecha de salida), para que la perforadora coloque el metal en bruto en el horno, el cual puede recibirlo de cualquiera de sus lados.
# Llena tanto la perforadora como el horno con [[Fuel/es|combustible]]s, tales como carbón o madera.
# Espera. Tras unos pocos segundos, la primera pieza de [[Iron plate/es|placa de hierro]] será fundida y estará disponible para su recolección. Puedes recocerla manualmente, o sacarla utilizando un [[Inserters/es| insertador]]

Todo este proceso se conoce comúnmente como 'fundición'. La {{L|Copper ore}} debe ser fundida también.

== Avanzado ==

La creación de artículos puede ser automatizada. Para crear artículos automáticamente, coloque una [[Assembling machine/es|máquina de ensamblaje]] y seleccione la receta. Tenga en cuenta que si la receta es lo suficientemente complicada, pueden ser necesarias máquinas de ensamblaje de mayor nivel. Luego coloque todos los ingredientes solicitados en las ranuras de entrada, y la máquina de ensamblaje debe diseñar el artículo. Tenga en cuenta que, a diferencia de la creación manual, cada paso de la creación requiere otra máquina de montaje. Por ejemplo, crear una [[lamp/es|lámpara]] requiere que una máquina fabrique [[copper cable/es|cable de cobre]], una máquina para hacer [[iron stick/es|barras de hierro]] s, una máquina para hacer [[electronic circuit/es|circuitos electrónicos]] s, etc. ''Las máquinas de ensamblaje no pueden crear componentes intermedios en cadena automáticamente como lo hace el jugador.''

Para mantener una producción continua, los ingredientes deben proporcionarse a través de un [[belt transport system/es|sistema de cintas transportadoras]] e [[Inserters/es|incertadores]]. Los objetos manufacturados también pueden ser extraídos por los insertadores y están disponibles para su uso posterior en cualquier otro lugar de la fábrica.

== Dificultad de las recetas ==

En el [[World generator/es|generador de mapas]], el jugador puede elegir entre recetas normales o caras (modo caro). Las recetas caras representan un reto mas allá del juego "vanilla" con recetas normales (modo normal) porque cambian algunos ratios comunes y tienen requerimientos de recursos mas elevados.

== Ver también ==
* [[Electric system/es|Sistema Eléctrico]]
* [[Assembling machine/es|Máquina de ensamblaje]]
* [[Furnace/es|Horno]]

Crafting/es

2019-04-28T22:48:26Z

LagExpress: /* Creación manual */ added /Crafting_queue_anim.gif

{{Languages}}
El proceso de 'Creación' es producir un producto final a partir de productos de entrada utilizando una receta. El [[player/es|jugador]] o las [[Assembling machine/es|máquinas de ensamblaje]] pueden crear. La fundición se logra utilizando [[furnace/es|hornos]]. Dado que el jugador no puede realizar la fundición directamente, es imposible crear algunos objetos directamente a partir de recursos en bruto. Algunas recetas incluso mas allá de los recursos en bruto pueden requerir una máquina de ensamblaje.

Al principio del juego, es fácil hacer todo manualmente, pero a medida que el juego avanza la creación manual se hace cada ves una forma menos eficiente de crear. Los productos que requieren líquidos y algunos otros (tales como los motores) no pueden ser creados manualmente. Esto es para incentivar la automatización

== Logros ==
{{Achievement|lazy-bastard}}

== Creación manual ==
[[File:crafting_queue_anim.gif|left]]
La creación manual es la forma de fabricación mas básica, es realizada directamente desde el inventario del jugador. Para crear un objeto manualmente, abre el inventario del jugador (Tecla Predeterminada {{keybinding|e}}), y selecciona un objeto a crear manualmente en la derecha. Clic izquierdo para uno, clic derecho para cinco, y mayús + clic para crear la máxima cantidad posible. Si la imagen del objeto se encuentra en gris, asegurate de tener los materiales necesarios para crear el objeto, si no tienes los recursos, te lo mostrara resaltado en texto rojo si pasas el cursor sobre el producto. Los materiales que no tienes pero que pueden ser creados se te mostraran resaltados en texto naranja, y será una cadena de creación para completar la creación del producto que seleccionaste. Esta es la ventaja sobre la creación automatizada utilizando maquinas, las cuales no crean automáticamente los ingredientes intermedios.

Mientras creas manualmente, aparecerán iconos en la esquina inferior izquierda de la pantalla, la cual mostrara la operación de creación actual. Cuando un objeto es seleccionado para su creación, los recursos serán removidos del inventario del jugador preventivamente. Si la operación es cancelada, los recursos regresaran en su totalidad al inventario del jugador

Para cancelar una operación de creación manual desde la cola en la parte inferior izquierda de la pantalla, haga clic con el botón izquierdo (para cancelar una operación), haga clic con el botón derecho (para cancelar cinco operaciones) o haga clic izquierdo con la tecla Mayús presionada para cancelar la creación de ese producto. Esto es útil si accidentalmente colocas en la cola el producto equivocado, o demasiados productos. Todos los materiales tomados para fabricar el artículo serán devueltos a su inventario. La creación manual se puede cancelar en cualquier momento, pero los productos intermedios ya creados no se reintegraran ni eliminaran.

== Creación automatizada ==

La creación automatizada se realiza fuera del inventario del jugador, permitiendo la producción de múltiples productos simultáneamente, en sincronía armónica. Aquí es donde la mayor parte de la producción debe llevarse a cabo.

Las estructuras clave en la creación automatizada son:
{| class="wikitable"
!colspan=2| Extracción de recursos
|-
| {{Imagelink|Burner mining drill}} {{Imagelink|Electric mining drill}} || Extrae recursos [[Mining/es|mineros]].
|-
| {{Imagelink|Offshore pump}} || Extrae [[water/es|agua]] de los lagos.
|-
| {{imagelink|Pumpjack}} || Extrae [[crude oil/es|petróleo crudo]] de yacimientos petroleros.
|-
!colspan=2| Hornos
|-
| {{Imagelink|Stone furnace}} {{Imagelink|Steel furnace}} {{Imagelink|Electric furnace}} || Procesan los minerales en bruto a su estado metálico, mediante un proceso de fundición.
|-
!colspan=2| Producción
|-
| {{imagelink|Assembling machine 1}} || Puede crear objetos que requieren hasta 2 tipos de ingredientes. No puede manejar ingredientes fluidos.
|-
| {{imagelink|Assembling machine 2}} || Puede crear objetos que requieren hasta 4 tipos de ingredientes. Puede manipular recetas con ingredientes líquidos.
|-
| {{imagelink|Assembling machine 3}} || Puede crear objetos que requieren hasta 6 tipos de ingredientes. Puede manipular recetas que requieren ingredientes líquidos.
|-
| {{Imagelink|Oil refinery}} {{Imagelink|Chemical plant}} || Procesa [[crude oil/es|petróleo crudo]] y otros fluidos.
|-
| {{imagelink|Centrifuge}} || Procesa el [[uranium ore/es|mineral de uranio]] en productos intermedios más útiles.
|}

== Básico ==
Como una introducción a la creación, crearemos algunas placas de hierro

'''Tarea''': Crear [[iron plate/es|placas de hierro]].

Pasos:
# Coloca una [[burner mining drill/es|perforadora a vapor]] sobre una un campo de [[Iron ore/es|menas de hierro]]. Este es un parche plateado que es bastante común.
# Coloca un [[Furnace/es|horno]] directamente en frente de la salida (presiona {{keybinding|Alt}} para mostrar la flecha de salida), para que la perforadora coloque el metal en bruto en el horno, el cual puede recibirlo de cualquiera de sus lados.
# Llena tanto la perforadora como el horno con [[Fuel/es|combustible]]s, tales como carbón o madera.
# Espera. Tras unos pocos segundos, la primera pieza de [[Iron plate/es|placa de hierro]] será fundida y estará disponible para su recolección. Puedes recocerla manualmente, o sacarla utilizando un [[Inserters/es| insertador]]

Todo este proceso se conoce comúnmente como 'fundición'. La {{L|Copper ore}} debe ser fundida también.

== Avanzado ==

La creación de artículos puede ser automatizada. Para crear artículos automáticamente, coloque una [[Assembling machine/es|máquina de ensamblaje]] y seleccione la receta. Tenga en cuenta que si la receta es lo suficientemente complicada, pueden ser necesarias máquinas de ensamblaje de mayor nivel. Luego coloque todos los ingredientes solicitados en las ranuras de entrada, y la máquina de ensamblaje debe diseñar el artículo. Tenga en cuenta que, a diferencia de la creación manual, cada paso de la creación requiere otra máquina de montaje. Por ejemplo, crear una [[lamp/es|lámpara]] requiere que una máquina fabrique [[copper cable/es|cable de cobre]], una máquina para hacer [[iron stick/es|barras de hierro]] s, una máquina para hacer [[electronic circuit/es|circuitos electrónicos]] s, etc. ''Las máquinas de ensamblaje no pueden crear componentes intermedios en cadena automáticamente como lo hace el jugador.''

Para mantener una producción continua, los ingredientes deben proporcionarse a través de un [[belt transport system/es|sistema de cintas transportadoras]] e [[Inserters/es|incertadores]]. Los objetos manufacturados también pueden ser extraídos por los insertadores y están disponibles para su uso posterior en cualquier otro lugar de la fábrica.

== Dificultad de las recetas ==

En el [[World generator/es|generador de mapas]], el jugador puede elegir entre recetas normales o caras (modo caro). Las recetas caras representan un reto mas allá del juego "vanilla" con recetas normales (modo normal) porque cambian algunos ratios comunes y tienen requerimientos de recursos mas elevados.

== Ver también ==
* [[Electric system/es|Sistema Eléctrico]]
* [[Assembling machine/es|Máquina de ensamblaje]]
* [[Furnace/es|Horno]]

Main Page/New content/es

2019-04-28T19:11:42Z

LagExpress: updated from 0.16.0 to 0.17.0

'''Lo nuevo en la versión 0.17.0:'''
* GUI overhaul
* Nuevo editor de mapas
* Nueva campaña
* Nueva generación de mapas
* Agregado Control + C, Control + X y Control + V para copiar, cortar y pegar
* Añadida la sincronización de mods para el multijugador
* Añadida la red de Steam para el multijugador
* Planificador de mejoras y equipamiento de inmunidad a las cintas transportadoras añadidos.
* Tecnología de paquete de ciencia añadida
* Cambios en los nombres y recetas de los paquetes de ciencia
* Tecnologías militares de bonificación modificadas - menos tecnologías pero más potentes

El registro completo de cambios se puede encontrar [[Version_history|aquí]].
<noinclude>
{{Languages}}
{{C|Main}}
</noinclude>

Military science pack/es

2018-11-29T17:50:53Z

LagExpress: full translation

{{Languages}}{{:Infobox:Military science pack}}
El '''paquete de ciencia militar''' es uno de los cuatro [[science pack/es|paquetes de ciencia]] en el juego temprano, siendo los otros tres el [[science pack 1/es|paquete de ciencia 1]], el [[science pack 2/es|paquete de ciencia 2]] y el [[science pack 3/es|paquete de ciencia 3]]. Son utilizados para la [[research/es|investigación]] la cual permite al jugador avanzar su fuerza militar a través de la totalidad del Juego, desbloqueando más opciones de balas, armas, torretas, etc.

== Ratio ==

A continuación se muestra la relación mínima de ensambladores/máquinas y elementos necesarios para producir un paquete de ciencia militar, de manera que la suma de ensambladores/máquinas sean números enteros. Los artículos por minuto se calculan utilizando la [[assembling machine 3/es|máquina de ensamblaje 3]] [[module/es|sin módulos]] o [[beacon/es|balizas]] y todos los ensambladores funcionando a toda velocidad. La elaboración de algunos productos intermedios no se muestra (debido a la suposición de que estos artículos están disponibles en grandes cantidades dentro de la fábrica). Esta tabla fue producida usando la dificultad normal de la receta.

{| class="wikitable"
! Items/min !! Assemblers
|-
| {{Icon|Military science pack|150}}
|
: {{Icon|Assembling machine 3|10}}
|-
|
: {{Icon|Piercing rounds magazine|75}}
|
: {{Icon|Assembling machine 3|3}}
|-
|
:: {{Icon|Firearm magazine|75}}
|
: {{Icon|Assembling machine 3|1}}
|-
|
::: {{Icon|Iron plate|300}}
|
|-
|
:: {{Icon|Steel plate|75}}
|
|-
|
:: {{Icon|Copper plate|375}}
|
|-
|
: {{Icon|Grenade|75}}
|
: {{Icon|Assembling machine 3|8}}
|-
|
:: {{Icon|Coal|750}}
|
|-
|
:: {{Icon|Iron plate|375}}
|
|-
|
: {{Icon|Gun turret|75}}
|
: {{Icon|Assembling machine 3|8}}
|-
|
:: {{Icon|Iron plate|1500}}
|
|-
|
:: {{Icon|Copper plate|750}}
|
|-
|
:: {{Icon|Iron gear wheel|750}}
|
: {{Icon|Assembling machine 3|5}}
|-
|
::: {{Icon|Iron plate|1500}}
|
|}

== Ver también ==
* [[Research/es|Investigación]]
* [[Science pack/es|Paquete de ciencia]]
* [[Technologies/es|Tecnologias]]

{{IntermediateNav}}
{{C|Science packs}}

Crafting/es

2018-11-29T17:18:10Z

LagExpress: full translation

{{Languages}}
El proceso de 'Creación' es producir un producto final a partir de productos de entrada utilizando una receta. El [[player/es|jugador]] o las [[Assembling machine/es|máquinas de ensamblaje]] pueden crear. La fundición se logra utilizando [[furnace/es|hornos]]. Dado que el jugador no puede realizar la fundición directamente, es imposible crear algunos objetos directamente a partir de recursos en bruto. Algunas recetas incluso mas allá de los recursos en bruto pueden requerir una máquina de ensamblaje.

Al principio del juego, es fácil hacer todo manualmente, pero a medida que el juego avanza la creación manual se hace cada ves una forma menos eficiente de crear. Los productos que requieren líquidos y algunos otros (tales como los motores) no pueden ser creados manualmente. Esto es para incentivar la automatización

== Logros ==
{{Achievement|lazy-bastard}}

== Creación manual ==

La creación manual es la forma de fabricación mas básica, es realizada directamente desde el inventario del jugador. Para crear un objeto manualmente, abre el inventario del jugador (Tecla Predeterminada {{keybinding|e}}), y selecciona un objeto a crear manualmente en la derecha. Clic izquierdo para uno, clic derecho para cinco, y mayús + clic para crear la máxima cantidad posible. Si la imagen del objeto se encuentra en gris, asegurate de tener los materiales necesarios para crear el objeto, si no tienes los recursos, te lo mostrara resaltado en texto rojo si pasas el cursor sobre el producto. Los materiales que no tienes pero que pueden ser creados se te mostraran resaltados en texto naranja, y será una cadena de creación para completar la creación del producto que seleccionaste. Esta es la ventaja sobre la creación automatizada utilizando maquinas, las cuales no crean automáticamente los ingredientes intermedios.

Mientras creas manualmente, aparecerán iconos en la esquina inferior izquierda de la pantalla, la cual mostrara la operación de creación actual. Cuando un objeto es seleccionado para su creación, los recursos serán removidos del inventario del jugador preventivamente. Si la operación es cancelada, los recursos regresaran en su totalidad al inventario del jugador

Para cancelar una operación de creación manual desde la cola en la parte inferior izquierda de la pantalla, haga clic con el botón izquierdo (para cancelar una operación), haga clic con el botón derecho (para cancelar cinco operaciones) o haga clic izquierdo con la tecla Mayús presionada para cancelar la creación de ese producto. Esto es útil si accidentalmente colocas en la cola el producto equivocado, o demasiados productos. Todos los materiales tomados para fabricar el artículo serán devueltos a su inventario. La creación manual se puede cancelar en cualquier momento, pero los productos intermedios ya creados no se reintegraran ni eliminaran.

== Creación automatizada ==

La creación automatizada se realiza fuera del inventario del jugador, permitiendo la producción de múltiples productos simultáneamente, en sincronía armónica. Aquí es donde la mayor parte de la producción debe llevarse a cabo.

Las estructuras clave en la creación automatizada son:
{| class="wikitable"
!colspan=2| Extracción de recursos
|-
| {{Imagelink|Burner mining drill}} {{Imagelink|Electric mining drill}} || Extrae recursos [[Mining/es|mineros]].
|-
| {{Imagelink|Offshore pump}} || Extrae [[water/es|agua]] de los lagos.
|-
| {{imagelink|Pumpjack}} || Extrae [[crude oil/es|petróleo crudo]] de yacimientos petroleros.
|-
!colspan=2| Hornos
|-
| {{Imagelink|Stone furnace}} {{Imagelink|Steel furnace}} {{Imagelink|Electric furnace}} || Procesan los minerales en bruto a su estado metálico, mediante un proceso de fundición.
|-
!colspan=2| Producción
|-
| {{imagelink|Assembling machine 1}} || Puede crear objetos que requieren hasta 2 tipos de ingredientes. No puede manejar ingredientes fluidos.
|-
| {{imagelink|Assembling machine 2}} || Puede crear objetos que requieren hasta 4 tipos de ingredientes. Puede manipular recetas con ingredientes líquidos.
|-
| {{imagelink|Assembling machine 3}} || Puede crear objetos que requieren hasta 6 tipos de ingredientes. Puede manipular recetas que requieren ingredientes líquidos.
|-
| {{Imagelink|Oil refinery}} {{Imagelink|Chemical plant}} || Procesa [[crude oil/es|petróleo crudo]] y otros fluidos.
|-
| {{imagelink|Centrifuge}} || Procesa el [[uranium ore/es|mineral de uranio]] en productos intermedios más útiles.
|}

== Básico ==
Como una introducción a la creación, crearemos algunas placas de hierro

'''Tarea''': Crear [[iron plate/es|placas de hierro]].

Pasos:
# Coloca una [[burner mining drill/es|perforadora a vapor]] sobre una un campo de [[Iron ore/es|menas de hierro]]. Este es un parche plateado que es bastante común.
# Coloca un [[Furnace/es|horno]] directamente en frente de la salida (presiona {{keybinding|Alt}} para mostrar la flecha de salida), para que la perforadora coloque el metal en bruto en el horno, el cual puede recibirlo de cualquiera de sus lados.
# Llena tanto la perforadora como el horno con [[Fuel/es|combustible]]s, tales como carbón o madera.
# Espera. Tras unos pocos segundos, la primera pieza de [[Iron plate/es|placa de hierro]] será fundida y estará disponible para su recolección. Puedes recocerla manualmente, o sacarla utilizando un [[Inserters/es| insertador]]

Todo este proceso se conoce comúnmente como 'fundición'. La {{L|Copper ore}} debe ser fundida también.

== Avanzado ==

La creación de artículos puede ser automatizada. Para crear artículos automáticamente, coloque una [[Assembling machine/es|máquina de ensamblaje]] y seleccione la receta. Tenga en cuenta que si la receta es lo suficientemente complicada, pueden ser necesarias máquinas de ensamblaje de mayor nivel. Luego coloque todos los ingredientes solicitados en las ranuras de entrada, y la máquina de ensamblaje debe diseñar el artículo. Tenga en cuenta que, a diferencia de la creación manual, cada paso de la creación requiere otra máquina de montaje. Por ejemplo, crear una [[lamp/es|lámpara]] requiere que una máquina fabrique [[copper cable/es|cable de cobre]], una máquina para hacer [[iron stick/es|barras de hierro]] s, una máquina para hacer [[electronic circuit/es|circuitos electrónicos]] s, etc. ''Las máquinas de ensamblaje no pueden crear componentes intermedios en cadena automáticamente como lo hace el jugador.''

Para mantener una producción continua, los ingredientes deben proporcionarse a través de un [[belt transport system/es|sistema de cintas transportadoras]] e [[Inserters/es|incertadores]]. Los objetos manufacturados también pueden ser extraídos por los insertadores y están disponibles para su uso posterior en cualquier otro lugar de la fábrica.

== Dificultad de las recetas ==

En el [[World generator/es|generador de mapas]], el jugador puede elegir entre recetas normales o caras (modo caro). Las recetas caras representan un reto mas allá del juego "vanilla" con recetas normales (modo normal) porque cambian algunos ratios comunes y tienen requerimientos de recursos mas elevados.

== Ver también ==
* [[Electric system/es|Sistema Eléctrico]]
* [[Assembling machine/es|Máquina de ensamblaje]]
* [[Furnace/es|Horno]]

User:LagExpress/test/es

2018-11-29T17:09:03Z

LagExpress: full translation

{{Languages}}
El proceso de 'Creación' es producir un producto final a partir de productos de entrada utilizando una receta. El [[player/es|jugador]] o las [[Assembling machine/es|máquinas de ensamblaje]] pueden crear. La fundición se logra utilizando [[furnace/es|hornos]]. Dado que el jugador no puede realizar la fundición directamente, es imposible crear algunos objetos directamente a partir de recursos en bruto. Algunas recetas incluso mas allá de los recursos en bruto pueden requerir una máquina de ensamblaje.

Al principio del juego, es fácil hacer todo manualmente, pero a medida que el juego avanza la creación manual se hace cada ves una forma menos eficiente de crear. Los productos que requieren líquidos y algunos otros (tales como los motores) no pueden ser creados manualmente. Esto es para incentivar la automatización

== Logros ==
{{Achievement|lazy-bastard}}

== Creación manual ==

La creación manual es la forma de fabricación mas básica, es realizada directamente desde el inventario del jugador. Para crear un objeto manualmente, abre el inventario del jugador (Tecla Predeterminada {{keybinding|e}}), y selecciona un objeto a crear manualmente en la derecha. Clic izquierdo para uno, clic derecho para cinco, y mayús + clic para crear la máxima cantidad posible. Si la imagen del objeto se encuentra en gris, asegurate de tener los materiales necesarios para crear el objeto, si no tienes los recursos, te lo mostrara resaltado en texto rojo si pasas el cursor sobre el producto. Los materiales que no tienes pero que pueden ser creados se te mostraran resaltados en texto naranja, y será una cadena de creación para completar la creación del producto que seleccionaste. Esta es la ventaja sobre la creación automatizada utilizando maquinas, las cuales no crean automáticamente los ingredientes intermedios.

Mientras creas manualmente, aparecerán iconos en la esquina inferior izquierda de la pantalla, la cual mostrara la operación de creación actual. Cuando un objeto es seleccionado para su creación, los recursos serán removidos del inventario del jugador preventivamente. Si la operación es cancelada, los recursos regresaran en su totalidad al inventario del jugador

Para cancelar una operación de creación manual desde la cola en la parte inferior izquierda de la pantalla, haga clic con el botón izquierdo (para cancelar una operación), haga clic con el botón derecho (para cancelar cinco operaciones) o haga clic izquierdo con la tecla Mayús presionada para cancelar la creación de ese producto. Esto es útil si accidentalmente colocas en la cola el producto equivocado, o demasiados productos. Todos los materiales tomados para fabricar el artículo serán devueltos a su inventario. La creación manual se puede cancelar en cualquier momento, pero los productos intermedios ya creados no se reintegraran ni eliminaran.

== Creación automatizada ==

La creación automatizada se realiza fuera del inventario del jugador, permitiendo la producción de múltiples productos simultáneamente, en sincronía armónica. Aquí es donde la mayor parte de la producción debe llevarse a cabo.

Las estructuras clave en la creación automatizada son:
{| class="wikitable"
!colspan=2| Extracción de recursos
|-
| {{Imagelink|Burner mining drill}} {{Imagelink|Electric mining drill}} || Extrae recursos [[Mining/es|mineros]].
|-
| {{Imagelink|Offshore pump}} || Extrae [[water/es|agua]] de los lagos.
|-
| {{imagelink|Pumpjack}} || Extrae [[crude oil/es|petróleo crudo]] de yacimientos petroleros.
|-
!colspan=2| Hornos
|-
| {{Imagelink|Stone furnace}} {{Imagelink|Steel furnace}} {{Imagelink|Electric furnace}} || Procesan los minerales en bruto a su estado metálico, mediante un proceso de fundición.
|-
!colspan=2| Producción
|-
| {{imagelink|Assembling machine 1}} || Puede crear objetos que requieren hasta 2 tipos de ingredientes. No puede manejar ingredientes fluidos.
|-
| {{imagelink|Assembling machine 2}} || Puede crear objetos que requieren hasta 4 tipos de ingredientes. Puede manipular recetas con ingredientes líquidos.
|-
| {{imagelink|Assembling machine 3}} || Puede crear objetos que requieren hasta 6 tipos de ingredientes. Puede manipular recetas que requieren ingredientes líquidos.
|-
| {{Imagelink|Oil refinery}} {{Imagelink|Chemical plant}} || Procesa [[crude oil/es|petróleo crudo]] y otros fluidos.
|-
| {{imagelink|Centrifuge}} || Procesa el [[uranium ore/es|mineral de uranio]] en productos intermedios más útiles.
|}

== Básico ==
Como una introducción a la creación, crearemos algunas placas de hierro

'''Tarea''': Crear [[iron plate/es|placas de hierro]].

Pasos:
# Coloca una [[burner mining drill/es|perforadora a vapor]] sobre una un campo de [[Iron ore/es|menas de hierro]]. Este es un parche plateado que es bastante común.
# Coloca un [[Furnace/es|horno]] directamente en frente de la salida (presiona {{keybinding|Alt}} para mostrar la flecha de salida), para que la perforadora coloque el metal en bruto en el horno, el cual puede recibirlo de cualquiera de sus lados.
# Llena tanto la perforadora como el horno con [[Fuel/es|combustible]]s, tales como carbón o madera.
# Espera. Tras unos pocos segundos, la primera pieza de [[Iron plate/es|placa de hierro]] será fundida y estará disponible para su recolección. Puedes recocerla manualmente, o sacarla utilizando un [[Inserters/es| insertador]]

Todo este proceso se conoce comúnmente como 'fundición'. La {{L|Copper ore}} debe ser fundida también.

== Avanzado ==

La creación de artículos puede ser automatizada. Para crear artículos automáticamente, coloque una [[Assembling machine/es|máquina de ensamblaje]] y seleccione la receta. Tenga en cuenta que si la receta es lo suficientemente complicada, pueden ser necesarias máquinas de ensamblaje de mayor nivel. Luego coloque todos los ingredientes solicitados en las ranuras de entrada, y la máquina de ensamblaje debe diseñar el artículo. Tenga en cuenta que, a diferencia de la creación manual, cada paso de la creación requiere otra máquina de montaje. Por ejemplo, crear una [[lamp/es|lámpara]] requiere que una máquina fabrique [[copper cable/es|cable de cobre]], una máquina para hacer [[iron stick/es|barras de hierro]] s, una máquina para hacer [[electronic circuit/es|circuitos electrónicos]] s, etc. ''Las máquinas de ensamblaje no pueden crear componentes intermedios en cadena automáticamente como lo hace el jugador.''

Para mantener una producción continua, los ingredientes deben proporcionarse a través de un [[belt transport system/es|sistema de cintas transportadoras]] e [[Inserters/es|incertadores]]. Los objetos manufacturados también pueden ser extraídos por los insertadores y están disponibles para su uso posterior en cualquier otro lugar de la fábrica.

== Dificultad de las recetas ==

En el [[World generator/es|generador de mapas]], el jugador puede elegir entre recetas normales o caras (modo caro). Las recetas caras representan un reto mas allá del juego "vanilla" con recetas normales (modo normal) porque cambian algunos ratios comunes y tienen requerimientos de recursos mas elevados.

== Ver también ==
* [[Electric system/es|Sistema Eléctrico]]
* [[Assembling machine/es|Máquina de ensamblaje]]
* [[Furnace/es|Horno]]

User:LagExpress/test/es

2018-11-29T00:25:58Z

LagExpress: Crafting/es

{{Languages}}

The process of 'crafting' is to produce an end product off of input products using a recipe. The [[player]] or [[Assembling machine]]s can craft. Smelting is achieved by using [[Furnace]]s. Since smelting cannot be done by the player, it is impossible to craft some items directly from raw resources. Some crafting even beyond raw resources still requires an assembling machine.

In the beginning of the game, it is easy to make everything manually, but as the game advances manual crafting is less and less efficient of a way to create. Products that require liquids and a few others (such as engine units) cannot be manually crafted. This is to encourage automation.

== Logros ==
{{Achievement|lazy-bastard}}

== Creación manual ==

Manual crafting is the most basic form of crafting, it is done directly in the player's inventory. To manually craft an object, open the player's inventory (Default keybinding {{keybinding|e}}), and select an object to manually craft on the right. Left click for one, right click for five, and shift click to make as many as possible. If the image of the item is grayed out, ensure you have the materials necessary to craft the object. If you lack a resource, it will be shown highlighted in red text if you mouse-over the product. Materials that you don't have but you can craft will be highlighted in orange text, and will be chain-crafted to reach the product you selected. This is an advantage over automatic crafting using machines, which do not automatically create intermediate ingredients.

While manually crafting, there will be icons in the bottom left of the screen, which shows the current crafting operation. When an item is selected for crafting, the resources will be preemptively taken from the player's inventory. If that operation is then canceled, the items will be fully returned to the player.

To cancel a manual crafting operation from the queue at the bottom left of the screen, left click (to cancel one operation), right click (to cancel five operations), or shift-left click to cancel all crafts of that item. This is useful if you accidentally queue the wrong product, or too many of a product. All the materials taken to craft the item will be returned to your inventory. Manual crafting can be canceled at any time, but already-crafted intermediate products will not be uncrafted.

== Creación automatizada ==

Automated crafting is done outside of the player's inventory, allowing for multiple products to be produced at once, in synchronous harmony. This is where most crafting should take place.

Key structures in automated crafting are:
{| class="wikitable"
!colspan=2| Extraccion de recursos
|-
| {{Imagelink|Burner mining drill}} {{Imagelink|Electric mining drill}} || Extrae recursos [[Mining|mineros]].
|-
| {{Imagelink|Offshore pump}} || Extrae [[water|agua]] de los lagos.
|-
| {{imagelink|Pumpjack}} || Extrae [[crude oil|petroleo crudo]] de yacimientos petroleros.
|-
!colspan=2| Hornos
|-
| {{Imagelink|Stone furnace}} {{Imagelink|Steel furnace}} {{Imagelink|Electric furnace}} || Procesan los minerales en bruto a su estado metalico, mediante un proceso de fundición.
|-
!colspan=2| Producción
|-
| {{imagelink|Assembling machine 1}} || Can craft items that require up to 2 types of ingredients. Cannot handle fluid ingredients.
|-
| {{imagelink|Assembling machine 2}} || Can craft items that require up to 4 types of ingredients. Can handle recipes with fluid ingredients.
|-
| {{imagelink|Assembling machine 3}} || Can craft items that require up to 6 types of ingredients. Can handle recipes requiring fluid ingredients.
|-
| {{Imagelink|Oil refinery}} {{Imagelink|Chemical plant}} || Processes [[crude oil]] and other fluids.
|-
| {{imagelink|Centrifuge}} || Process [[uranium ore]] into more useful intermediate products.
|}

== Basic ==
As an introduction to crafting, let's craft some simple iron plates.

'''Task''': create [[Iron plate]]s.

Steps:
# Place a [[Burner mining drill]] onto an [[Iron ore]] resource field. This is a silvery patch that is fairly common.
# Place a [[Furnace]] directly in front of the output (press {{keybinding|Alt}} to show output arrow), so that the miner outputs the ore into the furnace, which can receive on any side.
# Fill both the miner and the furnace with [[Fuel]], such as coal or logs.
# Wait. After a few seconds, the first piece of [[Iron plate]] is smelted and available for collection. Either collect it manually, or pull it out with an [[Inserters|inserter]].

This entire process is commonly referred to as 'smelting'. [[Copper ore]] must also be smelted.

== Avanzado ==

Crafting of items can be automated. To automatically craft items, place a [[Assembling machine]], and select the recipe. Note that if the recipe is complicated enough, higher tiers of assembling machines may be necessary. Then, place all requested ingredients into the input slots, and the assembling machine should craft the item. Note that unlike manual crafting, each step of the craft requires another assembly machine. For example, crafting a [[lamp]] requires a machine to make [[copper cable]], a machine to make [[iron stick]]s, a machine to make [[electronic circuit]]s, etc. ''Assembly machines cannot automatically chain-craft like the player.''

To keep up continuous production ingredients must be provided via [[belt transport system|belts]] and [[Inserters]]. The manufactured items can also be extracted by [[Inserters]] and are then available for further usage elsewhere in the factory.

== Dificultad de las recetas ==

When [[World generator|generating a world]], the player can choose between normal and expensive recipes (expensive mode). The expensive recipes represent another challenge beyond the "vanilla" game with normal recipes (normal mode) because they change some common ratios and have higher resource requirements.

== History ==

{{history|0.15.0|
* Crafting now pauses when the results cannot fit into the player's inventory.}}

{{history|0.13.4|
* Surplus items are used for crafting further items, instead of being dropped into the inventory.}}

{{history|0.13.0|
* Crafting counts are recorded per force.}}

{{history|0.11.15|
* Order of inputs/outputs for fluid in machines is now constant.}}

{{history|0.11.9|
* Inventory now sorts properly when god mode crafting.}}

{{history|0.11.0|
* Event "on_player_crafted_item" is now called for every single finished item.}}

{{history|0.10.3|
* Crafting GUI now supports scrolling.}}

{{history|0.9.4|
* Recipes can now be hidden, so they don't appear in the player crafting screen.}}

{{history|0.9.2|
* Crafting GUI now resizes dynamically to fit the largest size.
* Only play crafting sound when final product is finished.}}

{{history|0.9.0|
* Updated/added sounds for crafting.}}

{{history|0.8.0|
* Unified crafting time, crafting time is now 1:1 with manual crafting.}}

{{history|0.5.0|
* Recipes categorized better.
* Recipes can now cost nothing but time.}}

{{history|0.4.0|
* Wider item selection screen.}}

{{history|0.2.10|
* Tool tip in technology preview now shows total raw.}}

{{history|0.2.9|
* Recipes are categorized.}}

{{history|0.2.8|
* Intermediate items in the crafting queue now show in a different color.
* Canceling crafting now cascades to all ingredients.}}

{{history|0.1.0|
* Introducido}}

== See also ==
* [[Electric system]]
* [[Assembling machine]]
* [[Furnace]]

Bulk inserter (research)/es

2018-11-28T11:06:48Z

LagExpress: Created page with "{{Languages}} {{:Infobox:Stack inserter (research)}} Los insertadores de stacks pueden mover más objetos al mismo tiempo dependiendo de su mejora. Algunas de las mejoras rel..."

{{Languages}}
{{:Infobox:Stack inserter (research)}}

Los insertadores de stacks pueden mover más objetos al mismo tiempo dependiendo de su mejora. Algunas de las mejoras relacionadas también aumentan la capacidad para los otros tipos de insertadores.

== Ver también ==
* [[Research/es|Investigación]]
* {{L|Technologies}}

{{TechNav}}

Main Page/es

2018-11-27T16:07:09Z

LagExpress: design consistency

{{Languages}}
{{DISPLAYTITLE:Wiki Oficial de Factorio|noerror}}__NOTOC__[[Image:Factorio-logo.png|center|link=http://factorio.com/]]


Bienvenidos a la wiki oficial de Factorio, la fuente oficial de documentación de Factorio™. 
{{NUMBEROFACTIVEUSERS}} editores activos (de {{NUMBEROFUSERS}} registrados) están actualmente manteniendo [[Special:Statistics|{{NUMBEROFARTICLES}} artículos]] y [[Special:ListFiles|{{NUMBEROFFILES}} imágenes]].


{| style="width: 100%; border-spacing: 8px;"
{{ContentCell|66%|
|{{:Factorio:About/es}}
}}
{{ContentCell|34%|[[File:Iron axe.png|link=]] [http://www.factorio.com/buy Obtén el juego]|{{:Main Page/Get the game‎/es}}
}}
|-
{{ContentCell|66%|[[File:Lab.png|link=]] [[News|Blog del desarrollador: Factorio Friday Facts]]|{{:News}}
}}
{{ContentCell|34%|[[File:Assembling machine 3.png|link=]] Últimas actualizaciones|{{:Main_Page/Latest_versions}}
}}
|}

==== El juego ====

{| style="width: 100%; border-spacing: 8px;"
{{ContentCell|33%|[[File:Transport belt.png|link=]] Principiantes | {{:Main_Page/Beginners/es}}
}}
{{ContentCell|33%|[[File:Fast transport belt.png|link=]] Avanzados | {{:Main_Page/Advanced/es}}
}}
{{ContentCell|34%|[[File:Express transport belt.png|link=]] Expertos | {{:Main_Page/Expert/es}}
}}
|}
{| style="width: 100%; border-spacing: 8px; margin-top: -8px;"
{{ContentCell|100%|Objetos y Recetas|{{Inventory}}
}}
|}

==== Información Adicional ====
{| style="width: 100%; border-spacing: 8px;"
{{ContentCell|33%|[[File:Processing unit.png|link=]] Nuevo contenido|{{:Main_Page/New_content/es}}
}}
{{ContentCell|33%|[[File:Questionmark.png|32px|link=]] Preguntas Frecuentes|{{:Main_Page/Frequently asked questions/es}}|
[[File:Repair pack.png|link=]] Contribuir a la wiki|{{:Main_Page/Contribute/es}}
}}
{{ContentCell|34%|[[File:Behemoth-spitter.png|link=]] Comunidad|{{:Main_Page/Community/es}}
}}
|}

__NOEDITSECTION__

{{C|Main}}

User:LagExpress

2018-11-27T15:11:36Z

LagExpress:

[https://wiki.factorio.com/User:LagExpress/Main_Page/es Main Page]

[https://wiki.factorio.com/User:LagExpress/Multiplayer/es Multijugador]

Portable solar panel/es

2018-11-27T11:09:34Z

LagExpress: Created page with "{{Languages}} {{:Infobox:Portable solar panel}} Los '''Paneles solares portátiles''' son las unidades generadoras de energía básicas para la {{L|Modular armor}}. Proporcio..."

{{Languages}}
{{:Infobox:Portable solar panel}}

Los '''Paneles solares portátiles''' son las unidades generadoras de energía básicas para la {{L|Modular armor}}. Proporcionan solo una pequeña cantidad de energía, y solo durante el día.

Los paneles solares portátiles se pueden utilizar para recargar lentamente el {{L|Energy shield}} fuera de combate, pero son casi inútiles para el {{L|Personal laser defense}} o el {{L|Exoskeleton}}, incluso con un gran número de {{L|Battery}}s.

Los paneles solares portátiles tienen un tamaño de 1x1 y por lo que se utilizan principalmente en la {{L|Modular armor}}, la cual dispone de una cuadrícula de 5x5 por lo que no puede almacenar eficientemente el mucho mas potente {{L|Portable fusion reactor}} de 4x4. (Podría almacenar uno, pero no quedaría espacio para que algo utilizara la energía).

Las armaduras más avanzadas casi siempre deberían hacer uso del {{L|Portable fusion reactor}} en su lugar.

== Ver también ==
* {{L|Modular armor}}
* {{L|Portable fusion reactor}}

{{CombatNav}}
{{C|Equipment}}

User:LagExpress/Multiplayer/es

2018-01-18T21:16:19Z

LagExpress:

{{Languages}}
{{DISPLAYTITLE:Multijugador|noerror}}
En adición a ser un juego para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo que múltiples jugadores cooperen y se ayuden entre sí, o trabajen contra el otro en JcJ. Esta página documenta cómo configurar una partida multijugador y cómo unirte a una. De forma predeterminada, las partidas multijugador ejecutan el escenario de [[Game modes and options/es|juego libre]] CO-OP donde todos los jugadores trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas de JcJ, están disponibles para su descarga en el foro de [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Mapas y Escenarios].

== Creando Una Partida Multijugador ==

Las partidas multijugador pueden ser alojadas en el cliente del juego mientras juegas o mediante un servidor dedicado. Las partidas multijugador pueden ser anunciadas en la red LAN asi como en la lista publica de partidas.

Usa el botón ''Multijugador'' del menú ''Jugar'' para empezar a jugar una partida multijugador, elige ''Nuevo juego'' o ''Cargar partida'' o ''Escenarios'' para alojar y jugar, o ''Buscar partidas públicas'' o ''Jugar en LAN'' para conectarte a una partida ya en marcha. El anfitrión también puede optar por no anunciar la partida en absoluto, en cuyo caso necesitarás la dirección IP del servidor (pública o accesible de otra manera); entonces puedes ''Conectar al servidor'' para unirte a la partida.

Notas y consejos:

* Todos los jugadores necesitan ''exactamente la misma'' version del juego y mods.
* Los servidores de factorio utilizan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuracion]].
* Factorio utiliza solamente el puerto UDP. Asegúrate de configurar correctamente la apertura de puertos en tu router. (El juego construye su propia capa de "entrega fiable" construida sobre UDP para hacer frente a la pérdida de paquetes y problemas de reordenación.)
** Asegúrese de que no haya ningún firewall o antivirus bloqueando los paquetes UDP.
* 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.

=== Servidor Dedicado/Headless ===

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)
* Saves the game on exit (and autosaves normally)

''Please note that there has been a slight change between 0.12, 0.13 and 0.14 in how --start-server (and others) interpret the given parameter. Version 0.12 expected --start-server to be followed by a save name, that was to be found in the saves directory. 0.13 instead expects --start-server to be followed by a path to a save file. I.e. if you did '''factorio --start-server foo''' in 0.12, you probably want to use '''factorio --start-server saves/foo.zip''' in 0.13.''

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>

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

2018-01-18T21:04:31Z

LagExpress:

[https://wiki.factorio.com/User:LagExpress/Multiplayer/es Multijugador]

User:LagExpress/Multiplayer/es

2018-01-16T21:08:09Z

LagExpress:

{{Languages}}
{{DISPLAYTITLE:Multijugador|noerror}}
En adición a ser un juego para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo que múltiples jugadores cooperen y se ayuden entre sí, o trabajen contra el otro en JcJ. Esta página documenta cómo configurar una partida multijugador y cómo unirte a una. De forma predeterminada, las partidas multijugador ejecutan el escenario de [[Game modes and options/es|juego libre]] CO-OP donde todos los jugadores trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas de JcJ, están disponibles para su descarga en el foro de [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Mapas y Escenarios].

== Creando Una Partida Multijugador ==

Las partidas multijugador pueden ser alojadas en el cliente del juego mientras juegas o mediante un servidor dedicado. Las partidas multijugador pueden ser anunciadas en la red LAN asi como en la lista publica de partidas.

Usa el botón ''Multijugador'' del menú ''Jugar'' para empezar a jugar una partida multijugador, elige ''Nuevo juego'' o ''Cargar partida'' o ''Escenarios'' para alojar y jugar, o ''Buscar partidas públicas'' o ''Jugar en LAN'' para conectarte a una partida ya en marcha. El anfitrión también puede optar por no anunciar la partida en absoluto, en cuyo caso necesitarás la dirección IP del servidor (pública o accesible de otra manera); entonces puedes ''Conectar al servidor'' para unirte a la partida.

Notas y consejos:

* Todos los jugadores necesitan ''exactamente la misma'' version del juego y mods.
* Los servidores de factorio utilizan el puerto '''34197'''. El puerto puede ser cambiado en el archivo de [[Application directory/es|configuracion]].
* 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)
* Saves the game on exit (and autosaves normally)

''Please note that there has been a slight change between 0.12, 0.13 and 0.14 in how --start-server (and others) interpret the given parameter. Version 0.12 expected --start-server to be followed by a save name, that was to be found in the saves directory. 0.13 instead expects --start-server to be followed by a path to a save file. I.e. if you did '''factorio --start-server foo''' in 0.12, you probably want to use '''factorio --start-server saves/foo.zip''' in 0.13.''

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>

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

Steel processing (research)/es

2018-01-16T20:08:55Z

LagExpress: Created page with "{{Languages}} {{DISPLAYTITLE:Procesamiento de acero (Investigación)|noerror}} {{:Infobox:Steel processing (research)}} '''Procesamiento de acero''' te permite procesar el ac..."

{{Languages}}
{{DISPLAYTITLE:Procesamiento de acero (Investigación)|noerror}}
{{:Infobox:Steel processing (research)}}

'''Procesamiento de acero''' te permite procesar el acero a partir de hierro, y permite la creación de elementos de acero básicos. Dado a la cantidad de opciones de investigaciones que desbloquea y lo fácil que es de obtener, esta sera una de las primeras tecnologías que el jugador investigue.

== Ver también ==
* [[Research/es|Investigación]]
* [[Technologies/es|Tecnologías]]

{{TechNav}}

Steel chest/es

2018-01-16T19:41:57Z

LagExpress: Created page with "{{Languages}} {{:Infobox:Steel chest}} El '''cofre de acero''' es el más grande de los tres tipos de cofres utilizados para el almacenamiento de artículos básicos. '''Ste..."

{{Languages}}
{{:Infobox:Steel chest}}
El '''cofre de acero''' es el más grande de los tres tipos de cofres utilizados para el almacenamiento de artículos básicos. '''[[Steel processing (research)/es|Procesamiento de acero]]''' debe ser investigado antes de poder construirlo. El cofre de acero, al igual que otros cofres, puede ser conectado a la [[circuit network/es|red de circuitos]] para proporcionar su contenido mediante la misma utilizando señales.

== Historia ==

{{history|0.13.0|
* El cofre de acero ahora se puede conectar a una [[circuit network/es|red de circuitos]]. }}

{{history|0.1.0|
* Introducido. }}

==Ver también==
* [[Storage/es|Almacenamiento]]
* [[Iron chest/es|Cofre de hierro]]

{{LogisticsNav}}
{{C|Storage}}

User:LagExpress

2018-01-16T00:20:03Z

LagExpress: Blanked the page

User:LagExpress/Multiplayer/es

2018-01-16T00:19:48Z

LagExpress:

{{Languages}}
{{DISPLAYTITLE:Multijugador|noerror}}
En adición a ser un juego para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo que múltiples jugadores cooperen y se ayuden entre sí, o trabajen contra el otro en JcJ. Esta página documenta cómo configurar una partida multijugador y cómo unirte a una. De forma predeterminada, las partidas multijugador ejecutan el escenario de [[Game modes and options/es|juego libre]] CO-OP donde todos los jugadores trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas de JcJ, están disponibles para su descarga en el foro de [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Mapas y Escenarios].

== Creando Una Partida Multijugador ==

Las partidas multijugador pueden ser alojadas en el cliente del juego mientras juegas o mediante un servidor dedicado. Las partidas multijugador pueden ser anunciadas en la red LAN asi como en la lista publica de partidas.

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)
* Saves the game on exit (and autosaves normally)

''Please note that there has been a slight change between 0.12, 0.13 and 0.14 in how --start-server (and others) interpret the given parameter. Version 0.12 expected --start-server to be followed by a save name, that was to be found in the saves directory. 0.13 instead expects --start-server to be followed by a path to a save file. I.e. if you did '''factorio --start-server foo''' in 0.12, you probably want to use '''factorio --start-server saves/foo.zip''' in 0.13.''

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>

=== 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:LagExpress/Multiplayer/es

2018-01-16T00:17:56Z

LagExpress: Created page with "multiplayer"

multiplayer

User:LagExpress

2018-01-15T23:46:18Z

LagExpress:

{{Languages}}
{{DISPLAYTITLE:Multijugador|noerror}}
En adición a ser un juego para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo que múltiples jugadores cooperen y se ayuden entre sí, o trabajen contra el otro en JcJ. Esta página documenta cómo configurar una partida multijugador y cómo unirte a una. De forma predeterminada, las partidas multijugador ejecutan el escenario de [[Game modes and options/es|juego libre]] CO-OP donde todos los jugadores trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas de JcJ, están disponibles para su descarga en el foro de [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Mapas y Escenarios].

== Creando Una Partida Multijugador ==

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)
* Saves the game on exit (and autosaves normally)

''Please note that there has been a slight change between 0.12, 0.13 and 0.14 in how --start-server (and others) interpret the given parameter. Version 0.12 expected --start-server to be followed by a save name, that was to be found in the saves directory. 0.13 instead expects --start-server to be followed by a path to a save file. I.e. if you did '''factorio --start-server foo''' in 0.12, you probably want to use '''factorio --start-server saves/foo.zip''' in 0.13.''

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>

=== 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}}
{{Translation|es}}

User:LagExpress

2018-01-15T23:45:02Z

LagExpress:

{{Languages}}
{{DISPLAYTITLE:Multijugador|noerror}}
En adición a ser un juego para un solo jugador, Factorio también ofrece un modo multijugador, permitiendo que múltiples jugadores cooperen y se ayuden entre sí, o trabajen contra el otro en JcJ. Esta página documenta cómo configurar una partida multijugador y cómo unirte a una. De forma predeterminada, las partidas multijugador ejecutan el escenario de [[Game modes and options/es|juego libre]] CO-OP donde todos los jugadores trabajan juntos para lanzar un cohete con un satélite al espacio. Otros escenarios, incluyendo mapas de JcJ, están disponibles para su descarga en el foro de [https://forums.factorio.com/viewforum.php?f=36&sid=93d1fbe9336d31d6bac60847b6c97985 Mapas y Escenarios].

== Creando Una Partida Multijugador ==

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)
* Saves the game on exit (and autosaves normally)

''Please note that there has been a slight change between 0.12, 0.13 and 0.14 in how --start-server (and others) interpret the given parameter. Version 0.12 expected --start-server to be followed by a save name, that was to be found in the saves directory. 0.13 instead expects --start-server to be followed by a path to a save file. I.e. if you did '''factorio --start-server foo''' in 0.12, you probably want to use '''factorio --start-server saves/foo.zip''' in 0.13.''

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>

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