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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

Anyone else level a monk notice everytime it goes to the class hall it can never figure out how to get to portal, you have to move him about 30 yards every time.
 
Profile for legion 99% afk.
Did handle only chain to go Stormheim.

I have started bot on lvl 100, but he is ended on 109 lvl. Did all lines in 4 zones.

Here is the best way to improove:
Let the bot take quests to dungeons. So when char hit 109 lvl users can just go to some dungeons and level up to 110
 
Hello I am running this profile and enjoying it up until I received the dungeon quest Wrath of Azshara. The quests calls for me to go into the dungeon w/ group and defeat it, however I do not have time for that. I have tried dropping the quest many times and even starting from different zones, but the autoloader always brings me back to the entrance to the dungeon whether I have the quest or not...any ideas??
 
Chuckles said:
I just got my toon from 100 to 110 in 2 days using this. A few bugs along the way but generally it did everything well. I watched all quests (because its entertaining) and manually fixed the odd stuck. Its really remarkable watching this bot (profile) do its thing and I'd like to thank you for your time and effort on it. A quick thanks for a thankless job !!
Click to expand...
Good to hear it's working well!
Most of the consistent "stuck spots" will be fixed when the blackspot system is working again.
 
elpargo said:
On azsuna's quest "Still Alive" (after completing "The Nightborne Prince") the toon should take a ride from Stellagosa but instead mounts and turns around and after walking some distance just hangs there.
Had to manually take the ride/walk it to Azurewing on every toon. Also, the Singular thread misses its master :D
Click to expand...
I think this was because of the Bonus Objective in the area.
I'm still smoothing the edges down around Bonus Objective spots - so there's a good chance it's due to the rough edges.
 
Zher0 said:
Currently getting an error with the WOD pathfinder profiles:

Code: 
[LoadProfile-LoadPr(info)] Loading profile 'Master Treasure Hunter.xml'
Changing current profile to Master Treasure Hunter ($Rev: 5593 $)
MoveTo failed to move to the location: <4390.585, 5114.498, 44.67813>
Click to expand...
This seems to be an issue brought on by the new navigation system.
The treasure it's going after is: Adventurer's Sack

The error is most-likely due to the treasure being underwater as HB3 isn't as tolerant to water as HB2 was.
If you manually retrieve this treasure, it should go on after that.

In the mean time, I'll mark this down as an issue and will look into fixing it when the lower priority profiles will be addressed.
 
godpan said:
Wtf is going on at all? Why does my character who is level 75 already still strives to the low-level location, so much so that ready to suicide himself, trying to get to BC-locations across the sea...
The selecting of the profile on auto-loader and it always chooses the wrong profile that doesnt match the level of the character.
Click to expand...
Because the original "Auto-Loader" doesn't check your player level.
Hence why it's affixed with "for Loremaster" under the "Quick Start" section.

Use "Auto-Loader v2" if you want the loader to check your player's existing level while a profile appropriate for your character is considered.
 
Joker76 said:
I think this is somehow related to the Lycanthoth the Corruptor - Quest - World of Warcraft quest that is a prerequiisite to The Shrine Reclaimed - Quest - World of Warcraft. The first quest turn in is sometimes bugged, as the comments on Wowhead will confirm, so needs to be abandoned and/or turned in manually. So I must've turned it in manually, picked up The Shrine Reclaimed - Quest - World of Warcraft and turned that in manually as well before restarting the bot.

It looks like the TurnIn for this quest is outside the /If tag, starting on line 1234 of [Fly][N - Quest] Hyjal 80-82 [Kick].xml, so the profile didn't realize I had already turned it in and kept throwing an error.

Code: 
[B][I]--snip--[/I][/B]

Should it be changed to something like below?
Code: 
[B][I]--snip--[/I][/B]
Click to expand...
I honestly have no idea why Kick wrote these profiles with those If statements.
<PickUp/> and <TurnIn/> internally check all this stuff, so the <If/> statements themselves are all redundant.

PickUp only runs if: You don't have the quest in your questlog, and it's not completed.
TurnIn only runs if: You have the quest in your questlog and it's completed.

If these conditions aren't met, the lines are ignored.
So it being outside of the If tag shouldn't matter either way.

I can look into adding extra code to handle the Blizz-end bug.
I'll go ahead and mark this down to be investigated if it's not caught and fixed by Hawker - who is currently hard-testing the 1-100 range.
 
Lockwood said:
BC - Horde Questing 58-68:

Quest: Bonechewer Blood.

Works well but takes ages- misses a lot of mobs. Could do with an increase in the pull range to improve.
Click to expand...
I've swapped out the logic here so that the bot will better handle this quest.
Thanks for the report!
 
Endocytotic said:
Problem where the bot likes to stand still and go back to a set location, both in azuna and stormheim.
Click to expand...
I've never had this reported nor have my testers ran across this issue.
Given this, I have no basis to debug off of.

If you could provide a log, or any technical information from the bot that will better help me understand what exactly is causing the issue - I'll be glad to look into it for you.
 
dottzor said:
Trying to quest in Stormheim.
Bot refuse to start.

CR: Singular
Click to expand...
There seems to be an issue with your client.
Either Honorbuddy or WoW - something is breaking the GreyMagic injection process.

Could you try with DirectX9 instead of DirectX11?
If that doesn't work - try a fresh install of Honorbuddy.
 
Frizbick said:
Hi Echo, thanks for this awesome profile pack! But would you mind adding Surumar progres, please?
Click to expand...
Progress will come after I'm able to fix all the existing issues in the Artifact Profiles + Singular.
Hopefully this will be soon - perhaps within the coming week.
 
Ghostspike0 said:
Does anyone know a workaround for the problem if you dont have draenor pathfinder on any toon and thus can't fly. The questing pack requires flying for 90-100 and the draenor pathfinder profiles are now very bugged on movement
Click to expand...
The profiles for 90-100 do not require flying at all.
In fact, they were built purely with ground navigation logic.

The flight logic that was added after-the-fact is simply "layered" in and has no affect on the original ground navigation.
If you're having issues with movement, then this is due to HB3's new navigation system.

The profiles are slowly being adapted to fully support the new navigation tolerances of HB3.
 
ezraelic said:
Were you able to fix this issue or is it on going? Cause I am caught up with it too.. and its non stop. Please get back with me, Thanks.
Click to expand...
I've pushed an edit to the pack that will make the bot farm for the item if you don't have it.
And I've also added a HasItem() check prior to running the quest pick up code to ensure the player has the item first.

This should prevent this issue from ever happening again.
 
deftoner500 said:
This works really well when it works, it might be an issue on my end, but the bot stops like every other turn in and if I hit start again it will go right back to questing... not sure what thats all about, he will run to an npc either do the turn in and stop or stop before the turn in I have to keep starting it over and over. I always deleted the cache too.

This is on legion questing with autov2 or specific zones too doesnt matter.
Click to expand...
There's no reason why it should be saying this error under normal circumstances.

For it to say that, it would have to be ignoring the "do quest" logic.
But for it to ignore the "do quest" logic - the quest would have to be complete in the first place.
But if that was the case, then the TurnIn wouldn't be saying it's not complete.

Do you have any logs of this?
 
You must log in or register to reply here.
Back
Top