Starcraft Remastered Ladder

broken image


Server Status

Return to Glory Prepare to rediscover a classic. StarCraft: Remastered upgrades Blizzard Entertainment's original sci-fi real-time strategy game and its acclaimed expansion, StarCraft: Brood War, from beginning to end. Experience the intergalactic battle between the terran, protoss, and zerg with improved graphics and audioand the same classic gameplay that made StarCraft a global phenomenon. To play a ladder match, click the Multiplayer menu item in the top left, select a mode from 1v1, 2v2, 3v3, or 4v4, select a race, and then click Find Match. After playing in five placement matches within one mode (e.g. Five 1v1 matches) you will be placed in a ladder for that mode.

Nov. 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.

Sc2 current ladder maps
ClientStatusGameHost BotAway BotMapDurationWinProperties

Bots

0 items
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
No bots registered!
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active

Detailed Results

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?
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. Logic pro audio effects. If a bot exceeds the max, it loses the game.

Crashes
Bots
Loser
0 Items
ProtossTerranZergRandom
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 Remastered Ladder
ClientStatusGameHost BotAway BotMapDurationWinProperties

Bots

0 items
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active
No bots registered!
Bot NameRaceAuthorOrganizationTypeBWAPI VersionLast Updated(UTC)Active

Detailed Results

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?
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. Logic pro audio effects. If a bot exceeds the max, it loses the game.

Crashes
Bots
Loser
0 Items
ProtossTerranZergRandom
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/1

Starcraft 2 Rank System

Results Summary

BotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout
No result
BotGamesWinsLossesWin %ELOAvg TimeGame Time LimitCrashFrame Timeout

Sc2 Gm Ladder


Bot files

Sc2 Current Ladder Maps

Register

Forgot





broken image