HB ARCHIVES: Kick's Old Posts Thread--DO NOT DELETE!

Here is the profile & log, could u please take a look at it?

View attachment 22.08.2012_17_59 3316 Log.txt

View attachment Questeer.xml

 

I tried a restart with no luck. Im thinking its because I am LVL 69 and completed that area and it had no where to go next. So I loaded 70-80 Profile and he wouldn't leave netherstorm. I hearthed to Org and he wont leave Org im wondering if i need to send him to borean manually?

 

I fixed the Warning message by changing
<CustomBehavior File="FlyTo" Name="Repair Run" X Y Z />

to
<CustomBehavior File="FlyTo" DestName="Repair Run" X Y Z />

I am trying to grind with fly mail/repair support with the template you told me to use, could you please explain to me why it wont behave or atleast give me something to work with instead of trashing my replies -.-

But it still flies to first hotspot, then mounts and does a repair run, followed by flight back to first hotspot and doing repair run again.
Just an endless loop of repairing

Here is the profile & log, could u please take a look at it?

View attachment 22.08.2012_17_59 3316 Log.txt
View attachment Questeer.xml

 

please make your own thread in the dev forum and i'll look at it

 

Finaly got to 68 with your profile Great
But going to start LK 68-80 now but when i have taken the first quest Warchief's Command Northrend! and click start the bot is deleting the quest and starts saying

[Profile Message]: If the bot takes more than 10 seconds to move, it is compiling quests to see where you are - it's about 1 minute per zone completed
[Profile Message]: Compiling Borean Tundra Quests
[Profile Message]: Compiling Warsong Hold Quests
Moving to Type: QuestPickUp

After 30min i quit the bot.

 

as stated in the first post, attach the log if you want assistance

 

I have a Worgen at level 70 with the running ability instead of mount. When I load 70-80 I just wants to run and train mount, how can I make it use the Worgen running abilty?

 

Hi, got a question or maybe a request. I have used your profile on 6 toons and i must say that it is amazing. Sometimes it get stuck or something but that are small stuff. But got a question. When it's done in winterspring 53.5-54 , it always need to kill alot of mobs to get to lvl 55. Shouldn't it be better to but in some quest in another zone beetwin winterspring and Silithus, like Un'Goro Crater or something ? The same goes for then it's in northrend and need to kill alot of mobs in storm peaks. It should save some time when levling.. And again, an amzing job you put into this profile.

 

I am currently level 12 using Singular as CC, and it get's stuck on FP. It just toogle's the FPs but does completly nothing. Any help? Dunno where to find logs etc..

 

Hey guys,
I am having a bit of a problem with the bot/profile.. I have leveled 1-64 currently with no problems but now the bot seems to go to the quest giver/turn in and just stay doing nothing.. If I manually click the turn in/accept it happily goes off and carries on working.
Nothing is happening in the log either it just says turning in/accepting quest and stays like it until I stop the bot or help it with accept/turn ins.
Is anyone else having this in Zangermarsh?

 

Im having kinda the same issue, since I got my flying mount it wont do anything, its just stuck on
I am in HFP

P.S. Kinda Confused on how to attach a log
[7:31:04 PM:566] [FlyTo-v217(debug) @line 1953]: Flying to 'Turnin Quest': <-702.8469, 1889.476, 61.3567>.

 

Hey Kick im having some issues with the Classic Alliance questing profile. Started out in NE starter area and then swung over to Goldshire On several of the quests i am getting the message Could not create current in quest bot; exception was thrownThe type initializer for 'Styx.Logic.Profiles.ProtectedItemsManager' threw an exception. any thoughts on this??

 

reinstall from scratch

 

i have already done it twice but now that some i have said that it will work...thanks Kick!!

 

Hi Kick,

There's a bug I've found on all my toons when they're on the Burning Steppes quest Strategic Cuts, specifically when trying to kill the troll at the top of the tower Voodooist Timan.

The problem is that the bot runs to the top of the tower and then runs off the back of it. After landing, the bot runs into the outside wall of the tower indefinitely. When one of my toons was stuck on this, I actually saw another toon doing the exact same thing as mine, which was pretty hilarious.

I think if the RunTo coordinates at the top of the tower could be updated this could fix the problem. I can't login to the game to troubleshoot this right now, but will try to when I can login later today.

View attachment 8-23-2012_9_46 AM 5924 Log.zip

 

fixt and committed to svn

 

Hi Kick,

I svn'd and, while he no longer runs off the top anymore, the problem now is that he doesn't use the item on the NPC. I checked your code and it seems correct, but I'm not sure why it's not working. Any ideas?

View attachment 8-23-2012_12_20 PM 2068 Log.txt

 

dunno what to tell you, it should use it, wait 10s and try to use it again :|

 

Yeah, I've tried it four times now, restarting the bot and/or stopping and starting the bot. It won't use the item on the NPC.

View attachment 8-23-2012_12_40 PM 5808 Log.txt
View attachment 8-23-2012_12_53 PM 5500 Log.txt

I'll try abandoning the quest and running the profile again when I get home.

 

Hi Kick,

So I spent an hour troubleshooting this when I got home and was able to kill the troll and undead NPCs. The ogre was bugged out, and, as I read on Wowhead, won't work until a server restart.

Edit: Turns out killing the ogre on one of my 85 toons reset him, and I was able to kill him along with the troll and undead with this code fix.

To kill all three NPCs I replaced UseItemOns with RunTos and /tar and /use macros. The previous positioning put the bot in front of the troll, and you have to be behind him to use the item (this only appears as an in-game error, it doesn't show in the logs). I also put the ogre in front of the undead because the ogre is closer to the troll.

To implement this fix, replace lines 7546-7559 with this: