[EU ONLY][BETA] HB 1.936 - Questing Overrides and Improved Targeting
- Thread starter Hawker
- Start date
letsgo2u
New Member
- Joined
- Jan 15, 2010
- Messages
- 252
- Reaction score
- 0
check box still doesnt change <UseMount>False</UseMount> and I need to change it manually.
Raf leader no longer waits for party members
edit: in fact RaF appears totally broken generating theerror below before giving up
[11:16:16:330] RaF Leader set to:NightElf - Druid
[23:16:16.8581] [Navigator] Generated path from <-3189.538, -2127.55, 15.80757> to <-3204.502, -2219.281, 15.80314> in 141 ms (0.14 seconds)
[11:20:07:177] exception in DoTraceLine:Thread was being aborted. - at EndScene.ExecutorRand.Execute()
at Styx.WoWInternals.World.GameWorld.DoTraceLine(WoWPoint from, WoWPoint to, Single distance, UInt32 flags) - Honorbuddy
[11:20:07:507] RaF Leader set to:NightElf - Druid
[11:20:50:239] exception in DoTraceLine:Thread was being aborted. - at EndScene.ExecutorRand.Execute()
at Styx.WoWInternals.World.GameWorld.DoTraceLine(WoWPoint from, WoWPoint to, Single distance, UInt32 flags) - Honorbuddy
[11:21:28:744] Failed to set RaF Leader!
[11:21:33:873] Activity: Moving to hotspot
[11:21:33:874] Mount up - ActionMoveToHotspot
[11:21:33:965] Mounting: Mount Name Here
[11:21:34:194] Exception in DoString: Thread was being aborted. StackTrace: at EndScene.ExecutorRand.Execute()
at Styx.Lua.DoString(String lua, String luaFile, UInt32 pState)
[11:21:34:210] Thread was being aborted. - From: Honorbuddy at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.Tick()SmartExceptionsCore.UnhandledException @ 2441, offset:395
Raf leader no longer waits for party members
edit: in fact RaF appears totally broken generating theerror below before giving up
[11:16:16:330] RaF Leader set to:NightElf - Druid
[23:16:16.8581] [Navigator] Generated path from <-3189.538, -2127.55, 15.80757> to <-3204.502, -2219.281, 15.80314> in 141 ms (0.14 seconds)
[11:20:07:177] exception in DoTraceLine:Thread was being aborted. - at EndScene.ExecutorRand.Execute()
at Styx.WoWInternals.World.GameWorld.DoTraceLine(WoWPoint from, WoWPoint to, Single distance, UInt32 flags) - Honorbuddy
[11:20:07:507] RaF Leader set to:NightElf - Druid
[11:20:50:239] exception in DoTraceLine:Thread was being aborted. - at EndScene.ExecutorRand.Execute()
at Styx.WoWInternals.World.GameWorld.DoTraceLine(WoWPoint from, WoWPoint to, Single distance, UInt32 flags) - Honorbuddy
[11:21:28:744] Failed to set RaF Leader!
[11:21:33:873] Activity: Moving to hotspot
[11:21:33:874] Mount up - ActionMoveToHotspot
[11:21:33:965] Mounting: Mount Name Here
[11:21:34:194] Exception in DoString: Thread was being aborted. StackTrace: at EndScene.ExecutorRand.Execute()
at Styx.Lua.DoString(String lua, String luaFile, UInt32 pState)
[11:21:34:210] Thread was being aborted. - From: Honorbuddy at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.Tick()SmartExceptionsCore.UnhandledException @ 2441, offset:395
Last edited:
metus
Member
- Joined
- Jan 15, 2010
- Messages
- 142
- Reaction score
- 3
Okay I think I'm officially done with WoW. The time between new releases is just too slow on Honorbuddy. No offence to the developers, I know you are working hard on it, but some bugs just persist through releases which have several weeks in between them.
Botting is no longer fun for me personally, I'm more into Quake now.
Thanks HB/GB crew, you enlengthened my WoW lifespan by at least a year, but now it's over for me.
Botting is no longer fun for me personally, I'm more into Quake now.
Thanks HB/GB crew, you enlengthened my WoW lifespan by at least a year, but now it's over for me.
I got this error last release, (it was with the hog things in the area though) I just completed one of the quests by hand and it fixed it.
Mordd
New Member
- Joined
- Jan 15, 2010
- Messages
- 1,036
- Reaction score
- 33
Doing, and turning in one quest at a time is really stupid and is taking forever to level with. Leave it up to the profile author to decide when quests are safe and not safe to do. I would rather HB go out and do all the quests on its list then come back and turn them all in.
Mordd
New Member
- Joined
- Jan 15, 2010
- Messages
- 1,036
- Reaction score
- 33
Maybe the radar engineer can explain why a level 24 pally gets killed by a group of level 18 gnolls. Oh wait, it might have somthing to do with the fact that its running right into the entire camp and being overwhelmed.
Radar does not work as it should. Plain and simple. This release is no better than beta 3.
Radar does not work as it should. Plain and simple. This release is no better than beta 3.
LAP87
Member
- Joined
- Jan 15, 2010
- Messages
- 451
- Reaction score
- 0
Releases are slow i can agree on that, it's no fun when it's not working properly.
I also think it's ridicolous that this isn't the way it was built from scratch.
Really, using you breakneck profile + Convalesce (latest afaik) took me 7 hours! to get to lvl12
This, plus the patrolmode shit it's doing whenever i'm not lookin. i.e.
Quest Area A <------------x-------x------------> Quest Area B , X being the spots it runs inbetween.
Only fix so far is stopping the bot and moving it in a direction of either areas then start it up again.
Same problems here using the rogue.cc I shut HB Questing down, after the basic functions of HB are broken. Guess I'll wait until the next alpha build of HB and test again.
theatristformallyknownasG
Active Member
- Joined
- Jan 16, 2010
- Messages
- 3,041
- Reaction score
- 8
Agreed, it is what i do when I level an character by hand.
Code:
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.
Activity: Moving to turn in quest Cutting Teeth.
Activity: Moving to quest turn in at quest giver Gornek.Epic fail.
ice1ner97411
New Member
- Joined
- Jun 14, 2010
- Messages
- 4
- Reaction score
- 0
que problem
Im queing for bgs iwth the bot well av to be exact but it wont accept the que i have to do it manually.
What should i do i attached my log in the reply.
Im queing for bgs iwth the bot well av to be exact but it wont accept the que i have to do it manually.
What should i do i attached my log in the reply.
We do have some negative comments in this thread, which I don't find all that helpful, and we all know that log files are asked for when reporting issues anyway.
I wanted to say that in my own experience of using Hawkers 58-70 questing profile, with everything else clean from this download, I am seeing a much improved experience on my hunter. I'm not saying it's perfect at all and won't belittle anyone elses experiences. Yes, I am seeing quest hand-in issues and other issues that are already reported, but I am also seeing more logic being used where the bot doesn't just run through mobs on its way to a questing hotspot and will take out those mobs appropriately. Targeting seems improved. Looting is also much faster. In other words, this was worth downloading as it has improved my own experience. I don't know if it's not where it was supposed to be at for this release, but we can still be very thankful that we have devs that are actively working on it and engaged with their customer base.
I wanted to say that in my own experience of using Hawkers 58-70 questing profile, with everything else clean from this download, I am seeing a much improved experience on my hunter. I'm not saying it's perfect at all and won't belittle anyone elses experiences. Yes, I am seeing quest hand-in issues and other issues that are already reported, but I am also seeing more logic being used where the bot doesn't just run through mobs on its way to a questing hotspot and will take out those mobs appropriately. Targeting seems improved. Looting is also much faster. In other words, this was worth downloading as it has improved my own experience. I don't know if it's not where it was supposed to be at for this release, but we can still be very thankful that we have devs that are actively working on it and engaged with their customer base.
So much is changing in Cata, you think things are broken now? Just wait.
theatristformallyknownasG
Active Member
- Joined
- Jan 16, 2010
- Messages
- 3,041
- Reaction score
- 8
1. Targeting
When moving to a quest objective, the bot now searches the local environment and if there is a hostile mob in the path, will try to kill it. This ends the problem of the bot dying too often as it quested. It also works in PVP.
FAIL FAIL FAIL
this is far worse than beta 3
Atleast I know my character can take on 5 mobs at once now, 7 is a bit much though
fleeeing mob logic seems to be improved, doesn't want to chase anymore from my watchings
If my elemental attacks a mob and my character has kill his mob and elemental is still killi its mob my character just stands around and watches, not sure if that is HB or .cc related ?
When moving to a quest objective, the bot now searches the local environment and if there is a hostile mob in the path, will try to kill it. This ends the problem of the bot dying too often as it quested. It also works in PVP.
FAIL FAIL FAIL
this is far worse than beta 3
Atleast I know my character can take on 5 mobs at once now, 7 is a bit much though fleeeing mob logic seems to be improved, doesn't want to chase anymore from my watchings
If my elemental attacks a mob and my character has kill his mob and elemental is still killi its mob my character just stands around and watches, not sure if that is HB or .cc related ?
Last edited:
dayloon
Active Member
- Joined
- Mar 5, 2010
- Messages
- 1,046
- Reaction score
- 3
This beta is not the improved version i'd hope it would be, hard to believe it took 3 weeks to be honest. There are fundamental flaws in HB which need addressing before new features are added. There is no point listing them as they've been mentioned several times. Just read all of Mordd's posts.
I know it's been said many times before but doing 1 quest, handing it in, doing the next, handing it in and so on is taking a long time to level. It needs to be able to do multiple quests before handing them all in.
I know it's been said many times before but doing 1 quest, handing it in, doing the next, handing it in and so on is taking a long time to level. It needs to be able to do multiple quests before handing them all in.
Last edited:
laria
Well-Known Member
- Joined
- Jan 15, 2010
- Messages
- 5,386
- Reaction score
- 36
I don't mind slow releases, i can imagine that it's a lot of work to do it right.
I keep telling myself and others that its better to have less releases less often with less bugs than have them every day with severe flaws.
The problem i see here is major pressure on the dev-team, everyone wants a new build, so we need to show them, that we are still working on the whole thing.
What i dont like is, the fact that you push a public questing build and then a few minutes later, you push a new one to fix stuff
And /or people mention things as being broken, that were broken before and/or are very common and important, like looting, mailing and so on.
If you have some kind of release candidate, you should give it more testing by a couple of people and not just running it yourself on your own cc and profile for 2h and say "ok, works"
This can't reveal problems properly i think.
We appreciate the hard work you do, but i think the way you handle the releases and PR, you need to re_think your strategy.
I keep telling myself and others that its better to have less releases less often with less bugs than have them every day with severe flaws.
The problem i see here is major pressure on the dev-team, everyone wants a new build, so we need to show them, that we are still working on the whole thing.
What i dont like is, the fact that you push a public questing build and then a few minutes later, you push a new one to fix stuff
And /or people mention things as being broken, that were broken before and/or are very common and important, like looting, mailing and so on.
If you have some kind of release candidate, you should give it more testing by a couple of people and not just running it yourself on your own cc and profile for 2h and say "ok, works"
This can't reveal problems properly i think.
We appreciate the hard work you do, but i think the way you handle the releases and PR, you need to re_think your strategy.