I've been thinking about this for a while actually. Since I'm using both RID (Occasionally) and Simba, I believe RID has a superior anti-ban.
What I've been considering is, I know Simba and SRL are open source, but how about we start working on a global anti ban, that can be called in all scripts, but people wont' be able to analyze the code of it.
I was thinking something like, make a list of all the things you could do while bored in RS, like look at stats (Wihin there there should be randomness as well, it should roll like 1-30 and pick a stat) The stat you're currently botting should be higher priority though, seems most logical. And even within that, when it rolls, for instance Woodcutting, it would have another roll, to either just hover the skill, or maybe even click it, and scroll around in the overview menu of the Woodcutting skill.
This is just the basic idea, I've been thinking of it for quite some time.
This would be extremely random, and very human like, it would call a random roll within a random roll, within a random roll, leaving it with an almost human decision making... Since it would have 100s of things to do when bored.
AND you could even make it so everytime a script loads, it loads a random roll number (For the whole antiban itself, in ms, like 12002 or something, so every script would be completely random, antiban wise.
Here's a very basic example:
Simba Code:Randomness = '50' // This is the value that should be randomized everytime a script starts.
procedure AntiBan;
begin
if not LoggedIn then Exit;
case Random(Randomness) of
0:ExampleProcedure0;
1:ExampleProcedure1;
2:ExampleProcedure2;
3:ExampleProcedure3;
4:ExampleProcedure4;
end;
end;
procedure ExampleProcedure0;
begin
if not LoggedIn then Exit;
case Random(Randomness) of
0:ExampleAction0;
1:ExampleAction1;
2:ExampleAction2;
3:ExampleAction3;
4:ExampleAction4;
end;
end;
procedure ExampleProcedure1;
begin
if not LoggedIn then Exit;
case Random(Randomness) of
0:ExampleAction0;
1:ExampleAction1;
2:ExampleAction2;
3:ExampleAction3;
4:ExampleAction4;
end;
end;
procedure ExampleProcedure2;
begin
if not LoggedIn then Exit;
case Random(Randomness) of
0:ExampleAction0;
1:ExampleAction1;
2:ExampleAction2;
3:ExampleAction3;
4:ExampleAction4;
end;
end;
procedure ExampleProcedure3;
begin
if not LoggedIn then Exit;
case Random(Randomness) of
0:ExampleAction0;
1:ExampleAction1;
2:ExampleAction2;
3:ExampleAction3;
4:ExampleAction4;
end;
end;
procedure ExampleProcedure4;
begin
if not LoggedIn then Exit;
case Random(Randomness) of
0:ExampleAction0;
1:ExampleAction1;
2:ExampleAction2;
3:ExampleAction3;
4:ExampleAction4;
end;
end;
It's just a really really rough piece of code, but you get the idea! First of all, some general random actions, and when one of those get triggered, you get the specific action it can do in the particular situation. Let's for arguments sake say that "ExampleProcedure1" is something like, "Needing to check something"... Then it has 4 "ExampleActions" one could be "Hoverskill" another could be "clickskill and scroll" Another could be enable xp counter, or whatever! You get the idea.
This isn't as much a suggestion, more like, I need people to join the project. Since it's a big one. And we need alot of different ideas ^^



Reply With Quote












