Pick the brief that lets you validate walk or cab view, camera inspection, throttle, boom and winch control, attach and release, instrument focus, emergency stop, pause, and reset or follow state through scenario configuration, physics constraints, equipment state, environment variables, failure injection, scoring, telemetry, replay markers, and deterministic reset. Every Unreal Simulation 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 Simulation Game Maker as a native Unreal 5 slice: configure a weather condition, operate a harbor crane, load two cargo types, respond to a mechanical fault, finish within the safety envelope, and replay the scenario. Place it in an original coastal logistics yard with a working crane, cargo deck, service bay, wind indicators, and protected operator route. The build passes only when the same inputs reproduce comparable outcomes, instruments reflect actual state, invalid operations are rejected, the fault is recoverable, and reset returns every variable to baseline. Preview the Unreal Simulation 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 coastal logistics yard with a working crane, cargo deck, service bay, wind indicators, and protected operator route around these player inputs: walk or cab view, camera inspection, throttle, boom and winch control, attach and release, instrument focus, emergency stop, pause, and reset. For the Unreal Simulation 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 scenario configuration, physics constraints, equipment state, environment variables, failure injection, scoring, telemetry, replay markers, and deterministic reset as observable state in the Unreal Simulation Game Maker project. Connect each transition to configure a weather condition, operate a harbor crane, load two cargo types, respond to a mechanical fault, finish within the safety envelope, and replay the scenario, 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 simulation designers proving rules, controls, instrumentation, and repeatable outcomes. Prove that the same inputs reproduce comparable outcomes, instruments reflect actual state, invalid operations are rejected, the fault is recoverable, and reset returns every variable to baseline, then deliberately trigger this risk: convincing visuals can hide unstable physics, unit mismatches, nondeterministic timing, misleading instruments, incomplete reset, or unsafe assumptions about real equipment. Preserve a rollback point, repeat the same test, and preview the unreal simulation game maker result in a browser, measure its risky path, package it, and keep the unreal project downloadable.
Use this prompt