Jump to content

OSBot 2.0 New ETA & Backwards Compatibility Info


Laz

Recommended Posts

Hello community.

 

Unfortunately we have missed the ETA for the private BETA for scripters which was December 1st, but I was caught up with my studies and the rest of the development team has been focusing on the SDN and maintaining OSBot 1.

 

We've decided that instead of having a private BETA for the month of December, we will allow our scripters to enjoy their holidays and simply release the entire bot by the first week of January to the public. Since OSBot 2.0 will feature an OSBot 1 script emulator upon the public release, it will be a fully functioning bot with ALL the scripts you've already purchased and/or added to OSBot 1. The transition from OSBot 1 to 2 will be extremely transparent to the community. Although OSBot 1 scripts will not enjoy ALL the new benefits of the upcoming script engine, you should still expect better reliability and performance, both memory and CPU wise.

 

Although the support of OSBot 1 scripts will be available for OSBot 2, upon the release of the newest API we will start discouraging any development of new scripts for OSBot 1. Despite this, in reality, scripters will not NEED to learn the new API. Because of this, we have justified our new API which although may seem complicated to novice programmers at first, is much more abstract and organized as well as being smarter.

 

tl;dr: The new ETA for the PUBLIC beta of OSBot 2 is the first week of January.

 

Thanks!

 

Sincerely,

Laz and the OSBot Team.

  • Like 20
Link to comment
Share on other sites

If the case is OSBot 1 scripts to work with OSBot v2 then I don't see why we have to wait 1 more month for OSBot 2, there's really no pressure on the scripters to get it update to OSBot v2 if everyone is working fine.

 

OSBot 2 is too immature for a public release at the current moment. We're still integrating the SDN with it and the emulator has JUST begun development. There's also still some bugs with the new async script engine and we still need to document some of the API.

  • Like 1
Link to comment
Share on other sites

  • Developer

If the case is OSBot 1 scripts to work with OSBot v2 then I don't see why we have to wait 1 more month for OSBot 2, there's really no pressure on the scripters to get it update to OSBot v2 if everyone is working fine.

 

We want to complete the OSBot 2 API with all the features and new techniques for hand in the OSBot 2 engine before we release.

And of course we want to have OSBot 2 tested on multiple systems to make sure there are no hidden flaws that can only be spotted when ran on multiple different systems.

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...