Pick the brief that lets you prove top-down or third-person movement, attack, dodge, ability use, interaction, upgrade choice, map view, and run restart or follow state through seed management, room graph, encounter spawning, loot tables, upgrade synergies, run state, death cleanup, meta unlocks, and deterministic replay logs. Every Unreal Roguelike 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 Roguelike Game Maker as a native Unreal 5 slice: enter a seeded dungeon, clear three room types, choose one of two upgrades, defeat an elite, die or extract, and begin a visibly different next run. Place it in an original subterranean archive with modular chambers, branching doors, ritual hazards, an elite arena, and a protected extraction room. The build passes only when the same seed reproduces the same route, a different seed changes meaningful choices, death clears transient state, rewards respect tables, and upgrades alter combat observably. Return the Unreal Roguelike Game Maker browser preview, performance notes, packaged output, and native project for download.
Use this promptControls and camera
Greybox an original subterranean archive with modular chambers, branching doors, ritual hazards, an elite arena, and a protected extraction room around these player inputs: top-down or third-person movement, attack, dodge, ability use, interaction, upgrade choice, map view, and run restart. For the Unreal Roguelike 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 seed management, room graph, encounter spawning, loot tables, upgrade synergies, run state, death cleanup, meta unlocks, and deterministic replay logs as observable state in the Unreal Roguelike Game Maker project. Connect each transition to enter a seeded dungeon, clear three room types, choose one of two upgrades, defeat an elite, die or extract, and begin a visibly different next run, 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 roguelike teams proving run variety, risk, and deterministic recovery. Prove that the same seed reproduces the same route, a different seed changes meaningful choices, death clears transient state, rewards respect tables, and upgrades alter combat observably, then deliberately trigger this risk: randomized layouts can create unreachable rooms, invalid combinations, stale actors, misleading variety, or unreproducible defects. Preserve a rollback point, repeat the same test, and return the unreal roguelike game maker browser preview, performance notes, packaged output, and native project for download.
Use this prompt