Colony Survival Server Settings Explained: The Best Config for Your Group

For a private group, run a password-protected SteamOnline server, set maxplayers to your expected peak, begin on Normal difficulty, leave monsters enabled, and keep public listing disabled unless you deliberately want strangers to discover the world. Use local Steam hosting only when the host can stay online; choose a dedicated machine, VPS, Docker deployment, or managed panel for a 24/7 world. Protect RCON with a separate strong password, back up the save before changing world identity or mods, and make every player use the same mod files. The settings below explain what each option does, which ports to open, and how to recover from the mistakes that most often create a new world or an unreachable server.

Which Colony Survival hosting mode should you choose?

The hosting mode determines who can discover the server, how Steam authentication works, and whether the world survives when the host stops playing. Choose it before tuning difficulty or access rules.

Mode	Best use	Important limitation
Singleplayer	Solo play or local testing	Not an internet-facing group server.
LAN	Players on the same local network	Remote friends cannot normally reach it without additional network setup.
SteamLAN	Steam friends on a local or private network	Use it only when your group does not need a generally reachable internet server.
SteamOnline	Friends joining over the internet	Requires the server’s network and firewall configuration to be correct.

The dedicated-server documentation identifies SteamOnline as the internet-facing choice because it uses Steam networking, authentication, and the game’s online connection workflow. A local server is appropriate when the host is playing and can leave the process running. A dedicated PC, VPS, Docker host, or managed service is safer for an always-on world because the game session and server process are independent.

What are the best settings for a private friend group?

Start with a private, passworded Normal world and adjust only after the group has played together. The following presets are starting points, not measured difficulty or performance benchmarks.

Group profile	Difficulty	Monsters	Listing	Hosting	Why it fits
Relaxed builders	None or Low	Enabled unless everyone wants pure construction	Private	Local or managed	Reduces pressure while preserving the option to defend the colony.
Mixed-experience friends	Normal	Enabled	Private or friends-only	SteamOnline, Docker, or managed	A familiar survival pace without the extra pressure of High or Very High.
Experienced survival group	High or Very High	Enabled; double monsters only by agreement	Private or public	Dedicated, VPS, Docker, or managed	Gives a coordinated group stronger attacks and fewer recovery margins.

Monster spawning, daytime attacks, and doubled monster counts are separate controls. Do not assume a higher difficulty automatically changes every monster toggle. Agree on the rules before creating the world, because the documented initial difficulty choices are applied when a new world is created.

How do I install and launch a dedicated server locally?

Steam distributes a separate Colony Survival Dedicated Server tool. It can be launched through a console or graphical interface, but an internet server must use SteamOnline and have the required ports allowed through the host firewall and router.

1. Open Steam’s library tools and install Colony Survival Dedicated Server.
2. Start the server executable through its console or GUI.
3. Set the network type to SteamOnline for friends joining over the internet.
4. Choose a unique server name and world name, then set the seed, player limit, password, and initial settings before generating the world.
5. Allow the documented game and Steam ports on the host firewall and forward the applicable ports on the router.
6. Start the server and have one friend test discovery and joining before you distribute the address or instructions to the whole group.

A local process stops when the computer sleeps, shuts down, loses power, or the server window is closed. If the host will not remain available, move the same configuration to a dedicated machine, VPS, Docker host, or managed panel.

How do I run Colony Survival 24/7 with Docker or a VPS?

The official headless-server workflow uses Docker Compose and is intended for a VPS or NAS. It keeps world data outside the image so replacing the container does not inherently erase the save.

1. Create a folder for the server on the VPS or NAS.
2. Copy docker-compose.yml and server.config.json from gamedata/help/hosting_docker/ in the server distribution into that folder.
3. Review the mounted configuration file. The official workflow treats it as read-only, so make changes there rather than editing files inside a running container.
4. Start the service with

   docker compose up -d

5. Check the container log for world creation or loading, then test a connection from outside the VPS network.
6. Schedule backups of the host directory that contains the mounted world data, not merely the disposable image.

The published image is pipliz/colony-survival-dedicated-server:latest. The guide’s configuration model uses NewOptions to create a world; if the configured WorldName already exists, that operation becomes a load-world operation. When NewOptions is omitted, use LoadOptions with the same world name. This distinction prevents a restart from unexpectedly generating a different save.

How do seed and difficulty keys work in Docker?

DifficultyKey selects a preset by index from gamedata/settings/server.json. A seed can be written as text or an integer in the Docker configuration; the server hashes text seeds when generating a world. Keep the seed and world name in your records so a rebuild can reproduce the intended new-world setup.

What settings do managed server panels expose?

Managed panels present the core configuration as form fields, which is useful when you do not want to maintain Steam, Docker, and firewall services yourself. Stop the server before editing when the provider requires it, save the changes, and restart before testing.

• Server name and world name
• Seed
• Valve Anti-Cheat toggle
• Monster spawning and double-monster options
• Initial difficulty settings
• Maximum players
• Server password
• RCON password

World identity follows the configured world name. If you replace it with a name that does not already exist, the panel can create a new world instead of loading the old one. Back up the save and verify the exact spelling before applying a world-name change.

Which ports does a Colony Survival server use?

The documented defaults are UDP 27004 for the game/server-browser query and TCP 27005 for the Steam connection port. Additional Steam API traffic may require UDP 3478, 4379, and 4380, and Steam can select a random port from 27005 through 65535 while establishing connections.

Option or service	Documented default or value	Use
+server.gameport	27004	Port queried for server-browser information; documented as UDP.
+server.steamport	27005	Primary Steam connection port; documented as TCP.
Steam API	3478, 4379, 4380	UDP ports that may be required by Steam networking.
Steam connection range	Random port between 27005 and 65535	Can appear during connection establishment, depending on Steam’s behavior.

Open only the ports your chosen network mode and host require. Confirm protocol, router forwarding, and firewall rules on the actual machine; the game or Steam can change connection behavior, and a port that is open on the router but blocked locally still produces a failed join.

What command-line options should you set?

These are the documented options and defaults. Values marked as defaults apply to a fresh configuration or new world where the documentation specifies that scope.

Option	Documented value	Configuration effect
+server.networktype	Singleplayer, LAN, SteamLAN, or SteamOnline	Chooses the connection and discovery model.
+server.maxplayers	10 by default	Sets the connection ceiling; choose the expected peak rather than an aspirational number.
+server.gameport	27004 by default	Sets the game/server-browser query port.
+server.steamport	27005 by default	Sets the primary Steam port.
+server.password	No password by default	Protects entry to a private server.
+server.ip	0.0.0.0 by default	Lets the server select an available network adapter automatically.
+server.usevac	false by default	Controls Valve Anti-Cheat when supported by your setup.
+server.seed	Integer for a new world; text is supported in the Docker workflow	Determines generated terrain for a new world.
+server.monsterson	true by default for new worlds	Enables monster spawning.
+server.initialsettings	normal by default for a new world	Selects the initial difficulty preset.
+server.monstersday	false by default	Controls whether monsters can spawn during the day.
+server.monstersdouble	false by default	Controls doubled monster amounts.

How do I choose difficulty and monster settings?

The documented difficulty scale runs from 0 to 4, with day and night selected separately. Initial difficulty is applied after a new world is created, so decide before generating the shared save.

Value	Label	Practical starting use
0	None	Construction-focused groups that want no standard threat pressure.
1	Low	New players or groups prioritizing experimentation.
2	Normal	Recommended first shared survival setting.
3	High	Coordinated groups seeking stronger attacks.
4	Very High	Experienced groups that accept a narrow recovery margin.

Separate controls cover whether monsters spawn at all, whether they appear during daylight, and whether their amount doubles. The available documentation does not provide a measured relationship between these values and server performance or player skill, so treat the presets as editorial starting points rather than tested benchmarks. If players disagree, Normal with monsters enabled and doubled monsters disabled is the least disruptive compromise.

How do I set a password, whitelist, and RCON safely?

A private server has no password by default, so set one before sharing the server name. Use a different, long password for RCON and expose RCON only when administration requires it.

1. Set +server.password or the panel’s server-password field to a value that is not reused for Steam, email, or the host machine.
2. Keep listing visibility private or friends-only while the group is testing the world.
3. Enable RCON only if you need remote administration, then set a separate strong RCON password and restrict access through the host firewall.
4. Use the documented permission roles and /setgroup command to grant elevated powers only to named administrators.
5. Maintain the world’s permission files and record who can alter permissions, difficulty, or save files.
6. Use whitelist and blacklist commands when a password alone is not enough to control membership.

For public or semi-public servers, the Docker configuration exposes ServerListPublicly, ServerListLAN, and ServerListFriends. Decide whether discovery should happen through the master server, local-network discovery, Steam friends, or a combination, and review that choice whenever the membership changes.

How many players can a Colony Survival server support?

The documented maxplayers default is 10, and the server lets you change that ceiling. No supplied source publishes a reliable player-count, hardware, or colonist-performance benchmark, so there is no evidence-based “optimal” capacity number beyond your group’s expected peak.

Set the limit to the highest number of simultaneous players you genuinely expect, then increase it only after observing the world under normal activity. A lower limit prevents accidental overbooking and makes resource planning easier; a higher limit does not guarantee smooth performance. Record the host hardware, world size, mod list, and player count if you run your own capacity tests so later changes are comparable.

How do I change difficulty after creating a world?

Initial settings are designed for world creation. Changing a panel field or startup option may not retrofit the existing save, so do not assume a restart alone will convert a live world.

1. Stop the server and make a complete copy of the world’s save directory.
2. Check whether the host or panel documents an in-place setting change for the specific option.
3. If the option is an initial-world setting, create a test world with the new value and verify the result before touching the shared save.
4. Keep the original world name and backup untouched until every player confirms the replacement behaves as intended.
5. Document the final difficulty and monster toggles so a future rebuild uses the same values.

For a group that wants a harder challenge without risking its main colony, create a separate world with a different name and compare the experience there first.

How do mods work on a dedicated server?

Workshop mods require manual download and activation on the dedicated server. Every player should load the same mod files and versions; a mismatch can prevent joining or create inconsistent behavior.

1. Agree on a mod list and version set before installing anything.
2. Download the Workshop content to the server installation as described by the dedicated-server documentation.
3. Enable the selected mods in that world’s modstate.json.
4. Back up the world before adding, removing, or updating a mod.
5. Apply updates during a maintenance window, then have one test player join before reopening the server.

Keep a plain-text inventory of mod names, versions, activation order if relevant, and the date of the last update. If a player cannot join after a change, compare that inventory first rather than regenerating the world.

What should you back up before changing server settings?

Back up the world before changing its name, initial settings, permissions, or mods. World identity is tied to the configured name, and a new name can create a separate save that looks like lost progress.

• Copy the complete world save directory while the server is stopped.
• Keep at least one backup outside the server’s data directory or container mount.
• Record the world name, seed, network type, player limit, difficulty values, monster toggles, passwords’ storage location, and mod versions.
• Label backups with the date and the change that preceded them.
• Test restoring a backup on a separate instance before you need it in an emergency.

Why can friends not find or join my server?

Most connection failures come from a mismatch between network type, listing visibility, ports, firewall rules, and passwords. Work through the checks in order instead of changing several settings at once.

1. Confirm the server is running and set to SteamOnline for internet friends.
2. Verify that the server name, world name, password, and player limit are the values you intended.
3. Check that UDP 27004, TCP 27005, and any required Steam API UDP ports are allowed on both the host firewall and router.
4. Confirm the router forwards to the correct local IP address; a changed DHCP address can invalidate an old rule.
5. Review listing controls: a server hidden from public, LAN, and friends lists may still be reachable only through the connection method you configured.
6. Test from a network outside the host’s LAN, because a local test can succeed even when internet forwarding is broken.
7. Compare each player’s mod files and versions before changing the world or reinstalling the server.

What is a reliable 24/7 maintenance routine?

A small, repeatable routine prevents most avoidable outages and save mistakes.

• Before every restart, confirm the intended world name and configuration file.
• Keep the server software, Docker image or managed-panel template, and mod list on a written update schedule.
• Back up the world before updates and retain a known-good previous copy.
• Use a maintenance window for mod or difficulty experiments.
• Review RCON and administrator membership periodically.
• Check container or server logs after startup for a load-world message and expected network mode.
• Ask a player to verify joining after changes, then record the result and date.

This approach lets a group keep a stable main colony while testing new settings in a disposable world.

Frequently Asked Questions

Can I run the dedicated server and play on the same computer?

Yes. A local dedicated process can run alongside the game, but the computer must remain powered, connected, and free to run the server. Closing the server process or putting the machine to sleep makes the world unavailable to everyone else.

Does changing the seed regenerate an existing Colony Survival world?

No. The seed is used when a new world is generated. Keep the existing world name and save if you want to preserve progress; use a different world name to test another seed safely.

Can I make a private server temporarily public?

You can change the listing controls for the master server, LAN discovery, or Steam friends discovery, then restart or reload as required by the host. Keep the password and review administrator permissions before opening discovery to people outside your group.

Are there published hardware requirements for a specific player count?

The available documentation does not publish a verified hardware-to-player or colonist-performance table. Treat the default limit of 10 as a configuration default, not a performance guarantee, and measure your own host with the exact world and mod set you plan to use.