Not a very productive day as I've been unexpectedly busy with work.
But I have tided up the UI a little and added some popup menus.
[video=youtube_share;Puf5YtIHvPI]http://youtu.be/Puf5YtIHvPI[/video]
The combat routine is responsible for healer, combat, resting etc. The weak healing is likely the combat routine, and if you're using Singular I can attest to its extremely poor performance as a healer.
Not a very productive day as I've been unexpectedly busy with work.
But I have tided up the UI a little and added some popup menus.
Enjoy the wine my friend! My steamroll team of paladins thanks you immenselyCan't wait to get my hands on this new version.
Assuming you do run your own bot base, did you see better performance healing using a different CC? I had just stuck with it since you mentioned things could be problematic if not using Singular.
Best viewed in full screen HD.
[video=youtube_share;eaYazlzy_cg]http://youtu.be/eaYazlzy_cg[/video]
EDIT: Things to keep in mind; this is not scripted in anyway. The quest pick ups and turn ins are user definable, as is the ability to target and pull quest related mobs. Currently this is only working for quests where you are required to kill mobs for objectives. This is not a relacement for Quest bot, this is not intended to be a fully automated quest bot, its simply meant to expedite your RAF expierence and remove some of the manual process. ,
Now that's impressive! Will it collect more than one at a time and hand in when complete or just do them one by one?
Thought of one more awesome idea...
HB Navigation and LazyBoxer CTM...
Why not mesh them...
IF HB Navigation is broke and I'm stuck more than X amount of times, instead of "unstuck" attempt LazyBoxer CTM (Rename obviously)... Then if both fail, move to unstuck method. (Maybe custom type/you decide... Use some of the code from the logic sections...)
![]()
That... would be awesome to have included.
I can keep thinking of more I am sure!![]()
thank you so much for the generous donation. Its greatly appreciated![]()
One thing I noticed over the weekend was the quest object interaction. I was in the Undead starting area and even though I couldn't pick up the quest (forsaken only) all the bots would run off to a grave and repeatedly interact with it. Turning the interaction off was fine and they would continue as normal, but it's going to be annoying if I have to constantly turn if off and on.
Definitely may be the reason as I use singular for all classes. Currently running mw monk as slave. Im leveling up 8 sets of toons so I'll give as much feedback as I go.The combat routine is responsible for healer, combat, resting etc. The weak healing is likely the combat routine, and if you're using Singular I can attest to its extremely poor performance as a healer.
...I'm not sure if you answered already but how are we handling quest object interaction with the new version, as mentioned in my post here:
Emmm.... not that I wanted to get this involved in the automated questing portion of RAF Bot, but I have a very simply way of obtaining all relevant quest information from an online source, and utilizing that information I can further automate the process.
Information such as;
Map locations for almost all mobs and intractable game objects
ItemCollection - the intractable game object that yields the quest item
Mobs ID's.
etc etc...
All of which I have been unable to obtain from HB directly.
Basically, pull it from WoWHead.com
For example, the quest Westfall Stew (Westfall Stew - Quest - World of Warcraft)
One of the objectives is to gather 6 x Okra. When this item is in your bags the item ID is 57911. But, the object in the game world you need to interact / harvest this from is item ID: 203982. So far I've not been able to obtain this information from HB, thus the requirement for adscititious information. Ostensibly, fully making questing automation possible without the need for scripts or profiles.