MANSETry the engine

Manse documentation · v0.1

Build active games in plain language.

Manse Creator gives Codex the engine contract, deterministic checks, publishing workflow, and reusable design patterns it needs to build a standalone motion game Site.

Install the plugin Browse source

01 · Install

Add Manse Creator to Codex.

The plugin is distributed from the open Manse repository marketplace. It runs inside Codex and does not require an OpenAI API key, Manse account, or publishing token.

  1. 1

    Open Plugins in Codex

    Use the Codex app's plugin manager and choose to add a repository marketplace.

  2. 2

    Add the Manse repository

    Use https://github.com/ahndohun/manse as the marketplace source.

  3. 3

    Install Manse Creator

    Select Manse Creator, then begin with “Create a Manse game about…”

Creator promise

You should be able to describe, preview, validate, and publish a game without manually editing source code.

02 · Create

Use one conversation from idea to Site.

Example prompt

“Create a gentle ocean rescue motion game for ages 6-9, playable while seated or standing, in English and Korean.”

Codex selects the right Manse Creator skills as the project moves through the workflow:

create-game

Turn a natural-language brief into a complete Manse game Site.

generate-assets

Create original art and keep its provenance and license metadata.

preview-game

Run the simulator and a local browser preview before using a camera.

validate-game

Check the pack, public manifest, assets, accessibility, and compatibility.

remix-game

Create an attributed variation from a compatible open game.

publish-game

Publish through Sites and verify the public deployment contract.

submit-to-showcase

Prepare the small catalog contribution for maintainer review.

The plugin pauses for meaningful creative choices and performs deterministic validation before it proposes publishing.

03 · Contract

Every published game stands on its own.

A Manse game is an independent public Site. Its runtime, packs, generated assets, and offline resources are bundled with the deployment. There is no runtime CDN or hosted AI dependency.

Public manifest/.well-known/manse-game.json

Identity, URLs, engine compatibility, locales, movement, accessibility, license, and provenance.

Portable pack/packs/<game>/manse.pack.json

Strict declarative scenes, challenges, localized narration, assets, and adaptation data.

Version 1 safety boundary

  • No arbitrary JavaScript, HTML, or executable WebAssembly in packs.
  • All assets use relative in-Site paths and declare origin and license.
  • Unknown fields, broken references, and paths escaping the pack root fail validation.
  • Permissions are explicit; v0.1 permits camera and device-local storage only.

04 · Runtime

Target the browser, adapt to the device.

The engine keeps pose inference and rendering independent so each can scale without slowing the other. Quality tiers can adjust model complexity, inference cadence, effects, and resolution while preserving the game rules.

DeviceExperience
Phone and tabletFront or rear camera, touch-friendly setup, responsive layout
Laptop and desktopWebcam play, keyboard-accessible setup, simulator fallback
Camera-equipped smart TVLarge-display layout with device capability detection
Honest compatibility

Individual game manifests disclose their supported inputs and access features. The engine selects a device tier at startup, but creators must still test every device class they claim.

05 · Privacy

Camera access is local input, not uploaded content.

Manse processes camera frames on the playing device. The platform does not transmit frames, collect child data, create player accounts, or add behavioral analytics. Creator-owned Sites must preserve this boundary to qualify for the official Showcase.

  • Ask for camera permission only in direct response to the player.
  • Explain the camera purpose before the browser prompt appears.
  • Keep captions, reduced stimulation, seated alternatives, and input fallbacks discoverable.
  • Declare asset sources, licenses, and generated-asset provenance.

Next step

Published already?

Verify the public manifest and learn how the lightweight Showcase review works.

List your game