Before we dissect version 30, let’s define the baseline. Creature Framework is a real-time 2D/3D skeletal animation system designed for high-performance runtime rigging. Unlike traditional bone-based animation that relies on rigid hierarchies, Creature utilizes Mesh Deformation with Controlled Bones (MDCB).
Creature Framework 30 is the latest iteration of this engine-agnostic runtime. It supports Unity, Unreal Engine, Godot, and custom C++/C# projects. Version 30 is not merely an incremental update; it is a complete architectural rewrite focusing on multithreading, physics-based animation, and AI-driven motion synthesis.
One of the hidden gems in Creature Framework 30 is the RealtimeIKPass. To make a creature look at a target: creature framework 30
creature.EnableFeature("FullBodyIK");
creature.SetIKTarget(BoneType.Head, Camera.main.transform);
creature.SetIKWeight(1.0f); // Full influence
The solver runs in a separate job thread, meaning it doesn't block the main game loop.
Component lifecycle:
Getting started with Creature Framework 30 is streamlined. Since the API has changed drastically from v2.5, follow this basic implementation guide.
The developer (Kestrel Moon Studios) has released a roadmap for v30.x: Before we dissect version 30, let’s define the baseline
Perhaps the most powerful addition is the Motion Graph. Previous frameworks forced developers to hard-code transitions between idle, walk, and run. Creature Framework 30 uses a node-based visual scripting tool (editable at runtime) that blends up to 12 animations simultaneously based on parametric variables like velocity, slope angle, and emotional state.
2.1 Background Previous iterations of the Creature Framework relied on rigid, pre-defined state machines. While functional for simple fauna, the system lacked scalability and required extensive hard-coding for new species introductions. As the simulation scope expanded, the overhead for managing diverse biological niches became unsustainable. The solver runs in a separate job thread,
2.2 Objectives of v3.0 The development of CFW 3.0 was driven by three core requirements: