web stats

Private Server Setup Questions

Tags: setup, private-server, networking

A private server for friends should prioritize security, predictable performance, and easy access. Here is a compact plan to get it right the first time.

Network and access

  • Forward ports 26900 - 26902 UDP/TCP to the host machine (or use a VPN to avoid port forwarding entirely).
  • Set a strong password and disable public listing by keeping ServerDisabledNetworkProtocols empty and ServerVisibility set to Friends.
  • Add SteamIDs to serveradmin.xml for admins and consider a whitelist for all allowed players.

World and pacing

  • Choose an 8 - 10k map for 4 - 8 players; larger worlds grow save size fast.
  • Adjust DayNightLength and BloodMoonFrequency to match how often the group plays. On V3.0 and later both are sandbox options, not serverconfig.xml properties: set them with a SandboxCode or with setgamepref.
  • Keep MaxSpawnedZombies modest for stability during horde nights.

Operations

  • Use a scheduled restart once daily with a short in-game warning.
  • Back up Saves/ and serverconfig.xml before any mod or version change.
  • Keep telnet enabled but restricted to localhost or VPN; never expose it directly to the public internet.

Quality-of-life

  • Enable a shared storage region near spawn and pin rules to the in-game MOTD.
  • Decide early on drop rules (DropOnDeath, DropOnQuit) to avoid disagreements mid-season.