Pick the brief that lets you prove networked third-person movement, interaction, ability use, ping, revive, ready state, and session leave or rejoin or follow state through session lifecycle, server authority, replicated inventory, shared objective state, latency feedback, revive rules, reconnect policy, and completion ownership. Every Unreal Multiplayer Co-op Game Maker CTA carries the Unreal engine, this source page, its intent, and campaign attribution into the same generation workflow.
Playable vertical slice
Generate Unreal Multiplayer Co-op Game Maker as a native Unreal 5 slice: two players join a session, carry separate power cells, activate paired switches, defend a shared objective, revive once, and extract together. Place it in an original two-player sci-fi relay station with split routes, a central defense platform, paired consoles, and a shared extraction lift. The build passes only when host and client observe the same objective state, duplicated items are impossible, late actions resolve predictably, disconnects do not corrupt progress, and both players receive completion. Return the Unreal Multiplayer Co-op Game Maker browser preview, performance notes, packaged output, and native project for download.
Use this promptControls and camera
Greybox an original two-player sci-fi relay station with split routes, a central defense platform, paired consoles, and a shared extraction lift around these player inputs: networked third-person movement, interaction, ability use, ping, revive, ready state, and session leave or rejoin. For the Unreal Multiplayer Co-op Game Maker movement and interaction pass, record the pass and failure evidence; delay visual polish until failure and restart behavior is clear.
Use this promptStateful game systems
Represent session lifecycle, server authority, replicated inventory, shared objective state, latency feedback, revive rules, reconnect policy, and completion ownership as observable state in the Unreal Multiplayer Co-op Game Maker project. Connect each transition to two players join a session, carry separate power cells, activate paired switches, defend a shared objective, revive once, and extract together, expose it in the browser build, and mark the Blueprint, C++, asset, or configuration assumption that still needs editor inspection.
Use this promptRegression and packaging
Run a regression build for small teams proving a cooperative loop before scaling networking scope. Prove that host and client observe the same objective state, duplicated items are impossible, late actions resolve predictably, disconnects do not corrupt progress, and both players receive completion, then deliberately trigger this risk: a local two-window demo can conceal authority bugs, latency sensitivity, race conditions, reconnect failures, or dedicated-server differences. Preserve a rollback point, repeat the same test, and return the unreal multiplayer co-op game maker browser preview, performance notes, packaged output, and native project for download.
Use this prompt