I've been thinking a lot of the structure of scripts as of late, mostly due to the fact that I haven't had much time to do any actual work on the framework. My conclusion comes down to this: Scripts should be easy to install and for developers to maintain and update. If you've ever used other bot bases you'd most likely be familiar with the basic workflow for developers and how downloading and keeping routines up-to-date can be a tedious task. This is why I've decided that the best implementation to make sure that developers can easily maintain a project and users are always up-to-date is to use Git. In short, Git is a distributed version control system that allow for easy development across multiple developers. The workflow for projects would look something like this: Developer creates a git repository on whatever platform he/she likes, GitHub and GitLab being the most popular platforms. This allows developers to do changes to do code and test internally, either locally or collectively using different branches. Releasing an update developers is as simple as pushing/merging to the master branch of the repository. Users adds that repository in the client and it automatically pulls it from the current master branch and will keep it up-to-date automatically every time the user launches the client by pulling the git repository. This approach also have another big upside to it, most git platforms have an integrated issue tracker, wiki and more awesome features that makes it very easy for users to report bugs, request new features or even contribute to the project itself. The end goal of this is very simple, developers and users alike must have an easy way of either developing or using scripts. This became a pretty long post so I'll end it here, in the next few weeks I will be working towards getting git integrated into the client and separate the default routines, Anti-AFK script and fishing script different git repositories with all the benefits talked about above.