Gamibase

●Gamibase Studio · Local Engine Builds in active development

Local Engine Builds

Open the native project on your PC, choose a supported build, cook, package, play, or capture task, then review its status, logs, and output in one place.

Gamibase Studio
Search Bloxiti / sessions, assets, commands...?K
UE5.8

Unreal

Maze on this machine
Stays on this machineIllustrative sample output
Maze running in UE5.8 on this machine
Maze from above in UE5.8

Maze from above

Red chamber in Maze in UE5.8

Red chamber

Neon corridor in Maze in UE5.8

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

Output

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

gamibase-studio-serviceLocal project connectedReview requiredApproval requiredReady
Interactive Studio preview using sample project data. Features may change before early access.
●Native project files

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.

01

Native maps and assets

Content stays in the engine project Studio opened.

02

Source and configuration

Code and project settings remain ordinary project files on disk.

03

Produced files

Logs, cooks, packages, and captures stay with the local project.

See the task first

Know what will run before the engine starts.

Studio shows which tasks are available for the open project. Choose one, review the plan, confirm when needed, and run it on your PC. More project and engine combinations are being prepared for early access.

Play

Play when a target is available

Open a runnable target supported by the current project.

Build

Build or cook from a clear plan

Review the command first, then keep its local log with the project.

Package

Choose the package target

See whether the target is supported and confirm the run when required.

Capture

Capture when supported

Capture appears only for projects with an available capture task.

●Inspect the result

A finished command is only the beginning.

See how the command ended, read its log, and check that the expected file or project change exists.

01

Selected engine and target

The engine, project, and target chosen for this task.

02

Run status

How the local command ended.

03

Transcript

The local log for that run, kept with the project.

04

Expected output

What should exist after the task, and what Studio found.

05

Clear problems

Missing output, mismatches, blocked runs, and unsupported tasks are shown clearly.

What stays on your PC

Your native project stays native.

Project source, assets, build logs, and generated files stay on your machine. Optional diagnostics send only approved, redacted information. Raw source and private assets are not uploaded.

What to know

Local project possession

Source, logs, and generated outputs stay where the project is opened.

Support for the open project

Studio shows only the tasks available for the selected engine and project.

Diagnostics are optional

Optional diagnostics are a separate choice. Raw source and assets are not uploaded.

Join the Studio waitlist

Be first to hear when early access opens.