build-game-monster-system

Define a serializable MonsterDefinition with stats, attacks, and budgets, then build a rig with a stable root/motion/body hierarchy, real parented joint chains, and semantic sockets. Connect it to the runtime through a view adapter that never derives damage from rendered poses.

Attack contacts should come from authoritative action IDs and collision events on dedicated attack volumes, enabled only during the active window. Animation may expose a normalized phase but must never create damage by itself, and each contact applies once per action-target pair.

A conforming enemy needs five explicit layers: solid for world blocking, navigation for movement profile, hurt for damage-receiving volumes, attack for offensive contact shapes, and trigger for perception or effects. Use capsules, spheres, or boxes rather than visual mesh overlap.

Yes, the asset contract supports procedural, GLB, or hybrid sources as long as provenance, license, scale, and forward axis are recorded. Imported models must still expose the required semantic joints, sockets, and collision layers to conform.

LOD changes must alter visual children only while preserving root, joints, sockets, collision, and animation state. Socket drift across LOD tiers is a conformance failure, so keep gameplay transforms outside the swappable visual groups.

The default budget targets near LOD at 50k triangles or fewer, far LOD at 12k or fewer, at most 48 draw calls, and up to 12 textures at 1024px. Boss or hero enemies can override these only with an explicit budget declaration.