gamer and yeah Posted August 1, 2019 Share Posted August 1, 2019 When running in headless mode, how does the client deal with new revisions. If I run headless after a revision, should I expect any specific error code? Quote Link to comment Share on other sites More sharing options...
Token Posted August 1, 2019 Share Posted August 1, 2019 What's headless mode? Quote Link to comment Share on other sites More sharing options...
zwaffel Posted August 1, 2019 Share Posted August 1, 2019 22 minutes ago, Token said: What's headless mode? He wants to boot Osbot without an UI and just get the cli output. Quote Link to comment Share on other sites More sharing options...
Token Posted August 1, 2019 Share Posted August 1, 2019 3 minutes ago, zwaffel said: He wants to boot Osbot without an UI and just get the cli output. If the question was about the nointerface mode then, you should receive same login response code as without, the one associated with "There was a game update! Please refresh this page." or whatever the message was. Quote Link to comment Share on other sites More sharing options...
Chris Posted August 1, 2019 Share Posted August 1, 2019 14 hours ago, gamer and yeah said: When running in headless mode, how does the client deal with new revisions. If I run headless after a revision, should I expect any specific error code? it will not let you Boot the client if a new version of the client exists. Quote Link to comment Share on other sites More sharing options...
gamer and yeah Posted August 2, 2019 Author Share Posted August 2, 2019 3 hours ago, Chris said: it will not let you Boot the client if a new version of the client exists. In this case I imagine that I would then just redownload the .jar with wget https://osbot.org/mvc/get -O osbot.jar to resolve the issue (assuming the new osbot release at the link fixes the client). Quote Link to comment Share on other sites More sharing options...
Chris Posted August 2, 2019 Share Posted August 2, 2019 2 hours ago, gamer and yeah said: In this case I imagine that I would then just redownload the .jar with wget https://osbot.org/mvc/get -O osbot.jar to resolve the issue (assuming the new osbot release at the link fixes the client). correct 2 hours ago, gamer and yeah said: In this case I imagine that I would then just redownload the .jar with wget https://osbot.org/mvc/get -O osbot.jar to resolve the issue (assuming the new osbot release at the link fixes the client). u can run a job that checks the announcements section 24/7 for a new thread then u can execute the download command Quote Link to comment Share on other sites More sharing options...
