Core Keeper: Complete Dedicated Server Setup Guide
Everything you need to know about setting up, configuring, and managing a Core Keeper dedicated server for underground mining adventures with friends. If you would rather skip the manual setup, managed Core Keeper server hosting gets you online in minutes.
System Requirements
Minimum Requirements:
- CPU: Intel Core i3-3220 or AMD FX-4350
- RAM: 4GB DDR3
- Storage: 2GB available space
- Network: 5 Mbps upload for 4 players
- OS: Windows 7+ or Ubuntu 16.04+
Recommended Requirements:
- CPU: Intel Core i5-8400 or AMD Ryzen 5 3600
- RAM: 8GB DDR4
- Storage: 5GB SSD storage
- Network: 20 Mbps upload for 10+ players
- OS: Windows 10/11 or Ubuntu 20.04 LTS
Installation Process
Step 1: Install SteamCMD
# Ubuntu/Debian
sudo apt update
sudo apt install steamcmd
# CentOS/RHEL
sudo yum install steamcmd
# Windows
# Download from: https://steamcdn-a.akamaihd.net/client/installer/steamcmd.zip
Step 2: Download Core Keeper Server
# Create server directory
mkdir /home/corekeeper
cd /home/corekeeper
# Download server files (App ID: 1963720)
steamcmd +login anonymous +app_update 1963720 validate +quit
# Create necessary directories
mkdir saves configs logs
Step 3: Initial Configuration
Create server.cfg in the server directory:
# Core Keeper Server Configuration
[Network]
Port = 27015
MaxPlayers = 10
Password = ""
ServerName = "My Core Keeper Server"
ServerDescription = "Underground mining adventures await!"
[World]
WorldName = "CoreWorld"
WorldSeed = 12345
WorldSize = Medium
Difficulty = Normal
PvP = false
FriendlyFire = false
[Gameplay]
DayLength = 24
ResourceRespawn = true
EnemyRespawn = true
BossRespawn = true
DeathPenalty = Normal
[Performance]
AutoSaveInterval = 300
MaxFPS = 60
NetworkUpdateRate = 30
Configuration Options Explained
Network Settings
- Port: UDP port for game connections (default: 27015)
- MaxPlayers: Maximum simultaneous players (1-20)
- Password: Optional server password for private games
- ServerName: Display name in server browser
- ServerDescription: Detailed description shown in server list
World Generation
- WorldName: Unique identifier for your world
- WorldSeed: Seed number for world generation (0 = random)
- WorldSize: Small, Medium, Large, or Huge
- Difficulty: Peaceful, Normal, Hard, or Hardcore
Gameplay Balance
- PvP: Enable player vs player combat
- FriendlyFire: Allow damage to teammates
- DayLength: Day/night cycle length in hours
- ResourceRespawn: Regenerate ore deposits and resources
- EnemyRespawn: Respawn monsters after defeat
- BossRespawn: Respawn boss monsters after defeat
Performance Settings
- AutoSaveInterval: Time between automatic saves (seconds)
- MaxFPS: Server-side frame rate limit
- NetworkUpdateRate: Network update frequency
Starting the Server
Linux Launch Script
#!/bin/bash
# start_corekeeper.sh
# Configuration
SERVER_DIR="/home/corekeeper"
STEAM_DIR="$HOME/Steam"
APP_ID="1963720"
# Navigate to server directory
cd "$SERVER_DIR"
# Update server (optional, comment out to skip)
echo "Updating Core Keeper server..."
"$STEAM_DIR/steamcmd.sh" +login anonymous +app_update $APP_ID +quit
# Start the server
echo "Starting Core Keeper server..."
./CoreKeeperServer.x86_64 -config server.cfg
# Keep script running (auto-restart on crash)
while true; do
sleep 10
if ! pgrep -f "CoreKeeperServer" > /dev/null; then
echo "Server crashed, restarting..."
./CoreKeeperServer.x86_64 -config server.cfg
fi
done
Windows Batch File
@echo off
:start
cls
echo Starting Core Keeper Server...
REM Update server (optional)
echo Checking for updates...
"C:\Program Files (x86)\Steam\steamcmd.exe" +login anonymous +app_update 1963720 +quit
REM Start server
CoreKeeperServer.exe -config server.cfg
REM Auto-restart if crashed
echo Server stopped or crashed. Restarting in 10 seconds...
timeout /t 10 /nobreak > nul
goto start
Systemd Service (Linux)
Create /etc/systemd/system/corekeeper.service:
[Unit]
Description=Core Keeper Dedicated Server
After=network.target
[Service]
Type=simple
User=corekeeper
WorkingDirectory=/home/corekeeper
ExecStart=/home/corekeeper/CoreKeeperServer.x86_64 -config server.cfg
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
# Enable and start the service
sudo systemctl daemon-reload
sudo systemctl enable corekeeper
sudo systemctl start corekeeper
sudo systemctl status corekeeper
Administration and Commands
Admin Commands
Access admin commands via in-game console (Tab key) or RCON:
/save
Force immediate world save.
/shutdown [seconds] [message]
Shutdown server with countdown and message.
/kick [player] [reason]
Kick player from server with optional reason.
/ban [player] [reason]
Ban player from server permanently.
/unban [player]
Unban previously banned player.
/tp [x] [y]
Teleport to specific coordinates.
/spawn [item] [count]
Spawn items in inventory (admin only).
/time [hour]
Set time of day (0-23).
RCON Setup
Add RCON settings to your server.cfg:
[RCON]
Enabled = true
Port = 27016
Password = "your_secure_password"
AllowedIPs = "127.0.0.1,your_admin_ip"
Using RCON
# Install rcon-cli
npm install -g rcon-cli
# Connect to server
rcon-cli -H localhost -p 27016 -P your_password
# Execute commands
save
list
kick playerName
Advanced Configuration
Performance Optimization
[Performance]
MaxFPS = 60
NetworkUpdateRate = 30
MaxChunkLoadRadius = 10
MaxConcurrentConnections = 20
CompressionLevel = 6
Custom World Settings
[World]
WorldSize = Huge
WorldSeed = 987654321
BiomeDistribution = Balanced
CaveDensity = Medium
OreDensity = Normal
BossFrequency = Normal
Server Security
[Security]
WhitelistEnabled = false
WhitelistFile = "whitelist.txt"
BanFile = "banned.txt"
MaxConnectionsPerIP = 3
AntiCheat = true
LogChat = true
Backup and Maintenance
Automated Backup Script
#!/bin/bash
# backup_corekeeper.sh
SERVER_DIR="/home/corekeeper"
BACKUP_DIR="/home/backups/corekeeper"
DATE=$(date +%Y%m%d_%H%M%S)
MAX_BACKUPS=14
# Create backup directory
mkdir -p "$BACKUP_DIR"
# Save before backup
echo "save" | rcon-cli -H localhost -p 27016 -P your_password
sleep 5
# Create backup
tar -czf "$BACKUP_DIR/corekeeper_backup_$DATE.tar.gz" \
-C "$SERVER_DIR" saves/ configs/
# Clean old backups
ls -t "$BACKUP_DIR"/corekeeper_backup_*.tar.gz | tail -n +$((MAX_BACKUPS + 1)) | xargs -r rm
echo "Backup completed: corekeeper_backup_$DATE.tar.gz"
Maintenance Script
#!/bin/bash
# maintain_corekeeper.sh
SERVER_DIR="/home/corekeeper"
LOG_DIR="$SERVER_DIR/logs"
# Clean old logs
find "$LOG_DIR" -name "*.log" -mtime +7 -delete
# Check disk space
DISK_USAGE=$(df "$SERVER_DIR" | tail -1 | awk '{print $5}' | sed 's/%//')
if [ "$DISK_USAGE" -gt 80 ]; then
echo "Warning: Disk usage is ${DISK_USAGE}%"
# Send notification to admin
fi
# Restart server weekly (Sundays at 4 AM)
if [ $(date +%u) -eq 7 ] && [ $(date +%H) -eq 4 ]; then
echo "Performing weekly restart..."
systemctl restart corekeeper
fi
Mod Support
Installing Mods
Core Keeper supports mods through the Steam Workshop:
# Subscribe to mods in Steam client
# Download mod files
steamcmd +login your_username +workshop_download_item 1963720 mod_id +quit
# Enable mods in server.cfg
[Mods]
Enabled = true
ModDirectory = "mods"
WorkshopMods = "mod_id1,mod_id2,mod_id3"
Popular Mod Categories
- Quality of Life: Inventory management, UI improvements
- New Content: Additional items, weapons, and tools
- Game Balance: Difficulty adjustments and economy changes
- Cosmetic: Visual enhancements and character customization
- Admin Tools: Enhanced server management capabilities
Troubleshooting
Common Issues
Server Not Appearing in Browser
- Check firewall: Port 27015 UDP must be open
- Verify configuration: Check server.cfg for errors
- Network connectivity: Test from different networks
- Steam services: Ensure Steam is running and updated
Connection Timeouts
- Check network stability and latency
- Verify player client version matches server
- Monitor server resource usage
- Check for bandwidth limitations
Performance Issues
- Monitor CPU and memory usage
- Reduce player count if necessary
- Check for corrupted save files
- Update server software regularly
Save File Corruption
- Restore from recent backup
- Check disk space availability
- Verify save file permissions
- Consider increasing save frequency
Log Analysis
Key log files for troubleshooting:
- output_log.txt: Main server log
- Player.log: Player connection logs
- Network.log: Network traffic and errors
- Error.log: Critical errors and exceptions
Best Practices
Security
- Use strong admin passwords
- Regularly update server software
- Monitor player activity
- Keep backups off-site
- Use VPN for remote admin access
Performance
- Monitor server resources regularly
- Optimize configuration for your hardware
- Use SSD storage for better performance
- Limit concurrent connections if needed
- Schedule regular maintenance windows
Community Management
- Establish clear server rules
- Use whitelist for private servers
- Maintain active admin presence
- Regular backups and recovery testing
- Communicate maintenance schedules
Conclusion
Your Core Keeper dedicated server is now ready for underground mining adventures! Regular maintenance, monitoring, and community management will ensure a smooth experience for all players.
Need Help? Join our Discord community for server admin support and share your Core Keeper server stories!