Multiplayer Guide: How to Host, Join & Run Servers
Multiplayer in Mindustry covers the ways players connect and play together, the server types and hosting options, basic security and networking considerations, and common multiplayer game modes and map conventions. This page summarizes practical steps and recommendations for running or joining multiplayer games.
Overview
Multiplayer allows cross-platform play between PC, Android, and iOS clients as long as all clients run the same game version. Multiplayer modes include Survival, Attack, PvP, and Sandbox; servers can host campaign-like maps with multiple cores or custom PvP maps designed specifically for player combat.
Server types and when to use them
Local (in-game) LAN / Steam servers
- Launched from the game UI via "Start Game" → "Open Server" (or "Host" in the pause menu).
- Best for quick sessions with a few friends on the same local network (same Wi‑Fi or hotspot).
- The host must keep the game running; when the host closes the game the server stops.
- Clients on the same LAN will typically see the server in the in-game server list automatically.
Dedicated (headless) servers
- Standalone Java JAR applications intended to run on a separate machine (Linux or Windows recommended).
- Suitable for public or persistent servers and for supporting many players or long uptimes.
- Require installing at least JRE/JDK 8 (or newer where supported), placing the server JAR on the host, and launching with java -jar server.jar (or server-release.jar).
- Provide administrative commands and can be modified/configured for custom behavior.
- If the server will be accessible from the internet, port forwarding or cloud hosting is required.
LAN vs Dedicated: use LAN for casual local games; use a dedicated server for persistent, public, or higher‑load hosting.
Connecting: IPs, ports, and NAT
- Local connections: join via the in-game "Join Game" UI; LAN hosts normally appear automatically.
- Remote connections: clients must know the host's public IP address and port to join a non-LAN server. Hosts must either:
- Configure port forwarding on their router for the server port, or
- Use a VPN or tunneling service (e.g., Hamachi) if port forwarding is not available, or
- Host on a cloud provider (recommended for public servers).
- Mindustry uses both TCP and UDP; allow the server port through the host machine's firewall. Common documentation recommends allowing port 6567 for TCP and UDP when using Windows Firewall.
- Never publish your personal public IP widely; exposing it risks DoS and other attacks. Use DNS, a domain, a reverse proxy, or cloud hosting to mask your IP for public servers.
Hosting basics and common commands
- For in‑client hosting: pick a map and gamemode (Survival, Attack, PvP, Sandbox), start the server from the pause menu, and invite players on the same network or share your IP if you port‑forwarded.
- For dedicated servers:
- Place the server JAR on the host machine, open a terminal/command prompt, cd to the JAR directory, and run java -jar server.jar (or server-release.jar).
- Use the server console and built‑in help command to learn admin commands.
- Use host
[mode] (or the server’s equivalent command) to load a map and gamemode. - Configure firewall rules to allow the server port if necessary.
Multiplayer gamemodes and map types
- Survival: defend cores and survive waves.
- Attack: assault enemy bases (used in campaign-like maps).
- PvP: player-versus-player combat, often using specially designed PvP maps.
- Sandbox: private play/testing environment with freer building rules.
PvP maps and conventions:
- PvP maps (often abbreviated P or PVP) are designed specifically for player combat and may lack campaign features like enemy spawn cores.
- Common PvP map subtypes:
- Formula maps: symmetrical, tidy terrain and mineral placements; often include a protection time (commonly 600s on many maps).
- War‑wall maps: neutral turrets or strong defenses split bases.
- Rank maps: many basic resource nodes and extra cores; sometimes have no protection time.
- HEX maps: procedurally generated hex-based maps; each hex can represent a team.
- Notable named map styles include variants colloquially called "飙车", "熔岩", "赤潮", etc., which are popular in community rotations.
- PvP strategies include fast-tech rushes (e.g., rushing overdrive-related tech), use of air units, and advanced tactics like manually controlling units and logic to boost projectile reach or speed.
Cross-platform play and versioning
- Mindustry supports cross-platform multiplayer between PC, Android, and iOS clients.
- All clients must run the same game version to connect; version mismatch prevents joining.
- Keep server and clients updated to the same release to avoid compatibility issues.
Practical tips and security
- Use LAN for small friend groups to avoid port forwarding and public exposure.
- For persistent/public servers, prefer a dedicated machine or cloud host to ensure uptime and performance.
- Use strong admin passwords and restrict who can access admin commands.
- Mask or avoid sharing your home public IP; use DNS, domain names, or cloud hosting when possible.
- If you must port-forward, follow router-specific guides and only forward the ports required for the server.
- Allow the server port through the host OS firewall (Windows users often need to add firewall rules manually).
Common troubleshooting
- Server not visible on LAN: ensure host and clients are on the same LAN, check firewall, and verify the host opened an in-game server.
- Remote join fails: check that port forwarding is correctly configured, the public IP is correct, and firewall rules permit the server port (both TCP and UDP).
- Version mismatch errors: update server or client so all are on the same build.
- Cross-platform issues: confirm all devices use the same game release channel (stable, beta, or custom builds).
This guide covers the essentials for connecting, hosting, and running multiplayer in Mindustry. Configure hosting to your needs—LAN for quick games, dedicated servers for persistent or public play—and follow basic network security practices when exposing a server to the internet.