Maxi

Dear community, Sorry for the delay in updating equipment last week. I will make sure the fix will be made and uploaded today. Other updates required caused by todays update will be included as well. Sincerely, Maxi & the OSBot team

It sounds funny when you put it like that. I don't think this will affect many scripts, but in order to have those methods working properly they needed to have a interrupted exception clause in the method signatures, which might cause some script to face problems. Essentially it should be a 2 second job to update this for script writers if their script is affected by this which really depends on whether they have those methods running in blocks that don't throw/account for interrupted exceptions.

Dear community, This patch contains fixes for banking and equipment. Developers please note that the equipment patch may cause your scripts having errors, we have had to implement some behaviour in the equipment methods that throw Interrupted exceptions, however you might not be catching those in your scripts. I'll make a note of this in the scripters section and the SDN administrators have been notified, please update your scripts as soon as possible. Download can be found here: http://osbot.org/get/index.php Sincerely, Maxi

Dear community, The hooks have been updated for this release and after closing your OSBot client and restart it you should be able to continue using OSBot. Sincerely, Maxi

My username says Maxi though ;).

Dear community, I wanted to give you an update on my personal life. As some of you might have read that the father of my partner in life was diagnosed with cancer in a terminal stage I wanted to share the news that her mother was also diagnosed with cancer, however in a less severe stage. Luckily the dust has settled and we both have found structure again and have an idea how to deal with this terrible news. The past two weeks I've spent in the hospital mostly and in her parents house helping out with cleaning and cooking diner. We have made arrangements for people who will help out with health care of her parents and cooking/cleaning. This will release some stress and pressure so she can focus on spending time with her parents and I can continue living my life of which working on OSBot is part of. With the latest plans for OSBot 2 we plan on having a steady platform for OSBot 2 soon enough in which we can involve the community more. Sincerely, Maxi

Dear community, Two days ago my partner in life received the news that her father is terminally ill. He was diagnosed with cancer that is already in the stage where it has spread. I'll try my best to keep working on OSBot 2 and right now release an update for the revision update 42 that Jagex made yesterday. Sincerely, Maxi

I'm sorry for the confusion. The GUI is misleading, currently this release is only accessible for developers for testing purposes.

I'll upload the latest hooks file and restart the server to use it. Edit: done.

Edited the main post, the download link was the wrong one. Should be the correct one now.

Dear community, As expected but not hoped, parts of the security manager having to do with internet connections cause problems for some. For now I have built a version without all features of the manager enabled to make sure you can all run it. All major updates in this update are listed in the release thread of v2.0.11-12. The download to the jar can be found here: http://osbot.org/osbot2_beta/OSBot-packed-2.0.14.jar The javadocs can be found here: http://osbot.org/osbot2_api/ The javadocs zip file can be found here: http://osbot.org/osb...api/javadoc.zip Sincerely, OSBot.org

I'm looking forward for more of these, we'll need them to hammer down the security manager. However it's odd that your system says it wants to have read and write access to ALL properties.

Dear community, In this release the accessors of the bot have been made public. The accessors have always been protected from access by developers because they would allow for unprotected access to RS username and password information if made public. I've revisited the thought on how to open up the accessors publicly without losing security and created a system that will open up the accessors but block any access to the password and username information. This is part of the promised security manager. Not only that has been done, OSBot 2 no longer allows using reflection. This together combines more freedom to the developers, as they can now freely access accessor methods without reflection, and more security as reflection can no longer be used. Opening up the accessors also allowed me to clean up the amount of deprecated methods in certain accessor wrappers, cleaning up the API significantly for developers. However this has made some changes to the API that developers should take a note of: client.getRegion() has been removed. It can now be found in Map.getRegion() and most of its features are now available in Map and no more in the Region class client.getEntitiesOnCursor() has been removed because it's available in mouse.getEntitiesOnCursor() client.getMapBaseX/Y() have been removed because it's available in map.getBaseX() and map.getBaseY() ; also note that map.getMapBaseX/Y() are refactored to getBaseX/Y() Region.getTiles() added Region.getObjects() added ; note that these are accessors of the client its objects, not the wrapped RS2Object instances Client.getPlane() has been removed because its functionality can be found in the Map api class Client.getMyPlayer() has been removed because its functionality is already provided in MethodProvider Client.getLocalPlayer() has been removed because its functionality is already provided in the Players api class Client.getLocalNPC() has been removed because its functionality is already provided in the Players api class Client.getLocalPlayers() has been removed because its functionality is already provided in the Players api class Client.getLocalNPCS() has been removed because its functionality is already provided in the NPCS api class Client.getClippingPlanes() has been removed because its functionality is now available in the Region class Client.getMenuX() has been removed because its functionality is now available in the menu api class Client.getMenuY() has been removed because its functionality is now available in the menu api class Client.getMenuWidth() has been removed because its functionality is now available in the menu api class Client.getMenuHeight() has been removed because its functionality is now available in the menu api class Client.getMenu() has been removed because its functionality is now available in the menu api class Client.getOnCursorCount() has been removed because its functionality is now available in the mouse api class Client.getMenuCount() has been removed because its functionality is now available in the menu api class Client.isMenuOpen() has been removed because its functionality is now available in the menu api class Client.getCameraYaw() has been removed because its functionality is now available by using the Client accessor instance Client.getCameraPitch() has been removed because its functionality is now available by using the Client accessor instance Client.getDestination() has been removed because its functionality is available in the map api class Client.getMinimapX() has been removed because its functionality is now available by using the Client accessor instance Client.getMinimapRotation() has been removed because its functionality is now available by using the Client accessor instance Client.getMinimapZoom() has been removed because its functionality is now available by using the Client accessor instance Client.isMinimapLocked() has been removed because its functionality is now available in the Map api class Client.getInterface() has been removed because its functionality is available in the Interface api class Client.getRawInterfaces() has been removed because its functionality is available by using the Client accessor instance Client.getValidInterfaces() has been removed because its functionality is available by using the Client accessor instance Client.getRunEnergy() has been removed because its functionality is available in the Settings api class Client.getLevelExperience() been removed because its functionality is available through the Client accessor instance Client.getLevelStat() been removed because its functionality is available through the Client accessor instnace Client.getCurrentLevelStat() has been removed because its functionality is available through the Client accessor instance Client.getVertexHeights() has been removed because its functionality is available through the Client accessor instance On top of the changes mentioned above the following update were made: Inventory.isItemSelected() - returns whether an item is selected Inventory.getSelectedItemName() - gets the name of the selected item Magic.isSpellSelected() - returns whether a spell is selected Magic.getSelectedSpellName() - gets the name of the selected spell Client.getCrossHairColor() - gets the state of the mouse cross hair / cursor (0 = not present, 1 = yellow, 2 = red) The anti ban roll with not happen if human input is enabled whilst running a script Bank.withdraw(X value) and bank.deposit(X value) will now use the last used X value if possible and have now detection for changed enter X value interfaces Character.isUnderAttack() is now fully functional (see the documentation) Character.isAttackable() method added, taking in to account multi and single combat zones Extended the ConditionalSleep class to support for custom sleeping times (see the documentation) Fixed the bug with the InteractionEvent for interacting with entities where it wouldn't do anything while having either a magic spell or inventory item selected. It now automatically accounts for selection, no different user input required Ported over a fix for interfaces from OSBot 1 Ported over dynamic prayer button identification from OSBot 1 The RandomSolver system uses id's again for now, this might be changed to enums later. This allowed for adding the random behaviour hook system back with some fixes Added back the WorldHopper class Your mouse will now exit the screen when pausing or stopping a script Settings.setRunning() now uses the orb to activate or deactivate running Prayers have been updated to use the new config Two freezing bugs that existed in OSBot 1 previously as well have been fixed Made certain interactions faster and fixed a bug in the walking event that caused delays sometimes The GUI for opening and closing tabs is now faster and more responsive as the majority of cpu intensive actions are not separated from the GUI threads Added coloring of the bot tab that is active and also all tabs now display your character's display name if logged in The Interfaces.containgSprite() methods have been fixed to account for sub sub interfaces (basically children on child interfaces) World selection and interface value debugging have been added back and can be found in the quick right click menu on the settings button I also did some work on the updater which had broken identifiers for a set of hooks which we would adjust manually for the past few revisions and I introduced a couple of new hooks: isItemSelected, selectedItemName, isSpellSelected, selectedSpellName and crossHairColor. But..... last and certainly not least: Security Manager. The Security Manager is in place in this release. It could cause issues as it has not been tested on a wider variety of systems, but we will be able to figure this out with your help. If it's the case that too many people run into problems, we will release a version without it in place and ask more experienced users to share the thrown security exceptions with us. In summary the Security Manager restricts the access of the OSBot 2 client in several places: Reflection to access hidden fields is no longer possible Execution of commands on the command line is no longer possible Access to most internet connections are now locked down. We will white list trusted IP's, but for now only imgur, our server and the RS servers are allowed to make a connection. For people who want to keep track of signature data, we will introduce an easy to use system that will forward any requested data to your server. The above doesn't summarize everything as there is more, but it should give you a general idea. The download to the jar can be found here: http://osbot.org/osbot2_beta/OSBot-packed-2.0.12.jar The javadocs can be found here: http://osbot.org/osbot2_api/ The javadocs zip file can be found here: http://osbot.org/osbot2_api/javadoc.zip Expect significant work on the random handlers this next week! Sincerely, The OSBot team

Dear community, Sorry for another release but I only realized just now that most combat scripts don't have a random behavior hook for the Run Away From Combat random handler (which they should!). Therefore the changes I made to the handler were causing problems for all combat scripts, I have reverted those changes. The download can be found here: http://www.osbot.org Sincerely, OSBot.org

Dear community, In this release you will find the following changes: Dynamic methods to find prayer interface childs. This fixes interacting with the prayer buttons and because it's dynamic it won't break again. Some other methods that interact with interface childs have been rewritten to use dynamic methods to identify the childs to prevent them from breaking. The download can be found here: http://www.osbot.org Sincerely, OSBot.org

Dear community, In this release the following issues regarding OSBot 1 have been tackled: Login for high risk worlds Freezing random event engine related to hopping A change to gaussian distributions so they are capped and can't produce the VERY rare exceptions and thus bugs The isUnderAttack methods is now no longer just a logout timer. If nothing is facing you, it won't tell you that you're in combat. If something is facing you, it will check the actual logout timer. The above is implemented into the Run Away From Combat anti-random handler Both Login and Welcome Screen randoms have gotten an overhaul and work better The World Hopper should now have no more bugs All randoms that need a canReach() check now actually have it implemented Download for this version can be found here: http://www.osbot.org I know I should be focusing on OSBot 2, but on the other hand some of those fixes were a necessity. Sincerely, OSBot.org

It comes close to it (not completely though) and with the exception that it is dynamic. Your situation might occur once, but it would be dynamic, thus different the next time. For example maybe left of the first two three lava pools, perhaps right of the last big one (starting bottom left).

We can make legacy scripts use this if we want yes. I'm most likely releasing this in OSBot 1 as well.

Dear community, We have a new pathing algorithm that is ready for OSBot 2. One of the most common bot detection techniques that we know of by reading papers about bot detection within games like World of Warcraft is tile hotspot detection. In summary tile hotspot detection is the act of storing tile clicks and from those clicks find out that bots usually tend to click the same tiles when traversing from A to B. The tiles are different every time you walk the path from A to B, but the path remains the same which means the tiles of the path become hotspots. Scripts with little differentiation most likely end up with walking from A to B by using for example area's, which slightly spread the tile clicks because the paths are slightly different, but they end up around a certain threshold regardless. This is very easy to monitor by a program, simply storing tile clicks on the servers of Jagex and process them to see if there is a recurring pattern in tile clicks. It doesn't take much computational power and is quite exact when it comes to identifying bots. Humans on the other hand tend to randomize their clicks far better, not because they do it on purpose, but we're human and can't click with bot precision and don't always judge correctly what is the shortest path from A to B. We know this way of detection is/was used in World of Warcraft. I haven't done any research into what World of Warcraft bots have done to mimic humanlike pathing, I haven't been able to find this information, most likely because of the fact they like to keep their magic tricks secret. This new pathing algorithm tackles this way of detection. Chances you will walk the exact same path from A to B are very small and this isn't just done by taking the path from A to B and differentiate around the tiles in the path. This would essentially still give easily detectable hotspots, with the only difference that instead of one path they are evenly distributed around the path. It constructs a giant shape which can be traversed and will make sure that it won't exceed a certain threshold of length compared to the shortest path, making sure it doesn't become utterly stupid or inefficient. Sincerely, OSBot.org

I don't see anything new there. Either it's planned to be developed, it already exists or you're giving very little information about your 'good' ideas. If anything, we would outsource development of features that we don't have time for or want to have faster. So your whole merge idea is something I don't understand. What exactly would you be bringing to the table? On another note, we don't condone ANY black hat activities at OSBot. It's NOT 'cool' or 'fun'. We can continue this conversation via Skype.

Everything is back to normal.

The server has been restarted a minute ago again, you should be fine within a minute.

Sorry, but I must ban you now.

Dear community, This release contains a dynamic method for calculating the enter amount interface, used for example in banking with the X-option. This will make sure it won't break again and if it does, the client will send you messages in the log that it's broken. Download can be found here: http://osbot.org Sincerely, OSBot.org

I'll update this. Edit: I've written a dynamic identifier for the child id. Uploading it in some minutes.