Satire

What about 7qp ready accounts?

Road trail. bdum tss

Won't make a difference. The whole client is detected when in tutorial island. It's hard to explain but you'll get banned even if you do tut island manually. The only way not to get banned is to do tut island manually on an actual client.

Look at the like and dislike ratio lmao

Don't hesitate to sell your gold to this guy. He has superb support and is always on point. He's a very professional dude and gets the job done instantly. Highly recommended!

Yea possibly. But It still uses an injection/reflection/technique that reads data through a client. One thing i'm assuming is that the server sends a special token to the client and if the client doesn't respond with the correct answer, it locks your account randomly near the end of tut island or randomly after.

Even if you do it manually with no scripts through osbot you get banned. Abuse shows the vid here. So It's best to do it manually via legit client or osbuddy.

Seems like the accs that are ran through tut island are monitored carefully for a certain amount of time. After that time, it stops monitoring your account if you "pass" the test. They're detecting the client somehow and soon I think they'll role this out for it to constantly monitor all accounts. I'm assuming that their servers aren't good enough to handle all this monitoring so they do it for a certain amount of time. Maybe they're upgrading their servers to allow them to constantly monitor every account. Because they haven't told anyone they updated their system, nobody can confirm what's happening. If you were to make an accounts and finish tut island via Osbuddy or rs client, then logged it out for 24 hrs, it shouldn't ban you. I'm testing it now and if this works, then this will be the end of bots (temporarily) soon when they roll this out. Yolo lol

Seems they have done something different. I'm getting banned now constantly. Even if I make the accs from the website. So I have a theory i'm testing, if this theory is true then I'll never have to worry about getting another acc banned. It wasn't till today I started getting banned. They're constantly improving their anti-bot system. I'm also assuming that they did something to the server configs with their anti-botting system that causes the servers to lag a lot. I tried to unlock the "stolen acc", it asked me to dl the rs3 client and then I was too lazy to even try...

Yaay

Sure EDIT: Added stun, what other spells did you want? I'll finish it off after I get back from the gym. Rolled update.

You're obviously doing something wrong. I haven't been banned at all yet. I've made over 70 accounts since this topic has been made. I haven't changed a thing in my acc creator too. I'm pretty sure you're just using a "flagged" ip. I don't know what you do to cause it to get you banned . I'm having no problems at all lol. As I said, this is a confusing matter. Everyone's getting banned but I'm having no problems at all. I don't really know what they've done to make your accs get locked like that. Have you tried to play on the actual RS client or osbuddy? Does it still lock? If it does, OsBot may be "detected" or some part of it might be. But that wouldn't be the case, or else I would've been banned too. Cause I've been using osbot for a long time since this update.

GUI (tick spell/alch for the combobox to appear) Choose Tile by pushing Get Tile (then it'll show the current Tile). Enter the monsters name exactly as it appears If character goes out of tile, it'll walk back to that tile. Please make sure you are in a safe place because this does not run away from monsters! But, if your health is less than 50% it'll automatically run to the nearest bank from this list and then logout List of banks

Just as I suspected. I made one for my creator lol but did you ever consider the captchas? After 3 attempts, you'll be required to solve a captcha. Giving it a web request after that point, it will not log you in. Instead you'll receive this http://pastebin.com/eUBtsPb2 which is basically a redirect to the login page and throws this result. var RESPONSIVE = RESPONSIVE || {}; RESPONSIVE.constant = RESPONSIVE.constant || {}; RESPONSIVE.constant.user = { language: 0, isLoggedIn: 0 }; It is meant to look like this when you're logged in. RESPONSIVE.constant.user = { id: 1234, name: 'usr', member: false, language: 0, isLoggedIn: 1 }; So the only real way to check the accounts is to either use 2captcha or proxies.

New servers, that's why.

Mine does that but has more logic, it isn't the condition man, it goes passed the condition(condition returns true). It's the actual call! I always use conditional sleeps but I even tested without the conditional sleep. It doesn't want to accept. Have you tried it with this current version? Cause I'm not sure what's going on. My mule trader I made a while back never had this problem so I'm going to run it now to see if it starts spazzing out as well. EDIT: Confirmed, it's the API itself! It started to spaz out and I know for a fact that it isn't broken! Been using it for ages and boom. EDIT2: Cleared the cache and it works, wow I'm a retard. Dunno what caused it to bug out. That's very, very strange.

So idk wtf is going on. I'm here testing out my trading bot and it decides to do this Notice, it's calling the acceptTrade() method. I have a logger that literally tells me "line 344" which is the script calling the accept trade method. Like with osbot 1.0.9 it only happened sometimes, now it happens all the time. Is it just me? wtf. I'm not doing anything wrong, legit. It should just accept! Also: It works well on the second trade interface, just not the first Edit: Will still like to know if it's just me or it is broken. I currently fixed this error by making it interact with the widget itself. EDIT2: CONFIRMED, it's the API! EDIT3: Cleared the cache and it works, wow I'm a retard. Dunno what caused it to bug out. That's very, very strange. @Saiyan Can you please lock this thread lol.

They are treated like normal people. If the system bans them, it doesn't take ranking into account. If a mod bans them, it gets reviewed manually and then banned. I don't know why you posted something so retarded. What do you think? Just cause they have restrictions, does it mean they can't get banned from botting?

I'm not an American so I wouldn't know how it works in America. But from what I can see, Trump can't just keep banning shit or doing shit people don't like. We'll see what happens in the future.

It's best to use Osbuddy. They update the prices every x seconds. As jagex does every 1min - x (can't remember). Kappa I didn't read. From what I can see tho, rsbuddy uses their own prices and their prices are based off of the amount of buys/sells people make through osbuddy.

It will get overthrown just like his Muslim ban. So no, he can't.

I laughed so hard. I thought this guy came back on the show and actually talked about it. The sub fits perfectly with his actions and laughs. The best one yet.

Works fine for me too.

If you make an account with the same ip and bot it on that same ip, you don't get banned ( not with my tut island script). I was then able to use a normal free proxy and login to the account, it still isn't locked. I think if you just make the acc on the same ip and then bot it straight after, you don't seem to get banned. Like legit, I have only been banned twice using my creator and I was using Explv's tut island. When I don't use it and use a private tut island script, I don't get banned. Jagex are playing with us or we're just questioning ourselves too much. They probably made an upgrade to their bot detection algorithim, hence the more frequent bans.

The only reason why he's saying it's the automated creators is because this was not there before. /track/ was added recently, I don't know the exact time it was added but it's new (when I was making my creator, this wasn't there). However, the fact that my creator still works means this tracking is possibly for something else. The fact that I made another 5 accounts and all of them aren't banned means it's either the tut island scripts, people doing something wrong (who knows what) or the ip is *possibly* flagged.