// the take
A state chart library for Godot 4, built on top of hierarchical/parallel state machines rather than plain FSMs, so it handles things like substates, history states, and parallel regions without the state-explosion problem flat FSMs get into. Aimed at Godot developers building character controllers, AI, or any gameplay logic with more than a handful of states, in either GDScript or C#.
Everything is modeled as Godot nodes in the scene tree, so you build state charts visually in the editor instead of writing boilerplate state classes - the diff with a hand-rolled FSM is immediately obvious. Transition guards are declarative (AnyOf/AllOf/Not/expression guards) and composable without subclassing. It ships a working in-game debugger (editor_debugger, ring buffer history) so you can actually watch state transitions happen live instead of printf-debugging gameplay code. Inactive states skip per-frame updates, which matters in a game loop where every idle node processing _process() adds up.
It's a single maintainer project (derkork) with no indication of a broader core team, so bus-factor risk is real for something you'd wire gameplay logic through. Being GDScript/node-based means state chart logic lives in the scene tree rather than in code you can unit test or diff cleanly in version control - .tscn files with embedded state nodes merge badly. The C# bindings exist but are clearly secondary to the GDScript implementation (NodeWrapper/ResourceWrapper indicate a wrapping layer, not a first-class API), so expect rougher edges and slower parity with new GDScript features. Tied tightly to Godot's node/signal model, so there's no path to reusing this logic outside Godot if you ever need the state machine on a server or in a different engine.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →