KGB Studio v1.0.6 — Complete Operator Guide

A deeper top-to-bottom guide for someone who did not help build the Studio.

The Core Idea

KGB Studio is the builder. The game is what players open. The project is the editable working file. The package is the exported playable folder/ZIP. The runtime is the JavaScript harness that makes the package playable.

The v1 Pipeline

New Game → Template → Actor → Action → Scene → Interaction → Preview → Package → Release

That means you start with an idea, generate a starter, define what moves/acts, place objects, classify interactions, preview the real package, export it, then release it.

Vocabulary

Studio: the single-file builder app.
Game: the thing players play.
Project: editable Studio working data.
Operation: the current project/work session.
Platform: Studio internals like modules, adapters, event bus, commands, and persistence.
Production: release-quality output path.
Package: exported playable game folder/ZIP.
Runtime: JS harness that loads and runs the package.
Manifest: JSON index of assets/files/actors/scenes/release data.
Adapter: wrapper that lets embedded tools behave like Studio modules.

MISSION

New Game creates a project from game line/template/title. Mission Brief summarizes status and next actions. Project JSON shows the raw editable project.

ASSETS

Asset Library browses assets. Asset Intake imports files. Actor Builder creates actor/action definitions. Scene Builder places objects and interactions. Shape/Sprite/Slicer/GIF/Forge Suite create visual/audio/supporting assets. Metadata Forge cleans files. Tool Registry explains embedded tools/adapters.

SYSTEMS

Runtime Preview previews individual assets. TAIO handles text/data work. Persistence manages autosave/snapshots. Asset Registry indexes assets. Event Bus shows module messages. Platform shows modules/adapters/operators. Changelog tracks v1.

BUILD

Production Release is the release gate. Playable Loop validates Milestone A. Templates generate starters. Game Package exports the playable package. Package Preview runs the real package inside Studio. Validate checks project health.

DEPLOY

Download production package, unzip, run python3 -m http.server 8000, test smoke-test.html, then test index.html. For GitHub Pages, copy the package into a repo folder like /games/<slug>/.

JSON/File Guide

.kgbproject.json: Studio backup for editing later.
game.config.json: runtime settings and package paths.
assets.manifest.json: asset/file index.
actors.manifest.json: actor/action index.
starter.scene.json: scene/object/interactions data.
kgb-production-release.json: release metadata and readiness.
release-notes.txt: human release notes.
production-readme.txt: exported package instructions.
smoke-test.html: package reachability test.
kgb-runtime.js: actual runtime code.

What Creates What?

New Game creates project/template/actor/scene starter data. Templates create starter actors/scenes/interactions. Actor Builder creates actor JSON. Scene Builder creates scene JSON. Game Package creates playable files. Package Preview creates an in-memory virtual package. Production Release creates release manifest, notes, README, and production ZIP. Persistence creates snapshots/backups. Forge tools create assets.

Most Common Workflows

New game: New Game → Playable Loop → Package Preview → Production Release.
Edit scene: Scene Builder → Save Scene → Package Preview.
Edit actor: Actor Builder → Save Actor → Package Preview.
Add assets: Asset Intake/Forge Suite → Asset Library → Actor/Scene Builder.
Publish: Package Preview → Production Release → Deploy Notes → local server test → repo commit.

Troubleshooting

If preview is stale, refresh Package Preview. If files do not load locally, use a local server. If actor does not appear, check Actor Builder and actor spawn. If collisions fail, check Scene Builder behavior. If you need a backup, download the .kgbproject and production ZIP.

Download the full text guide

The on-screen version is condensed. Click Download README.txt for the full detailed operator guide.

Help