Theme
Run a LAN server
This walkthrough sets up a WildM game server on one PC and joins it from others on the same network.
1. Start the server
sh
cd game-server
node server.jsNote the address it prints, for example http http://192.168.1.20:30120. The server picks its first private IPv4 address automatically; force another with WILDM_HOST:
powershell
$env:WILDM_HOST = "192.168.1.20"; node server.js2. Let the traffic in
On the server PC, allow Node.js on private networks when Windows Firewall asks, or create inbound rules for TCP 30120 (HTTP) and TCP 30121 (game). Check from another PC that http://192.168.1.20:30120/info opens in a browser and shows JSON.
3. Join
On each player PC, in the launcher search box:
text
> 192.168.1.20:30120and press Enter. Use the HTTP port, not the game port.
4. Optional: appear in the list
If the players' launchers point to a master server you also run (or that is reachable), register the server on the Portal and add the key:
powershell
$env:WILDM_SV_KEY = "wfx_…"; node server.jsThe console should print master : annonce acceptée, serveur visible dans la liste WFX.re. The list entry will carry the LAN address, which only works for players on the same network.
Checklist when it does not work
| Symptom | Check |
|---|---|
| Serveur injoignable | Server running? Firewall rule for 30120? Correct IP? |
| Stuck after download, pas connecté au serveur de jeu | Firewall rule for 30121 |
Serveur plein in wildm_net.log | Raise maxPlayers in server.json |
| Not in the list | svKey / WILDM_SV_KEY set and accepted? Launchers using the same master URL (Settings → Network)? |