Gamibase

●Gamibase Studio · Director in active development

Project Director

Project Director is being built for one game project at a time: talk at any altitude, shape an approved living game model, move the next playable slice, and judge the result where it matters—in the game.

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

Reelhaven

UE5.8 · Sample project
Approval requiredContent lanesFlatPause
# Flat view# Now

You · 14:02 — 'The reel feels sluggish when a big fish hits — like pulling through mud. What would night fishing take?'

Director — matched to your 1:24 playtest note; night fishing logged as an open question beside co-op scope.

↑ 7 moments today — open the day

Director · Now

The reel tune is ready to feel — your call decides it.

Tune proposal

Waiting for your review

Reel torque ramp

Shorten the spin-up so the reel bites immediately under load.

ReelTorqueRampMs 320 ms → 210 ms

▶ 1:24 — “the reel feels sluggish” ▣ screenshot pinned

A/B re-play · 20 squeued behind: bigger splash when the fish escapes

? Open question · Dusk water · from your 2:12 note

Dusk water reads flat. Which way should it lean?

Stylized ripple bandsDenser sim foamPainterly, sparse specular
Add a note to this sitting...
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.
●The Director loop

From an idea to something you can play.

One conversation carries the idea into focused work, a playable result, and the next decision.

01

Talk at any altitude

Begin with the vision, a feature, an exact change, or a question.

02

Approve the living game model

Keep the direction, open questions, and approved choices easy to see.

03

Build the next playable slice

Work is organized around the smallest milestone that can be played and judged.

04

Play, decide, and tune

Judge each result in the game and carry that feedback into the next change.

Direction and result

See the idea and the game side by side.

Director keeps the approved direction separate from what is currently in the project. When they differ, you see the gap and decide what should change.

What to know

Approved intent

The game model keeps the creative direction, open questions, and approved choices together.

Observed reality

The current project shows what the playable build actually contains.

Playable result

Each finished step returns to the game so the team can judge it in context.

Your creative call

When intent and reality disagree, Director surfaces the drift. You decide what to keep.

One project only

Notes and decisions stay with the project they belong to, with their source and age visible.

●The taste loop

Play it. Say what feels wrong. Compare the change.

During native play, feedback stays attached to the exact moment, project state, and live values. After play, Director can return a grounded proposal for A/B review. You decide what feels right.

01

Play natively

Mark the moment in the running game so the note stays attached to state and values—not a detached ticket.

02

Review one grounded proposal

Return to a concrete change proposal you can compare, including A/B review when the slice supports it.

03

Keep it or go back

Keep the version that feels right and see whether the change can be reversed later.

Join the Studio waitlist

Be first to hear when early access opens.