- Thread Author
- #1
First of all, thank you for your patience in regards to the recent downtime we've experienced. Starting around the end of last year the development of a new updater was started. While the old updater used DFS across CFG's, the new updater relies on expression trees built from the basic blocks of organized CFG's. Expression trees are far easier to organize, meaning they're far more predictable and as a result more stable patterns can be derived from them.
As far as timing goes, there was no particular reason that we chose to deploy the new updater at the same time that OSRS updated. It was merely a coincidence. The only thing that changed in the OSRS game engine was the way that the combat gauges of characters was handled. A very simple fix.
This is a large update and has required a lot of testing already, and is bound to have some bugs that we hope to be able to iron out quickly. In exchange for this temporary inconvience, developers can expect new API To be added to the Actor and InterfaceComponent classes among others over the next few days. These new APIs will have a trickle down effect to the rest of our users because developers will be able to write more intelligent bots.
As far as timing goes, there was no particular reason that we chose to deploy the new updater at the same time that OSRS updated. It was merely a coincidence. The only thing that changed in the OSRS game engine was the way that the combat gauges of characters was handled. A very simple fix.
This is a large update and has required a lot of testing already, and is bound to have some bugs that we hope to be able to iron out quickly. In exchange for this temporary inconvience, developers can expect new API To be added to the Actor and InterfaceComponent classes among others over the next few days. These new APIs will have a trickle down effect to the rest of our users because developers will be able to write more intelligent bots.
