SRL Archive - RuneScape News and General

Rs updates randomly?


kingarabian

2011-10-29 03:56:03

So my bot was running on my VM. Suddenly I get kicked out and it says that "Rs has been updated, please refresh the page". Ironically I was on the same world with my main, and I did not get kicked out nor did I see anything about an upcoming update.

Weird indeed… has this happened to anyone?

litoris

2011-10-29 04:12:34

Seems like a bot-catching measure. A normal person would be able to refresh and move on.

Tickyy

2011-10-29 04:57:21

Nah, probably they just missed anything, and left small bugs in-game, so they don't have to make it public for example if they fixed a few graphical pixels.

kingarabian

2011-10-29 04:58:39

From: Tickyy
Nah, probably they just missed anything, and left small bugs in-game, so they don't have to make it public for example if they fixed a few graphical pixels.


Well I found it weird one account got kicked and my other one didn't as well as the others in my world. We were both on the same world when it happened.

WT-Fakawi

2011-10-29 05:43:45

I have the same feeling. It looks like it updates itself every 8 hours or so. At least after 8 hours my script stops for an update.

noidea

2011-10-29 09:35:01

From: WT-Fakawi
I have the same feeling. It looks like it updates itself every 8 hours or so. At least after 8 hours my script stops for an update.


Same man.
Its probably possible to terminate the current instance of SMART and start a new one though if we detect that theres been an update. Probably should be too hard to get around.

Kave

2011-10-29 10:47:44

I've also noticed this you just randomly disconnect.

Brandon

2011-10-29 10:58:54

It only happens to me when my ip changes.. dunno why :S But its annoying as hell man.. same with the glory glitch.. Glory's been in my house for over a year now.. and its now invisible so u can't use it..

Big Tom

2011-10-29 11:02:31

From: ggzz
It only happens to me when my ip changes.. dunno why :S But its annoying as hell man.. same with the glory glitch.. Glory's been in my house for over a year now.. and its now invisible so u can't use it..


You can still use your glory if you can locate it I had the same problem but if you remember where you put it it still works, atleast for me it does.

blabla7

2011-10-29 11:27:02

From: ggzz
It only happens to me when my ip changes.. dunno why :S But its annoying as hell man.. same with the glory glitch.. Glory's been in my house for over a year now.. and its now invisible so u can't use it..


Ive heard that ip change error a lot. Personally I have a static IP and I am not noticing any problems at all.

[XoL]

2011-10-29 13:49:21

This happened to me last night, I checked the forums for any one else with a similar problem but seems I am unique at least on the RSOF.

WT-Fakawi

2011-10-29 15:07:29

So, can we assume that the runescape client needs reloading every 6-8 hours? The client simply kicks you after a couple of hours; when you re-login it pops up with "runescape has been updated".

nielsie95

2011-10-29 15:09:17

Perhaps they're reobfuscating the client, changing all the hooks?

grats

2011-10-29 15:49:50

yep I've had that happen twice

no countdown or anything

I logged in immediately after, it definitely seems like a bot catching trick

Wizzup?

2011-10-29 16:07:00

So we can assume it doesn't happen to fighting scripts?

kingarabian

2011-10-29 16:41:50

From: Wizzup?
So we can assume it doesn't happen to fighting scripts?


It happened to all 5 of my accounts running Tara's chicken killer.

Mr. Bottomtooth

2011-10-29 19:46:55

From: kingarabian
It happened to all 5 of my accounts running Tara's chicken killer.


How can they just make people DC while in combat, that would completely screw up PKing and PvM. I mean sure they CAN but that'll make a lot of people mad.

WT-Fakawi

2011-10-29 20:19:53

Well, it happened again after 5 hours and 7 minutes using HLR:

Status: /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
Status: | SRL Randoms Report |
Status: | www.villavu.com |
Status: |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Status: | SRL Logs : 2 |
Status: \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~/
**********************************************

<============== 0.84 Progress Report ===============>
Worked for 5 Hours, 7 Minutes and 59 Seconds
Coins = 0
Total Goblins = 999
Goblins Combat = 999
Goblins Ranged = 0
Goblins Maged = 0
Total Rats = 199
Rats Combat = 199
Rats Ranged = 0
Rats Maged = 0
Bones Buried = 0
Meat Collected = 50
Water Collected = 168
Earth Collected = 0
Arrow Collected = 3
Rests = 0
Beers Drank = 0
Food Eaten = 51
Food Burned = 0
Fish Caught = 0
Shrimp Caught = 0
Anchovie Caught = 0
Sardine Caught = 0
Herring Caught = 0
Shrimp Eaten = 0
Anchovie Eaten = 0
Sardine Eaten = 0
Herring Eaten = 0
Trees Chopped = 9
Logs Burned = 0
Willows Chopped = 220
Willows Burned = 220
Times Cooked = 10

'Runescape has been updated.'
Successfully executed.


There is definately something going on here.

Harry

2011-10-29 20:21:38

It shouldn't be hard to modify SMART to reload itself. Only then you risk the chance of it downloading an update that could make SRL behave incorrectly.

kingarabian

2011-10-29 20:41:20

From: WT-Fakawi
Well, it happened again after 5 hours and 7 minutes using HLR:

There is definately something going on here.


It just happened to me as well just as my bots hit the 6 hours mark.

All 4 of them logged out, but my other bot that has been running for 3 hours is still going. We need a Java guru to look in this.

Come on in Method/Pyro/MITB/Benland

WT-Fakawi

2011-10-29 20:54:58

So: Nielsie is right! The hooks change 4 times a day!

Flight

2011-10-29 22:08:59

You still have to load up Runescape in a regular browser after an update, correct? I'd imagine refreshing a page is no problem when running Simba directly in the browser. Then how would this affect Smart?

Harry

2011-10-29 22:16:18

From: Flight
You still have to load up Runescape in a regular browser after an update, correct?

No. After the update you can even delete all jagexcache related stuff and SMART loads fine and updates itself.

grats

2011-10-30 00:28:16

From: WT-Fakawi
So: Nielsie is right! The hooks change 4 times a day!


Well they clearly don't like reflection.. they don't want it working even if someone figures how to get around their new code

KingKong

2011-10-30 02:23:14

From: kingarabian
It just happened to me as well just as my bots hit the 6 hours mark.

All 4 of them logged out, but my other bot that has been running for 3 hours is still going. We need a Java guru to look in this.

Come on in Method/Pyro/MITB/Benland


i think thats because jagex automatically kicks players if they're online for 6 hrs straight.

HyperSecret

2011-10-30 02:46:26

From: KingKong
i think thats because jagex automatically kicks players if they're online for 6 hrs straight.


Even though, before tuesday it never resulted in the client needing to be reloaded, it simply just wanted you to log back in.

Iron Man

2011-10-30 02:55:11

From: HyperSecret
Even though, before tuesday it never resulted in the client needing to be reloaded, it simply just wanted you to log back in.


And it happened to Fakawi@5 hrs.

kingarabian

2011-10-30 03:38:47

From: KingKong
i think thats because jagex automatically kicks players if they're online for 6 hrs straight.


And if they wanted to kick me out they would allow me to log back in. Instead it says "Runescape has updated please refresh the page". I can't log back in until it's refreshed.

litoris

2011-10-30 03:50:51

Maybe they are putting code into the jar files of people they suspect of botting?

kingarabian

2011-10-30 16:02:59


Worked for 5 Hours, 49 Minutes and 23 Seconds
Changing Players
NextPlayer(True)
SwitchToPlayer(PlayerNo: 1, Active: True);
Welcome to Runescape.
********
'Runescape has been updated.'
Successfully executed.


Worked for 5 Hours, 58 Minutes and 43 Seconds
Changing Players
NextPlayer(True)
SwitchToPlayer(PlayerNo: 0, Active: True);
Welcome to Runescape.
***** am
'Runescape has been updated.'
Successfully executed.


Worked for 5 Hours, 52 Minutes and 52 Seconds
Changing Players
NextPlayer(True)
SwitchToPlayer(PlayerNo: 0, Active: True);
Welcome to Runescape.
*********
'Runescape has been updated.'
Successfully executed.

Heavenzeyez1

2011-10-31 13:17:19

It's getting VERY annoying, is there anything we can do about it? :(

~Eerik.

whatev

2011-10-31 13:22:33

From: Heavenzeyez1
It's getting VERY annoying, is there anything we can do about it? :(

~Eerik.


Is there some way to create a top level function in MSI that will kill SMART+loop back around when it prints 'Runescape has been updated'?

Though, I feel like if this were possible, you'd definitely need some fail safes for when runescape actually has updated.

Main

2011-10-31 13:34:31

if the script is not world dependant (like a wcer). We can just change the world list on smart and restart smart (if we can figure that out) as if you change the world, smart closes its old one and open up an new one.

Coh3n

2011-10-31 19:51:26

I've said this in another thread. I've talked to Ben about it and it can be done. SMART just needs to be altered a little so the "Applet declaration" error doesn't pop up with you try to load RS from a browser.

Harry

2011-10-31 21:47:08

From: Coh3n
I've said this in another thread. I've talked to Ben about it and it can be done. SMART just needs to be altered a little so the "Applet declaration" error doesn't pop up with you try to load RS from a browser.

It no longer does that. Try it yourself. Delete all Jagex related stuff and SMART loads fine.

Coh3n

2011-10-31 22:43:51

From: Harry
It no longer does that. Try it yourself. Delete all Jagex related stuff and SMART loads fine.
Do you have to delete that stuff after it updates though? Cause the point is to continue autoing if it updates, and if you're not at your computer, you can't delete all the files.

Harry

2011-10-31 22:53:22

From: Coh3n
Do you have to delete that stuff after it updates though? Cause the point is to continue autoing if it updates, and if you're not at your computer, you can't delete all the files.

No, you don't have to, that's just an example.

Overtime

2011-10-31 23:19:00

Just got it today.

/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
| --> YoHoJos PMS 1.05 <-- |
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~/
| Worked for 2 Hours, 9 Minutes and 1 Seconds
| Mined 1092 ores at a rate of 511 per hour
| Mined 39 loads at a rate of 18 per hour
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>
# : Nick = A : Level Worked Mined Loads XP Location
0 : ames = T 57 03:37:15 1092 39 38220 L:Cant Find Rock :(
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>
Welcome to Runescape.
'Runescape has been updated.'
Successfully executed.

Coh3n

2011-11-01 01:34:24

From: Harry
No, you don't have to, that's just an example.
If that's the case then all we have to do is call the SMART setup method in SRL so it will restart.

Harry

2011-11-01 04:15:57

From: Coh3n
If that's the case then all we have to do is call the SMART setup method in SRL so it will restart.

IIRC SMART doesn't free its memory when it gets recreated. That'd cause some problems. Other than that, sure, might work.

KingKong

2011-11-01 05:42:03

From: Harry
IIRC SMART doesn't free its memory when it gets recreated. That'd cause some problems. Other than that, sure, might work.


^This. Everytime you restart SMART you increase your mem usage by ~200M? So running multiple clients will cause loads of errors.

Coh3n

2011-11-02 15:41:09

From: KingKong
^This. Everytime you restart SMART you increase your mem usage by ~200M? So running multiple clients will cause loads of errors.
We talked about this on the SMART thread. If we can't find a solution, I'll make an option for restarting SMART. The user can choose whether or not to do so.

E: Harry, I still get this error after RS says it's updated.


I'm actually getting it even after I load RS in my browser.

Fire Monkey

2011-11-02 16:35:34

I've read on other forums that this happens when you are logged in for 6hours.. Jagex sure knows how to annoy botters!

A G E N T

2011-11-02 17:30:03

I don't think it's even being logged in for any amount of time - I've had it happen a few times recently where I've left the applet open (in a browser) and come back a few hours later to get that message.

noidea

2011-11-02 17:34:10

From: Coh3n
We talked about this on the SMART thread. If we can't find a solution, I'll make an option for restarting SMART. The user can choose whether or not to do so.

E: Harry, I still get this error after RS says it's updated.


I'm actually getting it even after I load RS in my browser.


Same man. I changed the SMART_World or w/e it is, and that fixed it.

Kave

2011-11-02 17:47:07

We'll be doing a system update in about 20 minutes to try and fix the problem with log-in timeouts for some people.

Keep an eye out for the timer!

Could this be the fix hmm?

Harry

2011-11-02 17:51:38

That error will only happen if you're trying to load an invalid world. If you load a valid world now without updating it doesn't error, at least not for me.

Narcle

2011-11-02 19:53:07

From: Harry
That error will only happen if you're trying to load an invalid world. If you load a valid world now without updating it doesn't error, at least not for me.


This. I think the default for SMART_world in the include is random() every time its ran. With my scripts I always set SMART_world := 1 or 160 that way SMART doesn't have to reload.

Coh3n

2011-11-02 20:39:10

From: Fire Monkey
I've read on other forums that this happens when you are logged in for 6hours.. Jagex sure knows how to annoy botters!
Happened to me after 2 hours.

From: A G E N T
I don't think it's even being logged in for any amount of time - I've had it happen a few times recently where I've left the applet open (in a browser) and come back a few hours later to get that message.
Me too.

From: Kave
We'll be doing a system update in about 20 minutes to try and fix the problem with log-in timeouts for some people.

Keep an eye out for the timer!

Could this be the fix hmm?
Let's hope so. :)

From: Harry
That error will only happen if you're trying to load an invalid world. If you load a valid world now without updating it doesn't error, at least not for me.
Yeah, I got it to work now, thanks.

From: Narcle
This. I think the default for SMART_world in the include is random() every time its ran. With my scripts I always set SMART_world := 1 or 160 that way SMART doesn't have to reload.
How do you know you'll never get it with those worlds?

Wanted

2011-11-02 20:56:06

The actual build number isn't any more frequent than normal: http://www.moparisthebest.com/rs/update.log interesting…

Coh3n

2011-11-02 21:04:56

This announcement says they're aware of the issue, I think. I'm assuming anyway as I'm not aware of any other type of login issue.

kingarabian

2011-11-02 22:50:35

From: Coh3n
This announcement says they're aware of the issue, I think. I'm assuming anyway as I'm not aware of any other type of login issue.


I think it's purposely there as an anti-ban measure. If it was some kind of bug then our players won't be getting kicked out of the game right around 6 hour mark.

insanomano

2011-11-02 22:59:27

I have encountered this problem also, I have been running my personal M1D1 Powerminer for long periods of time on my main and every time I come back a few hours later RS has been updated, I definitely think its to catch bots and whatnot

Coh3n

2011-11-03 02:00:33

From: insanomano
I have encountered this problem also, I have been running my personal M1D1 Powerminer for long periods of time on my main and every time I come back a few hours later RS has been updated, I definitely think its to catch bots and whatnot
I find that hard to believe simply because if I was a legit player I would find that rather annoying.

kingarabian

2011-11-03 03:47:37

From: Coh3n
I find that hard to believe simply because if I was a legit player I would find that rather annoying.


But not many legit players play for 6 hours straight.

Coh3n

2011-11-03 09:28:49

It doesn't always happen after 6 hours. A few people, including me, had it happen after only a couple hours.

WT-Fakawi

2011-11-03 11:20:06

From: Coh3n
It doesn't always happen after 6 hours. A few people, including me, had it happen after only a couple hours.

Yes, I have seen that too. I have had session of 6 hours 54 minutes. But also 2 hours 45 minutes.

Maybe it is at regular GMT/EST times?

EDIT:

BTW: are you too noticing a long lag (freeze) when re-entering the game after a random?

Flight

2011-11-03 11:26:32

From: WT-Fakawi
BTW: are you too noticing a long lag (freeze) when re-entering the game after a random?


This and clicking on the quest/music/emotes tab. The bigger the list it has to load, the longer the lag…

WT-Fakawi

2011-11-03 11:34:09

I suspect when returning from a random they do some code-shuffling :)… why would it otherwise all-of-a-sudden take so long?

Heavenzeyez1

2011-11-03 11:38:14

From: Flight
This and clicking on the quest/music/emotes tab. The bigger the list it has to load, the longer the lag…


Yes, I've noticed it as well, sometimes it takes up to 3-5 seconds, can be very annoying nad yes, after coming back from random it will lagg much aswell. :(

~Eerik.

HyperSecret

2011-11-03 11:39:08

There are a lot of areas atm that encounter large lag spikes when doing. They are actually trying to address that issue too (according to them).

About the "RS updating" stuff, I only have it happen to me when I log out of the game and try to log back in. It doesn't automatically "kick"/take me out of the game SOLELY to do this. So when your scripts go to switch players, that is probably when this comes up.

Flight

2011-11-03 11:48:07

From: WT-Fakawi
I suspect when returning from a random they do some code-shuffling :)… why would it otherwise all-of-a-sudden take so long?


That would be pretty smart if that's what they were doing. IDs snuffled after every time that map region changes? Teleports/random events/walking to a different area.

Ya know if you hadn't said it I wouldn't have realized it. Click on your quest tab and after the long lag click to another tab, then back to the quest tab. It won't take any time at all to load it the second time, right? Now walk to a different area and try clicking on the quest tab again, another huge pause?

onilika

2011-11-03 14:38:50

Hmm…now that yous guys are talking about those updates, I'll have to take a closer look when I play Runescape for long hours. And then, I'll see if post some stuff at this thread.
Thanks for you guys having me know..

Coh3n

2011-11-03 14:39:02

From: HyperSecret
About the "RS updating" stuff, I only have it happen to me when I log out of the game and try to log back in. It doesn't automatically "kick"/take me out of the game SOLELY to do this. So when your scripts go to switch players, that is probably when this comes up.
Yes that's when it happens to me. I'll be running one player soon so we'll see how that goes.

kingarabian

2011-11-03 15:10:46

From: HyperSecret
There are a lot of areas atm that encounter large lag spikes when doing. They are actually trying to address that issue too (according to them).

About the "RS updating" stuff, I only have it happen to me when I log out of the game and try to log back in. It doesn't automatically "kick"/take me out of the game SOLELY to do this. So when your scripts go to switch players, that is probably when this comes up.


I am running a single player script as well and it gets kicked near the 6 hour mark.

Kave

2011-11-03 22:12:19

From: kingarabian
I am running a single player script as well and it gets kicked near the 6 hour mark.


*You will be automatically logged out after 6 hours of continuous play. This is to stop someone who has hacked an account to stay on it, which helps the original owner recover it once they have changed their password. This can also stop bots, however, most bots are advanced enough to re-login. *

kingarabian

2011-11-03 22:53:00

From: Kave
*You will be automatically logged out after 6 hours of continuous play. This is to stop someone who has hacked an account to stay on it, which helps the original owner recover it once they have changed their password. This can also stop bots, however, most bots are advanced enough to re-login. *


Yes before they would kick you out of the game and you would have to re-log. BUT it now kicks you out, tells you Runescape has updated, and you have to reload the game. Don't forget some people have been getting this at the 2-3 hour mark as well.

What makes it really suspicious is that as you reload the game, something is being updated or downloaded to either the cache or client because the loading takes its time…

P1nky

2011-11-04 03:39:20

Runescape is gay… what's really happening is … they lose $$$ since bot accounts dont buy p2p anymore … less players … item stock will be lowered = more expensive (yews/food/runes/etc….)
RS should just let it be… either way, all these communities will find a substitute. Players will get irritated from these lags and what not and more people will quit … since it is quite hard to make $ and get those 99's legitly. oh well that's Runescape or we are just too spoiled/use to the easy money income haha.

kingarabian

2011-11-04 05:49:17

logged me out @ around 5 hours requiring me to refresh.

Heavenzeyez1

2011-11-04 06:28:38

From: kingarabian
logged me out @ around 5 hours requiring me to refresh.


I played legit yesterday just to see what happens, I had been online for 5h and 53 min and got kicked, had to refresh aswell. :(

~Eerik.

Swatarianess

2011-11-04 10:40:14

apparently its a pointless method to stop botting :/

kingarabian

2011-11-09 13:32:09

Just to prove that the client indeed updates every 4-6 hours is that my bot logged me out @ just 1 hour of run time. 6 ours later I try to login to my account and it tells me Runescape has updated. Ofc Jagex really didn't update. So logged in our logged out the client updates in 6 hours. Which is a good time frame because not many legits play for 4-6 hours-ish straight.

Kyle Undefined

2011-11-09 13:39:41

From: kingarabian
Just to prove that the client indeed updates every 4-6 hours is that my bot logged me out @ just 1 hour of run time. 6 ours later I try to login to my account and it tells me Runescape has updated. Ofc Jagex really didn't update. So logged in our logged out the client updates in 6 hours. Which is a good time frame because not many legits play for 4-6 hours-ish straight.


My bot is about to come up to 5 hours total running. I have it setup to bot for 2 hours, then take an hour break, and repeat. I wish there was a way around it :/

Coh3n

2011-11-09 13:45:08

From: Camo Developer
My bot is about to come up to 5 hours total running. I have it setup to bot for 2 hours, then take an hour break, and repeat. I wish there was a way around it :/
SMART just needs to be reloaded. IIRC you just have to call SetupSmartEx again when an update has been found. I've never tried this so I don't know if it works, but it's worth a shot.

Also, Ben said by doing that you could run into memory issues if you restart SMART several times because RS doesn't free the JVM properly (I think).

Shuttleu

2011-11-09 13:51:59

From: Coh3n
SMART just needs to be reloaded. IIRC you just have to call SetupSmartEx again when an update has been found. I've never tried this so I don't know if it works, but it's worth a shot.

Also, Ben said by doing that you could run into memory issues if you restart SMART several times because RS doesn't free the JVM properly (I think).


no because the RS memory is held in the program running it (in this case simba) meaning the memory doesnt get free'd and to free it you need to close and reopen simba, which would stop the script (i can remember pointing this out before and said it was a memory leak :p)

lemme find it…

~shut

kingarabian

2011-11-09 14:22:32

From: Coh3n
SMART just needs to be reloaded. IIRC you just have to call SetupSmartEx again when an update has been found. I've never tried this so I don't know if it works, but it's worth a shot.

Also, Ben said by doing that you could run into memory issues if you restart SMART several times because RS doesn't free the JVM properly (I think).


Yeah there are definitely problems with reloading SMART. I am running 6 SMARTS right now, imagine if I restart them all and the previous memory is not released? My memory would be 6x2 = 12 while I'm only running 6 SMART's.

Yago

2011-11-09 21:10:43

Just get wizzup to create something to somehow free only SMART memory and we will

Love Him Forever!!!!

Kyle Undefined

2011-11-10 09:19:52

From: Yago
Just get wizzup to create something to somehow free only SMART memory and we will

Love Him Forever!!!!


It's the way SMART works which is the problem, and also the JVM.

obx420

2011-11-11 10:07:10

I just got back after several months off autoing/Runescape. I just started using my fighter the script yesterday again, works fine but after about 5 hours my game "Updated" and got me disconnected. When i woke up I set it up again about 1 hour and 30 minutes into this session I read a message as I walk by, "Runescape will be updating in 1 hour".

2 Updates so soon? :confused:

hamster31

2011-11-11 11:17:29

From: obx420
I just got back after several months off autoing/Runescape. I just started using my fighter the script yesterday again, works fine but after about 5 hours my game "Updated" and got me disconnected. When i woke up I set it up again about 1 hour and 30 minutes into this session I read a message as I walk by, "Runescape will be updating in 1 hour".

2 Updates so soon? :confused:


If you play longer than 6 hours continously…they "update" runescape.

obx420

2011-11-11 12:36:21

From: hamster31
If you play longer than 6 hours continously…they "update" runescape.


Thanks for the info.

Any information if this "update" if caught playing and disconnected by this "update" (while using a script) flags you're account for "botting/macroing"?

If so I may have to keep a closer eye on my account while it's going.

Coh3n

2011-11-11 14:37:47

I may flag your account, but I wouldn't count on it because this happens to legit players as well. If you just have the client open for 6 hours it happens. Before this, accounts were logged out after playing 6 hours straight to stop hackers from staying on the accounts they hacked.