Help Center & FAQ

Symptoms: Player slots revert to eight, world size snaps to 8K, or consoles say “modified files detected.”

Guidance: Crossplay servers must match Fun Pimps’ console envelope (8 players, 8K map, EAC on, no mods). When you enable crossplay the panel clamps out-of-range values automatically. Remove all modlets from both the server and clients, restart, and console players will be able to join.

Symptoms: The panel sits on “reconfiguration scheduled” or “Server is off” for long stretches after clicking an installer.

Guidance: It simply means your job is waiting in the queue. Once the sync finishes the server stops and waits for you to press Start. Avoid double-clicking, and if the log tail never changes share it with support so we can bump the stuck action.

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

Guidance: Confirm the live build in the console matches your Steam client. Use Check for Steam upgrades for stable branches, reinstall from Distros for experimentals, and re-enter/clear the password fields so the panel isn’t sending a blank value. Remove any mods that consoles forbid and restore from backup if the log shows corruption.

Symptoms: Auto-update never triggers, or you cannot reach the new EXP build.

Guidance: Stable releases: click Check for Steam upgrades once, wait for “successfully installed,” then start the server. Experimentals: reinstall from Configure → Distributions & ModPacks. Always download a manual backup before switching builds.

Symptoms: Worlds revert to older days or you’re unsure which `world.zip` to keep.

Guidance: Automatic snapshots run every 24–48 hours under Backups/Fixer. Download `world.zip` from Files & Mods before major changes and store it locally so you always have a known-good restore point.

Symptoms: Horde nights rubber-band, zombies disappear, or the portal feels sluggish during big releases.

Guidance: Heavy patches overload nodes temporarily. Upgrade plans for higher CPU priority if your world is busy, schedule regular restarts, and watch the console for corruption. If you see SleeperVolume errors, follow question 7.

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

Guidance: The save’s region data is corrupt. Stop the server, restore a previous backup, or remove the damaged region files before restarting.

Symptoms: The upload completes but the panel says no map data or nothing new appears.

Guidance: Step one or two folders up before zipping so the archive contains the full userdata/Saves/<world> tree plus userdata/GeneratedWorlds/<world> and loose config files (for example serveradmin.xml). If the region/player folders are missing the panel flags the upload as “no map data.”

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

Guidance: FTP (available on M/L/XL plans) uses plain FTP on port 2121. Copy the dedicated FTP host/username/password/port from the Details page and connect without SFTP. For a full walkthrough with screenshots, open the FTP access page.

Symptoms: The scheduler tab is missing or only runs on the hour.

Guidance: Automated tasks are unlocked on M, L, and XL plans. S-plan servers must be restarted manually. Scheduled jobs always fire at the top of the hour; off-hour restarts mean the server crashed.

Symptoms: Botman fails to connect or rewrites files unexpectedly.

Guidance: Botman and similar tools aren’t supported on Supercraft’s managed stack. Use the built-in panel, Alloc’s fixes, or CSMM for analytics instead.

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

Guidance: Use the one-click installers when available - they wipe your world, so back up first. For manual uploads, mirror the sample layout exactly and remember that every player needs the same mod pack locally.

Symptoms: Modlets refuse to load on Alpha 21/1.x builds citing Harmony errors.

Guidance: Download the official “TFP Harmony” bundle shared in our resources and place it in the Mods folder (server and client). Restart so dependent modlets find the correct library.

Symptoms: After editing the config, the console references ``.

Guidance: Delete that line from the config via Files & Mods, save, and restart. Experiments manage the path themselves; the stray entry prevents the world from loading.

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

Guidance: Copy `%APPDATA%/7DaysToDie/Saves/` and `%APPDATA%/7DaysToDie/GeneratedWorlds/` into an `upload` folder, zip them so the archive contains `userdata/Saves` and `userdata/GeneratedWorlds`, then upload/activate it.

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

Guidance: Join the server, run `le` to get the entity ID, then use `admin add <entityId> 0`. Restart so `serveradmin.xml` updates. Telnet passwords can be revealed from the Details page.

Symptoms: Assuming the slider boosts server performance.

Guidance: Admin Slots only reserve join slots or priority for admin accounts. They do not change CPU/RAM allocations.

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

Guidance: Upgrades create a new subscription. Purchase it, use Move Server, then cancel the old plan. Billing runs through Stripe/PayPal, so change cards by cancelling at the end of the term and purchasing again.

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

Guidance: All plans use the same hardware; higher tiers get higher CPU priority, FTP, mod installers, and scheduling. If your world is crowded, upgrading secures more compute time.

Symptoms: Console shows the new build, but the dashboard version stays the same.

Guidance: The banner reflects the version installed when the subscription was provisioned. Verify the live build via the console or in-game version command. If you want the banner updated, reinstall after backing up.

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

Guidance: War3zuk installs must be synchronized everywhere. Verify the Steam build on your server matches the War3zuk version, have every player install the same pack locally, then restart both server and clients to clear cached bundles. War3zuk really wants at least an L plan - lighter tiers tend to crash mid-week once the world grows.

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

Guidance: Download the Wasteland archive manually, extract it locally, and inspect the folder structure. Use FTP (host and credentials are on your server’s Details tab) instead of the panel uploader, then copy the extracted mod folder into sdtd/bin/Mods. Reboot and confirm the mod appears under Mods in the dashboard.

Symptoms: The toast says “oops something went wrong” after a mod upload and no new files appear.

Guidance: Refresh the Mods page first - the file often succeeds even when the toast misfires. If nothing new shows, connect over FTP and place the mod folders directly under sdtd/bin/Mods, then restart to confirm the DLLs load cleanly.

Symptoms: Players request EnableEditorTools for the Volume tool in live worlds.

Guidance: Grant the player admin permissions in serveradmin.xml, then instruct them to enable creative (cm) and debug (dm) once they join. Editor tools become available immediately to admins - no serverconfig.xml edits are required.

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

Guidance: Have them search only for the exact server name (clear filters), ensure their region selector matches the server location, and confirm both console and server are on the same build (for example, console 2.4 requires reinstalling 2.4 via the Mods & Distros tab). Mismatched versions and wrong regions completely hide the listing.

Symptoms: The control panel shows only 8K worlds or overwrites larger custom maps.

Guidance: Generate your 8K+/custom world locally via RWG, then upload the entire world folder using Import Local Game or FTP. Set GameWorld/GameName to the uploaded world name and restart - the backend accepts any size once the folders exist.

Symptoms: Unsure how to upload random-gen worlds or large mod folders outside the panel.

Guidance: Generate the world offline, gather both the world folder and any required mods, then connect with an FTP client such as FileZilla to <cluster>.supercraft.host on port 2121. Upload worlds under the Saves/Region path, mods under sdtd/bin/Mods, select the world inside the panel, and reboot.

Symptoms: The import button is missing or fails on S-tier subscriptions.

Guidance: S plans don’t support local save uploads. Upgrade to an M (or higher) plan, upload the save there, then cancel the S plan once migration finishes.

Symptoms: Players are rejected instantly even after restarts.

Guidance: Ask support to reset the server’s network interface - the cited fix cleared stale routing entries and connections worked afterward. No client-side changes were required.

Symptoms: Browser-based FTP mounts open the file read-only or fail to save changes.

Guidance: Switch to a full FTP client (FileZilla/WinSCP), download the file, edit it locally, then upload to overwrite the server copy. The credentials already have write access; browser mounts typically block PUT requests.

Symptoms: The panel lacks buttons for your layout or support requests screenshots of your structure.

Guidance: Use FTP whenever you need to upload/download whole folders, review generated worlds, or share data with support. Provide annotated screenshots of your folder tree, ensure cloud links (Google Drive, etc.) are shared with support accounts, and recreate archives if any directory is missing - accurate FTP transfers resolve the majority of stalled tickets.

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