SRL Archive - News and General

Should we be afraid?

http://services.runescape.com/m=news/fighting-the-bots---an-update
:norris:

Not at all. We'll be the last bot they look to take legal action against.

Good to hear :) *thumbs up!*

Separately, as part of normal legal process and procedure, we have also taken steps to acquire the details of all players who have purchased bots.

cool

har har, you'll never catch me alive, coppers!

http://www.youtube.com/watch?v=uC6rjeDEVFQ

From: tarajunky
http://www.youtube.com/watch?v=uC6rjeDEVFQ

Win! :D

Too few of us for legal action/action at all to be worthwhile.

From: mat_de_b
Too few of us for legal action/action at all to be worthwhile.

Not only that, IIRC we don't do anything illegal.

In the meantime, be safe, don’t fall to the dark side and we look forward to the positive outcomes of our actions ultimately making the game experience a better one for everyone.

But we have cookies :stirthepot:

From: Smarter Child
Not only that, IIRC we don't do anything illegal.

We break a game ToS agreement rule thing.

From: TomTuff
We break a game ToS agreement rule thing.

The one's who are using the program is breaking the ToS, but not Simba itself. Meaning they can ban the users breaking the ToS, but can't go all legal on simba

From: Zyt3x
The one's who are using the program is breaking the ToS, but not Simba itself. Meaning they can ban the users breaking the ToS, but can't go all legal on simba

Yes, this is what I meant. Simba = clean

Yes indeed! And always will be!

There's one thing that sets us apart from these other botting systems: the fact that Simba can be used for many other things unrelated to RuneScape (forms and GUIs, mouse and keyboard macros for repetitive computer tasks, etc.). The others create software that has one purpose only; to cheat on RuneScape.

I think we as a community are relatively safe :thumbsup:

And we, as a community, we communicate each others, we discuss stuff of our day, and more. We're not so restrict like the others! That makes us uniques :D

This is a very good thing, if Jagex removes Rsbuddy and Powerbot, they'll think they have put down macroing sites, and there will be less bot catching systems, so we can bot more. Understand wat im saying, or do i need to put water on my face because I just woke up?

LOL good morning then ! xD
I agree with you mate! Let's pray for that!

From: Huthaifah
This is a very good thing, if Jagex removes Rsbuddy and Powerbot, they'll think they have put down macroing sites, and there will be less bot catching systems, so we can bot more. Understand wat im saying, or do i need to put water on my face because I just woke up?

They know we are here though, we are one of the oldest cheating communities around. So even after getting rid of Powerbot and RSBuddy they will still be aware of us.

From: Echo_
They know we are here though, we are one of the oldest cheating communities around. So even after getting rid of Powerbot and RSBuddy they will still be aware of us.

Yes, but they can't take legal action against us, as long as we do things properly.

We don't have anything to worry about here or at the few of our associated forums.

~BraK

From: Coh3n
Not at all. We'll be the last bot they look to take legal action against.

There's multiple reasons why you're absolutely right. First of all, we're absolutely non-profit, we've always been this way and always will be. If that changes then I'll cease to support SRL at all.

Secondly, we're the small group, not a big user base, not even a percentage compared to the java bots. We pose very little threat to Jagex. How many other bot sites do you see where the community is up for taking action against the bot swarm? How many of them have developed a report-bot script? (Thanks by the way Harry :p)

Anyways, I think it'd be a good idea to get in the habit of doing as much of our scripts as we can in color just incase something should happen to Reflection.

I like to think of us as Jagex's favorite cheating community <3

^^^ Lol, were harmless :)

From: drags111
I like to think of us as Jagex's favorite cheating community <3

Would be nice to think that :rolleyes:

I was thinking tho, IF runescape messes up the java bots, where will people look to bot again ? to get their fix. SRL will be a big target for leecher and then runescape will look at SRL as a threat and do what ever they can to squash us. I would prefer they just find out better ways of banning people using them (only made to cheat runescape bots) like RsBuddy/RsBot.

From: whacko999
Would be nice to think that :rolleyes:

I was thinking tho, IF runescape messes up the java bots, where will people look to bot again ? to get their fix. SRL will be a big target for leecher and then runescape will look at SRL as a threat and do what ever they can to squash us. I would prefer they just find out better ways of banning people using them (only made to cheat runescape bots) like RsBuddy/RsBot.

Quick! Close registrations and make everything private!!! :P

From: Flight
Anyways, I think it'd be a good idea to get in the habit of doing as much of our scripts as we can in color just incase something should happen to Reflection.

Plus SRL will eventually be able to run straight through updates (only if the script is 100% color obviously). I've been looking in to it lately, taked to BenLand100 and it is possible, I just need the knowledge to do so.

From: whacko999
Would be nice to think that :rolleyes:

I was thinking tho, IF runescape messes up the java bots, where will people look to bot again ? to get their fix. SRL will be a big target for leecher and then runescape will look at SRL as a threat and do what ever they can to squash us. I would prefer they just find out better ways of banning people using them (only made to cheat runescape bots) like RsBuddy/RsBot.

Banning people will help to a certain degree, but it won't make a big enough impact unless Jagex shuts down the source.

From: whacko999
Would be nice to think that :rolleyes:

I was thinking tho, IF runescape messes up the java bots, where will people look to bot again ? to get their fix. SRL will be a big target for leecher and then runescape will look at SRL as a threat and do what ever they can to squash us. I would prefer they just find out better ways of banning people using them (only made to cheat runescape bots) like RsBuddy/RsBot.

I'm for the idea of getting rid of reflection use all in all, I think it's worth it for everyone to lose it including us because we'll always have that upper hand to everyone else… with the exception or RID if anyone knows what that is. :rolleyes:
We could, though, be more particular on which scripts we publicly release and which we would keep privately to the people who contribute. This will always keep out that 90% of user-base who just prefer plug-and-play.

From: Coh3n
Plus SRL will eventually be able to run straight through updates (only if the script is 100% color obviously). I've been looking in to it lately, taked to BenLand100 and it is possible, I just need the knowledge to do so.

I think Appa will play a serious roll in Rs botting should reflection permanently break. It's still minimizable, it's not just the RS client so we'd be loading Runescape through the browser. And because of this, we can check, by color, if Runescape has been updated and simply hit the refresh button or navigate through the main website to load another client. Tis very simple.

From: Flight
I think Appa will play a serious roll in Rs botting should reflection permanently break. It's still minimizable, it's not just the RS client so we'd be loading Runescape through the browser. And because of this, we can check, by color, if Runescape has been updated and simply hit the refresh button or navigate through the main website to load another client. Tis very simple.

Has anyone used Appa for Runescape? I've never used it personally, but if it's really as easy as you describe, maybe it could/should be used for 100% color scripts.

From: Flight
I'm for the idea of getting rid of reflection use all in all, I think it's worth it for everyone to lose it including us because we'll always have that upper hand to everyone else… with the exception or RID if anyone knows what that is. :rolleyes:
We could, though, be more particular on which scripts we publicly release and which we would keep privately to the people who contribute. This will always keep out that 90% of user-base who just prefer plug-and-play.

I think what you seem to be forgetting is how the other bot's aren't using reflection. They are using injection (except a couple of them), which is the one where you run into troubles, as you are modifying and redistributing the client. Reflection is 100% legal, so your argument to get rid of it completely is a bit silly.

Reflection reads client data only it in no way edits or changes it. Thus keeping us on the legal side. :) Ultimately everything here at SRL is legal…

~BraK

From: drags111
I think what you seem to be forgetting is how the other bot's aren't using reflection. They are using injection (except a couple of them), which is the one where you run into troubles, as you are modifying and redistributing the client. Reflection is 100% legal, so your argument to get rid of it completely is a bit silly.

I've always known RSBot was bcel, or atleast it was when I was around, but that was quite a while back. RsBuddy, reflection, those 'perfectious' bots, reflection, NeXus, I really don't know… Get rid of those alone and you've cut bots down by 85%.

powerbot is indeed *injection* if I'm not mistaken. At any rate, our reflection is 100% legal, so it would be silly/stupid to get rid of it. I don't see your argument there.

I've said this before, How hard would it be to make every tile, and id dynamic? They have dynamic tiles in MTA for sure, I don't see how they cant do it for the rest of rs

From: Awkwardsaw
I've said this before, How hard would it be to make every tile, and id dynamic? They have dynamic tiles in MTA for sure, I don't see how they cant do it for the rest of rs

It would still be too easy to get around that. As I was just telling Home about his ess miner: Just get an object thats always in the same spot, use it's tile to calculate your next move. Easy. As far as ID's being dynamic, don't think they could/would do that.

From: drags111
It would still be too easy to get around that. As I was just telling Home about his ess miner: Just get an object thats always in the same spot, use it's tile to calculate your next move. Easy. As far as ID's being dynamic, don't think they could/would do that.

If the tiles change, how can you find the object? As far as reflection knows, the object has moved

You don't find objects by the tile… You find them by the ID.

From: drags111
You don't find objects by the tile… You find them by the ID.

And assume that id's are dynamic ;)

Is it possible for them to prevent Java bots from "hacking the client" ?

They can't just make the Ids dynamic. But even if they did all you would need to do is check model points or something along those lines. All these what-if arguments wills do you no good since a lot of it they simply just won't do.

From: drags111
They can't just make the Ids dynamic. But even if they did all you would need to do is check model points or something along those lines. All these what-if arguments wills do you no good since a lot of it they simply just won't do.

Enlighten me, please :) explain how it won't work. How different is it from dynamic tiles

The reason they have dynamic tiles is because it's what's called an instance location. They have static locations such as the entire world map, and this allows for allthe users to be together in the world. If they sent you to an instance every time yOu logged on then you wouldn't be able to see anyone else. It just doesn't make sense that they would so that.

They could potentially change the tile IDs every day or so, though.

You're suggesting dynamic everything. Now, if it was dynamic everything, how would the client even know when you clicked something? If the location the object was on must have moved by the time you clicked it, I suppose the client thinks you're walking now…Very good, you've managed to shut down all bots. Color and reflection alike. Heck, even legit players can't play properly. (Obviously this is an exaggerated case of dynamicness)
The client still needs to have way ways to determine an event. Jagex can create new fields for identifying objects (they'll still need to be able to get information from the cache), but it means reflection can still get it…
If the client "knows" something, reflection can get it (provided its not a local field).

From: pyroryan
You're suggesting dynamic everything. Now, if it was dynamic everything, how would the client even know when you clicked something? If the location the object was on must have moved by the time you clicked it, I suppose the client thinks you're walking now…Very good, you've managed to shut down all bots. Color and reflection alike. Heck, even legit players can't play properly. (Obviously this is an exaggerated case of dynamicness)
The client still needs to have way ways to determine an event. Jagex can create new fields for identifying objects (they'll still need to be able to get information from the cache), but it means reflection can still get it…
If the client "knows" something, reflection can get it (provided its not a local field).

This.

EDIT: @Flight: Current bots that use injection: powerbot, rsbuddy, runedev, and epicbot.

we have also taken steps to acquire the details of all players who have purchased bots.

Oh wow. I wonder how they're planning to get that information and what they're going to do with it. Didn't they already try to take down Impsoft and lost? Seems like the usual exaggerated Jagex bullshit that they pull out of their ass to keep legit players happy.

From: pyroryan
You're suggesting dynamic everything. Now, if it was dynamic everything, how would the client even know when you clicked something? If the location the object was on must have moved by the time you clicked it, I suppose the client thinks you're walking now…Very good, you've managed to shut down all bots. Color and reflection alike. Heck, even legit players can't play properly. (Obviously this is an exaggerated case of dynamicness)
The client still needs to have way ways to determine an event. Jagex can create new fields for identifying objects (they'll still need to be able to get information from the cache), but it means reflection can still get it…
If the client "knows" something, reflection can get it (provided its not a local field).

Nicely stated pyroryan :) Rep+

~BraK

You told me earlier Powerbot was reflection.

I guess I've misspoke then, not so much doing something about reflection but an obtained client that's directly loaded rather than through the Runescape website.

As far as Awkwardsaw's points, I can back him up in that. I've noticed in a few places both Object tiles and Object IDs are dynamic. Take the Abyss for example, say the ID for the crawl space (Agility) is… 4321 at tile 3200,4300…, the next time you enter the abyss that same tile might have no object at all, and that specific ID (4321) might be the ID for distraction eyes, so nothing is static, the only definite way to search for what you're looking for is Model ID's, if you can track those on the mini-map then that'd be great…

This is also done in the Livid Farm and I assume it's the same in the newly release Jadinko Lair.

From: Flight
You told me earlier Powerbot was reflection.

I guess I've misspoke then, not so much doing something about reflection but an obtained client that's directly loaded rather than through the Runescape website.

As far as Awkwardsaw's points, I can back him up in that. I've noticed in a few places both Object tiles and Object IDs are dynamic. Take the Abyss for example, say the ID for the crawl space (Agility) is… 4321 at tile 3200,4300…, the next time you enter the abyss that same tile might have no object at all, and that specific ID (4321) might be the ID for distraction eyes, so nothing is static, the only definite way to search for what you're looking for is Model ID's, if you can track those on the mini-map then that'd be great…

This is also done in the Livid Farm and I assume it's the same in the newly release Jadinko Lair.

Right and like I said, those are Instances. That can exists within instances because its not the static "world of runescape." Outside an instance, find me a dynamic object.

EDIT: Also when did i tell you powerbot was reflection…

From: drags111
powerbot is indeed reflection if I'm not mistaken. At any rate, our reflection is 100% legal, so it would be silly/stupid to get rid of it. I don't see your argument there.

If we can't search by ID or Tile, how would we find them? Can we find an object on the mini-map by searching just for the model ID?

From: Flight
If we can't search by ID or Tile, how would we find them? Can we find an object on the mini-map by searching just for the model ID?

Ah i meant to say injection, typo. And what you said earlier was you were going to stop using object finding all together. You didn't say only in this scenario. And there are probably some wall objects that are static in there you could use as a reference. Remember, there are more than just interactables you could search for.

I'm working on a solution to the abyss issue (should also apply to Livid Farm). Drags111 is testing the fix atm.

Edit:
SecondLevelObject.getChangingIDs (modelReferenceID? I need a better name) should solve the issue. Preliminary testing is successful for abyss.

Edit 2:
Abyss eyes:
Trip 1: changingID = 7168;
Trip 2: changingID = 7168;

Looking good.

Edit 3:
All of them match according to Drags.

Hooks file updated.

From: Flight
You told me earlier Powerbot was reflection.

I guess I've misspoke then, not so much doing something about reflection but an obtained client that's directly loaded rather than through the Runescape website.

As far as Awkwardsaw's points, I can back him up in that. I've noticed in a few places both Object tiles and Object IDs are dynamic. Take the Abyss for example, say the ID for the crawl space (Agility) is… 4321 at tile 3200,4300…, the next time you enter the abyss that same tile might have no object at all, and that specific ID (4321) might be the ID for distraction eyes, so nothing is static, the only definite way to search for what you're looking for is Model ID's, if you can track those on the mini-map then that'd be great…

This is also done in the Livid Farm and I assume it's the same in the newly release Jadinko Lair.

I guess if by "dynamic" you mean that the objects' appearance can be changed during runtime, you're correct. Many npcs and objects have varying appearances based on the value of a particular setting. Farming patches work that way, and your objects in the abyss are no different.

From: drags111
Right and like I said, those are Instances. That can exists within instances because its not the static "world of runescape." Outside an instance, find me a dynamic object.

EDIT: Also when did i tell you powerbot was reflection…

No, they're not.

From: Method
I guess if by "dynamic" you mean that the objects' appearance can be changed during runtime, you're correct. Many npcs and objects have varying appearances based on the value of a particular setting. Farming patches work that way, and your objects in the abyss are no different.

I was saying the Object ID and Tile will vary, for example, every trip into the Abyss. Are you referring to that or to their Model ID as being the appearance?

From: Method
No, they're not.

You load the area up and things are loaded dynamically (even just the portals) so what you see isn't exactly what everyone else sees, so in a way, kind of is.

@Flight: At any rate we found the solution so you can once again not worry about using objects. Pyro found a hook that stays static even on those "dynamic" objects.

From: Flight
I was saying the Object ID and Tile will vary, for example, every trip into the Abyss. Are you referring to that or to their Model ID as being the appearance?

In all likelihood, neither will change. Here's the information you should need to figure out which object is which:

7142:
-- name: "Blockage" or "Rock" or "Tendrils" or "Boil" or "Eyes" or "Gap" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7156, 7158, 7161, 7165, 7168, 7164, 7154, 7164, 7168, 7165, 7161, 7158, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Blockage, Rock, Tendrils, Boil, Eyes, Gap, Passage, Gap, Eyes, Boil, Tendrils, Rock, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7143:
-- name: "Rock" or "Blockage" or "Tendrils" or "Boil" or "Eyes" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7158, 7156, 7158, 7161, 7165, 7168, 7158, 7154, 7158, 7168, 7165, 7161, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Rock, Blockage, Rock, Tendrils, Boil, Eyes, Rock, Passage, Rock, Eyes, Boil, Tendrils, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7144:
-- name: "Tendrils" or "Rock" or "Blockage" or "Boil" or "Passage" or "Broken rock" or "Chopped tendrils" or "Eyes"
-- 21 parent(s): [7161, 7158, 7156, 7158, 7161, 7165, 7161, 7158, 7154, 7158, 7161, 7165, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Tendrils, Rock, Blockage, Rock, Tendrils, Boil, Tendrils, Rock, Passage, Rock, Tendrils, Boil, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7145:
-- name: "Boil" or "Tendrils" or "Rock" or "Blockage" or "Passage" or "Broken rock" or "Chopped tendrils" or "Eyes"
-- 21 parent(s): [7165, 7161, 7158, 7156, 7158, 7161, 7165, 7161, 7158, 7154, 7158, 7161, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Boil, Tendrils, Rock, Blockage, Rock, Tendrils, Boil, Tendrils, Rock, Passage, Rock, Tendrils, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7146:
-- name: "Eyes" or "Boil" or "Tendrils" or "Rock" or "Blockage" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7168, 7165, 7161, 7158, 7156, 7158, 7168, 7165, 7161, 7158, 7154, 7158, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Eyes, Boil, Tendrils, Rock, Blockage, Rock, Eyes, Boil, Tendrils, Rock, Passage, Rock, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7147:
-- name: "Gap" or "Eyes" or "Boil" or "Tendrils" or "Rock" or "Blockage" or "Passage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7164, 7168, 7165, 7161, 7158, 7156, 7164, 7168, 7165, 7161, 7158, 7154, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Gap, Eyes, Boil, Tendrils, Rock, Blockage, Gap, Eyes, Boil, Tendrils, Rock, Passage, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7148:
-- name: "Passage" or "Gap" or "Eyes" or "Boil" or "Tendrils" or "Rock" or "Blockage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7154, 7164, 7168, 7165, 7161, 7158, 7156, 7164, 7168, 7165, 7161, 7158, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Passage, Gap, Eyes, Boil, Tendrils, Rock, Blockage, Gap, Eyes, Boil, Tendrils, Rock, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7149:
-- name: "Gap" or "Passage" or "Eyes" or "Boil" or "Tendrils" or "Blockage" or "Rock" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7164, 7154, 7164, 7168, 7165, 7161, 7164, 7156, 7164, 7168, 7165, 7161, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Gap, Passage, Gap, Eyes, Boil, Tendrils, Gap, Blockage, Gap, Eyes, Boil, Tendrils, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7150:
-- name: "Eyes" or "Gap" or "Passage" or "Boil" or "Blockage" or "Rock" or "Broken rock" or "Tendrils" or "Chopped tendrils"
-- 21 parent(s): [7168, 7164, 7154, 7164, 7168, 7165, 7168, 7164, 7156, 7164, 7168, 7165, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Eyes, Gap, Passage, Gap, Eyes, Boil, Eyes, Gap, Blockage, Gap, Eyes, Boil, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7151:
-- name: "Boil" or "Eyes" or "Gap" or "Passage" or "Blockage" or "Rock" or "Broken rock" or "Tendrils" or "Chopped tendrils"
-- 21 parent(s): [7165, 7168, 7164, 7154, 7164, 7168, 7165, 7168, 7164, 7156, 7164, 7168, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Boil, Eyes, Gap, Passage, Gap, Eyes, Boil, Eyes, Gap, Blockage, Gap, Eyes, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7152:
-- name: "Tendrils" or "Boil" or "Eyes" or "Gap" or "Passage" or "Blockage" or "Rock" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7161, 7165, 7168, 7164, 7154, 7164, 7161, 7165, 7168, 7164, 7156, 7164, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Tendrils, Boil, Eyes, Gap, Passage, Gap, Tendrils, Boil, Eyes, Gap, Blockage, Gap, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

7153:
-- name: "Rock" or "Tendrils" or "Boil" or "Eyes" or "Gap" or "Passage" or "Blockage" or "Broken rock" or "Chopped tendrils"
-- 21 parent(s): [7158, 7161, 7165, 7168, 7164, 7154, 7158, 7161, 7165, 7168, 7164, 7156, 7159, 7160, 7162, 7163, 7166, 7167, 7169, 7170, -1]
--- Rock, Tendrils, Boil, Eyes, Gap, Passage, Rock, Tendrils, Boil, Eyes, Gap, Blockage, Rock, Broken rock, Tendrils, Chopped tendrils, Boil, Boil, Eyes, Eyes, null
-- vbidx: 625
--- vb: bits 18 to 29 of setting [491]
-- sidx: -1

pssshh.. my script is almost entirely math based… lets see if they can break that:P

From: Jagex
Don't fall to the dark side

lolz…

Yay Jagex is cleaning up the bots so more $$$ and EXP for us! :D

IF they actually clean up the bots. Chances are they wont succeed :P