SRL Archive - General Botting Help

Sorry if I've missed this while searching through the forums, but when I start a script (any script) smart logs in and then right after clicking play gets a message saying that the client token changed and continues on to closing smart and restarting the process. This results in an infinite loop of logging in, "client token changed", and restarting again. Is there an easy fix for this?

Any help is appreciated!
Thankyou!

additional info: Everything worked fine with smart 7.2, but I just updated to Smart 8 and this has just now started happening? I did declare smart8 in the script however?

Log in manually to RS and then start script. Does it still give you that error?

From: t4q
Log in manually to RS and then start script. Does it still give you that error?

yes unfortunately it does :/ not sure why?

From: rotchy1
yes unfortunately it does :/ not sure why?

I suggest you to reinstall :/

From: t4q
I suggest you to reinstall :/

doing my 3rd reinstall as we speak, im gona try to roll back to SMART 7.2

I won't lie… I have a private script that has a 100% of this occurring on login. Just one script, and it is using the exact same initialization code as the rest of my scripts. According to the code for why this error is displayed, it's a pixel count that handles the detection of all our error messages on login (I feel like we could solve that with OCR instead and be more accurate, but i also feel like there's probably a reason for why it is currently done the way it is). But anyway, this issue kinda prevents me from wanting to publicize my script while I can't understand this client token issue. :(

From: Kevin
I won't lie… I have a private script that has a 100% of this occurring on login. Just one script, and it is using the exact same initialization code as the rest of my scripts. According to the code for why this error is displayed, it's a pixel count that handles the detection of all our error messages on login (I feel like we could solve that with OCR instead and be more accurate, but i also feel like there's probably a reason for why it is currently done the way it is). But anyway, this issue kinda prevents me from wanting to publicize my script while I can't understand this client token issue. :(

strange, does this happen to you with only smart8? or is it with 7.2 as well?

From: rotchy1
strange, does this happen to you with only smart8? or is it with 7.2 as well?

I wrote it since I upgraded to Smart8, however I don't really see it as a smart based issue based on the code for how this "client token changed" error is determined. I can offer a suggested change that should at least cover up the issue, but it won't ever detect when the issue would actually occur (which I have no idea what situation that would be anyway tbh).

From: Kevin
I wrote it since I upgraded to Smart8, however I don't really see it as a smart based issue based on the code for how this "client token changed" error is determined. I can offer a suggested change that should at least cover up the issue, but it won't ever detect when the issue would actually occur (which I have no idea what situation that would be anyway tbh).

would you mind posting your suggested change?

Keep in mind this is in no way an official fix by any means and is roughly equivalent to sweeping a ball of dirt under the rug, but:
In your login.simba file (inside the SRL/Core folder), line 816 currently is:

591: Actions := ['Client token changed.',                 0,    0,    'RSUpdate',      'Client Token Changed'];

Just comment that out, so instead it looks like:

//591: Actions := ['Client token changed.',                 0,    0,    'RSUpdate',      'Client Token Changed'];

Edit: I also haven't officially tested this suggestion as I don't like hiding issues as opposed to fixing them. But that's where it detects whether that error happened so that should be how we would hide it away.

From: Kevin
Keep in mind this is in no way an official fix by any means and is roughly equivalent to sweeping a ball of dirt under the rug, but:
In your login.simba file (inside the SRL/Core folder), line 816 currently is:

591: Actions := ['Client token changed.',                 0,    0,    'RSUpdate',      'Client Token Changed'];

Just comment that out, so instead it looks like:

//591: Actions := ['Client token changed.',                 0,    0,    'RSUpdate',      'Client Token Changed'];

Edit: I also haven't officially tested this suggestion as I don't like hiding issues as opposed to fixing them. But that's where it detects whether that error happened so that should be how we would hide it away.

Well it appears my stupidity still has yet to amaze me. Turns out after you update to smart 8 you can to manually put the client into safe mode on first run? haha oh well, seems to work for me. Thanks for the help though!

From: rotchy1
Well it appears my stupidity still has yet to amaze me. Turns out after you update to smart 8 you can to manually put the client into safe mode on first run? haha oh well, seems to work for me. Thanks for the help though!

Oh you haven't been running in safe mode? Well then I think that settles that lol
Good luck!

From: Kevin
Oh you haven't been running in safe mode? Well then I think that settles that lol
Good luck!

turned out to be a fluke, it worked 1 time and then proceded with the same problem, I also tried you quick fix and it does not seem to work :/….the process continues to loop infinitely and I continue to search for an answer.