Leaderboard

v1.7.80: Mandatory update due to changes in RS. v1.7.81: Fixed issues with closestAttackableNPC() that was causing the bot to click on recently killed NPCs (thanks @Swizzbeat and ).

What is this, a Facebook suggestion?

So I guess I can post this here because Idk Anyway; I've been in music for a while, and this is a vocal cover I did, with some Older gear and software as a one last hoorah with it. (it uses a newer EQ though) All vocals are by me, the music itself is from the album. The song is "Broken Fame" by Fit For a King, Vocals covered by me. (All of them) Warning: This is a heavier song. and I know most of you are not into my style of music so I figured I'd warn you before hand. anyway, tell me what you think. Thanks. https://soundcloud.com/timedead/fit-for-a-king-broken-fame/s-Zvg2L -Dustin

Release 2.0.9 which features a fix for the connection class. Also I believe theres a memory leak where if you open one tab and you close it, the client stays running in the background. I would advise against closing tabs on OSBot 2 until this issue is fixed!

penis

Cool, hopefully the community will help get this thing into tip top shape!

Hello, this is the first semi-public release of OSBot. Please remember that this is still in BETA and still isn't fully completed. OSBot 2 is currently only available for VIP, Sponsors, $100+ Donators, and Script Developers. If it wasn't for these particular people, OSBot would not have been what it is today! Here's the download link: http://osbot.org/osbot2_beta/OSBot-packed-2.0.9.jar Here's the JavaDocs for the latest OSBot 2: http://osbot.org/osbot2_ap Thanks, Report any bugs you encounter. Remember only these particular randoms have been written for OSBot 2: The bot will need baby sitting. This early access version of the bot is too accelerate the development of randoms and fixing bugs by having a wide audience to test it. Have fun! Enjoy! Sincerely, Laz and the OSBot Development Team. EDIT: I've release 2.0.8 which features a bugfix in the client injector! EDIT: I've released 2.0.9 which fixes server-client communications and fixes the script loader.

Enjoyed

GJ

NIce dbow loot at the end

Enjoyed the video, great work!

nice pks man! the music kinda made my ears bleed

Very entertaining, nice video, mate!

Nice video + music!

It doesn't make sense that you are in a RuneScape botting community then, there are other communities out there that do not relate to RuneScape.

Lol thanks man for ur screenshots forgot to ask you :P

I personally don't give a single fuck good fucking luck

Froze after opening third tab, with 2 bots already running,. Just reporting errors.

I vote yes. But only if it doesnt show on profile like your likes does i wouldnt like having 100000000000 dislikes from trolls :P

Hello OSBotters, the much anticipated wait for OSBot 2 is over. On Friday 12:00AM EST, I will be making OSBot 2 available to VIP and Sponsor members. For those who do not have VIP or Sponsor, do not panic! OSBot 2's collection of random event solvers will still be very small. The purpose for this private BETA is to speed up the process of developing the random event solvers to finally get the public bot out. Tonight I released OSBot 2.0.6 to the private testing group. By tomorrow I will have reviewed any bugs mentioned by the private testing group and finalize OSBot 2.0.7, which will be the first semi-public version of the bot. Sneak Peak: Thanks, OSBot wouldn't be possible without our VIP and Sponsor members! Sincerely, Laz and the OSBot Team!

SUPPORT

lel i was gon say .

emulation errors are outrageous Exception in thread "pool-1-thread-7" java.lang.VerifyError: Expecting a stackmap frame at branch target 44 in method script.Core.onMessage(Ljava/lang/String;)V at offset 7 at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.getConstructor(Unknown Source) at org.osbot.script.engine.ScriptManager$4.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

OSBot 2 is actually fairly stable with actual OSBot 2 scripts. The problem is that the emulator for OSBot 1 scripts is still very experimental.

Following on to what @Allen stated above, proper conventions such as indenting, camelCasing, capitalized class names, etc. are just as important as the actual programming. An extremely beneficial resource (like I said before I HATE thenewboston as he doesn't explain anything) would be the Java tutorials from Derek Banas. These videos are on the lengthy side and move extremely fast through lots of different information, but he stresses the important things and explains everything you would need to know in great detail. Here's his first video: Don't be turned off from the amount of material he presents in the short time frame. Just watch the video multiple times and before long (even if you decide to learn the information elsewhere that goes slower) you'll release that watching his video helped tremendously. His whole playlist, a whopping 94 videos, can be found here http://www.youtube.com/playlist?list=PLE7E8B7F4856C9B19

http://gyazo.com/56e1a272c7cec80be37b646012fed851

I didn't know merching was against the rules

lol lazy cele

Hello, first of all I am sorry if this is in the wrong section, it seemed to be the most logical section to post this in in my eyes. The reason I am posting this is, I recently noticed that many people do not understand how the break timer actually works, I know to some this may seem easy, and make this post unneccesary, but I think this still needs to get out there So here it goes: Average interval: is after how long do you want it to take a break? Interval deviation: How long can it vary from the interval time Break time: how long does it take a break? Break time deviation: how long can it vary from the break time Example: I want it to take a break every 2-4 hours, for 30-60 min Average interval: 180 min (=3 hour) Interval dev: 60 min (so it can vary from 180-60 to 180+60 = 2-4 hour) Break time: 45 min Break time dev: 15 min (makes it vary from 45-15 to 45+15 min)

V1.1 Released! Hello, For all my scripts I require a walking class so I made this class that DOESN'T glitch/pause on breaks. Example (V1.1): This class/package is able to: Manage the run energy Open doors (ONLY closed ones) Clicks next Position when it is in range for smooth walking Path randomization which can be turned of for each position DOESN'T glitch/stop Easy to use! Has a debug paint Requirements/How to implement: Import the jar first (You can also open the JAR with 7Zip and go to the walker folder for the source) States makes this alot easier. First you need to make a new PathTile, a PathTile is a class that extends Position so you can use it as a Position aswell. By not specifying the randomize boolean it will be true (so randomized) PathTile tile = new PathTile(Entity ent); PathTile tile = new PathTile(Entity ent, boolean randomize); PathTile tile = new PathTile(int x, int y, int z); PathTile tile = new PathTile(int x, int y, int z, int randomize); Then you make a PathTile array PathTile[] pathTiles = new PathTile[] { new PathTile(3186, 3429, 0), new PathTile(3191, 3429, 0), new PathTile(3196, 3429, 0), new PathTile(3196, 3424, 0), new PathTile(3197, 3419, 0, false) }; // By not specifying the randomize boolean it will be true (so randomized) After that you can make a new Path Path path = new Path(Script s, PathTile[] pathtiles, int maxRandom); // For example Path path = new Path(this, pathTiles, 2); // This will make a new Path with the Path Tiles we made before and the randomization value is 2. (So the x can vary between -2 and 2) Then we need to make our walker class Walker walker = new Walker(Script s, int doorDistance); // For example Walker walker = new Walker(this, 2); So how do we combine these things? Because it doesn't glitch on breaks you should use states. if (State.START_WALK) { path.start(); } if (State.IS_WALKING) { walker.walkPath(path); } // For the IS_WALKING state you can use path.isWalking(); // For the START_WALK state you could use an area for example. If you want to draw the debug paint then put this in your onPaint: //Make walker and your path public/private/protected public void onPaint(Graphics g) { this.walker.drawDebug(g, this.path); } If you want to draw the path on screen then put this in your onPaint: public void onPaint(Graphics g) { this.walker.drawPath(g, this.path, Color.CYAN, Color.RED); } If you don't understand it watch this very basic implementation video: --Updating Changelog; ---------------V1.2--------------- Added Walker.recover(); It will try to find the closest PathTile of the last path and start walking from there. Useful to put in your Idle state (where nothing happens so your bot is stuck) ---------------V1.1--------------- Added drawPath(Graphics g, Path p, Color c1, Color c2) - Credits to jelknab Added doorDistance to the Walker constructor: Walker w = new Walker(Script s, int doorDistance) : if doorDistance is 0 then it won't detect doors! Changed the randomization, the path will be randomized when you use Path.start() and not when getting new points. Source is now in the Walker folder. ---------------V1.0--------------- Release Download V1.2: http://uppit.com/8vp0h4o867xc/AIOWalker.jar Source (Pastebin) V1.2: Path.java: http://pastebin.com/hcUjnafE PathTile.java: http://pastebin.com/4FB7nqYk Walker.java: http://pastebin.com/37tjiZ4g Download V1.1: http://uppit.com/vwqn9srba1k1/AIOWalker.jar Source (Pastebin) V1.1: Path.java: http://pastebin.com/hcUjnafE PathTile.java: http://pastebin.com/4FB7nqYk Walker.java: http://pastebin.com/60M51rcu Download V1.0: http://uppit.com/tlub9ozv2t3o/AIOWalker.jar Source (Pastebin) V1.0: Path.java: http://pastebin.com/y7GdDZLG PathTile.java: http://pastebin.com/VBK0cTnR Walker.java: http://pastebin.com/FV013cG9