So I'm new to honorbuddy (just got it a few days ago) and was disappointed at the lack of lvl 80 farming profiles on the forums. So i decided to try to make one of my own. I read through 2 guides i found on the forums and tried to educate myself on the mesh system. When i finish making my profile and mesh files and actually run the bot it walks maybe 10 feet and then constantly fails to generate a path. What am i doing wrong? I Tried recording the mesh and running around like crazy and just mapping almost every possible point and still failed to create a profile / mesh. Any advice or tips that could help me create profiles/meshs?
IFirst of all, hi mate and welcome I had the same issue for my first time and so I started to think about whats gone wrong. I asked here in forums too and after all I found a solution. My problem was that I don't had run arround enough. Look, the mesh is some kinde of map that tells your bot "hey dude in this area you can walk". So as more as you run arround and try to walk over the whole floor as more ways your bot will find. Also remember not to jump while mapping a mesh, if you use a GM server don't fly and don't run faster then a speed of 3.5 and set hotspots as well. Good luck
Strange, i thought i might have been OVER mapping. Is there such a thing to over map an area? What I thought might have been the problem is I wasn't mapping while i was creating the hotspots and i thought they might not have been connected somehow? Still trying to learn more about how the system works to get the best experience. Kurious over at MMOwned did a great review for honorbuddy and did a nice job explaining the mesh system so I thought i had a good understanding of how things worked. Thanks for the tip, ill give it a try.
You don't have to stop mapping if you're adding a HotSpot. I found out that you ONLY should stop mapping if you're finnish with mapping. Don't try to pause it. Here you can finde a pretty nice guide remade my ZoOoOoM: http://www.buddyforum.de/showthread.php?1507-Creating-A-Mesh-Profile-Guide-[v2-0]
There really is no such thing as over mapping. The more nodes that are connected the better. Less chances of getting stuck. What I did was walk the area in a circle, setup hotspots, and then run it. Test it out. If everything went okay, I go back and mesh alittle more detailed to ensure everything runs smoothly.
I lol'd. I was meshing earlier today and setting up another profile. Worked perfect. Please provide abit more information on what your talking about, please.
There is indeed an issue with mapping. If you create a new mesh, load it, map, then save it, the file will get no data (0kb). You have to append to an existing mesh, or open an existing mesh, clear it, then map it.
Honorbuddy 1.247 is what I am using, I have not seen a issue with it. I've even made new files and it works perfect. In a post, I made a profile for a 60farm and saved it. Without problems. Is it with a different version?
There were a bunch of threads about it over the last week. Works fine for some and not for others. I myself can't make a mesh from scratch and have it work. I have to copy an existing one and clear it. (Tried with 1.247 and 1.249). Its listed as an open bug, but there's a new nav system coming soon so its a low priority.
First... Best to start a new thread, rather than hijacking an existing one. Now on to the problem... This is easily accomplished, but you'll need to use a QuestOrder to make this happen. The pattern looks like the following... HTML: <QuestOrder> <SetGrindArea> <GrindArea> <!-- ...whatever... --> <Hotspots> <!-- ...lotsa hotspots here... --> <!-- last hotspot --> <Hotspot X="-9203.612" Y="-261.6649" Z="373.0209" /> </Hotspots> </GrindArea> </SetGrindArea> <!-- do this forever --> <While Condition="true"> <!-- Grind until we're within 3 yards of last hotspot --> <GrindTo Condition="Me.Location.Distance(new WoWPoint(-9203.612, -261.6649, 373.0209)) < 3" /> <!-- Done with this loop, take a break 5-10min break --> <CustomBehavior File="WaitTimer" WaitTime="300000" VariantTime="300000" GoalText="On biobreak, back in {TimeRemaining}" /> </While> </QuestOrder>