Your Core Keeper server: installation and setup on a VPS/dedicated server

To install and configure your own Core Keeper server on a VPS or dedicated server, you will need a Linux operating system (Ubuntu 20.04+ recommended), a minimum of 2 vCPUs, 4 GB RAM, and a 20 GB NVMe disk for comfortable gameplay with 4-8 players, with a budget starting from $15-20 per month.

Core Keeper, an indie survival and sandbox game, has captured the hearts of millions of players worldwide thanks to its unique blend of dungeon exploration, crafting, and building. Playing with friends in a shared world is one of Core Keeper's key features, but the built-in hosting system often faces limitations in performance, stability, and availability. This is where the option to create your own Core Keeper server on a VPS or dedicated server comes to the rescue.

In this article, we will detail how to install and configure a Core Keeper dedicated server, ensuring optimal performance and stability for your gaming group. We will cover everything from choosing suitable Core Keeper hosting to fine-tuning configuration, DDoS protection, and mod management, so your Core Keeper world is always accessible and runs smoothly.

Why do you need your own Core Keeper server? Advantages of dedicated hosting

Playing Core Keeper with friends is much more enjoyable than a solo adventure. However, using the game's built-in hosting, where one player acts as the host, comes with several significant drawbacks. Creating your own Core Keeper server on a powerful VPS or dedicated server solves these problems, offering significant advantages.

Why choose your own Core Keeper server instead of the built-in one?

When playing through the built-in host, server performance directly depends on the host's computer and internet connection. If the host leaves the game, the world becomes inaccessible to everyone else. Furthermore, a slow internet connection or a weak host CPU can lead to delays (lags) and unstable operation for all participants. Your own Core Keeper server, hosted on professional hosting, eliminates these problems:

• 24/7 Availability: The server runs 24/7, regardless of whether any players are online. You and your friends can join the world at any time.
• Stable Performance: A VPS or dedicated server provides guaranteed resources (CPU, RAM, network bandwidth), eliminating lags, freezes, and crashes related to insufficient power.
• High-Speed Connection: Data centers have high-speed communication channels, ensuring low ping for all players, regardless of their location (within reasonable limits).
• Full Control: You get full administrative access to the server, allowing you to install mods, configure game parameters, create backups, and manage access as you see fit.
• Player Independence: The Core Keeper world is not tied to a single player. If the host is busy or their computer is turned off, the server continues to run.

Flexibility and control: the foundation of a Core Keeper dedicated server

Deploying a Core Keeper dedicated server gives you complete control over the game environment. You can:

• Configure game rules: Change difficulty, plant growth speed, monster count, loot parameters, and much more through configuration files.
• Install mods: Expand game functionality, add new items, mechanics, or fix shortcomings. Modifications can significantly enhance the gaming experience, and your own server is the ideal platform for using them.
• Create backups: Regularly save world progress to avoid data loss in case of unforeseen failures or errors.
• Manage access: Protect the server with a password to play only with trusted friends, or open it for public access.
• Monitor resources: Track CPU, RAM, and disk usage to promptly respond to potential problems or optimize server operation.

For those who have experience setting up game servers, such as their own Palworld server or their own Valheim server, the Core Keeper installation process will be intuitive.

Minimum and recommended requirements for a Core Keeper server

Choosing a suitable VPS or dedicated server is a key step to ensure stable and comfortable Core Keeper gameplay. Resource requirements primarily depend on the number of players who will be simultaneously on the server and the size of the generated world.

CPU and RAM: the heart of your Core Keeper server

Core Keeper, like many Unity games, is quite demanding on CPU performance, especially at startup and during world generation. RAM also plays an important role, especially with a large number of players and active exploration.

• For 2-4 players:
  • CPU: 2 vCPUs with a frequency of 2.5 GHz or higher. Good per-core performance is important. Intel Xeon E3/E5 or modern AMD EPYC/Ryzen processors will be optimal.
  • RAM: 4 GB. This will be sufficient for basic server and OS operation.
• For 5-8 players:
  • CPU: 2-4 vCPUs with a frequency of 3.0 GHz or higher. Increasing the number of cores will help distribute the load, especially during active player actions in different parts of the world.
  • RAM: 6-8 GB. Additional memory will allow the server to cache more world data, reducing delays.
• For 9-16+ players:
  • CPU: 4-6 vCPUs with a frequency of 3.5 GHz or higher. For this number of players, a dedicated server may already be required to ensure stable operation.
  • RAM: 10-16 GB. The more players, the more memory is required to maintain all game objects and logic.

It is important to note that Core Keeper relies more on single-core CPU performance than on the total number of cores. Therefore, choose processors with a high clock speed.

Disk and network: speed and stability of Core Keeper hosting

The speed of the disk subsystem and the stability of the network connection are also critical for comfortable gameplay.

• Disk:
  • Volume: A minimum of 20 GB is required for Core Keeper server and OS installation. However, as the world is explored and generated, file size can grow. It is recommended to have a reserve of 50-100 GB, especially if you plan long-term gameplay and mod installation.
  • Type: It is highly desirable to use NVMe SSD. The high read/write speed of NVMe disks significantly speeds up world loading, progress saving, and overall server responsiveness. HDD disks are strongly not recommended due to their low performance, which will cause lags.
• Network:
  • Bandwidth: Minimum 100 Mbps, but 1 Gbps is better. Although Core Keeper is not the most bandwidth-intensive game, a stable and fast channel will ensure low ping and no packet loss.
  • Traffic: Most hosting providers offer unlimited traffic or very large volumes, which will be sufficient for a game server.
  • DDoS Protection: It is highly recommended to choose a hosting provider that offers built-in DDoS protection. Game servers are often targets for such attacks, and having protection will ensure the continuous operation of your Core Keeper dedicated server.

Choosing an operating system and preparing your VPS/dedicated server

For deploying a Core Keeper dedicated server, it is recommended to use a Linux operating system. While it is technically possible to run the server on Windows, Linux offers better performance, stability, and lower resource consumption for server applications. Valebyte.com offers a wide selection of OS for Windows dedicated servers, but for Core Keeper, we recommend Linux.

Linux or Windows: which is better for a Core Keeper dedicated server?

The choice of OS matters for performance and ease of management:

• Linux (recommended):
  • Advantages: Lower consumption of system resources (RAM, CPU), leaving more for the Core Keeper server itself. High stability and security. Most game server installation guides are Linux-oriented.
  • Recommended distributions: Ubuntu Server (versions 20.04 LTS or 22.04 LTS) or Debian (10/11). They are easy to manage, have extensive documentation, and a large community.
• Windows Server:
  • Advantages: Familiar graphical interface for those not accustomed to the command line.
  • Disadvantages: Higher RAM and CPU consumption by the OS itself, which can affect Core Keeper server performance. Requires a license (for dedicated servers).

In this guide, we will use Ubuntu Server 22.04 LTS as the most common and convenient option.

Initial setup and dependency installation

After deploying a VPS or dedicated server with Ubuntu Server, the first step is to connect to it via SSH. Use a client such as PuTTY for Windows or the built-in terminal for Linux/macOS.

ssh username@your_server_ip

After a successful connection, follow these steps:

1. System Update:

   Always start by updating the package database and installed packages to ensure system currency and security.

   sudo apt update
   sudo apt upgrade -y

2. Creating a separate user for the server:

   For increased security and isolation, it is recommended to run the game server as a separate user, not root.

   sudo adduser corekeeper
   sudo usermod -aG sudo corekeeper # If you want to give the corekeeper user sudo rights (optional, but convenient)
   su - corekeeper # Switch to the new user

   All subsequent commands will be executed as the corekeeper user.

3. Installing necessary dependencies:

   For SteamCMD and the Core Keeper server itself, 32-bit libraries and other utilities may be required. Install them:

   sudo apt install -y steamcmd lib32gcc-s1 lib32stdc++6 curl screen

   If steamcmd is not found in the repositories (which is unlikely for modern Ubuntu), it can be installed manually, as described in the next section.

   screen is a very useful utility that allows you to run processes in the background and detach from the SSH session without stopping the server. We will use it to run Core Keeper.

Step-by-step installation and launch of the Core Keeper server

The Core Keeper dedicated server is installed via SteamCMD – a console version of the Steam client designed for installing and updating game servers.

Downloading and configuring SteamCMD for Core Keeper

If you installed steamcmd via apt, skip this step. Otherwise, do the following:

1. Creating a directory for SteamCMD:

   mkdir ~/steamcmd
   cd ~/steamcmd

2. Downloading and extracting SteamCMD:

   curl -sqL "https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz" | tar -xz

3. Launching SteamCMD:

   The first time SteamCMD runs, it will update. This may take some time.

   ./steamcmd.sh

   You will see the Steam> prompt. Now you can execute SteamCMD commands.

Next, regardless of how SteamCMD was installed, perform the following actions in the SteamCMD console:

1. Login (anonymous):

   login anonymous

2. Installing Core Keeper dedicated server:

   Create a directory for the Core Keeper server and install it there. The Core Keeper Dedicated Server application ID on Steam is 2169540.

   force_install_dir /home/corekeeper/server
   app_update 2169540 validate

   The download process may take some time depending on your internet connection speed. Upon completion, you will see the message Success! App '2169540' fully installed.

3. Exiting SteamCMD:

   quit

Now the Core Keeper server files are located in the /home/corekeeper/server directory.

First launch and world generation of Core Keeper

Before the first launch of the server, you need to ensure that you have execute permissions for the server file. Navigate to the server directory:

cd /home/corekeeper/server

And grant execute permissions:

chmod +x CoreKeeperServer.x86_64

Now you can start the server. It is recommended to use the screen utility so that the server continues to run after closing the SSH session.

1. Creating a new screen session:

   screen -S corekeeper_server

   You will be in a new "virtual" console.

2. Launching the Core Keeper server:

   Start the server with minimal parameters for the first launch. The Core Keeper Server uses several command-line arguments. The most important one is -world to specify the path to the world file.

   ./CoreKeeperServer.x86_64 -world /home/corekeeper/server/worlds/my_corekeeper_world.world

   On the first launch, the server will generate a new world at the specified path. You will see server logs indicating its operation and world generation. Once the server loads and is ready to accept connections, you will see messages like "Server started on port XXXXX".

3. Detaching from the screen session:

   To detach from the screen session without stopping the server, press Ctrl+A, then D. You will return to the main SSH session.

4. Reconnecting to the screen session (if needed):

   To reconnect to the session and view server logs, use:

   screen -r corekeeper_server

Configuring Core Keeper dedicated server: configuration and ports

After the first server launch, you can configure its parameters to adapt the gameplay to your needs. Core Keeper uses a configuration file for these purposes.

Main configuration parameters for the Core Keeper server

On first launch, Core Keeper creates a server.json configuration file in the world save directory (in our case, /home/corekeeper/server/worlds/, next to the .world file). You will need to edit this file to change server parameters.

nano /home/corekeeper/server/worlds/my_corekeeper_world.world.server.json

Example content of server.json (may vary depending on game version):

{
  "serverName": "My Core Keeper Server Valebyte",
  "worldName": "my_corekeeper_world",
  "password": "your_very_complex_password",
  "maxPlayers": 8,
  "gamePort": 27015,
  "queryPort": 27016,
  "publicServer": false,
  "seed": "", // Leave empty for a random world or specify a number for a specific seed
  "difficulty": "Normal", // Easy, Normal, Hard
  "enablePvP": false,
  "spawnMonsters": true,
  "allowCheats": false,
  "saveInterval": 300, // Autosave interval in seconds
  "serverIpAddress": "0.0.0.0" // Usually not changed
}

The most important parameters to configure:

• "serverName": The name of your server, which will be visible in the server list.
• "worldName": The name of the world file. Should match what you specify in the -world argument when launching.
• "password": Password for connecting to the server. If you want to make the server private, be sure to set it.
• "maxPlayers": The maximum number of players who can be on the server simultaneously. Remember that this directly affects resource requirements.
• "gamePort" and "queryPort": Ports used by the server. By default, these are 27015 (UDP) and 27016 (UDP). They will need to be opened in the firewall.
• "publicServer": If set to true, the server will be visible in the public Core Keeper server list. Otherwise, connections can only be made via IP address and port.
• "difficulty": The difficulty level of the world.
• "enablePvP": Enable/disable PvP between players.

After editing the file, save it (Ctrl+O, Enter, Ctrl+X) and restart the server for the changes to take effect.

screen -r corekeeper_server # Reconnect to the session
Ctrl+C # Stop the server
./CoreKeeperServer.x86_64 -world /home/corekeeper/server/worlds/my_corekeeper_world.world # Start again

Then detach from the session again with Ctrl+A, D.

Opening ports and firewall rules

For players to be able to connect to your Core Keeper dedicated server, you need to open the used ports in your VPS or dedicated server's firewall. By default, Core Keeper uses UDP ports 27015 (game) and 27016 (query port for server information).

We will use ufw (Uncomplicated Firewall), which is pre-installed in Ubuntu.

1. Check ufw status:

   sudo ufw status

   If ufw is inactive, it needs to be enabled.

2. Enable ufw (if inactive):

   sudo ufw enable

   Confirm the action by pressing y.

3. Allow SSH connections:

   Before opening other ports, ensure that the SSH port (default 22) is allowed, otherwise you will lose access to the server.

   sudo ufw allow ssh

   or specifically:

   sudo ufw allow 22/tcp

4. Open Core Keeper ports:

   sudo ufw allow 27015/udp
   sudo ufw allow 27016/udp

5. Check ufw rules:

   After adding the rules, check the status again to ensure the ports are open.

   sudo ufw status verbose

   You should see rules allowing traffic on ports 22, 27015, and 27016.

Now your Core Keeper server should be accessible for external connections. Players can connect using your VPS/dedicated server's IP address and port 27015.

Managing and optimizing Core Keeper server: mods and backups

For long-term and comfortable gameplay on your Core Keeper server, it's important not only to configure it but also to know how to manage it, install modifications, and regularly create backups.

Installing mods on your Core Keeper server

Modifications can significantly expand Core Keeper's capabilities, add new content, or improve gameplay. Installing mods on a Core Keeper dedicated server usually requires several steps:

1. Selecting and downloading mods:

   Most Core Keeper mods are distributed through platforms such as Thunderstore.io or Nexus Mods. Installing mods on the server often requires a special mod loader, such as BepInExPack.

   Download the necessary mod files (usually .dll files) and the mod loader to your server. This can be done via scp or sftp, using a client like WinSCP.

   scp /path/to/mod.zip corekeeper@your_server_ip:/home/corekeeper/server/mods/

2. Installing the mod loader (BepInEx):

   BepInEx is a universal plugin loader for Unity games, often used for Core Keeper. You need to download the appropriate BepInEx version for Linux x64 and extract it into the root directory of your Core Keeper server (where CoreKeeperServer.x86_64 is located).

   cd /home/corekeeper/server
   # Example: downloading BepInEx (check Thunderstore for the latest version)
   wget https://github.com/BepInEx/BepInEx/releases/download/v5.4.21/BepInEx_unix_5.4.21.0.zip
   unzip BepInEx_unix_5.4.21.0.zip
   rm BepInEx_unix_5.4.21.0.zip

   After extraction, you will have a BepInEx folder in the server directory.

3. Placing mod files:

   Then place the mod files (usually .dll) into the BepInEx/plugins folder within the server directory.

   mkdir -p /home/corekeeper/server/BepInEx/plugins
   # Assuming you downloaded mod.dll
   mv /home/corekeeper/server/mods/mod.dll /home/corekeeper/server/BepInEx/plugins/

4. Launching the server with mods:

   The server should be launched via a BepInEx script, which ensures mods are loaded. This often looks like:

   # In the /home/corekeeper/server directory
   chmod +x run_bepinex.sh # If such a script exists in the BepInEx archive
   ./run_bepinex.sh ./CoreKeeperServer.x86_64 -world /home/corekeeper/server/worlds/my_corekeeper_world.world

   If there is no run_bepinex.sh script, try launching the server directly; BepInEx should intercept the process. Check server logs for messages from BepInEx and loaded mods.

Always carefully read the instructions for each mod, as the installation process may vary. Some mods require installation on both the server and the client.

Regular maintenance and backup

Backup is a critically important aspect of managing any game server. Losing Core Keeper world progress can be very frustrating.

1. What to back up:

   You need to regularly back up the Core Keeper world directory. In our example, this is /home/corekeeper/server/worlds/.

2. How to create a backup manually:

   Stop the server before creating a backup to avoid data corruption.

   screen -r corekeeper_server # Reconnect
   Ctrl+C # Stop
   cd /home/corekeeper/server/worlds/
   tar -czvf ~/corekeeper_world_backup_$(date +%Y%m%d_%H%M%S).tar.gz ./*
   # Start the server again
   cd /home/corekeeper/server
   screen -S corekeeper_server -dm ./CoreKeeperServer.x86_64 -world /home/corekeeper/server/worlds/my_corekeeper_world.world

   The -dm command in screen launches the session in the background immediately, without connecting.

3. Automating backups:

   Use cron to automate the process. Create a backup script that will stop the server, make a copy, and start it again. Example backup_corekeeper.sh script:

   #!/bin/bash
   SERVER_DIR="/home/corekeeper/server"
   WORLD_DIR="$SERVER_DIR/worlds"
   BACKUP_DIR="/home/corekeeper/backups"
   TIMESTAMP=$(date +%Y%m%d_%H%M%S)
   BACKUP_FILE="$BACKUP_DIR/corekeeper_world_$TIMESTAMP.tar.gz"
   
   mkdir -p "$BACKUP_DIR"
   
   # Stop the server
   screen -S corekeeper_server -X quit
   
   # Wait for the server to fully stop (can add sleep)
   sleep 10
   
   # Create backup
   tar -czvf "$BACKUP_FILE" -C "$WORLD_DIR" .
   
   # Start the server
   screen -S corekeeper_server -dm "$SERVER_DIR/CoreKeeperServer.x86_64" -world "$WORLD_DIR/my_corekeeper_world.world"
   
   # Delete old backups (e.g., older than 7 days)
   find "$BACKUP_DIR" -type f -name "corekeeper_world_*.tar.gz" -mtime +7 -delete

   Make the script executable: chmod +x backup_corekeeper.sh.

   Add a task to crontab (as the corekeeper user):

   crontab -e

   And add a line for daily backup, for example, at 3 AM:

   0 3 * * * /home/corekeeper/backup_corekeeper.sh > /dev/null 2>&1

4. Storing backups:

   It is advisable to store backups not only on the same server but also on remote storage (S3-compatible storage, Google Drive, Dropbox, etc.) for maximum reliability.

Protecting Core Keeper server from DDoS attacks and security

Game servers, including Core Keeper dedicated server, are often targets for Distributed Denial of Service (DDoS) attacks. These attacks can lead to server unavailability, high ping, and loss of players. Ensuring the security of your Core Keeper hosting is a priority.

Basic protection measures for Core Keeper hosting

Start with the basic protection steps:

1. Strong SSH password: Use a complex, unique password for SSH access or, even better, set up SSH key authentication and disable password login.
2. Firewall (UFW): As we have already configured, UFW allows opening only the necessary ports (22 for SSH, 27015/27016 UDP for Core Keeper). Close all other ports to minimize the attack surface.

sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow 22/tcp
sudo ufw allow 27015/udp
sudo ufw allow 27016/udp
sudo ufw enable

3. Non-root user: Running the game server as a separate user (e.g., corekeeper) with limited access rights reduces potential damage in case of server compromise.
4. System updates: Regularly update the operating system and all installed packages to patch known vulnerabilities.

sudo apt update && sudo apt upgrade -y

5. Fail2ban: Install and configure Fail2ban to protect SSH from brute-force attacks. It automatically blocks IP addresses from which numerous failed login attempts occur.

sudo apt install fail2ban -y
sudo systemctl enable fail2ban
sudo systemctl start fail2ban

Configure /etc/fail2ban/jail.local for finer configuration.

These measures will significantly increase the overall security of your VPS or dedicated server running Core Keeper.

Additional solutions for Core Keeper dedicated server

For more serious protection against DDoS attacks, especially if your Core Keeper server becomes popular, consider the following options:

• Hosting with built-in DDoS protection: Valebyte.com offers professional DDoS protection solutions on all its VPS and dedicated servers. This means that traffic to your server passes through specialized filters that detect and block malicious packets before they even reach your server. This is the most effective way to protect game servers.
• Using proxies/tunnels: In some cases, for very popular servers, specialized proxy services (e.g., Cloudflare Spectrum or other providers focused on game servers) can be used to hide your server's real IP address and filter traffic. However, for Core Keeper, this is usually not required if the hosting already provides reliable protection.
• Traffic monitoring: Use network monitoring tools (e.g., nload, iftop, or graphical monitoring panels provided by the hosting) to track unusual traffic spikes that may indicate an attack.

Choosing a provider with comprehensive DDoS protection, like Valebyte.com, is often the simplest and most effective solution for most game server administrators. This allows you to focus on game management rather than fighting network attacks.

Which Core Keeper hosting to choose: Valebyte.com tariffs

Choosing the right Core Keeper hosting on a VPS or dedicated server is an investment in stability and gaming enjoyment. Valebyte.com offers various tariff plans that can meet the needs of both small groups of friends and larger communities.

Comparison table of VPS/dedicated servers for Core Keeper

Below is an approximate table with recommendations for choosing a Valebyte.com VPS or dedicated server configuration for Core Keeper, depending on the estimated number of players. Prices are approximate and may vary.

Number of players	Server type	CPU (vCPU / GHz)	RAM (GB)	Disk (NVMe SSD)	Approximate budget (USD/month)
2-4 players	VPS (Entry)	2 vCPU / 2.5+ GHz	4 GB	20 GB	$15 - $25
5-8 players	VPS (Standard)	2-4 vCPU / 3.0+ GHz	6-8 GB	40 GB	$25 - $45
9-12 players	VPS (Advanced)	4 vCPU / 3.5+ GHz	10-12 GB	60 GB	$45 - $70
13-16+ players	Dedicated server (Base)	4-6 Cores / 3.5+ GHz	16 GB	120 GB	$80 - $120
Very large communities / Mods	Dedicated server (Performance)	6-8+ Cores / 4.0+ GHz	32+ GB	240+ GB	$120+

It is important to remember that these recommendations are a starting point. Actual resource consumption may vary depending on game activity, the number of mods, and world specifics.

Optimal configuration for different numbers of players

When choosing your Core Keeper server, focus on the following aspects:

• For a small group (2-4 friends): A lower-tier VPS plan will be optimal. Make sure it offers NVMe disks and sufficient CPU frequency per core. For example, a VPS for 7 Days to Die entry-level often suits Core Keeper as well.
• For a medium group (5-8 players): A VPS with more RAM (6-8 GB) and a more powerful CPU (3.0+ GHz) will be needed. This will ensure smooth gameplay even with active world exploration.
• For large communities (9+ players) or with mods: It is recommended to consider dedicated servers. They provide guaranteed physical resources, which eliminates the "noisy neighbor effect" (the influence of other users on the same physical server) and ensures maximum performance. A dedicated server is also ideal if you plan to install resource-intensive mods. Valebyte.com offers various locations, for example, dedicated servers in Ashburn, providing low ping for players from North America.

All Valebyte.com plans include DDoS protection, which is an important advantage for game servers. Also, pay attention to the data center location: choose one that is geographically closer to most of your players to minimize latency.

Conclusion

Creating your own Core Keeper server on a VPS or dedicated server is the best way to ensure a stable, 24/7 accessible, and fully customizable gaming environment for you and your friends. When choosing Core Keeper hosting, prioritize providers with NVMe disks, high-frequency CPUs, and built-in DDoS protection, such as Valebyte.com, to guarantee the uninterrupted operation of your Core Keeper dedicated server.