Maxi

Dear community, With the new orbs introduced, I will have to reverse engineer the new calculations used for minimap walking. In the meanwhile, go out and have some fun. Edit: All should be fine again. Make sure you download 1.7.68 here: http:/www.osbot.org Sincerely, OSBot.org

You should know by seeing this that the enums LoginStage and LoginState are declared in the Client class. Their respective fields are as well. So I'm not really sure what you said. I suggest you start looking in the MethodProvider, which is the base for your script, the API and events.

This is possible in OSBot 1 with random behaviour hooks.

Dear community, We have decided that we would give you a preview of the OSBot 2 API by providing the java documentation to you. This should give you an idea of how the OSBot 2 API is structured. Note that the API is not finished and unfinished features are not included in this preview. You can find the preview here: http://www.osbot.org/osbot2_api_preview/ As is OSBot 1, the root of the scripts is the MethodProvider which is located in the org.osbot.script package. Have fun reading it, OSBot.org

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.

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.

Fixed. Closing this.

Dear community, This release contains the fix for the walking. The download can be found here: http://www.osbot.org Sincerely, OSBot.org

Updated the first post.

Dear community, Make sure you close your OSBot client and restart it if you haven't done so since the update 10 minutes ago. Edit: It appears Jagex has changed the tile walking flags, I'll have to reverse engineer the client's walking methods to find out if this is the case. Edit 2: It seems like Jagex has removed client sided pathfinding. I'll have to some more research to verify this is correct for sure. Will update this post. Edit 3: Everything is fixed and resolved now. Make sure you download BETA v1.7.66 which contains the fix for walking. Sincerely, OSBot.org

It is. I'll look into swarms today. We'll post an update on it today. Should be both. Will be looking into evil twin today if I come across the random.

Dear community, In this release I have fixed several bugs that I came across whilst running OSBot 1 in the background while testing/working on OSBot 2. I'll work on some more fixes tomorrow. A bug with bank scrolling and withdrawing has been fixed. Multiple randoms received some changes and updates. Several other glitches. Download can be found here: http://www.osbot.org/ Sincerely, OSBot.org

The main focus at this moment for OSBot 2 lies in making sure we have organized and covered every part of the planned API. The moment we release we can't refactor existing code anymore. Because we want OSBot 2 to have a very intuitive API, besides the performance gains, we are making sure we are not missing anything.

Dear community, The download for BETA v1.7.64 is available for download. This should fix an issue for some users who were not able to get the OSRS client downloaded. The OSBot 2 API has been getting many updates, we hope to finish this up soon. Sincerely, OSBot.org

You have received your refund: member_id: 64121 old_credit: 0.0 new_credit: 8.091000000000001 That's your refund. You can see your store credit here: http://osbot.org/forum/index.php?app=nexus&module=clients&section=payouts

I must have missed Insane Minotaurs as the package didn't exist in the database anymore. I'll have to ask the SDN managers when this was removed and why to see what will happen with those. I'll let you know. Edit: I have retrieved the id's for this package. I don't know where this package was lost or removed, although I decided I would refund it as well straight away.

Dear community, As promised 3 days ago we would refund everyone who ever bought any of the Insane scripts. More information about this can be found in this thread: http://osbot.org/forum/topic/27268-5uck-malicious-content-report/ I said it would have been done in 2 days, unfortunately I found out the second day that the IP.Board Nexus system doesn't support mass refunds for packages. So today I had to write a little custom tool that would communicate with the database directly to do this job for us. I can happily announce that all customers have been refunded with store credit now. In total 634 purchases have been refunded. You can see your account credit by going http://osbot.org/forum/store/ and looking on the right hand or here http://osbot.org/forum/index.php?app=nexus&module=clients&section=payouts Edit: Apparently I missed out on the Insane Minotaurs refunds. I have refunded those as well. In total there were 41 refunds of those, so in total 675 refunds have been made. Yours sincerely, OSBot.org

We want to complete the OSBot 2 API with all the features and new techniques for hand in the OSBot 2 engine before we release. And of course we want to have OSBot 2 tested on multiple systems to make sure there are no hidden flaws that can only be spotted when ran on multiple different systems.

I will be handling the refunds as we speak. Edit: It will take a couple of hours to process every sale of each script developed by 5uck.

Please follow the instructions given in the announcement and you should be fine.

They were always checked, with the exception of 3 scripters and 5uck was added to that list when he received global mod.

The virus does hide elsewhere. The best way is to run a virus scan to help make sure that there are no remaining traces.

Everyone who has the script in their collection will get refunded. This means that you will get refunded as well.

This will be found by Kasperky, NOD32, Avast and a couple of other AV's.

Dear community, Earlier yesterday and today 5uck has spread malicious content through one of his scripts, the Insane Druids script, for a total amount of 12 hours. We removed access to the scripts immediately after finding out. Most of the scripts at OSBot need to be validated before they are updated, which means the contents of the code are inspected before approved to be sent to the users. In this case, 5uck was given a position with more responsibility and the contents of his script were allowed to be auto updated (due to his former rank of global moderator). This means his scripts didn't require staff approval. He has put malicious content in the Insane Druids script but luckily we caught up on this fast, thanks to one of our previous administrators Raflesia. We have disabled all his scripts for the time being in the SDN. We have taken action by contacting the hosting provider of the malicious application and asked for further action against the user who uploaded it. Furthermore, we are reverse engineering the application to tell you exactly what malicious practices are run by it. We are very touched by this. This was the reason why we had pre-approvals of script contents in the first place, something for the better of the community. It meant updates sometimes had to wait for a couple of days, but in the end a secure solution. We gave in to giving some people trust, giving them the ability to control updating of their own scripts. This trust has been broken today. But before I continue on this matter, I want to provide you (the users of the Insane Druids script) with some steps to get rid of this malicious content. Please note that you have only been infected if you ran the script yesterday or today. I also URGE you to change your passwords, but AFTER doing the next few steps and reading some information: Download the anti virus software called Kaspersky. Scan your computer, remove and/or quarantaine any infections found. By now you probably know what you are going to do. Restart your computer and come back to this thread. You have restarted your computer. Change your passwords now. You are done and safe again. 5uck has abused his privileges. He did this to get access and rob you from your private information. It has made us see that even though some developers we 'think' we trust can't be trusted. We have decided that we will take away any auto-update privileges from anyone (only 3 others had such privileges). We can say that only a hand full of people got infected and hope to have informed you well enough and stay safe. We will be refunding anyone who bought any of his scripts with account credit within the next 2 days. We are sorry for the inconvenience and hope we can satisfy the customers with this refund. Please note: the refunds will occur automatically, there is nothing you have to do for this to happen. It will take some time for IP.Board to process all the refunds though. 5uck has been banned and will not be associated with OSBot any longer. Sincerely, OSBot.org P.S. On a side note, there were some problems with the web server hosting the website in the last couple of hours. These issues have should be resolved. P.S.S. I accidentally typed Insane Fletcher but I meant Insane Druids, I fixed it in the post.