What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

Proceed said:
Just a general question, I started the profile "[H - Quest] Tauren 1-5 [Kick]" and its questing in the tauren starting area right now, is there a certain way i need to close it, or will it recognize by itself how much questing progress has been made and continue on the point where i quit the game and closed the bot ?
Click to expand...

Hi, Proceed,

The profiles will auto-chain from one to the next until all the profiles are complete. You can read more about this in Where Do I Start?.

cheers,
chinajade
 
Wullie said:
Fix to issue:

"Zone: Valley of the Four Winds
Quest: Gardener Fran and the Watering Can - Quest - World of Warcraft
Attachment 104438
Starts out alright, but after a while it goes back to the NPC in order to get another watering can even though it still has it and could continue fine. Because it still has the buff Fran isn't offering the gossip option, which halts the bot. The watering can buff lasts 10 mins currently, it remember it being a lot less some while ago."

Problem is that Gardner Fran only gives the gossip option to obtain the "Watering Can" if you don't already have it. For some reason we first obtain it, and then try to obtain it again. The bot immediately stops as that gossip option is no longer available.
The "Watering Can" is actually an Aura on the player, rather than an actual item, so I simply surrouned the two places where it tries to get the "Watering Can" with a check to ensure we don't already have it.

Tested and working :)

Another one off the list...
Click to expand...

Hi again, Wullie!

v2744 has folded in your changes. I've also removed the issue from the Known Issues list at your confirmation of fix.


Wullie said:
This one was a little trickier but got there in the end. Don't suppose there's a guide on the "Development Tools" functionality, specifically how to run methods like IsObjectiveComplete from there (It was moaning about accessibility level as it's a protected method).
Click to expand...
Sadly, the Developer Tools dialog is subject to the same constraints as the compiler. If the method is protected or private, the Developer Tools does not have access to it either.

cheers & thanks for knocking out another!
chinajade


[size=-2]Ref: Yet another Wullie quest fix![/size]
 
Luvs2spludge said:
Forgive for my many post lol,
But minus my other issue china,

I ran into something this am, I would have posted then, but OMG i was so damn tired.

Ok so in the WL file 68-80, it keeps resting my pull distance to 0, and then it stood there not doing anything.

I hope to god this doesn't have to do with my previous issue, but here is the log.

If it does, im going to be very upset cause this issue is really bugging the hell out of me.

View attachment 104619

If this issue precisest with no fix, I just might give up on HB all together, but I know you are doing everything you can to help and that i do appreciate.
Click to expand...

Hi, Luvs2spludge, and thank you for the log,

Until we get that other problem repaired, there is simply no point in chasing this. Trying to debug a damaged install is simply a waste of time. We need to get the primary problem repaired first.

I responded to your post in the Support forum. Hopefully, with more eyes on the issue, someone will figure it out. Both CodenameG and Tony are much better than I am at diagnosing issues like this. At worst case, they may need to have you use the Honorbuddy Service.

cheers,
chinajade


[size=-2]Ref: Loves2spludge's original post w/log[/size]
 
Wullie said:
Just to confirm that your previous fix to the issue:

"Hop Hunting" (Hop Hunting - Quest - World of Warcraft)
About line 1247.
Apparently, Bliz has changed the gossip options on Gai Lan.
[12:02:53.112 N] [InteractWith-v719(error)] Gai Lan is not offering gossip option 2 on page 1. Did competing player alter NPC state? Did you stop/start Honorbuddy? Terminating behavior.[/font][/indent]
Ref: Copyleft's problem report w/log"

Has worked perfectly. My last toon through here had problems, this time it was smooth, no issues. I have not done a single quest manually, and have only ran kicks, so it's safe to assume these are the new and correct gossip options.
The only bit that's got me wondering is that I think that this NPC provides dailies though, so that may effect the available options. Perhaps worth a comment in the profile to prevent it being changed "back" if dailies to turn out to be effecting it.
Click to expand...

Wullie, thank you for the confirmation!

The item has been removed from the Known Issues list. In v2745 of the profile, I've also added a maintainer's note that quest options change based on order of quest turnin. So, hopefully future maintainers won't make that same mistake.

cheers,
chinajade


[size=-2]Ref: Wullie's confirmation of repair[/size]
 
paintgod93 said:
Hey Kicks, just wanted to say thank you for the in-depth explanation to get this running correctly. Mucho appreciated.
Click to expand...

Hi, Paintgod93,

Thank you for the kind words. We are always looking for ways to improve.

cheers,
chinajade
 
Wullie said:
One thing I did notice is that the profile at present is:

Code: 
<CustomBehavior File="InteractWith" QuestId="30031" QuestObjectiveIndex="3" MobId="210023"
				IgnoreMobsInBlackspots="true" X="-572.6497" Y="683.4078" Z="143.9894" />
			<CustomBehavior File="InteractWith" QuestId="30031" QuestObjectiveIndex="1" MobId="210021"
				IgnoreMobsInBlackspots="true" X="-496.7322" Y="667.3381" Z="136.3906" />
			<CustomBehavior File="InteractWith" QuestId="30031" QuestObjectiveIndex="2" MobId="210024"
				IgnoreMobsInBlackspots="true" X="-563.9459" Y="571.0447" Z="136.5778" />
			<CustomBehavior File="InteractWith" QuestId="30031" QuestObjectiveIndex="4" MobId="210022"
				IgnoreMobsInBlackspots="true" X="-596.4932" Y="573.7743" Z="136.4" />

Surely, that IgnoreMobsInBlackspots should be set to false if we want it to make an "exception" and get the items from inside a blackspot? Could that not be done, and the blackspot radius put back to 20? Apologies if I've misunderstood how the element functions.
Click to expand...

Hi, Wullie,

I believe you are correct. In v2747, I've increased the radius of the "Tower By Grainery" blackspot back to 20 (from 10). And the IgnoreMobsInBlackspots arguments have been flipped to "false". (The value of "true" is the default, and the attribute should've never been in the invocation if that was the true intent).

Thinking it through, I believe this to be correct. If you disagree please let me know. I'm going to leave the issue on the Known Issues list until we can confirm it.

cheers,
chinajade



[size=-2]Ref: Wullie's bug report[/size]
 
Hi

First of all a great bot. Makes playing more fun for me. But I have som issues in Hellfire Peninsula. Im playing a alliance Death Kight and the bot seems to have som problems with finding a correct path to quest and many times the bot will not fly to that location, instead it will walk.

It seems that it cant find it's way properly from Honor Hold i Hellfire.

Im attaching two log files, one from yesterday and one from this morning.

I hope I have put enough iformation for you to adress this.

Best regards
//Andreas
 

Attachments

Wullie said:
VoFW. Level 88. Quest: Evacuation Orders.

The last objective is to speak to "Wei Blacksoil" four times. For some reason after speaking to him once it just stands there beside him doing nothing. Not in combat, and ever after leaving 15 minutes didn't do anything.

After stopping and starting, same thing again - speaks to him once, then just stands there, as if it was waiting for something that never happened. I recall having to intervene the last time I had a toon here.

There are four CustomBehaviours, and although they're in a loop, it just seemed that it was stuck on one and not that it was looping endlessly.

This certainly appears to have sorted it, although I can't test "fresh" till I get another toon through.
Click to expand...

<waves at Wullie>,

v2748 has captured your corrections to the profile pack. I've also included the issue on Known Bugs List: MoP 85-90 with an indication that confirmation is all that is required.

Thanks again!
chinajade


[size=-2]Ref: Wullie's quest fix[/size]
 
Ehnoah said:
Do you plan to fix such thinks Kick? Oh and why no Quest Behaviors more? =(

I still a Fanboy of KicK! But sad that he might gone inactive?

[CastSpellOn-v664(warning)]
/********************
DEPRECATED BEHAVIOR (CastSpellOn)
The CastSpellOn behavior has been deprecated, but will continue to function as originally designed. Please replace the use of the CastSpellOn behavior with the InteractWith behavior.
The replacement command to accomplish this task is:
<CustomBehavior File="InteractWith" QuestId="14283" InteractByCastingSpellId="8921" MobId="35118" NumOfTimes="3" Range="25" MinRange="3" X="-1702.011" Y="1307.625" Z="19.78224" />
********************/
[CastSpellOn-v664(warning) @line 239]: Attribute 'WaitTime' is not recognized by this behavior--ignoring it.
Click to expand...

Hi, Ehnoah,

Yes, we intend to repair issues like this, but they are not high priority. Our priority at the moment is to get the profiles working smoothly in the new WoW 5.4 gameworld.

As stated in the message, those are just warnings, and the old behaviors should continue to work just fine. Old, and redundant behaviors are being deprecated as aggressively as we can. This makes it difficult for profiles to 'keep up' at times, but things will eventually settle out.

cheers,
chinajade
 
HB2807Z57 said:
Hi

First of all a great bot. Makes playing more fun for me. But I have som issues in Hellfire Peninsula. Im playing a alliance Death Kight and the bot seems to have som problems with finding a correct path to quest and many times the bot will not fly to that location, instead it will walk.

It seems that it cant find it's way properly from Honor Hold i Hellfire.

Im attaching two log files, one from yesterday and one from this morning.

I hope I have put enough iformation for you to adress this.

Best regards
//Andreas
Click to expand...

Hi, HB2807Z57, and thanks for the logs.

What you are reporting is not errors with the profile. You should make a post into the Support forum regarding these issues. But before going there, we'll try to help you get fixed up.

[07:04:18.269 D] MountName: Armored Snowy Gryphon
[07:04:18.269 D] FlyingMountName: Armored Snowy Gryphon​

Your MountName should be a bona-fide "ground only" mount--not a flying mount.

A flying mount as MountName will cause pathing issues, or back-and-forth motion when Honorbuddy is navigating.

In your first log, we see this:
[07:22:04.226 D] Could not generate path from {-852.9789, 2894.301, 103.3989} to {-1104.507, 3242.45, 67.1872} (time used: 0 milliseconds) @ FindStartPoly​

This may be related to the mount issue. If not, you should be able to find your help in this article:

In your second log, it looked like the bot was stopped right after Honorbuddy took 12 seconds to calculate a path, and was about to start moving. Destinations that are distant can take a few second to calculate.

If this doesn't get you fixed up, please make a post to the Support forum, and show them a fresh log with your current issue.

As to your question about using 'ground travel' instead of 'flying'...
Not all the profile in the pack have been converted to use flying yet. Currently, you won't start flying until the end of the Hellfire Peninsula profile.

cheers & happy botting,
chinajade



[size=-2]Ref: HB2807Z57's original post w/log[/size]
 
I level right now up to 90 from Level 1.

So I am not sure I am right now in redrige Mountains and if he is Indoor It spams my Log:

Is this a bug or intended? If it is a bug I report it.

He also move very often trough walls / doors etc. It all looked like he is 1 Meter to far away from "normal" way.



Code: 
[12:18:22.946 N] Moving to Type: QuestTurnIn
[12:18:23.053 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=49.3 indoors=Y canmount=N riding=0
[12:18:23.096 N] Moving to Type: QuestTurnIn
[12:18:23.222 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=49.4 indoors=Y canmount=N riding=0
[12:18:23.263 N] Moving to Type: QuestTurnIn
[12:18:23.369 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=49.8 indoors=Y canmount=N riding=0
[12:18:23.413 N] Moving to Type: QuestTurnIn
[12:18:23.510 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=50.2 indoors=Y canmount=N riding=0
[12:18:23.552 N] Moving to Type: QuestTurnIn
[12:18:23.648 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=50.7 indoors=Y canmount=N riding=0
[12:18:23.689 N] Moving to Type: QuestTurnIn
[12:18:23.790 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=51.6 indoors=Y canmount=N riding=0
[12:18:23.833 N] Moving to Type: QuestTurnIn
[12:18:23.934 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=53.0 indoors=Y canmount=N riding=0
[12:18:23.976 N] Moving to Type: QuestTurnIn
[12:18:24.079 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=54.3 indoors=Y canmount=N riding=0
[12:18:24.122 N] Moving to Type: QuestTurnIn
[12:18:24.224 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=55.5 indoors=Y canmount=N riding=0
[12:18:24.266 N] Moving to Type: QuestTurnIn
[12:18:24.374 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=56.8 indoors=Y canmount=N riding=0
[12:18:24.417 N] Moving to Type: QuestTurnIn
[12:18:24.516 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=58.2 indoors=Y canmount=N riding=0
[12:18:24.558 N] Moving to Type: QuestTurnIn
[12:18:24.657 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=59.5 indoors=Y canmount=N riding=0
[12:18:24.698 N] Moving to Type: QuestTurnIn
[12:18:24.799 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=60.7 indoors=Y canmount=N riding=0
[12:18:24.843 N] Moving to Type: QuestTurnIn
[12:18:25.090 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=63.1 indoors=Y canmount=N riding=0
[12:18:25.173 N] Moving to Type: QuestTurnIn
[12:18:25.345 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=65.4 indoors=Y canmount=N riding=0
[12:18:25.427 N] Moving to Type: QuestTurnIn
[12:18:25.598 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=67.7 indoors=Y canmount=N riding=0
[12:18:25.685 N] Moving to Type: QuestTurnIn
[12:18:25.881 D] [Singular-DEBUG] DruidMoveBuff: poitype=QuestTurnIn poidist=69.6 indoors=Y canmount=N riding=0
[12:18:25.994 N] Moving to Type: QuestTurnIn
 
Ehnoah said:
I level right now up to 90 from Level 1.

So I am not sure I am right now in redrige Mountains and if he is Indoor It spams my Log:

Is this a bug or intended? If it is a bug I report it.

He also move very often trough walls / doors etc. It all looked like he is 1 Meter to far away from "normal" way.
Click to expand...

Hi, Ehnoah,

This doesn't look like a profile issue. Please see if this article will help you resolve the problem:

If that doesn't resolve the issue, please follow our guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade
 
After installing the kick's profiles I can't find the Questing profile in the folder, did they remove it or so ?
 
Starting the bot!
Currently Using BotBase : Questing
[Compiler Error]: c:\Users\Steven\Documents\GAMING\HONORBUDDY\Quest Behaviors\QuestBehaviorCore\Utilities.cs(294,24) : error CS0111: Type 'Honorbuddy.QuestBehaviorCore.QuestBehaviorBase' already defines a member called 'UpdateGoalText' with the same parameter types
[Compiler Error]: c:\Users\Steven\Documents\GAMING\HONORBUDDY\Quest Behaviors\QuestBehaviorCore\UtilityBehaviors\UtilityBehaviors_Combat.cs(170,73) : error CS0426: The type name 'ProvideBoolDelegate' does not exist in the type 'Honorbuddy.QuestBehaviorCore.QuestBehaviorBase'
[Compiler Error]: c:\Users\Steven\Documents\GAMING\HONORBUDDY\Quest Behaviors\QuestBehaviorCore\UtilityBehaviors\UtilityBehaviors_Combat.cs(170,93) : error CS1750: A value of type '<null>' cannot be used as a default parameter because there are no standard conversions to type 'Honorbuddy.QuestBehaviorCore.QuestBehaviorBase.ProvideBoolDelegate'
Click to expand...


:D sorry if im being retarded, but just getting this now :S
 
stevendesignz said:
:D sorry if im being retarded, but just getting this now :S
Click to expand...

Sound like you've perhaps got a corrupted install.

I would recommend installing fresh to a new directory (eg don't just install over the top of existing files as that looks like the issue perhaps)
 
Questing in Krasarang Wilds. Level 88 Horde.

Quest: Finding Yi-Mo - Quest - World of Warcraft

Issue: This is just a minor one, but since it would cause the bot to "stop" and require intervention I thought I'd report and see if we can get it fixed. It seems that the bot has to travel to this NPC then speak to it initially which alters the state to the point that it can speak to it again and the complete the quest.
The bot was stuck with the initial dialog to the NPC open, and would proceed no further. Left it for a good 10 minutes I'd say.
The NPC was showing with a yellow "?" quest complete symbol, and merely manually closing the open dialog cause the bot to interact with the NPC and then complete the quest. This is why, on this occasion I'm not submitting a fix since I wasn't able to test :(

This is the section it seemed stuck in:
(Line 862)

Code: 
			<While Condition="((HasQuest(30080)) &amp;&amp; (!IsQuestCompleted(30080)))" >
				<CustomBehavior File="InteractWith" QuestId="30080" MobId="58376" CollectionDistance="1000" X="-324.2101" Y="-863.3698" Z="120.1054" />
			</While>
		<TurnIn QuestName="Finding Yi-Mo" QuestId="30080" TurnInName="Yi-Mo Longbrow" TurnInId="58376" X="-324.2101" Y="-863.3698" Z="120.1054" />

In my log you'll see around 5001 this I think is where it's stopped doing nothing for what looks around 12 minutes.

View attachment 4300 2013-09-22 14.09.txt

Specifically

Code: 
[Ref: "[N - Quest] 87-87.5 Krasarang Wilds [Kick] ($Rev: 2722 $)" @line 863]
[13:57:05.491 D] Activity: Moving to interact with Yi-Mo Longbrow (id: 58376, dist: 64.6, TtB: 49s)
[13:57:05.525 D] Inserting Yi-Mo Longbrow [Gossip, Questgiver] into the database!
[13:57:06.767 D] Activity: Moving to interact with Yi-Mo Longbrow (id: 58376, dist: 44.8, TtB: 48s)
[13:57:08.081 D] Activity: Moving to interact with Yi-Mo Longbrow (id: 58376, dist: 24.6, TtB: 47s)
[13:57:09.948 D] [Lua.Events] Attached to event UNIT_SPELLCAST_FAILED with handler HandleInterrupted
[13:57:09.963 D] [Lua.Events] Attached to event UNIT_SPELLCAST_INTERRUPTED with handler HandleInterrupted
[13:57:09.963 D] [InteractWith-v719(debug)] Interacting with 'Yi-Mo Longbrow'
[13:57:09.963 D] InteractDebug:631174756
[13:57:09.969 D] Interact Done:631174756
[13:57:10.682 D] [InteractWith-v719(debug)] Interact with 'Yi-Mo Longbrow' succeeded.
[13:57:10.682 V] Blacklisting F130E40800003011 for 00:00:30 [Type: Interact]
[13:57:11.011 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[13:57:11.011 D] Removed hook [Combat_Main] b1f5af3c-91ab-41b5-9aa0-eef47cb94efc
[13:57:11.011 D] Removed hook [Combat_Only] 0cc98675-6b73-455a-9dcb-f14607814e23
[13:57:11.011 D] Removed hook [Death_Main] 11534924-ece8-493a-bdef-801e60a69af8
[13:57:11.011 D] Removed hook [Questbot_Main] 47d105d4-56fc-4187-bd8d-91f71c9a4a1c
[13:57:11.249 N] [Singular] attention: Pull Distance set to 25 yds by Questing, Plug-in, Profile, or User 
[13:57:11.869 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedWhile.
[13:57:11.870 D] [QDBG] Starting behavior [ForcedQuestTurnIn QuestId: 30080, QuestName: Finding Yi-Mo].
[13:57:11.870 D] Goal: Turning in Quest - Finding Yi-Mo : QuestID - 30080 : To - Yi-Mo Longbrow : ID - 58376
[13:57:11.871 D] Changed POI to: Type: QuestTurnIn
[13:57:12.155 D] Stop and dismount...
[13:58:16.290 D] Updating repair cost for current equipped items. New value: [1g34s76c]
[14:08:12.949 N] [Singular] Casting Soulstone on Me @ 100.0%
[14:08:12.952 D] [CGSpellBook::CastSpell] Override ID: 20707, KnownIndex: 66
[14:08:16.215 D] [Singular-DEBUG] Spell.Cast("Soulstone"): cast has ended
[14:10:17.169 D] Updating repair cost for current equipped items. New value: [1g34s76c]
[14:11:21.531 D] InteractDebug:631174756
[14:11:21.546 D] Interact Done:631174756
[14:11:23.676 D] Cleared POI - Reason Quest Completed
[14:11:23.676 D] Cleared POI
[14:11:23.937 D] [QDBG] Done with forced behavior [ForcedQuestTurnIn QuestId: 30080, QuestName: Finding Yi-Mo].
[14:11:23.937 D] [QDBG] Starting behavior [ForcedQuestPickUp QuestId: 30082, QuestName: Cheer Up, Yi-Mo].
[14:11:23.949 D] Goal: Picking Up Quest - Cheer Up, Yi-Mo : QuestID - 30082 : To - Yi-Mo Longbrow : ID - 58376
[14:11:24.280 D] Changed POI to: Type: QuestPickUp
[14:11:25.209 D] InteractDebug:631174756
[14:11:25.215 D] Interact Done:631174756
[14:11:27.408 D] [QDBG] Done with forced behavior [ForcedQuestPickUp QuestId: 30082, QuestName: Cheer Up, Yi-Mo].
[14:11:27.408 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[14:11:27.408 D] Compiling expression '((HasQuest(30082)) && (!IsQuestCompleted(30082)))' @ line 867
[14:11:27.658 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[14:11:27.659 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[14:11:27.659 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedWhile.
[14:11:27.659 D] Compiling expression '!IsQuestCompleted(30082)' @ line 869
[14:11:27.879 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[14:11:27.880 D] Goal: InteractWith-v719: "In Progress (no associated quest)"
Interacting with Yi-Mo Longbrow

I'm not totally sure why it's not moving and completing the quest. I appears to be getting past the while loop.

Perhaps "[13:57:10.682 V] Blacklisting F130E40800003011 for 00:00:30 [Type: Interact]" is of note?

Or perhaps a "WaitTime" of some seconds on the initial InteractWith might help?

Am happy to modify profile and test out on my next toon though here, just not sure what modifications to make :)

Hope this helps.
 
Hey guys,

Is there any plan for this profile pack to be loaded into a single plugin such as cava's or brodie's? Doing so would ensure updates are done automatically and that things are installed correctly (barring any plugin update issues). Also, it saves us from downloading tortoise.
 
Please add avoid for Tagar Spinebreaker while doing the starting quests in Hellfire ([Fly][A - Quest] BC 58-70 [Kick]). Would also be nice with avoid for Fel Reaver, it killed me as well while providing log for this post. :P. Wow, and funny enough on top of this Honorbuddy crashed while copying log while it was running (not move but copy). This got alot more than I planned to report in the first place. Hope log will help to fix things. ;)View attachment 6072 2013-09-23 04.39.txt

EDIT: I see that Fel Reaver is beeing avoided already according to log, but this doesn't seem to work while in combat already. Result dies.., would been better to get regular mob adds than getting annihilated by Fel Reaver as most classes can handle that anyways.
 
Another error while doing quest Disrupting Their Reinforcements in Hellfire ([Fly][A - Quest] BC 58-70 [Kick]). Profile kept trying to use portal to close it but didn't manage to do on its own. had to help bot. Good I was not AFK a.t.m. :O

Status: 2
[03:27:36.243 D] Cleared POI - Reason Waiting for loot flag
[03:27:36.243 D] Cleared POI
[03:27:38.042 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedMoveTo.
[03:27:38.042 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedMoveTo.
[03:27:38.042 D] Goal: Moving to <-418.1776, 1861.961, 85.3735>
[03:27:40.109 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedMoveTo.
[03:27:40.112 D] [QDBG] Starting behavior [ForcedQuestObjective Objective: [UseGameObjectObjective GameObjectId: 184414, Count: 1]].
[03:27:40.113 D] Goal: Goal: Use Portal Grimh x 1
[03:27:40.163 D] Activity: Using Portal Grimh for quest Disrupt Their Reinforcements.
[03:27:40.164 D] InteractDebug:465433452
[03:27:40.182 D] Interact Done:465433452
[03:27:41.702 D] Cleared POI - Reason Successfully interacted
[03:27:41.702 D] Cleared POI
[03:27:43.407 D] Cleared POI - Reason Successfully interacted
[03:27:43.407 D] Cleared POI
[03:27:43.629 D] InteractDebug:465433452
[03:27:43.646 D] Interact Done:465433452
[03:27:45.231 D] Cleared POI - Reason Successfully interacted
[03:27:45.231 D] Cleared POI
[03:27:46.971 D] Cleared POI - Reason Successfully interacted
[03:27:46.971 D] Cleared POI
[03:27:47.175 D] InteractDebug:465433452
[03:27:47.192 D] Interact Done:465433452
[03:27:48.764 D] Cleared POI - Reason Successfully interacted
[03:27:48.764 D] Cleared POI
[03:27:50.549 D] Cleared POI - Reason Successfully interacted
[03:27:50.549 D] Cleared POI
[03:27:50.778 D] InteractDebug:465433452
[03:27:50.798 D] Interact Done:465433452
[03:27:52.400 D] Cleared POI - Reason Successfully interacted
[03:27:52.400 D] Cleared POI
[03:27:54.248 D] Cleared POI - Reason Successfully interacted
[03:27:54.248 D] Cleared POI
[03:27:54.516 D] InteractDebug:465433452
[03:27:54.534 D] Interact Done:465433452
[03:27:56.075 D] Cleared POI - Reason Successfully interacted
[03:27:56.075 D] Cleared POI
[03:27:57.879 D] Cleared POI - Reason Successfully interacted
[03:27:57.879 D] Cleared POI
[03:27:58.127 D] InteractDebug:465433452
[03:27:58.145 D] Interact Done:465433452
[03:27:59.792 D] Cleared POI - Reason Successfully interacted
[03:27:59.792 D] Cleared POI
[03:28:01.577 D] Cleared POI - Reason Successfully interacted
[03:28:01.577 D] Cleared POI
[03:28:01.818 D] InteractDebug:465433452
[03:28:01.826 D] Interact Done:465433452
[03:28:03.411 D] Cleared POI - Reason Successfully interacted
[03:28:03.411 D] Cleared POI
[03:28:05.205 D] Cleared POI - Reason Successfully interacted
[03:28:05.205 D] Cleared POI
[03:28:05.464 D] InteractDebug:465433452
[03:28:05.483 D] Interact Done:465433452
[03:28:07.054 D] Cleared POI - Reason Successfully interacted
[03:28:07.054 D] Cleared POI
[03:28:08.865 D] Cleared POI - Reason Successfully interacted
[03:28:08.865 D] Cleared POI
[03:28:09.106 D] InteractDebug:465433452
[03:28:09.123 D] Interact Done:465433452
[03:28:10.677 D] Cleared POI - Reason Successfully interacted
[03:28:10.677 D] Cleared POI
[03:28:12.489 D] Cleared POI - Reason Successfully interacted
[03:28:12.489 D] Cleared POI
[03:28:12.728 D] InteractDebug:465433452
[03:28:12.745 D] Interact Done:465433452
[03:28:14.305 D] Cleared POI - Reason Successfully interacted
[03:28:14.305 D] Cleared POI
[03:28:16.056 D] Cleared POI - Reason Successfully interacted
[03:28:16.056 D] Cleared POI
[03:28:16.267 D] InteractDebug:465433452
[03:28:16.284 D] Interact Done:465433452
[03:28:17.878 D] Cleared POI - Reason Successfully interacted
[03:28:17.878 D] Cleared POI
[03:28:19.677 D] Cleared POI - Reason Successfully interacted
[03:28:19.677 D] Cleared POI
[03:28:19.909 D] InteractDebug:465433452
[03:28:19.925 D] Interact Done:465433452
[03:28:21.527 D] Cleared POI - Reason Successfully interacted
[03:28:21.527 D] Cleared POI
[03:28:23.339 D] Cleared POI - Reason Successfully interacted
[03:28:23.339 D] Cleared POI
[03:28:23.555 D] InteractDebug:465433452
[03:28:23.571 D] Interact Done:465433452
[03:28:25.179 D] Cleared POI - Reason Successfully interacted
[03:28:25.179 D] Cleared POI
[03:28:25.520 D] System.ApplicationException: Cannot run Tick before running Start first!
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
[03:28:25.495 N] Stopping the bot!
[03:28:25.495 D] Stop called!
[03:28:25.496 Q] Bot Stopped! Reason: User pressed the stop button
[03:28:25.502 D] Behavior flags changed! All -> All
[03:28:25.510 D] Activity: Honorbuddy Stopped
[03:28:25.520 N] [Singular] attention: Pull Distance set to 45 yds by Questing, Plug-in, Profile, or User
[03:28:25.520 D] System.ApplicationException: Cannot run Tick before running Start first!
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
[03:28:25.522 D] Cleared POI - Reason Exception in Root.Tick()
[03:28:25.522 D] Cleared POI
 
You must log in or register to reply here.
Back
Top