I just want to point out bold, easy to implement features: 1. Honor-buddy spams tab, and maps nearby enemies... so that way it won't mindleslly run into a group of three. 2. Z axis location checks, it shouldn't be trying to kill something below the cave. 3. Stop moving to hotspots, or clear target when being hit, so that way It doesn't pull 3 or 4 enemies. 4. New Profile features for quests, in example. <Quest Id = "??" Name="??" Type="Explore" Hotspot1 ="X,Y,Z"> <Quest Id = "??" Name="??" Type="Grind" Hotspot1 ="X,Y,Z"> 5. Instead of grinding when out of quests, provide a pvp grind instead. A few wishes have already been granted, such as death logic and questing alone ^.^ Take note that the grinding of honorbuddy needs love too!
Decent suggestions, though the last one is a bit tricky. You should know that most of the servers don't have any active pvp battlegrounds at all. I bot during nights mostly and a bg never pops on my realm.
The quest type is not available anywhere in the wow world, so we can't really mine that data out of anywhere. Me, as a profile creator, wouldn't want that feature at all. Also, the hotspot for quests is directly taken from WoW's new quest tracker (ie: directly from the game), thus that feature is pretty much useless. But I agree with 1 and 2.
The type grind means it will force honorbuddy to grind in that location until it's complete. Let's say you wanted to go to fargodeep mine instead of jasperlode, you would tell it to grind at hotspot1 until it's complete. I make the profiles too. Type="Explore" tells honorbuddy (beauty of c# and other languages) that it's not a grind quest, instead to complete all you need to do is go to hotspot1.
Awsome idea, as in Loch Mordan doing quest "In defense of the kings land" the bots goes to the cave for part 3, where the islandsin middle of lake is a far less death area for bot, to anf from caves 16 deaths as a mage, only 2 deaths on island so far
Well, with the current honorbuddy it looks like my suggestion made it through. Sweet, now it fixes alot of quests!
Quest priority so you can "define" a quest order. <Quest Id = "??" Name="??" Type="Explore" Priority="80" Hotspot1 ="X,Y,Z"> <Quest Id = "??" Name="??" Type="Grind" Priority="50" Hotspot1 ="X,Y,Z">
No need for that, just make the forced quest list go in order, rather than nearby. By simply adding a function like <ForcedQuestListinOrder>True</ForcedQuestListinOrder>
