1. A description of the suggestion

This would be focused towards CLI usage in which a flag would cause the client to write any failed launches to a provided log file name in OSBot directory then the client close itself

It would be cool if this could write the log file anywhere the client has access to -- but not necessary.

The failed launched conditions i mentioned would be any such as
-Bot intialzation errors
-Bad proxy connection
-failed hooks (bot initialization??)
-client out of date
-script not found
-etc

A bit extra for this suggestion is allow login responses to be written to a file too. ;)

 

2. How will this suggestion impact scripters and/or botters?

This would be very useful for automated management of multiple bots at once, the ability to monitor failures which can't be overriden by scripts. Anyone who has the ability to write a little bit of code would find this very useful in bot management.

 

3. Post any examples such as code or pictures to supplement your description (optional)

Something simple like
A master flag such as 
-verbose

And some child flags like
-failure {filename}.txt -loginResponse {filename).txt

Not a bad idea but I'm pretty sure you can do this already without help from OSBot. Also sometimes errors can arise for a variety of reasons, which makes it sometimes difficult to say "it was because of xyz reason".