Alek

THE SCRIPT IS OUTDATED IS IT A SCRIPT ON THE SDN OR A LOCAL SCRIPT?

The timeout is at 15 seconds; meaning the logout waits 15 seconds after clicking "Logout".

Maximum timeout is at 15 seconds.

Must have been Laz:

The OSBot development team has ethical and moral standards when creating software. We are just normal people who write code, learn about technology, and have fun doing it. Consider our team below. Zach: MGI: Alek:

idi nahui

What is this: sleep (random(123,569));

Hope you learned your lesson.

I thought they only made televisions.

It's a laptop, the specs are going to be crap. I don't want a laptop but it's my only option.

I looked at the same laptop but with a 5700HQ and DDR3L for $200 cheaper, looks pretty convincing.

Think I can knock off a few hundred and still get about the same performance?

I'm going to be moving around a lot over the next year so I'm looking to get a laptop. I really love desktops and as soon as I'm stable again I'll get another. Looking at a laptop with: i7-6700HQ (2.6 GHz) GTX 960M (2 GB GDDR5) 16GB DDR4 17.3" display Price: $1,200 Trying to keep the price on the low-side while still being able to work on OSBot, hacking, light gaming, etc. Are these decent specs for a laptop? Update 1: Found same laptop but with 5700HQ and DDR3L for $200, looks convincing.

-Cleaned up InteractionEvent and made a bunch of adjustments. For those who are new to scripting at OSBot, InteractionEvent handles just about everything allowing you to rapidly develop scripts. A few checks which it makes: -Custom visibility checks, optimized for mouse destinations -Rotating the camera -Walking to the object if the camera adjustment fails/doesn't help -Various inventory checks such as if an item is selected -Equipment checks ... and a few other checks/handlers It seems about every month or so I'm working on this event because it's widely used among both new and experienced scripters. If you want anything changed/improved in this event, post in this topic. I'll work on this event (yet again) until Monday, after that I'm going to work on some new stuff. Let me know how this version works in the comments below, I'll keep a close eye.

You can make a poll, but this is not even up for consideration.

This is a pretty small update in comparison to the relatively large releases over the last few weeks. I'll be back from leave next week so expect to see some bigger changes around Thanksgiving weekend. @Alek's changes: -Public API (api package only) method parameters are no longer obfuscated -Booter disables proxies when mirror mode is selected --Proxy settings are dropped anyways when mirror is booted --Plan to remove the mirror mode message regarding proxies, move the text to the right hand side so debuggers don't overlap @Zach's changes: -Updated InteractionEvent camera and point calculations (dealing with trying to click on entities off-screen) -Improved depositAll() for Bank and Trade -Fixed some threading issues with Swing Have a great Saturday/Sunday -The OSBot Staff

This is the proof you have from "two major botting sites": 1. Member with one post count posts on p****bot that he's getting instant-banned. Chris (administrator) had this to say: 2. ***** disabled their client because of claims of client detection. They then solicited feedback from their members with a form; many of which were not banned on OSRS/DMM, but instead banned on DS/RS3. Additionally, they were mainly concerned with botting Tutorial Island. From the looks of it, this is the closest thing which happened to what you are referring: https://www.reddit.com/r/2007scape/comments/3t09cv/ive_just_lost_complete_faith_in_the_jagex/cx20wsg A bunch of accounts got banned in one-go, that's how anti-cheat works. Signatures are built by grabbing a bunch of information to use against botters/cheaters/hackers in the future; when enough information is gathered that account pool is banned. This is nothing new, nothing to be scared of, this is routine business when botting, cheating, or hacking in any video game.

Right click the menu item.

Probably one of the most requested features, this should make it a little easier to start OSBot with pre-configured proxies. I really didn't want to work on this update because I'm a bit tired of working on GUI interfaces, so hopefully I can finally get back to more bot-related stuff. How it works: -In the booter click on the Proxy tab -Type in your proxy details, user + pass if necessary -When you click "Launch", the proxy will be saved for the next boot -Your last used proxy will be set as the first by default -Right click a proxy to remove it (will only save after launch) Proxy information is saved encrypted on your computer, the booter will decrypt the information on load. In addition the AccountSelector is a little bit smarter, making it easier to operate. Zach also worked on some model stuff for improved interactions and new Player API (prayer icon, skull, etc). Currently status: Stable Build Edit: It's possible you may start off with a proxy of "null:null", it's safe to remove this. If you get any serious, try deleting your proxies file located in "Local" OSBot folder. -The OSBot Staff

Without using OSBot filters/DIY: You can do this by grabbing all the NPCs and then sorting the collection with a Comparator. Once you have this sorted collection you can iterate through them to check for everything else such as already in combat, health, etc. Of course you can do this in reverse and filter NPCs that aren't in combat, have high health, etc. and then go on to sort the collection.

What's the name of the script you are using?

Right clicking the bot in the menu closes it.

Ban rate is 10.9%

Tell Henry I said hi.

Look into layering Swing/FX components on AWT (in specific, Applet) and this idea gets thrown out completely pretty quickly. I was really limited in what I could do and explored a ton of options over a week.