unavailable quests... why must the bot just sit there looking stupid?

[socket]

For the love of god and everything that is holy. If the bot clicks on an NPC for a quest and can't get it why does it sit there and try until the end of time? Maybe after the 5th time it can give up and blacklist the quest for a couple hours (or even better the current session)?

 

[Kickazz006]

i don't see a log attached

 

[kyvari]

I dont see why he needs a log, ( no offense ) its a pretty simple question, and it seems like a pretty simple If loop would solve the problem. If it asks for the quest more than 1000000000 million times it should be able to figure out it cant accept the quest.

 

[Kickazz006]

if it stands there, then the profile writer needs to see what's wrong.

it could be because the user has done quests manually, or it could be a profile issue itself

 

[Lockwood]

I dont see why he needs a log, ( no offense ) its a pretty simple question, and it seems like a pretty simple If loop would solve the problem. If it asks for the quest more than 1000000000 million times it should be able to figure out it cant accept the quest.

Quite right.

A log would simply tell you what has gone wrong (usually associated with checkpoints in a profile) and the quest order.

There should be some logic to auto overide.

Problem is I dread to think how that will be handled. Thats complex, lets fix the basics of HB first please.

 

[Bengan12]

Yes this should be fixed, from time to time it fails geting an item or mixing stuff up, mostly as quest behaviors change 50 times a day, skipping a quest or two would not hurt, or atleast stoping the bot. or something. the only way it might hurt is if it is a chain and it affects other quests.

 

[Kickazz006]

actually, on a *lot* of profiles, skipping a quest does hurt.

guys, write a profile and see what happens

imo the best thing to do is that it should reload the profile automatically if it messes up, but if it *skips* a quest, especially in classic... that whole zone (or at least a lot of the quests in the zone) are screwed... depending on which quest we're talking about.

 

[Lockwood]

actually, on a *lot* of profiles, skipping a quest does hurt.

guys, write a profile and see what happens

imo the best thing to do is that it should reload the profile automatically if it messes up, but if it *skips* a quest, especially in classic... that whole zone (or at least a lot of the quests in the zone) are screwed... depending on which quest we're talking about.

Surely the question is why if the profile is correct (like many are with the correct quest orders and commands and behaviours) does HB not run it correctly.

The issue should be fixing HB. Not looking for ways to cover up HB not running questing profiles correctly.

That and the fact that the most popular levelling mode (mixed mode) is broken.

 

[Bengan12]

actually, on a *lot* of profiles, skipping a quest does hurt.

guys, write a profile and see what happens

imo the best thing to do is that it should reload the profile automatically if it messes up, but if it *skips* a quest, especially in classic... that whole zone (or at least a lot of the quests in the zone) are screwed... depending on which quest we're talking about.

automatic quest bevahiour updating and so on would be nice to. not sure if SVN updates stuf unless you force it to.

 

[Kickazz006]

the issue 95% is profile related. 4% user related, and 1% hb related...

if it's profile related, generally it's easy to fix
if it's hb related, that's why <While> conditions were applied, thus throwing it back at the profile writer

4% user issue means that the user has done something manually, which happens a lot, and they fail to tell the profile writer about it, nor provide a lot

@OP:

provide the full log via attachment

 

[Anonuzer01]

"Quest Skipped....Grinding to level 85"

 

[socket]

the issue 95% is profile related. 4% user related, and 1% hb related...

if it's profile related, generally it's easy to fix
if it's hb related, that's why <While> conditions were applied, thus throwing it back at the profile writer

4% user issue means that the user has done something manually, which happens a lot, and they fail to tell the profile writer about it, nor provide a lot

@OP:

provide the full log via attachment

I think we've opened up a bit of a Pandora's box here. No no log because I know what the problem is... which is I don't have access to the quest.

If it's the profile writers issue I'm fine with that. But seems a bit silly to expect profile writers to be able to account for every quest deficiency or the chance a specific player does not have access to a specific quest. Most of the time I just edit the profile and remove any reference to the quest. This happens on almost every quest profile I've tried lately. So if it's something quest profile writers need to address they largely are not.

 

[Lockwood]

It's a cop out to blame profile writers or users.

I've had it running top writers quests like Natforth and Kick's profiles. I always try and AFK them. I only step in once there is an error.

I read the profiles and I note if there are errors but usually there are no errors. HB has simply failed again.

 

[kyvari]

Honestly, and I truly 100 percent do not mean this in a bad or negative way, but a bot that costs as much money as it does, and as many people that have bought it, it should be a 1 click to 85. Really. It should. Honestly. Don't lie. It should. It is COMPLETE BULLSHIT that the people who make all the money off this bot do not hire "Professionals" so to speak, to make INTEGRATED quests and grinding profiles that have had hours of rigorous testing. AND CC's! (Although FPSware pretty much has this). A professional HB team that made their own stuff instead of relying on their community to do their dirty work for them would solve 99% of all issues people have with this bot. And it's seriously getting a bit pathetic. I've bought 3 lifetimes (Almost 400 dollars) and this bot isn't even close to 1 click to 85.

Just my opinion though, some people don't hold their own work to the values (err standards) I do. When it's something I care about, (a career or job or whatever) I put 110% into it. This sadly, just is not the case with HB.

(I AM NOT IN ANY CASE SAYING THAT ALL THE PEOPLE WHO WORK ON THIS DO NOT DO AN OUTSTANDING GREAT JOB, AS LOTS OF THEM ARE NOT PAID AND I KNOW THIS, THEY DO A GREAT JOB, BUT THIS COMMUNITY SHOULD NOT BE DONATION DRIVEN!)

Oh, and the bugs are annoying too =[

 

[socket]

Funny thing about this is I'm just asking why the bot never gives up. I'm not asking for it to be magic and keep going if it can't. It just doesn't make any sense why the bot stays in an endless loop (endless loops resulting in nothing useful are never a good thing or acceptable in software design generally). After five tries give up and /quit or something. Just don't sit there over and over again trying to do the same thing that failed the first 500 times.

 

[Dgc2002]

Funny thing about this is I'm just asking why the bot never gives up. I'm not asking for it to be magic and keep going if it can't. It just doesn't make any sense why the bot stays in an endless loop (endless loops resulting in nothing useful are never a good thing or acceptable in software design generally). After five tries give up and /quit or something. Just don't sit there over and over again trying to do the same thing that failed the first 500 times.

Why i would imagine it doesn't just give up:

HB is there to interpret and run what a profile writer has written. The bot should NOT make any decision on whether or not a bit of code in this profile is executed as it is stated in the profile. If HB was free to make these decisions it would cause countless problems in large profiles. Say you get a lag spike while HB is trying to pick up a quest, this quest is very important(It begins a large quest chain in Deepholm), if HB decides 'alright we've tried enough.. move on'

Problem:

Where does it move on to? The next line of code? Would be way too sloppy. To the next quest pickup? Well the next quest pickup is probably the 2nd quest in that quest line, if its not then eventually it will get to the 2nd quest in that quest line and we simply encounter this problem again. Large quest profiles(All of kick's profiles for 1-85 for example) at some point have a very specific set of steps, you don't just run around picking random quests up but you do it in a specific laid out order so that it flows well.

The problem here isn't HB at all as far as i'm concerned, its the profile. For some reason the flow if the profile is messed up, you might be too low of a level to pick up the quest so either a few more quests need to be added or a grind section should be, maybe the pre-req to the quest wasn't included in which case it will need to be scripted and added in. Also as Kick said another issue is that maybe the user stopped the bot and quested on his own/started the profile part way through their own level and for some reason HB hasn't determined that this quest has already been done. Steps can be taken to avoid this(Different logic statements in profiles) but its not perfect.

 

[Kickazz006]

also @ the 1-85 1 click comment..

you can 1-click my 1-70 so far, you used to be able to 1-click my LK profile, but due to mesh, it's buggy again (yay!) which i'll be fixing once raphus has the behaviors updated for me (nothing super drastic, adding multiple npc's to interact with, useitemon, etc etc so i don't have to "guess".

anyways, for most users, 1-70 is 1 click (my classic profile loads my BC profile). now, due to various issues (mainly gearing issues), you may have to intervene, or "stupid bot" issues such as meshing, which I can only accommodate for so much =(

but yes, i do agree that the questing bot does need a lot of work still (but compared to 1 year ago, it has come a *very* long way)

 

[Lockwood]

also @ the 1-85 1 click comment..

you can 1-click my 1-70 so far, you used to be able to 1-click my LK profile, but due to mesh, it's buggy again (yay!) which i'll be fixing once raphus has the behaviors updated for me (nothing super drastic, adding multiple npc's to interact with, useitemon, etc etc so i don't have to "guess".

anyways, for most users, 1-70 is 1 click (my classic profile loads my BC profile). now, due to various issues (mainly gearing issues), you may have to intervene, or "stupid bot" issues such as meshing, which I can only accommodate for so much =(

but yes, i do agree that the questing bot does need a lot of work still (but compared to 1 year ago, it has come a *very* long way)

Kick ur profiles are awesome. I used them for all my alliance to level 70. But even then HB spazzes out sometimes for no apparent reason. Not fully completing quests etc.

Do you not agree that for the classic dungeons and cata dungeons IB development is also a priority? The fact that people can only afk less than 10% of the dungeons is absurd. Enough with Arch buddy and more with IB.

I just can't help thinking that the new releases 'fix' things only to make other aspects unusuable.

Either way I agree with Kyvari. Far too much of this is community based. It's an exploitation and means people have to develop stuff themselves or risk having wasted a bunch of money.

 

[Kickazz006]

well that's why i'm hired, and tuba was also hired, but he didn't stay but a month and didn't release much content.

the 1-80 will have a lot of love coming up, I'm mainly waiting for the behaviors that i've been QQ'ing about so much.

after 70-80, then 1-60 will be reflowed.

BC right now is 99% flawless. The only issues i've seen are meshing & / or not obeying blackspots (ie: horde towns)

 

[zarlia28]

People really don't understand how hard it is to get a program to funtion correctly without any issues, people expect way way to much. If you think it should be 1 click to 85 you have no idea how computers work and in all honesty, you probs should not even be using this bot.