Moving to hunting ground waypoint 'hunting ground center'

somehow i get the feeling the devs are not too much into this here... does not feel good as a paying customer.

for those who like to see the error in action in kicks profile here is a screenshot:

http://www.thebuddyforum.com/attachment.php?attachmentid=116121&d=1388694684&thumb=1&stc=1


questgiver is Initiate Goldmine in Quartzite Basin Deepholm. Bot just stands there and waiting for something thats not there or cannot be clicked or whatever... For logs please review the earlier posts (in #11 is a log from a kicks profile error, too).

Kind regards,
McW

 

I can second this on 2 different 86 chars questing in mop both with kickass on 2 different computers on 2 different HBs.

 

so might it be that this problem is maybe however not on user (profile) side? especially when you think about the fact the problem was not noticeable before the 716 (oder 718) update... I am just thinking loud...

 

It's quite obviously a HBCore issue.

The support staff never even read your posts about the issue fully, and just gave a generic canned answer repeatedly (eg complete quest manually), so I've little faith they've done any due diligence and looked further into this unfortunately.

I've never been able to figure out the abysmal attitude of some of the support staff; I guess 90% of the issues they see are the same moronic user problems over and over again, so that must wear down any patience they have, but still, I don't think it's an excuse for not even reading what a customer has posted or trying to understand the issue in an objective manner.
I've made a number of posts in the Kicks 1-90 thread, and the support I get there from Chinajade is absolutely fantastic and never dismissive, it's a real shame that that same level of support isn't carried over to the general support forum.

Hopefully as more people complain about the issue, a proper dev will stumble over it, and fix it. For the time being I've got my tillers profiles almost all working sweet again (10/11 toons ran without intervention today), albeit with absolutely horrid workarounds.

 

this is what i get when i click on start bot with my lv 78 Dk with Kick's profiles lv 68-80 no quest in quest log anymore, ive manually completed them.

 

its not a core issue, just because changes HAVE to be made to quest behaviors and profiles break does NOT mean its a core issue. it definitely does not mean we're going to roll back stability fixes and improvements because a profile breaks. the profile creator NEEDS to update the profile.

 

Then please update Kick's Profiles since they are in your hands now...

and again even if you differ in opinion CodenameG: If the bot sets itself into a loop, where it does not come out again itself or at least turn off, how should that NOT be a core issue? I can understand that because of such a tiny thing nothing will be rolled back, but maybe you could check the code again (I mean the changes from 715 to 716) which leeds to that specific behavior of the bot. As I said various times before: It even happens with Kick's profiles... Always when the bot tries to use or press something and cannot interact with it properly... And thats NOT only a Brodie, Cava or Kick's profiles issue...

And I am pretty sure that does look like a suspisious situation for pepole from the big snowstorm company, if the bot (if used unattended) stands around for maybe hours in the qorst case, trying to press or use something it cannot reach... or whatever it does when it is Moving to hunting ground waypoint 'hunting ground center' ...

I know you all have much to do (we all have) but sometimes it pays out to read carefully what users writes....

 

Sorry CodenameG and Tony,
but this is to 100% a Core Issue and i know what is broken.

When you use the InteractWith Behavior, for example:

Code:

<CustomBehavior File="InteractWith" QuestId="25134" MobId="10556" InteractByUsingItemId="16114" AuraIdOnMob="17743" Range="5" NumOfTimes="100" CollectionDistance="1000" X="-413.3748" Y="-4101.751" Z="49.63153" />

and you dont use HuntingGrounds:

Code:

      <HuntingGrounds>
        <Hotspot X="-1322.207" Y="-5187.333" Z="1.443815" />
        <Hotspot X="-1300.66" Y="-5158.513" Z="1.31347" />
      </HuntingGrounds>

then you will get the HuntingGround Error, when the Bot dont find a Mob he can Interact with.
(maybe you will get this error to if you have HuntingGrounds, but no Mob is in range)


And because to the kick's profiles nothing was changed (on the InteractWith Codes) since HB v716, its a HB Core Issue.

Maybe the changes in Honorbuddy 2.5.9048.717 InteractWith.cs breaks it:


Or its in the Core, but with v717 you have changed something on the InteractWith.

 

Indeed, MaxMuster has pretty much nailed this one.

Recently, 'path caching' was installed to address some performance issues. The caching triggered a latent bug in QBcore-based behaviors (InteractWith is one such behavior).

The problem was captured in bug report HB-282, and has already been repaired. The repair should be available in the next Honorbuddy drop.

cheers,
chinajade

 

Thx...you are my Hero...its absolutely terrible when the Support Team say: This is a Profile Problem
But we all know: No its not.

 

what else am i suppose to say? when we know its an issue we report it to devs. in this case it appeared to be a quest profile issue. i don't write quest behaviors, i don't write the profiles all i do is troubleshoot the issue and escalate when necessary.

 

take a look at your intern bug tracker?

 

Hi, MaxMuster,

There is no real way for the Support team to be aware of all issues at all times. The team supports several products, and the bug list for each product is updated several times an hour. They are knowledgeable about plugins, quest behaviors, profiles, bots, combat routines, user and program configurations, machine specifications, interfering programs, etc--any of which can cause problems. However, nobody can know it all, and stay up to date.

To put it into perspective, the title to HB-282 was "Management Material 13640 badly broken", and the description wasn't much better. There was no meaningful search the Support team could have run to locate the issue, and correlate it to this problem.

The Support staff works with hundreds of people a day to resolve their issues. They don't have time trying to match symptoms to problem descriptions and discussions in the bug tracker if the title is not a very close match to the current problem they're looking at. Sometimes the mapping of "this bug report is the same issue I'm looking at" is not intuitive at all!

The development team doesn't "drop by" the Support forum just to help out. They come because the Support staff asks one of us to take a look.

The Support team is doing an outstanding job, IMHO.

cheers,
chinajade

 

Hi chinajade,

thank you for the first competent answer here!

Could you please tell me why it now IS a core problem, after maxmuster told you the exact code that is broken? I know he is not a regular user, cause I "know" him for a long time, but I ask myself right now: Why is it not enough when a regular customer (like me e.g. or wullie) reports an error numerous times? why is the only thing CnG and Tony say is (and they insisted again and again) "it is not a core issue", when they should know it IS a core issue? and why does BotOperator close my thread in the German section where i just tried to call attention from a more competent (sorry i dont mean that rude, i am just missing the right word, but i think you know what i mean - "knowing"?) Mod or Dev to this problem...

In my eyes this is not the right way to respond to something a "valued" customer tried to tell you guys... and in my eyes every paying customer should be a valued one ;-)

Thanks again chinajade and keep up the good work!


Edit: I wrote this before I saw the last 3 comments on this... But I still am a little bit "concerned" because of the closing of my other thread instead of just taking a deeper look and reading this thread attentively...

Edit 2: I am really glad this issue is beeing addressed now and you finally did take a look at this thread. I am no one who is opening threads and posting "errors" for nothing or if they are non existant. Lack of internal communication often leads to dissatisfied customers ;-)
I would wish for myself that an issue if someone insists a few times but not later than when 2 or more people are insisting would be redirected to someone who is more into it...

@ Tony and CnG: I bet you 2 do a great job. I know that managing a community is often a very unthankful job, but please read at least sometimes the posts of your users more attentive or at least give me the feeling you did so ... ;-) feel hugged by me

 

Quest Behaviors are not part of the core.

thats why its not a "core" issue.

the quest behavior can be changed and updated independent of the honorbuddy version again, meaning its not a core issue.

as far as BotOp closing threads, if you can pm me the link to the thread, if there was not a valid reason for it to be closed, then ill talk to him.

 

Hi,

I'm not qualified to debate if it's a core or profile issue, but I'm having the same issue with every profile I'm using. (Kick's and Cava's that is.)

The last update would have made every profile out of date ? :/

 

Hi, Raidenjack,

Please open your own Support thread—this one belongs to McWeiss. In that new thread, you will need to attach the log that captures whatever issue you describe as the problem.

Ref: [Guide] How to attach your log​

Also, we're closing this thread as "answered". We are very sorry that answer is "fixed in the next HB drop, and there is no work-around".

cheers,
chinajade