godot-behaviour-tree VS godot-steering-ai-framework

Some nice added benefits are an open source behaviour tree system (https://github.com/andrew-wilkes/godot-behaviour-tree), an open source audio solution (https://github.com/kyzfrintin/Godot-Mixing-Desk), the Tween nodes, being able to animate material properties, a functioning navmesh (again, 3D issues on Unity's front; 2D ports don't support side view), no need for weird lighting setups between 2D and 3D, faster scripting with gdscript, the Line2D node (which I use to render and bend the body of the wormy creatures in our latest tweet), and generally just the fact that all transforms are in 2D without needing to worry that my scene view is playing tricks on me.

Found multiple following behaviours, but decided to use one from GDQuest's "AI following the leader" tutorial video, as it's nicely separated into static Steering class. Also found very cool Godot Steering AI Framework from same GDQuest, which is so modular and reusable that I guess 90% of developers should start using it instead of writing their own boilerplate.

Battle for Rhiannon NetworkDevlog SummaryCard Battling 3rd Person ShooterGame Engine: Godot 3.3Days Left: 46---Log 007- Created Enemy to rushes PlayerTook some time to learn FSM and Steering AI with help from u/NathanGDQuestLinks to the projects below:https://github.com/GDQuest/godot-design-patternshttps://github.com/GDQuest/godot-steering-ai-framework

I’m using https://github.com/GDQuest/godot-steering-ai-framework for steering. I calculate path using godot astar implementation and then apply it to follow path option of steering framework. The steering framework itself is not super performant as it is implemented using gdscript, but for my game it’s more than enough. Check out it’s specific steering options to get some inspiration. It is well documented and has a lot of examples.