SRL Archive - SRL Suggestions

Hey, about 20% of the time I get this error when botting…

We're going to take a break for 19 minutes
We're now going to bot again, for 91 minutes
Welcome to Runescape.
********@*****.Com
'Game session expired.'
SRL Compiled in 0 msec
Loading SMART: http://world53.runescape.com/f5206623663117098436
Welcome to Runescape.
********@*****.Com
Screenshot of: IP Log 7 Hours, 8 Minutes and 34 Seconds
'One minute has passed...  Debug: 1375'
** Warning in SixHourFix: Could not log in player **
Successfully executed.

Obviously this is a bug from SRL SixHourFix,… Does anyone experience the same or has a fix for it?

the title is ironic… SixHourFix bug its meant to be a fix… but its a bug.. hahahah ;)

From: The Killer
the title is ironic… SixHourFix bug its meant to be a fix… but its a bug.. hahahah ;)

:p kind of..

but still, there's a bug in a fix. The fix doesn't work all the time

It could also be that the scripter didn't consider what would happen if the player were to be logged out in the middle of the script.

So it logs back in and then shuts down? Anybody know if any changes been made recently to loginplayer or sixhourfix?

From: Ashaman88
So it logs back in and then shuts down? Anybody know if any changes been made recently to loginplayer or sixhourfix?

I think Riwu took delcare players out so it doesn't mess up multi-player?

From: Ashaman88
So it logs back in and then shuts down? Anybody know if any changes been made recently to loginplayer or sixhourfix?

AFAIK the only change that COULD be effecting this is the SRL_NAVBAR_BITMAP was recently changed…

Maybe Jagex changed the Colour of the text that is counted to detect what login message is displayed.

Fix = Bug… Lol boss.

Did you declare your player id&pass properly?

Also I've never experience any false positive with the new nav bar.
A common error is when you don't set your CTS back to 1 which will cause the nav bar not to be detected.

From: riwu
Did you declare your player id&pass properly?

Also I've never experience any false positive with the new nav bar.
A common error is when you don't set your CTS back to 1 which will cause the nav bar not to be detected.

How do you do that?

From: BMWxi
How do you do that?

If you don't know then you aren't changing it :P so it cant be that.

From: riwu

Also I've never experience any false positive with the new nav bar.
A common error is when you don't set your CTS back to 1 which will cause the nav bar not to be detected.

Although couldn't we fix this if this was the case? (although I cant really understand how it could come to cts) but along the lines of

cts := getcurrenttolerancespeed

setcolortolerancespeed(1)
do the bitmap finding blah blah

setcolortolerancespeed(cts);

I think there are quite a few SRL functions that uses CTS 1, and they do not check for it either. It is the scripter's responsibility to reset to 1 before any LoginPlayer is executed.

Eg. wrong way:

//wrong eg. 1
SetColorToleranceSpeed(2); 
If not FindColorsTolerance() then
  Exit; //exited without setting back

//wrong eg.2 
SetColorToleranceSpeed(2); 
FindColorsTolerance();
//some other codes
if not LoggedIn then  //CTS at this point is still 2!
  LoginPlayer;

SetColorToleranceSpeed(1); 

Always ensure that the CTS will be set to 1 regardless of what happens, and LoggedIn checks should only be performed after it is set to 1.

As a good practice, set it back to 1 right after the color finding function.

Thanks! Will test this this evening :)

Edit: it can't be CTS because I don't use it in my whole script. (But it might be set to 2 somewhere in a function I use from the SRL include, might it?)