Build Game Monster System

Establish the contract

• Use

  img2threejs

  for image-driven procedural reconstruction and its staged visual gates.
• Use

  build-hybrid-game-assets

  to choose procedural versus imported representation and record provenance/budgets.
• Use

  tune-enemy-ai

  for perception, intent, movement, and behavior transitions.
• Use

  design-action-combat

  for startup/active/recovery timing and authoritative contact.

Separate four layers

1. MonsterDefinition

   : serializable authored facts, tags, scale, stats, attacks, locomotion, asset provenance, and budgets.

2. MonsterRig

   : semantic transform hierarchy, joints, sockets, secondary-motion anchors, materials, and LOD visuals.

3. MonsterRuntime

   : current state, timers, target intent, health/posture, cooldowns, and authoritative combat events.

4. MonsterViewAdapter

   : drives rig poses, VFX, audio, visibility, and LOD from runtime state; never decides hits from rendered pose.

Build the rig

• Use

  +Y

  up,

  +Z

  forward, meters, and a ground-contact root.
• Keep

  root -> motion -> body

  stable across every monster and LOD.
• Parent limb segments as real joint chains so shoulder/hip motion propagates through elbows/knees to wrists/ankles.
• Name semantic equivalents for nonhumanoids; do not fake absent anatomy.
• Provide sockets for attack origins, VFX, audio, targeting, ground contact, attachments, and death effects.
• Keep visual meshes out of physics by default. Provide simple solid, navigation, hurt, attack, and trigger shapes separately.
• Preserve root, joints, sockets, collision, and animation state across LOD changes.

Connect behavior and combat

idle

investigate

pursue

reposition

windup

attack

recover

stagger

defeated

Compose testable movesets

• Author movesets as serializable sequences of intent states and attack IDs. Keep attack timing in the attack definitions; the moveset references it instead of copying it.
• Compile attack steps into explicit startup, active, and recovery phases.
• Provide a pure sampler from

  (movesetId, elapsed)

  to state, attack, normalized phase, active flag, interruptibility, and stable action ID.
• Give every loop cycle a new action ID while preserving one ID across an attack's startup, active, and recovery phases.
• Expose queryable or seeded fixtures for the midpoint and boundaries of every phase so reviewers can freeze and reproduce them without campaign playthrough.

Verify conformance

• Add deterministic fixtures for all required states, each attack phase, interrupt/stagger, death, LOD switching, and reset.
• Test moveset timeline continuity, exact active-window boundaries, full attack coverage, per-action ID stability, and per-loop ID renewal.
• Test joint propagation, socket stability, collider coverage, single-contact idempotence, and disposal.
• Render the monster at real encounter distance in the in-app browser.
• Measure triangles, draw calls, textures, frame time, and mobile pixel-ratio behavior.
• Fail the asset if it has floating attachments, missing mandatory states, pose-derived damage, LOD socket drift, or unbounded resource cost.