Maxi

Dear community, Runescape has updated to revision 23. I was at the hospital unfortunately so I couldn't update as soon as Jagex updated. I'll push the new hooks in a bit. Remember to close your client and reload it once I have done so. Will edit in a bit. Edit: We're good to go again. The hooks have been updated. Remember to close your client and restart it. Sincerely, OSBot.org

Runescape was updated. I'll push the updated hooks in a bit.

Hello everyone, In this release Strange plant should be working 100% again. In the previous version a small bug was left in the handler and I verified and tested it with my own eyes this time. v1.7.52 was lost due to a crash of my programming environment. Download can be found here: http://osbot.org Sincerely, OSBot.org P.S. Beehive will come tomorrow.

Dear community, I'm glad to announce that OSBot BETA v1.7.51 has been released. In this release the main focus has been random events. Not every event has received an update as I did not have the luck to encounter them nor got offered any accounts for these. In this release the following random events received an update: Miles, Giles and Niles: was working most of the time but some side case bugs were fixed and should no longer cause trouble Experience rewards: in the case you have an item selected it will make sure it is deselected first, also some minor changes that Jagex made are accounted for now Strange box: there was an issue where the strange box could cause the handler to keep throwing exception and not handling those well, resulting in never logging out neither solving the boxes, this has been resolved Strange plant: the run away from combat solver has been adjusted to not trigger on non aggressive plants, this must have slipped in at some point but was never intended to do so. Will pick the fruit correctly again. Molly: was working most of the times, although has received some changes when it comes to handling the door, however I'll need more accounts to do more testing on the result Frog cave: seems to only not work in some weird side case, I've made some changes that will hopefully make those side case fails vanish Drill demon: will no longer falsely trigger in highly populated area's like w1 Varrock and finish properly. Also some changes were made how it handles the exercises Download can be found here: http://osbot.org Sincerely, OSBot.org

JavaFX will still have to proof it will be the next standard for GUI design but I definitely believe this will be the case. It has quick development and release cycles and they are working out the downsides at a fast pace.

It performs slightly faster when it comes to drawing as it uses a smaller time step in its engine than Swing. Swing uses a 5ms time step where as JavaFX allows for smaller time steps. We won't have to release a custom JRE, we will probably simply provide the JavaFX runtime through booting.

try un-installing then re-installing the bot, helped me when I had this issue. gl mate didnt work i did that roughly 10 times.i got it working earlier,but it wasnt because of that.3 days is what they needed to fix the issue i guess.others had the same problem.im just glad that it works.took a while though We didn't 'fix' anything. Whatever the issue was, we didn't release or change anything.

Please make sure you have read the first post before posting. Thanks for the help so far. I'm currently working on the Beehive and after that I only have the Lost & Found and Maze random left. Any accounts in those are appreciated much!

I reported a lost & found stuck for fishing if that counts. my bot only ran around trying to fish but there were no pots so it couldn't and eventually lead to my 2 day ban. can post a pic of banned account if needed. ~ edit wasn't needed but here's the picture http://gyazo.com/eca20ddc500ac35577c354aa8982663d This is not the lost & found random. The lost & found random is with the abyssal appendages (four of them) which you get when doing any kind of teleportation in runescape. You are talking about a script specific fail that I can't help with, you'll have to report the bug to the script writer.

Dear community, I want to give you an idea where OSBot 2 is at. First of all I want to let you know that OSBot 2 is rewritten from the ground up to tackle some problems that you as a community pointed out. Things like CPU usage increasing over time in a scale of hours, something that never was a huge problem to most users but could be annoying for some. Besides that, increased overall performance is something everyone always likes to see. By writing an entire new core and taking time to do so, the client will score better at those points. At the moment, there is an abstract core written which is extendable for the most part to write implementations of other server revisions, such as RS3. Whether we will do so or not doesn't matter, it will be reusable. The entire GUI of the current OSBot was written using Swing. For OSBot 2 we are using JavaFX. JavaFX might not be as developed in certain areas as Swing, however those area's won't affect us. Besides that, JavaFX performs faster and gives more reliable output when it comes to exceptions. Not to mention, I personally and many others agree, I think that the look and feel of JavaFX is far better and promising than Swing. At the moment, a lot of the main GUI features are done. The client loads the applet, injects the client, hacks the canvas and such. So from here on, our first focus will be towards designing and organizing the new API. The API will have the same features as seen in the current OSBot and those features will be ported over. This is not a very hard job, most of it will just be refactoring. Other new features will remain secret and will be revealed as progress proceeds. Besides the API, which its functions will not have to be rewritten, we are planning and thinking about a second scripting engine. The current scripting engine is completely sequential in a blocking fashion. The new scripting engine, don't worry the old one won't disappear, we want to give a fully event driven asynchronous environment where you will dispatch tasks based on events and have control over the queue by using policies for tasks. We are looking forward writing this as Laz and I love writing new and fancy stuff. There are many other things that need to be done for OSBot 2, but the above is the majority. We can't give you an ETA, we don't want to stress any deadlines and instead focus on its quality. Laz has done a great job on it so far and now I'm joining him in this battle progress will speed up. I hope you had a fun read, Sincerely, OSBot.org

I have made a fix for this. I would very much like to have an account stuck in this random event! Edit, another update on what has been done so far: Currently I have worked on these randoms and have improved side cases where they would break or fix them entirely as far as I could test myself: Miles, Giles and Niles: little fix to account for the possibility of the interface not containing the childs, letting it wait for them to be set and after a couple of retries restart the random handler Exp rewards should now have a fix to account for cases where you have selected an item Strange box should now have a fix to account for cases where you have selected an item Strange plant should now be prioritized again to pick the fruit, running away from combat should only occur anymore if the plant has it's attacking form Molly has some modifications made, these still need to be tested Frog cave has some modifications made to account for the rare cases where it will sit there and do nothing, this is untested and will have to be confirmed by the community as it seems this case is quite rare to encounter Drill Demon has some modifications made to it, it will no longer trigger outside the area and will be more efficient Strange plant should no longer trigger the run away from combat handler first, it will try and pick the fruit. The handler will only run away if the plant every reaches its attacking form where you get poisened and won't wait for the first hit to be dealt Things I'm still looking for are: Beehive stuck accounts Lost & found stuck accounts Accounts stuck in maze

I will also need a couple of accounts in drill demon to fix the issue people are having in world 1 with it! Edit: Currently I have worked on these randoms and have improved side cases where they would break or fix them entirely as far as I could test myself: Miles, Giles and Niles: little fix to account for the possibility of the interface not containing the childs, letting it wait for them to be set and after a couple of retries restart the random handler Exp rewards should now have a fix to account for cases where you have selected an item Strange box should now have a fix to account for cases where you have selected an item Strange plant should now be prioritized again to pick the fruit, running away from combat should only occur anymore if the plant has it's attacking form Molly has some modifications made, these still need to be tested Frog cave has some modifications made to account for the rare cases where it will sit there and do nothing, this is untested and will have to be confirmed by the community as it seems this case is quite rare to encounter Things I'm still looking for are: Beehive stuck accounts Screenshots of the strange plant in all its forms with the entity debugger enabled and the mouse pointed at the strange plant Lost & found stuck accounts Account in Drill Demon: not stuck accounts, but to gather some needed information to fix the bug people encounter in highly populated area's where the sergeant wanders around sometimes grabbing other people Accounts stuck in maze

Would love to have an account for that!

I need pictures of the strange plant with the entity debugger enabled and the mouse on top of the strange plant in all its forms! If you come across any please post them .

It's magic.

I'm on this one, will squeeze a little fix in for this asap. Also, I will introduce a fix for the strange plant issue.

I forgot to restart the server, my bad. Restart your client and all should be working now.

The hooks have been updated. Please restart your bot client and we wish you happy botting!

Hello everyone, Jagex has just updated their client to a new revision: 22 I will be running the updater and quickly test all major hooks and supply the server with the new hooks. This will hopefully take no longer than 30 minutes. Edit: The hooks have been updated. Please restart your bot client and we wish you happy botting. Edit 2: Id's for different entities have been switched up, so for example for Ande's autofigther you will have to change your setup to match the correct npc id's again. Sincerely, OSBot.org

These are all script related things and have nothing to do with OSBot's random handlers. So far I have been botting nearly 24 hours and haven't come across a broken random myself. I really need accounts people !

I want to stress that keeping accounts in randoms and sharing them with me will greatly speed up the process of fixing up the broken randoms!

I'll need an account for this unless I encounter it myself.

With a community that can give you accounts stuck in randoms why would you play for hours on end to get all the random information on one of your own accounts. Please tell me where it says you HAVE to send your account information... Lol chill out bro... It was just a question, an I didn't mean we have to send our account lmao I meant why would you need it an what do you mean why would you get all the random information on one account its the same thing as getting it on others I take it It could take me days to get a specific random, which renders it very inefficient. If I come across randoms myself I will use that, but it will take me a very long time to get the randoms and I'll possibly need randoms multiple times to verify/improve the handlers.

We will be looking in to an easy solution for this, but we created random behaviour hooks for developers to cope with this. Developers using random behaviour hooks should be able to handle this, as it might be very specific based on the script. What version is this on? I encountered Drill Demon today and it solved it. Noted, I'll need an account to fix this. Alright, I'll need an account to see what's going on.

Hello everyone, I will be focusing on fixing any (partially) broken random. In this thread you will be able to post what random you encountered and give a detailed description of what exactly happened. I know we have a separate thread for this, however I wanted to reach out to as many people as possible. If it's a random where you can stay in (meaning you're stuck), please stay there and share your RS account credentials with me in a private message if you feel comfortable enough to do so. Make sure you change your password to a temporary one that you change prior and post giving it out to us. Without accounts the progress of fixing broken randoms will slow so for the sake of the community and the bot, please consider leaving your accounts in randoms and share them with me! Please format in this way: Please note that any post not regarding randoms will be removed and are not asked for. Edit: Currently I have worked on these randoms and have improved side cases where they would break or fix them entirely as far as I could test myself: Miles, Giles and Niles: little fix to account for the possibility of the interface not containing the childs, letting it wait for them to be set and after a couple of retries restart the random handler Exp rewards should now have a fix to account for cases where you have selected an item Strange box should now have a fix to account for cases where you have selected an item Strange plant should now be prioritized again to pick the fruit, running away from combat should only occur anymore if the plant has it's attacking form Molly has some modifications made, these still need to be tested Frog cave has some modifications made to account for the rare cases where it will sit there and do nothing, this is untested and will have to be confirmed by the community as it seems this case is quite rare to encounter Drill Demon has some modifications made to it, it will no longer trigger outside the area and will be more efficient Strange plant should no longer trigger the run away from combat handler first, it will try and pick the fruit. The handler will only run away if the plant every reaches its attacking form where you get poisoned and won't wait for the first hit to be dealt. Also will no longer fail to pick the fruit. Things I'm still looking for are: Beehive stuck accounts Lost & found stuck accounts Accounts stuck in maze Sincerely, OSBot.org