What's new
  • 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!

Honorbuddy v2.6.15573.831

Status
Not open for further replies.
No Bossland GmbH product emits a message like this. The first place to look would be any third-party offerings you are running. A log attached may provide some insight.
Ref: [post=378165][Guide] How to attach your log[/post]


I will run HB again and post my log as soon as i get the same error. I would like to clarify that it was not a GmbH product that produced this message. It was in game and a prompt that appeared to be produced by the actual WoW client. Or do you mean that it is impossible for any GmbH product to produce this prompt via the WoW client? Thanks for the speedy reply and assistance!
 
Also on a seperate note, alot of the paid / free profiles for farming that run in "Questing" mode are not pathing properly, but if they include a grind profile as well its working perfectly. If this matters to the devs or anyone else who wants to test it.
 
Tried running studio 60's cata runs, toon flew to the instance ok but once inside all I got was "MoveTo failed to move to the location: <878.2985, 225.1927, 503.0983>"

Log attached
View attachment 204819
Hi, Wingsta, and thanks for the log.

Places to look...

The profile your running may require the ability to fly, and you've no mounts specified:
[02:39:17.555 D] UseRandomMount: False
[02:39:17.555 D] MountName has no value yet
[02:39:17.555 D] FlyingMountName has no value yet

You've also got ElvUI running, and this is known to interfere with certain Honorbuddy operations. (TukUI is similar and does not interfere.)

cheers,
chinajade
 
The prompt is from Blizzard/WOW

I ran the exact same profile: Omation Firelands Profile (25m Heroic- normal mode). There are two issues I would like to address in the hopes of shedding light on this issue and helping/hoping to get it resolved ASAP.

ISSUE 1: When entering the the firelands i was promted with a message stating, "You are running a third party script. Doing so compromises the account and the gold made on it." with a yes or no option....i ignored it and entered the instance...it would not load until I hit stop on HB. I am concerned about this for obvious reasons and would like to know the communities thoughts as well as devs thoughts on the matter.

ISSUE 2: Once inside Firelands the bot seemed to start as normal but after its second pull section, it stopped and sat there for 10+ mins before i reset it. I tried multiple times but it will not continue its normal pathway through instance nor attack if being attacked.

I have logs that i have attempted to attach (this is my second attempt to post) but I just signed up (i have auth'ed through email already) and might not have admin approval or something. I will add logs as soon as I am available to do so but I at least wanted to point out the issues I am currently running into.
 
Last edited:
About the 'custom script' popup some are encountering...

getting a message about running custom scripts as a popup in wow, has this happened before on previous releases? i've never seen it before, this is with questbot and kicks
Hello Everyone,

Just recently ran the new patch. I ran Omation's Firelands (25-Man Hardcore / Vendor Lockboxes). I left for about 20 minutes to the store and when i came back I received a prompt in game stating "You are running a third party script. Doing so compromises the account and the gold made on it."

I have never seen this prompt before while running HB. I also read that a few others have this issue. Is it safe to run HB right now? Or would you recommend laying low for now?

Any help on this would be greatly appreciated! Thanks!
Uhm...guys?
This isn't good is it?
Am going to stop testing for now i think ^^

This message just popped up in game...
View attachment 204818
This was the same message I was talking about as well.
I ran the exact same profile: Omation Firelands Profile (25m Heroic- normal mode). There are two issues I would like to address in the hopes of shedding light on this issue and helping/hoping to get it resolved ASAP.

ISSUE 1: When entering the the firelands i was promted with a message stating, "You are running a third party script. Doing so compromises the account and the gold made on it." with a yes or no option....i ignored it and entered the instance...it would not load until I hit stop on HB. I am concerned about this for obvious reasons and would like to know the communities thoughts as well as devs thoughts on the matter.

ISSUE 2: Once inside Firelands the bot seemed to start as normal but after its second pull section, it stopped and sat there for 10+ mins before i reset it. I tried multiple times but it will not continue its normal pathway through instance nor attack if being attacked.

I have logs that i have attempted to attach (this is my second attempt to post) but I just signed up (i have auth'ed through email already) and might not have admin approval or something. I will add logs as soon as I am available to do so but I at least wanted to point out the issues I am currently running into.

Hi, all,

This...
attachment.php
...is a new safety measure in the WoWclient to prevent some nasty attack vectors from other users. More info here:

[post=2228409][Warning] PSA: New WoW Gold/Item scam can cost you dearly...[/post]

Scripts are legitimate things to run, but they can also be used for nefarious purposes as described in the article.

You should probably not click on 'Yes' for this. Instead, you should pursue what is causing the problem and have it corrected by the author. If you click 'Yes', the WoWclient remembers the decison and never asks again. This leaves you open to attacks from other users, if you get careless one day.


It is not Honorbuddy causing this issue, but a third-party product (e.g., plugin, profile, etc.), or WoWclient addon you are running. You will have to figure it out through the process of elimination.

Seems that Charl13P7OP has figured out one of the culprits—Omation. This should be reported to the Omation Support thread. If you find any other culprits, please share, as others are encountering this issue with the new WoWclient.

cheers,
chinajade
 
Last edited:
do NOT try to do BGs guys!!! pretty important stuff since it's so easy to get banned in BGs

Bot stops after the first death in any BG. if you don't intervene (restart bot), you will get deserter / reported for botting / screamed at in chat / votekicked for being AFK, the whole nine yards. sometimes it just stand at entrance of BG afk, don't even need to die.

if you do restart the bot, it will simply stop the next time you die and stand there afk till deserter. it'll then freaking requeue in 15 min and get another deserter.

I really hope people don't lose their accounts over this by turning on BGBuddy and going to bed. sweet internal testing for this sweet account-losing feature, buddyteam.

couple logs from 830 and 831, bloody hell
 

Attachments

I can't even get this build to load. It freezes and closes on load. Anyone else seeing this?
Hi, Zebradude12,

Its a problem peculiar to your machine. Try switching the WoWclient from DX11 mode to DX9 mode, and restart the WoWclient. More info here:

If no joy, make a new thread in the Support forum, and attach a full log of the issue.
Ref: [post=378165][Guide] How to attach your log[/post]

cheers,
chinajade
 
Some Antivirus are interfering with Honorbuddy installs...

FYI the file udis86net.dll is showing up in Norton as a virus "WS.Reputation.1" Yes I added the exception already.
 
Last edited by a moderator:
Hopefully this log is enough - doesn't show much. Disabled all addons, bot just sits there after casting a few spells, if the bot dies just 1 it'll sit in the graveyard and get deserter.
 

Attachments

Hey all,

Just updated to the newest version, and now what happens is that in the BgBuddy profile, my resto druid just sits there, doesn't move, will randomly cast Bark skin, but nothing more than that. Any ideas as to why? If the bot dies itll just afk in the graveyard until it get deserter - no addons enabled.
 

Attachments

Hi, Somegreendayfan101,

The logs in the last two posts are the same, and do not illustrate the problem you are describing. [size=-2](The logs are 5-lines long, and do not even show Honorbuddy initialize completion.)[/size]

Please try to hunt down and attach the appropriate logs. :D

cheers,
chinajade
 
Chinajade, sorry for wasting your time! I honestly assumed that these logs are auto generated in the "log" folder within honorbuddy itself. That was the most recent log that I linked...I will try to find more info within the log.
 
My post got moved with no response? Does this mean that mining is currently broken and being worked on?
Hi, Mudplayerx,

You mean [post=2228566]this post[/post]?

Posts in this thread are managed according to the Thread Management Rules stated in the first post. The thread is constantly being looked at by the development staff. [size=-2](Raphus hasn't slept in close to two days.)[/size] We declutter the thread as much as possible to make their job faster and easier.

cheers,
chinajade
 
Last edited:
Theres problems with questing using singular. It works fine for a bit then it stops doing anything. If bot dies it returns to the corpse and resurrects but still does nothing.

I can't upload the log here for some reason the logs generated gets massive as in 170mb for 30 mins of gameplay. Most of the log seems to be repeating so i copied what might be the issue

[EDITED 25-Jul-2016 by chinajade]: Removed abusive cut-n-paste of log. Please learn to attach logs. If they are large, zip them first.
Ref: [post=378165][Guide] How to attach your log[/post]

Also this seems to happen prior to the problem "[03:48:45.949 N] (Singular) (Singular) info: 94.1 seconds since BotBase last called Singular (now in Rest)"
Hi, Labze,

Raphus just confirmed a problem with incoming heals causes Singular to throw exceptions in some cases. From the log fragment you showed us, this appears to be your case.

There is nothing you can do about this, and may just have to wait for another Test Release.

cheers,
chinajade
 
Hi, Labze,

Raphus just confirmed a problem with incoming heals causes Singular to throw exceptions in some cases. From the log fragment you showed us, this appears to be your case.

There is nothing you can do about this, and may just have to wait for another Test Release.

cheers,
chinajade

Alright, cheers for the response.
 
Status
Not open for further replies.
Back
Top