Category Archives: games I regret

GAMES I REGRET PARTING WITH: LOST: The Game

Perhaps one of the big reasons why I adore the show LOST so much is because it was something my mother and I both watched, and after each episode, we’d e-mail each other with reactions or theories or to generally complain about how mean Ben is or what nickname Sawyer came up with for some other cast member. Good times. She got really into it during those early seasons; I can’t remember if she ever saw its conclusion before passing away in December 2010. At some point during the show’s popularity, my mother purchased for me LOST: The Game at her local Borders. Here’s the sad rub: I never played it, and by the time I was ready to move out of my studio apartment in Clifton, NJ, I tossed the whole thing away, cool suitcase and all.

Now, around this time, I did make some friends, and we played a lot of board games, such as every iteration of Munchkin out at the time, Talisman, Dungeons & Dragons, Catan, Chez Geek, Pimp: The Backhanding, Kingmaker, and so on. I just never felt comfortable bringing the game over or learning the rules by myself and then having to teach everyone; plus, I was still pretty new to the world of board games, and I had no idea if LOST: The Game was a good one or a bad one or even worth figuring out.

LOST: The Game was released on July 15, 2006 in the United Kingdom and August 7, 2006 in the United States. The game was designed by Keith Tralins, developed through MegaGigaOmniCorp, and published by Cardinal Games. It is a hybrid strategy/social/role-playing game set in the world of LOST that, if you’d believe, is somewhat similar to many solo games I play now, such as Fallout: The Board Game and Discover: Lands Unknown. The game allows you to assume the role as a character from the show in your attempts to survive on the Island and features many of the elements involved in the first few seasons of the TV show, including mysteries, alliances, and the “Smoke Monster.”

There are 75 hexagonal Location tiles that make up the main playing area for LOST: The Game. There are two types of tiles: 30 Shoreline tiles and 45 Inner Island tiles. The location tiles are set face-down randomly to ensure that each experience with the game is unique, just like with Catan. The tiles can be arranged in any fashion the player wishes, as long as the Shoreline tiles are on the outside edge of the board because why would you put water in the middle of the island. Also, how did a polar bear get out there? Anyways…

Here’s how it plays, as far as I can tell. Players are randomly dealt a Starting Character, such as Jack, Locke, Kate, and so on. You cannot play as Desmond, and for that sin alone this game deserves to be stuffed down a hatch and forgotten for good. On each player’s turn, they must move all of the characters they own to an adjacent tile. If the location tile their character is located at is face-down, they flip the tile face-up and follow its instructions. If a Fate card is drawn, they must immediately deal with any Encounters or equip any equipment; however, they may choose to hold an Event card for later use. Characters may also attempt to lead neutral characters at their location. If another player occupies the same location tile, the players may attempt to engage their opponent’s characters to lead them, steal their Fate cards, or steal their equipment.

You win LOST: The Game when:

  • One player leads all characters on the Island
  • A Starting Character’s win condition is fulfilled
  • Another win condition decided upon by the players prior to the game (whatever that means)

Right, so it doesn’t sound like the most intricate or complicated board game ever designed. We’ll give that award to Scythe. Still, I wish I had my copy now because I’m more familiar with this style of gameplay, and it is something I’m curious about, as LOST is never not spinning away in the back of my mind. There wasn’t a lot of attention given to the game’s art or look, other than it coming packaged in a briefcase and using images from the show, and that’s a shame because a more stylized version might have convinced me to keep it for the long run. Oh well. Perhaps I’ll run into it again down the road. Y’know, when we all go back to the Island.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: X-Men: Mutant Apocalypse

I love X-Men, and I loved X-Men. I probably don’t love it as hard as I did as a young, lonely child with a wild imagination, but that’s okay. Not everything lasts forever, and that’s why nostalgia exists. Growing up, I had plenty of X-Men action figures, two VHS tapes–namely X-Men: Pryde of the X-Men and X-Men: Night of the Sentinels–that I watched over and over again, to the point of almost burning them up, and, of course, countless collectible cards, ranging from Jim Lee’s X-Men Series 1 to SkyBox’s X-Men Series 2 to X-Men ’95 FLEER ULTRA and even more. If you were at all like me, then you know exactly what I’m talking about; if not, oh well, move along. So it was natural for me to be excited about anything X-Men-related when it came to videogames, which brings us to X-Men: Mutant Apocalypse…for the SNES.

In X-Men: Mutant Apocalypse, Charles Xavier sends five of his beloved X-Men to sabotage various operations and structures on the Genosha island complex to liberate mutants in captivity. Further investigation reveals Queen Brood and Tusk are involved in this matter and headed by the titular Apocalypse. After defeating all evil forces on Genosha, Xavier discovers that Magneto intends to destroy Genosha from his space station Avalon. To prepare for the confrontation, Xavier tests the five X-Men in the Danger Room to defeat holograms of Omega Red and Juggernaut. After passing the tests, the X-Men go on separate paths inside Avalon to face and defeat Exodus and then battle against that non-magnanimous Magneto. It’s like a multi-part string of episodes from X-Men: The Animated Series, and I was into it.

Right, so. The player takes control of five X-Men who each have their own objectives, as well as different moves and capabilities activated by certain control combinations. There is a limited number of lives that count for all five X-Men and not one individually. That said, similar to Mega Man, the levels may be played in any order. At the end of each level, you fight a boss, and the next three levels are linear and require each boss level to be defeated. This is followed by two straightforward boss battles in the Danger Room. Finally, only one of the X-Men can be selected, each one going through a different end level. Thankfully, after beating the first five stages, a password can be acquired. The game has health pickups, as well as the option to gain extra lives by collecting three “X” icons hidden throughout each stage. Otherwise, it’s a straightforward action game where you destroy anything and everything in your path, usually with mutant powers.

Here’s who you get to play as in X-Men: Mutant Apocalypse:

  • Beast – Possesses superhuman physical strength, agility, and an ape-like appearance…if, y’know, apes had blue fur.
  • Cyclops – Produces powerful, uncontrollable beams of concussive force from his eyes, forcing him to wear a specialized visor at all times.
  • Gambit – Has the ability to manipulate kinetic energy and charge objects with it. He’s also skilled in card-throwing, as well as hand-to-hand and staff combat.
  • Psylocke – She can use her telepathic powers to form a “psychic knife” from her fist. She’s also an expert martial artist.
  • Wolverine – A gruff mutant possessing superhuman senses, enhanced physical capabilities, adamantium coated bones and claws, and regenerative abilities.

For me, I was sold the instant I knew I could play as Gambit. He was always a favorite of mine growing up, and I still think there is a coolness to the character now, even if I haven’t kept up on any of his storylines. I also enjoyed Beast a great deal, hanging upside-down and punching minions in the face. The pixels were big for X-Men: Mutant Apocalypse, almost zoomed in, which meant you didn’t get to see a ton of the environment around you, but you got a nice closeup of Cyclops firing off his laser blast. It definitely helped make these characters seem larger than life, which, for me at that age, they certainly were.

Now, around the same time as this game, there was another X-Men game, but it was for the SEGA Genesis. A system I did not own, but frequently played on at my then-best friend’s house. This was X-Men 2: Clone Wars, and it seemed to be the cooler-looking one of the bunch, much like how Mortal Kombat had blood on the Genesis and sweat drops on the SNES. In this one, you controlled a select few X-Men as they attempted to thwart the alien Phalanx from assimilating all of Earth’s inhabitants to their race. It played differently, and I still can’t pinpoint why I felt like my SNES title was inferior to it, but the feeling remains.

Either way, sorry, X-Men: Mutant Apocalypse, for trading you in. I do have a bunch of other X-Men-related games in my collection that remain untouched, shame on me, and I hope to get to them soon, as well as procure a copy of X-Men: Destiny, which might become a rarer thing down the line.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: Haven: Call of the King

I don’t believe I ever got past the first couple of levels in Haven: Call of the King, and that’s part of why I regret trading it in. I never gave it a fair shake or saw much more of it past the opening area, where you mostly do a bunch of platforming while escaping a collapsing mine and explore Virescent Village in search of one of Haven’s friends.

Haven: Call of the King is a single-player PlayStation 2 game developed by Traveller’s Tales–yes, the LEGO people–and published by Midway. It came out way back in the day, specifically the year 2002. It’s a combination of different gameplay types, namely action platforming, puzzle solving, and some shooting. The game was intended to be the first chapter in a trilogy of games, but was a commercial flop upon release; as a result, the story was never finished. I’m pretty sure I got my used copy from GameStop for a measly few bucks, and it didn’t even come in a case if I recall correctly. At some point, I traded it in with a bunch of other games for something, which is why it is now starring in this beloved Grinding Down feature.

Here’s all I know of Haven: Call of the King‘s plot, based on the very limited amount of time I spent in its world. Lord Vetch and the Overlord talk about The Voice and mention something about the slave named Haven–how there has been some trouble regarding him. See, he is one of several people who are infected with a virus that requires a constant supply of antidote, which the despot Vetch controls. The scene then cuts to Haven in his home as he is working on building a mechanical bird called Talon. Haven is late for work, so he heads off to the mines. There, he finds his friend Chess being hassled by some guard. The henchman notices Haven is watching, so he turns and fires his laser at Haven. He misses, instead taking out a chunk of the wall and causing the mine to begin to collapse. The true point of the game though is for Haven to find some mysterious bell Vetch has hidden away. Why? I know not.

One of the things I remember standing out in a big way in Haven: Call of the King is that there are no loading screens between environments, unlike Crash Bandicoot. It’s done more like as in the first Jak and Daxter. The game does all its loading during very quick cutscene transitions between levels. I know that this is pretty commonplace nowadays, but back that it was a big deal. Evidently, there were numerous minigame types folded into the standard platformer gameplay that I never even got to touch. There’s a variety of vehicles, including a jetpack, a boat, an airplane, a jetcar (that’s better than a jetpack, yes?), a glider, and a spaceship, and each has various gameplay goals attached to it, such as dogfighting, racing, manning a gun turret, or completing simple mission objectives. It’s a game that seems stuffed to the brim with things to do. The first area alone has a number of different things to collect–cog wheels, blue lights, pulsating egg-like things, heart refills, and so on. You’d almost think of this as more of a collect-a-thon if there wasn’t also a huge focus on action sequences and nimble platforming.

One unique element to Haven: Call of the King‘s platforming gameplay revolves around Haven’s main weapon, which is called the mag-ball. It’s a yo-yo type of weapon, with a fairly short range and a very tiny business end; however, the problem was you simply didn’t have fine enough control over which way Haven was facing to aim it properly. There also wasn’t any kind of lock on or auto-aim to help take out enemies or burst acid/fire pots. The mag-ball can also be used on tracks in the air to get Haven from place to place, kind of like the grind boots from Ratchet & Clank.

While the game presented itself as cartoony and kid friendly, it definitely has some dark undertones to it, what with all the slavery business. Sounds like Haven: Call of the King ends on a dreary note, and that’s all she wrote, as this trilogy is certainly never going to be finished. A strange game, for sure, one of its time and era–Haven’s rather appropriate bit of facial hair really stamps this game into place–and I honestly do regret giving this one up. At least I can revisit it on YouTube whenever I’m in the mood to see how this all ultimately unfolded.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: Smuggler’s Run

To me, Smuggler’s Run was probably my first dip into an open world environment. The fact that I was driving a vehicle and could leave the road at any point for a zip through the desert, going left or right as I pleased, felt revolutionary at the time. In fact, this type of driving was encouraged, especially when the U.S. border patrol began chasing after you. I wasn’t locked into a course with walls and barriers or even invisible walls, forced to follow the path that the developer wanted me to follow, doing the same thing as anyone else playing the game was doing. I was a smuggler on the run, running how I saw fit.

Like I just said, in Smuggler’s Run, you play a smuggler who needs to prove himself in this underground world and has a number of different vehicles at his disposal to do so, including dune buggies, rally cars, and military vehicles. These vehicles are used to smuggle assorted cargo through three different large, open levels. It’s a fairly weak plot to begin with, and your mission objectives are spelled out for you via some quick narrative before each mission. The missions  range from basic smuggling operations that involve moving the contraband from point A to point B, to customized versions of a checkpoint race and the loot grab modes, to completely original objectives like destroying a series of radar towers.

Smuggler’s Run had a couple of different modes to explore, and I’ll cover ’em briefly here because, honestly, I really only played one mode over and over again before eventually using this game and some others as a trade-in offer for…well, I have no idea what I got for them, but that’s beside the point. Smuggler’s Mission mode is basically the story campaign I described in the previous paragraph, seeing you go through three consecutive levels (forest, desert, and snow) with about ten missions per level. Turf War mode had three different mini-games, two of which involved smuggling cargo while fighting against a rival gang; the final mini-game involved a race through a popular spot in a level. Lastly, Joyriding mode allowed you to freely roam to and fro in any level without having to deal with the U.S. border patrol or CIA, and it was a great way to get to know the ins and outs of any level before taking it on via the story missions.

If I recall correctly, your vehicle will take damage not only from collisions with other vehicles and objects, but also from bouncing all over the particularly rough terrain. When your damage meter runs out, your engine stalls, and if a police vehicle touches you while you’re stalled, you’ll be placed under arrest. If no cops are around, you can restart your engine and continue on your merry way…though chances of that were seriously unlikely. The AI-controlled police were absolutely relentless, chasing you everywhere you go, which is why I mostly spent my free time in the Joyriding mode, free from such hassles.

For its time, Smuggler’s Run looked fantastic. The game’s terrain is large and detailed, and pop-up and fog were nowhere to be found…though that giant green arrow pointing you to your mission objective was then and is now beyond fugly. Each of the three maps are massive, with the missions taking place in smaller sections, but you aren’t limited in where you can roam. There’s also quite amount of small details everywhere, such as tire marks, active wildlife, train tracks, and actual hiking trails, which are just things you expect nowadays, but really helped add a bit of realism to the game on the PlayStation 2.

Evidently, they made a sequel with Smuggler’s Run 2, though I never played it. The only interesting factoid I know about it is that the game was originally supposed to take place in Afghanistan, but following the attacks on the World Trade Center on September 11, 2001, as well as the subsequent invasion of Afghanistan, the developers changed the Afghanistan levels to the deserts of Georgia/Russia instead. Rockstar also later released downloadable content for Grand Theft Auto Online named Smuggler’s Run, which added a customizable hangar and additional vehicles to play around with. At least they didn’t completely forget about this IP.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: Vandal Hearts

At first, I couldn’t remember the name of this game. Was it Valiant Hearts? No, that was the dramatic Great War take starring a cool dog from a few years back. Was it Vigilante Hearts? No, though something under that title does appear to exist. At last, after some light Googling, I figured it out and everything came rushing back…Vandal Hearts, one of my first stabs at a strategy RPG, as well as the title that helped pave the way for future classics like Final Fantasy Tactics and the Ogre Battle series. Too bad this one didn’t really go anywhere. Also, don’t expect it to show up on the forthcoming PlayStation Classic…though I’m surprised that both a sequel and a prequel were later made.

Anyways, this Vandal Hearts is a turn-based tactical role-playing video game developed by my once favorite companies Konami Computer Entertainment Tokyo for the original PlayStation back in 1997. It’s got a lot of what many modern, staple SRPGs have these days, such as Fire Emblem and its ilk: a grid-based map, a variety of abilities to employ, and rock/paper/scissors combat. Y’know, warriors with swords kill archers, archers kill hawknights, and hawknights kill swordsmen. There’s also healers, mages, heavy armor warriors, and monks to contend with–who later can turn into ninja, y’know like all monks eventually do. Your enemies for each mission is comprised of similar classes, and it’s your responsibility to exploit their weaknesses, and not every mission is about destroying all the enemies as other objectives are in play.

Vandal Hearts‘ story, as far as I can remember and dig up info on, revolves around one Ash Lambert, a young warrior tormented by the traitorous legacy of his father. Ash and his wonderfully named cast of allies have dedicated themselves to stopping a power-mad dictator named Hel Spites–what a name–from rising to power. It’s a bit traditional, but I liked a lot of the characters and dialogues, and there are some early twists to deal with that make their progress slow and, at times, a little dull.

I definitely did not ever beat Vandal Hearts. I probably didn’t even get too far into the whole affair as I knew early on that SRPGs just weren’t my cup of tea. Though many years later some titles would change my mind momentarily. I do remember being confused why archers were not able to shoot diagonally. Also, moving a cursor around with a PlayStation console was a chore and never felt fluid. Still, it’s a game I think about from time to time, maybe because I dig its aesthetic so much, or because I spent so much of my lonely teenager years hanging out with my best friend the gray videogame console adorned with PSM lid stickers, and the music is super solid.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: Midnight Club: Street Racing

This might be hard to believe, considering my long and well-documented love for all things racing games, but I willingly bought a copy of Midnight Club: Street Racing for the PlayStation 2 some time back in that wacky, inexplicable decade known as the aughts. I suspect I got it for cheap at the Blockbuster near my college’s campus when they started selling used games–or rather “previously rented”–but that’s just a suspicion, based mostly on the fact that that is where I got a small chunk of my early PS2 collection during my poorer days eating ramen noodles and working a few hours during the week in an art gallery. For the record, and yes, I just looked, here are all the games still in my collection rocking a “Previously Rented Game – Quality Guaranteed” label from the now defunct Blockbuster business:

Yup. Quite a super-squad there. With that said, let’s get on to the star of today’s show. Everybody, start your engines. Vroom vroom vroooooom…

Surprisingly, for a game centered around driving speedy cars quickly and aggressively, Midnight Club: Street Racing kind of had a story behind all its engine-driven action. Granted, around that timeframe, my experience was fairly limited to car-related adventures through things like Vigilante 8, Super Mario Kart, and Crash Team Racing, where vehicular combat was the central element, and it didn’t matter who was behind the wheel so long as they could toss projectiles out like everyone else. So, taking place in both New York City and London, you’re a bored-as-bored-gets cabbie looking for some street-style racing action…for reasons. Magically, you stumble across your first challenger named Emilio and are then invited to join the titular Midnight Club to continue proving your worth and burning gang leaders in races. There’s no real introduction, and the dialogue sections are flat images with character portraits speaking while two cars sit idly next to each other. Look, it’s not Great Expectations, or even Fast Five, but it’s something.

Not shockingly, when you see that Rockstar had a hand in this, but Midnight Club: Street Racing is a bit open-worldish. Y’know, a genre just starting to hit its stride then. You’re able to cruise around the respective cities, looking for trouble in the form of hookmen, which are visible on your mini-map, which, when you glance at the screenshot above, defies the definition of the word mini greatly. I mean, that was the UI for the era–big, bright, and loud. Anyways, once you get behind them, you’ll have to keep up with their ride until they feel that you’re worthy of a race, which is you against that driver’s entire posse. Also, you can call up these hookmen on your cell phone–a novel concept back then–for a more fair one-on-one race. If you win the race, you get to add your opponent’s car to your garage, which I guess is akin to carving up a dead animal and wearing its skin as a prize. I don’t know a lot about cars.

I remember being initially impressed by the scale of Midnight Club: Street Racing offered, but do remember the cities feeling lifeless and empty. Now, I’ve only ever been to New York City, and I remember a lot of cars and honking while there, as well as swarms of people; here, it is just mostly empty streets, with little traffic to deal with, and that just wouldn’t cut it today. Still, one must consider that this game came out before things like Grand Theft Auto III and Need for Speed: Hot Pursuit 2. It was also frustrating that, to even start a race with another member of the Midnight Club, you needed to follow them to the starting line first, weaving through traffic and praying they didn’t get too far ahead of your slow whip, which was often more challenging than the race itself.

Most races are checkpoint races, which means you can veer off the beaten path so long as you hit all the checkpoints and cross the finish line before anyone else. That might sound like there’s a ton of freedom at hand, but this is a condensed city-scape and not miles of Smuggler’s Run‘s open terrain, and there were generally only one or two ways to get the job done efficiently. If rubbing and racing isn’t your thing, well…there’s an arcade mode, which lets you set up head-to-head, checkpoint, and two-player races. Also, some sort of capture the flag mode where you need to bump into the car carrying the flag to steal it and then deliver to some hotspot on the map. I don’t believe I ever took down the gang champion of New York City, thus never even seeing the second half of the game set in London.

I have no idea if Midnight Club: Street Racing hold up in 2018, and I’m not interested in finding out. Still, if I had my copy around, I might pop it in randomly one night for a zip down memory lane, but oh well. Much like Blockbuster, this franchise stalled years ago, and newer, more efficient racers have taken the lead, like Burnout Paradise.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: X Squad

From one X to another, we move from talking about the highs of Mega Man X and how much it brought to the somewhat stale format to diving into X Squad, a PlayStation 2 launch title that, if I’m being honest, wasn’t all that good, but still holds a special space in my heart because it was one of a handful of games I owned after acquiring my hard-earned console. Also, by we I of course mean me, because this is Grinding Down, a singular voice shouting into an echo chamber, praying anyone is out there listening. If you are all ears, please, don’t be afraid to say hello. Tell me your favorite Animal Crossing villager or type of sushi roll. Anything.

Well, in X Squad, you play as John G. Ash, leader of the titular group. It’s the year 2037. Graduating at the top of his class at West Point, he excels in both marksmanship and urban-combat simulation, which is probably what got him the commanding role after forming his personalized team of problem-solvers. Something bad is happening, and the X Squad is called in. I think it has to do with a bio-terrorist organization releasing a devastating plague upon a major metropolitan area, but that’s only known from reading a summary over here. There’s not much story to go on from the get-go, with much of the plot kept secret even as you progress through the early levels. The opening cinematic is extremely vague, immediately starting with Ash talking about investigating “the situation” and ensuring that recon is passed on to the right people, but it doesn’t get any more specific than that, which makes it come across as an empty action hero romp–which is most certainly wants to be.

If I recall correctly, X Squad plays a lot like 989 Studios’ Syphon Filter, minus the cool animation you get when you don’t stop tasering an enemy or Gabe Logan’s hypnotizing swaying hips. You can roll in a bunch of different directions, as well as duck or peek around corners to get the upper hand on unsuspecting enemies. That’s all fine and somewhat standard for this type of run-and-gun action title, but the aspect that ends up making X Squad stand apart from its competitors ultimately detracts from the entire experience, offering next to no value. With only a few simple button presses, Ash can bark orders to his teammates, tasking them with things like scouting out an area to backing you up with gunfire. SOCOM U.S. Navy SEALs this is not. These commands fall under terms like “follow,” “recon,” and “stay.” Your teammates are never really as helpful as they should be, running into rooms of armed men wildly without even bothering to take cover, but thankfully you don’t need to rely on them 100% to make it through a mission with skin still attached to your bones. Still, the point of a squad is to fight as one singular unit, and that’s not the case here. Ash is better on his own, using his teammates more as distractions than anything else.

Also, X Squad is not a looker. I mean, it was a launch title for the PlayStation 2, and it shows. Besides having a bland, flat look to the environments and character models (save for Ash’s spike-tastic hair), glitches are bountiful, with flickering being a common issue. Sound-wise, there’s a lot going on here. The voice acting is stiff and uninspired, and though I like the inclusion of voiced tutorial prompts, it’s not executed well. Still, the door opening sounds are pretty good. The biggest compliment I can give X Squad is that those are some sick and consistent drum beats playing in the opening level (warning: they don’t kick in for at least a minute, but it’s worth the buildup). Also: really great slap bass lines throughout. Honestly, the OST is the reason to play X Squad, but you could also not play it and simply let your ears enjoy everything over on YouTube. Your call, boss.

Still, all that said, and I continue to lack the words to explain this phenomenon, I regret trading in my copy of X Squad. Maybe it has less to do with the game’s quality and more to do with the fact that the PlayStation 2 was the first console I purchased myself as a working lad, busing tables, and so every early game in my collection was special, regardless if it ultimately was special or not. I’m seeing copies on Amazon for around $8.00, and I sadly think that’s too steep of a mountain to climb. I’d love to see this come to the PlayStation Network as a downloadable, but I think the ship for digital PS2 games on that system has sailed, with no map or fuel reserves or even captain, never to be seen again.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: G-Police

When I think of Colony Wars, I think of G-Police. Conversely, when I think of G-Police, I also think of Colony Wars. Which I’ve already covered via this blog post tag, sadly. Though I do have a retail copy of Colony Wars: Vengeance somewhere among my small collection of PlayStation 1 games, though I don’t know if it better than the original. I hope to try it out…one day. Anyways, the two simulation shooters for the PlayStation 1 share the same space in my brain, and that space is the zone designated to sci-fi games where you pilot a futuristic spaceship of sorts. I have to imagine that I traded both in at the same time, forever marking one of the darkest days in the history of me.

G-Police takes place in 2097, when most of Earth’s resources are depleted. Because of this, humanity is beginning to form colonies on other worlds. So, basically, our future future. You are a man named Slater, a member of the futuristic government taskforce known as the G-Police. I’m going to go out on a limb and say that stands for governmental-police. Or maybe grassfed. His role is to maintain order on Callisto, one of Jupiter’s moons, as well as discover the truth behind his sister’s mysterious death. Because there has to be something else driving him forward besides him driving forward his g-copcar after criminals. I honestly don’t remember much of this murder mystery plot, as I was more strangely focused on doing cop-like things, such as escorting people to safety and…uh, other tasks.

Speaking of Slater’s g-copcar, it’s actually a vertical take-off and landing aircraft called the Havoc. You end up piloting this VTOL piece during the game’s various missions. Some missions require the gun-ship to drop bombs on enemies below while others are straightforward dogfighting sessions. Other mission objectives include escorting ally ground units, preventing smuggling, bomb disposal, and scanning for suspect vehicles. Sounds like there were 35 missions in total, as well as a bonus training mode, but I definitely never beat G-Police, just like how I never beat the original Colony Wars. I did, however, play their early levels over and over again because I enjoyed them that much. Also, the difficulty ramps up quickly.

I do remember the Havoc being a pain to control though. Every button on the PlayStation 1 controller was used to maneuver the heavy-as-heavy-gets thing. You could thrust forwards, backwards, up, and down, as expected, and you could also hold your altitude by holding the upward and downward thrusts. This was ultimately tricky on the original PS1 controller, but vital for making it through the missions in one healthy, whole piece. Unfortunately, and this was just kind of before its time, you were not able to move left or right without turning, what we now know as strafing. I have this really strong memory of lowering the Havoc to street level and watching citizens and vehicles going about their way.

That said, the Havoc had weapons. The selection was robust and expanded as you progressed through the missions. Missiles were your main mode of enforcing the law, with a good balance between strength and tracking enemies on the map. Locking on to objects also scanned them, with some missions requiring you to look for contraband cargo and the like. I enjoyed these, and this is one of the earlier signs that I preferred less violent gameplay means when possible, which is why I’d always lean towards stealth over guns blazing in the years to come. Certain missions also outfitted you with special items, ranging from bombs that can perform an EMP blast to shut down fleeing vehicles or a flare launcher to mark a location for SWAT teams on the ground to move in on. Y’know, cop stuff.

G-Police was heavily inspired by Blade Runner, but I didn’t know that at the time I bought it. Why? Well, I didn’t end up seeing Blade Runner until only a handful of years ago. I know, I know–my bad. There’s plenty of futuristic city stuff to eat up, like advertising blimps, hovercars, and neon lights. Lots of green and orange-red in your HUD, which is pretty close to what it is like in Descent, though I’m only now making that connection. You could also pull the camera out and play from a different perspective, but I mainly stuck to the first-person, inside-the-Havoc view. Graphically, G-Police was not a stunner, with a dark, oppressive environment and pop-up around every corner, but the thwumping techno-driven soundtrack helped alleviate some of these limitations.

However, in the end, G-Police was another take on the Colony Wars experience, and that was enough for me to hand over my hard-earned cash from washing cars and watering lawns and procure a copy. Alas, I never got to see it all the way through before giving it up for in-store credit, but I still remember its earliness fondly. I should find a full YouTube playthrough of it for my next marathon drawing session.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: Mega Man X

games I regret parting with Mega Man X

Mega Man X, as far as I can remember, is the only game in Capcom’s long-running and blaster-charging run-and-jump action series where an innocent-looking robot boy obliterates rogue worker automatons that I’ve beaten. Granted, I haven’t actually played all that many, and that’s mostly because they are challenging gauntlet runs that punish more than they reward. Still, back when I was younger and only had so many games to play and few IRL distractions, practice made for better attempts, and I eventually saw credits roll on Rockman’s first appearance on the Super NES. I absolutely know that getting all the capsule upgrades played a big part in this accomplishment. Without them, I probably wouldn’t have gotten past Chill Penguin. Sick frost burn.

Do you know Mega Man X‘s somewhat maturer plot? If you do, congrats. You can skip ahead two paragraphs. If not, allow me to summarize. Dr. Light created Mega Man X, commonly known as just X, years after the original Mega Man series, with a key difference: the ability to make his own decisions. However, Dr. Light was not completely blind and thus recognized the potential danger of this model, sealing X away in a diagnostic capsule for over 30 years of testing. X’s capsule was uncovered by an archaeologist named Dr. Cain almost a hundred years later. Excited by the possibilities X presented, Dr. Cain disregarded Dr. Light’s notes and warnings and created a legion of new robots that replicated X’s free will–Reploids.

Unfortunately, a virus spread and caused these Reploids turn deadly against humans. Shocking, I know. And so these Reploids became dubbed Mavericks, which lead to the formation of a group called the Maverick Hunters to combat them. Because what else are Maverick Hunters gonna do, y’know? Anyways, the Maverick Hunters were originally led by Sigma, the first Reploid created by Dr. Cain, until it also turned violent and declared war against humans. X joined the Maverick Hunters under its new leader Zero to save Earth from total evil robotic domination. It’s a story much more complicated and involved than the original NES games, which, as a young man with a blossoming brain and beginning to dip his toes in things like anime, I enjoyed greatly.

Mega Man X introduced a lot of new elements to the series. Like the Central Highway Stage, which is basically a tutorial level that allows players to get a feel for the game before setting out to stop the usual kill list of eight named bosses. It is in this level you are first taught how to dash along the ground, cling to walls, and wall jump, as well as dashing and jumping simultaneously, increasing X’s speed in the air. These modifications give X far more mobility than in previous games, which, often required precious timing and accuracy, especially when trying to jump from vanishing platform to vanishing platform. I don’t remember if I played Super Metroid before or after Mega Man X, but the wall-jumping is much easier to nail in the latter.

Besides gaining new weapons after kicking the metal butts of every robot leader, X is also able to upgrade parts of his armor, such as his helmet, boots, arm cannon, and chestplate. These are found in hidden capsules, and they are, as far as I can recall, fairly well hidden, save for the first one, which you have to stumble across for story purposes. X can also charge up the weapons he takes from defeated bosses, giving him a secondary fire mode. More options equals more fun, and some levels even feature alternate paths. Also, completing certain stages ahead of others will subtly affect the battlefield. For example, if you clear Storm Eagle’s aircraft carrier stage first, Spark Mandrill’s power plant stage will suffer from electrical outages.

And now, for everyone’s enjoyment, a list of the bosses in Mega Man X, which, at the time of its release, I thought were beyond cool, but now see that as simply uneducated madness:

  • Chill Penguin
  • Spark Mandrill
  • Armored Armadillo
  • Launch Octopus
  • Boomer Kuwanger
  • Sting Chameleon
  • Storm Eagle
  • Flame Mammoth

Actually, I still think Launch Octopus is pretty killer. We can blame that on Kojima and Decoy Octopus, I guess. Pretty much any combination of [cool word] plus octopus sounds fantastic. Like Fugazi Octopus. Or Mozzarella Sticks Octopus. See–works every time.

Giant Bomb is currently working their way through the Mega Man games with their premium video series Blue Bombin’, and I’m not sure if they’ll be playing the Mega Man X series of games, but here’s hoping they at least give the first one a chance as it certainly switched some things up for the little blue boy who could. I’ll always remember it fondly and wonder why on Earth I thought it was a good idea to give away this classic SNES cartridge (plus original packaging and manual) for a few measly bucks towards an original PlayStation 1. Sigh.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.

GAMES I REGRET PARTING WITH: Super Ghouls ‘N Ghosts

games i regret super_ghouls_n_ghosts

Starting out, I had only a few games for the Super Nintendo, my first home console. Back then, unlike today, games were scarce and limited, gifts given to you by loved ones every X number of months or purchased via the savings you had from doing daily chores over the summer, and so you played what you had, over and over and over, because they were the only digital entertainment you had. Hopefully your friends had different titles to try out. Well, you also played Super Mario World, Super Metroid, and The Legend of Zelda: A Link to the Past over and over again because they were fantastic, constantly surprising and rewarding, beyond fun to this day. More to the topic at hand, I played Super Ghouls ‘N Ghosts over and over again because it was frustratingly difficult.

You control the knight Arthur, who is entrusted to rescue the princess from a bunch of evil demons. Yup, game plots back then were as straightforward as they get, often with men saving a woman in peril, whether that man was a plumber, young boy, or legendary warrior. Anyways, Super Ghouls ‘N Ghosts‘ antagonist is the Emperor Sardius, who has kidnapped the princess in order to obtain the whereabouts of the Goddess’ Bracelet, the only weapon in existence capable of destroying himself. Kind of like a Horcrux, I guess. Hmm. I didn’t know about that last tidbit, but seeing as I never got really far along in this mighty quest, that makes plenty of sense.

For those that know not, Super Ghouls ‘N Ghosts is an action platformer, with a good focus on both action and platforming. Health is represented by Arthur’s suit of armor, which can be upgraded a bunch of times. Whenever an enemy deals damage, the armor lessons, falls apart, all the way down to having our heroic hero running around and tossing lances in only his boxer shorts. It’s humorless, but works really well to visually show how much more damage you can take before buying the farm. Oh, and Arthur can double jump, which was not as common as you think back then. Other than that, it’s all about moving and reaching the end, killing every demon or demon-created enemy in your way.

The big thing I remember about Super Ghouls ‘N Ghosts is that, just like in DuckTales, treasure chests are hidden and can only be accessed by moving through certain specific areas of the screen, causing them to appear. Thankfully, since I sucked at saving the princess, I got pretty good at knowing where many of the hidden areas were in the first few levels.

Years later, after piling this game up with a bunch of others and trading it in for some credit towards a PlayStation, I snagged a copy of Maximo: Ghosts to Glory for the PlayStation 2. It is based on the same universe and features original character designs by Japanese illustrator Susumu Matsushita. Despite having an albeit punishing save system, the game is still as grueling to get through, but I’m once again halfway decent at the opening few levels, as I just keep replaying them from time to time.

Evidently, to get the true ending and ruin the rest of Emperor Sardius’ days, one must complete Super Ghouls ‘N Ghosts twice. In a row. I’m sure it’s been done. I’m sure all I have to do is type some words into the YouTube search box and I’ll see what I want to see. That said, I prefer living in ignorance, remaining a child in his bedroom, twisting the SNES controller in my sweaty palms, screaming at the TV, “This game is impossible!” before popping back over to causing chaos in Sim City. I know it’s not, but Arthur’s journey is not a walk through the park. It’s a walk through a skeleton-laden park that hates you. Now double that feat and keep your clothes on the entire time. No thanks.

Sure, I like playing that opening level a whole bunch, but maybe, in the end, this is actually one game I don’t regret trading in.

GAMES I REGRET PARTING WITH is a regular feature here at Grinding Down where I reminisce about videogames I either sold or traded in when I was young and dumb. To read up on other games I parted with, follow the tag.