Project Reclaimer Wiki

Community-built environments with new layouts and gameplay spaces for fresh multiplayer experiences.

• Custom arena layouts
• Community multiplayer environments
• Server-specific map rotations

Custom campaign missions and cooperative scenarios that expand the sessions available through Project Reclaimer.

• Custom campaign missions
• Cooperative playthroughs
• Community-authored story content

Player-built maps and gameplay spaces shared through servers or supported Workshop workflows.

• Experimental map designs
• Community-built arenas
• Objective-focused custom layouts

Rules, scripts, and gameplay logic that reshape how a server session plays beyond standard settings.

• Custom objectives
• Special gameplay rules
• Server-specific scripted events

Supported content ships through Steam Workshop with a familiar subscribe-and-update workflow for creators and players.

• Subscribe to published content
• Keep supported items updated
• Organize community releases

Servers provide or advertise the files their maps and modes need, so joining players can acquire missing content automatically.

• Join modded public servers
• Synchronize map and mode dependencies
• Skip manual file setup

Start a solo session, gather around split-screen for local play, or open an online cooperative session for a large group.

• Solo is ideal for learning a mission
• Split-screen keeps everyone on one screen
• Online co-op scales up to 16 players

Pick the Halo 3 campaign mission, then choose the starting point or checkpoint intended for the session.

• Early starts for a full mission run
• Later starts for testing a specific encounter
• Align everyone on the mission before launch

Choose the intended difficulty and apply any campaign modifiers supported by the current setup.

• Difficulty shapes enemy pressure
• Modifiers can change session rules
• Match settings when reproducing results

Place the modification in the supported content location and load it when creating the session.

• Everyone needs compatible content
• Check mission and mod compatibility
• Return to the stock campaign to compare behavior

When a session needs custom campaign content, connected players can fetch the required files before joining the mission.

• Wait for transfers before starting
• Incomplete content blocks entry
• Keep host mission, version, and modifiers consistent

Players can drop into an active campaign through the supported mid-game join flow, where the mission state allows it.

• Joining depends on the current encounter
• New arrivals wait for the session to load
• The host restarts if the session hits an invalid state

A weapon-progression mode where players advance through a sequence of weapons and loadouts as they earn progress.

• Define the progression order
• Track player advancement
• Award the next weapon after each event
• Handle the final state and victory

A mode centered on shifting player power, equipment, and status as the match progresses.

• Track growth levels per player or team
• Apply changes when conditions are met
• Keep HUD state readable
• End the round at the target state

A restricted-ammunition mode built around careful engagements and a limited-resource loop.

• Set the starting ammunition state
• Restore resources on eliminations
• Handle out-of-ammo players
• Use round logic to close the match

A territorial mode where teams convert control of designated areas into score and progress.

• Create and identify active zones
• Detect presence and contesting states
• Award progress while in control
• Rotate or complete the objective by round rules

An infection-style mode where humans face the Flood and the match state flips with every conversion.

• Define the initial role assignment
• Convert players on infection events
• Track humans and Flood remaining
• End on the configured victory condition

JSON provides the structured configuration layer for mode settings, values, object references, and script data.

• Organize names and values by purpose
• Use consistent identifiers
• Validate the structure before loading
• Keep configuration separate from logic

Megalo supplies the gameplay logic that reacts to events, evaluates conditions, and modifies variables to control the match.

• Start from a Slayer-style foundation
• Add player, team, score, and round variables
• Connect events to conditions and actions
• Test each rule independently

Timers, regions, HUD elements, and round controllers are the reusable systems behind objective and custom modes.

• Timers for captures, cooldowns, and limits
• Zones for presence and objective control
• HUD elements for score and status
• Round logic for resets and victory