That’s cool, I’ll check it out. Decision making and “thinking” for the ai was the easier part of the process here. What I’m doing with my package is a lot of systems, tools, helper nodes, and custom classes. I was going to rename the plugin to something more descriptive than utility AI as I want to include several example of AI set ups without going to crazy on the set up. AI is one of those things that is not a one size fits all so I’d rather do a “best practices” and working examples package.
There’s some stuff though that I personally use from free third party packs so I may need to do a git hub for those kinds of set ups as I can’t include those on the store.