What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Inactivity timer tripped! Leaving game

Status
Not open for further replies.
solitudethedude

solitudethedude

New Member
Joined
Jan 11, 2012
Messages
118
Reaction score
0
After this occurs, it just sits in the main menu forever. How can I get it to start a new game after this happens?
 
Ugh I'm sick of posting the same answer to this question every other day.

Disable db inactivity timer by placing a zero in there n activate the atoms timer
 
Champagne said:
Ugh I'm sick of posting the same answer to this question every other day.

Disable db inactivity timer by placing a zero in there n activate the atoms timer
Click to expand...


Exactly what he said. The DB one does not work correctly, if you use Rad's instead, all works fine.
 
I have the exact same problem. Rad's is not the solution, as it crashes my wow every half an hour.
Could we get a look into fixing this inactivity timer "stuck in menu" problem by the devs? That's really the last real problem preventing us from botting successfully.
 
pretty sure thats the fix...

and maybe ur wow keeps crashing cuz ur pc cnt handle it?
 
well ur the only one thats not working for so i doubt the devs will look into it
 
griovejas said:
I have the exact same problem. Rad's is not the solution, as it crashes my wow every half an hour.
Could we get a look into fixing this inactivity timer "stuck in menu" problem by the devs? That's really the last real problem preventing us from botting successfully.
Click to expand...


Maybe try a different version of Rads or a clean install would be my suggestion. This fix has been working for everyone else without issue... my pair of bots havent had a single hitch less stopping to update/sell.
 
Maxasy said:
Maybe try a different version of Rads or a clean install would be my suggestion. This fix has been working for everyone else without issue... my pair of bots havent had a single hitch less stopping to update/sell.
Click to expand...

More people have problems with Rads, so it's not a solution for everyone.
Even then, it's a workaround. For a core problem such as these random stucks in menu, that prevent you from botting in some cases, we could use a Nesox solution.

P.S. Champagne, please keep your opinions to yourself, and keep this thread constructive (i.e. stop replying).
 
Last edited:
Not a opinion but a fact

There is only one stuck in menus due to the inactivity timer n that's the solution, I've talked with rad n me n him actually found the solution together.
 
Champagne is correct that the only current workaround is to use RadsAtom inactivity timer.
It's better designed than the current DB timer anyway, as it loads next profile instead of booting you to menu.

However, since you asked, I already suggested that Nesox rework the inactivity timer as you can see here:
http://www.thebuddyforum.com/demonb...nging-wednesday-build-282-a-8.html#post809563
So, it seems he is planning to work on the inactivity timer.

Also, may I suggest you try these versions of RadsAtom to see if it helps with your crashing problems?
Here's two frequently requested versions

1.3.6
https://www.dropbox.com/s/gl406v59ftgea1u/RadsAtom.zip

1.4
https://www.dropbox.com/s/nsb44axfiytfiw9/RadsAtom.zip

I've been using 1.3.6 since it's release with no crashes.
 
and for those of us who DO NOT use Rads Atom, this is still an issue, so it IS DB related not RADS ATOM related, would a dev or two mind taking a look at this, there are no logs, it just ends the runs and sits there until, stop/start is pressed.
 
devious21 said:
Champagne is correct that the only current workaround is to use RadsAtom inactivity timer.
It's better designed than the current DB timer anyway, as it loads next profile instead of booting you to menu.

However, since you asked, I already suggested that Nesox rework the inactivity timer as you can see here:
http://www.thebuddyforum.com/demonb...nging-wednesday-build-282-a-8.html#post809563
So, it seems he is planning to work on the inactivity timer.

Also, may I suggest you try these versions of RadsAtom to see if it helps with your crashing problems?
Here's two frequently requested versions

1.3.6
https://www.dropbox.com/s/gl406v59ftgea1u/RadsAtom.zip

1.4
https://www.dropbox.com/s/nsb44axfiytfiw9/RadsAtom.zip

I've been using 1.3.6 since it's release with no crashes.
Click to expand...
1.4 fixed the problem for me, ty
 
Moley said:
and for those of us who DO NOT use Rads Atom, this is still an issue, so it IS DB related not RADS ATOM related, would a dev or two mind taking a look at this, there are no logs, it just ends the runs and sits there until, stop/start is pressed.
Click to expand...

Congrats we should award yu with some kind of prize for repeating what we said.

Yu disable db inactivity timer and use atoms timer
 
Champagne said:
Congrats we should award yu with some kind of prize for repeating what we said.

Yu disable db inactivity timer and use atoms timer
Click to expand...

So you are saying RADSATOM is NOW REQUIRED for DB inactivity timer to work at all? This seems counter intuitive to what NESOX has posted in the main Beta thread.
 
Moley said:
So you are saying RADSATOM is NOW REQUIRED for DB inactivity timer to work at all? This seems counter intuitive to what NESOX has posted in the main Beta thread.
Click to expand...

dnt listen to them. ive seen posts and channel logs saying "random dungeons should work now" in like 10 db versions and its never true cuz theres always something wrong. basically if they say something works it only might work, 50/50? perhaps

maybe if yu use db without atom inactivity timer might work but if ur using atom the db timer does not work. never used it without the atom so cant confirm that.
 
Status
Not open for further replies.
Back
Top