Unreal Engine projects
Use Blueprint/C++ for gameplay and editor tools for automation.
Reviewed 6 October 2026 · 2 min read
Before you start
Choose the existing .uproject and matching engine. C++ also needs a native compiler and platform SDK. Avoid migrating projects merely to make a tool work.
Python is editor automation, not gameplay scripting. Enable the project’s PythonScriptPlugin before using it.
Step by step
- Inspect engine version and plugins; preserve a recoverable revision.
- Prototype gameplay in a small level with Blueprint or C++.
- Use Python for supported editor/content tasks; commandlets may need to load a level explicitly.
- Run a named automation test group and inspect report and log.
- Follow installed-version UAT BuildCookRun guidance for packaging and test the packaged executable.
Try this
Inspect this Unreal project without upgrading it. Add a small movement test area using the existing gameplay framework. Run relevant automation tests, report the number executed and capture the playable result.
Check the result
- The expected tests ran; empty reports are not passes.
- Editor logs show no hidden failures.
- Assets/gameplay work in the packaged target.
If something goes wrong
Check project plugin settings if Python is unavailable.
Community MCP bridges need compatible plugin/server versions. Review and pin them; do not assume Epic endorsement.
Further reading
External references inform the guidance; their product-specific features are not promises about Helios.