Help Center & FAQ

Symptoms: Player slots drop to eight, EAC switches back on, or console players say modified files were detected.

That is crossplay's rulebook rather than a fault. Console players can join only when the server has crossplay on, 8 players or fewer, EAC on and EOS sanctions not ignored, so the panel sets those for you whenever you save with crossplay on. Consoles also need a public server without custom mods, on plan M or higher. Remove the mods, save, and use Console players can't find it? Check why in the Connect block on Server info to see what is still missing.

Symptoms: “Client failed to authorize,” “server requires client mods,” “invalid password,” or “object not set.”

Most connect errors are a version or mod mismatch. The Version tile on Server info shows what the server runs; players must be on the same version and branch (stable or experimental). To change the server's version, use the Game version card on Server info. If the server runs mods, every player needs the same mods installed. For “invalid password”, the Connect block on Server info shows the join password.

Symptoms: Xbox or PlayStation players don’t see the server in the in-game browser.

Consoles find a server by searching its exact name, and only when it meets crossplay's rules (see the first question). Open Server info, Connect, Console players can't find it? Check why: it checks each requirement on your server and links to the setting that fails. Console players must also be on the same game version as the server.

Symptoms: Players are rejected instantly even after restarts.

Rule out a version or mod mismatch first (see the connect errors question). If players are still dropped right after joining, open a ticket with the time it happened and the player's name, so we can find it in the server log.

Symptoms: The update does not seem to happen, or you cannot reach the new experimental build.

Open Server info, Game version. Update within current version downloads the newest build of your branch and keeps your world, mods and settings; the console shows the download and the server starts again on its own when it finishes. To move between stable and experimental, use the branch switch in the same card (plans M, L and XL). A branch switch can leave an existing save unloadable, so download a backup from Files & Mods first.

Symptoms: You want to move a server to V3.x, or your settings behave differently after updating.

V3.0 “Dead Hot Summer” (stable since June 29, 2026) moved 30 gameplay settings out of serverconfig.xml into a single SandboxCode: set difficulty, loot and rules with the Sandbox options in Configure, not by editing the XML. The current stable is V3.2 (since August 26, 2026) and V3.3 is on the experimental branch. Back up before you update. If the server will not boot afterwards, the Health tab and, on plans M, L and XL, the Doctor can diagnose it. What changed in 3.0: /3.0.

Symptoms: The server runs the new build, but an embedded banner shows the old one.

The banner reads the version from your running server and refreshes within a minute. Forums and Discord keep their own copy of embedded images for longer, so an old one can stay there for a while. The Version tile on Server info always shows what the server runs now.

Symptoms: Worlds revert to older days or you’re unsure which backup to keep.

We keep day-1 and day-2 backups of your server, and Backups/Fixer in Server management restores a backup, selected regions or player data. Keep your own copy too: Files & Mods lists a world.zip for each world. Download it before updates, mod installs or a world change.

Symptoms: The console logs “Attempted to read past the end of the stream” or the world stalls around 99%.

A region file of the save is corrupt, usually because the server was interrupted mid-save. Server info names the affected region. Use Backups/Fixer to restore that region from a day-1 or day-2 backup, or reset it so the game regenerates it (anything built there is lost). Full walkthrough: corrupted region files.

Symptoms: The upload stops with a message about the zip, or nothing new appears.

The uploader checks the zip before it touches your server and says what is wrong. It accepts the world folder from GeneratedWorlds (with dtm.raw, map_info.xml, biomes.png, prefabs.xml and spawnpoints.xml), the save folder from Saves (for example Navezgane/MyGame, with its Region folder), or both side by side. Zip the folder itself rather than the files inside it, one world per zip. A world larger than your plan runs is refused (see below).

Symptoms: You built a map locally and want it live on the server.

On Windows the game keeps worlds in %APPDATA%\7DaysToDie\GeneratedWorlds and saves in %APPDATA%\7DaysToDie\Saves. Zip the world folder (with its save folder if you want your progress too), upload it in Files & Mods, Upload a save (world), then activate it. Uploads are available on plans M, L and XL.

Symptoms: The world size list stops at your plan's size, or a larger world will not upload.

Each plan runs worlds up to a set size: 6K on S, 10K on M, 12K on L and 16K on XL. That covers worlds you generate and worlds you upload: the uploader refuses a larger world and names the plan that runs it. For a bigger world, upgrade first (Upgrade Plan on My Servers), then generate or upload it.

Symptoms: The upload option is missing on an S plan server.

Uploads start at plan M. Use Upgrade Plan on My Servers: once paid, your server moves to the new plan with its world, and the old plan is closed for you. Then upload the save in Files & Mods.

Symptoms: Darkness Falls or War3zuk installs stall, or the console warns about missing ModInfo files.

Use the one-click packs in Configure, Distributions & ModPacks; the list shows which packs your plan offers. Installing one reinstalls the server, which wipes the world and settings, so download a backup first. Every player needs the same pack installed. Overhaul packs run with EAC off, so console crossplay is not possible with them.

Symptoms: Clients see “Unexpected data received… server requires the client to install mods” when joining a War3zuk world.

The client's mods do not match the server's. War3zuk must be identical everywhere: our one-click War3zuk runs on 2.6 (plans L and XL), every player needs that same War3zuk build, and a manual install needs everything the pack ships, including its Data/Prefabs files, not only Mods. Restart the server and the clients after changing mods. War3zuk is heavy; on smaller plans a growing world tends to crash.

Symptoms: You uploaded a mod but it is not in the Mods list.

Refresh the Mods page first. If it is still missing, check that the zip holds the mod folder itself (the folder with ModInfo.xml) and fits your plan's mod limit, or upload the folder over FTP into sdtd/bin/Mods and restart.

Symptoms: Modlets refuse to load citing Harmony errors.

Harmony is the library most code mods load through, and the game ships it: every server has it in Mods/0_TFP_Harmony. Don't delete or replace that folder. A modlet that reports Harmony errors was usually built for another game version; use a release made for the version your server runs.

Symptoms: Wasteland is missing from the ModPack list and the panel uploader rejects the archive.

Wasteland is not in the one-click list. Download it from its author, extract it locally and check the folder structure, then upload the mod folders over FTP (plans M, L and XL; host and login are on your server's Details page) into sdtd/bin/Mods. Restart and check the console for errors.

Symptoms: Botman fails to connect or rewrites files unexpectedly.

Botman and similar tools aren’t supported on our managed servers. Use the panel, Allocs Server Fixes or CSMM instead.

Symptoms: FileZilla reports “connection refused” or keeps asking for credentials.

FTP is available on plans M, L and XL. It is plain FTP (not SFTP) on port 2121; copy the host, user and password from your server's Details page. Walkthrough with screenshots: FTP access.

Symptoms: Unsure how to upload generated worlds or large mod folders outside the panel.

For worlds, use the uploader in Files & Mods: it checks the zip and sets the world up for you. FTP suits large mod folders: connect to your server's host on port 2121 with the Details page login, upload the mod folders into sdtd/bin/Mods, then restart.

Symptoms: You want to change a setting by editing the file directly.

Change settings in Configure instead: the panel writes serverconfig.xml every time you save settings there, so edits made over FTP are replaced on the next save. For a setting Configure does not show, open a ticket.

Symptoms: The panel lacks buttons for your layout or support asks about your folder structure.

For moving whole folders: large mod packs, downloading a folder for support, or checking what is on the server. When you ask support for help, include a screenshot of the folder tree and make sure shared links (Google Drive and similar) are open to us.

Symptoms: CM/DM says “denied” or Twitch won’t recognize your admin status.

The simplest way: Configure, Players tab, add the player's Steam or console ID as admin, then save. From the console: lp lists the players with their IDs, and admin add <id> 0 gives full permission (0 is the highest level). Telnet passwords are on your server's Details page.

Symptoms: Players ask for the Volume tool or creative tools in a live world.

Make the player an admin first (see the previous question). They can then open the console in game and turn on the creative menu with cm and the debug menu with dm.

Symptoms: Assuming the slider boosts server performance.

Admin Slots let that many admins join even when the server is full; Admin Slots Permission sets which permission level may use them. They do not change CPU or RAM.

Symptoms: The panel shows “Reconfiguration scheduled” for a long time after a change.

The change is queued or being applied. Saving settings stops the server, applies them and starts it again on its own; a version or modpack change downloads files first and can take several minutes, which the console shows. Press the button once. If the console has not moved for a long time, open a ticket with your server ID.

Symptoms: The Scheduler is missing or disabled.

The Scheduler is part of plans M, L and XL; S plan servers are restarted by hand in Server management. Scheduled jobs run at the full hour you pick, in your server's timezone.

Symptoms: Horde nights rubber-band or zombies disappear.

Busy worlds and horde nights push the server hardest. Regular restarts (the Scheduler on plans M, L and XL) keep memory in check, and a larger plan gives the server a higher CPU priority. If the console shows corrupted region errors, see the EndOfStreamException question.

Symptoms: Expecting more RAM on larger tiers or wondering whether an upgrade will reduce lag.

All plans run on the same hardware. Larger plans get a higher CPU priority, which matters when the machine is busy, plus uploads, FTP, modpacks and the Scheduler from plan M up.

Symptoms: You need a larger plan mid-cycle or a new card.

Upgrade with Upgrade Plan on My Servers: once paid, your server moves to the new plan with its world and settings, and the old subscription is closed for you. Payments run through Stripe or PayPal; to change the card, cancel at the end of the term and buy again.

Yes. Creators, clans and community admins can join the affiliate program to earn recurring commissions on referrals.

Yes. Streamers on Twitch, YouTube or Kick and community managers can pitch collaborations at /partners: co-branded servers, promo codes and support, on top of the affiliate program.