SRL Archive - Banned from RS

hi guys, just got banned using private green drags killing script. This one survived around 7k kills. I have no clue why i got it? maybe because i like to keep fighting dragon to keep at 45 or 315 degree angle ? antiban is huge, with lvl3 inside cases of random in some places, no clue tbh why, thought script is good. Loots both type of piles, where u see bone first or green hide first, uses porters, random looting scenarios, loots charms and clues,3 random walking pathes either to drags and to canoe, uses canoe to travel, cause botted moss drags. sometimes failed with edge teleport, because sometimes openinterfaceequipment fails , was thinking of rewriting that part but now i have something to thing about.

From: cosmasjdz
hi guys, just got banned using private green drags killing script. This one survived around 7k kills. I have no clue why i got it? maybe because i like to keep fighting dragon to keep at 45 or 315 degree angle ? antiban is huge, with lvl3 inside cases of random in some places, no clue tbh why, thought script is good. Loots both type of piles, where u see bone first or green hide first, uses porters, random looting scenarios, loots charms and clues,3 random walking pathes either to drags and to canoe, uses canoe to travel, cause botted moss drags. sometimes failed with edge teleport, because sometimes openinterfaceequipment fails , was thinking of rewriting that part but now i have something to thing about.

Do you use global variables/some method of logging to keep track of the number of times each individual function does not work the way it should? Adding those to scripts when you are writing them/redoing them and then testing can be very useful to you to find out what you need to rewrite.

By finding what messes up, you also find things that could make your script look more botty.

No one can tell without looking at the code if it is likely that script to have gotten you banned or not.

Were you running multiple accounts on it? If so, were their cache's seperated? Have you used any other scripts on it recently? If so, which/what type were they, and how long ago? Did you take breaks? What was the total average break time in 24 hours? Did you just run it constantly?

People tend to agree on that will make a script more likely to get you banned:
Botting with a script that is broken/does very repetitive things over and over with no randomization. (doesn't matter if it was the last script used on the acounnt)

yea a lot of people are getting banned atm (including me, gf 4 mains =( )

no i dont use global variables basicly i keep an eye on it, i dont leave it afk. I am updating it, fixing toobotty things, since it used to be in developement stage, wanted to add world hopping if oponent is near, fix some small issues, mostly the teleport toedge procedure. I also kept working on another script while waiting this one to fail. Basicly i use2 acc at the same time the another one is safe. and yep this script only was being used 1acc at a time. I used to bot for like 3-4 hours a day, longer at weekends after work. i dont trust it enough to leave overnight or while i am at work. It doesnt do repetetive things, have 2 separate atacking functions, some variations/antiban/minibreaks crowded everywhere as there could be, some antiban has like 1/3500 chances during antiban procedure like i said stacked 3 floors antiban… Iv lost another acc week ago when starting this script but then i didnt even had walking procedure variations, i have not had drags locating procedure, used to turn screen random angles.. and it survived 4k drags so around 50 hours without any antiban and just some very primitive procedures. Now i have quickloot, Normal loot, normal loot has variations whatever pick first etc… i just think somehow jagex seen smart? or 2 accs? By the way cache is in same folder…….

From: cosmasjdz
no i dont use global variables basicly i keep an eye on it, i dont leave it afk. I am updating it, fixing toobotty things, since it used to be in developement stage, wanted to add world hopping if oponent is near, fix some small issues, mostly the teleport toedge procedure. I also kept working on another script while waiting this one to fail. Basicly i use2 acc at the same time the another one is safe. and yep this script only was being used 1acc at a time. I used to bot for like 3-4 hours a day, longer at weekends after work. i dont trust it enough to leave overnight or while i am at work. It doesnt do repetetive things, have 2 separate atacking functions, some variations/antiban/minibreaks crowded everywhere as there could be, some antiban has like 1/3500 chances during antiban procedure like i said stacked 3 floors antiban… Iv lost another acc week ago when starting this script but then i didnt even had walking procedure variations, i have not had drags locating procedure, used to turn screen random angles.. and it survived 4k drags so around 50 hours without any antiban and just some very primitive procedures. Now i have quickloot, Normal loot, normal loot has variations whatever pick first etc… i just think somehow jagex seen smart? or 2 accs? By the way cache is in same folder…….

IF jagex can see smart right now, they have not decided to ban everyone using smart. Either there is an issue with your script, or you used a different script that was buggy on your account that got it flagged, or you ended up using the same cache with a bugged/unstable script, or you got player reported.

By the way you describe your usage of the program, it does not sound like you trust it at all. I leave my scripts running for long periods of time, and I don't bat an eye, or have any anxiety over them, as they have many fail safes. By using a reporting system/variables to keep track of each procedure/function/action you do, if it DOES mess up, you can easily tell where the mess ups are coming from, and adjust it.

There should be no issue of trust in your script running, the procedures either work 99% of the time, or they don't, or jagex updated something/lag(and the lag can be dealt with). A script will do exactly what you tell it to do. I'd recommend tracking all your methods, and debugging it after running it a bit to see what is problematic, and then refine from there.