Maxi

Much cleaner than the current one imo.

I'd swipe my ass with you. But nice troll :p.

Your information isn't entirely correct. Injection/reflection bots are not colour bots perse. I won't go into details because it doesn't matter to the subject anyways. Packet bots (I didn't even know they still existed and are used..) are extremely vulnerable for updates. Afaik, AutoRune was (one of) the last packet bots before they started to randomize their opcodes with ISAAC and hide the seeds inside RSA encrypted blocks, breaking the bot. This is a very long time ago. OSBot is not a colour bot and its injection techniques are not detectable with the clients current techniques and I don't see that changing any time soon, we have taken a different approach than most conventional bots have which have been copying older bots too much for the past couple of years. Like we try to mention a lot, OSBot has been given some (good) thought and care during its immature development.

There will be no difference between a 'dev' client and a normal client. The one client released will contain all kind of utilities to develop scripts, this to ensure it's as accessibel as possible, so the community can assure the bot's future with plenty of scripts. Later on, chances are we might introduce separated clients and drop support for the older client.

Solved.

According to my resources it has been added a while ago.

Hello community, Let me begin by telling you we are making good progress towards our release and inform you as needed: Global and local repository. We have started on the software required to load and use scripts from an online global script repository. In the future we intend to also have web access to the repository instead of access through our main client application only. The global repository will contain working (no errors, no major recognized flaws) scripts, both free and premium ones with a dedicated team behind it who make sure the quality is conform standards we expect from either free and/or premium scripts. This global repository will be used to download script files from you have access to, either because they are free or you have gotten the privileges for premium ones. The local repository is where those script files downloaded will be stored in, either downloaded through web access or the client. We will make sure this will be done in the most secure way possible. Not that scripts will hold any of your information, but we just want to make sure it will be hard to reverse engineer scripts in the local repository if they were manipulated in such way to prevent them from being accessibel. This all together, should maximize the ability to use the client 'offline'. By offline we mean that there is no connection with our server required when using the client, unless an update needs to be downloaded or a script needs to be added. We will still most probably add limitations to the amount of bots you can use per script/account. This is not some cheap ass trick, but we simply don't want our software to be unlimited for a reason. Scripting API. The API is nearing its completion for the first version we initially planned. It still needs some features to be added, but once done the only task left on the API is to make sure it's organized in an intuitive way and make sure all the documentation is written. Then we also generate all the webpages for the API documentation so you can either download to have an 'offline' reference, or simply access it through our website as an online reference. The online version will of course always be up to date, so if you can, use the online API documentation reference. Misc. There are tons of other small things I could mention, but I simply won't bother you with such boredom. So let's get to what's the most important in this thread: ATTENTION TO ALL SCRIPTERS: This thread is where we will gather a basic group of trusted and talented programmers that will help us out to write and test some important high quality scripts. Initially, this will be focused on random events and a series of free scripts for the community to use with a certain quality standard. Eventually, if both parties are satisfied, further coöperation can be continued by creating premium scripts. Remember that if you're not part of the scripting team, you can still advance your own skills by writing your own scripts and if you feel generous share them with the community to earn respect and fame! What do you need to do to apply? Fill in this little form and send it in a PM to me. We will look over your information and decide what further to do. PLEASE NOTE: Don't post your information on this thread! Use a PM to me. Don't forget links to previous work. Also, don't take previous work as an easy field. It may be anything that you think will show us you know what you are doing, but know we only go for real quality. After this nice wall of informative text I wish you a good night! OSBot.org

I like it Kati!

I think he is talking about user agreement contracts and disclaimers etc. And yes, we will put them on the site before release.

Any updates?

What are you saying Riskeh?

I don't see how it's inferior. In fact, I think it's the other way around. And about botwatch, botwatch is most probably a 'learning' detection system based on behavioral aspects of the bot as in mouse, key input, timing and human / nonhuman patterns. We will see how well our bot does against this 'botwatch'.

Yes.

Yes, however validating new premium scripts will always need a connection once when bought.

Hello everyone, Today we have spent time on reorganizing the thread design of the bot to allow for efficient concurrency. This means each bot will run on multiple threads and can handle multiple actions at the same time. For example, random detection and solving will happen on an entirely different thread than the main loop or the key input handler for example. Currently I'm writing methods to rotate the camera to certain points on the map, for example towards objects or npc's. This will be very useful for getting entities into the view screen, but also is good for anti ban detection. We also have been planning other important stuff for the release. Things like a new host and DDoS protection, to set everything up as comfortable as possible. However we are short on money at the moment, so if you feel like you have some spare cash please consider a donation. If you feel like doing so, you can send me a message. This money will go straight into a new host and its DDoS protection. Stay tuned as we try to get everything ready for release. Remember that you, the community, will represent the authors of the script base to start with. Exceptionally talented scripters can become premium scripters, to write scripts that guarantee quality. Your contributions will be what will make our community thrive. OSBot.org

10/10 for being a gray mouse!

Groovy yes. Java and JRuby will be supported in the future as well.

Nice to have you!

Looks sick! Keep the good work up !

Hello everyone, As we are making progress the first functional scripts are starting to get created. Today I wrote a script to cut willows at draynor, banking the logs in the bank and repeat. It's a very simple script, it has no support for bankpins or random events however those functionalities will be added in the coming days. The main thing is that it does its core job of cutting wood very accurately, chopping, walking from and to the bank and banking in a very decent manner. Stay tuned! OSBot.org

If there are multiple objects location can be given as a parameters. Right now when I want to chop down a specific Oak Tree I do this, it will walk you to the object if the object isn't within a clickable range: selectEntityOption(object, "Chop down", "Oak Tree") In that code it's up to you to decide how you get your object. You could choose for the closest object like: def object = closestObject(id) But we will have support for objects at specific locations, and it will be very easy to find the locations of the object because the bot client has options to enable and disable information like location etc drawn on top of for example objects.

We will have functions where you define an object and you define what to do. For example, walk to it and click and option. For example, the script i'm currently working at will have a series of objects registered as bank booths, and all I call in the script is simply: walkTo(object, "menu option to click string") Is that what you meant?

Goodluck, this sounds like a nice tool. The initial release of the bot will only support scripting in Groovy, it's very similar to Java. In the future JRuby and Java will also be supported.

Anti random events unfortunately can only be written once the events are encountered. It will take some time to encounter all of them multiple times to write and test the solutions. We will need your help for this, by using accounts that are stuck in random events or by code contributed by scripters who have encountered the events them self and wrote their own anti random for it.

Hello everyone, Today and yesterday we have been working on a couple of things. First of all, we have improved the bot its overal mechanisms we already implemented. Furthermore we have added a walking algorithm including pathfinding, which allows you to simply say: walkTo(x, y) Hooray! Today we are working on redesigning some of the ways input is handled and the overal design of the script / bot threads. Instead of one single thread, an event driven threading design has been introduced, to allow things to run more concurrently especially in the case of client callbacks. This isn't needed for most things, but in a few occasions this is very handy when developing scripts, such as walking and moving the camera at the same time. We are also implementing a function today that turns the camera into the direction of a certain object. If we finish all things I'm talking about above, we can run a basic but complete woodcutting bot by tonight, which would only require babysitting in the case of random events which then of course can be written as they are encountered. We're getting close! OSBot.org