Is it possible if the client is down after an update, to block it from running bots? This way we can prevent people from posting bad reviews/comments when it's not the authors fault. Alternatively, can the developers get a flag somewhere to check on it? So we can build in support for it in our bots? e.g. Code (Text): public void onstart(Args ...) { if(!Environment.isGameTypeAvailable(Environment.getGameType()){ getLogger().println(Error, "Cient is currently down."); /* log out & stop bot */ } }
Seldom is the bot down long enough for us to invest time into implementing this. There is an alternative that takes far less that is in the road map.
So soonTM I feel as if this wouldnt be to hard to implement and it would be a nice temporary solution, we've had the client go down for 5 days multiple times
@Party this could easily be implemented with cloud constants and a small amount of UI work. I think it'd be worth adding the ability for us to disable a game mode just in case of a big client update while I'm aware or some such.
It would be better to integrate with RWS seeing as we're trying to reduce the number of cloud constants (and also much easier for me and is what I was referencing in my earlier post).
I don't believe many people use RWS, at least I don't unless I am going for an omega shite and I need to check if it's still botting 30 minutes later. Will we still receive a warning on the actual client?
