eSafe - Making botting safer - v1.3

[thedrunk]

Since Erenion is not available atm I've decided to post a version that works with HB2. I do not plan on adding new features.

Thank you!!!

 

[highvoltz]

updated with some bug fixes. http://www.buddyforum.de/showthread...tting-safer-v1.3&p=71696&viewfull=1#post71696

 

[nudeltopf]

hmm i've searching probably the same, but the plugin should be screaming if another player comes by. no need the logout feature. i'm only babysitter-botting
i tried to extract that code but failed can anyone help me?

 

[Techz]

Not sure if its just me but i loved this plugin and for some reason with the latest HB it crashes alot saying its stuck when its not :-( here is the bottom part of the log

[19:11:49:506] Exiting wow! Stuck for too long!
[19:11:57:566] ReadByte at 0xBD0792 failed. - From: Honorbuddy at Magic.SMemory.ReadByte(IntPtr hProcess, UInt32 dwAddress)
at Magic.BlackMagic.ReadByte(UInt32 dwAddress)
at Magic.BlackMagic.(UInt32 address, Type t)
at Magic.BlackMagic.Read[T](UInt32[] offsets)
at Styx.WoWInternals.ObjectManager.get_IsInGame()
at ..(Object sleepTime)SmartExceptionsCore.UnhandledException @ 3846, offset:68
[19:11:57:589] Wow exited, Honorbuddy stopped!
[19:11:59:522] Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. - From: Honorbuddy at EndScene.ExecutorRand.GrabFrame()
at Styx.Logic.BehaviorTree.TreeRoot.Stop()SmartExceptionsCore.UnhandledException @ 3431, offset:73

The thing is its not stuck at all :-(

 

[mmjauaww]

Not sure if its just me but i loved this plugin and for some reason with the latest HB it crashes alot saying its stuck when its not :-( here is the bottom part of the log

[19:11:49:506] Exiting wow! Stuck for too long!
[19:11:57:566] ReadByte at 0xBD0792 failed. - From: Honorbuddy at Magic.SMemory.ReadByte(IntPtr hProcess, UInt32 dwAddress)
at Magic.BlackMagic.ReadByte(UInt32 dwAddress)
at Magic.BlackMagic.(UInt32 address, Type t)
at Magic.BlackMagic.Read[T](UInt32[] offsets)
at Styx.WoWInternals.ObjectManager.get_IsInGame()
at ..(Object sleepTime)SmartExceptionsCore.UnhandledException @ 3846, offset:68
[19:11:57:589] Wow exited, Honorbuddy stopped!
[19:11:59:522] Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired. - From: Honorbuddy at EndScene.ExecutorRand.GrabFrame()
at Styx.Logic.BehaviorTree.TreeRoot.Stop()SmartExceptionsCore.UnhandledException @ 3431, offset:73

The thing is its not stuck at all :-(

Same here..

 

[Robertoisrad]

Me three, My problem is at the BG gate before the round starts

 

[wilsonj17]

Me three, My problem is at the BG gate before the round starts

You do relise that this plugin wont work since the last update was nearly 3 month's ago? please check the date's of when the plugin was released and everytime HB get's a update then the plugin's will most likely need a update.

 

[tombstone]

New version of eSafe (now with hearth!!)

eSafe is one of my favorite plugins, and in my humble opinion, it is a must-have for anyone who uses Honorbuddy!

I have waited a long time for the hearth ability to be added to the plugin, but nobody ever added it, so I went and did it myself! I'm not even a C# programmer! Psh...

At any rate, here it is. This version is supported by HB2 and also includes the improvements made by Highvoltz.

P.S. Make sure that you set your hearth to an inn in your zone or else your bot will get confused. At the moment, Dalaran doesn't appear to be properly meshed, so if your hearth is set to Dal, your bot will do bad things!

Edit: Attachment removed. Please use version 1.5 in my following post.

 

[tombstone]

eSafe 1.5

I did some more testing with the Hearthstone functionality and I decided to implement a new feature:

The plugin now has an additional configuration variable, "useHearthAlways", which tells it to use the hearthstone *all the time*, no matter what. If this particular configuration option is enabled and the bot gets stuck, it will literally just stand there and wait until the hearthstone is off of cooldown. This way, your WoW program never actually gets shut down (unless you get automatically logged out due to inactivity).

If the "useHearth" is set to true, but "useHearthAlways" variable is set to false, the bot will attempt to use the hearthstone when stuck, but will go ahead and exit WoW if the hearthstone is on cooldown.

Note: If you do not currently have a hearthstone in your bags, this plugin will shut down WoW, regardless of the configuration parameters used.

 

[Zugga]

Im wondering does this work with the current version?
All my chars would be much higher if I trusted the bot to run when im afk, but unfortunately I come back all too often to them doing something retarted that if anyone witnessed i know id be banned.

 

[tombstone]

Im wondering does this work with the current version?
All my chars would be much higher if I trusted the bot to run when im afk, but unfortunately I come back all too often to them doing something retarted that if anyone witnessed i know id be banned.

Yes. I am currently running eSafe 1.5 with HB 1.9.5.8. I have only tested it with grinding and questing, though. I never do BGs because quite frankly, I think that PvP is a horrible idea for botting and you're just asking to be banned by interacting with groups of other players.

 

[TheFury]

I think that PVP is where HB truly shines, greatest thing ever haven't gotten banned and hoping that i don't.

 

[tombstone]

I think that PVP is where HB truly shines, greatest thing ever haven't gotten banned and hoping that i don't.

Yeah, I mean, don't get me wrong... The bot was clearly initially designed for PvP (hence the name "honor" buddy)... but just stop and think about it for a minute.

From what I've been told (because HB is supposedly undetectable by WoW), the #1 reason why botters get banned is reports by other players.

This is why so many "safe botting" guides say that you shouldn't bot in heavily populated areas or on servers with a lot of people. The more people that see your bot moving in its jerky click-to-move manner and doing things like not responding to whispers, the higher your odds of being banned.

Oh, so here's a good idea: Let's join a battleground and literally run around with 40 people (half of which are the opposite faction and are highly motivated to report suspicious enemy bots).

Yeah. No thanks.

 

[Nayhaw]

Oh, so here's a good idea: Let's join a battleground and literally run around with 40 people (half of which are the opposite faction and are highly motivated to report suspicious enemy bots).

Yeah. No thanks.

Wait you're saying half the people in Battlegrounds #1 goal is to "find botters" and not win the battleground? Hmmm

Also, everyone in the battleground is fine with w/e your doing unless your sitting in your starting spawn point (cave). Just sayin' my 2c

 

[tombstone]

Wait you're saying half the people in Battlegrounds #1 goal is to "find botters" and not win the battleground? Hmmm

Also, everyone in the battleground is fine with w/e your doing unless your sitting in your starting spawn point (cave). Just sayin' my 2c

I'm not saying that you will 100% without a doubt get banned by running battlegrounds. I'm just saying that if you follow the logical chain of thought, you can see how risky it might be. And the "half of the people" I was referring to was all the people on the opposite team.