Pick the brief that lets you validate networked first-person movement, aim, fire, reload, inventory transfer, interact, ping, heal, mission-item pickup, call extraction, spectate, and leave or follow state through session authority, spawn, replicated loot ownership, inventory transactions, mission item, AI patrol, damage, down or death policy, extraction timer, stash commit, reconnect rule, and raid cleanup. Every Unreal Extraction Shooter Game Maker CTA carries the Unreal engine, this source page, its intent, and campaign attribution into the same generation workflow.
Playable vertical slice
Assemble Unreal Extraction Shooter Game Maker as a native Unreal 5 slice: two players enter a flooded industrial district, find one mission item, choose between two loot routes, survive an enemy patrol, call extraction, defend the zone, and return or lose carried gear. Place it in an original flooded industrial district with warehouse route, elevated rail route, mission archive, patrol yard, flare-lit extraction pier, and distant storm. The build passes only when loot has one owner, the mission item follows declared death rules, extraction commits once, failed players receive no invalid stash items, reconnect follows policy, and the next raid has no stale state. Preview the Unreal Extraction Shooter Game Maker result in a browser, measure its risky path, package it, and keep the Unreal project downloadable.
Use this promptControls and camera
Greybox an original flooded industrial district with warehouse route, elevated rail route, mission archive, patrol yard, flare-lit extraction pier, and distant storm around these player inputs: networked first-person movement, aim, fire, reload, inventory transfer, interact, ping, heal, mission-item pickup, call extraction, spectate, and leave. For the Unreal Extraction Shooter Game Maker movement and interaction pass, make the result inspectable; delay visual polish until failure and restart behavior is clear.
Use this promptStateful game systems
Represent session authority, spawn, replicated loot ownership, inventory transactions, mission item, AI patrol, damage, down or death policy, extraction timer, stash commit, reconnect rule, and raid cleanup as observable state in the Unreal Extraction Shooter Game Maker project. Connect each transition to two players enter a flooded industrial district, find one mission item, choose between two loot routes, survive an enemy patrol, call extraction, defend the zone, and return or lose carried gear, 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 shooter teams testing authoritative raid state, loot risk, objectives, extraction, death, and persistence. Prove that loot has one owner, the mission item follows declared death rules, extraction commits once, failed players receive no invalid stash items, reconnect follows policy, and the next raid has no stale state, then deliberately trigger this risk: a small raid cannot prove production matchmaking, backend durability, anti-cheat, fraud prevention, regional latency, economic balance, moderation, live operations, or service cost. Preserve a rollback point, repeat the same test, and preview the unreal extraction shooter game maker result in a browser, measure its risky path, package it, and keep the unreal project downloadable.
Use this prompt