I'm not sure what the right section for this is but:
I'd like to have a killswitch built into a script. I have a buffbot that I run but I work from a lot of different computers so I'd like to be able to stop him and work on him from somewhere else and sometimes it would be nice if certain other people could take control of the Buffbot for a special case. As it stands, by bot uses the built in Buffbot functionality. It uses it for 10 turns then checks some things then does another ten turns. I see that gap of checking for other things as my opportunity to have it meet some criteria and call the logout or exit command. The question I have is what should he check. The built in buffbot function deletes kmails but saves donations, from what I can tell. Perhaps something in an enclosed donation?
Any ideas?
I'd like to have a killswitch built into a script. I have a buffbot that I run but I work from a lot of different computers so I'd like to be able to stop him and work on him from somewhere else and sometimes it would be nice if certain other people could take control of the Buffbot for a special case. As it stands, by bot uses the built in Buffbot functionality. It uses it for 10 turns then checks some things then does another ten turns. I see that gap of checking for other things as my opportunity to have it meet some criteria and call the logout or exit command. The question I have is what should he check. The built in buffbot function deletes kmails but saves donations, from what I can tell. Perhaps something in an enclosed donation?
Any ideas?