Managing server access is essential for any Conan Exiles community run, and the whitelist is the primary tool for controlling who joins your world. This guide explains how to set up and maintain a whitelist so your tribe can play safely with trusted players.
Whitelisting changes the default open-door policy into a permission-based system, helping reduce trolling, griefing, and unauthorized base access. The following sections break down setup steps, server commands, troubleshooting, and real-world policies that teams commonly use.
Server Configuration Overview
Understanding the core parameters makes it easier to maintain a stable whitelist across restarts and updates.
| Setting | Values | Effect on Whitelist | Recommended for Trusted Servers |
|---|---|---|---|
| Server Whitelist | Enabled / Disabled | Blocks players not on the list from joining | Enabled |
| Admin Account | Owner-built or external | Required to add and remove whitelist entries | Dedicated admin account |
| Max Player Slots | 12 / 24 / 48 | Controls how many whitelisted players can be online simultaneously | Match to tribe size |
| Save Interval | 30s / 60s / 120s | Determines how often roster changes are persisted | 60s |
| Server Join Delay | 0s / 5s / 10s | Reduces rapid join attempts that could bypass checks | 5s |
Preparing to Enable Whitelist
Before turning on the whitelist, prepare your admin credentials and collect the Steam IDs of every player who should have access.
Use the in-game console or server control panel to verify that remote admin access is secured with a strong password and two-factor authentication where available.
Gathering Steam IDs
Ask each approved player to visit steampowered.com and copy their Steam64 ID, or use server commands that log this automatically when they first join in open mode.
Enabling and Managing the Whitelist
Once the list is ready, you can enable the whitelist and start adding entries using precise command syntax.
Adding and Removing Players
Use server console commands to add or revoke access, and keep a small log file to track changes over time.
Surviving Server Restarts
Because the whitelist persists with server saves, regular backups help you recover player slots if an update or crash alters the roster.
Server Policies and Tribe Governance
Many tribes combine the whitelist with clear rules about sharing accounts, base access, and trade etiquette to keep the community stable.
Document these policies on your server description and in a shared notes file so new applicants understand expectations before receiving a slot.
Best Practices for Long-Term Server Health
Using the whitelist strategically supports a stable, low-conflict environment where trusted players can focus on building and exploration.
- Collect Steam IDs before approving any player entry.
- Keep a backup whitelist file after every major update.
- Set a reasonable max player slot count to avoid overcrowding.
- Document rules and enforcement steps on the server page.
- Review the roster monthly and remove inactive accounts.
FAQ
Reader questions
How do I add a player to the whitelist?
Enter the command "whitelist add " in the server console, save the config, and restart the server session if required.
Can I temporarily ban a whitelisted player?
Yes, remove their ID from the list or use in-game mute and jail structures, then re-add them later when needed.
What happens to a player if the whitelist is disabled?
Anyone can join the server, so it is best to disable the whitelist only during maintenance or special events.
Why do some players still fail to join after being added?
Check for duplicate Steam IDs, verify max player slots, review server logs for connection errors, and ensure the client version matches the server.