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!

Done and seems to be working fine, I'll see how it goes over night.

Must have been the addons, I only installed last night.
 
i didnt finish shadowmoon quest before i stopped the bot .next day i started i was level 93 so it took me to gorgrond . it is stuck waiting for a person or object that is not there . i seen other people comming to my spot so i asked them and they can see it i just cant.

i tried before to start in shadowmoon to finish any quests i was missing but it moved to Gorgrond. i leveled to 94 to skip gorgrond and move to next quest but it just wanted to grind to level 96
 

Attachments

not sure if the other files would help you find where i went wrong or if it a bug... so here is all of them for this shaman
 

Attachments

joseph said:
i didnt finish shadowmoon quest before i stopped the bot .next day i started i was level 93 so it took me to gorgrond . it is stuck waiting for a person or object that is not there . i seen other people comming to my spot so i asked them and they can see it i just cant.

i tried before to start in shadowmoon to finish any quests i was missing but it moved to Gorgrond. i leveled to 94 to skip gorgrond and move to next quest but it just wanted to grind to level 96
Click to expand...
There's no checkpoint system in the Draenor profiles, so it shouldn't have skipped Shadowmoon Valley if all the quests there weren't complete.
You may want to try manually loading the Shadowmoon Valley profile instead of using any auto-loaders.

It looks like it's trying to pick up the quest Growing Wood from the NPC Glirin.

If that NPC isn't there, there's a chance that your Cache could be corrupted.
On the front page of this thread - there's the "Question and Answer" link, which on there it describes what the cache corruption is, and how to identify it.
eg: If a quest or NPC isn't visible, there's a chance it could be a cache corruption (or a breadcrumb quest was completed manually that the profiles doesn't support.)

This Wiki article here describes cache corruption in further detail, and how to 'uncorrupt' it:

 
My Bot off of this Profile Pack has been Grinding a lot in order to reach the next level for instance it is currently grinding a full level from 57-58 in Badlands, any reason why
 
Brianpheath674 said:
My Bot off of this Profile Pack has been Grinding a lot in order to reach the next level for instance it is currently grinding a full level from 57-58 in Badlands, any reason why
Click to expand...
Do you perhaps have a log of this?
I believe when Kick originally wrote these profiles, there were spots where there was a lack of quests - which as an immediate solution Kick resorted to adding mob-grind logics to farm out some experience.

This only occurs in the 12-58 level range, and should be fairly rare.
From what I can remember, there's only two occurrences of this for the Alliance profiles.

It's on my to-do list (after Legion release) to go back and remove the grind areas and replace them with more quests.
That way this can be avoided.
 
58 onwards needs fixing. 58-70 use to work pretty fine, The quest is meant to start with the orc on the stairs then move ontop the flight woman, but the profile is trying to talk to the flight woman who has no quest yet.
after fixing that its also talking to "Foward commander To'arch" who also doesnt have a quest. (Prequest is Felspark Ravine)
On this characters I havnt gotten to zangarmarsh yet but theres a quest there where it uses a item on npc were the ID is wrong so it doesnt use the item.

edit: after completion when trying to hand in, its just interacting and canceling over and over. Its the only NPC at the moment that does this. I did afew quests manually and its now questing on its own again. Once I come across the Zangarmarsh quest ill let you know its name.
 
Last edited:
DracoBlaze said:
58 onwards needs fixing. 58-70 use to work pretty fine, The quest is meant to start with the orc on the stairs then move ontop the flight woman, but the profile is trying to talk to the flight woman who has no quest yet.
after fixing that its also talking to "Foward commander To'arch" who also doesnt have a quest. (Prequest is Felspark Ravine)
On this characters I havnt gotten to zangarmarsh yet but theres a quest there where it uses a item on npc were the ID is wrong so it doesnt use the item.

edit: after completion when trying to hand in, its just interacting and canceling over and over. Its the only NPC at the moment that does this. I did afew quests manually and its now questing on its own again. Once I come across the Zangarmarsh quest ill let you know its name.
Click to expand...
I'm not sure which quest "The quest" is, or which quests you're referring to in which you're having issues with so I'll need a log or more information regarding this.

There hasn't really been any changes to the 58-70 range of profiles. Here's the commit list: Horde 58-70 Questing Commits
Any changes that have been made were general bug fixes which wouldn't be causing these issues you're listing.

The order in which quests are picked up and completed is never changed unless there's an absolute reason for them to be.
The existing order that they're in now is the order they've been since they were originally created.
So if the bot is skipping quests, or isn't doing the quests in the proper order - then you may have a cache corruption.

None of my testers have noted any issues in the 58-70 range either, however it has been a while since I've had a batch of Horde testers go completely through from 1 to 100.
I'll launch a batch of them to see what they discover
Assuming these issues are not just a issues on your end caused by cache corruptions (or whatever else) - then Blizzard would've had to of changed something in a patch.
 
Another WoD flying issue. Keeps trying to go up the ship in the north at talador (there is nothing else apart from the ship north of it). I hearthed to garrison and started the profile again to fix the issue.

What happened to the support for non-flying wod profiles? They were here at one point... doesn't make sense to remove it since we get banned every 6months, a little longer than the expected time it takes to get WoD flying.

Cant seem to delete my old 10 uploaded file on hb....

removed parts of the log since it has 100k lines


http://pastebin.com/ZQjNkx4x
 
Last edited:
gamer427 said:
Another WoD flying issue. Keeps trying to go up the ship in the north at talador (there is nothing else apart from the ship north of it). I hearthed to garrison and started the profile again to fix the issue.

What happened to the support for non-flying wod profiles? They were here at one point... doesn't make sense to remove it since we get banned every 6months, a little longer than the expected time it takes to get WoD flying.

Cant seem to delete my old 10 uploaded file on hb....

removed parts of the log since it has 100k lines


http://pastebin.com/ZQjNkx4x
Click to expand...
There are no flying specific profiles here.
The profiles on the pack support both ground and flying - and are actually tested moreso with ground-based testers.

When flying support was added, it was done so in a manner that it doesn't effect the ground logic at all.
The flying logic just acts as an invisible layer of code for people who do have flying for Draenor.

I'll check out the stuckspot to see what's going on there.
 
boneair010 said:
i'm level 13 mage and it seems to attack the tower warden and die everytime. any tips?
Click to expand...
Without a log or any other information - I can't really diagnose what's causing the bot to die on that mob.

All I can gather is what I had to Google, which Tower Warden seems to be an NPC in the southern barrens - so you must be Horde correct?
Why the bot would be going to that location while you being a level 13 isn't something anyone has reported before, so I have no information that could help you.

Do you have a log of it going to this location and dying?
If so, I can read it to see what invoked the bot to go to that location.
 
So I'm having an issue with continuity with my bot. Every time I wake up or come home from work, my bot is DC'd.

In fact as we speak right now, my bot is standing next to Rexxar trying to turn in quests, 20 seconds passed and the boss force stopped.

I looked through my logs and there seem to be a few NPC's that it doesn't "recognize" as part as the quest path and it wont pick their quest up. Other times it just DC's for no reason. I don't think it's managed to run longer than 3 hours.

Just this morning before going to work I let it run, and came home now to find out my bot got maybe 4 bars worth of EXP before DC'ing.
 
SCNickerson said:
So I'm having an issue with continuity with my bot. Every time I wake up or come home from work, my bot is DC'd.

In fact as we speak right now, my bot is standing next to Rexxar trying to turn in quests, 20 seconds passed and the boss force stopped.

I looked through my logs and there seem to be a few NPC's that it doesn't "recognize" as part as the quest path and it wont pick their quest up. Other times it just DC's for no reason. I don't think it's managed to run longer than 3 hours.

Just this morning before going to work I let it run, and came home now to find out my bot got maybe 4 bars worth of EXP before DC'ing.
Click to expand...
I'll need a log to see what's going on.
Things like this could be caused by a number of things - addons, low framerate, Blizzard changing mob Ids, etc.

If you're wanting to run questing 1 to 100, then I'd recommend using a relogger.
A relogger will relog you back into the game if the bot messes up or if you get disconnected.
 
So again, put my bot on before I left and 16 minutes later it ran into a quest it couldn't accept and DC'd. I was gone for 8 hours today and got 16 minutes of botting.

[09:36:44.753 D] Current shown quest (http://wowhead.com/quest=34609) is not the quest we want (http://wowhead.com/quest=34612). Closing the quest frame to select to correct quest.
[09:36:44.847 D] Interacting with Magister Serena (Unit Id: 79392)
 
SCNickerson said:
So again, put my bot on before I left and 16 minutes later it ran into a quest it couldn't accept and DC'd. I was gone for 8 hours today and got 16 minutes of botting.

[09:36:44.753 D] Current shown quest (http://wowhead.com/quest=34609) is not the quest we want (http://wowhead.com/quest=34612). Closing the quest frame to select to correct quest.
[09:36:44.847 D] Interacting with Magister Serena (Unit Id: 79392)
Click to expand...
Hi, SCNickerson,

You are probably running a WoWclient addon, such as AutoTurnin, that is interfering with proper Honorbuddy operation. If that is not the case, you will need to attach a FULL log to have the issue analyzed.
Ref: [post=378165][Guide] How to attach your log[/post]​

cheers,
chinajade
 
You must log in or register to reply here.
Back
Top