TinyVM Connect4 Tournament – Specific Matchup
random_legal against random_legal
This page is about how random_legal fares as an attacker against random_legal. There's a different page for the reverse matchup. For a more general overview, visit the overview page.
This matchup is not deterministic.
The Games
Game type #1 (seen 1 time)
Loss due to connect4. (Executed 1142 instructions in total; opponent executed 1140 instructions in total.)
| #18 | #19 | |||||
| #16 | #17 | |||||
| #20 | #15 | #14 | ||||
| #21 | #12 | #4 | #13 | |||
| #6 | #22 | #23 | #11 | #3 | #8 | |
| #5 | #9 | #10 | #2 | #1 | #7 | #24 |
Game type #2 (seen 1 time)
Loss due to connect4. (Executed 1426 instructions in total; opponent executed 1422 instructions in total.)
| #26 | #19 | #29 | ||||
| #22 | #18 | #23 | ||||
| #30 | #24 | #21 | #15 | #17 | ||
| #25 | #20 | #16 | #13 | #10 | ||
| #14 | #4 | #28 | #11 | #27 | #12 | #5 |
| #8 | #3 | #7 | #6 | #1 | #9 | #2 |
Game type #3 (seen 1 time)
Win due to connect4. (Executed 672 instructions in total; opponent executed 576 instructions in total.)
| #13 | ||||||
| #11 | #12 | |||||
| #3 | #7 | #8 | #10 | |||
| #1 | #5 | #2 | #6 | #9 | #4 |
Game type #4 (seen 1 time)
Loss due to connect4. (Executed 1238 instructions in total; opponent executed 1236 instructions in total.)
| #15 | ||||||
| #25 | #22 | #13 | ||||
| #26 | #18 | #21 | #9 | #20 | ||
| #23 | #12 | #19 | #8 | #17 | ||
| #11 | #10 | #2 | #6 | #16 | ||
| #7 | #4 | #3 | #1 | #24 | #5 | #14 |
Game type #5 (seen 1 time)
Win due to connect4. (Executed 864 instructions in total; opponent executed 768 instructions in total.)
| #17 | ||||||
| #9 | ||||||
| #7 | #15 | #16 | ||||
| #5 | #6 | #12 | #10 | #13 | ||
| #4 | #8 | #3 | #14 | #11 | #2 | #1 |
Game type #6 (seen 1 time)
Win due to connect4. (Executed 480 instructions in total; opponent executed 384 instructions in total.)
| #2 | #8 | |||||
| #1 | #7 | #5 | #9 | #6 | #4 | #3 |
Game type #7 (seen 1 time)
Win due to connect4. (Executed 672 instructions in total; opponent executed 576 instructions in total.)
| #13 | ||||||
| #11 | ||||||
| #8 | #10 | #7 | #5 | |||
| #6 | #1 | #12 | #4 | #3 | #2 | #9 |
Game type #8 (seen 1 time)
Win due to connect4. (Executed 1238 instructions in total; opponent executed 1146 instructions in total.)
| #18 | #24 | |||||
| #16 | #23 | |||||
| #20 | #13 | #22 | ||||
| #19 | #12 | #25 | #9 | #21 | #17 | |
| #14 | #8 | #15 | #6 | #5 | #11 | |
| #7 | #1 | #2 | #3 | #4 | #10 |
Game type #9 (seen 1 time)
Win due to connect4. (Executed 1530 instructions in total; opponent executed 1438 instructions in total.)
| #30 | #28 | |||||
| #23 | #27 | #26 | ||||
| #22 | #19 | #20 | #24 | #17 | ||
| #15 | #18 | #25 | #9 | #31 | #5 | #16 |
| #13 | #14 | #21 | #7 | #29 | #2 | #11 |
| #8 | #10 | #3 | #4 | #12 | #1 | #6 |
Game type #10 (seen 1 time)
Win due to connect4. (Executed 480 instructions in total; opponent executed 384 instructions in total.)
| #3 | ||||||
| #2 | #8 | |||||
| #4 | #7 | #5 | #1 | #9 | #6 |
Game type #11 (seen 1 time)
Win due to connect4. (Executed 1050 instructions in total; opponent executed 956 instructions in total.)
| #16 | ||||||
| #15 | ||||||
| #13 | #20 | #21 | ||||
| #7 | #9 | #14 | #19 | |||
| #6 | #8 | #10 | #17 | #18 | ||
| #3 | #2 | #4 | #5 | #1 | #12 | #11 |
Game type #12 (seen 1 time)
Win due to connect4. (Executed 1318 instructions in total; opponent executed 1224 instructions in total.)
| #15 | #23 | #18 | ||||
| #27 | #12 | #22 | #17 | |||
| #25 | #8 | #19 | #11 | |||
| #21 | #6 | #16 | #10 | #26 | ||
| #13 | #5 | #14 | #7 | #24 | ||
| #2 | #3 | #9 | #1 | #20 | #4 |
Game type #13 (seen 1 time)
Win due to connect4. (Executed 1786 instructions in total; opponent executed 1694 instructions in total.)
| #36 | #27 | #25 | #24 | |||
| #35 | #26 | #20 | #34 | #37 | #23 | |
| #31 | #16 | #19 | #32 | #29 | #22 | |
| #30 | #12 | #13 | #18 | #17 | #14 | #33 |
| #21 | #9 | #4 | #15 | #11 | #8 | #28 |
| #1 | #3 | #2 | #10 | #6 | #5 | #7 |
Game type #14 (seen 1 time)
Win due to connect4. (Executed 1248 instructions in total; opponent executed 1152 instructions in total.)
| #24 | #18 | |||||
| #25 | #16 | #17 | ||||
| #22 | #11 | #15 | #8 | #20 | #23 | |
| #19 | #9 | #13 | #12 | #3 | #14 | #21 |
| #4 | #2 | #10 | #5 | #1 | #7 | #6 |
Game type #15 (seen 1 time)
Win due to connect4. (Executed 1248 instructions in total; opponent executed 1152 instructions in total.)
| #22 | #23 | |||||
| #25 | #14 | #24 | #17 | |||
| #15 | #12 | #20 | #8 | #21 | ||
| #13 | #7 | #19 | #6 | #16 | #5 | #18 |
| #9 | #4 | #11 | #1 | #3 | #2 | #10 |
Game type #16 (seen 1 time)
Win due to connect4. (Executed 960 instructions in total; opponent executed 864 instructions in total.)
| #12 | #15 | |||||
| #11 | #19 | #8 | ||||
| #10 | #18 | #17 | #6 | |||
| #7 | #14 | #9 | #3 | |||
| #4 | #13 | #5 | #1 | #2 | #16 |
Game type #17 (seen 1 time)
Win due to connect4. (Executed 576 instructions in total; opponent executed 480 instructions in total.)
| #7 | ||||||
| #5 | #8 | |||||
| #10 | #4 | #2 | ||||
| #6 | #9 | #3 | #1 | #11 |
Game type #18 (seen 1 time)
Win due to connect4. (Executed 384 instructions in total; opponent executed 288 instructions in total.)
| #6 | ||||||
| #2 | #4 | #3 | #1 | #5 | #7 |
Game type #19 (seen 1 time)
Win due to connect4. (Executed 1608 instructions in total; opponent executed 1518 instructions in total.)
| #31 | #24 | #28 | #29 | #32 | ||
| #27 | #23 | #16 | #26 | #30 | ||
| #25 | #22 | #9 | #18 | #21 | ||
| #20 | #19 | #6 | #15 | #12 | ||
| #14 | #17 | #33 | #5 | #13 | #10 | |
| #7 | #11 | #1 | #4 | #8 | #3 | #2 |
Game type #20 (seen 1 time)
Win due to connect4. (Executed 768 instructions in total; opponent executed 672 instructions in total.)
| #10 | #14 | |||||
| #13 | #12 | #9 | #3 | #11 | #15 | |
| #2 | #7 | #8 | #4 | #1 | #5 | #6 |
Game types #21 through #100
Sorry, the other game types (spanning 80 games) aren't listed to keep this HTML file reasonably small. If you're interested, the other game types in this matchup can be easily extracted from the JSON file. Give it a try!
This page was last rebuilt on 2023-06-28 02:02:32 CEST.
The raw data on this webpage is also available as a JSON file.