Most of his games are ladder but some are custom. Yeah, but I like ThisIsJimmmy because he only really plays Ladder. Just watch the game when it is done. He is top Masters. Bounces around 1-6. I do like Custom matches, but people play Custome to practice and they really do not play to win all the time. It is more if this works great and if not gg. Ladder abusers still exist and it is taking Blizzard WAY TOO LONG to ban them, The #1 ranked player on the ladder is 172-0 with 3032 MMR, he has been sitting at the top of the ladder with 1 ONE game (technically if you look at his stats, all of his games except one are 'Undecided' matches). StarCraft®: Remastered upgrades the essential sci-fi strategy experience from beginning to end. Welcome back to the original game and its award-winning expansion, StarCraft: Brood War. We've remastered our units, buildings, and environments, improved game.
Server Status
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).
Your sc2 ladder rankings since 2013. StarCraft 2 ladder rankings and statistics over time for players and teams. Search for players and see world, region and league rankings for 1v1 teams. All data is updated daily by fetching the current sc2 ladder standings from battle net. StarCraft: Remastered is a remastered edition of the 1998 real-time strategy video game StarCraft and its expansion Brood War, which was released on August 14, 2017.It retains the gameplay of the original StarCraft, but features ultra-high-definition graphics (ultra HD), re-recorded audio, and Blizzard's modern online feature suite.
Next reset on Nov. 27, 2020, aprox. 11:59 PM UTC.
| Client | Status | Game | Host Bot | Away Bot | Map | Duration | Win | Properties |
|---|
Bots
0 items| 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 |
Detailed Results
Detailed Results Legend
The End Type column gives some detail about how the game ended. This table explains each end type. Lowko starcraft remastered. 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 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. |
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.
| 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) |
Results Summary
| 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 |
Bot files
Register
Forgot
Server Status
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.
| Client | Status | Game | Host Bot | Away Bot | Map | Duration | Win | Properties |
|---|
Bots
| 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) |
Results Summary
| 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 |
Bot files
Register
Forgot
Server Status
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.
| Client | Status | Game | Host Bot | Away Bot | Map | Duration | Win | Properties |
|---|
Bots
0 items| 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 |
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 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. |
Starcraft 2 Rank System
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.
| 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) |
Sc2 Gm Ladder
1/1Results Summary
| 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 |
Bot files
Register
Forgot
