1) Hotspot Order: ** Informed that this was added to HB2 (Random Portion) Insturctions in this thread. - Add flags that will allow the toon to read the hotspots in order, reverse or random by adding a flag to the <hotspots> part by adding Order="Normal/Reverse/Random" to the Hotspots opening tag<hotspots order="Normal/Reverse/Random"> 2) Class/Faction identification - Ability to execute parts of profiles depending on the Class/Faction of a toon 3) PVP Looting - Ability to loot enemy toons after killing them. Yes i know some say this is pointless but honestly, its free coin. Plus it has its own PvP advantages (not allowing enemy's to respawn near flags and such) These are just 3 of the ideas I have. Any feedback from the developers and/or other users would be appreciated. Are any of these planned for in the near future by chance?</hotspots></hotspots>
Looting bodys in wintergrasp you get roughly 1g a body. This also might help with when someone takes a while to release and hb keeps targeting the dead player on the ground.
#1 is an excellent suggestion. To add further to it you could also do a once step4 completed return to step1 and repeat. If this were implemented it would make some of the profiles so much more efficient once they have been adapted.
have an idea: level offset. with level offset you can override the set level requirement given in a profile. this would be useful when using a class weaker than another in combat. e.g. at lvl 50, it's no problem to kill a mob lvl 52 - with hunter. but it's very hard with a priest (without running completely out of mana). with such an option, you can easily use one profile for all your bots without editing the lvl ranges, you just set an appropriate offset, e.g. -2 for a priest or +1 for a deathknight
That sounds interessting. My idea: Bot should be able to go to train by it self. W/o any plug-in. So it should know how to use for example portals in Dalaran to go back to the old cities and than it run back to where its started from
that's already possible with HB2, you can tell it to randomize the hotspots and set the maximum hotspot time eg; <hbprofile><subprofile><minlevel></minlevel> <maxlevel></maxlevel><factions></factions></subprofile></hbprofile> Code: <hbprofile> SubProfile GrindArea> RandomizeHotspots>true</hbprofile> /RandomizeHotspots Set to true if you want it to randomize the hotspots MaximumHotspotTime>900000 /MaximumHotspotTime Maximum hotspot time in milliseconds LootRadius>200 Loot radius /LootRadius Hotspots> Hotspot X="1179.575" Y="1477.302" Z="303.7145" /> Hotspot X="1212.108" Y="1521.171" Z="307.2656" /> Hotspot X="1307.19" Y="1512.425" Z="318.1264" /> Hotspot X="1311.416" Y="1455.583" Z="318.0512" /> Hotspot X="1278.418" Y="1383.8" Z="310.4631" /> Hotspot X="1218.592" Y="1363.973" Z="312.2679" /> Hotspot X="1155.666" Y="1402.953" Z="310.8594" /> /Hotspots> /GrindArea> /SubProfile> /HBProfile> <hbprofile><subprofile><hbprofile><subprofile><grindarea><grindarea><hotspots><hotspots><hotspot x="1179.575" y="1477.302" z="303.7145"><hbprofile><subprofile><hbprofile><subprofile><grindarea><grindarea><hotspots><hotspots><hotspot x="1179.575" y="1477.302" z="303.7145"><hbprofile><subprofile><grindarea><hotspots><hotspot x="2007.83" y="1674.748" z="1182.126"><hotspot x="1962.856" y="1451.778" z="1175.643"><hotspot x="2294.469" y="1679.573" z="1169.85"> </hotspot></hotspot></hotspot></hotspots></grindarea></subprofile></hbprofile></hotspot></hotspots></hotspots></grindarea></grindarea></subprofile></hbprofile></subprofile></hbprofile></hotspot></hotspots></hotspots></grindarea></grindarea></subprofile></hbprofile></subprofile></hbprofile><hbprofile><subprofile><hbprofile><subprofile><grindarea><grindarea><hotspots><hotspots><hotspot x="1179.575" y="1477.302" z="303.7145"><hbprofile><subprofile><hbprofile><subprofile><grindarea><grindarea><hotspots><hotspots><hotspot x="1179.575" y="1477.302" z="303.7145"><hbprofile><subprofile><grindarea><hotspots><hotspot x="2007.83" y="1674.748" z="1182.126"><hotspot x="1962.856" y="1451.778" z="1175.643"><hotspot x="2294.469" y="1679.573" z="1169.85"> </hotspot></hotspot></hotspot></hotspots></grindarea></subprofile></hbprofile></hotspot></hotspots></hotspots></grindarea></grindarea></subprofile></hbprofile></subprofile></hbprofile></hotspot></hotspots></hotspots></grindarea></grindarea></subprofile></hbprofile></subprofile></hbprofile>
Great to hear.. now is there a link to a post that shows the new features like this one and how to implement them? or is that in the works? ** Edited: Thanks for the correction above It will be a nice addition and i'm sure everyone will be happy about it. Any idea/word on the other 2 suggestions I posted on the original post?
i can't actually write the xml tags properly it keeps getting removed -.- but you get it use the GrindArea tag along with the RandomizeHotspots , MaximumHotspotTime etc. make sure you put the Hotspots inside the GrindArea tag tho Like this: http://pastie.org/931985 Edit: i think ski is gonna write a tutorial for that later
Any chance of Objective based profile swapping? Example in the profile you have subprofiles, currently level set to move to the next part. "level 6, move to goldshire, thing" Could we have the ability to add swapping after a certain timeframe or kill number? With HB2 being able to Nav around large areas would be nice to have for example grinding mobs in booty bay for parrot pet, after 1000 kills or 3 hours, profile dependant make its way to swamp of sorrows to grind for the pet there? Nice bit of movement and zone switching is always good!
Especially to avoid getting banned becauce of exzessive area-grinding. If nobody sees you, nobody would report you
Thanks for those tags nesox, that will make some of the profiles I have been making so much more smoother.
Like Nesox said, this is all possible with a plugin as it stands now. I may start working on one since I believe it would be extremely useful.
I believe Hawker told me HB will be using the travelling salesman problem to quest efficiently. How about letting us call this function for our own hotspots?
That's not much different from doing it linearly though. The hotspots you set are static, so you can just set efficient hotspots to begin with eliminating the traveling salesman problem. Say you make a profile with 5 hotspots, set non-random: You don't need to bother with TSP because linear will be the most efficient route anyway. Now, TSP would be handy if you just set random hotspots all willy-nilly, but its easy enough NOT to do that since you're usually generating them by moving in the path you want the bot to go anyway. Questing, on the other hand, is dynamic. This is where TSP comes into play: If you have 4 quest objectives that are in all different spots, you can't just go from obj1 to 2 to 3 to 4, it's inefficient. You use TSP to generate the most efficient overall route.
I would like to request three very simple features for testing. 1. Button: Go To Vendor 2. Button: Go To Mail 3. Button: Go To Next Hotspot Or Selection List and select Hotspot. These three things would help me when I am generating profiles, working on CustomClass, and/or Manually want to interfere with a session because maybe someone else is around or some such. I would think 1 and 2 would be way easy to code maybe 30 minutes and while 3 would definitely be more difficult, I wouldn't think no more than a 4-5 hours. Gee, I guess I would like the mail button to actually be a toggle. (Toggle Go to Mail and Toggle Don't need to go to Mail.) Sometimes after I vendor and there is 1 item that needs mailed, it annoys me to run forever to the mailbox to mail that one thing... Would be nice to tick it off...
