Go To: Results Overview. Click column header to sort. Sort multiple columns by holding shift.

Detailed Results Legend

The End Type column gives some detail about how the game ended. This table explains each end type. Only games in which at least one bot ended the game 'normally' and counted a final game frame greater than zero (see Duration column) are counted in the results summary.

End TypeDescriptionGame Counted?
NORMAL Game ended because a bot won normally, or the game reached the time limit (higher score wins), or one bot took too long to process one or more frames. Yes
GAME_STATE_NOT_UPDATED_60S The gamestate file (output from TournamentModule once game is running) wasn't updated for 60 seconds, but Starcraft is still running. If "Duration" is greater than 00:00:00
STARCRAFT_CRASH Crash detected by Tournament Manager client, which means that Starcraft was running at some point, but later the client couldn't find the Starcraft process.
GAME_STATE_NEVER_DETECTED No gamestate file (output from TournamentModule once game is running) detected by time limit (60s), but StarCraft is running.
STARCRAFT_NEVER_DETECTED No gamestate file (output from TournamentModule once game is running) detected by time limit (60s), and StarCraft never detected running.
GAME_STATE_NOT_UPDATED_60S_BOTH_BOTS Gamestate file wasn't updated for 60 seconds (both bots); assigned after the fact (detailed results only); can't know which bot (if any) is responsible. No (Winner/Loser is arbitrary)
NO_REPORT Only one report received; assigned after the fact (detailed results only); this could be caused by the Tournament Manager client crashing, or a network error, etc.

Timeouts: W 55, L 1000, etc. record the number of times a bot (winner or loser) took longer than 55, 1000, etc. ms to process a frame. If a bot exceeds the max, it loses the game.

Games: 0
Round/Game Winner Loser Crash Timeout Map Duration End Type W Score L Score (W-L)/Max W 55 W 1000 W 10000 L 55 L 1000 L 10000 Win Addr Lose Addr Start Finish