The Anatomy of a Shmup

If I haven't made it clear yet, I'm working on another shmup. This time, since I'm not restricted by a competition deadline, I've been paying close attention to the art behind creating shmups, both commercially and online. The big boys appear to be doing everything right. I only ever have a few nitpicks about them. If I ever feel like I don't like one, it's because of personal preference, not something that I can point out as being done poorly.

As for the indie shmups available for free or for a few bucks, they are hit or miss. Sometimes the design is ingenious, but the presentation is lacking. Sometimes the visuals are spectacular, but the gameplay is uninspired. Sometimes the game is pretty good, but could have been pushed further in various areas. There's a different reason for each game, but the importance here is that I'm taking notes on all of it.

Below I've gathered together a list of what I've observed over the months and years of playing. The ideas are in no particular order and only represent a fraction of my records. I thought I'd share them so you, too, can pinpoint a reason for any given game not being quite what you had hoped.

Keep in mind that not everything I say is required for every shmup. They each have their own place. Most of these notes are for scrolling and arena shooters, while some apply to any game or piece of art.

• Enemy bullets should always be visible. The bullets shot by enemies should be visible on top of explosions, power-ups, other enemies, etc. The point here is that those bullets are your primary reason for not beating the game. Any time not spent being able to see them is time not spent preparing to engage them. If a foreground object is going to obscure the view of play, it's a good idea to make sure no bullets are on-screen. The only exception for hiding bullets is the HUD; for this reason, the HUD should be kept to a visual minimum.


• Off-screen enemies should not be able to shoot. If the enemies aren't visible to the player, then how can a player even have a chance at feeling good about himself when dying from one of these bullets? This causes too much confusion, anger, and force quitting.


• All bullets should have a ricochet/splash effect when hitting something. Without some sort of "splash" or "pop" effect to show contact, it makes it feel like either the bullets have no effect or they're passing under the enemy/obstacle in question.


• Bullet collision should be accurate. This goes for any game where you can shoot and be shot at, but it's just a shame to be shooting something and having your bullets pass right by, or meeting the all-too-familiar death from a bullet that wasn't even in your area code.


• If the player's ship has a small hitbox, make it obvious. I seemed to miss this point with my last shmup. The key here is to let the player quickly know his boundaries of death when in a crunch. Sometimes only a few frames of opportunity are available, during which time it's essential to be able to see where your sweet spot is.


• The contrast between bullets and backgrounds should be high. This is something that's very important for survival, let alone for aesthetically pleasing visuals. An indie game for Dreamcast, Last Hope, had a special edition released that featured a higher bullet contrast. When Cave releases black label editions of their shmups, they oftentimes feature "darker background palettes". Also of note is that Cave has stuck with pink and bright blue colors for the bullets in all of their games. I guess they found the magic palette to make identifying bullets easiest.


• Enemies should show some sign of being hit. If an enemy doesn't flicker or shake or shoot sparks when being shot, I can only assume that it is invulnerable to attack. The whole thing doesn't need to flash white (it really hurts the eyes with bosses), but there needs to be some indication of it taking damage. On that note, if an enemy is invulnerable (shields are up, boss hasn't settled yet, etc.), don't change a thing about it. Some games let your bullets pass through during these times, which is also fine.


• Everything that is destroyed should explode. I'm almost completely serious when I say explode. As in fire and smoke. It doesn't seem to matter what the enemy is made out of; humans by nature love to see explosions and there's nothing more satisfying than watching something dangerous go up in flames. The Mushihimesama series gets around its insect/prehistoric theme by coloring its explosions blue, which in turn makes it look like a release of natural gas... or something. The point is, if you spend all that time pumping an enemy full of bullets, all of Newton's Laws say that it should explode into a fiery ball of satisfying pixelated splendor. And as far as boss explosions go, they better be a spectacular light show of gaseous fulfillment, including a screen-flooding flash of brightness that slows down gameplay.


• There should be a sense of flow to each level. If you fast-forward through superplays of various commercial shmups, it becomes very clear that the design of each level is structured to force you to want to zig and zag all over the place. It not only keeps your wrists happy, but it never leaves you waiting in boredom. Radiant Silvergun and Ikaruga both reward quick killers with additional enemies to shoot while waiting for the next section to arrive. It's okay to have nothing to do while being warned about a boss. For one, this gives your eyes a chance to focus on the text. Second, it allows you to build up whatever fear/confidence that its presence concocts in your body. Even arena shmups like Geometry Wars and Echoes provide a flow in where the enemies spawn.


• The visual style should be consistent through all levels, enemies, effects, menus, etc. The fact that this is something that every artist ever in history should be considering, it's sad to see it ignored so often. It's as if every 14-year-old with a wicked idea and limited freetime has used the same animated GIF of an explosion in his game. I was one of them. It's great as a placeholder, but if the rest of your game is composed of clean vector gradient fills, your explosion will not only look out of place; it will break gameplay. This happens a lot with uninspired menus as well, where a generic font is used without proper formatting. The end result can only make a player frown, no matter how spectacular the rest of the game looks.


• There should be "popcorn" enemies in every level. These are enemies that blow up (with an explosion) after being hit once (or very seldom). The key here is quantity. Popcorn enemies not only fill in empty holes of time between waves of more viable forces, but they also make the player feel like he's the coolest kid on his block (and if he's playing a shmup, he automatically is).


• There should be a way to save yourself in times of need. The most obvious method of saving one's life is the bomb. DoDonPachi also has a super/hyper beam. Ikaruga has homing lasers. Radiant Silvergun has a sword that slices everything in its path. The key here is that the player should be able to get out of a sticky situation. Most of these moves make the player invincible for a short amount of time, which in turn allows him to get out of physical obstacles as well as enemy fire.


• If an enemy appears out of thin air on-screen, allow time for the player to ready himself. Never have an enemy appear in the middle of the screen and fly off at full speed shooting everything its mother taught it. It's okay for it to accelerate to its destined speed, or wait a second before firing. There can even be an indication of its arrival before it even appears. Geometry Wars does this with particle splashes. Works wonders. Believe me.


• Enemy health should be either shown or predictable. Ikaruga shows the health of every enemy you start shooting at via a thin bar on the HUD. For games that show you nothing, you should be able to tell how long you need to be firing at an enemy before it's destroyed. Things like relative size or the presence of armor are usually good indications. If an enemy takes way too long to die, or if it explodes rather quickly, it will feel off, break gameplay, and your bewilderment over the developer's choosing of its health will put you into a stumper just long enough to be swallowed by an oncoming sea of bullets.


• The coming of a boss should be made clear. This can be done through a large warning sign, the sound of a siren, the sound of nothing at all, or simply a lull in enemies, signifying the coming of something large. If you don't know that you're fighting a boss, then you won't try as hard, and you also won't be as enraged when you come close to defeating it and ultimately die. Think of it this way: If you told Mr. Magoo that he just walked through a construction zone that failed its last safety and security inspections, he probably wouldn't be as emotionally struck as Lando Calrissian would feel if you told him that he just blew up the second Death Star and narrowly avoided being engulfed by its own flames (see? everything explodes). If you think that's a silly argument to make because Lando would have already known what just happened, you're right. That's the point. He knew the whole time that he was escaping certain death. The stakes were high and his adrenaline was pumping in return. The whole experience was a ride. And that's what a player needs to feel before the boss even shows its ugly mug.


• An unwanted sound should be heard when the player is hit/destroyed. The thought of losing a life and having to insert another quarter is enough to make a player avoid death, but the more that enforces that feeling of dread, the better. I think Squares 2 does this the best. The sound of that buzzer is the last thing I'd want to resonate in my ears, especially after having heard a looping sample from Daft Punk. Daft Punk!


• There should always be a way out of every situation. Here, I'm talking about designing the enemies and bullet formations such that there is definitely a way to get through, at least by the developer. I know players can lose focus and corner themselves into a tight circle of pain, but that's going to happen in any game. If you dodge the wrong way, you're only setting yourself up for failure. Half the "fun" of bullet hell games is learning how to manipulate the enemies into shooting such that you will have a measely crevice through which to escape failure. This is sometimes called bullet herding, which is kind of awesome. Even Space Invaders had this in the form of being able to hide behind your bases. That counts, right?


• Separate simultaneous bullet patterns should have different-looking bullets. The human brain is a beautiful thing, capable of recognizing complex patterns faster than any super computer today could ever hope to match (note: computers do not yet have hope). However, given the added sensations of stress, danger, and really fast bullets in large numbers, it would be such a great help if separate patterns had varied bullets. This can be achieved through color, shape, animation, and even rotation. The Touhou games are especially known for having hundreds of bullets on screen, each pattern distintively careening towards you at varying paces of fear induction.


• Camera-shake is a privelage, not a right. The effect always looks cool. Let's get that out of the way. The problem is when camera-shake is used when every enemy is destroyed, every piece of gold is collected, and every bullet is fired. Not only does this make for too much visual noise for the player's eyes (Cloverfield was under an hour for a reason), but it also dampens the effect. The less it appears, the more it'll mean for the player when it does happen. Trust me - less is more.

As I've said before, all of these suggestions are optional and in my opinion. They're all things that I've seen implemented beautifully in console/arcade releases and miserably emulated in free online Flash games. Since I'm making a free online Flash game, I'm going to do my best to maintain a level of polish and attention to detail that allows the game to stay together as a whole. Even a single out-of-place sound effect can ruin the entire experience.

To kind of drive these points home, I'd like to use the same identifying features from the screenshot of Ikaruga above and apply them to Space Invaders. Ya know, for fun.

It would be mean to point out the games that I feel could have been more successful, even by just following my suggestions above, so I'll just talk about the free shmups that did a lot of things right.

- Arcanacra: Excellent flow of gameplay, superb use of sound (The enemies/attacks are synchronized with the music), enemy bullets stay visible, enemies show signs of taking damage, there are popcorn enemies, and the boss explosion is worth the trouble. This is the best free shmup that I've seen do so many things so well.

- Cube Colossus: Excellent visual style (nice explosions), unique and useful control mechanic, bullet contrast against backgrounds, engaging sound design (especially when buying upgrades), ample warning before bosses and spawning enemies, and enemies have visible health and show signs of taking damage.

- Death vs. Monstars: visually and audibly unique explosions, a simple control mechanic that allows for quick and accurate aiming, popcorn enemies, a spectacular boss explosion, and enemy bullets that stay visible.

- Heavy Weapons: Great use of sound (especially of enemies spawning nearby), effects and menus match visual style of the game, and of course there are many popcorn enemies.

[cross-posted on Gamasutra] [continue]...

Lag, Control, and You

Talking about control isn't something that should be new to you. It's not some aspect of game design that slipped by your critical radar all these years and suddenly has been given new light. I'm sure you can still remember your thoughts when the Wii's controller was first unveiled; how impressed you were (and still are) at the SNES controller's simple, yet refined curves; how weird it was to see the Virtual Boy's double D-pad; how happy-yet-disappointed it was to see the Playstation controller evolve only under the hood - rather than on the outside - as each successive console was revealed. This is something that doesn't need to be said at all, as you should already know all of this. All of it. Still, though, I have things to say about control in relation to shmups. I'll try my best to stay on target.

First off, let's define something here: "control". Control is comprised of any and all aspects in games that allow you, the player, to interact with the game. The most prominent factors are some sort of input apparatus (e.g. a controller) and a monitor/television/Tiger Electronics LCD screen for viewing the status of a game. The factor I'm most concerned about is lag, which is no stranger to almost all other genres of games, especially fighters, racers, and FPSs.

Lag in itself means different things. We have:

• 1. Lag from human response time - This is how long it takes you to see something, calculate what you want to do, convert that to controller inputs, and make your body carry out those actions. This takes longer for more complex inputs (such as the infamous "The Mohawk").
• 2. Lag from controller-to-console-to-monitor - This is easily the shortest lag of all, yet it tends to gain the most hatred for ever existing. This also includes the online gaming route of controller-to-console-to-server-to-console-to-monitor.
  
• 3. Lag from game-related issues - Intentional slowdown, intense calculations, etc. This technically takes place during lag #2, but it deserves its own recognition.
  
• 4. Lag from Light - The time it takes for light to reflect off the monitor, travel through space, and into your retinas. I think I'll ignore this one.

And since we're all so visual nowadays, here are those same 4 kinds of lag, presented in one cohesive diagram:

Human Response Time Lag
In regards to response time, I don't have too much to say. This is the easiest lag to alleviate, though it takes the longest to achieve. The only way to make this lag go away is to keep on practicing until pressing buttons becomes second-nature. Luckily, practice in one game usually rolls over to other games, and even to other consoles. It varies from person to person. Some people are super quick at reacting, but aren't too accurate. Other people may take a few extra milliseconds to realize what's going on, but usually pull through. And of course there are people who are unfamiliar with their input device and have to look down at their hands more often than they look at the monitor.

Electronic Limitations Lag
Lag from the controller to the monitor is some kind of new-found beast in this generation. Back when we all had wired controllers and CRTs, no one even mentioned this. Now we've got Street Fighter IV vets who talk down upon wireless controllers' inferior speeds for sending input signals. There are forums dedicated to finding the right HDTV so as to minimalize the time it takes to process a composite signal into a digital format. Many HDTVs come with an option to switch to "Game Mode", which sacrifices cleaner visuals for less processing time.

As an avid fan and tournament-goer for Super Smash Bros. Melee, I can confirm for those out of the loop that pros will only play serious matches on CRTs. This is a fact across the United States and in international countries (I know you're there, Sweden, France, and Japan). Any HDTVs at a tourny are often used as the "just messin' around" TVs, the ones that are ignored during serious gameplay. Almost all players choose not to use the wireless Wavebird, despite its high review marks, to avoid any channel-switching shenanigans / battery-related tragedies. Does all of this attention to the saving of milliseconds make that much of a difference?

Yes. This is why MadCatz's billion-selling fight sticks have wires. They don't want any potential customer to doubt for a second that he or she will witness electric lag before purchasing one of these bad boys... especially when he or she will be dropping 150 big ones (i.e. dollars). Using HD cables on an HD console with a newer HDTV has become less of a problem. It's still there, but I feel technology is closing this short-lived chapter soon enough.

Intentionally Programmed / Intense Calculations Lag
When we press a button, we expect to see a result on the screen immediately (or rather, in such a quick manner that it feels instantaneous. Can't ignore physics after all.) If we press a button, wait, and then see the result appear on the screen, there had better be a good reason for it. Going back to Melee: if you try to jump, your character will first duck down and prepare for jumping, a Principle of Animation known as "anticipation". It makes the jump more believable, and only takes a few frames to accomplish. The game runs at 60 frames/second, so we're talking about a very short amount of time it takes to finally see your character leap into the air. This kind of lag is short enough to be ignored (...well maybe that's a poor example, as pros love to exploit this moment to wavedash all up and down their opponents' grills. It's hardly ignored at all and many players love to count frames to calculate how to achieve an added boost in--

Oh... right, shmups.

Intentional Lag in Shmups
The kind of input lag without immediate result that can really mess up gameplay can be found in many shmups. Let's look at Irukandji by Charlies Games. I hate to use this as an example, as I just love Charlie's other shmups to death, including the so-well-done (and 100% nsfw) Space Phallus, but I have a point to make here. The game takes place underwater. When you try to move, your ship takes a few frames to get up to speed, to simulate the water friction that would be found in such an environment. When you let go of movement inputs, the ship takes a few frames to slow down. This means if you want to move in a completely opposite direction than you currently are moving, then it takes about twice as long as usual to come to a stop, then start from rest and build that momentum back up to go the other way. The bullet patterns never get too complex to require intense weaving, and I totally understand that it's underwater and should feel like we're under water. But come on... this is a shmup.

I guess it makes little sense for a ship to be able to stop on a dime in any direction, but sometimes it's just needed. In shmups, it's almost always needed. And they're still tough as nails without any momentum lag. Plus, ya know, we have far more important things to complain about...

Here's a quick and dirty graph of the time it takes to reach full speed as compared with how much we should be tolerating it. I picked these games off the top of my head, so I can't exactly say they're accurately placed (especially since there are no numerical values for the axes). This graph is based simply off of my personal experience with them. Also note that the red bar exponentially reaches intolerability very rapidly.

Faster than Fast
It makes even less sense that most shmups allow your ship to move at full horizontal and vertical speeds when moving diagonally. The X and Y-axis movements are separate forces, so if you move diagonally, you actually end up combining their forces. Following Pythagoras, this means you'd technically be moving at ~1.414 times your normal movement speed. Ever wonder why speedrunners in FPSs move diagonally through worlds? Ever wonder why bunny hopping works so gosh darn well? Now you know.


That's all fine and dandy, but why don't more shmups force you to only move at your maximum speed? Many arena shmups impose this limitation, such as in Geometry Wars, but it's unheard of in vert and hori shmups. Why? Well, just think about it: As you wiggle through a swarm of pink death candy, you continuously hold [up] and sometimes press [right] to sneak through when an opening arises. If you could only move at maximum speed when moving in both directions, your vertical speed would slow down momentarily until you let go of [right]. This can very quickly become annoying and ultimately spell both your doom and a non-braggable NO RANK status at the leaderboard. It's cool with me to find this in arena shmups, especially when using analog sticks, since both your ship and the input device move in similar circular fashions.

Compensating for Something Small
It's possible to get used to sudden bursts and halts in speed as you weave in and out of certain death. It's possible to compensate for your ship's inability to change direction faster than in 0.2 seconds. It's possible for the mind to calculate everything happening on screen, tacking on an additional 0.2 seconds of leeway knowing that this one game was designed to feel more believable.

Back in the 56k modem days (33.3 for moi), we had to know when to let go of our sniper rifles' triggers in TFC, assuming the intended target would continue his trajectory and land under that big red spot just as the lag caught up and registered a hit. That was unnecessary skill, but we compensated. My point is, we shouldn't have to make that compensation, especially if the reasoning is because the developer(s) decided to make things not as responsive as they could have been.

True, there are plenty of instances where a little bit of intentional lag is passable, but when input-results become too delayed, the game isn't even worth getting good at. An exceptional exception is found in Mushihimesama Futari 1.5 (gazuntite) for Xbox360. The game intentionally creates gamespeed lag when too many bullets/killer insects are on screen (so as to emulate the arcade version). Your beetle-ship still responds faster than Lassie at an unsupervised well, but the whole game is slowed momentarily, allowing you to make even Neo a bit jealous.

Shameless Plug
And for those of you who were patiently waiting this whole time to make a comment about my own shmup's ship taking a little too long to move back and forth, I know. Trust me, I know. I obviously had my reasons, but I don't think they really make a difference at this point (especially after having rambled for much longer than was needed for something you already knew). If I ever make another shmup, rest assured you'll be stopping on dimes and moving at ~1.414 times your maximum speed all day.

[cross-posted on Gamasutra] [continue]...

Ikaruga: Practicing Faith

For those of us who've gotten "A"s and "S"s at the end of each chapter of Ikaruga, this one is for you. For those who don't quite understand how to get past that ridiculous symmetrical bullet-dodging section of Chapter 2, this one is for you. For those who haven't gotten into Ikaruga (shame on you and your friends for not getting you into it), this one is especially for you. There's a quality in this game and few others that we've taken for granted. I haven't come across too many games in my time where varying levels of challenge, skill sets, and excitement can all be experienced from the same game without even changing the difficulty or settings. For the sake of simplicity found in Chapter 3: Faith, I'll use the entire chapter as an example of what you may have already forgotten (or soon will be learning).

Chapter 3 contains the longest intro of any chapter, which accounts for it being the most difficult to chain perfectly (Chapter 2 coming in a very close second). There are several pinpoint shots that must be timed accordingly with your position on screen in order to not get crunched by the oncoming enemies... but I think I'm getting ahead of myself. The real joy and pleasure of this game - at least for me - comes from three very distinct moments in realization and accomplishments.

First is becoming aware of polarities and consciously switching to anticipate a future action, whether it be for dodging debris, to absorb bullet fire, or to drain an enemy's health faster. Regardless of your reasons for fine-tuning this ability into the hard-wirings of your brain, there's a moment where you step outside of your body, take a look at yourself, and see how much you've grown adept at switching polarities without having to be told why. You're a shining star in the world - if only for that one moment. This one really only applies to the earlier chapters, as this skill naturally carries over into later levels. The other two are on a chapter-to-chapter basis.

The second moment in memorable Ikaruga milestones is in the feeling of taking down a boss. That doesn't just mean you took down a boss. That means you also successfully understood the majority of what was going on throughout the entire chapter, which is something that does not come on the first try. Even Chapter 1 has its hardships towards the end when two lanes of little guys fall from the middle while two large pods do a ballet about the screen's perimeter, with helpless little you trying to survive the crisscrossing of enemy bullet fire streams. Then there's of course, you know, all of Chapter 4...

The third and most important moment you can possibly have in Treasure's (♥) masterpiece is chaining a level from start to finish. This arrives in varying degrees, from knowing of the chains that should be tackled and how, to actually doing a full chain without losing a life. I don't know about some of you (okay, none of you, so keep in touch), but I never really understood chaining even after being shown the art by a friend. It wasn't until I watched a couple superplays that it at least made sense on paper. It's not until you go in and do it yourself that it'll really click and you'll begin to appreciate the work that was put into this game.

Many other shmups out there have a chaining system of some sort. While they, too, have a strict script of actors that appear on screen, strategically placed for the sake of a specific methodology for chaining, it's never more apparent and satisfying than in Ikaruga. Perhaps it's the simplicity of your firing that allows you to know for sure what it was you just blew up and what's left on screen. Maybe it's your ability to count to three in your head rather than space out your shots hoping that your meter doesn't run low (my fist remains clenched for DoDonPachi).

So let's get back to Chapter 3. Right off the bat, you're presented with a whole screen of dancing foes and these guys that run down the side and turn when at your position in y-coordination notation. Eventually I learned to do some backtracking on the screen in order to fake them out, but the superplay spoke of a different method. Watch the clip below and pay attention to how the double sets of three spinning enemies open up a hole just wide enough for a bullet to get through and destroy all three of the inside ones in a single shot. Also pay attention to how the side guys are tricked into coming for your ship as you lure them in prematurely. Pause at 0:17 and continue reading. We'll take a look at other sections soon enough.



And that's just how you start the intro. The whole screen was cleared, not an enemy was spared, and the chain is unbroken. Gorgeous. Keep in mind that this player is quite flashy with his movements and switches polarity for the sake of collecting a few extra pieces of enemy debris, making his final score a few thousand points higher than the rest of the handful of shmup gods out there who also go for the small details in life. Let's move on.

Below you'll see a section that comes up halfway in the chapter wherein the walls close in, making your area for movement quite tight. As if that isn't enough, gates start closing in on you at staggered positions, requiring you to watch your spacing even further. A series of enemies are found within these tight spaces, not really posing a threat as long as you're constantly firing. Upon the first few playthroughs, they're nothing more than an afterthought. Eventually, once you learn the method for chaining them, the whole sequence is seen in a new light. The formations of their arrival is no mistake, as you must fire a rapid shot at one column, then the other, for shooting straight-on will immediately break the chain. A few spherical stragglers break up the rhythm (our player here releases his homing shot as it yields more points in the long run. That and it's a lot safer than going past the destination hole to single-shot those guys). As for the second set of enemy columns, they may appear similar, but this time they need to be rapidly shot down the middle, as they're now approaching in even-odd formation. Take a look below and then pause at 2:30.



It goes by so quickly, doesn't it? That's probably a good reason why people have such a hard time getting into shmups, but I'll save that thought for another week. In the meantime, let's focus on the next segment. A miniboss appears behind you, rendering your past strategy of hugging the back wall useless (and putting all of your practice in dodgeball down the gutter. Well, at least I hugged the back wall). This forces you up a little bit and closer to a series of closing gates that each have a spherical friend (i.e. foe) waiting in place. Of course we all had enough to worry about, what with the closing gates and big metal thing chasing on our tails, so we just held down the fire button and didn't even worry about those bystanders. Little did we know that we needed to single-shot them all, in order, to achieve a full chain. The genius design of this section is that if you shoot rapidly, your line of fire will skip ahead to an enemy above the closest one, breaking the chain. This requires you to utilize the ability to change rhythms on the fly, weave through gates, stay above the miniboss (which really isn't that daunting. The fear factor is what makes him worth mentioning), and single-shot those suckers right before you have a head-on collision and have to tell Guinness to come back another day to see you hit that world record. Watch below. Then pause at 2:42.



As if that strict set of movements wasn't enough, you also need to remember to move out of the way because that thing that was chasing you before suddenly feels the need to scoot ahead and take control of the situation. Yes, memorization is key in this game, though there's a point at which you stop thinking about what's coming and your mind simply knows. It's hard to explain, but your fingers eventually do all of the thinking, allowing your brain to focus on other things happening on screen. Seriously, I can't be the only one who has a spectator ask, "How did you know to dodge that?" and my only response is, "I'm not too sure... I just knew."

Continuing along, once the miniboss is kaput, a series of seemingly randomly-spawned enemies appear on the screen. And when you shoot one, it only multiplies into two, until the entire screen is filled with a chaotic nonsense of bouncing sphere guys. Well, at least it was random to us at first. There's a very definitive pattern here, and our player below exploits it for all it's worth. He doesn't finish killing them off as this section is just a filler until the boss (or rather, a bonus section as a reward for killing the miniboss earlier than expected. Afterall, the entire game is synced to the soundtrack). Go ahead and watch to the end. We'll discuss the boss battle in a hot second.



Yes, so... a phenomenal performance on the final boss of Chapter 3. Our player's strategy was to weaken the outer units each to the brink of blowing up, then summoning a homing laser that destroys the bulk of them simultaneously. The remainder of them is finished off amongst some mighty angry laser action coming from the core, which is strikingly similar to one of the bosses in Chapter 3 of Treasure's previous shmup, Radiant Silvergun. And speaking of bringing back battles, that miniboss hearkens of another battle from Silvergun wherein you were chasing / being chased by a miniboss. That same battle seemed to evolve yet again in Sin & Punishment. One can only hope these foes make their spiritual reappearance in Project RS3 (or Sin & Punishment 2).

As you've seen (and hopefully experienced), there are quite a few layers of play packed into Ikaruga's deceptively simple design. Strategies change quite a bit once you play on the different difficulties, though the harder it gets, the more you have to achieve. It's design like this that really keeps me entertained, excited, and glad to be a part of the shmup community. Indie developers are constantly finding fresh ways to keep an old genre alive, while a few larger-scale companies out there are still dedicated to providing high-quality adventures in the skies (and seas!) that we've come to love.

And for those of you wondering why I never mentioned the fourth Ikaruga milestone - achieving a one credit full-game completion - I'm still working on that one. I've only been able to get halfway through Chapter 5 on one credit, so some of you may agree that I have a long road ahead :]

[cross-posted on Gamasutra] [continue]...

Battle Garegga: More pink flamingos, please

I don't know about you, but when I play shmups, I hold the fire button down until I either get a Game Over or beat the game. I capitalized "Game Over" because it is most definitely a proper noun. It's the last thing you see upon every play, and all-too likely, the most visible memory you have when thinking back to certain experiences (I shake my fist at thee, Andross). In the case of Ikaruga, the way the game is frozen while you enter your initials (or "AAA" in a fit of rage from missing that 4 mil mark on Chapter 1) and then reanimates back into motion with a mechanical buzzing sound of defeat is all it takes to make me want to come back and prove the game wrong. At least in Ikaruga, I know it's possible to come back and do better and get a little farther. At least the game is beatable when I do my best. I wish I could say the same for Battle Garegga.

Developed by Raizing, the game is one of those pivotal entries in the genre that helped define all of that manic craziness that we know and love. It apparently was a heavy inspiration for DoDonPachi's golden joyride, so why not love it, too? Probably because it hates you. I speak of course of the rank system in the game, an invisible collection of algorithms designed to slowly deteriorate you from the inside-out. Sure, rank systems are in all kinds of games, not just shmups. GTA IV has a dynamic system that changes the difficulty of missions based on how many tries it takes you to complete them. Left 4 Dead heavily uses a ranking system that fluctuates difficulty in real-time based on how well your party knows how to avoid being vomitted on. So why point out Battle Garegga's rank? Because if you just hold down the fire button, dodge every bullet, and collect every power-up, the game will become literally impossible to beat. It simply cannot be done. And it's all thanks to the omni-present rank which oversees your every move.

Unfortunately, the dedicated community over at the shmups.com forums have collected a compendium of knowledge around this one aspect of the game. Unfortunate, in how I now know just what goes into deciding the rank (quick summary: everything). Let's start with collectibles. If you touch a power-up, rank goes up. That goes for weapons upgrades, options (helper pods at your side), bombs, medals, and auto-fire upgrades (big no-no on touching those). If you shoot a bullet, rank goes up. If you use special bullets, rank goes up. Using a bomb, gaining a life, beating a boss, simply existing; it doesn't matter. Rank goes up (Yes, simply existing without dying makes rank go up). The list goes on. Rank is even so evil that it will sneak its way into your next play session, requiring a reset of the ROM or PCB or whatever you may be using to play it in order to get it back to default. The only true way, in fact, that lowers your rank is to die (what a wonderful lesson this game teaches us about life and its hardships). The less lives you have when you die, the further the rank is reduced (excluding having 1 life left, at which point dying will inevitably give the game another chunk of your soul).

This may be bleak news, to find that anything you do in the game in order to survive and get ahead only pushes you further back. If I recall correctly, the final boss to Final Fantasy VII had a similar fate if you maxed out your characters' stats, rendering the battle impossible to win (making it even more ironic that the very final battle with Sephiroth is impossible to lose). I suppose on the bright side with Garegga, you don't have to invest dozens of hours into one game with no backup saves only to find that you can't beat it; that realization takes only a few minutes. The best way to play (i.e. complete) the game is to take your time collecting power-ups, avoiding certain power-ups altogether, only shooting when necessary, etc. Players going for score use this same recipe, though they incessantly dangle their fragile progress in front of the rank system, pushing it as far as it can go without causing an implosion of the game and its local universe.

Fortunately, as with almost all games in existence, there are a few tricks to getting an upper hand. There's a few sneaky ways to exploit massive point gain with some later bosses. My personal favorite is by hassling a flock of pink flamingos that found refuge in a castle, shrouded by a small forest, in the first half of level 2. Your fire disrupts their peace, forcing them to migrate north, at which point spraying them with more bullets / fire can cause your score to become an overnight millionaire. None of them seem to be harmed, so it's okay that I mention finding extreme joy in sending a flamethrowing special move into their haven.

I originally thought this game would be an ideal place to go for a good ole 1CC. Further reading made me not back off, but rather take my time with pacing if I ever wanted a shot at seeing some sort of credits roll. That rank system is just about as in-your-face as Sinistar's ego-centric taunts. At least Sinistar eventually shows his ugly grin.

Because showing a skillful run of this game is a slow and flavor-filled art, even under my respectful gaze, I'll just show you those awesome flamingos instead. They may be hard to see, but they're all flapping away from 0:28 to 0:38.


And finally, I wish the best of luck to Zakk from Hey Poor Player! in his endeavors to get a 1CC in Battle Garegga. [continue]...

Raiden III: That poor, hapless driver

Having much more to do with the morals and decisions of warfare than those of shmup mechanics and the did-you-ever-notice spiels I usually blurt out (although this entire post is about something I'm wondering if you've ever noticed), I'm interested in just what was going through the heads of the developers at Moss when they decided to allow you to kill an innocent bystander (actually a driver, but keep reading) in Raiden III for a rather uneven compensation.

The whole scenario unfolds within only a minute of starting your first mission. You begin soaring over what looks like a desolate and war-torn city, already in the midst of destruction and chaos. The only movement on the ground comes from tanks that are quite aggressively firing at you. All of a sudden, atop one of the highways, a red compact car blindly roars by from left field, entering the crossfire. Naturally, you'd just want to blow up everything in front of you, but on this specific occasion, you're blowing up much more than an enemy; this driver was trying to save his own life.

You may be wondering why I even care about that car. For all I know, it could have been driven by one of the generals of the opposing force, or even be a pilot running late to the hanger bays that morning. However, since it fires no bullets at you and simply wants to use the highway as it was originally designed, I can't help but feel guilty whenever I destroy it. The payoff is certainly not worth it, a measly 1000 points in exchange for his death. I eventually played through with the intent not to blow him up, and guess what? The car swerves out of the way of an oncoming tank before exiting the screen. He clearly was in a rushed, panicked confusion during this battle. And you just went and blew him up.

This begins to make me wonder why I don't care about blowing up other by-standing things. In DoDonPachi, entire warehouses of who-knows-what are destroyed, simply for the pleasures of watching explosions and collecting stars (and possibly uncovering a fragile skeletal bee). In Guwange, the player sometimes blows up entire wooden watchtowers in 14th Century Japanese villages (while at a casual strolling pace, mind you). However, in none of these situations do the presumably destroyed individuals bare a soul, a will to live, or even a rather dashing vehicle.

I couldn't help but compare this fascination with the destruction of life to the 1996 movie Independence Day. Though destruction of innocent life goes on throughout the whole film, I feel quite differently when those immature alien-inviting New Yorkers are decimated as compared to how compassionate I am for the survival of Jasmine's dog Boomer when escaping a flame-engulfed tunnel (yes, I know - I'm just as shocked as you are that someone actually uploaded a screenshot of the very moment to which I'm referring). The point here is, we as an audience were swayed into having little-to-no emotion for the New Yorkers (though still just as innocent as those who weren't inviting the aliens) and had much love for a dog trying to escape fire alongside co-star Vivica A. Fox. Why did we feel this way? Because the dog wasn't a bad guy at all. He wasn't twisted or evil or filled with even the slightest hint of bad intentions. And neither was that red car.

For the sake of tying things back to shmups, here's actual footage of someone blowing up the unfortunate vehicle (@ 0:53). Note how an entire condo is blown up immediately afterwards and how little I care about it.


Know what's even worse? In Dual and Double modes, there are two cars careening to their doom atop that highway. A moment of silence for the blue car, too.

[cross-posted to Gamasutra] [continue]...