sudoinit6

This has been one of the most frustrating parts of building my bot farm, all the misinformation and old wives tales. Fist of all the issue here is locked accounts, not banned accounts, there is a big difference. Secondly I can assure you that verifying emails will not prevent a single account from getting locked. I won't comment on bans because my experience is solely with suicide botting so my ban rate is 100%.

I love that I came here to post something similar and found someone else who thinks the same way I do.

My first scripts were state based and then I discovered tasks. As a noob who is shit at programming I find task based easier to troubleshoot, but really they are pretty much the same thing formatted differently. Just my opinion, but I am bad at this so take it with a grain of salt. Let me show you my Tut Island script and its 60+ classes, it would make you vomit!

I haven't really pushed it yet, it came in the day before I went on vacation and I just got back, but I use HP servers at work and am generally happy with them. Just got back into town last night, I should be updating this thread this week.

42, 2 kids 12 year old son and 15 year old daughter, two step-kids 10 year old daughter 13 year old son. We are like the Brady Bunch.

That was me that posted it, and the more I think about it the more it I believe it is most likely confirmation bias. Until I do so empirical testing it really isn't worth putting much stock in that observation. I intend to test the hell out of several scenarios like Vap0r, but I am out of town this weekend so it is going to have to wait. I do intend to figure out how to circumvent these locks, and I have a few ideas...

Like everything else I will fix them when it doesn't work, that's how one learns.

Meh, I am a horrible coder, but it gets the job done. I was just trying to help out.

This works for me, ignore the "script." that precedes all of my crap, it's a long story. edit: looks like you just need yo use trade instead of getTrade if (script.trade.isFirstInterfaceOpen() == true){ script.log("First window open, waiting"); new ConditionalSleep(30000) { @Override public boolean condition() throws InterruptedException { return script.trade.didOtherAcceptTrade() == true; } }.sleep(); script.trade.acceptTrade(); new ConditionalSleep(30000) { @Override public boolean condition() throws InterruptedException { return script.trade.didOtherAcceptTrade() == true; } }.sleep(); script.log("Second window open, accepting"); Script.sleep(Script.random(2000, 3000)); script.trade.acceptTrade();

Did. I have to run out and do some prep for my trip (taking the family to Cali for awhile). But I am confident we can work through this.

Can you set your system to create the accounts but not run tut? That would alleviate many of the variables. I can try the same but like I said it will have to wait till next week. I would like to add that it is GREAT talking to someone else who knows their stuff and is trying to solve this problem. I have been banging my head against a wall in solitude for a couple months now!

I can test tonight. I have three "first batch" bots running on a proxy today. I will mule them tonight and set that machine to not bounce the proxy server before account creation tomorrow. I will let you know what happens.

The re-captcha solver I use is $.70 per 1000 solves, so literally fractions of a penny. My proxies are "free" because I know stuff. I own my own hardware. I write my own scripts. The only thing I pay for is OSBot. But I will be making much more if I could get enough accounts past these damn locks! Please define "works perfect". You are able to create accounts that don't get locked 100% of the time if you use your "deep freeze like" option?

"so once the session is over everything is wiped (kind of like deep freeze)" But apparently that isn't successful as you are still getting locks/bans, right? "maybe using an API to look up the ISP details, If they can confirm it is a data center IP they lock" I have six bots running right now on two proxies that were created today on Cloud IPs, three of them what I have termed "first batch" I suppose they could only be locking some accounts so that we can't figure out exactly what they are doing, but that seems dubious to me. edit: I have a theory that the IP might get flagged if bots are banned on that IP and any accounts created on that IP in the next x days gets locked after tut island, but it is just a hypothesis that would take testing.

Yes, my proxies are hosted on a large cloud provider. It could be that Jagex has them flagged, it would explain why all accounts are banned the next day, but not why some get locked and some don't. I am also considering creating an account unlock process, that would take considerable effort given all the moving parts involved, but it is doable. I am hoping to find a way to not have to go that route. Hell, at this point I am open to buying accounts but I don't trust that they wont get locked and I want my entire process to be dependent on no one (except of course Alek and his amazing team, I couldn't do this without them). I have yet to do detailed tracking so if I were forced to guesstimate I would say that ~60-70% of the accounts are "successful", but by successful I mean I am able to use them that same day to bot for ~18 hours. I have tried pre-creating the accounts and using them on a day other than the day they were created. I have tried this a number of ways including bouncing the proxy between every single creation and I have a ZERO success rate doing this. All accounts I create in this manner are banned the next day when I try and use them. I am not using a VPS but I have recently acquired a pretty hefty server (Proliant DL 360 G6) so I have more options now. I am considering using VMware and spinning up a new clone for every account creation to check for exactly what you said. I am a unix/vmware admin in real life so this will be trivial, unfortunately I am going on vacation tomorrow and won't be back till next week so that will have to wait. I have yet to try an OS re-install on the machine with higher failures, but I have considered doing that and using something like this: https://www.howtogeek.com/howto/6520/windows-steadystate/ and bounce between account creations. Should I go the VMware route this would be redundant though. Thanks! Then they win. I won't let them win.

I will add what anecdotal information I have for what it's worth. I currently run two different "master" machines that are Windows boxes that create accounts then launch them remotely on a linux box to run. Each Windows machine uses a different proxy both hosted in the same datacenter. Up to this point my machines have each been creating three accounts each day and running those accounts, until recently I was limited by hardware to just six accounts per day. Frequently accounts get locked (not banned, locked) after tut island. If one account gets locked, all three on that proxy are going to get locked within minutes. My machine is able to detect that the account got locked, kill the clients using that proxy, bounce the proxy server (which gives it a new ip), create three more accounts, and try again. Here is the strange part: One machine is highly successful, most of the time none of the accounts get locked. If they do, most of the time the second batch each day is successful. The other machine has an extremely high failure rate, frequently it will take three or more batches of new accounts to be successful. I am not sure what the difference is between these two systems that could be causing this, they are similar hardware and both running the same OS. Neither system is used for anything other than botting. I have done some informal testing and the locks seem to be based on the IP that the account was created on, not the IP the account is played on. I don't believe this has anything to do with the client. I am trying to make the leap from "botter" to "mass farmer" but my bottleneck is accounts that don't get locked. Others are obviously doing it, so any information on how to create mass accounts without them getting locked would be great. Edit: Oh and any account that gets locked, gets banned the next day. I can't speak for the ones that don't get locked because I suicide them that day, so naturally they all get banned too.

Never mind, it was a PEBKAC issue, The bot had the same three letter combo in it's name as the mules. Sorry for wasting peoples time.

This was working before but stopped in the last week (not sure when). My mule bots use it: Player mule = players.closestThatContains("xxx"); if (mule != null) { log("I see" + mule); Script.sleep(Script.random(2000, 3000)); mule.interact("Trade with"); } The log shows this: [INFO][Bot #1][06/06 09:56:23 PM]: I seeorg.osbot.rs07.api.model.Player@XXXXXXXX Repeatedly so it is seeing the mule just not interacting with it. Any thoughts?

I used the free course at udacity. I don't know java well, but well enough to write my own scripts.

What is the best way to determine in script the best buy or sell price of an item on the GE?

So my anti-ban is "being a horrible coder"? It takes my bots 13 minutes on average to complete TutIsland but my bots aren't getting banned...

Aha! I will give that a try, thanks!

I have some code in my script that creates a file when accounts get locked. I have another process that checks for that file every 5 minutes and if it finds it, it closes OSBot, bounces my proxy so it gets a new IP then creates new accounts and launches new bots. The problem I am having is that the code doesn't seem to differentiate between different login failures. Here is what I have: @Override public void onResponseCode(int responseCode) throws InterruptedException { if (ResponseCode.isDisabledError(18)) { log("Account locked, creating text file."); try { PrintWriter writer = new PrintWriter( "//$OSBotPath//data//AccountLocked.txt", "UTF-8"); writer.println("WhateverText"); writer.close(); } catch (IOException e) { // TODO Auto-generated catch block e.printStackTrace(); } } } } Occasionally I will have a network error and in the logs the response code is -2 but this bit of code executes on ANY login failure. I have tried adding code using: if (ResponseCode.isDisabledError(-2)) { But it doesn't seem to matter what integer I put in the code, it activates all of them on any failure. Ideally I would like to perform one action if it is -2 and a different action if it is 18 but I can't seem to get it to work, anyone have experience in thios area?

The hell you say!