Maxi

Dear users, Earlier today we experienced issues on our servers that caused multiple services to lag out. The source of the main issue has been identified, but we are further investigating as we suspect there could have been a multi-facetted issue that we have not fully identified yet. Servers seem to be stable again for now. Must any issues arise again, we are here to mitigate them as quickly as possible. Sincerely yours, The OSBot team

I wish I was as good looking as Mald.

Dear community, It has been a long search and tough decision on who we needed to continue the active development of OSBot. Several candidates were carefully reviewed and the decision was difficult to say the least. We are happy to announce that we think we have found the perfect candidate to follow up on the outstanding work that @Alek has always delivered. Without further ado, I want to present you our new developer: @Patrick A.K.A. Pat-Ji with a selfwritten introduction: The last administrative formalities are currently being taken care of and from here on out we'll be able to bring Pat-ji in to the working mix, by gradually giving him acccess to the bits and bytes of OSBot. We are really happy to have @Patrick on the team and are looking forward to his contributions to OSBot. Yours sincerely, The OSBot team

I will shortly post an update to announce our new developer. Excited :)!

Dear community, Dear Alek, As some of you may have noticed by now, Alek, our long time beloved developer, has been forced to resign his duties as he will take on a job offer as an engineer at a defense company. We are happy for Alek he was given this opportunity and want to take time to thank him in full for his service to OSBot and we are sad to see him leave. Alek came to OSBot as a script writer, writing unbreakable scripts with the passion of a young lion, eager to learn more. We, as a team, became friends with you, Alek, and you step by step became an undismissable cornerstone of OSBot. Starting out managing the SDN, stepping up your game to manage the scripters and become a developer for the bot core modules, you literally knew every part of OSBot like no other. Your endless energy to converse and communicate with community, albeit being a little explosive from time to time, you pulled one hell of a job. I can't really put to words what you mean for OSBot and this won't change in the future. I have to laugh when I think back to all the endless discussion and fights we had, all because you always wanted the very best for OSBot. Having someone who stands for his opinion is invaluable for a business to keep going forward. The greatest storyies are perhaps about how you and Maldesto were always water and fire. You loved each other and at the same time you could disagree so strongly, that sparks flew everywhere. You always ended up finding a resolution. Another great story is how in Zach you found a great friend and dear mentor, from a spirtitual and emotional level to technical programming levels. It was endearing to see you guys work together, as a group of friends, with OSBot as a common goal. I have seen you grow as a person and as a developer. A remarkable evolution, one that has brought you this job offer that will take you to the next level in life. Alek, you knew the community, the people and understood the larger picture. You knew the bot and put yourlove, time and effort in OSBot, through good and bad times. After all you have been through in real life and the way you have fought to come up on top as a winner, I can say nothing else than that I am really proud of you for achieving what you did. Alek, you are without a doubt the greatest guy and you will be missed sincerely. Although I know your new job forces you to resign your duties, I am sure we have not seen the end you. OSBot will always be here for you to thank you for your contributions and we hope to see you around for a long time in the future. May your new adventures be loving and fruitful, we will miss you. The community and we are greatful for everything you mean and meant for OSBot. Please stay around lurking and trolling on the forums, that's something you can't take away from us! I could ramble on, but really, it boils down to that we love you and feel happiness and sadness at the same time to see you leave. *sheds a tear of joy* Be safe Alek, We will always be here for you. Moving forward. It is going to a tough job to replace Alek, if not impossible. However life goes on and so does OSBot continue to exist. For that we have had a week of internal conversations to discuss how to handle the situation and make sure that OSBot can continue forward. We have compiled a list of actions we will undertake, to assure the community that the future of OSBot is secured and that we'll take our responsibility as a team to replace Alek as good as we can: 1.) New developer. We are in talks with several bot developers and will have a couple of interviews to hire a new bot developer. It is important for us that this person is close to the community or if not, has the ability to build a relationship with the community. Once we have found a developer who we deem to be a match, we will come forward with an announcement. 2.) Bugtracker. MGI and I will take one day of our busy schedules to work on bug fixes and updates. This shall usually be Thursday, as this is also the day that RuneScape often updates their client. For this we will open a bug tracker, which will be read only for the community, but it should give the community and us guidance on what bugs currently exist and are being worked on. Progress will be shared through this bugtracker and we will take reported bugs from the forums to be displayed on the tracker. We hope that with the addition of a new developer, we can optimize the translation of bugs to an understandable bug report format that contains specific instructions on how bugs can be replicated. Our aim is to get all existing bugs as soon as possible. Web Walker, Mirror, Trade API and new features regarding recent RuneScape updates are the main focus, along with stabilizing the updater the break less often (some of the identifiers are 5 years old, it's crazy they didn't break before). Any questions regarding Alek's leave or any responsibilities Alek had in his domain can be forwarded to me through PM for the time being. Once we have a new developer on board, responsibilities will flow back at a sustainable pace towards the new developer where we see fit. I hope this has answered your concerns and informed you enough, if not, please drop me a DM. Yours sincerely, Maxi and the OSBot team

Should be resolved.

Should be resolved.

The reason: RS was/is being DDOS'ed.

Should be refixed. Seems like an unintended roll back occurred of the hooks file.

It would help if you can run the jar from the command line and copy paste the output from the console when this happens, you will see some kind of Exception being printed to the command line console. I assume you are on windows, this is how you do it: - Search for cmd.exe and open it. - Type "java -jar " without quotes and then drag your OSBot jar on the cmd.exe window. - Hit enter

Bot is no longer down. Enjoy! Edit by Zach: Switched Stable branch to 2.4.61 from 2.4.59 for updates.

I will post in the announcement section when the client has been updated/patched.

I will post in the announcement section when the client has been updated/patched.

Winners will be announced shortly!

We will announce the winners shortly!

No. Simplifiedly put: the OSBot client just reads the OSRS client's memory. There is no way they detect how often or when you read this memory. Calling methods of the OSRS client might be dangerous if not done correctly, but that is something we have never done and will never start doing.

Same goes for drinking potions and eating food, could be merged with withdrawing essence and food.

Without further ado, here it comes: Happy 3'rd OSBot anniversary everyone! Three years ago we started out venturing in the world of OSRS botting and now we are here. It has been a sincere blast and with the developments over the last months we are sure we will bring another year worth mentioning! To celebrate we wanted to give something back to you guys so we decided that we are starting with giving away 5 LIFETIME Sponsorships. After that, we will have another round of giveaways, because we can! Special thanks goes out to you, the community, the community staff members who have been with us and those who still are and the development team. Without you, OSBot would not have been here. @Maldesto you are a true hero for handling this community, @Alek you are a true hero for keeping our scripters cornered and @Zach is there anything you can not do?! @MGI you are an amazing programmer and an even nicer person and @Dex please continue messing with our forums haha. @Asuna maybe you can teach Dex? @Genii, @Khaleesi, @Epsilon and everyone aforementioned; keep up the good work, you are awesome! What do you need to do to win? Like our OSBot Facebook page, like our anniversary post, share that post and be one of 5 to get that beautiful rank as a gratitude for your time with us. To get to the page and post click the image below. When will we announce the winners? On May 15'th we will make an announcement on the Facebook page as well as here on the forums. The winners will be only announced by their OSBot usernames with privacy in mind. Happy botting, The entire OSBot staff

It is refresh demanding because you wrote it to be refresh demanding, whatever that may mean. Hunter, nor any type of script in RS is refresh demanding as almost everything is updated in 600ms cycles. Blaming mirror because of that is on you, as all my own scripts function 100% on mirror in the same way they do on non mirror mode and none of them require a 'high' refresh rate. Advising people to not use mirror mode instead of improving your script is ill advised when you consider the fact that mirror mode lowers detection rates A LOT compared to injection mode.

The mechanics of animation are like this. The way the RS client functions is that is loops on a 600ms updating interval. For animations, the client will receive information how to animate in one cycle, and although this animation may last multiple cycles, the animation update flag in the client will only be set in the cycle in which the animation will initiate. Therefor it is only reliable to know whether an animation has started and it gives you no reliable way of knowing whether an animation has ended. In your specific case, a player is performing multiple animations in a row. This means that in between phases in which isAnimating() will return true, it will also return false which will break your sleep.

Malicious code for sure. Action will be taken, thanks for your efforts.

Try and delete your OSBot folder in your home directory.

Moved.

Resolved.

Please update your post according to the following guidelines: http://osbot.org/forum/topic/67338-posting-bugs-format/