FANDOM


Spr04b51

Results Edit

Poll1651

Tuesday, May 25th, 2004

Ulti's Analysis Edit

Poll 1651
Round Division 16 Semi Final
Match # 51
Match Date Tuesday, May 25th, 2004
Vote difference 13,753
Oracle
Expectations
Chrono Trigger - 70.88%
57 for - 0 against
GameFAQs
Prediction
Chrono Trigger - 61.95%
(25,362 brackets)

Coming into this matchup, Super Mario World was supposed to be strong enough to make this another Mario vs Crono type of match. After all, Super Mario World beat the holy hell out of Sonic 2 in a 70-30 rout, while Chrono Trigger lost a whole lot of percentage against Super Mario RPG through the day. As such, it looked like Super Mario World was on the upset track, while Chrono Trigger looked like it had to struggle through both of its matchups. The pre-match hype, as always, was all over the place as the match built itself up.

Yet once the match began, it was absolutely clear that Chrono Trigger was no joke in this contest. In a match that was supposed to be a trap for Chrono Trigger, it jumped out to a quick 63-37 lead and never looked back. This disappointed a lot of the people who were looking for drama after a long string of easy matches, but that's simply the way it was. Chrono Trigger, despite its troubles, was a strong game in this contest. Another thing to remember is the competition it faced. Secret of Mana, Super Mario RPG, and Super Mario World are damned strong competition. I mean, 2 Square RPGs and a mainstream Mario title? Losing percentage in the day against those three is perfectly okay.

Speaking of which, Chrono Trigger managed to continue to worry the people who had it in the finals when it dipped all the way down to 58.75% before making a small recovery to get near 60% again. But the damage was done long before any of this went down. Super Mario World looked prime for the upset in this match, and some people even gave it a chance to win the division before this match took place. But in the end, Chrono Trigger easily shook off Super Mario World like a bad case of the fleas to cement its status as a favorite in the division. But this was all covered in the last round, as the favorites were clearly Chrono Trigger, Link to the Past, and Final Fantasy 6. Chrono Trigger did its part in this match, and it was now time for the next match to defeat the hopes of another one of the favorites.

One final thing to note, and that is that Chrono Trigger's vote total had gone down in each of its first three matches to this point. Whether or not this was a warning sign remained to be seen.

Match Trends Edit

Graph1651

External Links Edit

Previous Match       • Next Match

2004 Spring Contest Matches

Round One
SMB3 > Metal Gear
Metroid > Pac-Man
Contra > Phantasy Star
FF > Pitfall
Donkey Kong > Duck Hunt
Zelda > Adventure
Pong > River City Ransom
Tetris > Galaga
CT > Secret of Mana
SMRPG > Street Fighter II
Sonic 2 > Shining Force
SMW > Simpsons
Zelda: LttP > Gunstar Heroes
Super Metroid > PS IV
Doom > Earthbound

FF VI > Mortal Kombat
FF VII > Suikoden II
Xenogears > Pokemon GSC
FFT > DDR
MGS > RE
SotN > Perfect Dark
Goldeneye > PDS
SM64 > NiGHTS
Zelda: OoT > Fallout 2
Starcraft > Halo
KH > Soul Calibur
Zelda: WW > Skies of Arcadia
Metroid Prime > Half-Life
FFTA > Fire Emblem
FF X > Shenmue
GTA: Vice City > KoTOR
SSBM > MGS 2

Round Two
SMB 3 > Metroid
FF > Contra
Zelda > Donkey Kong
Tetris > Pong
CT > SMRPG
SMW > Sonic 2
Zelda: LttP > Super Metroid
FF VI > Doom
FF VII > Xenogears
MGS > FFT
Goldeneye > SotN
Zelda: OoT > SM64
Starcraft > KH
Zelda: WW > Metroid Prime
FF X > FFTA
SSBM > GTA: Vice City

R3 and following
SMB3 > FF
Zelda > Tetris
CT > SMW
Zelda: LttP > FF VI
FF VII > MGS
Zelda: OoT > Goldeneye
Starcraft > Zelda: WW
SSBM > FF X
SMB3 > Zelda
CT > Zelda: LttP
FF VII > Zelda: OoT
SSBM > Starcraft
CT > SMB3
FF VII > SSBM
FF VII > CT (Finals)

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.