Pick the brief that lets you validate third-person exploration, talk, inspect, dialogue choice, journal view, objective focus, skip or advance, and checkpoint reload or follow state through conversation graph, conditions, quest stages, objective tracking, choice variables, NPC state, rewards, localization readiness, save data, and replay reset. Every Unreal Quest and Dialogue 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 Quest and Dialogue Game Maker as a native Unreal 5 slice: meet a harbor keeper, investigate a missing shipment, question two witnesses, choose whom to trust, resolve the dispute, and revisit changed dialogue. Place it in an original stormy harbor village with a keeper office, warehouse, market witness, lighthouse path, and visibly changed end-state. The build passes only when choices open the intended branches, unavailable lines stay hidden, quest stages cannot skip, consequences appear in world and dialogue, and save or replay restores the correct branch. Preview the Unreal Quest and Dialogue 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 stormy harbor village with a keeper office, warehouse, market witness, lighthouse path, and visibly changed end-state around these player inputs: third-person exploration, talk, inspect, dialogue choice, journal view, objective focus, skip or advance, and checkpoint reload. For the Unreal Quest and Dialogue 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 conversation graph, conditions, quest stages, objective tracking, choice variables, NPC state, rewards, localization readiness, save data, and replay reset as observable state in the Unreal Quest and Dialogue Game Maker project. Connect each transition to meet a harbor keeper, investigate a missing shipment, question two witnesses, choose whom to trust, resolve the dispute, and revisit changed dialogue, 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 narrative designers proving branching conversations and quest consequences. Prove that choices open the intended branches, unavailable lines stay hidden, quest stages cannot skip, consequences appear in world and dialogue, and save or replay restores the correct branch, then deliberately trigger this risk: branch conditions, quest flags, localization, skip behavior, NPC schedules, and saves can create contradictory or unreachable narrative states. Preserve a rollback point, repeat the same test, and preview the unreal quest and dialogue game maker result in a browser, measure its risky path, package it, and keep the unreal project downloadable.
Use this prompt