Server Setup Guide for [Don't Starve Together] Gamers

Game Server Requirements

Embarking on the perilous journey of Don't Starve Together (DST) with friends necessitates a robust server infrastructure. The foundational elements dictating a smooth, uninterrupted gameplay experience are rooted in the server's hardware specifications and network capabilities. Understanding these requirements is paramount to selecting or configuring an environment that can withstand the game's dynamic demands, particularly as the world evolves and player count fluctuates.

At its core, a DST server, whether self-hosted or provided by a commercial service, requires adequate processing power. The game's engine, while not inherently a graphical powerhouse, relies heavily on CPU cycles for world generation, entity tracking, and complex AI calculations. As the in-game days progress, the number of objects, creatures, and environmental effects escalates, placing an increasing burden on the server's processor. A multi-core CPU is generally recommended, with a strong emphasis on single-core performance, as certain game logic threads may not fully utilize all available cores. For a small group of 2-4 players, a dual-core processor with a clock speed of at least 2.5 GHz per core might suffice. However, for larger communities or servers intended to host 6+ players, a quad-core processor or better, with individual core speeds exceeding 3.0 GHz, becomes increasingly important to prevent noticeable latency and stuttering.

Memory, or RAM, is another critical component. DST servers are memory-intensive, especially when managing persistent world data, player inventories, and the numerous scripts that govern in-game events. A minimum of 2 GB of RAM is often cited for a basic, small-scale server. However, this figure quickly becomes insufficient as the world ages, more players join, or complex mods are introduced. For a more stable and future-proof setup, 4 GB of RAM is a more realistic starting point for a moderately sized server. Servers aiming to support a larger player base (8+ players) or those heavily reliant on community-created modifications should consider 8 GB or even 16 GB of RAM to prevent memory-related performance bottlenecks and crashes. Insufficient RAM can lead to frequent server restarts, data corruption, and a generally frustrating experience for all participants.

Storage, while less impactful on real-time performance than CPU or RAM, plays a crucial role in server responsiveness and data integrity. Solid State Drives (SSDs) are highly recommended over traditional Hard Disk Drives (HDDs). The rapid read/write speeds of SSDs significantly reduce world loading times, accelerate save operations, and improve the overall responsiveness of the server, particularly during initial startup or when players are joining. While the game's core files are relatively small, the persistent world data can grow over time. A minimum of 20 GB of SSD storage is a reasonable starting point, with 50 GB or more providing ample space for future expansion, backups, and potential mod installations.

Network connectivity is the final, yet equally vital, pillar of a successful DST server. A stable, high-bandwidth internet connection is indispensable. Both upload and download speeds are important, but upload speed is particularly critical for a server, as it dictates how quickly game data can be sent to connected clients. A dedicated internet connection with a minimum upload speed of 10-20 Mbps is advisable for a small to medium-sized server. For larger communities or those expecting frequent player activity, a connection with 50 Mbps or higher upload speed will provide a more robust and lag-free experience. Low latency, often measured in ping, is also crucial. A server located geographically closer to its player base will generally offer lower latency, resulting in a more responsive and enjoyable gameplay experience. Furthermore, the server's network must be configured to allow incoming connections on the appropriate ports, typically UDP port 10999 for DST, to ensure players can connect without issue.

Beginner's Guide

Setting up a Don't Starve Together server for the first time can appear daunting, but by following a structured approach, even novices can establish a thriving world for their friends. This guide will walk you through the essential steps, from initial setup to basic configuration, ensuring a smooth entry into the world of server administration.

The journey begins with deciding on your hosting method: self-hosting or utilizing a commercial game server provider. Self-hosting involves running the server software directly on your own computer or a dedicated machine. This option offers maximum control and can be cost-effective if you already possess suitable hardware and a robust internet connection. However, it demands technical proficiency, consistent uptime for your machine, and can consume local resources. Commercial hosting, conversely, offloads the technical complexities to a specialized provider. They manage the hardware, network, and often provide user-friendly control panels, making it an ideal choice for those seeking convenience and reliability, albeit at a recurring cost. For this beginner's guide, we will focus on the general principles applicable to both, with specific notes where differences arise.

Step 1: Acquiring the Server Files. If self-hosting, you'll need to download the Don't Starve Together dedicated server files. These are typically available through SteamCMD, a command-line version of the Steam client. You'll execute commands to log in anonymously and then download the dontstarvetogether_dedicated_server application. For commercial hosts, this step is usually handled for you, with the server files pre-installed and ready for configuration through their control panel.

Step 2: Understanding Server Structure. A DST server operates with two primary components: the "Master" shard and the "Caves" shard. The Master shard represents the surface world, where players typically begin their adventure. The Caves shard is a separate, interconnected world beneath the surface. Both shards run as distinct processes but communicate to maintain world consistency. Each shard has its own configuration files and save data. This dual-shard architecture allows for complex world generation and exploration.

Step 3: Initial Configuration - settings.ini and cluster.ini. The core of your server's identity and behavior is defined in two crucial files: settings.ini (for each shard) and cluster.ini (for the entire server cluster).

cluster.ini: This file, located in your cluster's main directory, defines global server settings. Key parameters include:

cluster_name: The name that appears in the server browser. Choose something descriptive and inviting!

cluster_description: A brief description of your server.

cluster_password: (Optional) A password to restrict access to your server.

max_players: The maximum number of players allowed on your server. Be mindful of your hardware and network capabilities when setting this.

game_mode: Common options include survival, endless, and wilderness. Survival is the standard experience, endless allows respawning, and wilderness scatters players across the map.

pvp: Set to true or false to enable or disable player-versus-player combat.

pause_when_empty: Set to true to pause the server when no players are online, saving resources.

autosaver_enabled: Set to true to enable automatic saving of the world.

autosaver_period: The interval (in seconds) between automatic saves.

settings.ini: Each shard (Master and Caves) will have its own settings.ini file, typically located within its respective shard folder. This file configures specific aspects of that shard. Important settings include:

shard_name: A unique name for the shard (e.g., Master or Caves).

is_master: Set to true for the Master shard, false for Caves.

bind_ip: (Self-hosting) The IP address the server should bind to. Usually 127.0.0.1 or 0.0.0.0.

master_port: The port for the Master shard (default 10999).

cluster_key: A unique identifier for your server cluster. This is crucial for connecting shards.

Step 4: Port Forwarding (Self-Hosting Only). If you are self-hosting, your router needs to be configured to allow incoming connections to your server. This process, known as port forwarding, directs traffic from the internet to your server's local IP address on the specified port (default 10999 UDP). Consult your router's manual or online resources for specific instructions, as the process varies between manufacturers. Commercial hosts handle this automatically.

Step 5: Starting the Server. Once configured, you can start your server.

Self-hosting: You'll typically use a batch file (.bat on Windows) or a shell script (.sh on Linux) to launch the dedicated server executables for both the Master and Caves shards. These scripts will specify the cluster and shard names.

Commercial hosting: You'll usually click a "Start" button within your host's control panel.

Step 6: Connecting to Your Server. After the server has started and is visible in the in-game server browser (it may take a few minutes), your friends can search for it by name or filter by password. If self-hosting, you can connect directly using your local IP address or localhost if playing on the same machine. Friends will use your public IP address.

Step 7: Basic Administration Commands. Once connected, you can use console commands (accessed by pressing ~ in-game) to manage your server. Common commands include:

c_announce("Message"): Broadcasts a message to all players.

c_kick("PlayerName"): Kicks a player from the server.

c_ban("PlayerName"): Bans a player from the server.

c_save(): Forces a manual save of the world.

c_shutdown(): Shuts down the server gracefully.

This beginner's guide provides the fundamental knowledge to get your Don't Starve Together server up and running. As you gain experience, you can delve into more advanced configurations, modding, and performance optimization.

Hosting Service Comparison and Recommendations

Selecting the ideal hosting service for your Don't Starve Together (DST) server is a pivotal decision that directly impacts your gaming experience. The market offers a diverse array of providers, each with its own strengths and weaknesses. This section will meticulously compare key aspects of hosting services and provide recommendations tailored for the discerning gamer.

The landscape of game server hosting is broadly categorized into two main types: shared hosting and dedicated hosting. Shared hosting, often the more economical option, involves multiple game servers running on a single physical machine. While cost-effective, performance can be inconsistent due to resource contention with other users. Dedicated hosting, conversely, provides an entire physical server or a virtual private server (VPS) with guaranteed resources exclusively for your use. This offers superior performance and stability but comes at a higher price point ( Cloud Computing: Concepts, Technology & Architecture ). For DST, given its CPU and memory demands, a dedicated VPS or a well-resourced shared plan from a reputable provider is generally recommended for a smooth experience.

When evaluating hosting providers, several critical factors come into play:

Performance and Hardware: This is arguably the most crucial aspect. Look for providers that offer modern, high-clock-speed CPUs (e.g., Intel Xeon E3/E5 or AMD Ryzen series), ample RAM (4GB+ recommended for DST), and SSD storage. The quality of the network infrastructure, including uplink speeds and peering agreements, also significantly affects latency and overall responsiveness. Some providers may offer "game-optimized" servers, which often means prioritizing low-latency routing and DDoS protection.

Uptime and Reliability: A server that frequently goes offline or experiences unexpected restarts is detrimental to the DST experience. Reputable hosts offer Service Level Agreements (SLAs) guaranteeing a high percentage of uptime (e.g., 99.9% or higher). Look for providers with redundant power supplies, multiple internet uplinks, and robust cooling systems in their data centers.

Location of Data Centers: The physical proximity of the server to your player base directly influences latency (ping). Choose a provider with data centers strategically located near the majority of your intended players. A lower ping translates to a more responsive and enjoyable gameplay experience, minimizing lag and desynchronization issues ( Networking: A Top-Down Approach ).

Control Panel and Ease of Use: A user-friendly control panel simplifies server management. Features like one-click mod installation, automated backups, easy configuration file editing, and a clear server console are highly desirable. While some advanced users prefer command-line access, a graphical interface significantly lowers the barrier to entry for beginners.

Customer Support: Even the most experienced server administrators encounter issues. Responsive, knowledgeable, and available customer support (24/7 via live chat, tickets, or phone) is invaluable. Check reviews for feedback on support quality and response times.

Pricing and Features: Compare pricing structures, ensuring you understand what's included (e.g., number of player slots, RAM, CPU cores, storage, DDoS protection, backup services). Be wary of excessively cheap plans that might compromise on hardware or support. Some providers offer free trials or money-back guarantees, allowing you to test their services before committing.

DDoS Protection: Distributed Denial of Service (DDoS) attacks can render your server inaccessible. Robust DDoS protection is a critical feature, especially for public servers. Many reputable game server hosts offer this as a standard inclusion.

Recommendations for Don't Starve Together Hosting:

Based on the criteria above, here are general recommendations for types of hosting services that typically excel for Don't Starve Together:

For Casual Play (2-4 Players, Light Modding): A well-regarded shared hosting plan from a specialized game server provider can be sufficient. Look for plans that explicitly state dedicated RAM and CPU resources, even if shared on a physical machine. Prioritize providers known for their performance in your region.

For Dedicated Communities (4-8+ Players, Moderate to Heavy Modding): A Virtual Private Server (VPS) is often the sweet spot. It offers dedicated resources, greater control, and better performance than shared hosting, without the full cost of a bare-metal dedicated server. Ensure the VPS plan provides sufficient CPU cores (2-4), RAM (4-8GB), and SSD storage.

For Large-Scale Public Servers or Competitive Play (8+ Players, Extensive Modding): A high-end VPS or a full dedicated server is recommended. This provides maximum performance, stability, and control, allowing for extensive customization and the ability to handle a large, active player base without compromise.

When making your final decision, always read recent user reviews, check independent comparison sites, and consider utilizing any trial periods offered. The best hosting service is one that aligns with your specific needs, budget, and technical comfort level, ensuring your Don't Starve Together adventures are as smooth and enjoyable as possible.

Troubleshooting

Even with meticulous setup, server issues can arise, transforming a planned survival adventure into a frustrating technical challenge. Effective troubleshooting requires a systematic approach, identifying the root cause of problems ranging from connectivity failures to in-game performance dips ( The Art of Debugging ). This section outlines common Don't Starve Together (DST) server issues and provides actionable steps to diagnose and resolve them.

1. Server Not Appearing in Game Browser / Connection Issues:

Symptom: Players cannot find your server in the in-game browser or receive "Failed to connect" errors.

Diagnosis & Solution:

Is the server actually running? Check your server console or hosting panel. Ensure both the Master and Caves shards are active. A common mistake is only starting one shard.

Port Forwarding (Self-Hosting): Verify that UDP port 10999 (and any other custom ports you've configured) is correctly forwarded on your router to the server's local IP address. Use an online port checker tool to confirm the port is open to the internet. Incorrect port forwarding is a leading cause of connection issues for self-hosted servers.

Firewall: Ensure your operating system's firewall (Windows Firewall, ufw on Linux, etc.) is not blocking incoming connections on the server's ports. Add exceptions for the DST server executables and the relevant UDP ports.

cluster.ini and settings.ini: Double-check cluster_name, cluster_password (if any), and master_port in cluster.ini. For each shard's settings.ini, ensure shard_name is unique and is_master is correctly set. Mismatched cluster_key values between shards can also prevent them from linking.

Public IP Address (Self-Hosting): If players are connecting directly via IP, ensure they are using your current public IP address. This can change if you have a dynamic IP. Services like DynDNS can help manage this.

Hosting Provider Issues: If using a commercial host, check their status page for outages or maintenance. Contact their support if the issue persists.

2. Lag and Performance Issues:

Symptom: Players experience high ping, stuttering, delayed actions, or frequent rollbacks.

Diagnosis & Solution:

Server Resources: This is often the primary culprit.

CPU: Monitor CPU usage. If it's consistently at 90-100%, your server is underpowered. Consider upgrading your CPU or migrating to a more robust hosting plan.

RAM: Check RAM usage. If it's near its limit, the server will start swapping to disk, causing severe slowdowns. Increase RAM or optimize mod usage.

Disk I/O: While less common for real-time lag, slow disk I/O (e.g., using an HDD instead of an SSD) can cause hitches during world saves or asset loading.

Network Congestion:

Server-side (Self-Hosting): Check your internet connection's upload speed and overall network activity. Other devices on your network consuming bandwidth can impact server performance.

Client-side: Ask players to check their own internet connections.

Geographic Distance: High ping can simply be due to players being very far from the server's data center.

Mod Conflicts/Overload: Too many mods, or poorly optimized mods, can significantly strain server resources. Try disabling mods one by one to identify problematic ones.

World Age/Complexity: Very old worlds with a vast number of items, structures, and creatures can naturally become more resource-intensive. Consider starting a fresh world if performance becomes unmanageable.

Garbage Collection: The game engine performs garbage collection periodically. While usually optimized, excessive entities can make these pauses more noticeable.

3. Server Crashes:

Symptom: The server abruptly stops running, often without warning.

Diagnosis & Solution:

Server Logs: The most critical tool for diagnosing crashes. Check the server's console output or log files (typically in the cluster_name/Master/server_log.txt and cluster_name/Caves/server_log.txt directories). Look for error messages, stack traces, or "out of memory" warnings. These logs often pinpoint the exact cause ( Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems ).

Mod Conflicts: A common cause of crashes. If a crash occurs after installing a new mod, that mod is the prime suspect. Disable it and test.

Memory Leaks: Some mods or even game bugs can lead to memory leaks, where the server gradually consumes more and more RAM until it crashes. Monitoring RAM usage over time can help identify this.

Corrupt Save Data: Rarely, a corrupted save file can cause crashes. If logs point to save data issues, you might need to restore from a backup or, as a last resort, start a new world.

Hardware Failure (Self-Hosting): Less common, but faulty RAM or an overheating CPU can cause instability. Monitor hardware temperatures.

4. In-Game Bugs/Glitches:

Symptom: Specific game mechanics are not working as expected, or players encounter unusual behavior.

Diagnosis & Solution:

Mod Interference: If you're using mods, they are the most likely cause. Disable all mods and test if the issue persists. If not, re-enable them one by one to isolate the problematic mod.

Game Version Mismatch: Ensure both the server and all connected clients are running the same, up-to-date version of Don't Starve Together.

Verify Game Files: On Steam, you can verify the integrity of game files for both the client and the dedicated server. This can fix corrupted game assets.

Report to Developers: If you've ruled out mods and version mismatches, and the issue seems to be a core game bug, consider reporting it to Klei Entertainment (the game developers) with detailed steps to reproduce and relevant server logs.

General Troubleshooting Principles:

Isolate the Problem: Change one variable at a time. If you make multiple changes simultaneously, you won't know which one fixed (or caused) the issue.

Check Logs First: Server logs are your best friend. They provide invaluable clues.

Backups: Always have recent backups of your server's world data and configuration files. This allows you to revert to a stable state if a change goes awry.

Community Resources: The Don't Starve Together community forums, wikis, and Discord servers are excellent resources for specific issues. Someone else has likely encountered and solved your problem before.

By systematically approaching troubleshooting with these guidelines, you can effectively diagnose and resolve most Don't Starve Together server issues, ensuring a more stable and enjoyable experience for all players.

Performance Optimization Tips

Optimizing your Don't Starve Together (DST) server is an ongoing process that can significantly enhance the gameplay experience, reducing lag, improving responsiveness, and accommodating a larger player base. While hardware is a foundational element, software configurations and in-game management play a crucial role in squeezing every ounce of performance from your server.

1. Hardware-Level Optimizations (Primarily for Self-Hosting or VPS):

Prioritize SSDs: As previously mentioned, using Solid State Drives for your server's operating system and game files dramatically improves load times and overall responsiveness compared to traditional HDDs. The faster I/O operations reduce bottlenecks during world saves and asset streaming.

Adequate RAM: Ensure your server has sufficient RAM. If your server is constantly hitting its RAM limit, it will resort to using swap space on the disk, which is significantly slower and will cause severe performance degradation. Monitor RAM usage and upgrade if necessary.

High-Clock-Speed CPU: DST benefits from strong single-core performance. While multi-core CPUs are common, ensure the individual cores have a high clock speed. Overclocking (if applicable and done safely) can provide a boost, but comes with risks.

Network Bandwidth and Latency: A stable, high-bandwidth internet connection with low latency is paramount. Ensure your server's network interface is not saturated by other applications or network traffic. For self-hosting, consider Quality of Service (QoS) settings on your router to prioritize server traffic.

2. Server Configuration File Optimizations (cluster.ini, settings.ini):

max_players: While tempting to set a high player limit, be realistic about your server's capabilities. Each player adds to the CPU and RAM load. Lowering max_players can significantly improve performance for the remaining players.

autosaver_period: The frequency of automatic saves impacts performance. While saving regularly is crucial for data integrity, very frequent saves (e.g., every 60 seconds) can cause noticeable hitches, especially on older worlds or less powerful hardware. A period of 120-300 seconds (2-5 minutes) is often a good balance.

pause_when_empty: Set this to true in cluster.ini. This pauses the server when no players are online, conserving CPU and RAM resources.

pvp: If not desired, setting pvp = false can slightly reduce server overhead by eliminating the need to track certain combat-related calculations.

tick_rate (Advanced): While not directly exposed in cluster.ini, some advanced server configurations or mods might allow adjusting the server's tick rate. A lower tick rate reduces the frequency of server updates, potentially improving performance at the cost of some responsiveness. This is generally not recommended for beginners.

3. In-Game World and Entity Management:

Reduce Clutter: Over time, worlds accumulate a vast number of items, dropped resources, and structures. Each entity consumes server resources. Encourage players to clean up dropped items, consolidate resources into chests, and avoid excessive, sprawling bases.

Limit Mob Farms/Spawners: While efficient for resource gathering, large-scale mob farms or areas with an extremely high density of creatures can be a significant drain on CPU due to AI calculations. Consider limiting their size or frequency.

Mod Management:

Review Mods: Not all mods are created equal. Some are poorly optimized or contain bugs that can cause performance issues or crashes. Research mods before installing them, checking for recent updates and community feedback on performance.

Minimize Mods: Only install mods that are truly essential for your desired gameplay experience. Each mod adds overhead.

Server-Side vs. Client-Side: Understand which mods are server-side (affecting game logic and requiring server resources) and which are purely client-side (cosmetic, affecting only the player's view). Server-side mods have a greater impact on performance.

World Regeneration: For very old, heavily explored, and cluttered worlds, starting a fresh world can often provide a dramatic performance boost. This is a drastic measure but can be necessary for long-running servers.

4. Operating System and Software Optimizations (Primarily for Self-Hosting):

Dedicated Server Machine: If self-hosting, run the DST server on a machine dedicated solely to server tasks, or at least one with minimal other applications running. This prevents resource contention.

Lightweight OS: For Linux servers, use a lightweight distribution (e.g., Ubuntu Server, Debian) without a graphical user interface. This frees up RAM and CPU cycles that would otherwise be consumed by the desktop environment.

Update Drivers and OS: Keep your operating system and network drivers up to date to ensure optimal performance and security.

Disable Unnecessary Services: Turn off any non-essential background services on the server machine to free up resources.

Antivirus/Security Software: Configure antivirus software to exclude the DST server directories from real-time scanning, as this can cause I/O bottlenecks. Ensure your firewall is configured correctly but not overly restrictive, which can cause performance issues.

By implementing a combination of these optimization strategies, you can significantly improve the stability and responsiveness of your Don't Starve Together server, providing a more enjoyable and lag-free experience for all survivors.

Technical Q&A

Navigating the technical intricacies of Don't Starve Together (DST) server administration often leads to specific questions beyond basic setup and troubleshooting. This section addresses common technical queries, providing detailed explanations rooted in server architecture and best practices.

Q1: How do I add mods to my Don't Starve Together server?

A1: Adding mods to a DST server involves a few steps, differing slightly between server-side and client-side mods.

Subscribe to Mods on Steam Workshop: First, you (or any player) must subscribe to the desired mods on the Don't Starve Together Steam Workshop. This downloads the mod files to your local game directory.

Locate Mod IDs: Each mod has a unique numerical ID. You can find this ID in the mod's Steam Workshop URL (e.g., id=1234567890).

Server-Side Mod Configuration:

Navigate to your server's cluster directory (e.g., ~/.klei/DoNotStarveTogether/MyCluster).

Inside, you'll find a mods folder. If it doesn't exist, create it.

Create a file named dedicated_server_mods_setup.lua within the mods folder.

Edit this file to include lines for each server-side mod you want to enable. The format is ServerModSetup("ModID"). For example:

ServerModSetup("1234567890") -- Example Mod 1

ServerModSetup("9876543210") -- Example Mod 2

Next, you need to enable these mods in your modoverrides.lua file. This file is located within each shard's folder (e.g., MyCluster/Master/modoverrides.lua and MyCluster/Caves/modoverrides.lua). If it doesn't exist, create it.

The modoverrides.lua file uses a Lua table structure. For each mod, you'll specify enabled = true. For example:

return {

["1234567890"] = { enabled = true },

["9876543210"] = { enabled = true }

}

Some mods also allow configuration options within this file. Consult the mod's workshop page for specific settings.

Client-Side Mod Configuration: Client-side mods (e.g., UI enhancements, visual changes) only need to be subscribed to by individual players. They do not require server-side configuration in dedicated_server_mods_setup.lua or modoverrides.lua.

Restart Server: After making changes to dedicated_server_mods_setup.lua or modoverrides.lua, you must restart your DST server for the changes to take effect.

Q2: How do I backup and restore my Don't Starve Together server world?

A2: Regular backups are crucial for disaster recovery.

Locate Save Data: Your server's world data is stored within your cluster directory. For example, ~/.klei/DoNotStarveTogether/MyCluster/Master/save and ~/.klei/DoNotStarveTogether/MyCluster/Caves/save. The entire MyCluster folder contains all your world data and configuration files.

Backup Procedure:

Stop the Server: It is highly recommended to stop both the Master and Caves shards before performing a backup to ensure data consistency and prevent corruption.

Copy the Cluster Folder: Simply copy the entire MyCluster folder (or whatever you named your cluster) to a safe, separate location. This includes all shard data, configuration files, and mod settings.

Automated Backups: Many commercial hosting providers offer automated backup solutions through their control panels. For self-hosting, you can use scripting (e.g., cron jobs on Linux, Task Scheduler on Windows) to automate this process, perhaps compressing the folder and moving it to cloud storage.

Restore Procedure:

Stop the Server: Ensure the server is completely shut down.

Delete Current Data (Optional but Recommended): If restoring due to corruption, delete the existing MyCluster folder on your server.

Copy Backup: Copy your backed-up MyCluster folder back to the original location (e.g., ~/.klei/DoNotStarveTogether/).

Restart Server: Start your server. It should now load the restored world data.

Q3: Can I transfer my Don't Starve Together server from one host to another, or from self-hosted to a commercial host?

A3: Yes, transferring your server is generally possible.

Backup Your Entire Cluster: Follow the backup procedure outlined in A2, ensuring you have a complete copy of your MyCluster folder. This is the most critical step.

Prepare New Host:

Commercial Host: If moving to a commercial host, they will typically provide a fresh server instance. You'll need to access its file system (usually via FTP/SFTP or a web-based file manager in their control panel).

Self-Hosted: If moving to a new self-hosted machine, ensure you have the DST dedicated server files installed via SteamCMD.

Transfer Files: Upload your backed-up MyCluster folder to the new host's designated server data directory (e.g., ~/.klei/DoNotStarveTogether/). Ensure the folder structure is identical to the original.

Configure New Host:

cluster.ini: Review and adjust cluster.ini as needed for the new environment (e.g., bind_ip if self-hosting, master_port if changing).

Port Forwarding/Firewall: If self-hosting, configure port forwarding and firewall rules on the new machine. Commercial hosts handle this.

Mod Setup: Ensure dedicated_server_mods_setup.lua and modoverrides.lua are correctly placed and configured.

Start and Test: Start the server on the new host and verify that players can connect and the world loads correctly.