I’ve written about Metroid‘s opening moments before. As a matter of fact, I wrote about them nearly seven years ago, making this the game that set me on the path of thinking about how level design works. (That article isn’t dated here, but the crossposted version on 1UP.com says “June 24, 2006” — apparently I’ve been banging the same drum for quite a while.) So now you know where the blame lies. Really, though, I’ve only fully analyzed the first few screens of the game without giving too much consideration to what lies beyond. After this first entry, I’m curious to see what I’ll have to say about Metroid.
I suspect a lot of it will be negative, because this is one of those early attempts to do something bold and brash and deep, and as such it was staking out territory no other game had properly charted. Sometimes, such endeavors involve missteps.
And fair enough. Great design is timeless, while innovative design belongs very much to its times. To properly understand Metroid, you need to cast your brain into the proper mindset. The year is 1986, and nearly every action game on the market is either a reaction to Super Mario Bros. or else was undertaken a little too late to be able to reflect the development community’s collective desire to make the next Mario by… trying to create a game exactly like Mario. In short, the market is suddenly glutted with games that try to imitate Mario‘s physics and rules, or else feel heartbreakingly primitive in their lack of comparative sophistication.
Metroid‘s designers, on the other hand, said, “Hey, let’s totally blow Mario out of the water.” They made a game that completely abandoned fundamental action game concepts like levels, scores, and ease of accessibility. It was a game with the sort of expansiveness you’d only have seen on a personal computer, except it ran on a console. That meant you didn’t have to control the action with arrow keys, it had good music, and it didn’t use black-and-white isometric graphics. It was like nothing else on consoles, which made it seem pretty awesome in its day. After all, its flaws didn’t seem quite so glaring when we didn’t have better efforts to compare it to.
Metroid kicks off with a degree of ceremony reminiscent of Namco’s classic arcade titles — like Xevious, Pac-Man, and Tower of Druaga, you hear a brief musical flourish before you begin play. The hero(ine) Samus materializes with a unique sprite (you only see it here and while riding the elevators between areas), then the action begins.
In 1986, side-scrolling games almost universally worked in one direction: Left to right. Look at Moon Patrol, Pac-Land, Super Mario Bros., Wonder Boy. Shooters like Gradius and Scramble cemented the auto-scrolling left-to-right horizontal format for that genre (Defender being little more than a strange blip in history). Even Rolling Thunder, which allowed some small amount of backtracking, offered the player no reason to walk left besides dropping back for tactical purposes. So why would Metroid be any different?
From the outset, Samus dashes right, gunning down what monsters she can draw a bead on — basically the pteranodon-like creatures that lurk on the ceiling and dive downward when Samus comes into range, launching a literal suicide attack by trying to skewer the heroine before lodging in the ground and exploding. These deathwish beasts serve their purpose, though: They teach players to aim and shoot upward and the value of rapid fire as advancing enemies will be halted for a frame or two of action when struck, allowing a rapid volley of shots to take down a speedy foe before it can collide with Samus.
Her line of fire unfortunately does not include Zoomers, the short spiky critters walking along the ground, as they move below the range of Samus’ blaster; sadly, she’s unable to duck and fire or aim downward. However, she can hit them when they climb on walls and ceilings: An observation you’re left to make at the end of the first room. Metroid operates on its own unique combat logic (well, “logic”), but it does a good job of allowing you to explore some of Samus’ basic skills right away.
Samus begins the game with 30 points of health, and enemies in this region (Brinstar) will sap eight points per attack. This allows players to make three mistakes before dying, and most defeated enemies drop health refills worth five points. So basically for every couple of creatures you destroy, you can absorb another hit. For now, Samus’ health maxes out at 99 health, so the game allows quite a bit of leeway for sloppy play — which is good, because she has very little mercy invulnerability and totally weird jump physics.
Metroid doesn’t have levels, but it does break its world into rooms — a little like its contemporary Castlevania, but with a major distinction. Rooms in Metroid alternate between vertical and horizontal scrolling. Unlike nearly every other game of its vintage, Metroid can scroll in four directions… but only two at a time, and the scroll orientation always alternates between rooms. I don’t think the change in directions is a specific limitation of the tech the team used for the game. Given that Metroid‘s sibling Kid Icarus (they share quite a bit of staff) does something similar it seems to be a conscious design style by the team rather than some kind of hardware requirement.
In your first time through the game’s second room, you can’t actually move vertically yet. So instead all the second room provides is a change in scenery; the level design goes from a fairly flat, open space to a series of odd-looking blocks arranged in horizontal layers, with one row situated above the floor. This forces players to scramble across the top while Zoomers crawl toward her. The raised platform and low ceiling mean you can’t simply jump over these creatures, forcing you to either time your dash across the platform to when they’re moving across its underside or else fire at them as they round the corner and come briefly into Samus’ line of fire. Either way, this room places monsters directly in your path and forces you to come to terms with them. And it holds secrets that you’ll later come to realize.
The next room is structured more like the first, with two of the dive-bombing Skree situated near the entrance. If you simply dash forward, the arc of your fall from the platform beneath the door will cause you to fall directly into their diving path, and the Zoomers moving along the ground will further complicate things. Instead, the correct approach is to slow down and drop gently from the ledge once the Zoomers pass beneath you, allowing you to lead the Skree one at a time and take out the Zoomers as they climb above you. For those used to the mad dash of a Super Mario Bros. or Wonder Boy, Metroid demands an uncommon degree of patience.
With the enemies taken care of, Samus comes to this low-hanging wall. With only a single-block gap between the overhang and the floor, Samus is physically incapable of advancing forward. She can’t duck or crawl, and she can’t pass through walls, so she’s effectively stuck.
For the first-time player in 1986, this created a confounding situation. You couldn’t advance; was there a secret? A trick? A mysterious way to get past this obstacle? You might begin to backtrack a little way to look for some kind of secret, something you’d missed. You’d push further and further back until…
…you were back here, at the beginning. But the screen kept scrolling, and no invisible wall prevented you from running left from the initial screen as it did in games like Super Mario Bros. and Pac-Land. You could run left for an entire screen or two, pushing back against what should have been an invisible boundary.
And eventually, you’d come to this: The Maru Mari, more commonly known as the Morph Ball. The Maru Mari allows Samus not only to duck, but to roll into a compact ball one meter high — just small enough to roll through one-block-high gaps.
In fact, once you’ve jumped over the large construct immediately to the left of the starting point, you’re forced to acquire the Mari Mari. The structure is too high to leap, and it’s too low to walk under. You can only return to the main game by ducking into a ball and rolling beneath the obstacle. Congratulations: You’ve just learned how to advance by using the Maru Mari.
You can do the same thing at that ledge in the third room. Welcome to the rest of the game.
It’s impossible to overstate how brilliantly the Metroid team executed this whole thing. They could have gone about it any number of ways. They could have placed the Maru Mari along your path. They could have forced players to run left from the start. They could have introduced the low wall much further into the game.
By placing this obstacle in that exact location, however, Metroid‘s designers turned progress into a test, and in doing so drilled the importance of your actions into your own mind. Instead of parceling out instructions or simply creating a mandatory learning process along the main path, the game forced players (accustomed to one-directional ratchet scrolling) to deduce a lot of different things at once: The freedom to move in either direction, the need to backtrack and explore, the importance of collecting items. Along the way, players learned both to use the Maru Mari and how to deal with certain enemies, the process of moving from room to room, and the fact that the game ahead would be packed with mystery.
Something I find particularly interesting about this sequence is that the distance from the Maru Mari to the low wall is nearly the same amount of screen real estate as World 1-1 of Super Mario Bros. The path to the wall essentially comprises the same volume of content as a normal level of contemporary games. Yet because of the need to double back and deal with threats that need to be dealt with with specific strategies, this sequence feels considerably different than the brisk dash through an opening stage seen in Metroid‘s contemporaries.
Whatever failings it may possess, Metroid begins with an extraordinary playable opening sequence. It may be hard to fully appreciate today, but viewed in the context of its time and place, this opening salvo served as a rousing statement of intent.