Leaderboard

Dear community, We want to give you a heads up on OSBot 2. Over the past couple of weeks we ran into many problems with JavaFX. It turned out that JavaFX isn't mature enough for the job we are trying to pull off with it for OSBot 2. It made us decide to convert the GUI back to Java Swing. With this being worked on and almost being finished, you might be wondering what has been done and what is still left to do. I'll try to make an overview of the features in OSBot 2, both already implemented ones and ones that are still to be finished up. Green is finished, orange is not completed yet but nearly finished and red is not started on but planned. Asynchronous Script Engine (ASE). OSBot 2 has a new script engine. This engine is based on tasks that can be executed after events are being triggered, or tasks within tasks. The scripter has full control whether to keep newly created tasks to be executed within the task it's executed from, or dispatch the event to the engine which will execute the task asynchronously. The engine will take care of several multi-threading issues by itself and won't allow you to execute two tasks asynchronously that both use the keyboard, or the mouse. If not explicitly defined what mode to run tasks in, tasks that are executed from within tasks will be executed sequentially in the same thread. Scripters can however explicitly define to execute tasks from within a task that will be dispatched to the engine to be executed asynchronously. This gives a lot of control to scripters to perform logic on different levels where this is possible, for example mouse and keyboard control at the same time, or a background process listening to events that can be used to interrupt other tasks if necessary. This engine is ready and we have not found any bugs in it so far. OSBot 1 Script Converter (OS1C). OSBot 2 has full capability to transform OSBot 1 scripts to run on the OSBot 2 engine. The engine contains a skeleton for the OSBot 1 logic, which is wrapped into the OSBot 2 classes and adapted to use the OSBot 2 equivalent methods and classes. A transformer transforms the bytecode of the original scripts to match the skeleton, which can then be wrapped into the OSBot 2 logic. The logic of the scripts are then executed as blocking tasks within the ASE, benefiting of the improved power OSBot 2 has to offer. Injection, Wrapper and Callback system. The OSBot 2 injection is far more intelligent than its previous OSBot 1 counterpart. First of all it is designed to be completely undetectable by any sort of classpath check, if this would ever be implemented by Jagex (which would be a very efficient way of detecting bots). Doing this at loader level is much smarter than having to create a work around later which would be far less convenient. The injection system allows for far more efficient wrapping of the client hooks, lowering the amount of CPU and resources being used compared to the system in OSBot 1. Another improvement that was allowed by this new system is the way callbacks work. Callbacks now use significantly less resources and CPU. Client Synchronization. OSBot 2 is synchronized far more with the OSRS client. Where in OSBot 1 some things would be done out of synch with the loop cycle of the OSRS client, in OSBot 2 we have made sure they will communicate at the correct moment for caching or accessing data required by the OSBot 2 client. This means data is precise and accurate. Tab Monitors. You won't have to worry about monitoring your tabs anymore. Each tab is now represented by a miniature of the OSRS client image on the right side of the OSBot 2 client. With it you see information what account is logged in to it. On top of that, you have a screen where you can monitor all your tabs with larger images, approximately half the size of the original client per tab. Another thing we introduce, is rename-able bot tabs. There is still some work needed to complete on the GUI part of this, as we converted back to Java Swing. Separated Tab Consoles. Where is OSBot 1 you had 1 console with output from all your bots and on top of that the output of the OSBot 1 client itself, in OSBot 2 you will be confronted with separated consoles. One for the OSBot 2 client's output and one for each tab you are running. This will simplify tracking down problems or gathering much needed information. There is still some work needed to complete on the GUI part of this, as we converted back to Java Swing. OSBot 1's resemblance in OSBot 2. As you can understand we have kept all features in OSBot 1, but most of them have been rewritten or improved along the lines. The big difference with OSBot 1 is that the old features of OSBot 1 are now available within the ASE of OSBot 2. On top of that, the API presents more ready to go features that you won't have to write yourself anymore. API. The API has gotten a big overhaul in OSBot 2. Where the OSBot 1 API was written without a proper design in mind, the OSBot 2 API has been designed with great care. There is still work to be done to the API, but in terms of organization it's done. The API, as is the entire OSBot 2 structure, is very generic and very clean. Everything is separated in categories and all features are correctly divided amongst those categories. Besides that, the API contains way more conditional work, improved and new features. The API should be finished after this weekend. Bot Scheduler. OSBot 2 has a plan for a bot scheduler. This basically means you can setup a schedule for an x amount of tabs and schedule scripts in there attached to accounts. You can save this and load this, where all the work of opening the tabs etc will be done for you. You can schedule different accounts on different tabs, breaks etc. This can all be configured dynamically, meaning that if possible the scheduler will move one account to a different tab at randomized timing if preferred, to randomize the schedule. SDN. For OSBot 2 we have a new webpage for free scripts with SDN integration. You will be able to add and remove free scripts to your collection. For paid scripts, the old systems will still be used, however this might be changed in the future too. Another feature for the future might be paid script trials, where people could try out scripts for an hour. Security Manager. The security manager will be a feature that will block any file writes or reads to files outside the allowed directories, which will be the OSBot folder in your home directory. Further more the manager will block any use of reflection, bytecode analyzation tools (which would also be detected in the SDN verification process anyways) and access to the command line. This will effectively create a near 100% safe solution to prevent any malicious code being executed in scripts, especially when you know all scripts in the SDN are verified anyways. Other things that still have to be done. The OSBot 2 client still needs to get server and SDN integration. This is something that can be copied from the OSBot 1 client for the most part, however we have some changes made to the SDN system as mentioned above where we need to create some new code for. And now, after writing this giant wall of code I'm going back to my editor and pump out more code. Stay tuned, OSBot.org Edit 1: User Behaviour Profiles ANTI-BAN. For OSBot 2 we have been mind mapping what we can do to make two players, running the same script, behave in different ways. We will not openly discuss what aspects we have thought of and how we will implement this. But what we can do, is tell you that we have gathered towards 20 different aspects, that can safely be randomized and stored in a user profile. This means the chances that you will bot in the same way as another user, even though you use the same script, are very small. This system is something we wanted for a very long time but never got started to be written. WIth OSBot 2 being designed a lot more generically, we can implement this system even though most of the code for OSBot 2 is done, without too much extra effort. Bot Proxy Configuration. This will make a lot of people who use multiple accounts very happy. For each bot tab (you will be able to open them in a different way than usual) you can specify a proxy server configuration. This is something that is also going to be implemented in the Bot Scheduler, making your life very easy. Hiding behind proxies can save your accounts if you are running a farm.

So I've done some research from the last 10 days of report of peoples clients crashing, this is the table I got: (Since 1st jan basically) FREE MEMBERS VIP SPONSOR 6 1 1 4 5 1 1 1 1 3 5 2 2 2 Total 28 7 0 From what I've' concluded... this issue seems to be happening majority of the time to free members. From that conduct, I have also seen approx 4 comments from VIP members saying once they gained VIP, they have stopped having these crashing problems, which gets me thinking, what do VIP/Sponsors have that normal members don't? Only thing that ticked my mind was adverts. Discuss.

Edited the first page with 2 features I forgot to add. User Behaviour Profiles ANTI-BAN. For OSBot 2 we have been mind mapping what we can do to make two players, running the same script, behave in different ways. We will not openly discuss what aspects we have thought of and how we will implement this. But what we can do, is tell you that we have gathered towards 20 different aspects, that can safely be randomized and stored in a user profile. This means the chances that you will bot in the same way as another user, even though you use the same script, are very small. This system is something we wanted for a very long time but never got started to be written. WIth OSBot 2 being designed a lot more generically, we can implement this system even though most of the code for OSBot 2 is done, without too much extra effort. Bot Proxy Configuration. This will make a lot of people who use multiple accounts very happy. For each bot tab (you will be able to open them in a different way than usual) you can specify a proxy server configuration. This is something that is also going to be implemented in the Bot Scheduler, making your life very easy. Hiding behind proxies can save your accounts if you are running a farm.

You are getting banned for clearly lying. You were on the skype that is the only ip that has been on that skype and your Osbot account. Pay him back or you will be banned and lose access to the bot. Stop lying you have been matched 100%

I like to examine random stuff when I play.. So you could probably add that

Two instances that you are using osbot.paul not 0sbot.paul You are clearly lying, also I have checked the ip that is using the skype osbot.paul and it is a 100% match to yours. Therefore you will be forced to pay back within 24 hours or you will be banned, which means you lose your VIP + all your scripts and have no access to the bot. Next time don't scam a few pixels that you can gain by using our bot within a few days. Also he doesn't need proof he is talking to you, when I matched the ip 100% that it is you.

I created this since I had to make many small paths that I couldn't well use with a map; hope someone finds some use in it Download: http://up.ht/1gqZhyG Notes: -It will automatically copy the code to your clipboard -It will also print it out in log Yea just put in the tile distance (I usually use 5 it seems to work well for walking long distances). Source if you want it package com.zscripz; import java.awt.Toolkit; import java.awt.datatransfer.Clipboard; import java.awt.datatransfer.StringSelection; import java.util.ArrayList; import org.osbot.script.Script; import org.osbot.script.ScriptManifest; import org.osbot.script.rs2.map.Position; @ScriptManifest(name = "zWalker", author = "zScripz", version = 1.0, info="Creates a path based on tile distance") public class Walker extends Script { ArrayList<Position> posList = new ArrayList<>(); Gui gui; Position control; public void onStart(){ gui = new Gui(); gui.frame.setVisible(true); control = client.getMyPlayer().getPosition(); } public int onLoop() throws InterruptedException{ if (!gui.textField.getText().equals("")) { if (distance(control) >= gui.getTileDistance()) { control = client.getMyPlayer().getPosition(); posList.add(client.getMyPlayer().getPosition()); log("Position added!"); } } return 0; } public String convertPos(Position p) { return "(" + p.getX() + "," + p.getY() + "," + p.getZ() + ")" + ", "; } public void onExit() { StringBuilder sB = new StringBuilder(); sB.append("Position[] path = new Position[] { "); for(int i = 0; i < posList.size(); i++) { sB.append("new Position" + convertPos(posList.get(i))); } sB.append(" };"); String myString = sB.toString(); StringSelection stringSelection = new StringSelection (myString); Clipboard clpbrd = Toolkit.getDefaultToolkit().getSystemClipboard(); clpbrd.setContents (stringSelection, null); log("Text copied to clipboard!"); log(sB.toString()); gui.frame.dispose(); } }

wow maldesto reply so much fame wow nope.

its so plane its just horrible

i support op 4 ban

Sell rsgp noob.........

I am currently working on fixing this up and will pm you Maldesto when I'm satisfied with how it runs

Was not abuse. Aussies rule!

All online.... O_o

the chance of getting banned is lower if you stay logged out

I'll start us off. I think the world is better off without religion. Religion clouds judgement, and directly shapes peoples perception of the world. There is no greater sin in my mind then directly influencing how people think to such a massive extent. Also taking a look back on the past and present, Lots of wars, genocides, etc all stem around religion. I think it's the one thing that keeps people divided instead of coming together in peace. ​I have nothing against religion this is just my view. What do you all think??? Please leave a reason to why you voted the way you did.

Wondering if anyone here is actually in the military! Post your branch if so !

Fucks sexy bitches all day erry'day.

Run around in circles and panic

tbh. Didn't know I had all these, till I looked deep in my old rs-classic folder.. some pictures were on rs-classic bots. lol sts leosleeper

I suggest since its your first few graphics you should prob start off free. We need to see how well you work

Started! Will be done in like 30 minutes.

I considered that into the count, but even still, the fact that many VIP/Sponsor members, including yourself and myself, have stated that when they had VIP/Sponsor, this problem never occurred, so it wouldn't really matter about the balance thing.

Oh, so not for quite a while still Oh well, better working then shit Jagex always has won, always will win...

You know how many people use OSBot, when the bot drops for 10 minutes and the worlds drop dramatically. Went from 30 players on the f2p to 4.

Lol i know,but yeah who wouldn't try to make a deal for him self. But still no bids i see, ill give this a few days and then ill delete this thread.

Bump<3

Closing this before terrible rumors/false information gets spread (as they tend to about those files). To answer your question - removing the cached files on your computer will not affect your chances of a ban.

v1.3.0 has been pushed to the SDN v1.3.0 -Re-release! -Fixed error with the bot not entering the coin amount -Updated banking to be smoother -Behind the scenes GUI update to prevent it from occasionally randomly glitching

Spinning flax into bowstring is a good method. You can profit as well.

I spun flax. do some nmz and use your points on flax and spin into bowstring. I got 10-77 within a day and a half. this will also make your money back from buying ppots etc. I suggest you use nexile spinner good luck!

What's your skype? I'm interesting in working out some sort of deal with you . my skype is i0wn4days the 0 is a zero

Try se7ensins they might still have lobbies for it!

skype: Dikkezak

TWC is permanent unless you can gather 100 Feedback to show your legitimacy. If you do not participate in the market anymore that's tough luck.

Another bot (not saying the name obviously) has been proven to be 99% undetectable mainly because of it's "user" type approach. Each account is given its own personal "game-play" which is basically just randomized things that make up each persons bot. For example when one person runs scripts they may notice their bot likes to right click things a lot and move the mouse off screen, while another is somewhat retarded and does weird loopy mouse movements. Oh and like @Pseudo said, do NOT add in an auto talker. There are so many ways to trick these things its ridiculous, in the end it would just make the person botting more obvious.

Need to make a system that can automatically switch between scripts, fishing for an hour then woodcutting for two. That will throw them off a bit.

nice site

Just waiting on Alek. This isn't to say he's slacking AT ALL. He's working hard to get a LOT of SDN upload requests processed, and is prioritising premium scripts so please just wait a few more days

auto log out if teled in other spot

why did i saw that coming? why did i saw that coming? him scamming everyone oh and next one will be B2b

70 Strenght 1 attack 1 defence, mithril gloves interested?

.. Don't leave your assignments till last minute then mope on a botting forum for help.. sheesh -_- Rule #1 of school.

Please don't post if you have no clue of what you are talking about

bump Bringing it back

I would love to see an energy potion update. The bot will drink a single dose of a (4) energy potion, and then store it in the bank and take out another (4) potion. If I start with 5k (4) energy pots, I'll finish with 1k (1)s, 1k (2)s, and 1k (3)s.

Jagex's Banned User Appeal Center