Cooperative Horror

A player steps through darkness with a flashlight raised, scanning the ground for dropped matches while listening for approaching footsteps. A roaming AI ghost picks up the trail, shifting from patrol behavior into an aggressive pursuit that forces the team to scatter or retaliate with salt. Cooperative Horror establishes this survival scenario through a modular, Blueprint-driven framework constructed for multiplayer sessions, solo trials, and dedicated server environments.

AI Ghost Encounters and the Altar Objective

The primary gameplay loop in Cooperative Horror centers on an objective-based survival encounter scaled for one to four players. Rather than relying on simple evasion alone, sessions require players to actively track down items scattered throughout the environment to secure a victory. The main win condition requires locating matches and using them to set fire to all altars positioned across the map.

Opposing the players are fully replicated AI ghosts. These hostile entities navigate the map independently, searching corridors and open clearings. When an AI ghost spots a human target, it switches from passive roaming to active chasing, closing the distance to execute physical attacks. Players caught without defensive measures must quickly break line of sight or rely on team coordination to survive.

To defend themselves, players can equip and throw salt directly at the ghosts. Landing a salt throw banishes the entity, interrupting the assault and granting the group a brief window to regroup, revive, or search for remaining altars. This creates a push-and-pull rhythm between scouring dark corners for matches, managing limited defensive consumables, and committing to the vulnerable animation of igniting an altar.

Dedicated Server Architecture and Lobby Controls

Multiplayer networking runs across both listen servers and dedicated servers, giving projects the flexibility to support peer-to-peer matchmaking or centralized game hosting. Every critical action—including inventory pickup, ghost banishment, and altar state changes—is handled through full network replication so that clients remain synchronized during high-stress encounters.

Session onboarding begins in the main menu, where players interface with a dedicated menu widget, adjust game settings, or browse available servers through an integrated server browser. Once connected, participants enter a pre-game lobby that handles the operational setup before a match begins:

• Character Selection: Players lock in specific survivor models prior to loading into the level.
• Host Controls: The hosting player maintains authority over session configuration, including the ability to kick players from the lobby.
• Lobby Chat: Text communication allows participants to coordinate roles, strategies, or server rules prior to launch.

True First Person, Third Person, and Spectator Camera Perspectives

Visual presentation is configured to support both true first-person and third-person camera views. The true first-person perspective aligns the camera directly with the player character mesh, ensuring that hand movements, held items, and body motions remain physically grounded in the world. Looking down reveals the character's limbs, anchoring the sense of vulnerability during ghost chases. For projects seeking an action or adventure horror presentation, the third-person camera offers broader peripheral visibility and an unobstructed view of survivor animations.

When an investigator falls during an encounter, the template does not force a hard disconnect or static screen. A built-in spectator mode activates, allowing downed participants to cycle through surviving teammates. This keeps eliminated players engaged in the outcome of the match while monitoring remaining altar counts and teammate positions.

In-Game Widgets, Flashlights, and Audio Notes

Once inside a match, information is delivered through an integrated user interface and contextual environmental tools. A specialized teammates widget stays visible on screen, showing player statuses so teammates can monitor who is actively working on objectives, who is wandering alone, and who requires immediate assistance. Text chat continues during active gameplay, enabling silent communication when voice options are not in use.

Exploration tools include a functional flashlight system, serving as the primary visual aid in dark interior and exterior spaces. Item interaction logic covers pickups for consumable defenses like salt pouches and matches needed for the altars.

Environmental storytelling is supported through two native item types:

• Text Notes: Readable pages that open in-game, allowing developers to communicate map lore, instructions, or codes.
• Audio Notes: Recorded audio logs that trigger playback upon pickup or interaction, delivering spoken narrative or ambient warnings.

Cursed Forest Map and Blueprint Layout

The framework supplies two distinct environments out of the box: a clean test level and the Cursed Forest demo level. The test level acts as a sterile staging ground where developers can isolate mechanics, test AI navigation bounds, check item respawns, and verify replication behavior without dense environmental props. The Cursed Forest level demonstrates a complete production environment, placing altars, roaming ghost paths, note placements, and item pickups into an atmospheric woodland setting.

Under the hood, the entire logic is built in clean, commented Blueprints. Node networks are grouped and annotated so creators can trace execution paths for matchmaking, player damage, ghost states, and inventory handling. This makes it straightforward to modify ghost speed, altar ignition times, or consumable drop rates without untangling complex logic dependencies.

The template also holds compatibility with Plug and Play Shooter AI, opening a path for creators who wish to expand beyond ghost banishing mechanics into combative horror or hybrid shooter frameworks.

Production Utility

Cooperative Horror serves teams seeking an immediate, fully functional cooperative loop without spending months establishing server browsers, character selection screens, and ghost replication systems. Because the objective flow, spectator views, AI patrols, and item pickups are fully interconnected in Blueprints, developers can treat the package as an operational production base, swapping in custom survivor meshes, audio files, and monster models to bring a unique survival horror vision to life.

More From The Same Workflow

• Asymmetric Multiplayer Horror
• Thief Simulator Starter Kit
• Modern Survival Horror Framework
• Advanced Survival Horror
• Classic Survival Horror Framework V2