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

Honorbuddy Beta Builds

Status
Not open for further replies.
Just tried Beta 218. Bot will not pick up a quest if the quest giver has more than one available. Using as shipped QB's.

K I have it fixed for the next push, it only affected profiles that where so long, and since the profiles I was using where only small zone sections it was not failing for me. Give me a min to fix the Dev tools and ill get another push.
 
K I have it fixed for the next push, it only affected profiles that where so long, and since the profiles I was using where only small zone sections it was not failing for me. Give me a min to fix the Dev tools and ill get another push.

Natfoth, did you get it done I still show 218 as current or did you not change the rev#? Not pushing ya just wanna know before I do a fresh set up :) Thanks for your hard work!
 
Natfoth, did you get it done I still show 218 as current or did you not change the rev#? Not pushing ya just wanna know before I do a fresh set up :) Thanks for your hard work!

Almost, will post for ya when its up.
 
Fresh install and Natfoth and for some reason there are a lot of times my toons are just trying to do the quest no matter how many mobs are killing me. lvl 65 monk windwalker.
 

Attachments

Fresh install and Natfoth and for some reason there are a lot of times my toons are just trying to do the quest no matter how many mobs are killing me. lvl 65 monk windwalker.

Fixed for the next push.
 
Left the house at lvl 44 in quest zone gone for 3 hours and its still 44 trying to accept a quest over and over and over.. Please fix this
 
Left the house at lvl 44 in quest zone gone for 3 hours and its still 44 trying to accept a quest over and over and over.. Please fix this

You didnt post a log or a beta version as there was a beta that was commited to fix it that you may not have gotten because you left it running.
 
The handin or trying to complete a quest objective over and over and over that is not possible to handin is quite common.

I would suggest that if you try to complete a quest 25 times that is marked as completed by the game/cache or how you sort it. Abanndon the quest and re-try. Otherwise put up a requester saying there is something wrong with this handin so that you can manually intervene.
 
The handin or trying to complete a quest objective over and over and over that is not possible to handin is quite common.

I would suggest that if you try to complete a quest 25 times that is marked as completed by the game/cache or how you sort it. Abanndon the quest and re-try. Otherwise put up a requester saying there is something wrong with this handin so that you can manually intervene.

I have used an auto accept/complete addon since bc for this very reason with glider first than hb. But hopefully nat will get this sorted out.
 
The handin or trying to complete a quest objective over and over and over that is not possible to handin is quite common.

I would suggest that if you try to complete a quest 25 times that is marked as completed by the game/cache or how you sort it. Abanndon the quest and re-try. Otherwise put up a requester saying there is something wrong with this handin so that you can manually intervene.

Trying to make it so it always does it just the first time so it doesnt matter, just commited a fix for this as I managed to reproduce it. Will do another build after a few more fixes.
 
Trying to make it so it always does it just the first time so it doesnt matter, just commited a fix for this as I managed to reproduce it. Will do another build after a few more fixes.

Excellent!
 
Questing seems to work more or less fine. But there are quite a few instances where the bot when (I assume). Have used FlyTo or ended up under water. Meaning it will end up with.

usually this is resolved by landing the bot or making it get ground under it's feet. If this could be resolved the questing bot could be more or less one click.

PHP:
[16:20:30.788 N] [Singular-DEBUG] .... [0] h=100.0%/m=96.8%, lstks=1, target=Glimmer Bay Orca.C64F @ 9.4 yds, th=6.0%, face=True tlos=True, tloss=True
[16:20:30.944 N] [Singular] Casting Lava Burst on Glimmer Bay Orca.C64F @ 6.0% at 9.0 yds 
[16:20:30.945 D] [CGSpellBook::CastSpell] Override ID: 51505, KnownIndex: 56
[16:20:31.880 N] [Singular] Current Kill POI dead. Clearing POI Glimmer Bay Orca.C64F!
[16:20:31.880 D] Cleared POI - Reason Unit is dead
[16:20:31.880 D] Cleared POI
[16:20:31.882 N] [Singular] Current target invalid.  No other targets available 
[16:20:32.011 N] [Singular-DEBUG] [CombatLog] SPELL_CAST_FAILED Lava Burst#51505 failure: 'Interrupted'
[16:20:32.237 N] [Singular-DEBUG] CheckCurrentTarget: changed to: (null)
[16:20:33.146 V] Blacklisting F1306274002EC64F for 01:01:01 [Type: All]
[16:20:33.147 D] Could not generate full path from {4379.452, 6154.918, -3.970875} to {4372.006, 6066.5, 0.6236644} (time used: 0 milliseconds)
[16:20:38.205 D] [CGSpellBook::CastSpell] Override ID: 32297, KnownIndex: -1
[16:20:38.248 N] Mounting: Swift Purple Wind Rider
[16:23:16.079 D] Updating repair cost for current equipped items. New value: [0g2s15c]
[16:23:58.217 D] Inserting Oracle Orphan [Gossip, Questgiver] into the database!
[16:24:18.788 N] [Singular-DEBUG] YourCurrentTarget: changed to: Brglmurgl.006F h=100.0%, maxh=10329, d=2.2 yds, box=3.0, player=N, hostile=N, entry=25199, faction=1968, loss=Y, facing=Y, blacklist=N
[16:24:22.820 D] [Mount] Flying Machine is known, but we don't have the skill to use it!
[16:24:27.268 N] Stopping the bot!
[16:24:27.269 D] Stop called!
 
Thanks for the GroupInfo.PlaceWorldMarker, now just need a built in tool for tracking placement!

<3 you guys, so much better than spell manager and lua method.
 
Natfoth,

Autoequip may be a lil borked on 227 I keep trying to replace weapon over and over, here's a log.

What mode do you have it set to? Like two hands - dual wield.
 
Status
Not open for further replies.
Back
Top