This version is more robust, thank you!
Is it possible to give session totals if the script stops due to dropped event?
I just did a 50 iteration 2 chain run and one chain ran to completion, the other chain stopped at 47. Last entry in the gCLI was Waiting for MMG event... After several minutes of no more MMG action, (using the default 30 second wait) I checked and there were no pending bets from me.
So I'm assuming the script had stopped due to a dropped event. Then I thought that it would be nice to see totals up to the point the script stopped, and notification that the script has stopped due to a dropped event.
Or, since these are both very minor points, I guess you could just wait and see if your bug report bears fruit instead of adding functionality that may be made obsolete soon.
Is it possible to give session totals if the script stops due to dropped event?
I just did a 50 iteration 2 chain run and one chain ran to completion, the other chain stopped at 47. Last entry in the gCLI was Waiting for MMG event... After several minutes of no more MMG action, (using the default 30 second wait) I checked and there were no pending bets from me.
So I'm assuming the script had stopped due to a dropped event. Then I thought that it would be nice to see totals up to the point the script stopped, and notification that the script has stopped due to a dropped event.
Or, since these are both very minor points, I guess you could just wait and see if your bug report bears fruit instead of adding functionality that may be made obsolete soon.