Belle and I were planning on getting a Roku to replace our five-year-old XBox this Christmas, since the games are drying up and it doesn't make any sense to pay for a Live subscription just to watch Netflix and HBO. I still kind of bear a grudge against Sony for the CD rootkit they passed around years ago, but then my employers at ArenaNet bought everyone a PS4 as a holiday bonus. I am, it turns out, not above being a hypocrite when it comes to free stuff.
You can explain a lot about the last three generations of consoles by remembering that, at heart, Microsoft is a software company and Sony is a hardware company. Why did the XBox 360 suffer regular heat failures? Why does the PS Vita interface look like an After Dark screensaver? Our 360 was clearly on the edge of another DVD failure, so I bear them no particular good will. But you have to admit: up to the point that a given XBox malfunctions in one way or another, Microsoft knows how to build a usable operating system. Sony... well, it's not so much a core skill of theirs.
For example, after you turn on the PS4, and after the hundreds of megabytes of updates are done downloading and installing themselves a few times, you're greeted with a row of boxes:
Apparently I'm a little grumpy about the menus.
Anyway for us, this is a media player, which means we'd like to have a remote control, but those don't exist for PS4 yet and it can't use regular IR remotes. The controller layout may make sense to someone who owned a PS3, but it's just baffling to me: why is the button normally used to go backwards assigned here to play/pause duties? To be fair, the XBox never really had a great controller story for DVDs either (both of them put fast-forward on the triggers, where you're guaranteed to accidentally hit it while setting the controller down), but at least it tried to be consistent with the rest of the OS.
You can pair a smartphone with the PS4, which one would think could be a chance to show custom controls for media, what with the touchscreen and all. You'd be wrong: the PS4 app dedicates 90% of its surface to a swipeable touchpad, apparently on the assumption that the three directional inputs on the actual controller are insufficient.
The whole time you're watching a movie, of course, the controller will glow like some sort of demented blue firefly, which helps the camera (which I don't have) to see where I am (hint: the couch). Since you can't just turn off the LED, I've got the whole controller set to shut itself off after ten minutes. This solves the glow, and keeps the batteries from draining themselves at an alarming rate, but now when I want to actually use the controller for something — say, to pause the movie because our dog has started making that special "I'm going to throw up" face — it interrupts with a bright blue screen, every single time, to ask me who I am. Meanwhile, my movie keeps playing in the background.
This is worth some emphasis: on the XBox, a console where we actually had multiple accounts, each new controller that was activated would either log in as the current user or just kind of wait in "guest" mode until the player actually signed in. On the PS4, a console where we have one account, to which I was already signed in with our only controller 20 minutes ago, Sony needs to know my identity before I can perform the critical, account-bound task of pausing a movie. Meanwhile, the dog is now standing sheepishly in front of a vomit-stained rug.
I'm a little grumpy about the media functions, too.
I'm well aware it's a little ridiculous to gripe this much about a free game system. It's not that the PS4 is a bad machine — it's on par with your average DVD player in terms of usability — but I tend to feel like maybe they should aim a little higher. I'm really hoping that these kinds of fixes will be easy to update, since most of the UI is apparently built using web technology instead of painstakingly coded native widgets.
What's really interesting about comparing consoles from both companies is that the kinds of things I really miss from the XBox (pinned items, Kinect voice commands, good media apps) weren't there from the start. Microsoft has gone through at least three major revisions since they released the 360 in 2005. Even though there have been regressions (and the ads have certainly gotten bigger over time), the overall trend has been for the better — in part because they've been effectively allowed to throw the whole thing away and start over. As far as I can tell, the PS3 was also improved, even if it wasn't reinvented in the same way. It takes a lot of nerve to make sweeping changes like that, and as well as a conviction that the physical box is not what you're selling — a philosophy that's well-suited to Microsoft's software background, but that even hardware companies can no longer ignore.
I've been so embedded in a constantly-shifting web environment for so long that I sometimes forget that not everything updates on a monthly basis. Sony will be more conservative than Microsoft, but even they will be rolling out patches to the PS4, many of which will probably address my complaints. We live in a world where you can turn around and find that your DVD player, or your phone, or your browser suddenly looks and acts completely differently. That's great for people like me who thrive on novelty, but it now occurs to me just how disorienting this might be for ordinary people. It may be worth considering whether a little stability might be good for us — even if it means preserving the bad with the good — and whether the technical community might benefit from a little sympathy to users overwhelmed by our love of change.
There's a fine line between nonchalance and disregard for the player, and I'm not sure that Aquaria doesn't cross over it. As one of the best games on the Shield right now, I've been playing a lot of it — or, rather, alternating between playing it and looking up clues online. In a way, I respect the sheer amount of content the developers have put together, and the confidence they have in players to discover it, but I could use a little more signposting and, to be honest, a bit more challenge.
For example, the middle section of Aquaria is mostly non-linear: certain areas are locked away until you've beaten a few bosses and taken their abilities, but the order is still mostly flexible. Although it sounds great in theory, in practice this just means you're repeatedly lost and without a real goal. Having enormous maps just makes exacerbates the problem, because it means you'll wander one way across the world only to find out that you're not quite ready yet and need to hunt down another boss somewhere — probably all the way at the other end.
I'm goal-oriented in games, so this kind of ambiguity has always bugged me. The Castlevania titles post-Symphony of the Night suffer from this to some extent, but they usually offered something to do during the trip that made it feel productive--levelling up your character, or offering random weapon drops. Aquaria has a limited cooking system, but it's only really necessary in boss fights and it rarely does anything besides offer healing and specific boosts, so it's not very compelling.
According to an interview with the developers, Aquaria was originally controlled with keyboard and mouse, and they eventually moved it to mouse-only (which came in handy when it was ported to touch devices). Every now and then the original design peeks through, like when certain enemies fire projectiles in a bullet-hell shooter pattern. The Shield's twin-stick controls make this really easy (and fun) to dodge, but since the game was intended for touch, these enemies are relatively rare, and the lengthy travel through the game tends toward the monotonous.
Look, I get that we have entered a brave new world of touch-based control schemes. For the most part, I am in favor of that — I'm always happy to see innovation and experimentation. But playing Aquaria on the Shield makes it clear that there's a lot of tension between physical and touch controls, and it's easy to lose something in the transition from the former to the latter. Aquaria designed around a gamepad (and an un-obstructed screen) could be a much more interesting game. Yes, it would be harder and less accessible — but the existing game leaves us with "easy and tedious," which is arguably a worse crime.
I'm starting to think that in our rush to embrace casual, touch experiences (in no small part because of the rise of touch-only devices), we may be making assumptions about the audience that aren't true — such as the idea that it's the buttons themselves that were scary — and it's not always a net positive for game design. At its heart, Aquaria is a "core" game, not a casual game: it's just too big, and the bosses are too rough, for this to be in the same genre as Angry Birds or whatever. Compare this to Cave Story (its obvious inspiration), a game that was free to cram a ridiculous amount of non-linear content into its setting because its traditional platforming gameploy was so solid.
There is a disturbing tendency for many people to insist that there must be a winner and a loser in any choice. In the last two weeks, every tech site on the planet decided that the loser was Nintendo: why don't they just close up shop and make iPhone games? I think it's a silly idea — anyone measuring Nintendo's success now against their performance with the Wii is grading them on the wrong end of a ridiculous curve — and Aquaria only makes me feel stronger about that. For all that smartphone gaming brings us, there are some experiences that are just going to be better with buttons and real gaming hardware. As long as that's the case, consoles are in no danger of extinction.
Let's say that you're making a new game console, and you're not one of the big three (Sony, Microsoft, and Nintendo). You can't afford to take time for developers to get up to speed, because you're already at a mindshare deficit. So you pick a commodity middleware that runs on a lot of hardware, preferably one that already has lots of software and a decent SDK. These days that means using Android, which is why most of the new microconsoles (Ouya, Gamestick, Mojo) are just running re-skinned versions of Android 4.x.
Nvidia's Shield is no different in terms of the underlying OS, but it does change the form factor compared to the other Android microconsoles. Instead of a set-top box or HDMI stick, it effectively crams the company's ridiculously powerful Tegra 4 chipset into an XBox controller, and then bolts on an LCD screen. I like Android, I like buttons, and I spend a lot of time bored on a bus during my commute, so I bought one late last week.
It's a bulky chunk of plastic, for sure. I don't particularly want to try throwing both it and the Chromebook into the same small Timbuktu bag. But in the hand it feels almost exactly like an XBox 360 controller — meaning it's very comfortable, and not at all cumbersome. It's definitely the best package I've ever used for emulators: playing GBA games feels pretty much like the real thing, except with a much larger, prettier screen. I'd have bought it just for emulation, which is well-supported on Android these days.
Actual Android games are kind of a mixed bag. I own a fair number of them, between the occassional Play Store purchase and all the Humble Bundles, and most of them aren't designed for gamepad controls. The Shield does have a touchscreen (as well as the ability to use the right thumbstick as a mouse cursor), but the way it's set up doesn't promote touch-only gaming: there's no good way to hold the screen while the body of the controller sits in the way, and portrait mode is even more awkward.
But if the developer has added gamepad support, the experience is really, really good. I've been playing Asphalt 8, Aquaria, and No Gravity lately, and feeling pretty satisfied. For a lot of games, particularly traditional genres like racing or shooters that require multiple simultaneous inputs, you just can't beat having joysticks and physical buttons. It also helps showcase the kinds of graphics that phones/tablets can pump out if your thumbs aren't always blocking the screen.
So the overall software situation looks a little lopsided: lots of great emulators, but only a few native titles that really take advantage of the hardware. I'm okay with this, and I actually expect it to get better. Since almost all the new microconsoles are Android-based, and almost all of them use gamepads (for which there's a standard API), it's only going to be natural for developers to add controller support to their games. I think the real question is going to be whether Android (or any mobile OS) can support the kinds of lengthy, high-quality titles that have been the standard on traditional, $40/game consoles.
If Android manages to become a home for decent "core" games, it'll probably be due to what Chris Pruett, a game developer and former Android team member, calls out in this interview: the implicit creation of a "standardized" console platform. Instead of developers needing to learn completely new systems with every console generation, they can write for a PC-like operating system across many devices (cue "fragmentation" panics). Systems like the Shield, which push the envelope for portable graphics, are going to play a serious role in that transition, whether or not the device is successful in and of itself.
The other interesting question if microconsoles take off will be whether there's a driver for innovation there. In the full-sized console space, it's been relatively easy for the big three companies to throw out crazy ideas from time to time, ranging from Kinect and Eyetoy to pretty much everything Nintendo's done for the last decade. PCs have been much slower to change, a fact that has frustrated some designers. Are microconsoles more like desktop computers, in that they have a standard OS and commodity hardware? Or are they more like regular consoles, since they're cheap enough to make crazy gambles affordable?
The Shield, perhaps unsurprisingly from Nvidia, points to the former. It's an unabashedly traditional console experience, from the emphasis on graphics to the eight-button controller. It's good at playing the kind of games that you'd find on a set-top box (or indeed, emulating those boxes themselves), but it's probably not the next Wii: you're buying iteration, not innovation--technologically, at least. It just so happens that after a couple of years of trying to play games with only a touchscreen, sometimes that's exactly what I want.
There's a common complaint about the Bioshock games, which is that they're not very good shooters. People writing about Bioshock Infinite tend to mention this, saying that the story is interesting and the writing is sharp but the actual game is poor. And this is true: it's not a very good first-person shooter, and it's arguably much worse than its predecessors. But this implication of most of these comments, from Kotaku's essay on its violence to Brainy Gamer's naming it the "apotheosis of FPS, is that Infinite is bad in many ways because it's a first-person shooter--that it's shackled to its point of view. In doing so, it has become a sort of stand-in for the whole genre, from Call of Duty to Halo.
I sympathize with the people who feel like the game's violence is incoherent (it is), and who are sick of the whole console-inspired manshooting genre. But I love shooters, and it bugs me a little to see them saddled with the burden of everything that's wrong with American media.
Set aside Infinite's themes and its apparent belief that the best superpower is the ability to literally generate plot holes--when we say that it's not a good FPS, what does that means? What is it, mechanically, that separates the two? I'm not a designer, but as a avid FPS player, there are basically three rules that Infinite breaks.
First of all, the enemy progression can't be just about "bigger lifebars." A good shooter increases difficulty by forcing players to change their patterns because they're not able to rely on the same rote strategy. Halo, for all its flaws, gets this right: few of its enemies are actually "tough," but each of them has a different method of avoiding damage, and a different weapon style. By throwing in different combinations, players are forced to change up their tactics for each encounter, or even at multiple points during the encounter. Almost all of Infinite's enemies, on the other hand, are the same walking tanks, with similar (dim-witted) behaviors and hitscan weaponry. I never had to change my approach, only the amount of ammo I used.
Along those lines, weapons need strengths and weaknesses. Each one should have a situation where they feel thrillingly powerful, as well as a larger set of situations where they're relatively useless. This doesn't have to conflict with a limited inventory--I loved Crysis 2's sniper rifle, spending the entire game sneaking between cover positions in stealth mode, but it was always paired with a strong close-in gun for when I was overrun. A good game forces you to change weapons for reasons other than "out of ammunition." Infinite's close-range weapons feel identical, and its sniper rifle is rarely useful, since a single shot alerts everyone to your position.
Finally, every fight cannot simply be about shooting. Most shooters are actually about navigating space and territory, and the shooting becomes a way of altering the priorities for movement. Do you take cover, or dodge in the open? Do you need more range, or need to close on an enemy? The original Bioshock made the interplay between the environment and your abilities one of its most compelling features: electrifying pools of water, setting fire to flammable objects, flinging scenery around with telekinesis. But at the very least, you need an objective from time to time with more complexity than "kill everything," both as a player and in terms of narrative.
Bioshock Infinite has, in all seriousness, no period I can remember when my objective was not reduced to "kill everything." Combined with a bland arsenal and blander enemies, this makes it a tedious game, but it also puts it at complete odds with its characters. The writing in Infinite is unusually good for a shooter, but it's hard not to notice that Elizabeth freaks out (rightfully) during one of Booker's murderous rampages, comes to a cheery acceptance with it a few minutes later, and then spends the rest of the game tossing helpful items to you under fire. That's writing that makes both the narrative and the mechanics worse, by drawing attention to the worst parts of both.
It's not the only shooter with those flaws--people just had higher expectations for it. The average FPS is badly written, and it's a favorite genre for warmongering propaganda pieces. But that's true of many games, and yet we don't see pieces talking about the "apotheosis of platformers," or talking about RTS as though they're emblematic of wider ills just because Starcraft II is kind of a mess. And there's still interesting stuff being done in the genre: Portal and Thirty Flights of Loving come to mind. To say that FPS have reached their limits, ironically, seems like a pretty limited perspective.
During one of those 24-hour colds, when I curl up under every blanket in the house and just wait for the fever to break, I often lose track of reality. It's not like I hallucinate. But, drifting in and out of consciousness with my body temperature far above normal, the line blurs between dreaming and my rational mind, which means I find myself thinking quite seriously about things that are either entirely absurd, or which never actually happened. It's the closest I get to doing drugs.
It may just be that I was playing it after recovering from a cold during the holidays, but Hotline Miami often feels like it comes from a similar place (fever or drugs, take your pick). Although it pays homage to Drive with its setting, violence, and a selection of trippy electronic dance tunes, Hotline adds a gloss of unreality: heavy filtering (including a subtle screen tilt), an increasingly unreliable narrator, and an astonishing sound design. The darker half of the soundtrack leans heavily on synth drones, distorted bass, and indistinct vocal echoes, walking a line precisely between captivating and terrifying.
So it is atmospheric. But in the wake of Newtown it is difficult to talk about Hotline Miami without talking about violence, since it is also a game about brutal, sickening violence. Dressed up in a retro 16-bit facade, the blood and gore is made more abstract, and thus more palatable, but that's a bit of a cheat, isn't it? The NRA recently blamed video games for school shootings, drawing on such contemporary examples as Mortal Kombat and Natural Born Killers, and while that's obviously laughable (and more than a little disgusting) it's hard to take the moral high ground when a prospective game of the year for many people involves beating anonymous mobsters to death with a crowbar.
Part of the problem is that Hotline Miami is and isn't about those things. Someone playing the game isn't sitting at a computer plotting murder--they're primarily thinking about navigating space, line of sight, and the AI's predictable response. Most violent video games are only superficially violent: mechanically they're just button presses and spatial awareness. That's not an excuse, but it does explain why gamers get so huffy about the accusations of immorality. It also begs the question: if these games aren't actually about death and destruction, then why all the trappings?
In the case of Hotline Miami, there's a studied juvenile quality to the whole affair. It's the interactive version of some smart-but-disengaged stoner's doodling on their high school chemistry notebook. It's gross because its influences are gross, and because gross things are fun to draw, and because chemistry is boring, dude. This accounts for some of the feverishness as well, since it taps into the same powerful imaginative impulse that we have as kids and mostly lose when we have to start paying our own rent.
It's not a bad thing for Hotline Miami to draw on those influences, or for it to be ultra-violent. There's a place for ugly, childish things in our cultural stew: I don't think you get Death Proof without Saw or Dead Alive. I like the game. But it bothers me a little that its violence is so unremarkable, and that it wants to use self-awareness as an excuse or an explanation. Using excess to criticize gaming culture was old with Splatterhouse (another up-to-the-minute reference from the NRA, there). So since we don't have a lot of variety in video game narratives, maybe we should stop letting "bloodthirsty" pass for "profound."
Why is it all capitalized? That's what I want to know. XCOM isn't an acronym for something--presumably it stands for Extraterrestrial Combat (or Command?)--so shouldn't it be XCom? I guess that doesn't look as good on the posters. Maybe they should add an exclamation point. (Or a dash, according to the purists. Luckily, having never played the original, I'm not really interested in purity.)
There aren't a lot of games where I finish them and immediately start a new session. Mass Effect 2 was probably the last example--I did two straight playthroughs, and possibly started a third, just because the basic mechanics were so solid and enjoyable. XCOM might be just as catchy, even though I didn't expect it to be. Here are three things that surprised me the first time through:
I didn't think I'd get so attached to my squad. People talk about doing this in the old X-COM, being genuinely upset when a soldier bit the dust, and I just figured those people were crazy. But about half-way through the game, letting Col. Zahara "Werewolf" Mabuza die just stopped being acceptable. The nicknames must have a lot to do with it. I knew every nickname on my squad, especially the ones that got funnier as they got more panic-prone ("Padre," indeed).
XCOM gets a lot of mileage out of only a few maps. I think I saw in an interview that there's only 30 or so maps in XCOM, which is not a lot considering the hundreds of encounters in a typical game. Partly, the maps are just well-designed: just starting out in a different space and direction is enough to make many of the UFO capture maps completely disorienting. But they're also partially-randomized, meaning that you never entirely develop a single cover strategy for each map. Add in the day/night filters, and it feels like a lot more content than it actually is.
Everything is short. Six soldiers means that you're doing with a turn in roughly 60 seconds. A mission in XCOM takes, at most, 30 minutes. Between missions, you pick your research tasks and your engineering projects and then you hit the big "GO FAST" button in Mission Control and see how far you get before the next invasion. Sometimes a movie plays--they're all skippable, as are all the little interstitial animations (launching a fighter, landing the SkyRanger, etc). Everything in the game is made with the understanding that you Should Not Wait, a convenient side effect of which is that it's compulsively playable.
It's not a particularly profound game. It's not even particularly well-made--bugs pop up all over. Even with the tutorial, I restarted the game twice trying to figure out how to keep everything balanced, which is pretty hardcore. But it's so consistently fun that those problems don't halt the experience. I never really got the Halo philosophy of "30 seconds of fun" because I find Halo to be a boring, frat-boy knockoff of better shooters, but XCOM pulls it off.
The fourth Humble Bundle for Android is wrapping up today: if you like games and charity, it's a ridiculously good deal, even if you don't own an Android device--everything works on Windows, Mac, and Linux as well. Although it turns the Nexus 4 into a toasty little space heater, it would be worth it just to get Waking Mars, the loopy botany platformer I've been playing for a couple of days now.
If nothing else, I like that the Humble Bundle proves that it's still feasible to sell software the old-fashioned way: by putting up a website and taking orders yourself. Digital retailers like Steam or the various mobile platform stores are all well and good (the Bundle comes with Steam keys, which I usually use to actually download the games), but a lot of my favorite gaming memories come from this kind of ad-hoc distribution. I don't want to see it die, and I think it would be bad for independent developers if it did.
In the last few months, people like Valve's Gabe Newell and Mojang's Markus Persson have raised concerns about where Windows is going. Since the PC has been the site of a lot of really interesting experimentation and independent development over the last few years, Microsoft's plan to shut down distribution of Metro-style applications on Windows 8, except through a centralized store that they own, is troubling. At the same time, a lot of people have criticized that perspective, saying that these worries are overblown and alarmist.
There may be some truth to that. But I think the fact that the Humble Bundle is, across the three or four mobile platforms in popular use, only available on Android should tell us something. Why is that? Probably because Google's OS is the only one where developers can handle their own distribution and updates, without having to get approval from the platform owner or fork over a 30% surcharge. That fact should make critics of Newell and Persson think twice. Can the Humble Bundle (one of the most successful and interesting experiments since the shareware catalogs I had in the 80s) and similar sales survive once traditional computing moves to a closed distribution model? It looks to me like the answer is no.
When I bought a new computer a little while back, I figured it would be a chance to play some of the Steam/GOG.com games that I bought while they were on sale, knowing that my laptop couldn't handle them. And in one or two cases, it is. But for the most part, I spent last week's small amount of gaming time buried back in a trio of titles from Blendo--a one-man shop that's becoming my favorite indie developer.
Blendo (AKA Brendon Chung) is best known right now for Thirty Flights of Loving, sequel to his absurdist spy short Gravity Bone. It's a funny, cinematic little nugget of first-person narrative. It's also about seven minutes long. I'm not sure it was worth the $5 asking price, but Chung's definitely playing with some ideas here that are worth rewarding.
Besides, he had my good will starting from my first minutes playing Flotilla last year. This was a game that I'd wanted, but somehow had not been able to find: full 3D space tactics within a randomly-generated campaign. The missions themselves are tense, slow-moving affairs set to classical piano pieces, while the overworld screens are Blendo's typically jazzy blend of surrealism (rastafarian pirate cats, defanged space yeti, and wandering Greek goddesses appear along your journey) and procedural storytelling (decisions along the way are assembled into an illustrated ship's log). The combination of the two should be dissonant, but instead the funny bits serve as a nice break between the tense turn-by-turn bits.
And then there's Atom Zombie Smasher, which is the most unbalanced and most compelling of the three. It's basically a tower defense game, which means I should hate it, and yet somehow I really don't. It's ridiculously unfair--sometimes you get an overwhelming mix of units for a stage, and sometimes you just get barricades and mines, meaning that I tend to win or lose the whole game depending on which two units are randomly assigned in the first stages--and yet tremendously addictive. Maybe that's just the surf guitar talking.
Ultimately, I think what charms the most about these is that they almost remind me of board games in their approach to design and replayability. Even though they're radically different genres, Blendo's stuff shares a common sensibility in the way that they construct stories out of small vignettes and procedural generation. Each takes, at most, an evening to play completely through, and yet there's plenty of detail and reward for digging in. They continue to surprise players outside of all proportion to their actual size. There aren't a lot of people making games in this space--it's all either bite-sized casual fare or sprawling epics. Chung's genius is making the former feel, if only for a little while, like the latter.
When I started thinking about blogging again, after an unintentional break, I realized that I'd been doing this, almost continuously, for more than seven years now. That's a long time. Although it was tempting to let it lie fallow, I figured it would be a shame after such a long run--and besides, I do like writing here, especially now that most of the readers (such as they were) are gone.
When I turned Mile Zero into a blog, way back in the day, one of the main things that I wrote about was gaming--specifically, gaming culture. That wasn't all I wrote about, but it was something I was interested in, and there was a whole community of great gaming blogs I could join. Gaming culture had plenty to write about, because it was (and is) a problematic place dominated by emotional children and shameless hacks pretending to be journalists. If I took on those issues, even in a tiny way, I hoped it could help--and it was a good distraction from an office job I wasn't thrilled about and a freelance career that probably wasn't headed anywhere either.
A few years later I got a job at CQ as a "Multimedia Web Producer." Nobody at CQ knew what that was supposed to mean, so gradually I turned myself into the newsroom's go-to person for interactive journalism. I loved my job, and the time and energy I put into it (not to mention the strict editorial policy of non-partisanship) meant I cut back on blogging. I also threw myself into dancing, which I think took me by surprise as much as anyone else, particularly once I joined Urban Artistry. And I went on a bit of an information diet, angry with the low quality/high volume approach of most gaming and tech sites. When I got a chance to write here, usually once a week, the spread of subjects had become more random than ever.
So here we are, seven years (and almost two months dark) later. Sure, this was never really a gaming blog. But I did write about gaming, particularly the sexism, racism, and classism I saw there, and I hoped it could get better. Has it?
Well, kind of better. I mean, it's still awful, isn't it? Sometimes it just seems like the exploitation gets more subtle over time. Tomb Raider pops back up, for example, but now Lara Croft's proportions are less exaggerated--and she's being threatened with sexual assault so players can feel protective toward her. One step forward, two steps off a cliff marked "Seriously, guys, what on earth were you thinking?"
At the other end of the malevolence spectrum, I just finished Driver: San Francisco. Loved it: it's funny, well-balanced, filled with homage to classic car movies and TV (including constant callbacks to its obvious inspiration, Life on Mars). But even though it's a game where the main character is never playable outside a car, even though it's set in a world where the solution to every crime involves vehicular damage, even though the physical make-up of the hero is literally of absolutely no consequence whatsoever... you're still playing as John "Incredibly Generic White Dude With An Incredibly Generic White Dude's Name" Tanner. You could not possibly challenge fewer conventions than Driver:SF, which these days is not so much actively frustrating as it is wearying.
That said, I think there's hope. When I look at something like Anita Sarkeesian's Tropes Vs. Women project on Kickstarter, which went from zero to troll-ridden to ridiculously over-funded in a matter of hours, it kind of blows me away. Seven years ago, would Sarkeesian's videos have gotten that much support? Would it have gotten sympathetic attention from the corporate blogs? Would it have been picked up across a wide range of non-gaming media? I feel like no, it wouldn't have. And while tools like Kickstarter have made it a lot easier for small projects like this to get the funding they need, I suspect that changes in the culture have also made a big difference.
More importantly, it's not just one culture anymore, if it ever was. Communities don't just grow by getting bigger, they also grow by having new circles intersect at their Venn diagram. You see this everywhere: look at the way that music fans start out as a small, particular group, and then as the artist gets bigger, different people begin to attach--sometimes for very different reasons, which may eventually drive the original fans away. The reasons why I love the Black Keys (their early, filthy-sounding recordings from Akron) are not the reasons that new fans probably love them, but we all end up at the same concerts together.
When I was studying intercultural communication in college, the term for these meshed sub-populations was "co-culture." I didn't care for the term then, but now it seems appropriate. Gaming is bigger than it was seven years ago, and it's no longer accurate--or seen as desirable--to say that the "real" gamers are the angry 14-year-olds with a chip on their shoulder about girls and minorities. This space can (and does) support more than that: from Troy Goodfellow's series on science and national characters in gaming, to The Border House providing a critical examination of character and plot, to rhetorically-stunning games like Auntie Pixelante's dys4ia. These are not all the same voices I was reading and responding to seven years ago, but they are stronger and louder and more influential. That's fantastic.
I'll probably never refocus here to the degree I did when I was writing a post or more a day, because being a single-issue blogger (or a single-issue anything) has never been interesting to me. But I'm thrilled other people are doing good work with it. As a gamer, the same way that other people might be movie buffs or music snobs, I want to see it grow and change so that I'll be exposed to new and interesting perspectives. I don't want to see it stagnate. While progress is slow, I think it's being made. Let's hope in another seven years, I can look back and say the same.
The sound design, as usual for Nintendo, is instantly recognizable. It makes this kind of phased, dopplered hissing sound, a parody of "something going very fast." You can hear it coming up from behind a few seconds before it hits, or when it passes someone else in splitscreen mode. The latter is the really frustrating scenario: you know you're going to be knocked out of the race--the only question is, when?
The blue shell is the reason I can't play Mario Kart anymore. Belle and I started playing on the Wii again a couple of weeks ago, and for the most part I enjoy it. The boosts are toned down so that snaking can't be abused like the DS version, the tracks are decent with few outright stinkers, and I like the addition of motorcycles (even if they're unplayable with the Classic Controller). In multiplayer, I could care less: if I get knocked out and lose to Belle, it's all in good fun. But then I tried unlocking new characters in the grand prix mode, and the blue shell completely ruins that.
The thing about Mario Kart is that it's balanced via progressive taxation. Everybody in the race gets items, but the better you're doing (right at that moment) the worse those items generally are. If you're in the lead, you only get items that let you maintain that lead (but not increase it), like banana peels or fake item boxes. If you're in the back of the pack, you get items that let you jump up in line, like the star or bullet. And the game heavily incentivizes using those items quickly instead of hoarding them--a number of the other power-ups will cause you to lose anything you're holding when they hit you. It's actually an extremely clever set of interlocking mechanics, all designed to keep races unpredictable.
But the blue shell breaks that pattern. It doesn't give you a boost (even implicitly, by punishing everyone else, the way that the lightning does). In fact, if you're in the back of the pack, it probably doesn't help you at all--the second and third place racers are just going to shuffle up in position. Using a blue shell in Mario Kart has one goal, and one goal only: to ruin the third lap for the best racer on the track. It's subsidized griefing.
Worst. Power-up. Ever.