Table of Contents

Embedded planning, GameDirector, and creative runtimes

Embedded firmware planning

LocalGPT can turn a board description, pin layout, sensor/actuator roles, transport requirements, and policy constraints into a reviewable firmware plan.

The planner is transport-neutral. GPIO, ADC, PWM, I²C, SPI, UART, CAN, RS-485, physical 1-Wire, and LocalGPT logical telemetry are capabilities—not assumptions.

A plan can include:

  • board and pin assignments;
  • electrical or protocol findings;
  • firmware module layout;
  • telemetry contract;
  • generated source artifacts;
  • compiler and flashing prerequisites.

Planning, compilation, serial access, flashing, and actuator control are distinct operations. The later stages require the matching workspace and approval checks.

Organic 1-Wire

LocalGPT's “organic 1-Wire” is an application protocol for approved peers, publishers, add-ons, and devices. It is not limited to the Dallas/Maxim physical bus. Transport adapters can use TCP, HTTP/JSON, or a gateway while the application contract keeps identity, replay protection, approval, and capability routing explicit.

GameDirector

GameDirector is the authoritative game engine. Player controllers, creature Councils, and reactive map objects submit proposals; they do not mutate world state directly.

The deterministic resolver validates legality, turn order, movement, and state transitions. A configured model can enrich narration or predict consequences without owning the authoritative frame.

Runtime classes describe sessions, maps, players, directors, creatures, objects, and frames. Council roles can be assigned to world actors while the actual transition remains inside GameDirector.

ASCII play surface

The Chat ASCII console is both a normal conversation companion and a fixed-cell game/presentation surface. Council game sessions expose their own bounded live dimensions, while legacy deterministic game frames remain compatible with the established 80×25 path. Renderers can inspect the current display, update a single cell, write text, fill or blit a region, submit a complete frame, or submit a pregenerated 2–12 frame animation for browser-local playback. Presentation state never replaces the canonical conversation transcript or authoritative game state.

ASCII DOOM Council Adventure

The preseeded ascii-doom-council-adventure team treats CouncilGameSessionService as the only game engine. Starting the team creates or recovers one deterministic corridor session in Human + AI (Shared) control mode, with background autoplay off. Human input remains available immediately; selecting Human, Human + AI, or AI hunter in the Game tab changes runtime ownership without changing the Council team. The Council observes and explains the authoritative state; it does not run a second model-invented simulation.

The starter team assigns the resettable games.ascii.doom.campaign runtime class. Its visible class fields define the starting level, automatic level advance, and a configurable level-profile set containing map width/height, room count, enemy density, deterministic difficulty rating, enemy health/damage multipliers, and starting health/ammunition. The supplied class contains ten progressively harder starter levels. Copy the runtime class, edit any of those values or the level count/order, and assign the copied class to a copied team role to create a different campaign without changing engine code. The game service resolves a copied team assignment before the system seed and clamps the configured values to safe deterministic bounds; it does not invent a hidden replacement difficulty curve.

The active campaign class drives the connected map, persistent hostile actors, opening line-of-sight contact, ammunition/health, extraction coordinates, collision feedback, tactical radar, and automatic transition to the next configured level after a cleared extraction when autoAdvanceLevels is enabled. In Human mode AI-origin movement is rejected. In Human + AI, both sides may submit explicit bounded controls but no background autoplay loop runs. AI hunter is the only autonomous mode. The hunter reads the authoritative map, turns toward visible hostiles, shoots through validated line of sight, pathfinds around walls and occupied hostile cells, and routes to extraction after combat. Shooting, enemy HP, enemy pursuit/contact attacks, death, level progression, and extraction are deterministic service-owned transitions rather than model narration.

localgpt.game.session.get and localgpt.game.display.get can resolve the active conversation game when sessionId is omitted, so Council members must not guess GUIDs or ask the human for internal session identity. The renderer mirrors the canonical service-owned frame; optional decoration and 2–12-frame browser-local animations remain presentation-only.

ASCII Hot Seat — Neon Relay Arena

The preseeded ascii-hot-seat-showcase Council team is a two-player local hot-seat demonstration. Player 1 Hot Seat and Player 2 Hot Seat are HumanOnly Council roles, so LocalGPT pauses for each person in turn instead of simulating a missing player. One AI Arena Referee resolves both commands deterministically and emits the canonical HOTSEAT_STATE; a separate ASCII Display Director owns all terminal mutations.

The showcase intentionally exercises the ASCII stack: full-frame intro rendering, incremental text/cell/fill/blit updates, display readback for continuity, a score/HUD, sprites, and short pregenerated animations. The underlying Council game session is used only as the supported display host; the hot-seat multiplayer state remains referee-owned Council state and is not advanced through the single-player localgpt.game.control path.

Minecraft Mod AI Builder

The Minecraft builder applies the same project principles: source knowledge is versioned, generated artifacts are reviewable, dependencies are explicit, and a generated mod/datapack is not presented as tested until the correct toolchain has actually built or validated it.

Historical source comparisons and early game presets are retained as internal notes, while this page describes the maintained runtime contract.

Game projects and the ASCII engine runtime

The ASCII game functionality is the first rendering/control surface of a reusable LocalGPT game runtime, but game authoring belongs to the Project system one layer above it. A Game project can be built into a serializable ProjectGameDefinition; GameDirector then executes that definition using the same authoritative session, input, AI/Council, cancellation, and ASCII display contracts used by the built-in games.

The current project-build profiles are Corridor and Story. ascii-doom and green-dragon remain legacy-compatible built-in launch keys, while project-built games receive their own stable game key and project/version identity. This keeps existing games working while allowing LocalGPT to author and build new games through normal project revisions, requirements, workspace content, and approved artifacts.

A Game project now has a persisted Game Design profile separate from its build artifact. Save the design when runtime-facing project settings change; build only when that persisted design and the Project requirements are ready to become a runtime definition. Each build records the source profile, current revision, and user-approved requirement ids so a later playtest can tell which design baseline it is evaluating.

Four maintained Council presets support the development lifecycle. Game Project Discovery & Requirements interviews the user and persists confirmed requirements rather than guessing them. Game Project Development Team implements against those requirements and builds/launches bounded test sessions. Game Engine Extension Development Team is for reusable engine capabilities that cannot remain project data and explicitly includes migration, architecture-policy, async, diagnostics, and compatibility review. Game Project Playtest & QA verifies a built game requirement-by-requirement using canonical runtime state.

From ASCII Operator mode, :game project <project name or id> loads the latest approved build and enters game mode directly. A player therefore does not need to leave the ASCII surface to launch or control a project-built game.

Edit this page