• Visit Rebornbuddy
  • HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

    Discussion in 'Archives' started by chinajade, Sep 8, 2013.

    1. g0n3b4d

      g0n3b4d Member

      Joined:
      Jan 28, 2011
      Messages:
      93
      Likes Received:
      0
      Trophy Points:
      6
      Wolfsbane Root Not dismounting from flying mount.

      Quest ID = 12307

      When trying to destroy the Wolfsbane Root The character does not dismount causing the quest requirements never to be completed.

      Thx,

      g0n View attachment 1220 2016-10-20 13.09.txt
       
    2. Morx

      Morx New Member

      Joined:
      Jun 29, 2012
      Messages:
      139
      Likes Received:
      0
      Trophy Points:
      0
      Quest is definitely bugged. Bot says it's trying to turn it in, but it keeps pathing through the field of ettins and dying. The worst part is then I manually put my character right next to the guy turn in NPC, and he doesn't turn it in, but runs out of the cave, and straight to a particular etin, tries to kill it, but as I'm a Mage, and not Hunter/Warlock, I die, and this process repeats causing a death loop.

      Logs attached.

      Edit: Manually turn the quest in, and start the bot up again. Still says:

      Goal: Turning in Quest - The Path of Huln (The Path of Huln - Quest - World of Warcraft) : To - Spiritwalker Ebonhorn : ID - 99153 [Ref: "Turnin" @line 703]

      However, this has already been done, so now it's sounding like a Cache issue that I need to clear out.

      Edit2: It kept saying that step of the quest because it wanted to get back to town to repair. After it did this, the step progressed to picking up the next quest like normal. The pathing logic in this area is terrible though as it runs through etins constantly, which are elites and not easy to kill.
       

      Attached Files:

      Last edited: Oct 21, 2016
    3. hdleo

      hdleo Member

      Joined:
      Oct 18, 2014
      Messages:
      69
      Likes Received:
      1
      Trophy Points:
      8
    4. wallyworld

      wallyworld Banned

      Joined:
      Jul 22, 2016
      Messages:
      409
      Likes Received:
      5
      Trophy Points:
      0
      Here's another log from a completely different character that exhibited the exact same issue as I've reported with log...This is now the 4th character that this has happened on:

      View attachment 10552 2016-10-21 08.55.txt

      Here is the hotspot that is being moved to that causes the issue:

      <Hotspot X="3045.282" Y="3367.531" Z="546.4993" />

      And removing that hotspot fixes the issue.

      I'm not sure if this log shows it or it was my previous log, but if the Graymane quest fails to start the scenario on the boat on the start of Stormheim(not HB's fault, it's a known wow bug), the character flies out into the middle of the ocean and dies from fatigue. I've had this happen twice now. I caught it this time and flew back to the boat, abandoned the quest and re-started the scenario. I dunno if there's a way to check if the scenario starts, but it definitely shouldn't fly out into the ocean just to get rez sickness.
       
      Last edited: Oct 21, 2016
    5. Morx

      Morx New Member

      Joined:
      Jun 29, 2012
      Messages:
      139
      Likes Received:
      0
      Trophy Points:
      0
      Bot isn't interacting with ground targets and instead is just trying to kill mobs to complete objective. Objective would complete much faster if it would interact with Hexxing Fetish. The bot says in the "Info" tab that it will interact with them, but it does not.

      Goal: InteractWith-Intera: In Progress (no associated quest)
      Interacting with Hexxing Fetish, MobId(94153), Vilewing Hexer, Cursed Elderhorn, Cursed Prowler
      [Ref: "[N-Quest] Highmountain [Echo] ($Rev: 5831 $)" @line 1446]

      Unable to attach log. Going to try again after I post this to try and edit one in. Thank you.
       
    6. daemon9

      daemon9 New Member

      Joined:
      Feb 11, 2011
      Messages:
      528
      Likes Received:
      3
      Trophy Points:
      0
      Using this profile I find my toon just stopped at a questgiver and HB has stopped. Here's a log:
       

      Attached Files:

    7. Khazba

      Khazba New Member

      Joined:
      Sep 15, 2015
      Messages:
      27
      Likes Received:
      0
      Trophy Points:
      0
      Hi, do we plan for this to Support the Loremaster achievement, including Suramar? :D
       
    8. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      There's currently not a ETA on Suramar.
       
    9. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      Only the actual 1-110 questing profiles are being worked on at the moment, sorry.
      The special event profiles aren't of priority at all.

      You can try using the "version 1" of them to see if they do any better.
       
    10. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      This error can be ignored.
      It shouldn't be affecting the bot's performance.
       
    11. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      I believe my testers have encountered this as well.
      I'll look into getting a timer added in - thanks for the report!
       
    12. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      Alrighty, thanks for the update - class can definitely affect how some of these bugs happened.
       
    13. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      This could be possible - but would be a lot of work.

      TurnIn code for each quest would have to be added to the profile -
      and to add code I'll need to know what quests your player currently as, which is impossible for me to know ahead of time.
       
    14. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      The combat routine you're using is spamming so much useless data into the log, it makes it almost impossible to find anything actually useful.
      It's an absolute mess. Not your fault of course :p

      The only thing I see in this log is the bot was waiting 60seconds after attempting to leave Helheim - which then you stopped the bot.
      I'll run some testers through again to see if they have any weird movement with this quest.
       
    15. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      The profiles turn them on.
      You would have to remove the code from the profiles to prevent this.

      PHP:
      <CustomBehavior File="EnablePlugin" Names="Anti Drown" />
      If you search for that specific text in the profiles, you can see where it's turned on.
      Just remove this.
       
    16. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      I've added a few attributes that should help fix this.
      Thanks for the report!
       
    17. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      That doesn't seem like a bug - just an unlucky series of events.

      Right now blackspots don't work in the bot, and the work-around Avoidance logic to make the bot avoid the Ettins was previously causing people to run off the mountain, so it was removed.
      So in terms of keeping the bot from going near the Ettins - there's not a solution. Not at least until Blackspots are working.

      I can turn off repairing and vendoring prior to this quest being executed - but that would most-likely cause even more issues.
      The only thing I could think is to have the bot force-vendor prior to doing any of this quest. That way it doesn't stray off the intended questing path and run into Ettins.
       
    18. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
    19. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      Alright, I'll investigate this hotspot with my testers.

      In terms of the WoW bug - I've seen this personally as well.
      There's code to have it loop if it fails to enter the scenario, but it seems the detection is a bit bad - I'll look into improving it.

      Thanks for the update!
       
    20. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,807
      Likes Received:
      587
      Trophy Points:
      113
      It could be because the InteractWith logic is confusing itself. This seems to be a new issue as of HB3.

      Before - it properly identify a "enemy" and a "friendly" - and would engage or interact accordingly.
      Now, it seems to only want to kill stuff, and since the Hexxing Fetish objects are "friendly" - it's not engaging(interacting with) them for this fact.

      I'm working on a work around for this.
       

    Share This Page