I created a custom
NavGraph as well as a
GraphEditor for it, but unity was still giving me errors indicating that I did not have a
GraphEditor for the graph.
After a while I discovered that because I put the "AStarPathfindingProject" directory inside "Plugins" (where try to put all third party stuff), the search was not finding my
GraphEditor due to only searching the assembly that
GraphEditorBase is located in.
The solution was to move the package's directory back out of the "Plugins" directory, but I am curious what I would have done if my
GraphEditor was say inside a dll where it wouldn't matter where the package directory was, it wouldn't find it with the current implementation. This is a problem seeing as how a
GraphEditor is basically required to be found or else cause
AstarPathEditor to throw a fit.
Instead of iterating just the assembly the
GraphEditorBase is in, it may a good idea to search all assemblies, not just so I can move the package back into "Plugins" (my personal desire), but for the possibility for types of
GraphEditor to be located in external assemblies (so I don't seem selfish in my request).