Maxi

It seems there is a bot busting going on. We'll be spending time on changing methods and random solvers around to improve humanlike behaviour and create new unknown patterns which their behavioural analysis is unknown with. There has also been inside information saying the client recently got new detection systems. We are analyzing the client to see if this is actually true as well.

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.

Both of you have not completed your payments like AAJJU said. The invoices are still pending.

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.

The server was rebooting, this might have caused an issue. Restart your OSBot application and you should be fine.

Added your fix in GoldenGates.

This will be addressed in 1.7.59 which should be up in a couple of minutes.

Solved in the upcoming release of 1.7.59 in a couple of minutes.

Dear community, In this release you will find the following bug fixes: setRunning() is now working properly again withdrawX() is now working properly again moveCameraToEntity() is now working properly again The world hopper is working properly again A small issue with minimap walking was resolved An addition has been made to several randoms to handle post solving dialogue continuation And a tool called the ExperienceTracker for easy tracking of experience. This can be found in the API pages here soon as it is being uploaded as we speak: http://osbot.org/api More fixes as required will follow soon. The download can be found here: http://osbot.org Sincerely, OSBot.org EDIT: As I came across a bug posted on the forums I squeezed in another fix, sorry for the sequential updates. v1.7.59 contains a fix regarding the break manager which would throw an exception.

To answer Mikasa's question: Laz did loose his phone numbers when his phone was reset and was unable to reach me because of that.

Let me clarify myself. My message might have come across in a bad way. My post was not about justifying any actions that are mine. I know people are upset the way things have been for the last time, which is something we will have to make up for and prove ourselves, something that I feel sorry for. Whatever my reasons may be, I understand the community its frustrations. But this thread was created to set a boundary where my personal life gets intruded and shared. A boundary that is not to be crossed. No matter what frustrations or opinions. I hope you can separate those two things. For now, I believe any discontent can still be fixed. Maybe not tomorrow, but definitely soon. Like I said, we'll have to prove this which we will.

Alright. I've added something in that should essentially fix your problem, however I can't predict its interference with specific scripts. I'll be back online tomorrow. Any accounts I can get would be appreciated. Thanks!

The bot won't solve strange boxes when in combat. The scripters need to register a random behaviour hook for this, as there is specific cases that a scripter can account for but we can't because if we do we mess the solver up in general. Basically the scripter will simply provide logic that needs to be executed before and after solving the box, i.e. run to a safe spot before and run back after. In between the scripter can then use the default behaviour of the strange box solver.

yes, that's it. I've added a check for that, I hope that in practice it will not interfere with any scripts. In the past I've always told script writers to handle those themselves, mostly necessary in auto merchants, and scripters did. What kind of script are you running?

I have little reason to suspect that these randoms are not working however I had a minority of reports. What I'm saying is that I'm looking for these randoms for verification.