So I thought this was suppose to be fixed many builds ago when the options in settigs popped up. I have it activated to make diablo 3 believe its always the selected window, but its actually doing the OPPOSITE. Its deselecting it. I know I'm suppose to be able to constantly hear the game sound but I can't unless i click the window, in which cause it immediatley deselects it again.
Still being logged as "afk" with up to date beta
- Thread starter vwest877
- Start date
- Status
ffantasy87
New Member
- Joined
- Sep 25, 2012
- Messages
- 38
- Reaction score
- 0
I am also encountering this issue. Since I am only using 1 bot, I de-select the option "Make game thinks it's in foreground" and leave my diablo windows on foreground.
The problem I'm having with this is that I like to do other things while botting on the same PC - I.E. Play League of Legends.
This makes me have to pull out my laptop, so I have to keep two copies of DB, plugins and profiles updated. Its annoying.
Anonuzer01
Active Member
- Joined
- Sep 9, 2010
- Messages
- 947
- Reaction score
- 26
Are you guys running Beta 39? I just did a complete new install of Beta 39, latest trinity and latest rads atom and I'm not seeing this issue.
I'm running the most up to date beta of DB, Giles and Rads Atom. The "fix" has never worked for me on any build.
ffantasy87
New Member
- Joined
- Sep 25, 2012
- Messages
- 38
- Reaction score
- 0
You can put DB and profiles in Dropbox.
Well, I am still using the stable build 277 at the moment. Not dare to update to beta 39 yet
You can put DB and profiles in Dropbox.
Well, I am still using the stable build 277 at the moment. Not dare to update to beta 39 yet
I've been using teamviewer to transfer the files, its jut annoying.
stormwarr1
New Member
- Joined
- Oct 30, 2011
- Messages
- 846
- Reaction score
- 3
I haven't been flagged as AFK since the DB that fixed it. Make sure your box is ticked and try a clean install.
I have been having the same problem with the afk messages. I always do a fresh install of DB for any update including changes to trinity. I have tried multiple stable and beta builds with all the correct settings and I still received the afk messages. Today I think i finally got it to work, actually it is working just afraid to stop it in fear it will start giving me afk messages again. I will share exactly what i did for mine to start working and maybe it will help someone else.
Step 1: I did a clean install of the Beta 39 using plugins radatom 1.5.1 and trinity 1.6.3.3.
Step 2: Restarted my PC
Step 3: I loaded up Diablo 3. It loads up in window mode. I then went to options i changed it to full screen. I then changed it to full screen(window mode). Then changed back to windowed mode.
Step 4: I waited till D3 went afk, after getting the afk message I loaded up DB Beta.39 selected the profile and then clicked start.
Right after clicking start I received the you are no longer afk message. And it has not came back for the two hours its been running. Like I stated earlier I am not sure if something I did helped it start working or I am just lucky. I guess I will find out after it crashes. Anyways I hope this helps someone.
PS: Before this I tried clean installs of Beta's 27,29,33,39 and Build 277,278,279 and received afk messages with all. I dont think its DB's fault just something to do with our PC's or D3.
Step 1: I did a clean install of the Beta 39 using plugins radatom 1.5.1 and trinity 1.6.3.3.
Step 2: Restarted my PC
Step 3: I loaded up Diablo 3. It loads up in window mode. I then went to options i changed it to full screen. I then changed it to full screen(window mode). Then changed back to windowed mode.
Step 4: I waited till D3 went afk, after getting the afk message I loaded up DB Beta.39 selected the profile and then clicked start.
Right after clicking start I received the you are no longer afk message. And it has not came back for the two hours its been running. Like I stated earlier I am not sure if something I did helped it start working or I am just lucky. I guess I will find out after it crashes. Anyways I hope this helps someone.
PS: Before this I tried clean installs of Beta's 27,29,33,39 and Build 277,278,279 and received afk messages with all. I dont think its DB's fault just something to do with our PC's or D3.
Last edited:
- Status