|
Editorials 
Metroid: Retro's Poison
- By Ryan
Eid
NFL Football: Canned. Dune Racer: Canned. Raven Blade: Canned. Current project: Metroid. And that's it.
The company claiming to "make games fun again" isn't even making games. They are making one game, with the most powerful and successful developer in the world riding their backs all the way. This can't be good. What a year ago looked like a promising US-based Nintendo-only development team has turned into a maligned, out of control mess a year later.
But it isn't Retro's fault. Nintendo is stunting them incredibly. Nintendo is forcing something on them that the team is not ready for. It's like putting a single-A prospect into the 7th game of the World Series to face Randy Johnson. It just isn't going to work, and Nintendo should've realized this. Nintendo should've given Retro time to bloom. Let them get a few games under their belt like NFL Football or Raven Blade. Allow them to learn to work together cohesively as a unit, allow them to be familiarized with their coworkers' styles, and the architecture of the GameCube. Just because you've learned to walk doesn't mean you should be entered into the Olympics.
Metroid is a beast that Retro cannot tame. Why did Nintendo give it to them, then? "They wanted to make a splash" said one former Retro employee. "We had some Metroid fans in the office who were both thrilled and scared. Retro realized it was a great license, but we were also worried about the backlash from making it a first-person adventure game. We didn't want to be known as the studio that ruined Metroid." And Nintendo certainly doesn't want to be known as "the company that gave Metroid to an unworthy developer." So, as a result, Nintendo is forcing Retro to focus. No other projects can be worked on. If you are unworthy, you are fired. Metroid must come out and come out properly, not for Retro's sake, but for Nintendo's. Nintendo is slave-driving Retro beyond their means.
Retro, sadly cannot do anything about it. Nintendo owns them, pays the bills and has given them the opportunity of a lifetime. But at what cost? At the cost of dozens of workers, several promising titles, and pent up frustration toward Nintendo and gaming. Nintendo should realize patience is needed. Retro was obviously not ready for this. They didn't ask for this. It's not like NST with Wave Race. NST asked for it. NST felt comfortable that they could properly create Blue Storm. Metroid was thrusted upon Retro.
And Retro doesn't even have much say in the game design. The game will follow through Miyamoto's whims, and Retro will be forced to comply, because all their base is belong to EAD. EAD is the company that created Mario and Zelda, who is Retro to disagree? It's like giving a five year old a Rubix cube, but looking over his shoulder and taking it from him every so often and yelling "no! Turn this piece this way! You must align these colors over here, or it won't work! Here, take it back and do it right." The only difference is millions of fans will not be counting on this kid completing a rubix cube, only adding to the pressure.
In Nintendo's attempt to make a splash by giving Metroid to a young, promising team, they have corrupted a developer and doomed a franchise. Nintendo has clipped Retro's wings and forced it into constant work, while breathing down their necks. Don't blame Retro, people. Blame Nintendo. They've irresponsibly handed out Metroid to a house that just isn't ready for it. I would've loved to have seen Raven Blade, or NFL Football, but I guess Metroid is just too important to Nintendo's reputation. It's all about the dollars. It makes you wonder if Nintendo's new slogan should be "Making developers jaded again."
|
 |
|
QUOTE: |
| "Don't blame Retro, people. Blame Nintendo. They've irresponsibly handed out Metroid to a house that just isn't ready for it. " |
|
.gif)
