Pick the brief that lets you validate third-person movement, camera, climb, dodge, light attack, tool use, interaction, lock-on, and checkpoint restart or follow state through movement states, traversal tags, combat, damage, interaction, puzzle state, ability gating, checkpoints, camera volumes, and reward persistence. Every Unreal Action-Adventure 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 Action-Adventure Game Maker as a native Unreal 5 slice: cross a flooded temple approach, unlock a traversal tool, defeat guardians, redirect water through a mechanism, recover a relic, and exit by a changed route. Place it in an original overgrown river temple with flooded steps, climbable ruins, a guardian court, water mechanisms, and a relic vault. The build passes only when the player understands each gate, traversal and combat transitions remain stable, the puzzle changes the route, the relic persists, and the return path proves the new ability. Preview the Unreal Action-Adventure 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 overgrown river temple with flooded steps, climbable ruins, a guardian court, water mechanisms, and a relic vault around these player inputs: third-person movement, camera, climb, dodge, light attack, tool use, interaction, lock-on, and checkpoint restart. For the Unreal Action-Adventure 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 movement states, traversal tags, combat, damage, interaction, puzzle state, ability gating, checkpoints, camera volumes, and reward persistence as observable state in the Unreal Action-Adventure Game Maker project. Connect each transition to cross a flooded temple approach, unlock a traversal tool, defeat guardians, redirect water through a mechanism, recover a relic, and exit by a changed route, 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 teams combining traversal, combat, interaction, and authored discovery. Prove that the player understands each gate, traversal and combat transitions remain stable, the puzzle changes the route, the relic persists, and the return path proves the new ability, then deliberately trigger this risk: multiple feature families can obscure the core loop and create brittle transitions between movement, combat, interaction, camera, and save state. Preserve a rollback point, repeat the same test, and preview the unreal action-adventure game maker result in a browser, measure its risky path, package it, and keep the unreal project downloadable.
Use this prompt