Dear community,

 

We have decided that we would give you a preview of the OSBot 2 API by providing the java documentation to you. This should give you an idea of how the OSBot 2 API is structured. Note that the API is not finished and unfinished features are not included in this preview.

 

You can find the preview here: http://www.osbot.org/osbot2_api_preview/

 

As is OSBot 1, the root of the scripts is the MethodProvider which is located in the org.osbot.script package.

 

Have fun reading it,

 

OSBot.org 

Interesting, thanks for sharing.

Will you be able to make scripts work together with the Break Handler in OSBot 2.0? So for example if I'm using a hunter script it would be able to tell the bot is taking a break in 20 seconds, and therefore it should pick up all my traps. 

It's all looking great thus far, can't wait.  

Interesting, thanks for sharing.

Will you be able to make scripts work together with the Break Handler in OSBot 2.0? So for example if I'm using a hunter script it would be able to tell the bot is taking a break in 20 seconds, and therefore it should pick up all my traps. 

This is possible in OSBot 1 with random behaviour hooks.

Maybe it's because I'm not to familiar with API's in general as this is the first one I've ever used, but in my opinion it looks even more disorganized than the one we have right now. Things like this:

 

Why not have it all in the main client class? Plus considering the only difference from the LoginStage/LoginState packages is one letter. It's more confusing to have it like this then just neatly organized in the main client class.

Edited January 13, 201412 yr by Swizzbeat

Thanks I guess. Estimated ETA on when OSBot 2 will be released???????

Things like this:

 

Why not have it all in the main client class? Plus considering the only difference from the LoginStage/LoginState packages is one letter. It's more confusing to have it like this then just neatly organized in the main client class.

You should know by seeing this that the enums LoginStage and LoginState are declared in the Client class. Their respective fields are as well. So I'm not really sure what you said.

 

I suggest you start looking in the MethodProvider, which is the base for your script, the API and events.

Looks awesome thanks!

Great work man!

Nice one!

I got 99 problems, but this API ain't one.

i hope the randoms will be better 

I got 2 tabs up of bots at the moment and I go to check on the first one and turns out it never world hopped, a big issue with having 2-3 tabs on 1 client open or whatever, will this be fixed in OSBot 2 or not???????????

Looks nice and clean, keep up the good work.

Sweet, will look at this for a bit

 

Edit: Can you show us how conditions function? Seems like an interesting idea

Edited January 13, 201412 yr by oTroll