Interactive Friction: Watch_Dogs: Episode 15: Hope Is A Sad Thing

Now that I'm watching Sam play through this game again, I'm only now realizing just how much pointless fluff is in this story.

At this point in the story, we have acquired a part of the data located in Iraq's compound. Unfortunately, it's encrypted with a special encryption that can only be broken by the person who developed it: A former Blume employee named Raymond Kenney. (Blume is the company that made CTOS. Since this rarely comes up, you can be forgiven for not knowing that.)

Ignoring the fact that this data really isn't that important to our overall objective of figuring out who killed our dead nice, and further ignoring the fact that Clara should be able to get her hacker friends in on breaking the encryption, Aiden Pearce decides he needs to recruit Raymond Kenney to the cause in order to crack it.

At least the prostitution filler had the absolute mercy of being short. This is a entire act, consisting of 6 missions, dedicated to recruiting this guy to crack a code that doesn't need to be cracked, when should already have the resources required to do it ourselves.

I hate this game.

But on a more positive note, since we mention each of these guys early in the episode, it's worth linking to them here for your viewing pleasure.
John Green's Moral Story Through Grand Theft Auto 5
GoldVision's Grand Theft Auto Pacifist Series

The Texture Pop: Watch_Dogs: Episode 14: Puzzle Quest

I like the scene at the start of this episode, where Jacks watches Aiden Pearce slaughter several groups of armed men. It pretty subtle compared to many of the other scenes in game, yet that's what gives it power. Jacks doesn't need to say anything, just the simple act of pulling away from his Uncle Aiden is enough to convey everything that needs to be said. The psychologist's threat was just icing on the cake.

And then we get to Bedbug. I strongly suspect that the conversation between Bedbug and Aiden Pearce is meant to humanize Pearce a little bit. However, I personally found that it added more to Bedbug's character than Aiden Pearce's. He's not a bad person. He's just caught in a very bad situation. It's very telling that even after Aiden Pearce led Bedbug into a death trap, he still gave Pearce the information that he needed.

Unfortunately, neither of these people are the protagonist. Aiden Pearce is, much to my dismay.

I hate this game.

Interactive Friction: Watch_Dogs: Episode 13: Detour

Here it is, ladies and gentlemen. I present to you the most uncomfortable part of the game.

I still don't honestly know why this needed to be a part of the game. There's nothing wrong with video games trying to make some sort of point about sex trafficking. However, Watch_Dogs doesn't really say anything about it beyond "sex trafficking is wrong." Of course sex trafficking is wrong. What else do you have to say?

This scene didn't have the power for me that it clearly had on Sam. I thought it was a cheap way to make Lucky Quinn out to be unambiguously evil (and Iraq, by association).

There's also the fact that it's just so segregated from the rest of the plot. Remember, this story is about finding out who killed Aiden Pearce's niece and taking revenge. We know that it is likely the Merlaut job that gave this person motivation to assign the hit. Damien "gave" us the IP of the second hacker present during the Merlaut job, so we traced it to Iraq's compound.

And now, he need to corner Iraq at this slave auction, because of reasons that still never got explained. Since this part is to tertiary to the experience, we don't have time to delve into it. In terms of Aiden Pearce's story, it's not important. It's filler.

To me, the fact that someone so heavy and relevant is just relegated to filler content is unacceptable. If you want to include this kind of stuff, make it important. Make it a more core part of the narrative. If there's nothing to say about it, then why is it being brought up in the first place?

Evidently, whatever they had to say wasn't important to them, because it's relegated to a mere side-quest once this mission is over.

Sex trafficking: The Side Quest

I hate this game.

The Texture Pop: Episode 50: Poppin' Off

This is it, ladies and gentleman. After over two years of podcasting, The Texture Pop's crew has decided to shut our virtual office doors.

As much as we all enjoy doing it (and make no mistake, we ALL enjoy doing this and this is more painful than any of us expected), the simple fact is that we're all really getting busy with our lives. It's been hectic for each one of us, and since we aren't getting paid for this podcast, it's even more difficult to justify the time we spend on it.

Now, this isn't to say that this is the last you'll see of us. Nor is it the last time we'll all get together for a production. Once we all settle into our respective routines, it's likely that we'll reunite for something new.

On top of that, we all have our own projects we'll be working on. Garrett is starting up his Twitch stream. He'll also be joining Chris and number of our old, mutual friends in another video game related project. As for Sam and I, we each have our own blogs and Interactive Friction will continue as normal.

So while The Texture Pop may be over, we're all just getting started! :)

#96: Final Fantasy Type-0: Experience of the Sidelines

I've played a great many RPGs throughout the years. In that time, I have seen many design decisions constantly repeated and reiterated across various different games. Often it makes sense to reuse these tropes. For example, leveling up is such a core concept in RPGs that it would be strange to have no form of character development. However, some of these same choices come back for seemingly no reason whatsoever.

Recently, I beat Final Fantasy Type-0 HD, victim to one of the latter design choices. Taking place in a steampunk/fantasy setting, Type-0 is a war story following the exploits of Class Zero, a group of cadets at the military academy in one of the four great nations in the world. There are 14 members of Class Zero, all playable characters in the game. The player can have, at most, 3 of the classmates deployed at the same time, with other members on standby. When an enemy is defeated, only the 3 deployed classmates gain experience, while every other character gets nothing. And while Final Fantasy Type-0 is hardly the first RPG to make this choice, it’s the one I can best use to explain the problems inherent to it.

Depriving non-participants of experience discourages players from experimenting with their party formation and character selection. When Final Fantasy Type-0 first introduces the player to the full cast, it makes the recommendation to "try to level every character evenly". This, as is the case with most games where members on standby don't gain experience, is a terrible idea. Following this advice will have one of two possible outcomes: Either the party will be so under-leveled that playing through main story missions is an exercise in frustration, or so much time will be spent grinding for experience that the player will completely forget the main story. Raising a character by a single-level takes a great many battles. With 14 playable characters, bringing them up to each missions recommended level would take several hours of tedious grinding. At the same time, missions at a much higher level pit the player against enemies that can and will annihilate a single character in one or two attacks. For this reason, most players will ultimately decided on 3 or 4 characters that they will focus their experience on, and largely ignore the rest of the them.

Part of the draw of a large pool of playable characters is that there is a variety in the archetypes and playstyles. Under the restriction that party members only level up when they actively partake in battle, this variety is stifled by practicality. For instance: there might be circumstances where it would make more sense to use a long-range party of King the duel-pistol wielder, Cater the magic-gunslinger, and Trey the archer, like when a mission is packed with flying enemies out of melee range. However, most people will likely only have one of them leveled enough to use in that mission. While it may make more sense to use that particular party against ranged enemies, it makes no sense to use it in any other circumstance.

Since it's only sensible to train up about 4 people, most players will have a strong melee-character, a good ranged character, and a support, with a possible backup character in the event one of the first three dies. Any thought of changing up the party to suit a new situation, or experimenting to find a formation that may work better, is thrown to the wayside in favor of sticking with the old and familiar.

On top of that, games with sufficiently large casts nearly always have scenes where the party has to divide itself into multiple groups, and Final Fantasy Type-0 is no exception. Several missions have the player form 2 groups of three cadets each. Since the odds are that most players will only have enough characters leveled up for one full battle party, this section is significantly worse than it should be. Practicality, it ensures that one team will be vastly inferior to the other, or that both teams will have one under-leveled character dragging them down. In either case, battle ability is severely reduced because the player has done exactly what the game's systems have incentivized them to do.

In my playthrough, during the first of these missions, both of the parties had two characters that were Level 30, and one trailing far behind at Level 15. Unsurprisingly, the weak one in each party did hardly any damage, spending most of the mission as a corpse. With two characters left to pick up the slack of a three-person job, I didn't have as much fun with these missions as did with the others in the game. I had to restart this mission several times because, with the addition of my undue handicap, the enemies were just strong enough that my two level 30s in one team taking much more damage any dying more than they had in other missions. At one point, I even had to give up, go into a previous save, and rethink who I sent with which team. Needless to say, I was fairly unhappy with the game for crippling me like that.

Even though it’s extremely clear that this one concept hurts the games that use it, it is unlikely to get phased out anytime soon. As a genre, RPGs are soaked in tradition, making it difficult to weed out overused design cliches. Even worse, this is one that appears frequently, even in many of the greats like Persona 4 and Valkyrie Profile. Knowing this, I still think it's healthy to evaluate these game design tropes to see if they're still worth maintaining. Though it's common for the reserve party to not gain experience, this trope does more harm than good.