If i may jump in.
setting up a waypoint system isn't really that hard with playmaker as stock...
i've actually got a tutorial series that touches on this but i am planning on expanding it but here is the coles-notes that should get you started.
first off, if you want a set route/path that you want the ai to take, you're going to need some objects to be used as waypoints. this is easy to do since you can just use empty game objects.
from there, i then take another game object and make it the parent of those waypoints. this is where it gets a little tricky though since last time i tried it, the actions used to access them needed them to be in the right order... so, if you name them "waypoint 1," "waypoint 2," etc... then they should be updated in the heirarchy. this is kinda important because the system to set the waypoints uses the "Get next child" action and the order that they are in is kinda important (though it was a while since i revisited this... i've been focusing on other things which i need to devote more time to for my own game.)
so, you have a waypoint system and then you have a waypoint manager... so, the next thing you have to do is tell your AI what to use for the waypoint system... this can be wired directly in as a gameobject variable in the scene but if you're instantiating it at run-time, you might have to add in some "find" actions to find the right ones to use but that's not hard to figure out.
so, the ai now has the "waypoint container" and from there, you can tell it in the FSM to "get next child" and tell it to get the next child of the waypoint container. this should iterate through the list each time this action is called so if you have them organized right, it should go "waypoint 1" then "waypoint 2" then "waypoint 3" then back to "waypoint 1" (assuming three waypoints.)
when you do this, if you feed it into a second gameobject variable, you can then use this second "child" game object's information to extract it's location, it's orentation, all sorts of things which can then be fed to the actions that are driving the AI's movement. if you need a hand with telling your AI to move, the videos i have on basic AI should give you a decent starting point (though i am retooling the "radar" one since that one was a bit of a hatchet job and i'm redoing that video as a post-mortem to take into account what i've learned since i made that one... that should help make it clearer and easier to understand and much, much simpler.)
does this help? if not, let us know what you need help with and i'm sure you could find some help here. this is a really good community i've found.
