One-line AI headline and voting-anomaly flags for every contest match, from a
ChatGPT pass over the Board 8
wiki writeups (CC BY-SA 3.0). Machine-generated — may contain mistakes.
The full narrative shows under each row
(hide narratives).
Researching with your own AI? Grab the Board 8 wiki corpus for context.
See also: AI Contest Summaries
Contest:
All · SC2K2 · SC2K3 · Spring 2K4 · SC2K4 · Spring 2K5 · SC2K5 · BSE2K6 · CB2K6 · CB VI · CB VII · BGE 2K9 · CB VIII · GOTD · Rivalry · CB IX · BGE 2K15 · Best Year · CB X · GOTD 2
Anomaly:
any · SFF · LFF · Rally · Cheat · Pic · off-topic writeups
Round:
all · Wildcard · Round 1 · Round 2 · Round 3 · Division Semifinal · Division Final · Legends · Redemption · Final Nine · Quarterfinal · Semifinal · Final · Final Battle · Tournament of Champions · Battle Royale · Bonus (round labels are specific to contests)
Filtered:
entrant = Yoshi · anomaly = SFF — 5 of 1,514 matches
show all
5 matches
| # |
Poll ▼ | Contest | Round | Division |
Result |
Headline |
SFF |
LFF |
Rally |
Cheat |
Pic |
n |
| 1 |
5225
writeup (md) |
CB IX |
Round 2 |
Division 1 |
|
Link SFFs Yoshi as Raiden takes second |
✓ |
|
|
|
|
1 |
|
Link won comfortably while Raiden secured second after Yoshi faded under heavy Nintendo overlap. The writeup also treats Link's low turnout as another sign that voters were tiring of his dominance.
SFF: The writeup says Yoshi tried to resist Link's SFF but could not stay competitive, allowing Raiden to take second in the Expert Challenge ordering.
|
| 2 |
2121
writeup (md) |
SC2K5 |
Division Final |
20XX |
|
Mega Man SFFs Yoshi and enters the Sonic match favored |
✓ |
|
|
|
|
1 |
|
Mega Man easily dispatched Yoshi and ended the divisional round. The writeup attributes Yoshi's underperformance partly to SFF and uses that result to swing the coming Sonic-Mega Man debate toward Mega Man.
SFF: The writeup explicitly says Mega Man likely SFFed Yoshi because voters associate Mega Man strongly with Nintendo-era games.
|
| 3 |
1766
writeup (md) |
SC2K4 |
Round 3 |
Hyrule |
|
Link overwhelms Yoshi in harsher-than-expected SFF |
✓ |
|
|
|
|
1 |
|
Link destroyed Yoshi in a predictable same-company matchup, but the degree of suppression surprised even people expecting SFF. The writeup treats the result as another intimidating sign of Link's championship strength.
SFF: The writeup explicitly calls Link versus Yoshi a straight SFF match and says the fanbase effect was even harsher than most expected, heavily suppressing Yoshi.
|
| 4 |
1751
writeup (md) |
SC2K4 |
Round 2 |
Hyrule |
|
Yoshi beats Luigi in a predictable Nintendo SFF matchup |
✓ |
|
|
|
|
1 |
|
Yoshi beat Luigi in a heavily debated Nintendo matchup that ultimately followed the available statistical clues more closely than the hype suggested. The writeup calls the result disappointingly predictable despite the same-fanbase conditions.
SFF: The writeup explicitly describes Yoshi versus Luigi as an SFF affair between Nintendo characters, though it notes that older extrapolated standings still predicted the matchup unusually well.
|
| 5 |
1342
writeup (md) |
SC2K3 |
Round 2 |
East |
|
Bowser overturns Yoshi expectations with an SFF victory |
✓ |
|
|
|
|
1 |
|
Bowser quickly erased Yoshi's brief opening lead and won a matchup most of the board had expected Yoshi to take. The writeup treats the result as both an upset of prevailing assumptions and a clear SFF performance.
SFF: The writeup says Bowser caught Yoshi and then laid an SFF beatdown on him, overturning expectations built from an earlier favorite-Mario-character poll.
|
What this is
Each row's Headline and (on filter) narrative come from a
ChatGPT reading of that match's Board 8 wiki writeup. The five flags
(SFF same-fanbase factor, LFF low-fanbase
factor, Rally outside rally, Cheat cheating
alleged, Pic match-picture factor) are set only when the writeup
asserts that effect — never inferred from the numbers. Hover a check for the
note. †OT marks a writeup that mostly wanders off the
match.
Want to do your own AI assisted research? Board 8 wiki pages are available in markdown format here.