SRL Archive - S.M.A.R.T.

The fix with the .bat file works fine, but as described in the thread, is very hacky.

What I'm suggesting is that once the account reaches ~4 hours in the Progress Report, it simply logs out, and logs back in. This eliminates having to restart Simba or SMART, and would take less time also.

Thoughts?

Pretty sure that doesn't work. A lot of users take breaks and that 6 hour thing still happens. Just having the client open for 6 hours logged in or out causes it to happen unfortunately.

From: YoHoJo
Pretty sure that doesn't work. A lot of users take breaks and that 6 hour thing still happens. Just having the client open for 6 hours logged in or out causes it to happen unfortunately.

As long as you completely log out it works. Going into the lobby it doesn't, but completely logging out works. I'm almost sure of it. :)

From: shstiger2009
As long as you completely log out it works. Going into the lobby it doesn't, but completely logging out works. I'm almost sure of it. :)

Absolutely does not work.. I just lost a 5hr 10 min 37 second proggy cuz of it..

I have my script log out completely every 2 hrs.. Still gets the updated thing..

From: ggzz
Absolutely does not work.. I just lost a 5hr 10 min 37 second proggy cuz of it..

I have my script log out completely every 2 hrs.. Still gets the updated thing..

That's surprising. They must have changed something recently, because I know when I ran scripts from RSBuddy, I had much longer and saw much longer Progress Reports than just 6 hours. From what I saw, it was because they completely logged out and logged back in. The client was never closed.

Could you post the code so I could give it a try?

After the reflection update they changed it to the ~6 hour thing…

Yeah, sadly it applies even when in lobby/logged out completely.

I don't mind the 6hour thing, really.. I just babysit during the day and then refresh everything just before bed - then set PC to shut down in 6 hours.. doesn't lose much botting time :)

The obfusticated typeless array is scrambled up about every six hours. Anyone with the "old" client loaded is forced to reload. So you can't just log out, the java process has to be killed and reloaded.

I see. Sorry about that, wasn't aware.

i doubt it works like that… would be cool to bot 6h+ thought