Starcraft Remastered Ladder

Return to site

Starcraft Remastered Ladder

YSK there is a 3v3 BGH Automated Ladder in StarCraft Remastered: A good entry way for new players to learn the game in a fun environment and still feel competitive Discussion The TeamLiquid Thread. According to Blizzard on a post at the official Blizzard forums, previously Matchmaking and Ladder features were going to be free for both StarCraft: Remastered and StarCraft Anthology players. Another elder scrolls.
Server StatusNov. 22, 2020: Tournament reset, including result summaries, bot read/write dirs, and games.
Map pool updated to 2020 AIIDE Starcraft AI Competition maps (available here).
Next reset on Nov. 27, 2020, aprox. 11:59 PM UTC.
Starcraft 2 Ladder

ClientStatusGameHost BotAway BotMapDurationWinProperties
Bots0 itemsBot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
 No bots registered! 
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
Detailed ResultsDetailed Results Legend3d software free. 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?
NORMALGame 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_60SThe 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_CRASHCrash 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_DETECTEDNo gamestate file (output from TournamentModule once game is running) detected by time limit (60s), but StarCraft is running.
STARCRAFT_NEVER_DETECTEDNo 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_BOTSGamestate 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_REPORTOnly 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. Resilio sync 2 6 4. If a bot exceeds the max, it loses the game. https://jzcxnl.over-blog.com/2021/01/mac-cell-phone.html.
Crashes
Bots
Loser
0 ItemsProtossTerranZergRandom
Round / GameStart DateWinnerLoserCrashTimeoutMapGame TimeWall TimeEnd TypeW ScoreL ScoreWinner Timeout (55/1000/10000)Loser Timeout (55/1000/10000)
 No result 
Round / GameStart DateWinnerLoserCrashTimeoutMapGame TimeWall TimeEnd TypeW ScoreL ScoreWinner Timeout (55/1000/10000)Loser Timeout (55/1000/10000)
Starcraft 2 Leaderboard page: 1/1Results SummaryBotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout
 No result 
BotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout

Bot filesRegister

Bot Name	Race	Author	Organization	Type	BWAPI Version	Last Updated(UTC)	Active
No bots registered!
Bot Name	Race	Author	Organization	Type	BWAPI Version	Last Updated(UTC)	Active

End Type	Description	Game 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.

ProtossTerranZergRandom
Round / Game	Start Date	Winner	Loser	Crash	Timeout	Map	Game Time	Wall Time	End Type	W Score	L Score	Winner Timeout (55/1000/10000)	Loser Timeout (55/1000/10000)
No result
Round / Game	Start Date	Winner	Loser	Crash	Timeout	Map	Game Time	Wall Time	End Type	W Score	L Score	Winner Timeout (55/1000/10000)	Loser Timeout (55/1000/10000)

Bot	Games	Wins	Losses	Win %	ELO	Avg Time	Game Time Limit	Crash	Frame Timeout
No result
Bot	Games	Wins	Losses	Win %	ELO	Avg Time	Game Time Limit	Crash	Frame Timeout

ClientStatusGameHost BotAway BotMapDurationWinProperties
Bots0 itemsBot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
 No bots registered! 
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
Detailed ResultsDetailed Results Legend3d software free. 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?
NORMALGame 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_60SThe 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_CRASHCrash 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_DETECTEDNo gamestate file (output from TournamentModule once game is running) detected by time limit (60s), but StarCraft is running.
STARCRAFT_NEVER_DETECTEDNo 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_BOTSGamestate 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_REPORTOnly 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. Resilio sync 2 6 4. If a bot exceeds the max, it loses the game. https://jzcxnl.over-blog.com/2021/01/mac-cell-phone.html.
Crashes
Bots
Loser
0 ItemsProtossTerranZergRandom
Round / GameStart DateWinnerLoserCrashTimeoutMapGame TimeWall TimeEnd TypeW ScoreL ScoreWinner Timeout (55/1000/10000)Loser Timeout (55/1000/10000)
 No result 
Round / GameStart DateWinnerLoserCrashTimeoutMapGame TimeWall TimeEnd TypeW ScoreL ScoreWinner Timeout (55/1000/10000)Loser Timeout (55/1000/10000)
Starcraft 2 Leaderboard page: 1/1Results SummaryBotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout
 No result 
BotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout

Bot filesRegisterForgotServer StatusNov. 22, 2020: Tournament reset, including result summaries, bot read/write dirs, and games.
Map pool updated to 2020 AIIDE Starcraft AI Competition maps (available here).
Free 3d human maker. Built in camera. Next reset on Nov. 27, 2020, aprox. 11:59 PM UTC.
ClientStatusGameHost BotAway BotMapDurationWinProperties
Bots0 itemsBot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
 No bots registered! 
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
Detailed ResultsDetailed Results LegendThe End Type column gives some detail about how the game ended. This table explains each end type. Interactive ruler games. 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?
NORMALGame 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_60SThe 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_CRASHCrash 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_DETECTEDNo gamestate file (output from TournamentModule once game is running) detected by time limit (60s), but StarCraft is running.
STARCRAFT_NEVER_DETECTEDNo 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_BOTSGamestate 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_REPORTOnly 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.
Crashes
Bots
Loser
0 ItemsProtossTerranZergRandom
Round / GameStart DateWinnerLoserCrashTimeoutMapGame TimeWall TimeEnd TypeW ScoreL ScoreWinner Timeout (55/1000/10000)Loser Timeout (55/1000/10000)
 No result 
Round / GameStart DateWinnerLoserCrashTimeoutMapGame TimeWall TimeEnd TypeW ScoreL ScoreWinner Timeout (55/1000/10000)Loser Timeout (55/1000/10000)
 page: 1/1Results SummaryBotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout
 No result 
BotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout

Bot filesRegisterForgot