What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Urgent Issue with Botting

Status
Not open for further replies.

lazygun247

New Member
Joined
Aug 12, 2012
Messages
132
Reaction score
0
I am testing it out now and even though DB is running and moving and everything, it registers as you are afk.

Is there anyway to prevent this?

Basically i was testing some stuff and I notice that one of the accounts that was running DB shows up an "You are now AFK" msg even though bot is fully working.

I am a bit worried about this. Did this happen to anyone else?
 
Yup, this is worrying indeed, not botting till we can get this resolved personally :/
 
Seems to pop up when you don't have the D3 window active
 
I assume you guys are using the new .275 build ?
This is troubling matter indeed, but i think its nothing that the devs cant fix :D
 
Will take a look tomorrow, it's late here now.
You could try and start it with isboxer then make sure the option "Make the game think it's in the foreground" is enabled can't remember what it's called.
 
You are saying the D3 window must stay in the foreground or this message will pop up?
 
can u change the status to "busy"? after i change it to that, i do not have the afk message...
 
A simple yet effective way of detection. I guess you will only be able to run one copy of D3 per machine now (and you won't be able to do anything else with it at the same time) unless you use VM. :(
 
can u change the status to "busy"? after i change it to that, i do not have the afk message...


just b/c u don't get afk msg doesn't mean they can't detect it. It may just not send u the afk msg b/c u r busy...
 
when i set to busy, this does not happen been running it in the background for about 25 minutes.
 
A simple yet effective way of detection. I guess you will only be able to run one copy of D3 per machine now (and you won't be able to do anything else with it at the same time) unless you use VM. :(

This
 
when i set to busy, this does not happen been running it in the background for about 25 minutes.


doesn't mean they dont detect it.... busy is usually sign that u dont want to be disturbed, meaning they won't spam you with that stuff
 
A simple yet effective way of detection. I guess you will only be able to run one copy of D3 per machine now (and you won't be able to do anything else with it at the same time) unless you use VM. :(

If we were living in the stone age that is. I am sure this will be fixed by the end of tomorrow :D
 
just b/c u don't get afk msg doesn't mean they can't detect it. It may just not send u the afk msg b/c u r busy...


You dont think they could check this before? Just because we get a msg now that we are "afk" doesnt mean that they couldnt look up this all the time. You guys must have a collection of tinfoil hats...
 
If we were living in the stone age that is. I am sure this will be fixed by the end of tomorrow :D

I am sure they will come up with a workaround, I was speaking in more of a for the time being sort of way. This is more of an OS issue anyway, may be some kind of way to trick windows into thinking it has more than one window in the foreground?
 
You dont think they could check this before? Just because we get a msg now that we are "afk" doesnt mean that they couldnt look up this all the time. You guys must have a collection of tinfoil hats...

They probably never logged it before. At least not as extensively as now. Before they had AFK detecting system, but it was base don movements not whether d3 was in foreground or not... but yes, they could've detected it before. But also they may not have done it before and are doing it now
 
You dont think they could check this before? Just because we get a msg now that we are "afk" doesnt mean that they couldnt look up this all the time. You guys must have a collection of tinfoil hats...

If this was true, there probably would have been a whole shitload more bans. Maybe some packet sniffing is in order to see exactly what is being sent to blizz servers on this one...
 
I think it should be fixable going by what I've seen apparently its a similar approach applied to in WOW and if im not mistaken Honorbuddy works around it for WoW so it should be similar for db id assume - just needs time for the fix to be put in place.
 
Status
Not open for further replies.
Back
Top