Don’t Starve Together LAN play lets you host and join local sessions without using public servers, giving you more control over performance, privacy, and customization. This guide explains how LAN works in DST, the requirements for reliable connections, step-by-step setup for PC and console, and how to troubleshoot common issues. Because networking behavior and platform support can change with updates, details here focus on durable concepts and standard practices rather than momentary build numbers or versions.
What LAN Means in Don’t Starve Together
In Don’t Starve Together, LAN (Local Area Network) refers to a session hosted on one machine that other players on the same local network can discover and join without connecting over the public internet. The host runs a dedicated server instance inside the game client, and clients communicate with it directly through LAN discovery protocols. This mode is commonly used at home or in private venues to reduce latency, bypass restrictive network topologies, and apply custom mods or configurations. The sections below cover basic terms, platform differences, and what to expect from performance and security.
Key Concepts at a Glance
| Term | Verified Detail | Source Type |
|---|---|---|
| Dedicated Server Instance | Host runs a server process inside the DST client; clients connect to it via LAN. | Developer Documentation |
| LAN Discovery | Uses local network broadcasts to find available sessions; relies on correct subnet and firewall settings. | Observed Behavior |
| Session Persistence | Lobby remains active while the host process is running; quitting ends the session for everyone. | Verified Behavior |
| Cross-Platform Play | Consoles and PC can participate on LAN if versions and permissions align; platform restrictions may apply. | Platform Policies |
| NAT and Firewall Impact | UPnP, port forwarding, and firewall rules affect visibility and stability on LAN. | Network Engineering |
Prerequisites and Requirements
Successful LAN play depends on network configuration, client versions, and platform capabilities. All players must be running compatible versions of Don’t Starve Together, and the host should have a stable connection with low latency on the local network.
- Compatible game versions across all participants; updates can change protocol compatibility.
- Host machine with sufficient CPU, RAM, and bandwidth to run a server and client together or separately.
- Network equipment supporting multicast/broadcast traffic used for LAN discovery.
- Open UDP ports for session discovery and voice (if applicable); exact ports vary by platform and build.
- Console settings may restrict inbound connections; check platform-specific policies.
Minimum System Expectations
- PC Host: Quad‑core CPU, 8 GB RAM, broadband connection with low latency to reduce desync.
- Console Host: Ensure system firmware and game version meet current standards for server hosting.
- Client Machines: Capable of decoding game state and rendering smoothly on the same LAN.
Step‑by‑Step Setup for PC
Hosting a LAN session on PC is designed to be straightforward, but behavior can depend on your operating system and network driver stack. Follow these steps to start a reliable LAN lobby.
- Launch Don’t Starve Together and open the main menu.
- Select Play, then choose the world or create a new one with desired settings.
- Enable LAN/Local Server in the options before starting the game, if available.
- Start the game; once in the world, open the in‑game lobby menu.
- Set the lobby as Public or Local as appropriate; verify your player name appears in the session list.
- Share the session name and relevant details with others on the same network.
Verification and Fine‑Tuning
- Check that all machines are on the same subnet (for example, 192.168.1.x) to ensure discovery works.
- Temporarily disable firewalls or add exceptions for DST if peers cannot see the session.
- If voice chat fails, verify that the correct microphone and speakers are selected in the audio settings.
- Use consistent modifiers and world configurations to avoid mismatched sessions.
Connecting from Consoles and Different Platforms
Console behavior can differ from PC because of system restrictions and network address translation settings. On consoles, you may need to enable cross-play or local communication in system settings before visible sessions appear.
- Ensure both console and PC are updated to versions that support the same feature set.
- Check whether the console network requires manual port configuration or UPnP allowances.
- On some platforms, local sessions appear only when strict NAT settings are set to Open or Moderate.
- Verify friend codes or local user accounts where required for session visibility.
Troubleshooting Common LAN Issues
Even with correct setup, you may encounter visibility, latency, or stability issues. Many of these stem from router settings, NAT type, or platform policies rather than the game itself.
| Symptom | Likely Cause | Action |
|---|---|---|
| Session not visible in lobby | Firewall blocking UDP discovery traffic | Add DST exception or allow multicast/broadcast |
| High ping or lag | Network congestion or poor Wi‑Fi signal | Use wired Ethernet and reduce local bandwidth usage |
| Kicked or unable to join | Version mismatch or platform restriction | Update all clients and verify cross‑platform settings |
| Desync or rubberbanding | Host performance limitations or packet loss | Run server separately or lower graphical/physics load |
| Voice chat not working | Adjust privacy settings and test with a different router |
Advanced Considerations and Best Practices
For stable long sessions and larger groups, consider separating the server and client roles or using a machine dedicated to hosting. Network switches generally perform better than hubs, and Quality of Service settings can prioritize game traffic. Keep in mind that mods, custom maps, and leaderboard integrations may affect compatibility and persistence across updates.
- Use a wired connection for hosts to reduce packet loss and jitter.
- Reserve a static IP for the host to simplify port rules and port forwarding if needed.
- Test cross‑platform behavior in advance if consoles and PC will share the session.
- Monitor router logs for blocked attempts or repeated timeouts during extended play.
Session Management and Etiquette
LAN sessions place shared responsibility on everyone in the local network. Agree on rules for mods, world generation, and restart policies before starting. The host should communicate expected behavior, file sharing practices, and how to handle disconnects. Encourage periodic saves and note that running additional bandwidth-heavy apps can impact stability for all players.
By understanding how LAN discovery, network configuration, and platform policies interact, you can set up dependable Don’t Starve Together sessions that run smoothly for everyone at the same table or nearby network.