Listeners! This week’s episode is one based pretty much entirely on wishing and speculation. That basically means that Ben and Ash basically just spend an hour talking about things that feel are missing from Star Wars. Not in a negative way, but rather things that they would just like to see! It’s pretty unfocused, in classic Skyhoppers style.
This week, Ben and Ash are joined by Meg from Rogue Podron to talk about… dads? Obviously the big ones get hit on (Vader, Galen Erso, etc.), but of course if you’re familiar with Rogue Podron, you know Legends dads come up as well. Specifically one Hal Horn.
CW: A few minor rape mentions in the context of Game of Thrones
So. The showrunners of Game of Thrones are getting a Star Wars series. What does this mean? Honestly, Ben and Ash couldn’t tell you. But that doesn’t mean they don’t have thoughts on it!
(Ben says: There’s echo in the episode this week. Sorry about that. I couldn’t do much about it.)
(This was originally posted on my personal Star Wars Tumblr in October of 2018)
When I started reading the New Jedi Order series a few years ago, I knew enough about it to know which books were going to be the Big Ones™. Vector Prime (obvi), Star By Star, and Traitor were all ones that I was looking forward to since I knew they were all huge for their own reasons, and none of them disappointed me. Traitor is the one that I’ve read most recently (I just finished it a few weeks ago), and while I had a LOT of feelings after Star By Star, Jacen Solo has always been my favorite Solo kid and the one I identify with the most, so Traitor really got to me for a lot of reasons.
I think even if I hadn’t known that Jacen wasn’t actually dead after the events of Star By Star, I wouldn’t have believed it. He just winked out of the Force with no explanation of how that actually happened? Not buying it. While I didn’t think that this major character was killed off-screen, I was definitely wondering what happened to him, which was most likely the real purpose of his supposed “death.” Why would he just disappear from the Force? It was honestly a little distracting from the books between Star By Star and Traitor, since I spent so much time wondering what had happened to him. I think I succeeded in not rushing through Dark Journey or the Enemy Lines duology, but it was a relief to finally get to Traitor.
I had heard SO many good things about this book and Matthew Stover’s writing in general, and I was excited to read about Jacen (finally), but I’d also heard that this book is very “gray” in a lot of ways (namely the Force), which had me apprehensive, to say the least. Anyone who knows me personally or listens to my podcast knows that I tend to have a strong distaste for the concept of a “Gray Jedi” simply because I don’t think that that’s how the Force works.
I won’t go into my personal beliefs regarding the Force in much detail here since I could do multiple posts about it, really, but the long and short of it is that the Jedi way teaches passivity and communing with the Force and allowing it to act through you, and the Dark Side encompasses any action that exerts pressure on the Force through someone attempting to bend it to their will. Obviously there are exceptions and nuances within that philosophy, but that’s the best way to sum it up. Seeing as how I believe that Dark Side is always selfish and addictive, I don’t see much room for an individual that can utilize the Dark Side with no consequences.
With this set of beliefs, I knew that Traitor was going to be challenging for me before I even started it. The entire book focuses on Jacen being cut off from the Force by Vergere and him eventually overcoming that hurdle to not only regain his connection, but to obtain an even greater understanding of the Force that allows him to even sense the Yuuzhan Vong and their biological creations.
Throughout the book, Vergere is acting as a sort of mentor for Jacen not only during his period of captivity on board the Yuuzhan Vong worldship, but also during his escape on Coruscant. She feeds him questions that appear to make little to no sense at the time, but eventually lead Jacen to discover this greater connection to the Force of his own accord, and eventually unleash its power quite destructively. The utilization of the darkness inside of him even to save his life leaves him questioning everything he’s ever known about the Force before he eventually becomes this sort of messianic figure near the end of the book, bringing salvation to the New Republic and the Jedi. He almost doesn’t even feel like the same character after his encounter with the Yuuzhan Vong World Brain.
Needless to say, this WAS all very challenging for me. Coming to realize that the Yuuzhan Vong exist not outside of the Force but on some other sort of “Force wavelength” was a very strange idea at first, but the more that I thought about it, the more I became okay with it. I think I can kind of see where this expanded understanding of the Force that this series develops is going. Rather than being “gray” and allowing for use of both sides of the Force with no consequences, it posits that literally everything in the entire universe is connected through the Force, and nothing is more evil than anything else (at least that’s how I understand it). Everything just is, and it all belongs to the Force. There is no “light side” or “dark side,” it’s all just the Force.
Don’t get me wrong. I still don’t agree with this. But I can learn to live with it, if nothing else. At this point in time, Star Wars had to evolve and change, and the New Jedi Order gave it plenty of chances to do that. In the grimdark and morally-ambiguous era of media in the 90s and early 2000s, it only makes sense that something like this would happen at some point. The difference between “using both sides of the Force” and “the Force is everything” is super, super fine, but to me, it’s very important. Having a character walk the middle line with the Force is dumb, but a character who reaches a new understanding of the Force and uses it accordingly isn’t. Maybe I’m just nitpicky, but I’m glad that things ended up working out the way they did.
Honestly my bigger issue with this book is Vergere. As a character, I think she’s fine, but we’ve gotten hints about how powerful she is through not only her abilities, but also through how much she knows about the nature of the Force and the Yuuzhan Vong. She just seems so overpowered and it bugs me. This is totally coming from a place of “no one can be more powerful than my favorite characters and make them look like babies” but so far she’s saved both Mara and Jacen, and she’s acting all ambiguous about everything!! I will say, however, that stories and mysteries like the ones she’s at the center of make me happy that I only know major plot points from the series because I am very curious to see how she affects things in the future, even if I kind of hate her.
(This was originally posted on my personal Star Wars Tumblr in February of 2016)
To the untrained eye, 1995′s Dark Forces looks just like Doom with a Star Wars skin. In fact, there were some Star Wars mods for Doom that arguably looked better than this game. However, that doesn’t change the fact that this is one of my favorite Star Wars games of all time (despite the fact that before it came out on Steam, I had to screw around with DOSBox to get it to work). Part of the reason I love this game so much is that it’s the first appearance of everybody’s favorite Expanded Universe character Kyle Katarn, who will undoubtedly be written about in the future. Along with that, it just feels like Star Wars, if that makes sense. There’s something about being a Rebel agent on a secret mission to an Imperial base that gets my heart all fluttery.
With that said, despite all of the love that I have for this game, I also harbor an immense amount of hatred. The first level has you on the planet Danuta, where Kyle has been sent on a mission to steal the Death Star plans by Mon Mothma. That one is pretty straightforward. Kill some Imperials, get the plans, and get out. Mission two puts Kyle on the planet Talay at a Rebel base that was annihilated by an unknown Imperial force (which turns out to be Dark Troopers). While Kyle is investigating the destruction of the base, he finds a huge gun that no human could realistically wield, which he brings back to the Rebels. The Alliance traces the blaster back to an Imperial Moff/weapons designer named Rebus. Again, pretty easy.
Mission three, though. That’s when things start to plummet into hellfire. This time, Kyle gets sent to Anoat City on the planet Anoat, which is where Rebus has made his base. Anoat is basically a polluted wasteland after some miners screwed up the fragile ecosystem on the planet, so the city has been abandoned for some time by the time Katarn shows up. The mission begins in the ruins of the city, and then quickly shoves Kyle into an impossibly maze-like sewer system beneath the city. This is where the fun begins. If you aren’t being shoved into walls (and, by extension, down pathways that bring you back to the starting area) by torrential rivers of green poop, you’re probably lost. If you aren’t lost, you’re getting killed by a member of the seemingly-endless hordes of dianogas that inhabit the sewers or one of Rebus’s many droids. Did I mention that it’s pitch black if you don’t have your headlamp or infrared goggles on?
I’ve beaten this game at least ten times, and I’ve yet to spend less than 45 minutes on this stupid level. It never seems like it gets any easier. There’s always some switch I’ve missed or some drainpipe I’ve forgotten to wiggle down. I’m enraged just thinking about it. The worst part is that I firmly believe this is the hardest level in the game. Mission three. The hardest level. Think about that.
Now, after reading this, one might be inclined to wonder “Why write this whole thing just to complain about that one level?” Oh, dear reader. I wish that it were that simple. The sad truth is that this type of sewer level has become something of a trope in video games, and the Star Wars franchise is no exception.
The next recurrence (that I’m aware of) of this fecal nightmare occurs in 1996′s Shadows of the Empire.This game takes place during the events of The Empire Strikes Back and a little while thereafter. The player follows the story of smuggler-turned-temporary-Rebel Dash Rendar and his mission to help free Han Solo from Jabba the Hutt and bring down the leader of the Black Sun, Prince Xizor. The game goes relatively smoothly up until the second mission from the last, with some minor exceptions (fighting IG-88 in the Ord Mantell junkyard has never been easy for me, and I’m sure I’m not the only one).
Again, it’s the sewer level. At least you can see where you’re going in this one, I guess. Dash is in the sewers in order to infiltrate Xizor’s palace in Imperial City so he can blow it sky high with some pulse bombs. Sounds simple enough, right? Not when there are blaster turrets and droids hidden around almost every corner, not to mention the Black Sun soldiers that are hanging out down there. Thankfully, the environment isn’t out to get the player as much as it is in Dark Forces. The N64 couldn’t handle that much BS, I suppose. Having a jet pack makes getting around much, much easier. Regardless of that, there are still plenty of dianogas, and they still kill you in like three hits. The final boss of the level is a GIANT dianoga that lives entirely underwater. It has tentacles that take your health down 45% or so if you so much as touch them, and you somehow have to be able to tell them apart from the eye stalk you need to splatter on the wall to kill it. The worst part is that while underwater, if your jet pack isn’t actively sending you upward, you’re sinking. This makes aiming an absolute slog. If the player somehow manages to keep all of this in check, they can still die by sinking to the bottom of the giant toilet they’re in and into the dianoga’s mouth, or simply by drowning. Truly a miserable experience, though not as bad as Dark Forces, thankfully.
2003′s Knights of the Old Republic is pretty much universally loved by everyone that’s played it, right? I’m no exception. I’ve logged more hours in this game than I care to admit. But for some reason, when it was being developed, BioWare thought “You know what this game really needs? A segment in the sewers.” So they put one in. In order to get Mission Vao to help the player infiltrate a swoop gang’s base, you have to agree to help her save her friend Zaalbar, who’s been imprisoned in the Taris Undercity sewers.
Although this insufferable trope is present here, I will concede that it is easily the most tolerable sewer level I’ve mentioned. In fact, it’s bad almost entirely on principle instead of game play. The level is confusing to get around in the first few times, but it isn’t really that bad, especially compared to Dark Forces, though I’m beginning to think that nothing could compare to that mess. It’s annoying that you spend most of the area poisoned by the mutant rakghouls that infest the place, but even that is relatively minor. Heck, even the rancor down there isn’t THAT big of a deal (provided you don’t try to fight it and get around it some other way).
In recent years, we’ve been lacking in Star Wars games, and by extension, Star Wars sewer levels. As much as I hate the dumb things, I’m kind of starting to miss them. In my experience, the games that frustrate me the most are the games that I end up falling in love with for all time. The three games listed here, Devil May Cry 3, Oblivion, and countless others all hold special places in my heart because of how much I hate certain things about them. These aspects end up being endearing and give you things to share (read: commiserate about) with others, which deeply enriches the experiences they provide. After all, I’ve never gotten a long, ranting text message from my best friend at 2 o’clock in the morning about a game that DIDN’T frustrate him, which is something that happened concerning the mission to the Anoat City sewers. That has to mean something, right?