Alek

Well the script does exist. Is it worth 1B? I certainly do not think so. There were static NPC ids which are prone to breaking every week, randomized sleep times, randomized camera angles, and randomized just about everything (more happy to see randomized actions than bullshit sleep times). It didn't really strike me as anything revolutionary, just doing the same types of randomization but perhaps with a different formula. I have never found real players to naturally play this randomly. Also once again, more goes into a ban than just a script. The client, the botting patterns, linked accounts, total account consideration, etc. I'll move it back, but by no means am I claiming this script to be complete, working, and certainly not any better in terms of detection than any other script written for OSBot.

I don't give a crap about your methods or stealing anything from you. You are making outrageous claims for a private script with an outrageous price tag. If you want to be taken seriously I'm looking for some serious code to look at.

Those mouse keys are nothing. No offense but all it is, is elementary math and Java API written in 1996. If this is what OSBuddy is doing, then we are basically doing the same thing. I'm not looking at videos, I'll look at code. Since your antiban code is so sacred (even though I'm very sure if anything you are using an external API), send me the code without it.

Sure, lets go with the method simply wrapping the awt events just to keep things simple. You still didn't really show anything that proved these claims: 1. "fully custom mouse implementation which clones Sony's touch screen input controls" 2. "Combined with an exact clone of OSBuddy mousekeys behavior" I'm not saying that whatever you have is "ban proof", I just want to see what you're trying to sell actually exists. What you showed was stuff I've seen from the scripters you're calling out.

1. I want you to read the title under my name. 2. Now I want you to read what you wrote in your original post, "come with a fully custom mouse implementation which clones Sony's touch screen input controls" 3. Now I want you to read the default OSBot mouse event code which we created that you have in your snippet.

Seems like your internet is working well, I'll give you 30 minutes to part out parts of the code on a private pastebin.

Ill sandbox it later, in the meantime send me at least part of the script on pastebin. Your 1B pricetag ($1000?) barely pays my rent for the month. Specifically speaking, I want to see your main class and your mouse keys implentation. Either that or Ill ban you.

Your joke was the funniest at "open-license crypto-secure custom random generator" and "exact clone of OSBuddy mousekeys behavior".

This joke thread went serious real quick.

April Fools is over, belongs in the spam section. Edit: Boy you guys on this forum are gullible and eat up any anti-ban garbage someone pulls out.

Only if botters actually read the news on the main oldschool webpage, they would know the answer to this question. Edit: For the illterate, there was a news post about a month ago stating that all auto-clickers including "AHK" are bannable. They made some exceptions for whatever OSBuddy is doing since they can already get away with murder already.

Depends on what you mean by random events. Do you mean the in-game random events only, or do you mean the login screen, welcome screen, and bank pin as well? Also face palm gave some instructions on how to enable it.

Inheritance 101: interface Animal { int getAge(); } class Dog implements Animal { int getBarks(); } class Cat implements Animal { int getWhiskers(); } Dog doggo = new Dog(); doggo.getAge(); doggo.getBarks(); Cat cate = new Cat(); cate.getWhiskers(); cate.getAge();

In C++ you would have to define the function as taking a reference, otherwise this code would behave the same (pass by value). The function would look like: static void addOneTo (int& num)

This shows you all the coding conventions for Java (from an official source): http://www.oracle.com/technetwork/java/codeconvtoc-136057.html It tells you about spacing, brackets, naming styles, etc.

Strange, OSBot "natively" reads the class files; meaning that OSBot will unpack the zip or jar files and then use ClassLoader.

Moving this to the conspiracy theory section.

Moving off to scripting help, it's not a client bug.

Just for clarification "reflection" is not "injection vs reflection", it's to allow the Java reflection library which has nothing to do with detection at all. No randoms means anything thats a random event including auto-login, breaks, bank pin, etc. Edit: Also memory is not the max memory, it's the max heap space for the jvm. Your memory limit WILL exceed the limit you put in that box. Look up "Java Xmx" for more information.

If you didn't set a conditional sleep recheck time, the docs said it was centered around 25 ms. It was actually always at 20 ms and the sleep time which you set was randomized. Sometimes the sleep times you defined would go negative, therefore not sleeping at all. It was actually an issue I discovered with low cpu + grand exchange.

Doesn't take care of scrolling or items with the exact same name but different item ids. /:

No idea what that issue was, hopefully it inadvertently got fixed.

I decided to take a look at some of the reports in the Client Bugs & Suggestions and came up with a few things. 1. @Reveance Reported an issue with gRandom not correctly generating random numbers on a normal distribution, and he was correct. Unfortunately when I went to go back and make the formula correct, it broke a lot of our API. I took the lazy approach and deprecated all the gRandom methods and re-documented the method. 2. There were a few random reports about the GrandExchange buyItem/sellItem methods not working correctly on low cpu mode. I tested it, found a few areas of concern, and made it a bit more stable. It's a lot of code and anyone who says they wrote their own "in a few minutes" is either a blatant liar, doesn't perform all the checks, or is using breakable code (such as static ids). Speaking of performing checks, there was a check to see if you already had the buy/sell interface screen open. It however didn't check to see if there was an offer. Now it does both checks; so if there is an offer already in it backs out to the main Grand Exchange interface and selects the next available box. 3. When looking through Grand Exchange API I realized we had a broken function in ConditionalSleep. Probably lived there for many years, oh well squashed for now. 4. Spaghetti witchcraft mouse methods are getting removed. The following methods are deprecated and do nothing: -moveSlightly(int sleep) -moveVerySlightly() Additionally moveRandomly(int sleep) now only calls moveRandomly() without sleeping. Want the old functionality? Call moveRandomly(); sleep(time);. 5. We also took a look at some of the failed to fetch worlds list errors, hopefully thats resolved. Best of luck, let me know how this version works for you guys!

How do we know your custom methods aren't working? Timing.waitCondition? That doesn't look like an OSBot API class.

If the positions aren't being sent to the server and you are still performing actions, then it's pretty much saying you are playing without a mouse or touch-pad (tablets).