that's cool, i will look into generating my own. i think behavior designer is great, so keep that in mind when you hear the following criticism;
i do not think the documentation is good. i find it very difficult to navigate, and i don't find the argument of "we don't have an api reference, make your own!" to be compelling, as it is very much not the industry standard.
your competitors, like playmaker, have pages like this
playmaker api reference, and this
action reference.
clearly stating what tools exist within their framework, and how to use them.
behavior designers documentation reads more like a start to finish walkthrough with a huge glowing "NEXT" button at the bottom of every page.
this is great when you are first learning how to use the tools, but makes finding information during development very difficult.
let's say i want to consult the documentation to even just get a description of what a sequencer does, or what a conditional selector does. i have no idea where to find that information, there is no page with a list of actions, and none of your documentation is searchable. that information exists within tooltips in the unity editor, but that isn't what tooltips are designed for. they're meant to be
tips and reminders, not tutorials.
i want to see y'all do well because i think your products are of high quality, i've probably given you $200 at least over the year buying them, but i don't think you're going to reach your full potential or retain the quality of customers you want if you don't improve your documentation.
<3
