Maxi

We are currently doing research to the matter. We will get back to the community with an announcement soon.

He has not been demoted. More information will follow soon.

The scripts in the SDN have been updated earlier today, about 8 or 9 hours ago.

People are free to go where they want to be and go multiple places at the same time. But only if you have no commitments and responsibilities elsewhere and have the same elsewhere. People from Apple don't work with Microsoft but can certainly use Microsoft's software or visit their stores.

Dear community, Over the past few days we have been targeted by a group of angry people. They are angry for many reasons, some of which have solid ground but they have taken it too far. They created a new community and a competitor bot, which is good. Competition keeps everyone sharp and we did never mind about competitors as long as they did not attack us directly, for example by creating a lot of spam on the forums with inappropriate content. Their community and bot is called Osbot FTW. Master Chief has, without communication, become an administrator on their community. Therefore he has been demoted and it's a decision I didn't like to make but had to. His place will hopefully be filled by a great staff member. One more shoutout to you I want to make and perhaps to Osbot FTW as well is that I'm really surprised by their behaviour. I don't see how being hostile towards another community to begin with is a good start. But maybe I'm not the one to judge. I do understand people have their discontent which the development team is to blame for. On the other hand, we can make up for this and we will certainly do so. If you have no commitments, you have the freedom to chose where to be. Be in one place, two places or more. But if you work with Apple, you can't work with Microsoft at the same time. Thanks for reading, OSBot.org

For the past 2 days there is nothing new as my focus has been on the BETA client and dealing with angry people from you know where.

Dear community, This release contains the actual fixes meant to be in v1.7.61. Sorry for the inconvenience of downloading a new client twice. Sincerely, OSBot.org

My bad, I made a little mistake. Give me a minute and I'll upload the patch.

I'll do some research, perhaps I made a small mistake.

Thanks for your useless comment.

Dear community, In this release the following fixes are included: Genie should activate properly again (didn't activate most of the time since last update) Rick Turpentine should activate properly again (didn't activate most of the time since last update) Drunken Dwarf should activate properly again (didn't activate most of the time since last update) Mysterious Old Man should activate properly again (didn't activate most of the time since last update) Dr Jekyll should activate properly again (didn't activate most of the time since last update) Security Guard should activate properly again (didn't activate most of the time since last update) Cap'n Hand should activate properly again (didn't activate most of the time since last update) Sandwich Lady should activate properly again (didn't activate most of the time since last update) Miles Giles and Niles should activate properly again (didn't activate most of the time since last update) Prison Pete is working properly again And a small change to the camera method, which its documentation can be found in the updated API here: http://osbot.org/api Download can be found here: http://www.osbot.org Sincerely, OSBot.org

Yes, this will be in effect with the release of OSBot 2.

It seems some things have changed with the revision update #30. We're working on finding and fixing the issues with random. If you have any information you can share please do so and stuck accounts would be much appreciated.

http://osbot.org/forum/topic/24061-osrs-revision-30-update/page-2#entry275296 RS has updated and the reason why your client failed to load is because the hooks had to be updated. Restart your OSBot client to have the latest hooks. Also, use the latest version released 1.7.60.

I have updated the hooks. Restart your OSBot clients and continue botting.

Dear community, We are currently updating the client to support RS's latest update, revision 30. Please hang in there while we are working on it. EDIT: The updated hooks have been uploaded and the server has been restarted. Please close your OSBot client completely and restart it to have the latest hooks. Sincerely, OSBot.org

Dear community, In this release the following fixes are included: Changes made to prison pete are reversed to how it was in v1.7.57, it's unsure though if this will fix the current problem with prison pete as I have not had any accounts sent to me that are stuck in the event settingsTab.openHouseOptions() has been fixed settingsTab.setHouseBuildingMode() has been fixed A scroll pane has been added to the account selection window which should solve problems for anyone with many accounts stored to bot with The flax spinner is working properly again, this will be updated on the SDN soon. There are still some other server issues at the moment we are looking to fix, like the unable to login to the OSBot client issue. Please be patient for this to be fixed. On another note, I'm still in desperate need of accounts stuck in randoms. You have reported several problems of which a few have been fixed although I can use any accounts stuck in any random to change their behaviour (which is good for anti-ban) and if they have any problems or bugs, fix them. Sincerely, OSBot.org

The same accounts for this, I'll need an account to analyze the handler and event.

Please try to make your posts understandable. Also posting multiple times about what I think is the same subject is seen as spam, please don't do this. You have been warned about this earlier this week.

I would like to remind you of the rules & guidelines of the OSBot market: http://osbot.org/forum/topic/2624-your-rules-and-guide-to-the-osbot-market/ There is insufficient prove here and it will be hard to prove either one your cases.

I'll need accounts for prison pete people! It's probably an easy fix. If you could provide any that would really help out!

This has been repeated an awful lot of times that this should be handled by the script developers writing a random behaviour hook. We can't specify such behaviour because if we do it might be very dangerous. Contact your script developers to write a random behaviour hook to handle with such specific cases.

I'm still in need of accounts. I have fixed a couple of small issues with some randoms, those will be released shortly.

I'm only looking for accounts stuck in random events. And thanks for the accounts so far guys.

Added your fix in GoldenGates.