IW4x Server Types: Match, Party, and LAN Servers

IW4x Server Types: Match, Party, and LAN Servers

IW4x supports three server operating modes controlled by two cvars: sv_lanonly and party_enable. Understanding the difference helps you choose the right configuration for your use case and avoids common setup mistakes.

The Three Modes at a Glance

Match Server (Recommended)

iw4x.exe -dedicated +set party_enable "0" +set sv_lanonly "0" +set net_port "28960" +exec server.cfg +map_rotate

A match server is the traditional dedicated server model: it runs a continuous map rotation, players join and leave freely, and the server is listed publicly in the IW4x server browser. This is how virtually all public IW4x servers operate.

How it works:

• Server starts and immediately begins the map rotation from sv_maprotation
• Players connect directly via the server browser or connect [ip]:28960
• There's no "lobby" phase — players drop into the current match in progress
• When the match ends, the server loads the next map and continues

Best for: Public servers, all permanent dedicated servers, everything except LAN events.

LAN Server

iw4x.exe -dedicated +set party_enable "0" +set sv_lanonly "1" +set net_port "28960" +exec server.cfg +map_rotate

A LAN server is identical to a match server except sv_lanonly "1" tells IW4x not to register the server with the AlterWare server browser. The server is only discoverable on the local network.

How it works:

• Same behavior as a match server — continuous map rotation, players join in-progress
• Does not appear in the public server browser
• Players on the same LAN can discover it via the local server browser tab in IW4x, or connect directly by IP
• The server still needs the game port to be accessible on the local network

Best for: LAN parties, private events, internal testing, servers you don't want publicly listed.

Note: Even with sv_lanonly "1", the server is still accessible from the internet if the firewall is open. sv_lanonly only controls browser visibility, not actual network accessibility. If you want to truly restrict connections to the local network, you need firewall rules that block connections from outside your subnet.

Party Server (Avoid for Public Hosting)

iw4x.exe -dedicated +set party_enable "1" +set sv_lanonly "0" +set net_port "28960" +exec server.cfg +map_rotate

Party mode attempts to replicate the original MW2 matchmaking lobby experience — players gather in a pre-game lobby, a host starts the match, and the group stays together between rounds.

The problem: Party mode in IW4x is poorly implemented and frequently causes issues:

• The lobby state management is unstable and prone to softlocks
• Players often can't ready up or the match never starts
• Rotation after a match can fail, leaving players in a broken state
• party_enable "1" interacts poorly with map_rotate
• The system was designed for console peer-to-peer matchmaking, not persistent dedicated servers

When you might use it: Party mode is occasionally useful for very specific use cases like private tournaments where a coordinated group wants a lobby-style experience and can tolerate its instability. For any public-facing server, use match mode.

Changing Server Type at Runtime

You can change sv_lanonly at runtime via RCON to temporarily hide or show a server in the browser:

rcon set sv_lanonly "1"   // Hide from browser (takes effect immediately)
rcon set sv_lanonly "0"   // Show in browser again

Note that party_enable changes require a full server restart to take effect reliably.

Multiple Instances on One Machine

You can run a public match server and a private LAN server simultaneously by using different ports:

// Server 1 — Public TDM, port 28960
iw4x.exe -dedicated +set party_enable "0" +set sv_lanonly "0" +set net_port "28960" +exec server.cfg +map_rotate

// Server 2 — Private LAN, port 28961
iw4x.exe -dedicated +set party_enable "0" +set sv_lanonly "1" +set net_port "28961" +exec server2.cfg +map_rotate

Each instance needs its own server.cfg and should write logs to a different path to avoid conflicts.

Summary Recommendation

For virtually all use cases: run a match server with party_enable "0" and sv_lanonly "0". This is the stable, well-tested mode that the IW4x ecosystem is built around. Only use sv_lanonly "1" when you intentionally want to hide the server from the public browser, and avoid party_enable "1" unless you have a very specific reason and accept its instability.

Related

• Installing Your IW4x Dedicated Server on Windows
• IW4x server.cfg Complete Configuration Guide
• Host an IW4x (MW2) server with DustBowl.Games