Your own 7 Days to Die server is worthwhile if you want to control Blood Moon, loot, difficulty, and admin rights. At game-serverhosting, you rent a paid multi-game server with technical control, support, and traceable operating processes instead of running your co-op world on a private computer with changing availability.
Requirements
Before setting up the server, you should define three things: how many players will join regularly, whether the server should run publicly or privately, and how tough the survival rules should be. In the starting setup, at least 4 GB RAM is intended for 4-8 players. Still, do not set MaxPlayers higher than necessary because unused reserves do not guarantee a better player experience.
The official technical basis for configuration is the dedicated server documentation from The Fun Pimps: documentation at 7daystodie.fandom.com. Use it as the primary source for server parameters and check during version changes whether individual values have been renamed or changed. This guide is written as a practical setup for 2026 without claiming specific performance measurements.
If you are also planning other survival or co-op servers, the Valheim Server Co-op Guide 2026 and the Project Zomboid Multiplayer Guide will also help because they explain similar decisions around slots, world size, admin access, and private groups.
Rent a 7 Days to Die Server
Order a Server
- Go to game-serverhosting
- Choose at least 4 GB RAM (for 4-8 players)
- The server is set up automatically
After provisioning, you should first check whether the server starts cleanly and is reachable in the server list or via direct connection. Only after that is it worth making extensive configuration changes. This makes it easier later to see whether a problem comes from the base installation or from a changed setting.
Important Settings in serverconfig.xml
The central file is serverconfig.xml. Only change it while the server is stopped, or use the intended management interface of your hosting. After each change, the server usually needs a restart so the values are loaded reliably.
<property name="ServerName" value="My 7D2D Server"/>
<property name="ServerPassword" value="secret"/>
<property name="MaxPlayers" value="8"/>
<property name="GameDifficulty" value="3"/>
<property name="DayNightLength" value="60"/>
<property name="LootAbundance" value="150"/>
<property name="ZombiesRun" value="1"/>
<property name="BloodMoonFrequency" value="7"/>
<property name="AirDropFrequency" value="72"/>
ServerName should be unique so your teammates can find the server again. ServerPassword is recommended for private groups. MaxPlayers limits simultaneous players. GameDifficulty, LootAbundance, ZombiesRun, and BloodMoonFrequency strongly define how challenging the world feels. Do not change everything at once: adjust basic values first, play a few in-game days, and then fine-tune further.
Configure Blood Moon
Blood Moon is the most important rhythm driver for many 7 Days to Die servers. Horde nights that happen too often can overwhelm new groups; hordes that happen too rarely take pressure out of progression. The following values from the starting setup remain unchanged and are suitable as a starting point that you adapt to your group.
| Setting | Default | Recommended |
|---|---|---|
| BloodMoonFrequency | 7 | 7 (every 7 days) |
| BloodMoonRange | 0 | 2 (day 5-9) |
| BloodMoonEnemyCount | 8 | 8-16 |
BloodMoonFrequency defines the base interval. With BloodMoonRange, the exact day becomes less predictable. BloodMoonEnemyCount affects how many enemies can become relevant at the same time. Increase this value carefully, especially if players still have little equipment, weaker bases, or different experience levels.
Zombie Settings
Zombie behavior determines whether your server emphasizes relaxed building, survival roleplay, or frantic combat. For mixed groups, “running at night” is often an easy-to-understand compromise: during the day there is time to gather, at night the pressure rises.
| ZombiesRun | Behavior |
|---|---|
| 0 | Always walk |
| 1 | Run at night |
| 2 | Always run |
| 3 | Never walk (easy) |
If new players are joining, start conservatively. You can increase difficulty, loot, and zombie behavior later once the group understands tools, weapons, healing, and base defense.
Admin Rights and Commands
Admin rights are practical, but sensitive. Grant them only to people who handle teleporting, item granting, and time control responsibly. Document internally who is an admin so changes to the server remain traceable.
admin add <name> 0 # Admin rights (Level 0 = highest)
give <name> <item> <menge> # Give items
teleportplayer <name> <x> <y> <z> # Teleport
settime day # Make it daytime
killall # Kill all zombies
Test admin commands first in a non-critical situation. A wrong teleport or careless time change can disrupt ongoing missions, Blood Moon preparation, or group progress.
Performance Tips
These notes are not guaranteed performance values, but conservative adjustment points from the existing setup:
- WorldGenSize: 6144 instead of 8192 for better performance
- MaxPlayers: No more than the actual player count
- View Distance: Not changeable server-side, but map size helps
You should also consider mods, very large worlds, and high simultaneous player counts separately. If lags appear after a change, step back gradually: first disable mods, then check player limit and world size, then evaluate logs.
Check the Result
After the restart, connect to the server and check password, server name, slot limit, and day length. Ask a second player to join as well so you are not only testing the local client. Then open the logs and check whether serverconfig.xml was loaded without errors. If admin rights were set, test a harmless command before making interventions in the world.
Troubleshooting
If the server is not visible, first try the direct connection via address and port. Then check whether the server has fully started and whether a password was set. If settings do not take effect, the cause is often a restart problem, an incorrectly edited file, or an XML syntax error. With XML, missing quotation marks or a damaged line are enough for values not to be processed as expected.
If players report lag, do not change several parameters immediately. First lower WorldGenSize for new worlds, compare the actual player count against MaxPlayers, and observe whether the problems occur especially during Blood Moon, while exploring new areas, or after mod changes.
Verification, Limits, and a Safe Rollback
The guide “Rent a 7 Days to Die Server – Multiplayer Guide 2026” applies to the server type described in the article and the version status visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources can differ after updates. Therefore, do not transfer any values unchecked to another game, loader, or server version.
Before changing the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and check it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Stop and Rollback |
|---|---|---|
| Server start | The server reaches the ready-to-run state without a new error message. | If startup errors occur, revert the change and restore the latest backup. |
| Connection test | A test account can connect through the address shown in the panel. | If version or connection errors occur, recheck version, port, and access rules. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore the backed-up files. |
A successful individual test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.
FAQ
How Much RAM Do I Need for a 7 Days to Die Server?
In the existing setup, at least 4 GB RAM is intended for 4-8 players. Larger worlds, mods, or more simultaneous players can create additional demand, without any exact general value being promised seriously.
Should My Server Have a Password?
Yes for private groups. Set ServerPassword if only friends or a fixed community should join. Public servers, by contrast, need clear rules, active administration, and regular checks.
Which Blood Moon Setting Makes Sense for the Start?
BloodMoonFrequency 7 is an understandable starting point because the horde can be planned every seven days. With BloodMoonRange 2, the exact day becomes less predictable without completely dissolving the rhythm.
Why Do My Changes to serverconfig.xml Not Apply?
Most of the time, the server was not restarted, the wrong file was edited, or the XML structure was damaged. Stop the server, check the file for clean tags and quotation marks, save it, and then restart.
Can I Change Difficulty and Zombie Behavior Later?
Yes, many server values can be adjusted afterward. Change them gradually and inform your players beforehand, especially if Blood Moon, loot, or zombie speed are affected.