CCs do not handle finding targets.
Honorbuddy does that, then calls the public override Pull() part of the CC.
See if you can find CodenameGs beginner guide for CC creation.
Your Cc should only handle movement while in, or attempting to exit combat (feign death).
Thanks, I didn't know this was covered in tutorial. Ill check it out.
Recording one persons point every 5-10 seconds and adding it to a list wouldn't really be bad at all as long as you are removing the old points from the list as you reach or pass them.
On my ride home, I was also thinking of a plugin that would record raid/partymember's paths and store them in lists. Then when the player needed a path to move, the plugin would find one by:
1. Get current location
2. find a grouping of people
3. find who has been to both locations and what path they used
4. return path
This seemed like a ton oh information to store, so I wrote a program to test it. I tried to figure huge numbers... So 40 raidmembers fought a BG for 1 hour and the plugin saved each raidmember's location each second. So 60sec * 60min * 40raidmembers = 144,000 WoWPoints.
With this example, I made my program create 144,000 random WoWPoints, then set every 25th point to a specific point to simulate each raidmember visiting a common point.
It took about 3 seconds to generate the list of 144,000 points and 2 milliseconds iterate through and find all the nonrandom points.
Given these results, I feel like a plugin like this is worth pursuing. A bot that uses paths generated from real player movement could be perform better than one that follows a set pattern or one that follows someone around.
