[A - Quest] Human 1-60 [KaZ]

Can't get the 15-40 one to start. Giving following error:

I have tried this before manually accepting the quest, after accepting the quest, and after turning in the quest. Same error

 

any idea how i work around with tis? my toon is just stucked at 34. ;(

g:\DD\DDHb\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0122: 's' is inaccessible due to its protection level
g:\DD\DDHb\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0118: 's' is a 'type' but is used like a 'variable'
g:\DD\DDHb\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0122: 's' is inaccessible due to its protection level
g:\DD\DDHb\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0118: 's' is a 'type' but is used like a 'variable'
g:\DD\DDHb\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0122: 's' is inaccessible due to its protection level
g:\DD\DDHb\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0118: 's' is a 'type' but is used like a 'variable'
Stopping the bot!

 

that us an issue with the custom behavior TalkToAndListenToStory.cs currently it doesn't work properly without a fix, you will have to talk to them manually until updates

 

I will look into that, just comment out that quest if you have already done it so it will bypass it and let you continue for now, i have a updated release coming soon

 

so this quest will do your quests from 1 to 40? is it fixed? and only for umans?

 

hello killkaz, so far as mentioned with the problem abou talk and listen to npc with regards to cc problem, i manually did that particular quest and now its back running! thanks!

This is actually the official 1st quest profile i must say i used with breeze!! Are there any estimates when will the 41-60 be up for test? DD tyvm. i'd love to donate if u are welcoming contributions

 

Currently at 58 quest order, getting it to 60 today and doing a few modifications, and i hopefully plan to release a beta 1-60 for testing later this week.

 

gee killa thanks for the prompt update! Btw, thanks for your pm and i hope you shld have alr received it by now

back to topic. have another update. my toon is at 36, booty bay, even i unchecked Learn Flightpaths automatically, my toon still proceeds into
[1:33:43 AM:826] Changed POI to: Type: Fly

and targets the NPC below, which isthe flight master for Horde. I think it might be a HB issue? But i guess i gotta manually do this till she is out of here. *note: she's been dying because she's interacting with that gringer npc =X
Information about Gringer:
Name = Gringer
Wowhead Id = 2858
Faction = 29 [Orgrimmar]
Location = <-14448.56, 506.129, 26.27029>
Gringer" Entry="2858"

 

great profile so far, running it on paladin which is lvl16 atm without any major problems (he died quite alot on certain quests, but there murlocs were involved, so ... )

only problem ive encountered is the following:
Could not find quest giver NPC with ID 900 in database.
Could not create current in quest bot!
ThreadAbortException caught inside.
ThreadAbortException caught outside.
the bot has to turn in the quest "parker's report" but simply stops instead. moved the toon to the questgiver and turned it in manually and now its going fine again.

 

lvl 26

[7:24:06 PM:253] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.Logic.BehaviorTree.TreeRoot.a()
[7:24:40 PM:725] Start/Stop button pressed.
[7:24:41 PM:305] Cleared POI
[7:24:41 PM:565] Goal: Goal: Grind to level 16
[7:24:41 PM:565] Goal: Goal: Grind to level 20
[7:24:41 PM:565] Goal: Goal: Grind to level 21
[7:24:41 PM:565] Goal: Goal: Grind to level 22
[7:24:41 PM:565] Goal: Goal: Grind to level 23
[7:24:41 PM:565] Goal: Goal: Grind to level 24
[7:24:41 PM:565] Goal: Goal: Grind to level 25
[7:24:41 PM:565] Goal: Goal: Grind to level 26
[7:24:41 PM:567] Stop called!
[7:24:41 PM:705] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.Logic.BehaviorTree.TreeRoot.b()
at Styx.Logic.BehaviorTree.TreeRoot.a()
[7:24:41 PM:706] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.Logic.BehaviorTree.TreeRoot.a()

**Judgement**
**Crusader Strike**
#Killing Target *Panther* , Distance : 23 yards.#
#Combat Stance Enabled#
**Judgement**
**Crusader Strike**
#Combat Stance Enabled#
Stopping the bot!
ThreadAbortException caught inside.
ThreadAbortException caught outside.
Loading C:\Users\Tony\Desktop\KaZ_Alliance_15-40_QuestOrder_human-v1.0b.xml.
Changing current profile to [KaZ] Alliance 15-60 [QuestOrder]
Starting the bot!
Changing current profile to [KaZ] Alliance 15-60 [QuestOrder]
Could not find quest giver NPC with ID 739 in database.
Could not create current in quest bot!
ThreadAbortException caught inside.
ThreadAbortException caught outside

 

Try to do that quest manually first by accepting it. What I did was to open the profile and find 739 npc and then wowhead the quest name. I think most issues are wowhead related otherwise it's custom behaviours related to Hb. Hehe.

 

Try restart wow and HB. Worked for me after doing that.

 

I chose to be a hunter, the quest hunter's path, where it tells you to train steady shot, you have to do that by hand in order for it to continue. Also after the 1-5 it got stuck and kept shutting off saying no npc with #### found... i forgot the id number... anyway I moved it out of the starting zone, and put it by the guy that gives a quest right when leaving... When i turned it back on it started to work and picked up the quest... (all of this around lvl 5 I believe)

currently at level 8.5 killing some murlocs

Whats up with the future of the quests. I notice that the coding is just pick up, turn in... it may have special conditions in the profile, that I found in the "dwarf starting zone profile" that didnt work very well..

there were also clickto talk to an npc quests that it didnt like nor do.

Im a new user, so sorry for the ignorance I just got the bot today,
but from what I found is that honor buddy actually says what quest and where it is and what it should kill (i found this when I clicked on quest objective inside honor buddy.

 

the issue with the npc not found is cause you havent been near them to add them to database, this is resolved in the next release.

 

Ok i have completed the 1-60 profile working on a few mesh/custom behavior issues soon as these are resolved look for a release soon!!

 

Just came on to give an update on my new hunter, but then saw this! It's like xmas all over again!

anyway my huntard is just about to ding 24, when i checked in last night he was lvl 8 I believe.

Only issue so far, actually has already been addressed. It was that journal in the building in Duskwallow marsh... where your toon just chills outside the building...

Is there any feature that over rides paths for certain things like quest? That would be one way to solve it if it is possible.

 

hopefully this wil be fixed in next HB but for now there is a plugin called combat helper in plugin section it will fix you just standing around

 

I dont really expect you to know this, but I was botting on my laptop...

I logoff

go to my desktop, login blah blah

So I ended my bot on the laptop when I was going to turn in some quests currently @lvl 25

when I log in on the pc... it wants to go back to redridge and do quests I have already done... So What I did was zipped my folder from my laptop and dl it on my desktop

Its doing the same exact thing...

I let it go to redridge and it just sits there, with 0 quests to even get.... I did get it to the point where it said it was going to grind until level 23.... BUT IM LEVEL 25

So i log back in on the laptop and all is working well.....

only problem is i need my laptop for school work

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

EDIT: Nevermind I resolved the issue by zipping my mesh folder from the laptop, throwing it on a thumb drive, then loading it on my desktop... I then went to honorbuddy and pointed the mesh folder to that directory and everything seems to be working fine... Picked up right where I left off...

kinda sux if i have to do this everytime if i go back and forth

 

sometimes when you log out or restart a profile, when you start it it will start anywhere, thats when you have to stop it and restart it sometimes a few times till it figures out where it's supposed to be, and i have made this alot easier with my new profile that is undergoing final testing now before public testing heh

 

nice, ya after logging in and out too many times i decided to take other steps... lol