- Project Reclaimer Linux hosting uses Docker for a repeatable, isolated dedicated server deployment.
- Docker separates the server runtime from maps, mods, and logs for cleaner updates.
- RCON enables remote administration without touching the host machine.
- Port forwarding and firewall rules are mandatory before public sessions work.
- Anti-cheat and admin lists should be configured before opening your server to players.
Why Run Project Reclaimer Linux Servers?
Project Reclaimer is a standalone Halo 3 PC multiplayer project built on your own Steam installation of Halo: The Master Chief Collection. While most players join sessions through the client's server browser, hosts who want a persistent community server can deploy the dedicated server package on Windows, Windows Server, or Linux. The Linux Docker route is the cleanest option for repeatable deployments and container-level restart management.
Official deployment guidance is available on the Project Reclaimer hosting page, and release files are published on the official releases repository.
Windows
- Manual installation
- Local testing
- Direct file access
Windows Server
- Persistent hosting
- Scheduled maintenance
- Service-based operation
Linux Docker
- Repeatable deployment
- Isolated dependencies
- Container restart policies
Choose the Linux Docker path when you plan to run the server long-term, want crash recovery handled by a restart policy, or need to redeploy the same configuration quickly on a fresh host.
| Platform | Best For | Recovery | Update Workflow |
|---|---|---|---|
| Windows | Local testing, first-time hosts | Manual restart | Manual file replacement |
| Windows Server | Persistent community hosting | Service manager | Scheduled maintenance |
| Linux Docker | Containerized, repeatable hosting | Restart policy | Rebuild or replace container |
Project Reclaimer Linux Deployment: Step by Step
The deployment process mirrors the official dedicated server workflow, adapted for a Linux host running Docker. Follow each stage in order, because later steps such as RCON management depend on the network configuration you set earlier.
Choose a deployment environment
Confirm your Linux host meets your operational needs. Docker provides isolated dependencies and container-level management, which suits both single servers and multi-server hosts. Record the host specifications and the release version you install for troubleshooting later.
Install the server runtime and release files
Download the appropriate Project Reclaimer server release from the official releases page. Extract it into a dedicated directory, and keep executable files separate from user-generated maps, mods, and logs. Back up configuration files before any upgrade.
Configure the server and network ports
Edit the server configuration with your session settings, bind address, query or administration settings, and required ports. Allow those ports through the host firewall, forward them on your router if behind NAT, and restart the server after any network change.
Add maps and mods
Place supported map files and mod content in the directories the server expects, then reference the intended content in the configuration. Use separate locations for base maps and custom content when supported, and reload the server after adding anything new.
Set administrators, anti-cheat, and bans
Configure the administrator list with unique identifiers, grant access only to trusted operators, and enable available anti-cheat protections before opening the server publicly. Maintain a ban list for disruptive players.
Enable automatic restart and health checks
Run the server under a container restart policy or process supervisor so it recovers from crashes and reboots. Capture console output and logs, use scheduled restarts for maintenance, and verify the server returns to its intended map and settings after recovery.
Manage the server with RCON
Use the RCON tool for remote monitoring, map changes, kicks, and bans. Restrict RCON access to trusted networks, use a strong password, and test commands before relying on unattended operation.
Avoid assigning ports already used by other game servers or administration tools on the same host. A port conflict is one of the most common reasons a freshly configured server fails to appear in the server browser.
Configuration Reference and Security
A well-configured server separates runtime files from content, locks down remote administration, and survives crashes. Use the tables below as a pre-launch reference.
| Config Area | Key Setting | Recommended Practice |
|---|---|---|
| Bind address | Network interface | Bind only to intended interfaces |
| Firewall | Game and query ports | Allow only required ports |
| Admin list | Unique identifiers | Trusted operators only |
| Anti-cheat | Enabled for public play | Keep enabled on public sessions |
| Ban list | Persistent record | Maintain and review regularly |
| RCON Practice | Why It Matters |
|---|---|
| Strong password | Prevents unauthorized control |
| Trusted-network restriction | Reduces exposure surface |
| Command testing | Confirms behavior before unattended use |
| Post-action log review | Creates an audit trail |
Pre-Launch Checklist:
- Dedicated server directory created and version recorded
- Ports allowed through firewall and forwarded if behind NAT
- Maps and mods placed in expected directories
- Administrator list and anti-cheat configured
- Restart policy and logging verified
- RCON tested with a strong password
Official documentation lists dedicated server support with up to 127 server slots, giving Linux hosts substantial headroom for large community sessions.
Maps, Mods, and Content Sync on Linux
Project Reclaimer handles custom content through server-side sharing and Steam Workshop support. When players join a server using maps or mode scripts they do not have installed, the client can obtain the missing files before the session starts, which keeps Linux-hosted sessions synchronized without manual file distribution.
| Content Type | Distribution Method | Host Responsibility |
|---|---|---|
| Map mods | Server-side sharing, Workshop | Install before advertising session |
| Campaign mods | Server or client download | Verify version compatibility |
| Forge content | Server sharing or Workshop | Confirm mode compatibility |
| Mode scripts | Server-identified download | Reference in server config |
Install and test custom content on the server before listing the session publicly. Restart or reload after adding content so the server advertises the correct map and mode to the browser.
Troubleshooting and FAQ
The official Discord, linked from the Project Reclaimer homepage, is the primary channel for development updates, bug reports, and hosting questions.
Q: Does Project Reclaimer support Linux dedicated servers?
Yes. The official hosting documentation lists Linux deployment through Docker alongside Windows and Windows Server, making containerized hosting a supported path for persistent Project Reclaimer servers.
Q: Do I need Halo: The Master Chief Collection installed on the Linux server?
The client workflow requires a Steam installation of Halo: The Master Chief Collection with Halo 3 content on the player's PC. Follow the official host documentation for the exact content requirements placed on the dedicated server itself.
Q: How do players get custom maps when joining my Linux server?
Project Reclaimer supports server-side content sharing. When a joining player is missing required files, the client can download them automatically via the server or Steam Workshop, then reconnect if a restart is requested.
Q: How many players can a Project Reclaimer server handle?
Official documentation lists support for up to 128 players in a session and dedicated server packages with up to 127 slots, along with campaign co-op for up to 16 players.