Local Engine Builds
Open the native engine project on your machine, check whether the selected operation is available for its engine, project, target, and configuration, then plan, run, and inspect the result. Terminal status, logs, expected artifacts, and authoritative read-back stay together.
Unreal
Maze from above
Red chamber
Neon corridor
Project files
- Bloxiti.uproject
- Content/Maps/Maze
- Content/Materials/MazeStone
- Source/Bloxiti/World/MazeBlock.cpp
- Binaries/Win64/Bloxiti.exe
In Maze
- Maze towerscarved stone
- Player startspawn
- Water floorreflective
- Neon stripscyan and red
- Glass walkgrid walkway
Bloxiti.uproject · Maze
UE5.8 · Play · Bloxiti on this machine
09:18:02 Cook started on this machine
09:18:41 Play: Maze
09:19:08 Wrote Binaries/Win64/Bloxiti.exe
09:19:44 Waiting on playtest review
The engine opens the project through its engine-owned route.
Studio opens the project through its engine-owned route. The project remains editable in its native engine and on disk. Maps, assets, source, configuration, and outputs stay ordinary project files you can inspect outside Studio.
Native maps and assets
Content stays in the engine project Studio opened.
Source and configuration
Code and project settings remain ordinary project files on disk.
Produced files
Logs, cooks, packages, and captures stay with the local project.
Each operation begins as a plan and runs only when admitted.
Studio reports availability for the selected engine and project. Missing, stale, or unsupported evidence leaves the operation unavailable. Real execution is explicit after current readiness, policy, and required confirmation pass. The complete packaged Studio → Services → Core → engine execution and read-back path is being proven for early access.
Runnable target when exposed
Available only when the selected adapter and project expose a runnable target.
Build or cook from a plan
Start with a dry-run plan; real execution is explicit and keeps the transcript with the project.
Declared target, then gate
Requires a declared target, current support evidence, and approval when gated.
Only when catalogued
Shown only when the current operation catalog declares Capture available for this project.
A completed command is not proof.
Terminal status, transcript, expected artifact, and authoritative read-back stay together. Disagreement is a typed failure or blocker—not quiet success.
Selected engine and target
The engine, project, and target admitted for this operation.
Terminal status
How the local run ended, separate from whether the expected artifact exists.
Transcript
The local log for that run, kept with the project.
Expected artifact and read-back
What should exist after the operation, and what authoritative read-back actually observed.
Typed failure or blocker
Missing, mismatched, blocked, or unsupported outcomes stay explicit.
Native stays native. Availability stays explicit.
Project source, assets, build logs, and generated outputs stay on the machine. Optional telemetry upload is a separate explicit action using redacted aggregates; raw source and assets are not uploaded. Studio reports availability for the selected engine and project. Missing, stale, or unsupported evidence leaves the operation unavailable.
The boundary
Local project possession
Source, logs, and generated outputs stay where the project is opened.
Declared engine support
Availability is reported from current evidence for the selected engine and project—not implied by marketing copy.
Telemetry is explicit
Optional redacted telemetry upload is a separate action. Raw source and assets are not uploaded.
Get on the list before Studio opens.
Studio isn’t public yet. Our team uses it today and opens access gradually.