SRL Archive - OSR Help

"Client Token changed" error?


Ilya

2012-12-09 22:12:16

Compiled successfully in 2013 ms.
SRL Compiled in 16 msec
Loading SMART: [url]http://world39.runescape.com/f50349848004636901[/url]
Welcome to Runescape.
XXXXXXX
Screenshot of: IP Log 55 Seconds
'Client token changed.'
SRL Compiled in 15 msec
Successfully executed.

Keeps restarting the client even after it logs the player in.
Anyone else having this?

King

2012-12-09 22:17:23

From: Ilya
Compiled successfully in 2013 ms.
SRL Compiled in 16 msec
Loading SMART: [url]http://world39.runescape.com/f50349848004636901[/url]
Welcome to Runescape.
XXXXXXX
Screenshot of: IP Log 55 Seconds
'Client token changed.'
SRL Compiled in 15 msec
Successfully executed.

Keeps restarting the client even after it logs the player in.
Anyone else having this?


Hmm, restart Simba and the computer?

DannyRS

2012-12-09 22:18:08

Hmm weird, something somewhere is detecting a false positive on the client token update, hard or all but impossible to determine from that debug info though, try a fresh install of smart or entire simba?

Edit - if your using smart 7.2, go update to 8.0 its definetly worth it in the long run, and this may solve this problem whatever is causing it

krasniy

2012-12-10 06:26:43

Nope…working properly for me atm…. the previous suggestion of restarting everything is a great place to start. Hope it fixes your situation……….

Ilya

2012-12-10 15:33:51

Updated Smart to 8.0.
Still, even the first time I start Simba, logged my player in, says client token error, stops the script. Does it have something to do with my mainloop?

Begin

SetupSRL;



DeclarePlayers;
LoginPlayer;
Wait(RandomRange(5000, 6000));
ClickNorth(SRL_ANGLE_NONE);
SetAngle(0);



Theron

2012-12-12 01:14:40

I am having this same error :/

Justin

2012-12-12 06:08:04

Any chance you are able to get a screenshot right before it does this?

If you can't get a screenshot because it is closing the client too fast put
SRL_SixHourFix := false;
above the
SetupSRL;

in your script.

DannyRS

2012-12-12 06:10:14

Hopefully smart 8 will be in the damn installer soon so we can be done with this lol

Justin

2012-12-12 06:11:17

From: DannyRS
Hopefully smart 8 will be in the damn installer soon so we can be done with this lol


I don't recall having this problem with SMART 7.2 or 8.0

From: Ilya
Updated Smart to 8.0.
Still, even the first time I start Simba, logged my player in, says client token error, stops the script. Does it have something to do with my mainloop?


Your mainloop looks fine.

Please read the last post by me and add the line to the correct place and then see what happens

DannyRS

2012-12-12 06:18:42

From: [J]ustin
I don't recall having this problem with SMART 7.2 or 8.0


Me neither, but i get bored of all the threads because people cant extract a Zipped folder to the correct place,

Guess i kinda missread the topic, but its annoying to have to deal with half the people using 7.2 and half 8.0, would be awesome to just have the one standard for everything :)

Ilya

2012-12-13 12:02:39

From: [J]ustin
Any chance you are able to get a screenshot right before it does this?

If you can't get a screenshot because it is closing the client too fast put
SRL_SixHourFix := false;
above the
SetupSRL;

in your script.


Trying this now.
Hope it works.:)

Wardancer

2012-12-13 16:21:52

I am able to replicate this error, but, quite frankly, I'm not sure what to think. Someone has to try to replicate the error under the same condition else it'd be meaningless. It happens to me when I try to log on with a f2p account (just as it clicks on Play) and I'm getting the Festive Aura commercial (a commercial to try to make you become a member). It apparently leads to a false positive making the not so smart SMART think that runescape updated.

EDIT: A simple fix, if that's the issue you're facing, is to just disable smart the time that you manually log on to a world.

Ilya

2012-12-13 17:09:46

From: Wardancer
I am able to replicate this error, but, quite frankly, I'm not sure what to think. Someone has to try to replicate the error under the same condition else it'd be meaningless. It happens to me when I try to log on with a f2p account (just as it clicks on Play) and I'm getting the Festive Aura commercial (a commercial to try to make you become a member). It apparently leads to a false positive making the not so smart SMART think that runescape updated.

EDIT: A simple fix, if that's the issue you're facing, is to just disable smart the time that you manually log on to a world.


I'm not getting a commercial message. Mine says client token error as soon as it clicks login. Then mouse moves to the X at the top right of the client.

Justin

2012-12-13 17:15:57

From: Ilya
I'm not getting a commercial message. Mine says client token error as soon as it clicks login. Then mouse moves to the X at the top right of the client.



I'd have to have a look at it actually happening to be able to do some debugging on the issue

Wardancer

2012-12-13 17:43:29

From: Ilya
I'm not getting a commercial message. Mine says client token error as soon as it clicks login. Then mouse moves to the X at the top right of the client.


The commercial message is exactly what's next to the login button. It isn't something that pops up, more like a banner.

EDIT: I find it funny how there are commercials at so many places that we no more recognize it =p.

Justin

2012-12-13 20:07:04

Any chance you are able to PM me the login details so I am able to take a look after work? If not, could you please post some screenshots of the issue?

Wardancer

2012-12-13 23:02:51

[BANANA][/BANANA]

Trying to recreate the issue now, but I'm not getting the same banner anymore. I shall keep trying… for the sake of science (ya, who am I kidding? I just have time to waste).

Justin

2012-12-13 23:18:01

From: Wardancer
[BANANA][/BANANA]

Trying to recreate the issue now, but I'm not getting the same banner anymore. I shall keep trying… for the sake of science (ya, who am I kidding? I just have time to waste).



I'm not sure why there is a red box around the lobby ad, but that should't be affecting anything if that is changing

Wardancer

2012-12-13 23:31:24

I did the red box to point out what the issue was with as people had a hard time understanding what I was referring to. I should've mentionned it. I'm unable to replicate the bug at the moment so the issue might not be the banner too (or maybe something was modified? either the banner of smart codes).

Justin

2012-12-13 23:36:03

From: Wardancer
I did the red box to point out what the issue was with as people had a hard time understanding what I was referring to. I should've mentionned it. I'm unable to replicate the bug at the moment so the issue might not be the banner too (or maybe something was modified? either the banner of smart codes).


I just checked github, the dev team haven't push out any updates yet, not sure exactly was going on but if you could keep an eye on it and make sure you are using the
SRL_SixHourFix := false;
and then get a screenshot of when the script has terminated. (Making that false wont close\restart SMART)

Ilya

2012-12-14 11:30:50

From: [J]ustin
I just checked github, the dev team haven't push out any updates yet, not sure exactly was going on but if you could keep an eye on it and make sure you are using the
SRL_SixHourFix := false;
and then get a screenshot of when the script has terminated. (Making that false wont close\restart SMART)



Here is the debug box
Compiled successfully in 749 ms.
SRL Compiled in 15 msec
Loading SMART: [url]http://world18.runescape.com/f3046015925948442212[/url]
Welcome to Runescape.
XXXXXXX
Screenshot of: IP Log 29 Seconds
'Client token changed.'
Runescape has been updated! Please restart Simba.
Successfully executed.
and that was with the Player owned Ports commercial.
I think it gets a false positive due to the loading box?

Wardancer

2012-12-14 13:58:39

Was it on a f2p account by chance? Might help narrow down the possible issue. Asking because I only experienced the issue on f2p accounts.

iamorange12

2013-05-23 05:49:04

From: Wardancer
Was it on a f2p account by chance? Might help narrow down the possible issue. Asking because I only experienced the issue on f2p accounts.


Yes I've only had this issue of F2P accounts.