Final Fantasy Friday

In principle Jim the Editor and I are supposed to be streaming Final Fantasy X tomorrow morning/tonight (7am NZ time, 8pm UK time). Unfortunately, Jim’s just moved to a new flat and doesn’t have a good enough internet connection for streaming. For this week, we’ve pre-recorded something and are going to have it go live with Youtube’s premier feature, so we can have it air at the usual time with a live chat. As always, come and hang out if you’re free!

A Pokémon Trainer is You! XXIII: See the Forest for the Trees

[Catch up on the story so far here!]

Last time, on A Pokémon Trainer Is You:

What do you do with your prisoners?
– Restrain Kevin so you can drag them both to the authorities.

You all take a moment to revel in your victory and high-five each other before doing anything else.  You’ve got time; Ned is already pretty securely tied up, and Kevin… well, Kevin’s still moping over his unconscious Zubat.  Poor guy seems like he’s having some kind of breakdown.  Abner has his Pokémon start spinning more silk, and you help him tie up Kevin and attach some extra leads to Ned’s cocoon so you can drag him along the ground behind you.  Meanwhile Stacey and Ellis tend to the injuries the Pokémon have suffered – including Zubat.  You aren’t sure about the ethics of confiscating the loyal Pokémon of criminal trainers, and you don’t want to risk Ned’s Pokémon trying to fight you if you let them out, so you get Kevin to recall his Zubat and decide to let the police in Pewter City sort it out once you get there.  Neither Kevin nor Ned seem to be in any mood to talk (even if Ned’s mouth weren’t muffled by the silk), and refuse to say anything about their operation.  Once you’re sure Kevin’s hands are securely bound, you start moving back in the direction of the clearing where you found them.

Continue reading “A Pokémon Trainer is You! XXIII: See the Forest for the Trees”

Pikachu

Pikachu

Somehow, after writing on this blog for nearly 10 years(!!!) and having reviews of individual Pokémon be a pretty big part of my schtick, I’ve never actually talked in depth about Pikachu – the beloved mascot, the one Pokémon everyone knows, even people who have never played a Pokémon game or seen an episode of the TV show; heck, I’d wager there are people who don’t even know what a Pokémon is who’d recognise Pikachu.  But no more, for I have been commanded by the mysterious cloaked figures of my Dark Council to write next about the most famous Pokémon of all.  So… what exactly is Pikachu’s deal, anyway?  Where did it come from, and what makes the design so effective?  Whence Pikachu?  Read on, as we delve into the history of Pokémon’s favourite child.

Continue reading “Pikachu”

jeffthelinguist asks:

Maybe this answer exists somewhere online and I’m dumb, but… what benefit does Sudowoodo have using mimicry to appear as a tree? It seems like that is a poor choice for a rock type given it’s weak to water (which intelligent creatures will naturally pour on it).

uh

well, it

um

I suppose my first instinct is to say that, on an evolutionary timescale, creatures who see plants and immediately think to pour water on them are probably a recent enough arrival in the world that they wouldn’t have had much impact on Sudowoodo’s physiology or evolved instinctive behaviour yet.  But we don’t really know that’s true; there are Pokémon that modify and curate their environments; there are even Pokémon that tend gardens.  The Pokédex says that Sudowoodo looks like a tree to avoid predators, and that does make sense to me; I have no problem with that.  So I suppose the best answer is probably that looking like a tree does work really well for its intended purpose – well enough that it’s worth accepting the unfortunate side effect of sometimes having water poured on you.

Tapu Wooloo asks:

Would it be possible for Pokemon to retire the concept of “fainting”? Originally, Game Freak wasn’t even sure what fainting even meant–when you tried to send out a fainted Pokemon it said “there’s no will left to fight,” and in the early anime trainers simply withdrew a Pokemon when it clearly couldn’t fight anymore. So what if “[Pokemon] fainted” could be replaced with “[Pokemon] gave in” or something?

I’m not sure that it matters, particularly?  I certainly wouldn’t have a problem with changing it, but “fainted” isn’t a terrible word for what they use it to mean, and the condition itself is simple enough – the Pokémon can’t battle, full stop – that I don’t think it’s all that important to have precise language for describing it.  You could do away with the entire concept, and replace it with a range of more specific ways a Pokémon can be debilitated, each caused by particular attack types, requiring specialised forms of care and having different lingering effects after the Pokémon is healed.  I think you could build an interesting system out of that, although it wouldn’t be a very good fit with Pokémon’s general direction over the last several generations; it’s more of a “darker and grittier” mechanic.  If it’s just changing the name to slightly better reflect what we already imagine is happening, I could happily go either way.

Patchface asks:

Who would win in a fight to the death, all the Gen 5 Pokemon you allowed to live, or all the Gen 5 Pokemon you condemned to die?

Well, in general one of the criteria I used for letting them live or die was whether they were actually any good, so… well, the ones who lived get most of the legendaries, all three starters, Hydreigon, Excadrill and Volcarona… and the ones who died get, like… fµ¢£in’… Watchog and Emolga and $#!t.  I mean, it’s not all bad, they get Bisharp, and Bisharp is legitimately a lot better now than it was in generation V, but still… I dunno if I see it working for them.

Leo M.R. asks:

I watched a Pokémon video on YouTube where the guy pointed out that, for all the hype Mega Evolutions got prior to the release of XY, you actually only ever fight three Mega Evolutions throughout the course of the main story: Korrina’s Mega Lucario, Lysandre’s Mega Gyarados, and Diantha’s Mega Gardevoir. He argued that 1) the first one doesn’t even count because it was just a Mega Lucario battle, and 2) this is a big reason why XY felt too easy, especially since you can Mega Evolve after the third Gym. He suggested that, since you fight Lysandre before the final Gym, Wulfric and the Elite Four should all have been given Mega Evolutions, something the anime actually does (sans Drasna). It’s an excellent point and I… don’t know why Game Freak didn’t do this in the first place, now that I think about it. The final rival battle at Victory Road should probably also have given them their eventual Mega Absol, if Wulfric should have a Mega. What do you think?

…huh

Y’know, I never really thought about that – when I played X for the first time, I never used Mega Evolution unless my opponent did as well, because it seemed “unfair,” so I guess I just wasn’t thinking about it very hard.  But yeah, considering that Mega Evolution is generation VI’s flagship mechanic, it’s… not actually in there very much.  Alpha Sapphire and Omega Ruby are kinda light on it as well, at least in the main story; there’s… what, Archie/Maxie, Wally and Steven?  But then there are a lot more in the postgame: May/Brendan, Matt/Courtney, Zinnia and all of the Hoenn Elite Four.  X and Y don’t really have that.  This seems doubly weird considering how much work must have gone into designing the Mega Evolutions.  Wouldn’t you want to show them off?  I can see a perspective where finding all the Mega Evolutions is mainly meant as an end-game side-quest for the player, a little challenge for the 100%-completionists, but a) the Pokédex already provides plenty of that, and b) it would make a lot more sense if Pokémon had, like, Final Fantasy-style “bonus bosses” where you really needed the right Mega Evolution to win.

Continue reading “Leo M.R. asks:”