Discussion in 'Archives' started by chinajade, Mar 25, 2011.
how add this hotspot to blacklist ?
Hi, Tumbum, and thanks for the screenshots.
We've added your information to HB-1817 ("ArchaeologyBuddy: Unable to blacklist Draenor digsites?").
Hi, Rewards, Tia1979, and Jenia, and many thanks for the logs!
This was issue HB-2039, and should have been repaired in the .773 drop.
Hi, Stip, and thank you for the log.
The log shows you logged out because Honorbuddy was spent 20 minutes downloading new mesh data. We've opened a bug report against this issue. But, this problem should be recovered if you simply launch Honorbuddy again.
[size=-2]Ref: Stip's problem report w/log[/size]
The endless loop wasn't actually fixed in .773 though. It is still doing it for me, even now on 774. It just stands there endlessly finding digsites and doing nothing else
Tell a lie. It psyched me! Tried with Tuanha and Singular, logs attached.
Disregard. I uninstalled, deleted the folder and installed new. Works again!
Character still stands there. Came here, read to restart HB. Did that, still just stood there looking for digsites. Deleted the mesh folder to force download of meshes. Meshes loaded, still stood there.
Are you planning on implementing the draenor filters in the bot?
please add the dreanor sites for blacklisting. the bot will go to nagrand and be killed pretty easy since some of the sites are directly on a spot with elite 100s all over.
I am noticing the same problem as stated above, about the character just standing there.
clean install, latest HB.776, addons disabled, even meshes re-downloaded - toon just stands and spams log endlesly. Issue may not happen at start, but for sure happens on Kalimdor only. While Eastern Kingdoms, Outlands, Nordskoll are fine. Bot/Wow restart does not remove problem.
View attachment 5520 2015-03-24 15.56.txt
Hi, Plzdontban, Blind_nuku, and Muhamuh,
Indeedy, we discovered the problem wasn't repaired and placed issue HB-2039 back on the '.776 Known Bugs List.
Hi, ILLu710N, and Jsimmons10,
Yes, the feature request is captured into the Known bugs list.
Could you please advise where I can find documented ArchBuddy methods and properties like Honorbuddy Documentation - Redirect ? I am trying to make some plugins/profiles for it, but there's hardly any information available...
The bot base itself hasn't even worked for a month now, seems infinitely low on their priority list
ArchaeologyBuddy was not meant to be extended. That's why its not included in the Sandcastle documentation you cited. However, that doesn't mean that its not possible to enhance it in certain ways. The only place you will find the API for it is to load Visual Studio and look for Bots.ArchaeologyBuddy in Visutal Studio's Intellisense documentation.
Bot die all the time in one place, kill mobs with 1 strike.
Translate Google translate.
While the screenshot is nice, if you expect us to address a problem, we'll need the full log.
I'm having issues with the bot turning mantid (haven't done other pandaren ones) artifacts into restored artifacts. As far as i can tell the bot does try to create restored artifacts but this process is interupted almost every time because the bot moves to the next spot immediately.
Possible solution: wait for the restored artifact to be created before moving to next spot / dig site.
Hi, Superduke, and thanks for the log.
ArchaeologyBuddy should most definitely be waiting for the Restored Artifact spell to complete before moving on. It looks like the problem may be Singular trying to perform actions that are interrupting the restoration. We've opened HB-2215("ArchaeologyBuddy: Interrupted while trying to create Restored Artifacts") against this issue.
[size=-2]Ref: Superduke's problem report w/log[/size]
Something i'd like to add. Not sure if this is relevant but that's up to you to decide.
I have kept an eye on it for a while and noticed that the problem only happens when solving and crating when the dig site is not completely finished. Character moves to next digging spot before finishing the crating process.
When solving/crating after the dig site has been completed there is no problem.
I also noticed that the bot did crate all artifacts in backpack (about 35 i think) on a certain moment.
Separate names with a comma.