You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Real-time performance requirements in competition disincentivize bots from logging directly to disk. The incentive is instead to flush logs at the end.
However, if a client bot's pipe connection to StarCraft is broken, no further event handlers are called, leaving the bot without a last-ditch chance to flush logs.
Proposed feature: An onTermination() handler which is always called after a game, even in event of disconnection. This handler is called with the expectation that BWAPI is no longer accessible. This would allow bots a chance to flush any logs if they haven't already.
The text was updated successfully, but these errors were encountered:
Real-time performance requirements in competition disincentivize bots from logging directly to disk. The incentive is instead to flush logs at the end.
However, if a client bot's pipe connection to StarCraft is broken, no further event handlers are called, leaving the bot without a last-ditch chance to flush logs.
Proposed feature: An
onTermination()
handler which is always called after a game, even in event of disconnection. This handler is called with the expectation that BWAPI is no longer accessible. This would allow bots a chance to flush any logs if they haven't already.The text was updated successfully, but these errors were encountered: