Many a times I came across a new Osbot version that, as long as the scripter doesn't update his/her script, paralyzes it. What this means for you and I is that we can't make our monies for anywhere between an hour to a week.

 

So, when updates take a working script to something like this:

 

I'd like to use a past version of Osbot that worked very well with the script. There was a time when we could use past version, but now when I try to download an earlier version like .77 all while version .81 is fucking my assssssssss...

the link leads to this

and there's no restoring your old, working version of osbot because you HAVE to download the latest

 

I understand that it's necessary to keep bots up to date so no one's wondering if works on version negative 69.420 or whatever.

 

So what I propose is that there's a buffer period where we can still use and launch the last Osbot version. This will solve our issues with temporarily paralyzed scripts by using the last version that usually does work well with it. This will also preserve the urgency for scripters to bring their scripts up-to-date.

 

An idea of what I'm talking about:

 

I completely understand if this just isn't possible. I'm merely giving a friendly suggestion for us all to benefit from

 

 

The .81 update was forced on everyone for good reasons. As for .77, it doesn't work for a variety of reasons so even if we enabled it, that wouldn't help. Otherwise, we test all changes in development builds prior to making them stable. It used to be that people were reporting bugs with versions that were months (yes, months) old or were fixed weeks ago. So, we instead chose to go with a development and stable release system. That way, scripters know what changes are coming and can adjust their scripts accordingly. When it hits stable, then users are forced to upgrade, but in theory any instability would have been dealt with. There are no plans to go back to the old system because scripters would be forced into trying to maintain their scripts for older versions instead of targetting the new ones.