• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • [Beta] QuestBot

    Discussion in 'Archives' started by ExVault, May 4, 2016.

    Thread Status:
    Not open for further replies.
    1. PainfulDeath

      PainfulDeath Member

      Joined:
      Jul 12, 2012
      Messages:
      489
      Likes Received:
      1
      Trophy Points:
      18
      Tbh the current speed of the bot looks more like me playing, than the speed of usual grindbot (he seems like someone very slow in the head, taking second pauses between everything) -_-
       
    2. Peonsson

      Peonsson New Member

      Joined:
      Mar 22, 2014
      Messages:
      10
      Likes Received:
      0
      Trophy Points:
      1
    3. willowsan

      willowsan New Member

      Joined:
      Sep 24, 2014
      Messages:
      25
      Likes Received:
      0
      Trophy Points:
      1
      anyway to make the bot stop looting rare/RGB or make it use loot filter?
       
    4. nanggio

      nanggio Member

      Joined:
      Apr 13, 2016
      Messages:
      84
      Likes Received:
      1
      Trophy Points:
      8
      @exVault: does bot use Idler or not?, i'm afraid that GGG can detect us because i bot 12 hours per day.
      could you plz let us know about quest bot progress?, when can we disable some quest or something else?
      thank you very much
       
    5. Bitrix1004

      Bitrix1004 New Member

      Joined:
      Apr 19, 2016
      Messages:
      12
      Likes Received:
      0
      Trophy Points:
      1
    6. PainfulDeath

      PainfulDeath Member

      Joined:
      Jul 12, 2012
      Messages:
      489
      Likes Received:
      1
      Trophy Points:
      18
      A4 grand arena location, if bot chooses to explore to "wrong" (dead end) arena - he will bug out with these messages:
      Code:
      [TaskManager::Remove] Now removing [CustomLoot].
      [CustomLoot] Remove CustomLoot success.
      [FindAll] Found total 3 tgt(s) with name "colosseum_wall_door_v0?_0?_c3r2.tgt".
      [FindFirstWalkablePosition] Now trying to find walkable position for {575, 1173} (distance: 1086)
      [FindFirstWalkablePosition] Walkable position for {575, 1173} (distance: 1086) has not been found.
      [FindFirstWalkablePosition] Now trying to find walkable position for {1633, 2415} (distance: 1351)
      [FindFirstWalkablePosition] Walkable position for {1633, 2415} (distance: 1351) has not been found.
      [FindFirstWalkablePosition] Now trying to find walkable position for {437, 2277} (distance: 1719)
      [FindFirstWalkablePosition] Walkable position for {437, 2277} (distance: 1719) has not been found.
      [TgtPosition] Fail to find position for "colosseum_wall_door_v0?_0?_c3r2.tgt". Type: Closest.
      [CRITICAL ERROR] Now requesting bot to stop.
      
      solution to this is taking tp -> wp and exploring in other direction.
       
    7. matknot

      matknot New Member

      Joined:
      May 13, 2016
      Messages:
      16
      Likes Received:
      0
      Trophy Points:
      1
      so i made a new character to start the quest bot and i keep getting this error, cant figure out how to fix this. my character is bandspanking new. hasnt done anything yet.

      [GetToCoast] Current area "The Twilight Strand" is invalid for this quest stage.
      [CRITICAL ERROR] Now requesting bot to stop.
      [Stop] Now requesting the BotThread to stop.
      [Tick] Exception during execution:Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: CRITICAL_ERROR
      at EXtensions.ErrorManager.ReportCriticalError() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\EXtensions\Content-9971281\ErrorManager.cs:line 44
      at QuestBot.Helpers.ReportInvalidArea(String caller) in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\Helpers.cs:line 43
      at QuestBot.Quests.A1_Q2_MercyMission.<GetToCoast>d__16.MoveNext() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\Quests\A1_Q2_MercyMission.cs:line 138
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.Quests.A1_Q2_MercyMission.<GetToTidalIsland>d__17.MoveNext() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\Quests\A1_Q2_MercyMission.cs:line 148
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.Quests.A1_Q2_MercyMission.<KillHailrake>d__14.MoveNext() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\Quests\A1_Q2_MercyMission.cs:line 86
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.Quest.<Execute>d__14.MoveNext() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\Quest.cs:line 49
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.QuestTask.<Logic>d__1.MoveNext() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\QuestTask.cs:line 15
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Loki.Bot.TaskManager.J~Q\,W{W5yk@;CL'b<42 pc\&C".MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
      at QuestBot.QuestBot.<MainCoroutine>d__15.MoveNext() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\QuestBot.cs:line 218
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Buddy.Coroutines.Coroutine.EOY\[6>hyzBRG?8Og:5f4VZ4H!.siK(V{zJ\&qE:;h%/B$1|?Po$.MoveNext()
      --- End of inner exception stack trace ---
      at Buddy.Coroutines.Coroutine.‪​‎*​**‎‪‪*‬***‬‬‏‫*‬*​‎*​**(Boolean )
      at Buddy.Coroutines.Coroutine.​*​*‬*‏****‪​​*‏‫*‏*‫‬*‎‬‪*‪*(Boolean )
      at Buddy.Coroutines.Coroutine.Resume()
      at QuestBot.QuestBot.Tick() in C:\Users\Mat\Documents\EB24145172\3rdParty\_CONFIGS_\Default\QuestBot\Content-9971734\QuestBot.cs:line 147
      at Loki.Bot.BotManager.‫*​‬*‬‎*​*‪***‫‏‎*‬‏‫*‪*‏*(IBot )

      [QuestBot] Stop
      [CommonEvents] Stop
      [AutoFlask] Stop
      [AutoLogin] Stop
      [DevTab] Stop
      [EXtensions] Stop
      [ItemFilterEditor] Stop
      [ObjectExplorer] Stop
      [StuckDetection] Stop
      [OldRoutine] Stop
       
    8. nanggio

      nanggio Member

      Joined:
      Apr 13, 2016
      Messages:
      84
      Likes Received:
      1
      Trophy Points:
      8
      U have to create a text file : "QuestProgress.txt", put 0,0 inside (look at first post)
       
    9. ExVault

      ExVault Moderator Moderator Buddy Core Dev

      Joined:
      Oct 23, 2013
      Messages:
      748
      Likes Received:
      57
      Trophy Points:
      28
      If you created a new character - do not mess with "QuestProgress.txt". According to your log, you did. You are standing in Twilight Strand and your current quest is Mercy Mission. You either manually moved your character back to Twilight Strand after Enemy At The Gate quest was complete or manually set current quest to Mercy Mission before Enemy At The Gate was complete.

      I think its clearly stated on the first page that you don't have to do any "QuestProgress.txt" actions for a new character.
       
    10. matknot

      matknot New Member

      Joined:
      May 13, 2016
      Messages:
      16
      Likes Received:
      0
      Trophy Points:
      1
      i started the bot as soon as i logged in and he did nothing and i had to manual move him around a bit b4 he started moving on his own but he wasnt really following quests and also getting stuck at the portal gates, assuming i never found them wile on the maps so the bot would just stand there in town saying im stuck.
       
    11. hegs

      hegs New Member

      Joined:
      Jun 5, 2011
      Messages:
      101
      Likes Received:
      1
      Trophy Points:
      0
      any updates?
       
    12. nanggio

      nanggio Member

      Joined:
      Apr 13, 2016
      Messages:
      84
      Likes Received:
      1
      Trophy Points:
      8
      u dont get my idea :).
       
    13. toNyx

      toNyx Well-Known Member

      Joined:
      Oct 29, 2011
      Messages:
      3,770
      Likes Received:
      35
      Trophy Points:
      48
      Explain it then...o_O
       
    14. Tormiasz

      Tormiasz Community Developer

      Joined:
      Jun 16, 2014
      Messages:
      701
      Likes Received:
      5
      Trophy Points:
      18
      [​IMG]
      How ExVault is feeling now
       
    15. ExVault

      ExVault Moderator Moderator Buddy Core Dev

      Joined:
      Oct 23, 2013
      Messages:
      748
      Likes Received:
      57
      Trophy Points:
      28
      Update
      - QuestBot now has build-in stuck detection. This implementation is more advanced than default one, i.e. it will trigger faster if you actually stuck and will not trigger if you just having a long fight with some fat mob. It also does not trigger on lengthy actions like waiting for exit from Vaal Pyramid or Dominus second form spawning. Default StuckDetection plugin is no longer needed for QuestBot and should be disabled.
      - HandleBlockingChestsTask is now disabled by default and can only be activated by StuckDetection. It means now bot breaks jugs/barrels only if they actually blocking the path.
      - Fixed navigation through Daresso arena. Now bot will properly detect dead end rooms.
      - Fixed navigation through Slum Sewers. Now bot will properly detect fake grating holes (with no actual transition to Warehouse Sewers) and ignore them.
      - Fixed issue on Dominus fight with big combat range. Bot no longer endlessly attacks pre-second form immune to damage Dominus.
      - Improved bot navigation through all multilevel areas (Prison, Vaal Pyramid, Sceptre of God, Daresso Arena).
      - Improved all act boss fights (Merveil, Vaal, Dominus, Malachai).
      - After dying on boss bot will cast auras before re-entering the boss room, not after.
      - Fixed bug with IdTask bypassing the item filter and identifying everything.
      - Fixed LootItemTask blacklist ignoring and trying to pick up an item infinitely.
      - Lots of small improvements.

      Now, by default, bot is more human-like (slower). Users who wanna old fast behavior should set GlobalUseReactionWait to false in EXtensions.cs
      Don't forget to update EXtensions aswell.
       
      Last edited: May 17, 2016
    16. hegs

      hegs New Member

      Joined:
      Jun 5, 2011
      Messages:
      101
      Likes Received:
      1
      Trophy Points:
      0
      [GetToStrand] Current area "The Forest Encampment" is invalid for this quest stage.
      [CRITICAL ERROR] Now requesting bot to stop.
      [Stop] Now requesting the BotThread to stop.
      [Tick] Exception during execution:Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: CRITICAL_ERROR
      at EXtensions.ErrorManager.ReportCriticalError() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\EXtensions\Content-40973319\ErrorManager.cs:line 44
      at QuestBot.Helpers.ReportInvalidArea(String caller) in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\Helpers.cs:line 64
      at QuestBot.Quests.A1_Q1_EnemyAtTheGate.<GetToStrand>d__14.MoveNext() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\Quests\A1_Q1_EnemyAtTheGate.cs:line 131
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.Quests.A1_Q1_EnemyAtTheGate.<KillHillock>d__11.MoveNext() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\Quests\A1_Q1_EnemyAtTheGate.cs:line 70
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.Quest.<Execute>d__14.MoveNext() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\Quest.cs:line 49
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
      at QuestBot.QuestTask.<Logic>d__1.MoveNext() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\QuestTask.cs:line 15
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Loki.Bot.TaskManager.G\]-aHS'xMam4m>Ok`VH<?b9t!.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Loki.Bot.TaskManager./q\&Zspt-D1%;^)>qc;@0wK;{".MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
      at QuestBot.QuestBot.<MainCoroutine>d__15.MoveNext() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\QuestBot.cs:line 216
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Buddy.Coroutines.Coroutine.4FT\&d30_`KGUU{I !d; `%wZ\*.X05GC\.rJ~lfr%xB|Mj@\":O3.MoveNext()
      --- End of inner exception stack trace ---
      at Buddy.Coroutines.Coroutine.‏‏*‪‫****‪‬*​‬*‪‪‬‎*‏​‏*(Boolean )
      at Buddy.Coroutines.Coroutine.‎*​​‏‫*‏*‪*‪‪​‎‪*​*‬**‪*(Boolean )
      at Buddy.Coroutines.Coroutine.Resume()
      at QuestBot.QuestBot.Tick() in C:\Users\john\Desktop\1\3rdParty\_CONFIGS_\Default\QuestBot\Content-40976314\QuestBot.cs:line 145
      at Loki.Bot.BotManager.


      Not sure what im doing wrong, any help cheers
       
    17. wasted2007

      wasted2007 New Member

      Joined:
      Apr 15, 2016
      Messages:
      10
      Likes Received:
      0
      Trophy Points:
      0
      Have you downloaded the new version, right? Copy QuestProgress.txt from the old one.
       
    18. hegs

      hegs New Member

      Joined:
      Jun 5, 2011
      Messages:
      101
      Likes Received:
      1
      Trophy Points:
      0
      sure is, seems broke as fark.
       
    19. darlack

      darlack Member

      Joined:
      Mar 3, 2015
      Messages:
      252
      Likes Received:
      0
      Trophy Points:
      16
      We also can't run this new update.
       
    20. wasted2007

      wasted2007 New Member

      Joined:
      Apr 15, 2016
      Messages:
      10
      Likes Received:
      0
      Trophy Points:
      0
      I don't know what are you guys talking about. I've just copied txt file to new version and everything is ok.
       
    Thread Status:
    Not open for further replies.

    Share This Page