ENGINES & TOOLS

Your engine. Your direction.

Find the upstream entry points for Unreal Engine 5, Unity, Godot 4, three.js and Blender, with their roles, documented environments and demos.

Source reviewed 2026-09-05 · Curated and translated from the upstream documentation.

UE5ENGINE CONTEXT

Native worlds, engine-native workflows.

Follow the UEClient boundary for project work and the UE5 guide for native integration and validation.

Documented environment: Unreal Engine 5.4

Upstream reference, not independently tested here.

Read upstream guide

UnityENGINE CONTEXT

A familiar home for game prototypes.

Use UnityClient and the documented Unity context to connect generated assets, mechanics and interfaces.

Documented environment: Unity 2022.3.62f3c1

Upstream reference, not independently tested here.

Read upstream guide

GodotENGINE CONTEXT

A focused path into Godot 4.

Verify the requested Godot executable before project work, then use the public GodotClient workflow.

Documented environment: Godot 4.5.1 (installer default)

Upstream reference, not independently tested here.

Read upstream guide

three.jsENGINE CONTEXT

Interactive worlds for the browser.

The upstream three.js toolchain has its own Node and engine requirements. This PHP guide does not run that toolchain.

Documented environment: three.js r185

Upstream reference, not independently tested here.

Read upstream guide

BlenderASSET PROCESSING

Prepare the pieces of a world.

Use the documented bpy environment for neutral asset processing, rigging and repair. Blender is not presented here as a shipped game runtime.

Documented environment: bpy interpreter

Upstream reference, not independently tested here.

Read upstream guide

YOUR NEXT WORLD STARTS WITH AN IDEA

Make the first move.

Explore the project. Choose your direction. Start with a plan.

Start building View on GitHub