---
title: "7 Days to Die Dedicated Server (1.0): serverconfig.xml, RWG & RAM"
description: "Set up a 7 Days to Die dedicated server: Navezgane vs RWG in serverconfig.xml, ports 26900-26902, RAM sizing for Blood Moon hordes and hourly cost."
url: https://tickserv.com/guides/7-days-to-die-dedicated-server
site: "TickServ (https://tickserv.com)"
lang: en
published: 2026-10-25
games: [7-days-to-die]
---
# 7 Days to Die Dedicated Server (1.0): serverconfig.xml, RWG & RAM

Surviving the horde alongside friends in 7 Days to Die 1.0 without tethering progress to a host PC requires an independent dedicated server. You can deploy a tailored [7 Days to Die dedicated server](https://tickserv.com/games/7-days-to-die) with hourly billing and no recurring subscription.

## Navezgane vs Random World Generation (RWG) in serverconfig.xml

The dedicated server listens on TCP port **26900** and UDP ports **26900 through 26902**, supporting 1 to 16 players (8 by default). All gameplay rules and world options are defined inside the central `serverconfig.xml` file.

Your primary architectural decision is the world type (`GameWorld`):

- **Navezgane**: the classic handcrafted map designed by The Fun Pimps. Cities and points of interest are fixed, and the server boots almost instantly on initial setup.
- **RWG (Random World Generation)**: procedural world generation governed by `WorldGenSeed` and `WorldGenSize` (6144, 8192, or 10240).

Generating a large 8k or 10k RWG map during initial setup requires several minutes of intensive CPU processing before opening ports to players. Once generated and cached, subsequent startups become quick and lightweight.

## Blood Moon hordes, recommended RAM, and stopping the world clock

For small groups exploring Navezgane during initial game weeks, **8 GB** (€0.06/h in Eco) provides solid baseline performance.

However, the voxel engine in 7 Days to Die places heavy demands on CPU and system memory under two distinct scenarios:

1. Large procedural RWG maps measuring 8192 blocks or wider.
2. Day 7 Blood Moon events (`BloodMoonFrequency`, `BloodMoonEnemyCount`), where dozens of zombies run simultaneous pathfinding calculations while structural collapse physics trigger on reinforced base defenses.

When hosting 6 to 8 survivors or facing dense hordes, step up to **16 GB** (€0.12/h in Eco, €0.24/h in Dedicated). A critical benefit of hourly hosting is that stopping the server (€0 when stopped) completely freezes the world clock. Time does not elapse when players are offline, preventing surprise Blood Moon triggers while nobody is connected.

## Essential settings (ServerPassword, EACEnabled) and admin console commands

A few key properties in `serverconfig.xml` ensure server stability and base safety:

- `ServerPassword`: sets a private password to prevent unauthorized players from joining.
- `BedrollDeadZoneSize` and `LandClaimSize`: expand the protected perimeter around player bases to block zombie spawns and block modifications.
- `EACEnabled`: keep set to `true` by default. Only set this to `false` if your group installs mods requiring client-side binary modifications.

When issuing administrative commands via the in-game console, remember to enclose player names in quotation marks: use `kick "<player_name>"` to disconnect a user, or `ban add "<player_name>" 100 years "Reason"` for permanent bans.