The latest installment of Splatoon has been out for a few months now and is making waves among fans. In that time, Glen and Nathanael have delved the depths of Alterna, waged Turf Wars, and endured countless shifts at Grizzco to bring you this extended deep dive into Splatoon 3!
Enjoying the TBC Podcast? We are an ad-free show! Drop a comment, leave a like, or share with a friend.
At least where I live, that is. Not that I mind: I like watching rain fall, and rain brings with it flowers. And with flowers come bees.
My history with Buck Bumble is much like that of my experience with Bomberman Hero: I rented way back in the 90’s and it always stuck with me. Unlike Bomberman Hero, however, I never even got close to beating it. Heck, having played it again recently, I’m not sure I ever even got past the tutorial.
Buck Bumble is a third-person shooter published by Ubisoft and developed by the now defunct Argonaut Games. Hold up, Argonaut Games? Yes, the company that helped develop the Super Nintendo’s Super FX Chip and the first Star Fox game. Strange, I heard that after Nintendo turned down their proposal for a 3D Yoshi game—which would eventually become Croc: Legend of the Gobbos—they had a grudge against the Big N and only released their games on every other system. Well, if that rumor is true, it apparently only applied to the Croc games, because they not only made Buck Bumble for the N64, but went on to develop several other games that were released for Nintendo platforms: Bionicle Matoran Adventure for the G.B.A., I-Ninja for the GameCube, and… Catwoman: The Game… Hm…
Wait, where was I? Ah right, Buck Bumble! As with Bomberman Hero, I stumbled across Bumble in a used game store—possibly the exact same one—for a mere ten bucks. Needless to say, I didn’t hesitate to take advantage of the opportunity to see if this game was worth remembering. Read more Buck BumbleThat Was a Thing ›
Welcome to That Was a Thing! A new series in which I discuss my favorite weird, obscure, or simply underrated pantendo games and media. Think of it as the evil twin to Simeon’s Nintendo Experience series. In this inaugural installment, I’m going to look at one of my favorite—not to mention one of the only—real-time strategy Nintendo series out there: Battalion Wars.
The Battalion Wars duology was a spin-off of the Nintendo Wars franchise and originally had the working title of Advanced Wars: Under Fire. Unlike the other Nintendo Wars games, however, Battalion Wars wasn’t developed by Nintendo or Intelligent Systems, but a British company: Kuju Entertainment. The first game was released for the GameCube on September 19, 2005 and its sequel debuted on the Wii on October 29, two years later.
The Battalion Wars games are a combination real-time strategy and third-person shooter. Like most R.T.S. games, players are tasked with completing objectives with the units provided for the mission—riflemen, tanks, bombers, etc. Needless to say, each unit type had its own strengths, weaknesses, and abilities and the majority of the strategy revolves around knowing where and when to deploy each unit. The unique selling point of this game is that the player directly controls one of the units the whole time, with the ability to freely switch between units as needed. Think of it as being sort of like Pikmin but with guns…and tanks.
Both games are set in a fictional world filled with global super-powers just itching to find a use for their massive armies. Seeing as the series was developed in England, each of the games’ fictional nations are comically stereotypical counterparts to real-life countries. The United States is represented by the gung-ho Western Frontier, the Tundran Territories are an odd combination of Tsarist/Soviet Russia, likewise Xylvania combines Imperial Germany with Nazi Germany, the Solar Empire is a futuristic tropical Japan, and the Anglo Isles—first introduced in the second game—mirrors the Anglo Isles…I mean the United Kingdom…seriously, they weren’t even trying to be subtle with that one.
As to be expected, each of these nations employ an eccentric and colorful cadre of commanders. Each mission has the player receiving orders from one of their faction’s commanding officers while the enemy commander emotes and responds according to the events of the game. While they don’t offer any special gameplay bonuses like the commanders of the Advance Wars series, the commanders’ typically blasé attitude toward warfare and nonchalant dialogue helps keep the tone light. I would say the only commander that I personally didn’t care for was Empress Lei Qo of the Solar Empire—who left so little of an impression on me, I had to look up her name just to write the previous sentence.
The third-person perspective really is what makes gameplay stand out. Giving orders from the perspective of one of your men while returning fire yourself really makes you feel like you’re an actual part of the conflict, instead of some ghostly observer calling the shots. When your battalion’s under fire, you’re under fire, and having to make tactical decisions in the midst of the chaos of the battlefield can create some really tense moments. Then there are the times when you spot some enemies in the distance or look at the map and have to plan your next move. I’m not sure I can properly express the feeling I would get as my men crowded around me, expectantly waiting for me to formulate a plan of attack.
If quality gameplay wasn’t enough, these games are also overflowing with personality. The games’ humor and cartoonish visuals give the series a lighthearted tone; these aren’t games out to deliver a ham-fisted “war is bad” message but instead revel in the innocent—and perhaps naive—feeling of playing with toy army men. Despite having the depth of a Saturday morning cartoon, almost every character is likable in some way—with my personal favorites being Tsar Gorgi, Kaiser Vlad, and Col. Austin—and I genuinely wanted to know what happened to them next. Each faction’s units are instantly recognizable, and their designs convey a lot of personality, not just for the unit itself, but for the faction it belongs to.
Giving orders from the perspective of one of your men while returning fire yourself really makes you feel like you’re an actual part of the conflict.
Now that we’ve covered the basics, take a closer look at the first game.
I first heard of Battalion Wars from the now defunct Nintendo Power Magazine. That’s not to say I immediately took an interest in it, however. I wouldn’t pay it much mind until my younger brother returned from the now defunct Hasting’s Entertainment with a used copy of the game. Shortly after he inevitably lost interest in it, I took a crack at it and fell for it harder than Tsar Gorgi off a bridge (too soon?).
The game places the player in command of the forces of the Western Frontier—with some exceptions in the form of unlockable bonus missions. The story begins during an uneasy truce between the Western Frontier and their longstanding enemies, the Tundran Territories. War breaks out when Western Frontier troops find a Tundran spy on the Frontier side of the border. As the plot continues, the Tundrans ally themselves with the Xylvanians, the Xylvanians betray the Tundrans, an old man is thrown off a bridge, I think there was a zombie-ghost legion at some point…you get the picture.
While it won’t win any awards, the story has a great sense of progression to it. Plot-wise, mission objectives often tie into something you did in a previous stage. If you saved a spy, you can bet his intel is what will point you toward your next target. The fort you defend in one mission is essential to launching a counter attack in the next and so forth. It’s a small detail, but having your actions contextualized like that goes a long way toward making your input feel meaningful.
While it won’t win any awards, the story has a great sense of progression to it.
While we’re talking about writing, I need to discuss the most important character: the grunts. Throughout the game, the troops under your command are constantly responding to your orders, quipping at the enemy, talking among themselves, or commenting on the situation at hand…and it is freaking adorable! Okay, I know that sounds like it’d get annoying after awhile, but the troops have so many lines that I would sometimes still be discovering new ones on my fourth or fifth play-through of particular missions.
On to the atmosphere: the visual style is a strange blend of cute, chibi soldiers and vehicles and a muted color palette that gives the environments an oddly grim and gritty feel. This, in conjunction with a great soundtrack that wouldn’t sound out of place in an old WW2 movie, produces a unique atmosphere in which the tone is never too heavy or oppressive but the player is still fully aware that—no matter how cute the enemy’s tanks are—this is still war.
The game isn’t without faults, however. The A.I. for units under the player’s control is a little slow on the uptake, to the point of seemingly lacking a self preservation instinct at times. I found any mission where I had to fight enemy aircraft especially aggravating, as anti-air vets tend to not take initiative, resulting in massive losses from even brief lapses in focus. I didn’t care much for missions where the game expects me to command planes and ground forces at the some time, either. For whatever reason, when given the wait command, planes continuously fly in a straight line instead of staying in proximity to where they were when the order was given. This required me to constantly check back on them to make sure they weren’t about to fly over enemy anti-air embankments.
Battalion Wars 2
Battalion Wars 2 starts its story off 200 years in the past by showing the player the final conflict between the Solar Empire and Old Xylvania at the end of the “Lightning Wars”. Bottom line is that the S.E. nukes O.X.’s H.Q. with an orbital death ray and then—fearing that the weapon is too much power for anyone to wield—chucks the controller (a staff) into a glacial ravine…what could possibly go wrong?
Back in present day, it’s been 2 years since the events of B.W. 1 and the nations of the world are at peace…until the Anglo Isles preemptively attack the Solar Empire based on rumors that they are harboring some sort of super weapon. The plot jumps between flashbacks and modern day from there with each campaign focusing on a different faction: a conflict between the Western Frontier and Tundra, the Anglo Islands staving off the Solar Empire’s retaliation, one where the player controls Old Xylvania’s forces, and finally Tundra’s attempts to prevent Xylvania from finding the staff.
The plot sounds a lot more complicated, but it really isn’t. I assume the 200-year-old-artifact-of-doom plot was meant to make the story feel bigger than the last game’s. Unfortunately, I’m not very fond of epics; I much prefer down-to-earth plots as I think they tend to have better focus and require the author to actually make me care about something specific like people or places. Fortunately, most of the characters are still quite likable, including most of the new ones.
Sadly, the narrative’s constantly changing point of view leaves the story unfocused and absolutely kills that sense of progression the first game had. You only play as any one faction for at most five missions (usually less). Between less emphasis being placed on the player’s actions between missions and the fact the player constantly switches sides, that feeling from the first game of being a single commander fighting in a series of much larger conflicts is completely gone.
Did I mention the volume on the player’s soldiers has also been dramatically reduced? They still speak, and I’m sure it’s still adorable, but I for the life of me can’t hear what they’re saying.
The narrative’s constantly changing point of view leaves the story unfocused and absolutely kills that sense of progression the first game had.
Moving on to the visual design of this game: many of the units received redesigns, especially the Tundran Territories’ infantry, most of which I think are improvements. The same can’t be said for Brigadier Betty: her look, not to mention her distinctive voice and a good deal of her peppy can-do attitude, are gone, making this iteration rather bland and forgettable. Speaking of bland, the game’s color palette is much more colorful which, while fitting well with the cartoonish style, demolishes the unique atmosphere of the B.W. 1 and stands out less by comparison.
Okay, so maybe the aesthetics and narrative aren’t on par with the original, but this game fixes many of its predecessor’s failings when it comes to gameplay. The A.I. is much more proactive: there were many times I would be ordering my units to attack a tank or some entrenched enemy infantry and would be surprised by the wreckage of an enemy gunship I didn’t notice suddenly crashing nearby. Oh, and planes finally fly in circles when put on standby!
The motion controls also make targeting enemies and issuing commands a snap. The only place where they really feel out of place is when controlling aircraft, as pointing the Wii remote up or down controls altitude. This feels awkward, especially if the player is trying to target a ground based unit, partially due to the game not making the change in altitude immediately obvious.
The game’s missions do feel a bit more repetitive than before. BWii’s missions follow a pretty predictable formula: defend a location then go on the assault or go on the assault and then defend the capture point. That said, BWii doesn’t have any missions that drag on too long or feel unfair—which the first game was occasionally guilty of, so I guess it more or less balances out.
The game’s missions do feel a bit more repetitive than before. That said, BWii doesn’t have any missions that drag on too long or feel unfair—which the first game was occasionally guilty of.
Of course, Battalion Wars 2 also brought new gameplay elements to the table: naval units and buildings. Naval units basically feel like tanks and artillery, but much more sluggish. That said, the game does a great job of conveying their weight and scale, and their long range means naval missions don’t feel too drawn out. Unfortunately, missions in which the player has to command both land and sea units tend to feel disjointed and tedious, due the two unit types’ inability to travel together and the player not being able to use the “All Units” button to regroup their units without messing up their positioning.
Buildings are a solid addition. Players can’t select their position, instead having to secure predetermined locations. Once under the player’s control, buildings will periodically replace fallen units corresponding to the type of building (e.g. aircraft for airfields). These help take the edge off, as the player doesn’t have to worry about losing essential personnel. That said, the fact that units have to run all the way to the players position, which can be on the other side of the map, means the player can’t rely on reinforcements too much.
Despite all of the flak I just gave Battalion Wars 2, I do think it’s the better game. While I think Battalion Wars has more personality, it can also be much more tiring—and sometimes frustrating—to play. Of course, neither is particularly hard to come by, and they’re both worth your time.
Sadly, Nintendo never commissioned Kuju to make a Battalion Wars 3. I think it’s blend of action and strategy would’ve been a great fit for the Wii U, and the Wii U gamepad would’ve been a great help in micromanaging units, something that neither game made easy. Nintendo still seems to have a fondness for cartoony wars games if the recent 3DS game Tank Heroes is anything to go by, so I haven’t completely given up hope. If the rumors of GameCube games coming to the Switch’s Virtual Console are true, I’d happily double dip on Battalion Wars…and not just because of how utterly unreliable old GameCube memory cards are.
About the Author
Glen Straughn is a lifelong Nintendo fan whose love of video games has inspired him to pursue a career in computer programming. He is currently studying to receive his masters in computer science from Oklahoma State University. He has gotten an S rank on every mission in BWii, and even managed to get an S on the final mission on his first successful play-through…completely by accident.