SRL Archive - RS has been updated.

We've all been thinking about this new update. I'll try to summarise what I think has happened and will happen.

At least for a while, Reflection bots are out of the question. Some have gone as far as state that a whole new approach to Java botting is required, which could indicate it would take months, if not longer to get working java bots again. And they'd have to become popular again, and they'd have to face continued changes by Jagex, as Jagex has stated that they will continue to try and stay ahead of bots.

This means that a lot of users will just quit botting in general, and some will go to the only two working colour bots: Simba+SRL or RiD (which I have admittedly only heard of, I don't really know anything else about RiD).

Jagex also stated that at some point they would go after colour bots. I have absolutely no clue as to what that means. Essentially, you can hardly stop a bot that just works as a human player - although a mentally challenged human player with an incredibly long focus span. Unless they're going to throw in major graphical changes and rid them self of the safemode / software mode rendering I don't see any big bumps ahead for SRL.

We should however not think that we are untouchable. We might need new techniques to adept to their client-side changes, perhaps even new functions in Simba to properly read the Runescape client, etc. (Can Simba currently target and perform find functions on the OpenGL client?)

What we should worry about - and I advise caution, is the fact that they completely dropped the unsigned client. Using a signed client means they can access files on your computer, view active processes, etc. Even having something like Simba on your computer (although I really doubt this) might make you look like a potential botter to Jagex. While I am very sure they currently do not employ anything like this, it is probable that they might try something like this in the future. I'm not exactly sure how much they would be affected by privacy laws and all, but we'll have to ponder on this.

As for the future of SMART, I predict that SMART will work again for colour at some (hopefully near) point in the future, but I doubt it will give us Reflection back any time soon.

So, what will happen in the next few weeks on SRL? I suspect we'll come forward with SRL-5. It is not a complete rewrite of the include, but rather the long awaited clean up (removal of deprecated functionality) and features a (nearly complete) SRL documentation. We're in the process of back porting our documentation. Switching to SRL-5 should be relatively painless and would generally only require changing a few include statements.

Going forward, there will be a new interpreter for Simba which will most likely offer proper Linux/Mac (and 64 bit on Windows) support alongside with other features that I cannot give exact details on, as I don't know what those features will be exactly. (Perhaps OOP, perhaps pointers, perhaps another language but that does seem unlikely for now)

We'll also work on integrating the initial script manager in Simba - it's in a somewhat finished state but I assume to actually make it usable and attractive (GUI work mainly) it'll require some more work. We could then have a central repository with all the scripts on SRL - with integrated SRL Stats support, providing updates for all the scripts.

We've survived all this time because of our awesome community - and I see that hasn't changed one bit. See you on the forums and on our IRC channels, #srl and #simba. (on irc.rizon.net)

Let's do this! :)

Great! Good to hear that :)

Good to hear

From: Wizzup?
We've survived all this time because of our awesome community - and I see that hasn't changed one bit. See you on the forums and on our IRC channels, #srl and #simba.

I think this is what makes SRL different from other bots out there, community and people working together is the key to survival as you have stated.
__________________

From: Wizzup?
This means that a lot of users will just quit botting in general, and some will go to the only two working colour bots: Simba+SRL or RiD (which I have admittedly only heard of, I don't really know anything else about RiD).

I think what RiD lacks (what SRL has) is:
1) large amount of people working on scripts, perfecting them (community) and
2) free scripts. Most of them cost money, and at least you used to pay by the minute, meaning a "lifetime" bot costs a lot more than "48 hours" bot.

This is nice get an official evaluation on the situation and how it affects (and will affect) us. A general outline of what's to come and where we'll begin is great to get out there for everyone. Thank you for this.

Rsbuddy think they are already near ready state to start :(

Update: Before releasing an ETA I await Jagex's supposed second update, however, despite false speculation, the majority of the first update has already been completed at this time. Expect more information on Wednesday evening.

I wonder if it would even be legal to spy our computers to see if it contains something like simba…. That would make runescape spyware wouldn't it.

From: Troll
Rsbuddy think they are already near ready state to start :(

Of course they will say that to calm down their customers.

From: weequ
I wonder if it would even be legal to spy our computers to see if it contains something like simba…. That would make runescape spyware wouldn't it.

Sony almost got away with installing a rootkit on your computer when you pop one of their music cds in your computer. It's all legal until you get caught/enough people raise a stink.

I originally wanted to "pm" you via rep, but I must spread more before it so I will just spam instead.

I loved your speech. These leader speeches always makes me think about big film actor leaders speaking :D, if you get what I mean. Well done.
And SRL-5 I always believed in you!(noooooo, this last sentence is not sarcastic about all the delay :p)

New comers from other communities have high expectations.

From: Wizzup?
We've all been thinking about this new update. I'll try to summarise what I think has happened and will happen.

At least for a while, Reflection bots are out of the question. Some have gone as far as state that a whole new approach to Java botting is required, which could indicate it would take months, if not longer to get working java bots again. And they'd have to become popular again, and they'd have to face continued changes by Jagex, as Jagex has stated that they will continue to try and stay ahead of bots.

NeXus bots are supposed to be operational by the end of the week. I've been busy with school and got around 30 minutes yesterday to analyze the changes. If I get done with homework today, I'll get around to fixing parts of my deobber that broke and maybe hooking. Apparently with the update, a BCEL deobber doesn't play along nicely with an ASM updater (produces corrupted files due to missing labels). Not sure why yet.

From: pyroryan
NeXus bots are supposed to be operational by the end of the week. I've been busy with school and got around 30 minutes yesterday to analyze the changes. If I get done with homework today, I'll get around to fixing parts of my deobber that broke and maybe hooking. Apparently with the update, a BCEL deobber doesn't play along nicely with an ASM updater (produces corrupted files due to missing labels). Not sure why yet.

The not sure why yet is the main problem. If I have to believe BenLand100 or Speljohan, it is harder than most people think it is. I'm not saying Java bots will never come back, though.

From: Wizzup?
The not sure why yet is the main problem. If I have to believe BenLand100 or Speljohan, it is harder than most people think it is. I'm not saying Java bots will never come back, though.

Perhaps, I imagine Speljohan has invested quite a bit of time in analyzing so I won't question his judgement. The Object[][] pose some issues, but theres no reason that the type can't be stored for later use. Jagex is probably smart enough to randomize the indexes as frequently as possible, but these indexes still have to be stored. At this point, the indexes are not randomized.
I've sent to TRiLeZ a virtually recompilable deob yesterday and he started hooking.

Awesome news! And yes, RiD is getting a lot more popular due to other botting communities knowing about it, we're not as "known" (which is good, we don't really want most of those kids) I see posts about it on jsp people are heading over to it… for now

I really do hope we're the only bot around for a long while… but my hope is diminishing =[

From: pyroryan
Perhaps, I imagine Speljohan has invested quite a bit of time in analyzing so I won't question his judgement. The Object[][] pose some issues, but theres no reason that the type can't be stored for later use. Jagex is probably smart enough to randomize the indexes as frequently as possible, but these indexes still have to be stored. At this point, the indexes are not randomized.
I've sent to TRiLeZ a virtually recompilable deob yesterday and he started hooking.

Yeah but at this rate you guys will need atleast 3-4 days trying to obtain hooks. Jagex updates every week and they could have hidden updates as well throughout the week to scramble everything again. Basically this means less than 2-3 days of botting for the average-Joe. We still don't even know there new method of detection.

From: kingarabian
Yeah but at this rate you guys will need atleast 3-4 days trying to obtain hooks. Jagex updates every week and they could have hidden updates as well throughout the week to scramble everything again. Basically this means less than 2-3 days of botting for the average-Joe. We still don't even know there new method of detection.

You could have said the same thing years ago about hooks. Thats why updaters were built. And you are correct that we don't yet know if there are any new methods for detecting bots.

From: weequ
I wonder if it would even be legal to spy our computers to see if it contains something like simba…. That would make runescape spyware wouldn't it.

You agree to let them do that when you click "Allow for now" or "Always trust this *someWordHere*" on the pop-up that comes the first time you run runescape.

Wizzup? Link(s) to ScriptManager thread(s)? I'm quite interested

I use an autohotkey script to switch between scout accounts while I'm rune-mining, and everytime I use the script to log in to one of the scouts the client tells me that RS has been updated and I need to reload the page rather than letting me log in. This makes me believe that there is now detection built into the loading of the client, possible for processes, possibly just because autohotkey is easily detectable.

We moved back to freenode? :s

From: pyroryan
You could have said the same thing years ago about hooks. Thats why updaters were built. And you are correct that we don't yet know if there are any new methods for detecting bots.

Yeah will see. Tbh they've updated there client twice in the past 18 hours. Did it affect your hooks in anyway?

From: Hobbit
We moved back to freenode? :s

My bad… lol :p

From: pyroryan
You could have said the same thing years ago about hooks. Thats why updaters were built. And you are correct that we don't yet know if there are any new methods for detecting bots.

Couldn't you have a program iterate through all of the methods in the 668 client, store them in a map of some sort, then iterate through all of the methods in the new client removing methods with matching descriptors from the map? That would narrow down the amount of code we have to look through to find their detection.

From: legoace
I use an autohotkey script to switch between scout accounts while I'm rune-mining, and everytime I use the script to log in to one of the scouts the client tells me that RS has been updated and I need to reload the page rather than letting me log in. This makes me believe that there is now detection built into the loading of the client, possible for processes, possibly just because autohotkey is easily detectable.

Just had this happen to me… What happened was I changed my IP (did this by switching from my router to my iPhone tethering)..

Did that three times.. every single time it made me reload the client instead of letting me log in.. It sucks ass.. U get disconnected and get a new IP, ur screwed.. Same IP ur fine.. I tested this enough times now playing in that laggy ass castlewars.. Venge group everyone, lagged out.. new IP = reload.. Lagged out, same IP = login.

Kk so I tried this on a different computer and I get this:

http://i.imgur.com/qrBbs.png

every time… no matter what I do.. gotta keep my IP static.

From: Wizzup?
Some have gone as far as state that a whole new approach to Java botting is required, which could indicate it would take months, if not longer to get working java bots again.

Accurate statement is accurate. I would expound on this, but that would be a bit off topic. Short and sweet: The recent bots (anything in the last two years) worked because Aryan worked (to any devs that disagree with me, don't lie to yourselves; you couldn't have gotten reflection working without using the pre-existing knowledge that existed from mooching Aryan's codebase). Aryan worked because the client could be easily decompiled and studied. Now? Lol. The only real hope for a speedy recovery is if EVERYTHING code wise is the same and it's simple to figure out how Jagex has stored everything. Then an attempt at an updater could ensue, but this will be at least months away.

My two cents.

From: BenLand100
Accurate statement is accurate. I would expound on this, but that would be a bit off topic. Short and sweet: The recent bots (anything in the last two years) worked because Aryan worked (to any devs that disagree with me, don't lie to yourselves; you couldn't have gotten reflection working without using the pre-existing knowledge that existed from mooching Aryan's codebase). Aryan worked because the client could be easily decompiled and studied. Now? Lol. The only real hope for a speedy recovery is if EVERYTHING code wise is the same and it's simple to figure out how Jagex has stored everything. Then an attempt at an updater could ensue, but this will be at least months away.

My two cents.

There is something magical about this post.

From: Echo_
Couldn't you have a program iterate through all of the methods in the 668 client, store them in a map of some sort, then iterate through all of the methods in the new client removing methods with matching descriptors from the map? That would narrow down the amount of code we have to look through to find their detection.

Using KNN or another algorithm, sure.

This update truly deserves a spot in the little black book

Also this:

From: c0de
Also this:

Thats nothing. I was online with only 23 people in my world last night. People we need to hurry up and make scripts. I'm going to start on my Karamja fisher.

Im updating my Draynor fisher. Should be finished this weekend.

From: kingarabian
Thats nothing. I was online with only 23 people in my world last night. People we need to hurry up and make scripts. I'm going to start on my Karamja fisher.

From: noidea
Im updating my Draynor fisher. Should be finished this weekend.

MSI has both in case that affects anything. :p

If I recall, RSBuddy's progress resulted in the mere loading of the client and obtaining a ban instantaneously on login.

Progress and more progress! That's good news :)

From: c0de
Also this:

I wonder how that affects the number of worlds… Hopefully Jagex doesn't shut too many down.

From: t4
If I recall, RSBuddy's progress resulted in the mere loading of the client and obtaining a ban instantaneously on login.

Where did you get that information?
The official anouncements and blogs state that it is not distributed to anyone yet…

From: BenLand100
Accurate statement is accurate. I would expound on this, but that would be a bit off topic. Short and sweet: The recent bots (anything in the last two years) worked because Aryan worked (to any devs that disagree with me, don't lie to yourselves; you couldn't have gotten reflection working without using the pre-existing knowledge that existed from mooching Aryan's codebase). Aryan worked because the client could be easily decompiled and studied. Now? Lol. The only real hope for a speedy recovery is if EVERYTHING code wise is the same and it's simple to figure out how Jagex has stored everything. Then an attempt at an updater could ensue, but this will be at least months away.

My two cents.

I massively agree with you about the reference to all current bots being massively based off, and or influenced heavily by Aryan - As for a speedy recovery, it's not looking promising at the moment. Jagex have done themself a nice little treat at the moment: Switching around usage of native code, mashing everything into one huuuge array and removing (as we know / define it) the loader.

What has been learned recently (and when I say recently, I mean over the last year or two) has to be completely thrown to a side and only used for assisting in what must be redone now as far as I'm concerned.

From: Cowie`
I massively agree with you about the reference to all current bots being massively based off, and or influenced heavily by Aryan - As for a speedy recovery, it's not looking promising at the moment. Jagex have done themself a nice little treat at the moment: Switching around usage of native code, mashing everything into one huuuge array and removing (as we know / define it) the loader.

What has been learned recently (and when I say recently, I mean over the last year or two) has to be completely thrown to a side and only used for assisting in what must be redone now as far as I'm concerned.

So Rsbuddy claiming to be back tomorrow, or on Monday is a bluff right?

From: kingarabian
So Rsbuddy claiming to be back tomorrow, or on Monday is a bluff right?

From what I've seen so far, yes.

From: Cowie`
From what I've seen so far, yes.

Interesting, thanks for your input!

From: kingarabian
So Rsbuddy claiming to be back tomorrow, or on Monday is a bluff right?

They have an "update" countdown timer in the top right corner of their site. It's set for about 3 days and 14 hours from now. We'll see.

From: Silent SPY
They have an "update" countdown timer in the top right corner of their site. It's set for about 3 days and 14 hours from now. We'll see.

I think its to let people know the site will be down for a time while they update their server.

great thread. i got a comment and a suggestion:
comment: i have never used unsigned clients when botting. i have always botted signed. why? cuz it loads faster, and remembers cache. (ok maybe 1/1000 times il load unsigned)
and ive never been banned. and i bot hard. its not on an army. mostly on 1 acc for like 8-18 hrs a day. minimal breaks if any.

i rather doubt jagex will use java to monitor the systems of its customers. some heavy privacy law issues. even if they were to, i dont think they can do it unless it says so in their TOS or they will have to update their TOS and have us accept. (someone confirm this as i think im right but not 100% sure).

apart from that…my suggestion:

can you add to this threads OP the changes that jagex made to the game client. i belive ive seen marpis' post on the changes but i was unsure if he was speculating or quoting, so could you make like 2 lists saying confirmed (with source) and speculation (by whom - as in trusted such as wizz or marpis).

thanks.

oh also, as far as color scripts go, werent all randoms based on ref? as in when we had ref did we even bother updating random fixes for colors?

Unfortunately in Jagex's ToS, they state they withhold the right to update/alter/modify the ToS at any time without notification (They have done this in the past).

From: RS ToS
We may change these terms and conditions to reflect: changes in applicable laws; regulatory or security requirements; relevant guidance or codes of practice; technical alterations to Jagex Products; and to improve clarity and consistency. Please check the terms and conditions whenever you use a Jagex Product. If you are not a subscriber, we will treat your continued use of a Jagex Product as acceptance of these changes from their effective date as shown above. If you are a subscriber, we will treat you as bound by the changes on the first renewal date for your subscription after the effective date and so you should cancel your subscription (as explained below) before this renewal date if you don't like the proposed changes.

So they've changed the wording a little bit, but they are basically saying if you're not a member by loading our applet you accept our ToS. If you are a member, the fact that you are a member means you accept the ToS.


Edit:

From: RS Privacy Policy
We may change this policy at any time. Please check it whenever you return to the site. We will treat your continued use of our websites as acceptance of these changes from their effective date as shown above.

So again, they can change it at any time without notifying us.

From: RS Privacy Policy
We use cookies, collect and store IP-addresses, alphanumeric IDs and other unique identifiers in order to identify specific computers that access our websites. We identify and store the versions of Java and .NET (if any) on your computer along with your browser and operating system, and details of your device's hardware and software specifications.

Note that the scope of information they are collecting that could fall under "[…]details of your device's […] software specifications." it isn't defined.

From: Hobbit


Note that the scope of information they are collecting that could fall under "[…]details of your device's […] software specifications." it isn't defined.

well thats not good. but im wondering if this kinda falls into a scenario where its like your having a contract to do illegal things…err what i mean is …:

is it ok for jagex to simply say by visiting our website u agree we can invade ur privacy?

i mean isnt that like holding a gun t someones head and forcing them to sign a contract? err ofc one can argue that no ones forcing us to play rs, but what im saying is shouldn't they be restricted?? i suppose its country to country basis on laws. or would we have to abide by the laws of the countries in which the servers reside?

Scanning your computer and harvesting information which they then store would indeed be against privacy laws. Scanning your computer (per terms of a ToS/Priv Policy) for adjacent processes flagged at "bots" but storing no personal information would be well within law.

I believe WoW does this?

From: Hobbit
Scanning your computer and harvesting information which they then store would indeed be against privacy laws. Scanning your computer (per terms of a ToS/Priv Policy) for adjacent processes flagged at "bots" but storing no personal information would be well within law.

I believe WoW does this?

I heard the same, Blizzard apparently did/does this.

From: Hobbit
Scanning your computer and harvesting information which they then store would indeed be against privacy laws. Scanning your computer (per terms of a ToS/Priv Policy) for adjacent processes flagged at "bots" but storing no personal information would be well within law.

I believe WoW does this?

wouldn't it be a simple matter to alter the name or signature of such software? similar to the concept that rs updates hooks could we not have our bots change process name? split processes?(idk if that's even possible) or have a firewall limit the data java can receive/send? protocols and ports etc

From: Hobbit
Scanning your computer and harvesting information which they then store would indeed be against privacy laws. Scanning your computer (per terms of a ToS/Priv Policy) for adjacent processes flagged at "bots" but storing no personal information would be well within law.

I believe WoW does this?

They do, but it sure as hell doesn't give them an edge over botters. Botting is still a major problem there as well (BG bots and grinding bots).

From: chitin
wouldn't it be a simple matter to alter the name or signature of such software? similar to the concept that rs updates hooks could we not have our bots change process name? split processes?(idk if that's even possible) or have a firewall limit the data java can receive/send? protocols and ports etc

Only problem is, what stops them from coming here and looking what we've changed the name too(nothing). I know Ben mentioned earlier about possibly modifying SMART to sandbox the runescape runtime and trick it.

From: Hobbit
I know Ben mentioned earlier about possibly modifying SMART to sandbox the runescape runtime and trick it.

This would be nice. Meanwhile I'm going to play around with running RS inside a VM and Simba out on the host. It will still be able to detect it is running inside a VM, but that is not proof you are botting.

From: Hobbit
Only problem is, what stops them from coming here and looking what we've changed the name too(nothing). I know Ben mentioned earlier about possibly modifying SMART to sandbox the runescape runtime and trick it.

Forgive me I know nothing of the technical side of Simba and SMART, but wouldn't it be possible to make the name change simple so every person can change it to whatever they want? This way it would be impossible for Jagex to snoop the name from these forums, as everyone would have a different name.

Once again, I have no idea if this is even remotely possible. Just something that popped in my mind.

From: Hobbit
Only problem is, what stops them from coming here and looking what we've changed the name too(nothing). I know Ben mentioned earlier about possibly modifying SMART to sandbox the runescape runtime and trick it.

well like bottomtooth said, have it be changed to user input or just generate a totaly dif name. but perhaps a safer outcome would be to change it something that already exists: svchost. as far as having the system start it instead of user, well we can force that by having it autostart on start up or with task scheduler or maybe some other technical way. that or if were really tricky we can change the name to known RAT or worm….so if and when we get caught we can say we was haxxxed. :p

but about jagex snooping around, are they allowed to look at other peoples sites when employed by jagex? i could have sworn i saw mopar have a disclaimer of some sort on his site saying something like "if you work for jagex you cannot visit this site or your breaking law # blah blah blah"

but maybe that was just my misunderstanding?

In the updates posted today there is a mention of changing the location of uptext, which will severely hinder SRL for a while unless we prepare now. They said that there will be an "option" that will place NPC names/etc next to the mouse cursor rather than in the upper-left of the screen. Hopefully the OCR is modular enough that it can be changed over quickly. Just a heads-up in case no one else saw that.

We noticed. The OCR is versatile enough to OCR anything they can put on our screens (captcha's aside), but it might be a pain if all scripts need a revised uptext api. It might be possible to (accurately) detect the box's position then OCR there, and redirect uptext to that function.

IIRC getuptext uses static coords for grabbing the text. If we can figure out how to get the appropriate location for the text, this update might be a good thing. if they put a const background behind the text that is.

From: Nava2
IIRC getuptext uses static coords for grabbing the text. If we can figure out how to get the appropriate location for the text, this update might be a good thing. if they put a const background behind the text that is.

I had a quick 'n sloppy idea of just finding the upper-left corner (bitmap probably) of the "soon-to-come" text box and search within a max X/Y area from that beginning corner point for any text. Atleast once you find the box's corner you'd have a static X/Y to start at. I don't know if colors along would be so accurate, depending on what else is shown on-screen while the text box is present.

From: Flight
I had a quick 'n sloppy idea of just finding the upper-left corner (bitmap probably) of the "soon-to-come" text box and search within a max X/Y area from that beginning corner point for any text. Atleast once you find the box's corner you'd have a static X/Y to start at. I don't know if colors along would be so accurate, depending on what else is shown on-screen while the text box is present.

If there is a static coloured background (which there probably will be), it will make the OCR algorithm SO much quicker. Currently, the majority of the algorithm is just filtering out background noise. If we have that removed, we can get the EXACT points associated with the text and pass it to the OCR – we now have a much easier set of text to work with.

I hope this update goes like we expect.. Having the text show up overtop of the general surroundings would be quite a pain.. the only thing that might be bad is that they might do a semi-transparent box. If this is the case, I believe (not 100% sure) there is a relation between HSL of a colour when you make it transparent… or perhaps this is the alpha? Either way, it will give us something much easier to work with!

From: noidea
There is something magical about this post.

There's something bloody well magical with BenLand himself. :P

From: Hobbit
Only problem is, what stops them from coming here and looking what we've changed the name too(nothing). I know Ben mentioned earlier about possibly modifying SMART to sandbox the runescape runtime and trick it.

Was about to comment. "Sandbox"
but i read your post. brilliant idea.

This may sound a bit far fetched, but what if there were a required option during install to rename Simba and it's process to something different? (That is, if it's not possible to change the process name while it's running) At the very least this would slow Jagex in detecting Simba.

How difficult would it be to make Simba compatible with the OpenGL client (if it isn't already)? Surely if we start now we can eventually crack down coloring methods for the higher graphics settings. There's not a doubt in my mind that Jagex will now be paying very close attention to the graphics settings players use and may work towards removing the old settings.

I'm definitely going to try to make time this weekend to write a not-so-complicated color bot!

It's possible to change a programs name, hide its process and so forth, if its in .NET, which SIMBA looks like its been developed in..
A particular example devs of simba should look into is World of Warcraft's pvptool(aka pirox bot), which hides rather successfully from WoW's Warden detection system through polymorphing the .exe

From: Deni_mulic
It's possible to change a programs name, hide its process and so forth, if its in .NET, which SIMBA looks like its been developed in..
A particular example devs of simba should look into is World of Warcraft's pvptool(aka pirox bot), which hides rather successfully from WoW's Warden detection system through polymorphing the .exe

Simba is not .NET, it is Object Pascal. But yeah, it is possible to change names and titles.

From: Deni_mulic
It's possible to change a programs name, hide its process and so forth, if its in .NET, which SIMBA looks like its been developed in..
A particular example devs of simba should look into is World of Warcraft's pvptool(aka pirox bot), which hides rather successfully from WoW's Warden detection system through polymorphing the .exe

program new;
begin
 Disguise('SomethingHere');
end.         

~Home

From: Home

program new;
begin
 Disguise('SomethingHere');
end.         

~Home

I believe that only changes the program title.

Why are people seriously giving ideas on how to avoid JaGeX checking for programs that are possibly bots on your computer?

They don't.

From: Wanted
I believe that only changes the program title.

True, but I thought that it was what he asked :D


~Home

From: weequ
I wonder if it would even be legal to spy our computers to see if it contains something like simba…. That would make runescape spyware wouldn't it.


Of course they will say that to calm down their customers.

Well actually, World of Warcraft does exactly this. It looks at active process while your playing the game, and if theres a process amtch with a confirmed bot in it's database then its bye-bye to your account!

And they've managed to sneak this part somewhere in the middle of the ToS where nobody reads it anyway, so technically you're agreeing to it which makes it legal :P

First time here…No im not a rsbuddy transition but a RID tester. I wanted to see how well this bot works and hopefully help it advance…

From: hamster31
First time here…No im not a rsbuddy transition but a RID tester. I wanted to see how well this bot works and hopefully help it advance…

Welcome. I've heard that RiD is less advanced than SRL but I have personally never tried it. Next time make a new topic, I don't think this it is very relevant to this topic? ;)

From: Home
True, but I thought that it was what he asked :D


~Home

I meant more along the lines of hiding the process altogether from the task manager, I know the disguise function has been around for years lol

Any material on how this update works?