Hello everyone,

Is there a way to automatically update the OSBot client?

I have an automated farm which runs bots through CLI, but when an update occurs it can't run new clients anymore.

 

(I hope this is the right section, don't know where else to post this )

 

Imagine this scenario:

Current OSBot file: OSBot 2.4.153.jar

All fine and dandy and then a OSBot update hits. New file name OSBot 2.4.154.jar

Automatic updates hit - they download the latest file.

Now your launcher probably has a setting which tells it which OSBot file to use, how will you know which one to use? 

If auto updates won't change the file name to a previous one, no bueno for you.

I seriously doubt this that the devs would implement something like this. Best bet would be to do it yourself:

Check OSBot version - update needed - download latest file - rename

Would be great if they could add a CLI parameter that would have a set jar name specifically for CLI farmers.

54 minutes ago, purplewatilla said:

Would be great if they could add a CLI parameter that would have a set jar name specifically for CLI farmers.

When I add it Im going to make most of CLI VIP+ only since most of those features are for running more than 2 bots; which regular members cannot do.

43 minutes ago, El_Maestro said:

The same application that runs your farm could easily be improved to handle auto updating.

Yeah that's what I'm trying to do, although I don't know how I can update the client with code

6 hours ago, Alek said:

When I add it Im going to make most of CLI VIP+ only since most of those features are for running more than 2 bots; which regular members cannot do.

Was going to suggest that, sounds perfect!

4 hours ago, El_Maestro said:

I assume the launcher checks the current client version on start from an online file. IF the online file version number doesn't match the current client then it downloads the new client and launches it, else it just launches the client. You can emulate this yourself with a simple script. You will have to look into the launcher code and find the link which the launcher uses to check version.  

And how do I do that? I assume I can't just decompile the .jar file and look into the source