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!

[StandAlone] Yet Another Relogger!

Status
Not open for further replies.
From what i have read, d3starter is the problem right? If they actually ban all that used yar and/or d3starter probably u will have like 80% of users banned.... So nice... and when i just remember when people where reporting this as a possibility , they where called idiots, why wasn't this spotted as soon as the update was made?
 
From what i have read, d3starter is the problem right? If they actually ban all that used yar and/or d3starter probably u will have like 80% of users banned.... So nice... and when i just remember when people where reporting this as a possibility , they where called idiots, why wasn't this spotted as soon as the update was made?


They weren't called idiots (usually), most people were just saying that they didn't use either of these and were also banned.

That being said, I was actually someone saying that I didn't use them and I was banned.

Difficult to tell what's going on...

**EDIT**

However, it's nice to see the BuddyTeam let us know when they were informed of the issue and to immediately remove these plugins from the site.
 
Probably i have overreacted but still, like 10 days passed from the time this was added. I hope the casualties will be minimum and none will get the ban.
 
A well do I. 10 days of use is a lot of time if used wisely by there team. If your worried about losing your account. Don't bot for a week or so? Two to be sure. lol
 
ROFL How desperate do you have to be to get after 3rd party software, more evidence that demonbuddy is well protected (otherwise they would have just gone for demonbuddy).
 
ROFL How desperate do you have to be to get after 3rd party software, more evidence that demonbuddy is well protected (otherwise they would have just gone for demonbuddy).

Excellent point lol...I hadn't even thought of that.
 
Whatever gets bans for botters...anything is possible. They got the cash to have a team of anti botters I bet. This is all speculation though. Since demonbuddy is so well protected...why not slip in a sneak shot at all DB users who used that 3rd party software? Wouldn't that greatly weave out a lot of botters/sellers?
 
Is this new detection only a problem if d3starter is being used? Is this new detection a problem if YAR is used without d3starter (i.e. each bot has an exclusive copy of D3)?
 
you can combine YAR or rrrix's YAR with IsBoxer. Though it's a little complicated to setup and costs a bit of money. It creates additional cachefiles for every isntance. So if you want to run 10 bots on a SSD you don't need to have that much space...
 
you can combine YAR or rrrix's YAR with IsBoxer. Though it's a little complicated to setup and costs a bit of money. It creates additional cachefiles for every isntance. So if you want to run 10 bots on a SSD you don't need to have that much space...

just wanted to shamelessly advertise my guide below
 
It works great but then i get this error message.
[9/16/2013 4:23:08 AM] <M2B3> Sending MonsterPowerLevel: Level6
[9/16/2013 4:25:50 AM] <M2B3> Demonbuddy:4804: has not gained any gold in 200 seconds, trying reset
[9/16/2013 4:26:37 AM] <M2B3> Demonbuddy:4804: has not gained any gold in 246 seconds, trying reset
[9/16/2013 4:27:23 AM] <M2B3> Demonbuddy:4804: has not gained any gold in 293 seconds, trying reset
[9/16/2013 4:28:10 AM] <M2B3> Restarting...
[9/16/2013 4:28:10 AM] <M2B3> Diablo:6096: Kill process
[9/16/2013 4:28:10 AM] <M2B3> Demonbuddy:4804: Failed to close! kill process
[9/16/2013 4:28:10 AM] System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.TextWriter.WriteLine(String value)
at YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)
[9/16/2013 4:28:11 AM] <M2B3> Diablo:6096: Process is not running
[9/16/2013 4:28:11 AM] <M2B3> Killing Agent.exe:4516
[9/16/2013 4:28:11 AM] <M2B3> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
it's been fine past two weeks or so, and past an hour this started happening. NEED HELP!
any solutions?
 
Status
Not open for further replies.
Back
Top