Server Setup Guide for [Core Keeper] Gamers

Game Server Requirements

Embarking on a Core Keeper adventure with friends necessitates a robust server foundation. Understanding the underlying hardware and software prerequisites is paramount for a smooth, uninterrupted gaming experience. Unlike many graphically intensive titles, Core Keeper's server demands are relatively modest, focusing more on consistent processing power and reliable network connectivity rather than cutting-edge GPUs. This section delves into the specifics, drawing upon established principles of server architecture and network engineering.

At its core, a Core Keeper server, whether self-hosted or provided by a third-party service, functions as a dedicated environment for managing game state, player interactions, and world persistence. The primary computational burden lies in processing game logic, synchronizing player actions, and continuously saving world data. Therefore, the central processing unit (CPU) plays a pivotal role. A multi-core processor, even an older generation one, is generally sufficient. For a small group of 2-4 players, a dual-core CPU with a clock speed of 2.0 GHz or higher is often adequate. As the player count scales upwards, particularly towards the game's current maximum of 8 players, a quad-core CPU with a higher clock speed (e.g., 2.5 GHz or above) becomes increasingly beneficial to prevent latency and stuttering. The architecture of the CPU, whether Intel or AMD, is less critical than its core count and clock speed, as Core Keeper is not heavily optimized for specific instruction sets beyond general x86-64 compatibility (Modern Operating Systems).

Random Access Memory (RAM) is another crucial component. The game world, player inventories, and active entities all reside in RAM for quick access. For a basic server supporting a few players, 4 GB of RAM is a reasonable starting point. However, as the world expands, more structures are built, and more items are generated, the memory footprint will naturally increase. To accommodate a full 8-player server with a moderately developed world, 8 GB of RAM is highly recommended. This provides ample headroom for the game server process itself, as well as the underlying operating system and any auxiliary services that might be running. Insufficient RAM can lead to excessive disk swapping, significantly degrading performance and introducing noticeable lag.

Storage, while not as performance-critical as CPU or RAM for active gameplay, is vital for world persistence and loading times. A Solid State Drive (SSD) is unequivocally recommended over a traditional Hard Disk Drive (HDD). The faster read/write speeds of an SSD drastically reduce world loading times and improve the responsiveness of saving game data, which occurs frequently in Core Keeper. While the game world files themselves are not exceptionally large, the constant small writes and reads benefit immensely from SSD technology. A minimum of 20 GB of free storage space is a safe estimate for the game server files and several world saves, though allocating more is always prudent for future expansion and backups.

Network connectivity is arguably the most critical factor for a smooth multiplayer experience. A stable, high-bandwidth internet connection is indispensable. For self-hosted servers, an upload speed of at least 10 Mbps is recommended for a small group of players, increasing to 20-30 Mbps for a full 8-player server. Download speeds are generally less critical for the server itself, as it primarily sends data to clients, but a balanced connection is always preferable. Low latency, often measured in ping, is equally important. A server with high latency, regardless of bandwidth, will result in a "laggy" experience for players. This is particularly true for games like Core Keeper where precise timing and immediate feedback are important for actions like combat and resource gathering. For hosted solutions, the data center's proximity to the majority of players can significantly impact latency.

Finally, the operating system (OS) on which the server runs is a consideration. Core Keeper servers are typically run on Windows or Linux distributions. Windows Server editions offer a familiar graphical user interface (GUI) and broad software compatibility, making them accessible for those less familiar with command-line interfaces. However, Linux distributions like Ubuntu Server or Debian are often preferred in professional hosting environments due to their lower resource overhead, enhanced security features, and greater stability. For self-hosting, either can be viable, with the choice often coming down to personal familiarity and technical comfort. Regardless of the OS, ensuring it is kept up-to-date with the latest security patches and updates is crucial for server integrity and performance.

In summary, a well-configured Core Keeper server prioritizes a balanced allocation of CPU, RAM, and fast storage, all underpinned by a robust and low-latency network connection. While the specific requirements can vary slightly based on player count and world complexity, adhering to these guidelines will lay a solid foundation for an enjoyable multiplayer journey.

Beginner's Guide

Setting up a Core Keeper server, while seemingly daunting, can be a straightforward process with the right guidance. This beginner's guide will walk you through the essential steps, from initial preparation to getting your server online, focusing on clarity and ease of understanding. We'll cover both the official dedicated server tool and the general principles applicable to various hosting scenarios.

Before diving into the technicalities, ensure your system meets the minimum requirements outlined in the "Game Server Requirements" section. This foundational check will prevent many common issues before they even arise. Once confirmed, the first step is to acquire the Core Keeper dedicated server files. For PC users, these are typically available through Steam. Navigate to your Steam library, and under the "Tools" category, you should find "Core Keeper Dedicated Server." Install this just as you would any other game. This installation provides the necessary executables and data files for your server to run.

Once installed, locate the server's executable file. On Windows, this is usually CoreKeeperServer.exe within the installed directory. For Linux, it might be a shell script or a direct executable. The server can be configured through a configuration file, often named server.json or similar. This file is where you'll define crucial parameters such as the server name, maximum player count, world name, and password. It's highly recommended to set a strong password to prevent unauthorized access to your server. Other configurable options might include port numbers, save intervals, and various game rule adjustments. Carefully review the available options and adjust them to your preferences. Many hosting providers will offer a web-based control panel to simplify this configuration process, abstracting away the direct editing of JSON files.

Networking is often the most challenging aspect for new server administrators, particularly when self-hosting. For players to connect to your server from outside your local network, you'll need to configure port forwarding on your router. Core Keeper typically uses a specific port (e.g., 27015 UDP/TCP, though this can be configured). You'll need to log into your router's administration interface (usually by typing its IP address into a web browser) and locate the "Port Forwarding" or "NAT" section. Here, you'll create a new rule that directs incoming traffic on the specified Core Keeper port to the internal IP address of the machine hosting your server. It's crucial to ensure that your server machine has a static internal IP address to prevent issues if your router reassigns IP addresses. Consult your router's manual or your internet service provider's support for specific instructions on port forwarding, as interfaces vary widely.

Once port forwarding is configured, you can start your Core Keeper server. On Windows, simply run the CoreKeeperServer.exe executable. A command-line window will typically appear, displaying server logs and status messages. On Linux, you might execute a script or the executable directly from the terminal. Monitor these logs for any error messages during startup. A successful startup will usually indicate that the server is listening for connections.

To connect to your server, players will need your public IP address. You can find this by searching "What is my IP address" on a search engine. Share this IP address, along with the configured port if it's non-standard, with your friends. They can then use the "Join Game" option within Core Keeper, selecting "Direct Connect" and entering your server's IP address and port. If you've set a password, they'll be prompted to enter it.

For those who find self-hosting and port forwarding too complex, or who desire greater reliability and performance, a dedicated hosting service is an excellent alternative. These services handle all the technical intricacies, including server setup, network configuration, and maintenance. You typically interact with a user-friendly control panel to manage your server, making the process significantly simpler. While there's a recurring cost, the convenience and peace of mind often outweigh the expense, especially for those new to server administration.

Regardless of your chosen method, remember to regularly back up your world saves. Accidents happen, and having a recent backup can save countless hours of progress. Most hosting providers offer automated backup solutions, while self-hosters will need to manually copy their world save files to a secure location. By following these steps, even a complete beginner can successfully establish a Core Keeper server and embark on their multiplayer adventures.

Hosting Service Comparison and Recommendations

Choosing the right hosting service for your Core Keeper server is a pivotal decision that can significantly impact your multiplayer experience. The market is replete with options, each offering a unique blend of features, performance, and pricing. This section provides a comprehensive comparison of various hosting models and recommends services tailored to different needs, drawing upon established criteria for evaluating game server providers.

Broadly, Core Keeper hosting solutions can be categorized into three main types: shared hosting, virtual private servers (VPS), and dedicated servers.

Shared Hosting: This is often the most economical option. In a shared hosting environment, multiple game servers (and sometimes other applications) run on a single physical machine. Resources like CPU, RAM, and network bandwidth are shared among all tenants.

Pros: Low cost, easy setup with user-friendly control panels, often includes game-specific optimizations.

Cons: Performance can be inconsistent due to resource contention with other users (the "noisy neighbor" effect), limited customization options, potential for slower support response times.

Recommendation: Suitable for very small groups (2-3 players) who are highly budget-conscious and don't mind occasional performance fluctuations. Look for providers that specifically advertise Core Keeper support and offer clear resource allocations.

Virtual Private Servers (VPS): A VPS offers a more isolated environment than shared hosting. While still residing on a shared physical server, a VPS is allocated a dedicated portion of resources (CPU cores, RAM, storage) that are not shared with other users. This provides greater stability and performance.

Pros: Better performance and stability than shared hosting, root access for greater customization, scalable resources, often more affordable than dedicated servers.

Cons: Requires some technical knowledge to manage the operating system and server software, can be more expensive than shared hosting.

Recommendation: An excellent middle-ground for most Core Keeper players. Ideal for groups of 4-8 players who desire consistent performance and some control over their server environment. Many game server providers offer managed VPS solutions that abstract away some of the technical complexities.

Dedicated Servers: This is the pinnacle of hosting solutions, providing an entire physical machine exclusively for your Core Keeper server. All resources are yours, ensuring maximum performance, stability, and customization.

Pros: Unparalleled performance and stability, complete control over hardware and software, highest level of security.

Cons: Most expensive option, requires significant technical expertise to manage, often overkill for Core Keeper unless hosting for a very large community (beyond the game's current player limit, perhaps for multiple instances or other games).

Recommendation: Generally overkill for a single Core Keeper server given the game's relatively low resource demands. However, if you're running a large gaming community, multiple game servers, or other demanding applications alongside Core Keeper, a dedicated server might be justified.

When evaluating specific hosting providers, several key factors should guide your decision:

Performance and Reliability: Look for providers with a strong track record of uptime and low latency. Check reviews and consider their network infrastructure. Data center locations are crucial for minimizing ping to your player base.

Resource Allocation: Clearly understand the CPU, RAM, and storage allocated to your server. Ensure it meets or exceeds the "Game Server Requirements" for your anticipated player count.

Control Panel: A user-friendly control panel (e.g., Pterodactyl, cPanel, or a custom solution) simplifies server management, making it easy to start/stop the server, manage files, and configure settings.

Customer Support: Responsive and knowledgeable customer support is invaluable, especially when troubleshooting issues. Look for 24/7 support via multiple channels (live chat, tickets, phone).

Pricing and Scalability: Compare pricing models, including setup fees, monthly costs, and options for upgrading or downgrading resources as your needs change. Be wary of hidden fees.

Backup Solutions: Automated daily or weekly backups are essential. Confirm how backups are managed and how easy it is to restore a previous save.

DDoS Protection: Distributed Denial of Service (DDoS) attacks can disrupt your server. Many reputable providers offer robust DDoS protection as a standard feature.

Specific Hosting Provider Recommendations (General Categories):

For Budget-Conscious Beginners (Shared/Entry-Level VPS): Look for providers like Hostinger, OVHcloud Game, or smaller, specialized game server hosts. They often have tailored Core Keeper plans. Prioritize those with good community reviews for Core Keeper specifically.

For Balanced Performance and Control (Managed VPS): Providers such as DigitalOcean, Linode, or Vultr offer unmanaged VPS solutions that can be configured for Core Keeper. For a more managed experience, consider game-specific hosts that build on these infrastructures, offering a control panel on top.

For Maximum Performance and Customization (Dedicated Server/High-End VPS): OVHcloud, Hetzner, or ServerMania are well-regarded for their dedicated server offerings. For high-end VPS, the aforementioned DigitalOcean, Linode, and Vultr can be configured with substantial resources.

Ultimately, the best hosting service is one that aligns with your budget, technical comfort level, and the specific needs of your Core Keeper community. Thorough research and reading recent user reviews are crucial before making a commitment.

Troubleshooting

Even the most meticulously set up Core Keeper server can encounter issues. Effective troubleshooting is a critical skill for any server administrator, transforming frustration into resolution. This section outlines common problems and provides systematic approaches to diagnose and fix them, drawing upon general principles of network and software debugging.

1. Server Not Starting/Crashing on Startup:

Check Server Logs: This is your first and most important step. The server's console window or log files (usually found in a logs directory within the server installation) will often contain error messages indicating the cause of the crash. Look for keywords like "Error," "Failed," "Exception," or "Fatal."

Verify Configuration File: A malformed server.json (or equivalent) is a frequent culprit. Even a missing comma or an incorrect value can prevent the server from launching. Use a JSON validator online to check its syntax.

Resource Availability: Ensure the server machine has sufficient RAM and CPU resources. If other applications are consuming too many resources, the Core Keeper server might fail to allocate what it needs.

Port Conflicts: Another application or service might be using the same port that your Core Keeper server is trying to bind to. Check for port conflicts using tools like netstat -ano on Windows or lsof -i :[port_number] on Linux.

Firewall Issues: The operating system's firewall (Windows Defender Firewall, ufw on Linux) might be blocking the server executable or its communication ports. Temporarily disable the firewall for testing purposes (re-enable and configure exceptions afterward).

Corrupted Files: Rarely, server files can become corrupted. Try verifying the integrity of the server files through Steam (if applicable) or reinstalling the dedicated server.

2. Players Cannot Connect to the Server:

Incorrect IP Address/Port: Double-check that players are using the correct public IP address of your server and the correct port number.

Port Forwarding (Self-Hosted): This is the most common issue for self-hosted servers.

Verify Internal IP: Ensure the internal IP address configured in your router's port forwarding rule matches the current internal IP of your server machine. If your server's internal IP changes, port forwarding will break. Consider setting a static internal IP for your server.

Router Firewall: Some routers have their own built-in firewalls that might block incoming connections even if port forwarding is configured. Check your router's security settings.

ISP Restrictions: A few Internet Service Providers (ISPs) block certain ports or use Carrier-Grade NAT (CGNAT), which makes direct port forwarding impossible. Contact your ISP if you suspect this is the case.

Operating System Firewall: As mentioned above, ensure the OS firewall on the server machine is configured to allow incoming connections on the Core Keeper server port.

Server Not Running: Confirm that the Core Keeper server process is actually active and not crashed. Check the server console or process list.

Network Latency/Packet Loss: High latency or significant packet loss between the player and the server can prevent successful connections. Use ping and traceroute (or tracert on Windows) to diagnose network path issues.

3. Lag and Performance Issues:

Server Resources: The most frequent cause of lag.

CPU Overload: Monitor CPU usage on the server machine. If it's consistently at 90-100%, the CPU is a bottleneck. Consider upgrading or reducing player count.

RAM Exhaustion: Check RAM usage. If it's near 100%, the server is likely swapping to disk, causing severe slowdowns. Increase RAM.

Disk I/O: If using an HDD, slow disk read/write speeds can cause lag, especially during world saves. Upgrade to an SSD.

Network Congestion:

Server-Side Bandwidth: Ensure your server's internet connection has sufficient upload bandwidth. Other applications on the server machine or network might be consuming bandwidth.

Client-Side Network: Players with poor internet connections or high local network congestion will experience lag regardless of server performance.

Game World Complexity: Very large, complex worlds with many active entities, structures, and generated items can naturally increase server load.

Server Software Updates: Ensure your Core Keeper dedicated server software is up-to-date. Developers often release performance optimizations.

Mod Conflicts (if applicable): If using mods, a poorly optimized or conflicting mod can introduce significant performance issues. Test by running the server without mods.

4. World Save Issues:

Disk Space: Ensure there is ample free disk space on the server machine for world saves.

Permissions: The server process needs appropriate read/write permissions to the directory where world saves are stored.

Corrupted Save: In rare cases, a world save file can become corrupted. Regularly backing up your world is crucial to recover from this.

General Troubleshooting Principles:

Isolate the Problem: Try to narrow down the issue. Is it affecting all players or just one? Is it constant or intermittent? Does it happen only under specific conditions?

One Change at a Time: When making configuration changes or attempting fixes, implement only one change at a time. This makes it easier to identify which change resolved (or caused) the issue.

Consult Documentation and Communities: The official Core Keeper wiki, forums, and community Discord servers are invaluable resources. Many common issues have already been discussed and resolved by other players.

Restart Services: Sometimes, a simple restart of the server application or even the entire server machine can resolve transient issues.

By approaching troubleshooting systematically and utilizing available resources, you can effectively resolve most Core Keeper server issues and maintain a stable, enjoyable multiplayer environment.

Performance Optimization Tips

Optimizing your Core Keeper server's performance is key to providing a smooth and responsive experience for all players. While hardware plays a significant role, various software and configuration adjustments can further enhance efficiency and minimize lag. This section delves into practical strategies for squeezing the most out of your server resources, drawing upon best practices in server management and game optimization.

1. Hardware-Level Optimizations:

Prioritize SSD Storage: As previously mentioned, an SSD is non-negotiable for optimal disk I/O performance. If your server is still on an HDD, upgrading to an SSD will yield the most significant performance improvement for world loading and saving.

Adequate RAM: Ensure your server has sufficient RAM. If monitoring shows consistent high RAM usage, adding more RAM will prevent disk swapping, which is a major performance killer.

CPU Core Speed over Core Count (for single-threaded tasks): While Core Keeper can utilize multiple cores, many game server processes still have significant single-threaded components. A CPU with fewer, faster cores can sometimes outperform one with more, slower cores for certain game server workloads. However, a balance is ideal for overall system responsiveness.

Stable Network Connection: A wired Ethernet connection is always superior to Wi-Fi for server stability and lower latency. Ensure your server machine is connected directly to your router or switch via a high-quality Ethernet cable.

2. Operating System Optimizations:

Minimalist OS Installation: For dedicated servers, consider using a lightweight server-oriented operating system like Ubuntu Server or Debian. These distributions typically have a smaller footprint, consume fewer resources, and offer better performance than desktop OS versions.

Disable Unnecessary Services: Review and disable any non-essential services or background applications running on the server machine. Each running process consumes CPU cycles and RAM, potentially impacting Core Keeper's performance.

Keep OS Updated: Regularly apply operating system updates and security patches. These often include performance improvements and bug fixes.

Firewall Configuration: Ensure your firewall is configured correctly to allow Core Keeper traffic without excessive overhead. Overly restrictive or poorly configured firewalls can introduce latency.

Power Management (Windows): On Windows servers, set the power plan to "High Performance" to prevent the CPU from throttling its clock speed, which can lead to inconsistent performance.

3. Core Keeper Server Configuration Optimizations:

Max Player Count: While Core Keeper supports up to 8 players, consider if your hardware can comfortably handle that many. Reducing the maximum player count in your server.json can significantly reduce server load, especially if your hardware is borderline.

Save Interval: The server periodically saves the world state. While frequent saves are good for data integrity, very short save intervals can introduce micro-stutters, especially on slower storage. Experiment with slightly longer save intervals (e.g., every 5-10 minutes instead of every 1-2 minutes) if you experience hitches during saves.

World Size (if configurable): If the server configuration allows for initial world size generation, a smaller world might perform better, though this is less common for Core Keeper specifically.

Game Rules: Certain game rules or events might be more resource-intensive. While not directly configurable for performance, being aware of in-game activities that generate many entities (e.g., large mob farms, extensive automation) can help diagnose performance dips.

4. Network Optimizations:

Quality of Service (QoS): If your router supports QoS, you can prioritize network traffic for your Core Keeper server. This ensures that game data gets preferential treatment over other network activities (e.g., streaming, large downloads) on your local network.

Minimize Latency: Choose a hosting provider with data centers geographically close to the majority of your players. For self-hosting, ensure your internet connection is stable and has low ping to external servers.

Avoid Wi-Fi for Server: Reiterate the importance of a wired connection for the server machine itself.

Monitor Network Usage: Use tools to monitor network bandwidth usage on your server. If it's consistently saturated, it could indicate a bottleneck or even a DDoS attack.

5. Regular Maintenance:

Restart Server Periodically: A regular server restart (e.g., daily or every few days) can help clear out memory leaks, refresh processes, and maintain optimal performance. Schedule these during off-peak hours.

Keep Server Software Updated: Always run the latest version of the Core Keeper dedicated server. Developers frequently release patches that include performance improvements and bug fixes.

Monitor Resources: Continuously monitor CPU, RAM, and disk I/O usage. Tools like htop (Linux) or Task Manager (Windows) provide real-time insights. Set up alerts if resources consistently hit critical thresholds.

Clean Up Old World Saves/Logs: Over time, old world backups and log files can accumulate, consuming disk space. Regularly prune these files.

By implementing a combination of these optimization tips, you can significantly enhance the performance and stability of your Core Keeper server, ensuring a more enjoyable and lag-free experience for all your players.

Technical Q&A

This section addresses common technical questions that arise during the setup, maintenance, and operation of a Core Keeper server. The answers are designed to be concise yet comprehensive, drawing upon established technical knowledge and best practices in server administration.

Q1: What is the difference between a "listen server" and a "dedicated server" in Core Keeper?

A listen server, often referred to as a "host and play" server, is integrated directly into the game client. When a player starts a multiplayer game from within Core Keeper, their game client acts as both a player and the server. This is convenient for casual play with friends but suffers from several drawbacks: the server only runs while the host player is online, performance can be impacted by the host's game client activities, and it's generally less stable. A dedicated server, conversely, is a standalone application that runs independently of any player's game client. It can operate 24/7, offers superior performance and stability, and is the preferred method for persistent multiplayer worlds and larger player groups.

Q2: How do I find my server's public IP address for players to connect?

If you are self-hosting, you can find your public IP address by simply searching "What is my IP address" on Google or using websites like whatismyip.com. This is the address you will share with your friends. Be aware that most residential internet connections use dynamic IP addresses, meaning your public IP might change periodically. For a more stable solution, consider a dynamic DNS (DDNS) service or a static IP address from your ISP. If you are using a hosting service, your provider will typically give you a static IP address or a hostname to connect to.

Q3: Can I run multiple Core Keeper servers on the same machine?

Yes, it is technically possible to run multiple Core Keeper dedicated servers on the same physical or virtual machine, provided the machine has sufficient resources (CPU, RAM, network bandwidth) to handle the combined load. Each server instance will need its own unique set of configuration files, world saves, and, critically, must be configured to use different network ports to avoid conflicts. For example, one server might use port 27015, and another 27016. This requires careful resource management and port forwarding configuration.

Q4: What are the security implications of self-hosting a Core Keeper server?

Self-hosting exposes your home network to the internet, which carries inherent security risks. It's crucial to:

Use Strong Passwords: For your server and router.

Keep Software Updated: Ensure your operating system, router firmware, and Core Keeper server software are always up-to-date with the latest security patches.

Configure Firewall Correctly: Only open the specific ports required for Core Keeper and restrict access to other ports.

Monitor for Suspicious Activity: Keep an eye on server logs for unusual connection attempts.

Consider a VPN (for advanced users): A VPN can add an extra layer of security and privacy, though it adds complexity. While Core Keeper itself is generally not a high-risk application, a poorly secured server can be an entry point for other vulnerabilities on your network.

Q5: How do I back up my Core Keeper world save files?

World save files are typically located in a specific directory within your Core Keeper dedicated server installation or in a user-specific application data folder (e.g., C:\Users\[YourUsername]\AppData\LocalLow\Pugstorm\Core Keeper\Worlds on Windows). The exact path can vary slightly. To back up, simply copy the entire "Worlds" folder (or the specific world folder you wish to back up) to a safe location, such as an external hard drive, cloud storage, or another machine. For automated backups, you can use scripting (e.g., batch scripts on Windows, shell scripts on Linux) combined with scheduled tasks (Task Scheduler on Windows, Cron on Linux) to regularly copy these files. Most commercial hosting providers offer automated backup solutions through their control panels.

Q6: My server is showing "connection timed out" errors for players. What does this mean?

"Connection timed out" typically indicates that the player's client attempted to establish a connection with the server but did not receive a response within a reasonable timeframe. This is almost always a network-related issue. Common causes include:

Incorrect IP/Port: The player is trying to connect to the wrong address.

Server Not Running: The Core Keeper server application is not active.

Firewall Blocking: An operating system firewall or router firewall is preventing the connection.

Port Forwarding Issue: For self-hosted servers, port forwarding is either incorrectly configured or not working.

ISP Restrictions: Your ISP might be blocking the port or using CGNAT.

Network Congestion/High Latency: Extreme network lag can cause connections to time out before they are established. Start by verifying the server is running, then meticulously check all firewall and port forwarding configurations.

Q7: Can I transfer my single-player world to a dedicated server?

Yes, you can typically transfer your single-player world to a dedicated server. The process involves locating your single-player world save files (usually in a similar AppData path as mentioned in Q5, but under the game client's save directory) and then copying those specific world files into the dedicated server's "Worlds" directory. Ensure the dedicated server is configured to load that specific world name in its server.json file. Always back up both your single-player world and the server's existing worlds before attempting such a transfer.

Q8: What is the impact of mods on server performance and stability?

Mods can significantly impact server performance and stability. Poorly optimized mods, mods with memory leaks, or conflicting mods can introduce lag, crashes, and unexpected behavior. It's crucial to:

Use Reputable Mods: Download mods from trusted sources.

Test Mods Individually: Introduce mods one by one to identify any that cause issues.

Monitor Performance: Keep an eye on server resource usage after installing new mods.

Keep Mods Updated: Ensure all installed mods are compatible with your Core Keeper server version and are up-to-date. For critical servers, it's often advisable to run without mods or with a very limited, thoroughly tested set.

Q9: How do I update my Core Keeper dedicated server?

If you installed the dedicated server via Steam, simply restarting Steam and checking for updates in your "Tools" library should prompt an update. For Linux servers, you might use steamcmd with the app_update command. If you're using a hosting provider, they typically handle updates through their control panel, often with a one-click update button or automated processes. Always back up your world saves before performing a server update, as major updates can sometimes introduce compatibility issues or require a fresh world.

Q10: My server is experiencing rollbacks. What could be the cause?

Rollbacks, where player progress or world changes are lost, usually point to issues with the server's saving mechanism. Common causes include:

Server Crashes: If the server crashes before it can properly save the world, recent progress will be lost. Check server logs for crash reasons.

Insufficient Disk Space: The server might not have enough space to write the save file completely.

Disk I/O Errors: Problems with the storage drive itself (e.g., failing SSD/HDD) can lead to corrupted or incomplete saves.

Permissions Issues: The server process might lack the necessary write permissions to the save directory.

Forced Shutdowns: Abruptly terminating the server process without a graceful shutdown can prevent the final save from completing. Always use the server's designated shutdown command or button. Regular backups are your best defense against significant data loss from rollbacks.