A long shot, but if possible to do easily, might be useful.

1. A description of the suggestion

Once OSBot is updated to a latest version don't force it to always download the latest build (allow to run to say max 2 versions down). Sometimes issues with latest builds might occur and this might render the client unusable.

2. How will this suggestion impact scripters and/or botters?

Scripters: no real impact. It will take time for scripters to make use of the new features in the latest build in their scripts.

Pros for dev team: If the latest build has issues, they can search for a solution in a "calmer environment"

Pros for botters:

  * No OSBot downtime.

  * Farms will run more smoothly. Cause if you haven't implemented automatic new OSBot build download - new clients won't launch.

Cons for botters:

  * Less experienced botters might run into unnecessary issues if they are using a very old build.

3. Post any examples such as code or pictures to supplement your description (optional)

As I see it, could work like this:

Launching from GUI:
  * If your version is less than 3 or so builds down, upon launch you get a warning saying "You're not running the latest verison of OSBot. It is advised to download the latest build."

  * If your version is way back (say more than 3 versions down) - force to download the latest build.

Launching form CLI:

  Same as with GUI, just show the warning message in output and not as a dialogue.

I used to do dev builds because nobody used them, so I almost always force new updates. Also sometimes older versions simply don't work with game updates. 

Could you optionally force builds if game updates break the client? As having no downtime is a real perk when you're paying for servers etc. 

12 minutes ago, Alek said:

I used to do dev builds because nobody used them, so I almost always force new updates. Also sometimes older versions simply don't work with game updates. 

Dev builds are for testing purposes, though I do understand your grudge doing them and people not testing. 

Though I do believe that my suggestion would allow to alleviate (in regards to keeping the bot alive)

1) Human douchiness not testing new builds

2) Various new build bugs that might not be unforeseen.

3) Keeping the farms running even without updating the client in, say, half a days time (person is sleeping, busy or etc)

If the game breaks the client then all is understandable and you need to download the latest version.