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

EDIT: issue resolved


There was some minute color changes for tabs on 24 Oct. While the changes to GameTab & BankTab are universal, strangely lobby tab color for the RS browser/client remains the same but on Smart it changed.

This means that GetLobbyTab will work on Smart but not for browser/official client as they still retain the original color. Is Smart loading the wrong/outdated RS link?

EDIT: just realize the official client/browser retains the same color, this means that the RS update on 24 Oct only affected Smart?!

Loading RS in FF;

• 1st: Link with basics and 19 Random Numbers…

http://world[COLOR="Blue"]103[/COLOR].runescape.com/,f[COLOR="Red"]1234567890123456789[/COLOR]

• 2nd: Same link as above, except with some incremental (auth?) key
(page refresh, same loaded browser)

http://world[COLOR="Blue"]41[/COLOR].runescape.com/,f[COLOR="Red"]1234567890123456789[/COLOR],Here_Is_a_Length_40_Incremental_Code?

• 3rd: same link as 2nd
(page refresh again, same loaded browser)

http://world[COLOR="Blue"]38[/COLOR].runescape.com/,f[COLOR="Red"]1234567890123456789[/COLOR],Here_Is_a_Length_40_Incremental_Code?

• 4th, same thing when in same loaded browser and you close the tab with loaded game and load in different tab in same loaded browser…
• Note: The entire link stayed the same when I loaded my FF with RS (this test done over several minutes, may conclude differently after 6 hours?)

Hence:
The Worlds #'s change every time, SMART does this too.
The 19 Random Generated #'s are supposedly random every time too, SMART does this too.
The 40 (incremental auth key?) shared the same 1st 22 tokens and then changed the last 18 in what appears incremental (in the last 18) to me. - I don't think SMART does this?

I've wanted to say this for a while too:
Wouldn't loading RS in a proper loader other than trying to direct link be more human? I mean sure it's not BAD (AFAIK so far…) to play RS in a random 19 # generated link, but perhaps that second 40 tokens part creates unique [humanized] action?

Just a thought

Cheers,
Lj

When SMART is called to setup, it will use GetPage and get a vaild RuneScape client settings and they are then passed onto SMART. As far as Jagex can see (and I think) they see us as a valid client just like everyone one

From: [J]ustin
When SMART is called to setup, it will use GetPage and get a vaild RuneScape client settings and they are then passed onto SMART. As far as Jagex can see (and I think) they see us as a valid client just like everyone one

Good point; I still do wonder what the extra 40 tokens are for after refresh.

However an updated SMART loader would be Bendtastic too :)

Idk about whether Jagex can detect it, but it's certainly loading it differently in some way. Just test GetLobbyTab on Smart, then on browser/client. It will work perfectly on Smart but not on browser/client because they are of a different color.

EDIT:
seems like i didn't test it properly just now. In fact all colors remain unchanged on browser/client. Meaning the RS Update on 24 Oct only affected Smart?!

Hope this helps


From the looks of it, it seems that it was a client update, meaning the .jar, not effecting custom clients

Code used to get colors:

program TabDebug;
{$DEFINE SMART}
{$I SRL/SRL.simba}

procedure GetTabColors;
var count : integer;
begin
  for count := 1 to 6 do
    writeln(GetColor(63 + (count-1)*102, 32))
end;

begin
SetUpSRL;
GetTabColors;
end.

Opps sorry i was being an idiot grabbing the colors in Software mode…
Didn't know the colors vary from different modes :redface:

Nothing is wrong then, all colors are correct as long as you are in Safe mode.

From: riwu
Opps sorry i was being an idiot grabbing the colors in Software mode…
Didn't know the colors vary from different modes :redface:

Nothing is wrong then, all colors are correct as long as you are in Safe mode.

Its okay, I had a derp moment when I was getting random colours in the browser then I checked my game-mode too :P

E: IIRC somewhere in the Botney Bay livestream, someone suggested something along the lines of "Why don't you ban the botters before the log in game?" - The response was something like "We aren't able to detect if they are using a different client to load the game"