This guide covers server administration and mod installation for Colony Survival, including admin setup, console commands, player management, Steam Workshop and manual mod installation, colony management tips, and troubleshooting common server issues.
Prerequisites: This guide assumes your server is already running. If you need to set up your server first, start with the Colony Survival Server Setup Guide.
Admin Setup
Colony Survival uses a permission system where the server owner (the player who created the world) has full control. For dedicated servers, admin privileges are managed through configuration.
Setting Up Admin Access
- Stop your server from GPanel.
- Open the File Manager and locate your server configuration files.
- In
serverconfiguration.jsonor the relevant permissions file, add your Steam64 ID to the admin/operator list. You can find your Steam64 ID at steamid.io. - Save the file and start your server.
World Owner: The first player to create a colony on the server typically has owner-level permissions for that colony. On a dedicated server, the admin configuration file determines who has server-wide administrative control.
Server Console Commands
Colony Survival provides console commands that can be executed from the server console in GPanel or through in-game chat (if you have admin privileges). Access the GPanel console from the Console tab.
| Command | Syntax | Description |
|---|---|---|
| Help | /help |
Displays a list of all available server commands. |
| Kick | /kick [PlayerName] |
Removes a player from the server immediately. They can reconnect unless banned. |
| Ban | /ban [PlayerName] |
Permanently bans a player. They will be unable to connect to the server. |
| Unban | /unban [PlayerName] |
Removes a ban, allowing the player to reconnect. |
| Save | /save |
Forces an immediate world save. Use before maintenance or restarts. |
| List Players | /players |
Shows all currently connected players. |
| Say | /say [Message] |
Broadcasts a server message visible to all players. |
| Shutdown | /shutdown |
Gracefully shuts down the server, saving the world before stopping. |
Console Command Examples
/help
/players
/kick Griefer123
/ban Griefer123
/unban Griefer123
/say Server restarting in 5 minutes, please save your progress!
/save
/shutdown
Tip: Always run
/save before /shutdown to ensure the latest progress is preserved. While /shutdown typically triggers an auto-save, an explicit save beforehand provides extra safety.
Player Management
Kick and Ban
Use kick and ban commands to manage disruptive players:
- Kick: Use
/kick [PlayerName]for minor or first-time offenses. The player can rejoin immediately. - Ban: Use
/ban [PlayerName]for severe or repeated offenses. The player is permanently blocked from connecting. - Unban: Use
/unban [PlayerName]to reverse a ban if circumstances change.
Monitoring Players
- Use
/playersto see who is currently connected. - Watch the Console tab in GPanel for join and disconnect messages.
- Colony Survival is cooperative by nature, but on public servers, players could potentially grief by mismanaging shared resources or colony defenses.
Best Practices
- Establish clear server rules and communicate them to players.
- Use
/sayto broadcast important announcements (maintenance windows, rule reminders). - Keep a log of kicks and bans for reference.
- For private servers, use a password in
serverconfiguration.jsonto restrict access to trusted players only.
Mod Installation
Colony Survival has an active modding community. Mods can add new content, change gameplay mechanics, introduce new colonist jobs, and much more.
Steam Workshop Integration
Colony Survival supports Steam Workshop mods. To install Workshop mods on your server:
- Find the mod you want on the Colony Survival Steam Workshop.
- Note the Workshop ID from the mod's URL (the number in the URL, e.g.,
https://steamcommunity.com/sharedfiles/filedetails/?id=123456789-- the ID is123456789). - In GPanel, check the Startup tab for a Workshop ID field or mod configuration option. Add the Workshop IDs of the mods you want to install, separated by commas if multiple.
- Restart your server. SteamCMD will download the Workshop mods automatically during startup.
Client-Side Mods: Players connecting to a modded server may need to install the same mods on their client. Check each mod's description for whether it is server-only or requires client installation.
Manual Mod Upload
If a mod is not on the Steam Workshop, or you need to install a custom version, you can upload mods manually:
- Stop your server from GPanel.
- Download the mod files to your local machine.
- Connect to your server via SFTP or use the File Manager.
- Navigate to the mods directory. Colony Survival mods are typically placed in:
gamedata/mods/ - Upload the mod folder into the
modsdirectory. Ensure the folder structure matches what the mod author specifies. - Start your server. Check the console for messages confirming the mod loaded successfully.
Mod Compatibility: Always check that mods are compatible with your server's game version. Outdated mods can cause crashes or world corruption. Back up your save before installing new mods.
Removing Mods
- Stop your server from GPanel.
- Remove the mod folder from the
gamedata/mods/directory, or remove the Workshop ID from the startup configuration. - Start the server and verify it loads correctly without the mod.
Warning: Removing mods that added blocks, items, or colonist jobs to your world may cause errors or world corruption. Always create a backup before removing mods.
Colony Management
Running a Colony Survival server with multiple players requires some coordination. Here are tips for managing shared and individual colonies:
- Shared Colonies: Multiple players can contribute to the same colony. Coordinate building, resource gathering, and defense placement to avoid overlapping or conflicting builds.
- Separate Colonies: Players can also establish their own independent colonies in different locations. This reduces potential conflicts but means each colony must sustain its own defenses.
- Resource Management: Large colonies with many colonists consume significant resources. Ensure supply chains (food, tools, weapons) are well-organized to prevent colonist starvation or defense gaps.
- Defense Planning: Nightly monster attacks scale with colony population. As your colony grows, invest in walls, guard towers, and armed colonists to maintain safety.
- Performance: Very large colonies with thousands of colonists can strain server resources. Monitor server performance and consider setting reasonable colony size limits for public servers.
Troubleshooting
Server Crashes
| Problem | Solution |
|---|---|
| Server crashes on startup | Check the GPanel console for error messages. Verify serverconfiguration.json is valid JSON (no missing commas, mismatched brackets). Try removing recently added mods. If the issue persists, reinstall the server files from GPanel. |
| Server crashes during gameplay | This may indicate memory exhaustion from a very large colony, or a mod conflict. Check the console logs for error details. Reduce colony size or remove problematic mods. |
| Crash after game update | Game updates may break mod compatibility. Disable all mods, restart, and re-enable them one by one to identify the conflict. Check mod pages for update notes. |
Connection Issues
| Problem | Solution |
|---|---|
| Server not showing in browser | Ensure the server is running in GPanel and NetworkType is set to "SteamNetwork". The server may take a few minutes to register with the Steam master server after starting. |
| Cannot connect via direct IP | Verify the IP and port in GPanel. Make sure you are using the game port (not the query port). Confirm the server status is Running. |
| Frequent disconnections | This may indicate network instability or server overload. Check server resource usage in GPanel. Large colonies generating lots of terrain can cause network issues for players with slow connections. |
| "Version Mismatch" error | The server and client must be on the same game version. Restart the server from GPanel to trigger an update. Players must also update their game via Steam. |
Mod Conflicts
| Problem | Solution |
|---|---|
| Server crashes after adding a mod | Remove the mod, restore from backup if needed, and check the mod's compatibility notes. Some mods conflict with each other or require specific load orders. |
| Missing items or blocks after mod removal | If a mod added custom content to the world, removing it can leave orphaned references. Restore from a pre-mod backup, or accept the missing items. There is no way to recover mod-specific content without the mod. |
| Mods not loading | Verify the mod folder structure is correct in gamedata/mods/. Check the console for load errors. Ensure the mod version matches your game version. |
World Corruption
| Problem | Solution |
|---|---|
| World fails to load | The save file may be corrupted. Restore from the most recent backup. If no backup exists, you may need to start a new world. |
| Missing chunks or terrain glitches | This can happen after crashes during saves. Try loading the world; minor corruption may self-repair. For persistent issues, restore from backup. |
Performance with Large Colonies
| Problem | Solution |
|---|---|
| Server lag with many colonists | Very large colonies (1000+ colonists) require significant server resources. Optimize colony layout, reduce unnecessary colonist jobs, and ensure adequate RAM is allocated to your server plan. |
| Auto-save causes lag spikes | Increase the AutoSaveInterval in serverconfiguration.json to reduce save frequency. A value of 20-30 minutes reduces the impact while still providing reasonable protection. |
| Slow terrain generation | When players explore new areas, the server must generate terrain. This is normal but can cause brief lag. Encourage players to explore gradually rather than rushing across the map. |
Related Articles
- Colony Survival Server Setup Guide
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Getting Started with Your New Server
Need Help? If you are experiencing issues not covered here, please open a support ticket and our team will help resolve them.
