Monday, 27 July 2015

'World'

In my work on Tales of Vesperia particularly and JRPGs in general, I’ve been poking at a lot of virtual worlds, looking for the places where they start to come apart and the meaning that can be gleaned therefrom. In trying to develop a theoretical framework for this, I spent some time going through the etymology of the word ‘world’[1], and hopefully what I found is at least worth this post.

‘World’ comes from a Germanic root, a combination of ‘were’, meaning ‘man’ (as in ‘werewolf’) and ‘old’ for (if this isn’t obvious) things relating to age. The OED gives an ‘originally literal’ meaning of ‘age of man’[2]. What interests me about this is the temporal component.

I think it would be fair to say that we generally use ‘world’ as a geographic or ontological descriptor; ‘the world’ is either a place, or a(n in-some-way-maximal) set of objects. That’s not universally true, as we might speak of ‘the Jurassic world’ or ‘the modern world’, or say of some era of history that ‘it was a different world back then’, but I think it fits how the word is used today (I’d be very interested to hear from anyone who disagrees). We tend to use ‘age’ or ‘era’ to speak of periods of time.

And I think this is worth remembering when discussing ‘world’ in videogames, because it’s the temporal dimension of game worlds that tends to be the more complicated. Games compress distance, and even chop it up a bit, but as I’ve argued before, game spaces are generally straightforwardly spatial.

Time in game worlds, though, is rather more complicated. Partly out of technical limitations and partly out of courtesy to players, games have to convey the passage of time in mostly-abstract ways. Even the most literal driving/racing game, with a millisecond-precise lap timer in the top corner of the screen, will run its career mode, car tuning and car select menus in abstract time (thank heavens).

One of the coolest and most effective single experiences I’ve had in a game was Queers in Love at the End of the World by Anna Anthropy (go play it quickly and come back). This seems, on the face of it, to be a game with very literal time – a timer at the top of the screen counting down from 10 in seconds – but it relies on an abstraction to make that time meaningful. Specifically, the duration of your actions is abstracted to the time it takes to read, understand and navigate the hyperlinked options.

Without wanting to dig too deeply, this does complicate things. Time in Queers in Love passes differently depending on your reading speed. I tend to have time for about two choices; I feel like I can usually do more than ten seconds’ worth of actions in the game’s ten literal seconds. A slower reader, someone reading in their second language or with a condition like dyslexia, may find time flowing rather faster for their in-game avatar than I do.

The kind of games I spend most of my time playing – JRPGs and other epic narrative games – have to compress time much more severely. Sequences of events that by rights should take years must be fitted into forty hours or less. There are lots of ways to do this, all of which can be clunky in some contexts and entirely graceful in others.

It’s often in handling time that JRPGs get most abstract, or furthest from literalism. Plot developments that are tied to player progress can seem preposterous coincidences; taking time to complete sidequests after reaching the final save point before the final boss can drain all urgency from the impending apocalypse.

I’m not going to go into these topics in more detail this time, because each is worth at least a post on its own. But I do think it’s important to look at how games represent time, how we should interpret those representations, and how virtual experiences may conflict with our relationships to non-virtual time – and the non-virtual world.







[1] This is a Thing Philosophers Do, and I don’t necessarily mean to advocate for definitions based on etymology over use, but it’s often helpful when trying to develop a lexicon to get a sense of what other linguistic roots may be relevant.

[2] It should be noted – though it’s by no means my place to do more than note – that ‘were’ means ‘man’ in the sense of ‘male person’, not as a generic term for human beings. I leave it to more astute feminist scholars to examine the fact that ‘world’ is by root a gendered term.

Thursday, 9 July 2015

The Only 'Real' That Matters

You know that feeling of disbelief when you beat a difficult final boss and instead of another phase the ending cutscene starts to play? The sunrise-slow shift from breathless relief to triumph?

Has a plot twist ever punched you right in the gut (looking at you, Aeris)? Has an environment ever sent chills down your spine[1]? Ever find yourself wanting to chew your controller (don’t inspect my old Gamecube pad for toothmarks, please), or pitch your TV out the window?

These are the kind of effects that often get forgotten in the popular debate about whether games can have ‘real effects’. The focus tends to be on whether games are turning ‘our children’ into (a) uncontrollably violent beasts or (b) posthuman supergeniuses. But of course games can have real effects at the personal level, and the other concerns are best left to psychologists with some grasp of proper investigative methodology.

And it’s not just that certain pieces of digital software can cause effects on real people. If you cried when Aeris died, or punched the air when you beat your first Bowser, it wasn’t the flipping of a bit somewhere inside the console, or a shifting pattern of electromagnetic radiation emitted by the screen that had that effect on you.

Okay, in a way it was, but describing the pattern of light or the behaviour of the silicon isn’t the best explanation of your response. You didn’t punch the air because of [obscure technical description of computer hardware]. You punched the air because YOU BEAT BOWSER YEAAHHHH.

And really, that should be all it takes to justify the serious study of games and gaming. We shouldn’t need esoteric philosophical arguments like this and this to defend what we do. In an ideal world, the capacity to cause real experiences would be the only thing that counted when deciding what’s worth taking an interest in[2].

It can be tempting to dismiss this position on the grounds that game events or objects are just fictions – that we can account for them in the same way that we account for Sherlock Holmes, or Batman, or Narnia. And you know, fair enough provided you’re going to take the study of Sherlock Holmes and Batman and Narnia seriously (pulp crime fiction, comics and children’s fantasy have all had their own fights for recognition in academia). But there is a bit of a difference.

A fiction is a kind of tacit agreement between audience and author. Very roughly, when you open a novel, you’re accepting that the author is going to tell you a bunch of lies (or at least, things that aren’t true), but that something in those lies will be worth your attention. You’re entertaining the lies in the hope or expectation that they will have some positive effect on you – make you feel good, teach you something new, guide you to self-reflection.

Some games are fictions, of course. But some don’t really involve straightforward fictive assertions at all. Look at a game like Geometry Dash, a game that consists almost entirely of level geometry. The geometry of a Dash level isn’t a lie about how things are in some other realm, it’s just there. If I tell you there’s a sequence of spikes at a certain point in the level, that’s true.

In this way, game objects are more like the notes of a piece of music. They may contribute to the telling of a story, or the communication of fictive claims, but they are real parts of the work, however transient or intangible. “There’s a mushroom in the second ‘?’ block of Super Mario Bros level 1-1.” is the same kind of statement as “The first notes of Scott Joplin’s The Entertainer are a D octave.”

This is why I think it’s useful to consider game events real; it’s not just that they’re causally effective (though in some ways that’s enough on its own), but that they are also intersubjectively consistent in a way that fictive events are not. If you claim that ‘Sherlock Holmes lived at 221B Baker St.’, I am not obliged to agree, since the statement is only accurate to Conan Doyle’s fiction, and not the Baker Street that you can walk along in London. We must agree a frame of reference before that statement is true. But ‘The Companion Cube appears in Test Chamber 17’ is true simpliciter.

There’s more to be said on this, particularly concerning the types of fictional statement (‘221B Baker Street’ is a fictional address in a real place, whereas somewhere like ‘Bag End, Hobbiton’ is a fictional address in a fictional place), but I do need to leave something for the academic paper I’m writing on this subject, so I’ll leave things here for now.







[1] I’m not able to offer any intelligible examples of this one because I scare easily and I’m not admitting just how terrified I was of the Great Deku Tree for a while in early 1999…

[2] For more on this terrible philosophy joke, I wrote a brief and slightly clunky introduction to philosophical idealism here.

Monday, 6 July 2015

Abstraction, Simulation and Narrative Time

This post grew out of a conversation that’s happened between several people over quite an extended period of time, so apologies if I have to send you on a bit of a reading list to catch you up.

It more or less started here with Devon Carter’s Critical Switch guest episode about the role of abstraction in JRPG mechanics (which is basically essential reading if you want to follow anything I write on this blog, so get to it if you haven’t already).

Then Austin C. Howe had some thoughts about JRPGs on generation 7 hardware, which I Storified, where he discussed how more powerful technology had revealed some of the ways in which the classic JRPG form struggles with ‘realism’.

That prompted LeeRoy Lewin to write this excellent piece about how the basic abstractions of JRPG combat – HP, MP and XP – are bad representations of anything ‘real’.

Finally, and possibly independently of all this, Vincent Kinian reviewed Yuuyami Doori Tankentai with a focus on how it actually does address the real successfully.

Got all that? The key point I want to focus on is LeeRoy’s, that the mechanical abstractions in JRPGs don’t directly represent the things we ordinarily take them to. HP are a poor representation of health, or even endurance, because health is not linear or one-dimensional. XP in particular, to quote LeeRoy, models “the purest meritocracy, the most awful gamification, the idea that labor can transfer 1:1 value.”

If MP and equivalents are innocent in this, it’s only because they represent something that makes no claim to reality – magical power. Because it’s entirely up to an author to invent a magic system, we can’t gainsay the device of MP, but we can point out that it’s a formulaic and often uninteresting way of limiting power. To be fair, sometimes it doesn’t need to be interesting and is just an unobtrusive balancing tool, but I feel like there’s often a lot that could be done here that isn’t.

The more complex, player-engaging systems built on top of these stats – materia, GF junctions, sphere grids and so on – may be a little more representationally rich, depending on how they are contextualised[1], but the statistical foundation is poor in this regard. So why are these numbers so ubiquitous?

Convention, and the legacy of tabletop roleplaying games, makes up one major part of it, of course. Things are Done This Way because That’s How They’ve Always Been Done (and in the case of at least HP, the problem isn’t unique to JRPGs or even RPGs in general). But these stats do serve a function, or at least are a crucial pillar of a system that serves a function, and that function, I would argue, can be meaningful and valuable.

What JRPG systems – the stuff we think of as ‘systems’, the numbers bits – do is control the delivery of a story. They may do other things as well, but one persistent function is to determine when the story moves forward. Part of this is just to space things out, so you’re not just playing a novel (and to meet the ever-louder consumer demand for ‘value for money’, as measured in hours of ‘content’), but there’s also a crucial contribution that this makes to JRPG stories.

Pacing is everything. JRPG stories tend towards the epic in style as well as length. They are stories of big deeds, world-shaking changes. Worlds do not change overnight. Many forms of storytelling work just fine over short periods – one can hardly object to the near-real-time duration of Twelve Angry Men, or the one-night framing of Die Hard – but the grander the scale of a story, the slower it needs to feel like it moves.

The games industry is already bankrupting itself and driving employees to exhaustion to deliver games of sufficient length and graphical quality to keep ‘the market’ placated. As graphical standards continue to rise, representing the passage of time non-literally is going to get more and more important for delivering long-form stories.

This is where RPG mechanics, and particularly their JRPG versions, can shine. HP and MP represent the costs of time; the wear and tear of travel, the hazards and labour it involves. XP represents the benefits of that time – as LeeRoy pointed out, often badly, but I think this approach to them at least suggests some ways to complicate them into something more meaningful.

What is represented by these stats – perhaps it would be better to say ‘encoded’, since ‘representation’ implies something more explicit – is not really anything about the software objects to which the variables belong. What is represented is the world, the time and space through which these objects move.

If an encounter, or sequence of encounters, leaves your party on their last legs, you’re given the sense of characters limping into town, propping each other up, maybe dragging a stretcher, bags emptied of supplies. Backtrack over the same ground later in the story, and the easy passage, the image it conjures of marching proudly through the same gates with head held high, represents the sheer length of time it takes to master what was once marginal.

Here is where that stuff from Austin and Vincent becomes important. Taking stats to be directly representative creates misleading indulgences about vast gains in personal power and importance over implausibly narrow stretches of time. Austin’s point that realism is about more than just visual literalism, and Vincent’s that the sense of the real comes from the mundane, the stuff that happens between the fantasies, suggest that the way to get real value from explicit stats is to look at what they imply.

If a magic spell allows you to do ten times as much damage to a target as the strongest physical attack, but costs ten times as much to use, what does that say about the scarcity of that spell, the rarity of this casting? If a character is dying of poison and you’re out of antidotes, can you make it to the next inn or item shop in time? Frequent easy encounters that wear you down slowly suggest a long journey; fewer more potent encounters suggest danger and pain but less time; a surfeit of brutal fights implies that the world must turn a little longer before you can make it through.

The actual games could do a lot more to draw attention to this side of reading them, but that doesn’t mean that existing games shouldn’t or can’t be read in this way. It’s an approach that I’ve found useful particularly when looking at games that focus their narratives on journeys – I'm a broken record, I know, but Final Fantasy XII and Tales of Vesperia are both excellent examples of this[2].





[1] Some are much worse, particularly ‘relationship’ systems that reduce social ties between characters to single score variables.

[2] There are a couple of sequences in Vesperia where mechanical representations of the passage of time are directly contrasted with what cutscenes have told you about the time-frame of events, which show both how effectively good stat usage can suggest the passage of time and how quickly bad stat usage can undercut it.

Wednesday, 24 June 2015

Protecting the Trophy Cabinet

Tales of Graces is the story of Asbel Lhant, heir to the small border domain of Lhant. Asbel begins the game as a spirited, disobedient child at odds with his militaristic father's strictness. Eventually, Asbel runs away from home to pursue his dream of becoming a knight in the King's army; the bulk of the plot kicks off as he nears the end of his training seven years later.

In short, Asbel is a textbook fantasy hero. So textbook, in fact, that he and his kind were written out of the fantasy textbook some years ago as a tired and never-terribly-interesting cliché. Graces does a pretty good job of bringing the cliché to life, though, through a combination of good visual design, good voice-acting and a solid script.

And that's a problem, because this is a cliché that embeds a lot of toxic masculinity, and Graces either doesn't realise this or outright embraces it. Asbel is obsessed with the idea of protecting people; Graces' statement of theme translates as 'Discovering the Strength to Protect'. The idea of protection at hand is fundamentally possessive.

The best illustration of this is in Asbel's relationship to his childhood friend and eventual wife, Cheria. During the childhood section of the game, Cheria is unspecifically frail, easily exhausted and doted on by the people of Lhant. After the seven-year intermission, mysteriously[1] cured, Cheria becomes the party's strongest healer and a powerful caster.

During childhood, Asbel tolerates Cheria more than actually caring about her – in his initial escapade, he drags his brother along to climb a nearby hill, but leaves Cheria behind saying he doesn't want her slowing them down. When they return to town Cheria is upset; Asbel stalls her by handing over a flower he picked idly on the hilltop and pretending he meant it all along as a gift.

In his seven years of training, Asbel never once tries to contact Cheria. When the adult section of the story begins, she comes to find him at the knight academy to tell him his father has died and he's now the Lord of Lhant. She's reticent, clearly sympathetic to Asbel's loss but also unwilling to offer comfort. Asbel is too self-absorbed to understand, but the player will; Cheria has been deeply hurt by Asbel's silence.

Matters reach a head between them a chapter or two later, when Cheria is kidnapped and Asbel rescues her. When she isn't as grateful as he expects – as grateful as she would have been as a child, or as a fairytale damsel – he protests 'You've been treating me like crap ever since I got back here!' This spectacular feat of obliviousness is compounded by every other character present ganging up on Cheria to push her to be nicer to Asbel. Asbel offers only a trite apology, plus excuses that make it unclear whether he really understands his fault.

In other places, Asbel's determination to protect is played for laughs. At one point he gets into an argument with companion Sophie about which one of them will protect the other; they end up agreeing to a race to decide, and Sophie easily wins.

There are comedic examples of how much Asbel wants to fit the rest of the party to his script, too. The game has a rich variety of victory celebrations, several of which it implies have been coordinated and choreographed by Asbel. In the one that features Asbel and the three female party members, they mess up his script and he ends the animation effectively sulking in a corner:

Asbel, when women don't do what he wants.
If this were just another game mishandling the common toxicities of masculinity, it wouldn't be worth an essay in its own right, but the sad thing about Graces is that, in some ways, it's much more sophisticated than that. Its presentation of Asbel as a centralised male raised on myths and norms of his own importance rang very true to me as a centralised male raised on myths etc. etc. etc... He's neither a trite nor a shallow character.

Asbel's ideal of military prowess doesn't come from nowhere. It's bound up in the feudal structure of his society; his father is both master of the household and military commander, and clearly doesn't separate the two roles in his own head. Lord Aston is a harsh, cold presence in the childhood section of the story, and the silence of his absence seven years on is more a continuation than a relief.

It's a cliché to blame toxic masculinity on distant fathers, of course, but the distant father archetype is part and parcel of toxic masculinity, and Graces does a pretty good job of portraying it. In fact, overall, Graces understands toxic masculinity much better than the majority of male-led games. If it deploys clichés, it does so only because toxic masculinity is so inescapable that all its features are sadly familiar.

And herein lies the frustration; ultimately, Asbel gets his fantasy. In the final moments of the story, he gets to step forward and use his martial and magical strength to protect the world. Several much more interesting possibilities that the game flirts with, including some which would require him to accept the protection of others, are squandered.

Compare this, for example, to the engagement with masculine toxicity that Austin C. Howe finds in Final Fantasy VIII. Graces does try to build a contrast between Asbel and his even-more-toxic brother Hubert, but given its endorsement of Asbel, this doesn't actually achieve much. 'This is acceptable because it isn't as bad as that' is a child's excuse for a game that purports to be about growing up.

It is not enough to understand, or to present clear understanding of, dominant cultural constructs. That which does not explicitly challenge will be taken as tacit endorsement. Graces wastes its opportunity, and the good work of its writers, by allowing Asbel his triumph.






[1] Even the game doesn't think it's kidding anyone as to the nature of the mystery, but it's not relevant here.

Tuesday, 2 June 2015

Reporting a Wonder

One of the strangest scenes in Tales of Vesperia happens right near the start of the game, before you've even made it to the first combat tutorial. As protagonist Yuri is making his way from his humble abode up towards Zaphias' Royal Quarter, a wall calls out for his attention.

Yuri walks up to the wall, which explains that it is the 'Wonder Reporter', an individual whose raison d'etre is tracking the activities of heroes and documenting them. They draw Yuri's attention to the 'wonder log' he carries (the game's in-built synopsis), and claim to be the one responsible for keeping it up to date. Then, with an admonition to pay no attention to the fact that they're in the wall, the Reporter ends the cutscene.

They appear (or at least, speak) twice more in the course of the game, once in a pillar tucked out of the way in one of the game's most semiotically rich locations and then finally in a tree near a desert oasis. Neither of these later encounters triggers automatically – both must be found, and without so much as a hint to go on. Neither offers any metaphysical explanation for the Wonder Reporter, though the dialogue increasingly emphasises their essential voyeurism.

These cutscenes were what first induced me to look beyond Vesperia's narrative, and eventually led to my conceiving this project. I initially took the Wonder Reporter to be a symptom of budget limitations – devs with no resources to add another character model coming up with a desperate quick-fix to make the wonder log diegetic. This gives the game too little credit, and is probably a naive way of thinking about the relationship between budget and resources for game development.

The Wonder Reporter is absurd, but in a way that very carefully directs player attention. Vesperia has five separate 'log books' – the wonder log, the battle book (which records information from tutorials), the world map, the bestiary and the 'collector's book' (a list of all the items you've encountered in the game). Of these, only the battle book lacks narrative contextualisation, and even then Yuri's possession of it at the start of the game, and the fact that all the tutorials are his experiences, suggests it may be a holdover from his military training.

The bestiary is kept by Karol, a trainee monster hunter. The sidequest that revolves around completing it involves Karol's desire to prove himself to love interest Nan, herself an accomplished hunter. As a romance, it's sweet but quite straightforward. As a way of contextualising the monster book, though, it's both effective and more or less plausible.

By contrast, the item book sidequest is, on the face of it, a nonsensical mess. The book itself initially belongs to genius mage Rita, and she introduces it as a self-updating tome that automatically records whatever you pick up. The rewards from the quest hinge on a couple of chance encounters with another obsessive mage seeking the same information. The whole idea of a book that records every item in the world is absurd, particularly since it only documents those items the game allows you to pick up and none of the otherwise plenty detailed set dressing.

Even worse, for the sake of two items, the item book quest is the only thing in the game that can't be completed on a single play-through. The items in question aren't plot-sensitive, either - just a couple of weapon synthesis forms where two different weapons can be made from the same root, only one of which is available per play-through. To complete the item book you have to play the entire game twice and carry over your collection data.

There isn't really space to get into the diegetics of the world map, since there are a few different things that link to it. In particular, Karol's cartography is used as a metaphor for masculinity in a way that I could probably write a whole book on by itself. Still, topic for another time.

In essence, the game takes the same idea – log books to augment player memory – and plays it out in five different ways. At least one of these, the bestiary, is pretty strong. One, the item book, is obnoxiously hostile to player engagement. The battle book asks nothing; the map creates a compelling set of metaphors and challenges. And the wonder log draws attention to the sheer 'gameyness' (if you know a better word for this, please let me know) of the whole idea – the fact that this is all essentially what Devon Carter calls a concession to convenience.

Western criticism of JRPGs, at least at the time of Vesperia's development and release, was primarily ludic in focus. Apart from the stereotype of the effete, self-indulgently gloomy protagonist (always something of a mirage), mechanically linear narratives and formulaic, one-dimensional combat were the main complaints – but those same complaints were often paired with exceptions, usually either Final Fantasy VI or VII, depending on the age of the speaker.

What Vesperia does, in this case and in several others, is show that what matters is not the mechanic itself but the way meaning is built around it. That it is willing to embrace the absurdity of the Wonder Reporter (and, again, several similar signposts) to draw attention to this issue suggests a reading of the game as not just existing in tension with but actually outright responding to such unjust criticism.

This is the foundation of the close reading I'm working on. Vesperia expresses a frustration with the (Western) consumer response to JRPGs that I share, and makes an argument that I believe can be resoundingly justified. Obviously there's a lot more to it than I've covered here, but I'm working on it.

Thursday, 28 May 2015

Real Space

A few weeks ago I discussed one of the problems with trying to use 'real' to differentiate between video game worlds and our world. There, my discussion was based around issues of constitution and factuality. Now, I want to pick up a different issue in the same vein, one that I touched on when discussing Unwind; the fact that video games don't take place in our space.

In fact, it's tempting to say that video game events don't take place in (a) space(s) at all. They represent spaces (better: they present visual patterns which represent spaces), sure, but that's not the same as involving a space. Or is it? Depends what 'a space' is.

At the most basic level, Barry Dainton (full disclosure: my boss) identifies two functions we attribute to space rather than its occupants. Constraint is the function of limiting the ways we can move; our space is three dimensional, so any motion we can make is a combination of movements in those three dimensions[1]. Connection is the function of allowing space-occupants to interact; wherever you are, you and I are spatially connected because there are logically possible spatial movements that would bring us into contact.

It should be obvious that video game spaces meet these criteria. Connectedness is almost trivial when it comes to game objects, since a game cannot present an object unless it is possible within the game to view that object (and thus connect it at least to the camera/viewpoint). Dimensional constraint is such a significant factor in some games that we use different dimensionalities to partly define some genres – 2D and 3D platformers, for example.

Of course, this is a broad definition. It allows as a space anything that has both dimensions and occupants; the standard windows and HTML colour charts become spaces, whose dimensions may be rendered either as red, blue and green or hue, saturation and value. This shouldn't seem too counterintuitive, since we often and productively represent the colour chart spatially.

The colour chart is a kind of space we might naturally think of as abstract, but it's quite hard to pin down what this means. Its occupants are abstract in that they are colours abstracted from any particular object possessing them, but this is a fact about the occupants of the space, not the space itself.

Video game spaces are in a similar situation; we know they don't take place in our space, since we are not conventionally connected to their occupants (nor, indeed, conventionally constrained by their dimensions). But if there is a difference in kind between our space and game spaces – if video game spaces are not real in the way that our space is – it is difficult to articulate.

The simplest way is to adopt the substantival construal of space put forward by Newton to fit his classical mechanics. According to this view, space is a thing that exists independently of its occupants; list the fundamental ingredients of the universe and in addition to a set of physical atoms, there will also be a set of spatial points or regions. Empty a room of all its physical contents, and a substance remains: space, separating the walls and permeating the intermediary void.

Despite the utility of the physics that go alongside it, Newton's theory of space is notoriously difficult to prove. Newton's proofs rely on demonstrating absolute motion and rest – motion which is relative not to other objects but to space itself. The bucket argument is the best-known of these. Whether the bucket argument proves Newton right about substantival space, though, it cannot differentiate systemically between our space and game spaces; any game may be programmed to mimic the effect on which the argument trades.

Newton, then, cannot help us differentiate between 'real' and 'virtual' spaces. The chief opponent of substantivalism, the relationism of Leibniz and Descartes, does even less to distinguish the two. According to relationism, space is merely a matter of the spatial relations among objects; no objects, no space. So any set of real objects that are connected and subject to shared dimensional constraints will constitute a space.

This passes the question of whether game spaces are real or not back to the question of whether game objects are real, and as I argued last time out, there's little ground for saying game objects are less real than the conventional objects we deal with on a day-to-day basis.

Perhaps it's better to view this as a reductio ad absurdum on the common use of the term 'real'. We can intuitively understand that there's a difference between our relation to game objects and our relation to regular tables and chairs without needing to dismiss game objects as lesser.

Here, one final philosophical notion may be useful. In his work on possibility, David Lewis developed the theory of modal realism, which holds that every possibility is a universe in its own right, on a metaphysical par with our own. His reasons for this extremely profligate version of parallel world theory aren't important; what's useful is how he understands one particular possibility's being 'actual'.

For Lewis, 'actual' just means 'in our universe'. It's an indexical term, like 'here' or 'now' – its meaning depends on who says it. When I say 'here' it (almost always, because I don't get out much) means my house in Liverpool. I can say 'It's warm here', and absolutely not contradict you when you say 'It's cold here', so long as you and I are in different places.

We can use 'real' to distinguish between our space and video game spaces in much the same way; a 'real' space is a space we're in. Our space is real to us; the space of Hyrule is real to Link.

I've got one more sense of 'real' that I want to discuss, the one that I think is both most important and most clearly shared by game events and objects, but that will have to wait for another time.







[1]: This puts aside, for simplicity's sake, string and M theories which suggest our space may have more than three dimensions, as well as holographic theories which suggest it has fewer.

Thursday, 21 May 2015

Knight of Ratatosk

(Content note: Dawn of the New World features a character with two personalities. While the game eventually decides this is not a psychological condition, it remains a regressive engagement with dissociative identity disorder. I apologise if this essay causes harm or discomfort by touching on this theme).

About halfway through Tales of Symphonia: Dawn of the New World, I characterised its combat as brilliant, but almost completely unplayable. I think I had more game-overs in this game than in any other JRPG I've ever played, so quickly is it possible to go from full health and a full party to four corpses. What makes it brilliant is that every feature of the combat – including the difficulty itself – adds meaning to the experience of play.

Dawn's plot centres on Emil Castagnier, who makes a pact with a spirit of darkness, Ratatosk, to gain the power to protect Marta Lualdi, who (at that point) is a complete stranger to him. The game's engagement with masculinity-as-protection is better than average, I think, but tangential to my topic for today. What I'm interested in now is that subsequent to this Emil, heretofore a timid creature, develops a second nature, one of violence, aggression and cruelty.

The exact metaphysics are unimportant (I'm honestly not sure I ever figured out what was going on). What matters is that the character becomes as divided as his game; Dawn maintains the conventional JRPG separation between exploration and combat gameplay, and Emil's 'Ratatosk mode' is generally reserved for combat. Combat becomes a reflection of Ratatosk's values.

The most obvious element of this is in Emil's fragility. Where other Tales games can be tanked through as slugging matches, in Dawn taking damage is extremely risky. There's little feedback when you take a hit, as if Ratatosk doesn't feel pain. Health bars evaporate in moments.

It's also easy to get combo'd and stun-locked. Stuns last a long time, as do staggers. Get between even a couple of enemies and they can lock you down completely. The game knows this, too. Enemy packs are large, and most bosses come with multiple minions. Attacks generally have huge hurtboxes, so that even enemies attacking nearby friendlies may contribute to a lockdown.

The upshot of which is that unless you keep tight control of the battlefield, your position is always precarious. In many JRPGs, control is just a matter of keeping a safe margin of health, magic and item stocks. In Dawn, it means aggressively breaking up enemy attacks, shutting them down before they can do the same to you.

Mechanics can make meaning in the obvious way, as with the lack of feedback for incoming damage mentioned above, but they can also make meaning by incentivising certain player behaviours. Dawn heavily pushes one particular way to sustain the control needed to survive.

On the ground, Emil's attacks are sluggish, and his combos both short and easy to interrupt. Stagger an enemy and launch it, though, and Emil becomes the vengeful demon the 'Ratatosk mode' personality suggests. His combos are fast, fluid and long, startlingly easy to execute. And, of course, by being airborne with only a staggered enemy (often more than one, thanks to the large hurtboxes) for company, he's out of harm's reach.

There are other little rewards for focussing on aerial play, too. While Emil is slow to develop supplementary skills that improve his ground combat, skills and special moves for aerial use are commonplace, a sharp inversion of the Tales norm. And since TP ('tech points', the MP of Tales games) regeneration is tied to combos, the longer aerial combos mean basically never running short.

The only way to prevail, then, is aerial combat, and aggression. Single out the most dangerous enemy, lift them above the fray where they can do no harm, and repeat until they vanish in a puff of spirit energy. This is a fundamentally proactive violence.

It is also arrogant, a literal rising above Emil's fragility, rising above enemies and allies alike. To play this way is to ignore what happens on the ground, and focus all your attention on the kill. So it is with Ratatosk, who holds Emil in utter contempt. He resents sharing such a weak body, being trapped in it and only kept around for his utility.

Violence, though, is essential in this world. Monsters are everywhere, often in narrow passages that make them unavoidable. The respawn rate is high; some dead-end passages are long enough that if you kill the monster guarding them, collect whatever treasure they hold, and return, you must fight the same encounter again on the way out. Emil needs Ratatosk.

But Ratatosk does little more than kill. He does not protect – while he flies by sheer power of bloodlust, Marta must take care of herself on the ground (to her credit, she's generally more than capable of this). As is revealed later in the plot, he feels no compassion for the humans he aids.

And Ratatosk is isolated, too, literally and symbolically. The story is Emil's and Marta's, and indeed partly concerns their letting go of what meagre vindictiveness they each possess. They grow together as they work to bring peace to a divided and sometimes brutal world. Ratatosk must be isolated, the emotions and policies he stands for restrained.

Ratatosk stands for destruction, Emil and especially Marta for preservation. This creates a problem for resolving the game's story through traditional boss fights, given that combat remains Ratatosk's domain to the last. To cover the finale, I'm actually going to give an extra level of spoiler warning. Nothing I've described so far is game-ruining, but if anything I've said so far makes you interested in playing the game, stop here and go play it (it's worth it).