Maxi

What happens if you tickle your model and/or interface debug button on and off (keeping it on for like a second)?

Zach, Laz and Kati use Windows like all of you.

Are you running v1.3.1?

I don't see a problem here either:

I just realized Laz did not push his git with the fixed hooks. We'll push the update when he comes back.

It should be faster than ever, not the other way around :p. It is for me, Zach, Laz and a lot of others. Try and reload.

I can't see how it's broken. It types in strings fine.

That's obviously a script error, not an error in our code.

We are glad to announce that BETA v1.3.1 has been released! We have been hard at work optimizing, stabilizing and fixing bugs inside the bot client. We have accomplished the following things in v1.3.1: Improved memory usage. Currently, our tests show that memory usage ranges from approximately 130MB to 200MB whilst running OSBot with 1 script. Obviously, this depends on the situation. In either case, this is a significant reduction from the crazy numbers we would sometimes get in the past, reaching up to 700-800MB. A completely redesigned threading/concurrency system that has shown significant promise and improvements in overall stability. Improved CPU usage. The bot now creates a lower CPU footprint. Of the amount of CPU time the entire application spends including one Runescape client, only around 6 - 10% is spent by the logic of the script/bot. The rest of the CPU time is the Runescape client itself. On my own machine, I run one bot and script with approximately 10-15% CPU. Freezes of the loop and the graphics rendering should be completely in the past now, thanks to the top notch fresh threading system. The hooks we originally had that were not working (i.e. some of the skill hooks, in combat, facing etc) should all be fixed and working now. Laz forgot to push his git so the updates are not included. We will push them once he comes back home. A fresh new GUI theme that will fix cross platform problems, i.e. make it the GUI work perfectly on Mac OSX and Linux as well. Fixed any bugs that had to do with multiple bot tabs. Multiple bot tabs work a 100% now. Slight changes to the API here and there, however due to the above updates we did not have time for the API. All together, this gives us a fresh start without stability issues. Now these are out of the way and we have a very efficient bot, we will go back to our API and randoms to make its quality match its engine it's running on. The SDN continues to be worked on, however as we are outsourcing this we can't tell an exact date for when we will have the first barebone version of it running publically. The new API documentation has been updated: http://osbot.org/api/ The new OSBot download is found here: http://osbot.org Make sure you update your Java to the latest version: http://www.java.com/en/download/manual.jsp If you experience FPS issues, make sure you run 64bit java if you have a 64bit machine! If you're one of the people experiencing FPS issues, post your machine specs (cpu, 32/64 bit, java version + 32/64bit, os etc etc) and you can still use 1.2.2. Refresh your page (CTRL + R) in case it's still showing 1.2.2. Thanks for reading, The OSBot team

The update is not available yet Pike. It will be later tonight. Once we do so, your old version won't work anymore and you will have to download the newest version. I think we need a stable bot with low resource usage first. Your random won't do a thing without it.

Hi all, I have been working since wednesday on the promised engine overhaul. I took a day to completely map out the design on paper and whiteboard, and finished it yesterday. After that Zach and I have been profiling the OSBot lots and made major adjustments to its memory usage. Whilst running a script, the entire application never goes over 200mb of memory usage anymore and after garbage collection is even drops down to 130mb. It's averaging around 150-160mb, running Peter his chicken murder (with some adjustments). I thought I would show you a picture as well. The memory usage you see, is the OSBot client, script and the Runescape client. OSBot itself without running a script or a Runescape client, uses 82mb. So you can do the math yourself ;)! This is a major improvement. The engine overhaul also got rid of any freezes and other glitches. We still have some last things to do before we can tie up our next release, but I think you will all be pleased with it. Sincerely, Maxi

Like this maybe?

A rumor came to me today: Bitwise would have said the following: We are NOT, and will NEVER work on OSBot with Discardedx2. So much for Bitwise being a fool. Please note that this post is only to avoid this rumor, not to start any flaming or controversy with vInsert. Sincerely, OSBot

Have fun with your appeal.

I have in fact tried to reproduce one of them and succeeded as of yesterday. I do have an idea now where it happens in the code, but I'll have to get a freeze again to tell for sure, because that one time I wasn't profiling unfortunately. We are on it though.

Probably in a couple of versions. Once certain important additions are made, we'll release a new version.

What are the account requirements to go there and use it? My account is very low level so I assume I won't last long. If so, I'll have to borrow an account to profile.

Well, we might as well just put it our here. We have a massive goal set once again for this week. We've done that in the past and managed to more or less meet our goals within time. We will try to do the same thing this week, however this time it feels as if it's even more and the impact of these updates will make us the best bot out there if we manage to pull it off in time. So let's get to the list: Client related goals: [*]Find the source of invalid logins / unable to login / unable to connect to Runescape. This bug happens only to a select group of users, however we want OSBot to be public to everyone [*]Find the left sources of any freezing issues. I have not encountered it myself, but will try to reproduce the bug and profile it to find its origin. It's most likely a crash of the RS client itself caused by injected callbacks. [*]Fix up the skill hooks [*]Fix up the facing uid hook so we can return the proper facing entity [*]Add facing coordinates, x and y [*]Add the character chat messages, both force chat (used for randoms and such) and regular chat (used to write an AI to talk with other players in RS in the future) [*]Add the ability to provide the walking method with a collection of Position objects to create custom selfmade paths and lower overhead [*]Add a proper enum for hitsplats [*]Add a canReach method not only for entity, which we already have, but also for arbitrary Position objects [*]Find and fix the origin of non running onLoop() methods. This has occurred to me in the past, however not after last update, so we'll once again have to reproduce and find the cause. Non client related goals: [*]Finish up the SDN portal where script developers can login to maintain, update and submit their scripts. Set up the logic on the client and server to handle access to certain scripts (like premium scripts), automatic updates on random event handlers and a secure mechanism of providing the OSBot client with premium scripts that will prevent leaking to protect the creators of the scripts [*]Randoms, like we said, we aim to have most if not all randoms with their first version updated through the SDN once it's setup After writing this list I realized we should stop writing more and put the effort into real code! Yours sincerely, OSBot.org

Yes that was the initial plan. However for some reason we have trouble with our URL rewriting and what not, so nexus (our store system) is not working 100% correct. We hope to fix this soon, that way once a payment is done the system will automatically grant access to the features related to the product.

Dear community, Over the coming days I'll be focusing on writing all the randoms I can get my hands on. There have been other community members who have been writing anti random scripts too, I want to encourage this as it would lift work load of my shoulders. However, I will try and get most if not all randoms. Randoms are important and will be the key to our community thriving. Those randoms will have to distributed and version controlled through the SDN we are currently developing. This way you will never have to update your randoms by yourself, the client will automatically take care of this for you. We hope to have the SDN finished in time so we can deploy this system for the ease of use. Also this will mean premium scripts can be made available in the future in a secure way for both developer and user. ETA on full randoms and SDN: Friday April 19'th 8 - 10 PM EDT (GMT - 4) Also please note, any donation this week would help us out a lot. We are low on cash and the development of the SDN involves money! Sincerely, Maxi

OSBot.org does not support any external downloads of the OSBot client archive anywhere besides on our own website located under the Download button here: http://osbot.org If you download OSBot from anywhere else than the mentioned download page, we can NOT guarantee its safety! For your and our safety, OSBot.org

Ok everyone, After a week where we have once again made a lot of updates and improvements, I want to take back a step for a small moment of peace and recap on the past days since the public BETA release of OSBot. It was the 5'th of April, when we decided we could no longer wait to release. Even though we knew there were going to be issues, waiting longer to release the bot would have been bad. You were all so excited to have a sneak peek of OSBot. So we just decided to release it, after all we knew we would have to do it some day and if you as a community would help us out finding issues or missing features we could improve much. And a BETA is for a reason, to get your application out there, have it tested by people in every single way imagined and use the feedback to stabilize everything to eventually release the official first final release. So, we are the 13'th op April today, just over a week after the initial BETA release. We have passed BETA v1.0.0 in private, BETA v1.0.1, BETA v1.1.2, BETA v1.1.3, BETA v1.1.6, BETA v1.2.1 and BETA v1.2.2 in public. Even though I'm on the developers side of the bot, I can feel that the bot has made significant progress in all of these updates and that we are getting closer to a version of the bot that runs with no issues for anyone, that offers a rich enough scripting API to write all of your scripts you're looking for. Furthermore, within a week or so, we will have a professional Official Script Developers portal that is linked to our repository, where developers can maintain their scripts, add new scripts and update their current scripts. And to assure safety for all users of OSBot, these new or updated scripts, will pass through a validation check which will be performed by designated programmers to check for quality and whether they don't contain any code that will harm you. We are aiming for a truly professional end result that is safe, secure, reliable, stable and easy to use! If we look back at the past week, we realized that we have put so much effort into OSBot already. Today I looked through our log and saw that we we started the project on the 2'nd of March. That is just over a month ago! And look at us, we're sitting here with an awesome community with friendly people willing to help each other out. We are proud of that, and not only should we be proud, you should be proud too because you are part of it. If we have gotten this far in just over a month, imagine where we will be at after another equally large time lap! I want to ask you to share you positive moments so far with us, either general or specific ones. Stay tuned! OSBot.org

I have noticed that the account pop up is indeed coming up very slowly. I'll look into it.

Delete and download again boss, might solve it.