What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Honorbuddy Beta Builds

Status
Not open for further replies.
Questing bot seems to be working now.


HB Build: HonorbuddyBETA 2.5.6870.171
Bot: Questing
Profile: Kickz
CC: Singular


HB starts questing, but is crashes the WoW after a while.
 

Attachments

Still a problem with Questing while picking up if the quest giver has 2 or more quests to give. Else i would say the questing is working good.
 
mrmanid said:
Questing bot seems to be working now.


HB Build: HonorbuddyBETA 2.5.6870.171
Bot: Questing
Profile: Kickz
CC: Singular


HB starts questing, but is crashes the WoW after a while.
Click to expand...

i have the same evrything works in the beta but afther awhile in netherstorm it crashes also using kicks profile we have to wait application acces violation or somthing memory couldnt read only with the beta i have those and the stable isnt working with questing
 
mrmanid said:
Questing bot seems to be working now.


HB Build: HonorbuddyBETA 2.5.6870.171
Bot: Questing
Profile: Kickz
CC: Singular


HB starts questing, but is crashes the WoW after a while.
Click to expand...

Looks like the culprit is the following "Plugins\Refreshment\Apoc Refreshment"

Memory error comes after you char trys to drink.
 
GetQuestByID also seems to return null reference exception.
 
Memory exceptions here there and everywhere... Common developers make memory processing and interactions error free... Hawker fix that shit!
 
Had a issue first go with questing on this release beta at first where it would just mount then sit there and bot would spam " returning to the center of the hunting ground" over and over till the bot stopped itself. But restarted the bot and tried again and everything so far is working great on kicks 89-90 townlonggsteps !! Thanks so much for working on the questing ! edit: Although my hunter thinks we got a badass over here and pulls to many mobs a bit much and gets roflstomped now and then lol
 
Last edited:
I second the problem with quest-giver having more than One quest, heres the important part of my log with a little Background:

Code: 
[16:30:12.584 D] InteractDebug:963599588
[16:30:12.597 D] Interact Done:963599588
[16:30:14.345 N] Choosing Crime Scene Tape.
[16:30:15.387 N] [AutoEquip]: Equipping Waist "Crime Scene Tape" instead of "Simple Cord" - it scored 244 while the old scored 42
[16:30:16.944 D] Cleared POI - Reason Quest Completed #2
[16:30:16.944 D] Cleared POI
[16:30:17.112 D] [QDBG] Done with forced behavior [ForcedQuestTurnIn QuestId: 26209, QuestName: Murder Was The Case That They Gave Me].
[16:30:17.114 D] [QDBG] Starting behavior [ForcedQuestPickUp QuestId: 26213, QuestName: Hot On the Trail: The Riverpaw Clan].
[16:30:17.128 D] Picking up Hot On the Trail: The Riverpaw Clan : 26213
[16:30:17.128 D] Goal: Picking up Hot On the Trail: The Riverpaw Clan
[16:30:17.128 D] Changed POI to:Type: QuestPickUp
[16:30:17.387 D] InteractDebug:963599588
[16:30:17.408 D] Interact Done:963599588
[16:30:21.794 D] Cleared POI - Reason Quest Completed
[16:30:21.794 D] Cleared POI
[16:30:21.960 D] Changed POI to:Type: QuestPickUp
[16:30:22.223 D] InteractDebug:963599588
[16:30:22.238 D] Interact Done:963599588
[16:30:26.060 D] Cleared POI - Reason Quest Completed
[16:30:26.060 D] Cleared POI
[16:30:26.324 D] Changed POI to:Type: QuestPickUp
[16:30:26.550 D] InteractDebug:963599588
[16:30:26.566 D] Interact Done:963599588
[16:30:30.508 D] Cleared POI - Reason Quest Completed
[16:30:30.508 D] Cleared POI
[16:30:31.050 D] Changed POI to:Type: QuestPickUp
[16:30:31.333 D] InteractDebug:963599588
[16:30:31.348 D] Interact Done:963599588
[16:30:35.085 D] Cleared POI - Reason Quest Completed
[16:30:35.085 D] Cleared POI
[16:30:35.228 D] [QDBG] Done with forced behavior [ForcedQuestPickUp QuestId: 26213, QuestName: Hot On the Trail: The Riverpaw Clan].
[16:30:35.229 D] [QDBG] Starting behavior [ForcedQuestPickUp QuestId: 26214, QuestName: Hot On the Trail: Murlocs].
[16:30:35.243 D] Picking up Hot On the Trail: Murlocs : 26214
[16:30:35.243 D] Goal: Picking up Hot On the Trail: Murlocs
[16:30:35.243 D] Changed POI to:Type: QuestPickUp
[16:30:35.472 D] InteractDebug:963599588
[16:30:35.488 D] Interact Done:963599588
[16:30:39.644 D] Cleared POI - Reason Quest Completed
[16:30:39.644 D] Cleared POI
[16:30:39.809 D] Changed POI to:Type: QuestPickUp
[16:30:40.036 D] InteractDebug:963599588
[16:30:40.076 D] Interact Done:963599588
[16:30:43.381 D] Cleared POI - Reason Quest Completed
[16:30:43.381 D] Cleared POI
[16:30:43.535 D] [QDBG] Done with forced behavior [ForcedQuestPickUp QuestId: 26214, QuestName: Hot On the Trail: Murlocs].
[16:30:43.537 D] [QDBG] Starting behavior [ForcedQuestObjective Objective: [CollectItemObjective ItemID: 57755, Count: 1]].
[16:30:43.537 D] Goal: Goal: Collect Riverpaw Gnoll Clue x 1
[16:30:43.547 D] Activity: Moving to hotspot
[16:30:43.549 D] Unloading tiles!
[16:30:43.553 D] Activity: Loading Tile/s
[16:30:43.555 D] Loading Azeroth_30_50
[16:30:43.977 D] Activity: Moving to hotspot
[16:31:00.948 D] Activity: Setting Riverpaw Gnoll at 25 yards as your target
[16:31:01.124 D] Inserting Prairie Dog [PetBattle] into the database!
[16:31:01.482 D] Changed POI to:Type: Kill, Name: Riverpaw Gnoll

All in all: Nice work, if you fix this prob too you're my heroes^^
 
No log, but when I am trying to quest with the newest beta version, it will kill mobs for any certain quest, but unless the mob is INSIDE my area in which I can loot a mob, it will not run to any corpse, and loot anything at all.
 
finalization said:
No log, but when I am trying to quest with the newest beta version, it will kill mobs for any certain quest, but unless the mob is INSIDE my area in which I can loot a mob, it will not run to any corpse, and loot anything at all.
Click to expand...

This Beta is older then the newest test release!!!!!!!!
 
version 2.5.6870.171 questing with kikcs profile is working as intended for me? (so far)
 
bot isnt compiling quests properly after game crashed (lvl 5 gnome area) it tries to go back to very first quest


was working 100% till i received a crash
 
blaza said:
Fail, the Beta has another number.

look " Last edited by Natfoth; 02.03.2013 at 08:31. "

lol :D
Click to expand...

I know what the edit says, but if you click the link you will download a beta that is newer than the test release.

I wouldn't have posted if the current beta were not newer than the latest test release.

Therefore, you fail sir, for posting a "You fail" post prior to verifying the information yourself and making an assumption that the "last edit" date is an indication of when the latest beta build was pushed.
 
blaza said:
Fail, the Beta has another number.

look " Last edited by Natfoth; 02.03.2013 at 08:31. "

lol :D
Click to expand...

And you missed :

This version will ALWAYS be later then the current release even if the thread is not updated

On the first page?

The last test release was newer than the beta at the time yes. That was to stop people whinging so much since apparently it was too hard to click on the Beta thread. Seems they are back to normal as far as latest release being in the Beta release thread.
 
This Beta-Version works very good with my Drui. Youre on the right way :-)
 
So far, questing on Beta 6870.171 seems to be working. However, if I ran the TuanaDK CC movement was very screwy and all it wanted to do was run around in circles. Tried it with Singular and everything is running without a hitch so far.
 
Status
Not open for further replies.
Back
Top