Maxi

Because some of those bugs are encountered by for example only 5% of the people or less. So in my opinion, as long as we are in BETA, we support older versions and release public newer versions for testing. For example, the slow mouse movements, are so far only encountered by 3 or 4 people out the entire group of people who have used 1.4.1. (edit: apparently it happens more often on moving entities like npc's). Using only the script writers would not uncover all bugs. Once we leave the BETA, we will setup a release cycle with release candidates that will be tested before updates.

We are pretty much finished with what we aimed for 1.4.1. I'm waiting for Laz to return from a family event he's attending at the moment, in the meanwhile I'm just playing around, tweaking, trying to score bugs etc. Hang in there ;).

We will release 1.4.x tomorrow unfortunately. We are 95% done, but can't afford to release without having tested the last few things.

All all this can be scripted already.

I'm happy to announce that we expect our SDN to be and running by the end of sunday and with this most, if not all, random events included in the SDN and automatically loaded onto your computers. On another note, I expect BETA v1.4.1 by tonight. My list is still long and there have been many distractions around OSBot that needed our attention, however I will work on v1.4.1 for the coming 9 to 10 hours so that should be enough. Stay tuned all ! OSBot.org

The difference pretty much comes down to one thing (the language differences are neglectable): Groovy doesn't need you to compile which speeds up development, Java allows you to jar your files into packages to be used by the client. I would say, Groovy for development, Java for releases. One can be converted to the other within no time.

Ok, I want to discuss this with you script writers. Basically, we have a system setup which allows you to load random events simply by putting the files in the correct folder and it will be activated once the onActivate() method returns true. For most randoms, this will work fine. For example if you get the strange box, or if you're taken to the surprise exam, you want to solve it on the spot in most cases. But what if you get the evil chicken? Then you want to specify your own way out, either to run away, either to kill it etc. So I was thinking, we need to provide you with a random management system. See, we as OSBot will provide most and eventually all randoms through the SDN. These will be written by us and, as has already been done by some, people from within our community. But what if you're at the fight caves and you get an evil chicken outside? Well obviously the easiest way to avoid the random would be to hop back into the cave again. tl;dr I want to suggest to have a library with an unique id for each random (to be documented in the API), where for each id you can subscribe your own handler to with parameters to completely override the preprogrammed random behaviour, or to extend it in such a way that your handler will perform its logic and after that the code inside the random will take over. Before I start writing an implementation for this, I want you to think about any functionality you see fit in this system that we did not come across. Discuss.

These are just pre programmed values. We can and will change it to load and save the settings, however I'm not sure if with our current list of priorities we will manage to squeeze it in for this update. But in any case, we will make sure debugs are turned off by default initially.

I'm sorry for the delay of this release. I have spend more time than initially calculated to do a couple of these updates, and today and yesterday our country was completely in party mode because of the crowning of the new king, an event I of course had to attend. I will work as hard as possible to get this release out within 2 days.

If it would be the bot, other people would have complained about this too.

That's a very unlogical thing to say. See, we need to spend money to set up a limited liability company which will effectively make our chance on existence in the long future significantly bigger, legally speaking. This is how p****bot more or less manages to stay around. However this is not a cheap investment, so please next time try to gather some important information first, before holding people back to invest in the future of OSBot.

That's caused by errors in your scripts, not OSBot.

OSBot is not open source and won't be in the foreseeable future.

That space will be used to express some more information about OSBot.

Dark background variant: http://i.imgur.com/KfGS2A5.png

Concepts / basic empty layouts: Light background: http://i.imgur.com/Rw27Hd8.png Dark background: http://i.imgur.com/KfGS2A5.png I say yes.

Will be looked into this weekend and an update for it will be pushed.

I have updated the post to link to our Store as it all works now.

Random solvers are easy to do (most of them). We are waiting for our SDN to be deployed so we can distribute them to you without you needing any updates manually.

The red overlay and blue text with the random name indicate you're in a random. It goes away after the random. The paint for the script remains visible underneath it.

We should do this once the SDN is up and running. This way they won't get leaked, otherwise there would be no point.

We obviously are a new bot and didn't base our bot on any other bot, so we're worked from grounds up. If we want to become one of the major bots out there, we will have to do so ;).

Health checking does already work. @Xavier: it's on the list ;)

Food can be used now already, it's really easy to do. You just have to write more than one line, not simply something like eat(id)

Dear community, For the end of this weekend we have planned the release of BETA v1.4.1. With the previous update of v1.3.3 we managed to greatly improve the stability, memory and cpu usage of OSBot. This update will focus on how the current API works. Features/updates you can expect: Fixed area's Completely renewed mouse movement with much higher accuracy (no miss clicking) Improvements on the walking algorithm, also support for paths Improvements on the interaction methods New/improved camera rotation methods Support for local and global area's Fix of the onActivate method from the Login random Food API functions Prayer API functions Magic API functions Anti Ban API functions and more... Stay tuned! OSBot.org