Skip to content

Two shipped Characters #9

Closed
Closed

Description

@omesser

Depends on: #7, #8

Why

Two Characters in genuinely different styles validate the Character Package abstraction
against real variance before the format is published. One style would only prove the
format fits itself.

Scope

  • Faithful Win95 — 16-color, hard pixels, dithering.
  • Modern pixel art — larger palette, smoother animation.

Each ships the eight required animations, a Personality Prompt, and declared Behaviors.
The two must move and react differently enough that switching feels like a different
companion rather than a reskin.

Acceptance criteria

  • Both packages load through the same loader with no special-casing.
  • Both are playable with the static Director alone.
  • Switching between them visibly changes idle life, not just artwork.
  • Neither package requires a Primitive that the other cannot use.

Tests

Both packages load and validate in Engine tests. Visual quality is judged by hand.


Spec: docs/SPEC.md · migrated from docs/issues/0009-shipped-characters.md

Activity

  1. omesser commented on Aug 30, 2026

    @omesser
    OwnerAuthor

    Verified on main (b0a6e67) by running each Character for 110 seconds with AI_BUDDY_TRACE_FRAMES=1 and reading what the Engine actually played.

    The third criterion is the one that needed the Static Director. When #81 shipped the two Characters, their Behaviors differed on paper but none of them ever played: a Behavior reaches the Engine only as WorldSnapshot::proposal and nothing produced one. #82 landed the Director and gave BMO and Nim their weights, so they are selectable — StaticDirector::propose treats a Behavior with no trigger as always eligible (director.rs, None => true).

    Both played every Behavior they declare.

    • BMO: fidget, greet x2, patrol, report x2, walk
    • Nim: amble, doze x2, greet, mumble, stretch x2

    And the lives are visibly different, not just the drawing. Counting only animations a Behavior drove — the sprite Grounded, playing something other than idle, so the Engine's own State-driven animation is excluded:

    driven by a Behavior frames spent settling
    BMO land, react, talk, walk 0
    Nim land, sit, sleep, talk, walk, react 403

    BMO never sits or sleeps of its own accord; Nim does both. The shape of the two runs differs as well: BMO spent 3189 frames Perched and 1341 walking, Nim 5078 Grounded and 4474 idling.

    Worth separating from that, because it is easy to miscount: animation_for(State::Perched) is sit, so a perched sprite draws sit whoever it is. BMO logged 2842 such frames and none of them are the Character settling — they are the Engine's animation for standing on a window edge. The table above counts only what a Behavior put on screen.

    All four criteria met:

    One thing deliberately left open and tracked on #10: neither BMO nor Nim declares when conditions, so they have balance without arc — Nim can propose doze at someone actively typing. #9 does not ask for triggers, so it does not hold this open.

  2. omesser commented on Aug 30, 2026

    @omesser
    OwnerAuthor

    All four acceptance criteria met and verified on main. See the run above.

  3. added this to the V1 milestone on Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions