Alek

In an effort to keep both botters and scripters happy after RS updates, I've decided to embark on the long and grueling process of re-writing much of the API to cache interface ids. The first class to undergo this transformation is Equipment. Please let me know if you are having any new equipment related issues! Changelog: -Added error tracking to loading SDN scripts -The follows methods are now dynamically executed (without the use of static interface values): --Equipment: isStatsOpen(), closeStats(), getInterfaceId() -Added the following methods: --Equipment: getStatsParentId(), openStats() -Deprecated: Equipment.STATS_INTERFACE_ID, Equipment.STATS_CLOSE_CHILD_ID, Equipment.INTERFACE_ID -Added values: Equipment.MAIN_INTERFACE_ID_CACHE, Equipment.STATS_INTERFACE_ID_CACHE -Added Banks: Yanille -API Documentation has been updated! Please clear your browser's cached files. Caches only have to be written to once. So for the client to remember what the interface id is for the equipment stats interface, it needs to be opened once. This will be done automatically if you call a method; for instance if you execute equipment.interact("Remove", "Staff of air"), it will cache the main interface id automatically if it hasn't already been set. After that you can stop a script, log out, start a new script, and the cached id will be saved. Happy Botting! -The OSBot Staff

We track connection failures, so your problem will be sorted out in the next version.

This was actually really good.

Try downloading the newest version.

Many members here have been getting an error message of "Unable to connect to the OSBot server" for quite some time now, so something needed to be done about it. With that said, @Zach and myself made an automatic error reporting tool. This tool allows us to send exceptions of specific methods (such as the connection methods) to the server where we can later investigate the root causes. Changelog: -Added developer error reporting tool -Added 3 new banks --Camelot, Ardougne North, Ardougne South -Various Trade API methods now dynamically grab interfaces --didOtherAcceptTrade(), acceptTrade(), declineTrade() Have fun and happy botting! -The OSBot Staff

We're sorting out the download issue. The connection issue is another thing.

As promised, today is the release of the OSBot Script Browser. This marks a new major version bringing us to the 2.3.X series. This is the first release of the browser and although I thoroughly tested it, I'm sure that somewhere along this fairly large update there is a few bugs that need to be squashed (in which case please report them here). Changelog: -Completed Script Browser -Improved script loading methods -Patched "OSBot is ready" bug -Script selector is now responsive to connections -Utilities takeScreenshot() is now available for all members -Added Utilities method openWebpage(URL url) -Added Utilities method isVIP() (Checks for OSBot VIP) -Added 3 new Banks --Falador West, Falador East, Catherby -Patched jar version checker There are a ton of scripts to browse, however a good handful may be outdated. If you come across a few of these scripts, please report them here. Happy Botting, -The OSBot Staff

Interface hooks. We're well aware of that interface problem, it's been on the books before you mentioned it. Trust me, we are looking at it when the time becomes available (it's a high priority).

This release patches the trade API as well as interface hooks which were broken from yesterday's RS update. Thanks for your patience and understanding. Changelog: -Added banks: Lumbridge Lower, Lumbridge Upper, Draynor -Interfaces updated < say thanks to @Zach -Trade API updated < thanks to and @darkxor for reporting -Further progress on script browser -Various infrastructure fixes (Zach again) I plan on re-writing a large part of the API to prevent it from breaking (as often), however this will be a long project that I embark on. If you find any other problems which still persists from the RS Update, please let me know. Sincerely, -The OSBot Staff

It's the kind of crap I have to deal with every game. I can never get a good team.

I saw an AWP double kill on here today, not to steal his/her thunder but I score at least an ace every few days. I cropped out the first kill (the time apart was too long). Sorry for potato quality, if you guys want better quality and more vids let me know.

If it isn't an awp penta it really isn't youtube worthy .

Over the last few days I've been working hard in making this script browser come to life, and hopefully after this update it will become a reality. The main purpose for this release was to finish up the server and manifest code so I have all the tools needed for completion. To make this release somewhat worth your while, I went ahead and did a pretty large revamp to PositionPolygon (now known as PolygonArea). Changelog: -Added PolygonArea -Deprecated PositionPolygon -Added PolygonAreaFilter -Added closest(PolygonArea, ids) to EntityAPI -Added closest(PolygonArea, names) to EntityAPI -Added Banks to map>constants package --Banks contains preset PolygonAreas of banks ---For instance: Banks.EDGEVILLE.contains(myPosition()) ---Banks Added: Varrock West, Edgeville, Varrock East, Al Kharid -Added contains(Entity) to PolygonArea -SDNManifest now contains category id --This will be used for the script browser categories -Additional script browser GUI modifications Expect the PolygonArea code to go under some revisions, so the API may differ on the next few releases. You are completely safe to use the new map constants however, such as Banks.AL_KHARID. Happy Botting, -The OSBot Staff

I had a feeling I was a bit older.

You're showing on the forums as a regular member.

This is a quick fix for some server changes we made yesterday. You'll notice the additional tab for the script selector, this is currently disabled from use while I perform a quality check. Changelog: -Added script browser tab -Replaced "info" from sql entry to forum thread Thanks for your patience and understanding. Sincerely, -The OSBot Staff

That's a lot of detail for a logo. It looks great but I don't know how it would scale on a website or letterhead.

Looks super cozy. I celebrate with a bottle of Jagermeister and Koven.

Thought this was pretty cool when I was on my plane back from the US to Germany.

You haven't provided a lot of info such as the versions in which the CPU spiked, the script which you are using, whether or not the CPU decreased over time, etc. We can't work magic without a little bit of information. I can show you a screenshot of OSBot on my computer only using 120MB of RAM and 7% CPU.

Have you tried the new banking method I added with the release of 2.2.43? http://osbot.org/forum/topic/62310-osbot-2243-combat-magic-and-interface-patches/ bank.withdraw(HashMap<String, Integer>);

Really getting tired of people spreading lies and then everyone accepting it as the truth. Sorry, no American First Amendment rights here.

With the release of OSBot 2 over 11 months ago, we have been working hard to assist customers in providing them with 30-day free script trials of their OSBot 1 scripts which were created for OSBot 2. Q: I paid for the script, why can't we just get the OSBot 2 version? A: There was no simple "port", meaning that scripters had to RE-WRITE the ENTIRE script. It's essentially a brand new script and therefore scripters did this out of a nicety. Q: I can't believe OSBot did this to me! How can I trust you guys won't do this again? A: The switch to OSBot 2 was a necessity and the original developers never truly expected for the original OSBot to grow as it did. In order for OSBot to scale to the point where it is today, the second version was a must. Q: I still don't understand why I can't use OSBot 1 scripts with OSBot 2, please explain? A: Consider the OSBot 1 to OSBot 2 transition similar to upgrading Windows from Windows 98 to Windows 7. A majority of the software (scripts) for Windows 98 (OSBot 1) would be incompatible with Windows 7 (OSBot 2). We weren't going to continue developing a client that needed more than a few patches, it needed the re-work. Software is supposed to develop and improve over time. If everyone wants to pay for software once and never be expected to re-purchase it, then we would still be living in a time of Netscape and AOL Instant Messenger. Q: Please stop lying, we all know OSBot 2 was released 3 months ago! A: The OSBot 2 release: We have provided more than ample time for customers to redeem their 30-day free script trial. Doing these free trials requires a fair amount of time, time which could be better utilized improving OSBot 2. We will no longer be authorizing these trials! Thanks for your time and understanding.

Sorry about this unexpected update, but we changed some server code and the way it interacts with the client. Although I wanted to release the script browser updater all at once, it looks like I'm going to give it to you guys in slow chunks. Changelog: Note: You cannot physically use these features but they are coded -Add/Remove scripts from the client -Retrieve full SDN script list from the client Thanks for your patience. Hopefully the full release will come soon. The OSBot todo list has been updated: http://osbot.org/forum/topic/61397-official-osbot-todo-list/ P.S. Say thanks to @Zach for 2.2.44 compatibility. Sincerely, -The OSBot Staff

You know the key word is PREMIUM right? Meaning scripts that you PAY for? Nothing is stopping anyone from making a free cow killer or cow milker.