TinyVM Connect4 Tournament – Specific Matchup
random_legal against horizontal_mod
This page is about how random_legal fares as an attacker against horizontal_mod. 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 1152 instructions in total; opponent executed 60 instructions in total.)
| #23 | ||||||
| #21 | ||||||
| #16 | #20 | #14 | ||||
| #9 | #18 | #17 | #22 | #13 | ||
| #7 | #11 | #15 | #8 | #24 | #19 | #3 |
| #2 | #4 | #6 | #5 | #10 | #12 | #1 |
Game type #2 (seen 1 time)
Loss due to connect4. (Executed 1248 instructions in total; opponent executed 65 instructions in total.)
| #25 | ||||||
| #20 | #22 | #24 | #26 | |||
| #23 | #18 | #15 | #13 | #19 | #12 | #21 |
| #16 | #11 | #9 | #8 | #17 | #7 | #14 |
| #2 | #4 | #6 | #5 | #10 | #1 | #3 |
Game type #3 (seen 1 time)
Loss due to connect4. (Executed 1152 instructions in total; opponent executed 60 instructions in total.)
| #20 | ||||||
| #17 | #19 | #24 | ||||
| #16 | #18 | #15 | #22 | #13 | #14 | |
| #3 | #11 | #6 | #21 | #10 | #23 | #9 |
| #2 | #4 | #5 | #8 | #7 | #12 | #1 |
Game type #4 (seen 1 time)
Loss due to connect4. (Executed 384 instructions in total; opponent executed 20 instructions in total.)
| #7 | #5 | |||||
| #2 | #4 | #6 | #8 | #1 | #3 |
Game type #5 (seen 1 time)
Win due to connect4. (Executed 864 instructions in total; opponent executed 40 instructions in total.)
| #17 | ||||||
| #15 | ||||||
| #13 | ||||||
| #7 | ||||||
| #16 | #9 | #6 | #8 | #11 | #12 | |
| #2 | #4 | #1 | #3 | #10 | #5 | #14 |
Game type #6 (seen 1 time)
Win due to opponent's attempt to move at full column 1. (Executed 1520 instructions in total; opponent executed 80 instructions in total.)
| #21 | #25 | #31 | ||||
| #18 | #20 | #28 | ||||
| #15 | #17 | #29 | #24 | #27 | ||
| #30 | #5 | #7 | #22 | #19 | #23 | |
| #16 | #4 | #6 | #11 | #13 | #26 | #14 |
| #2 | #3 | #1 | #8 | #10 | #12 | #9 |
Game type #7 (seen 1 time)
Win due to connect4. (Executed 1436 instructions in total; opponent executed 70 instructions in total.)
| #26 | #29 | |||||
| #23 | #25 | #28 | ||||
| #18 | #22 | #27 | #13 | #21 | ||
| #17 | #15 | #24 | #12 | #14 | ||
| #16 | #11 | #20 | #8 | #19 | #7 | #9 |
| #2 | #4 | #6 | #1 | #10 | #5 | #3 |
Game type #8 (seen 1 time)
Win due to connect4. (Executed 960 instructions in total; opponent executed 45 instructions in total.)
| #19 | ||||||
| #17 | ||||||
| #16 | #9 | #15 | #14 | |||
| #5 | #18 | #7 | #8 | #12 | #13 | |
| #2 | #4 | #6 | #1 | #10 | #3 | #11 |
Game type #9 (seen 1 time)
Win due to opponent's attempt to move at full column 0. (Executed 1436 instructions in total; opponent executed 75 instructions in total.)
| #29 | #25 | |||||
| #17 | #22 | |||||
| #16 | #27 | #13 | #28 | |||
| #11 | #18 | #23 | #8 | #24 | #26 | #21 |
| #2 | #4 | #20 | #7 | #19 | #12 | #15 |
| #1 | #3 | #6 | #5 | #10 | #9 | #14 |
Game type #10 (seen 1 time)
Win due to connect4. (Executed 384 instructions in total; opponent executed 15 instructions in total.)
| #2 | #4 | #6 | #7 | #1 | #3 | #5 |
Game type #11 (seen 1 time)
Loss due to connect4. (Executed 384 instructions in total; opponent executed 20 instructions in total.)
| #3 | #7 | #5 | ||||
| #2 | #4 | #6 | #8 | #1 |
Game type #12 (seen 1 time)
Win due to opponent's attempt to move at full column 1. (Executed 1528 instructions in total; opponent executed 80 instructions in total.)
| #30 | #25 | #31 | ||||
| #29 | #23 | #28 | ||||
| #16 | #18 | #27 | #17 | |||
| #9 | #7 | #21 | #22 | #24 | #26 | #15 |
| #5 | #4 | #20 | #19 | #11 | #12 | #14 |
| #2 | #3 | #6 | #8 | #10 | #1 | #13 |
Game type #13 (seen 1 time)
Loss due to connect4. (Executed 384 instructions in total; opponent executed 20 instructions in total.)
| #5 | ||||||
| #2 | #4 | #6 | #8 | #1 | #7 | #3 |
Game type #14 (seen 1 time)
Win due to connect4. (Executed 1152 instructions in total; opponent executed 55 instructions in total.)
| #21 | #17 | |||||
| #16 | #20 | #14 | ||||
| #9 | #13 | #22 | #11 | |||
| #3 | #18 | #6 | #15 | #23 | #19 | #7 |
| #2 | #4 | #1 | #8 | #10 | #12 | #5 |
Game type #15 (seen 1 time)
Loss due to connect4. (Executed 384 instructions in total; opponent executed 20 instructions in total.)
| #7 | #3 | |||||
| #2 | #4 | #6 | #8 | #5 | #1 |
Game type #16 (seen 1 time)
Loss due to connect4. (Executed 1056 instructions in total; opponent executed 55 instructions in total.)
| #21 | #19 | |||||
| #20 | #17 | |||||
| #16 | #6 | #11 | #15 | |||
| #13 | #18 | #5 | #22 | #10 | #12 | #14 |
| #2 | #4 | #3 | #8 | #7 | #1 | #9 |
Game type #17 (seen 1 time)
Win due to connect4. (Executed 1526 instructions in total; opponent executed 75 instructions in total.)
| #23 | #29 | |||||
| #30 | #19 | #24 | ||||
| #16 | #18 | #25 | #31 | #17 | #27 | |
| #3 | #13 | #20 | #22 | #11 | #26 | |
| #2 | #5 | #15 | #21 | #10 | #12 | #28 |
| #1 | #4 | #6 | #8 | #9 | #7 | #14 |
Game type #18 (seen 1 time)
Loss due to connect4. (Executed 1248 instructions in total; opponent executed 65 instructions in total.)
| #18 | ||||||
| #15 | #25 | #22 | #26 | |||
| #16 | #9 | #20 | #17 | #24 | #21 | #14 |
| #11 | #5 | #13 | #8 | #23 | #19 | #7 |
| #2 | #4 | #6 | #1 | #10 | #12 | #3 |
Game type #19 (seen 1 time)
Win due to connect4. (Executed 1056 instructions in total; opponent executed 50 instructions in total.)
| #19 | ||||||
| #16 | #18 | |||||
| #15 | #13 | #21 | #17 | #11 | ||
| #3 | #9 | #20 | #8 | #10 | #14 | |
| #2 | #4 | #6 | #5 | #1 | #12 | #7 |
Game type #20 (seen 1 time)
Loss due to connect4. (Executed 960 instructions in total; opponent executed 50 instructions in total.)
| #15 | #14 | |||||
| #16 | #17 | #13 | #11 | |||
| #2 | #18 | #20 | #8 | #10 | #19 | #7 |
| #1 | #4 | #6 | #3 | #9 | #12 | #5 |
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.