I’m trying not to say ‘Zelda isn’t an RPG’. ‘Zelda’ and ‘RPG’ both mean too many different things to too many different people for that to be a useful statement. But I think I can say something useful about what I look for in an RPG – and particularly a JRPG – by contrasting it with what I look for and love in Zelda games. For clarity, I’m a 3D Zelda person – I’ve generally found the 2D games frustrating to play, though that may be because I’ve mainly played them on handheld and I kinda hate handheld gaming.
To start, here’s what I understand by ‘RPG’: a system of abstraction(s) that primarily serves to mediate the telling of a story. This is a pretty broad definition (the ‘primarily’ is important), but I think it’s useful because it captures the connection between pre-digital pen-and-paper RPGs and their digital analogues. The downside is that it leaves out the act of roleplaying that makes up such an important part of the pen-and-paper experience.
Anyway, what I mean by it is this. The abstractions in RPGs serve a primarily extrinsic focus[1]. Phenomena like HP and XP encode the labour and temporal cost of travel. World maps and sidequests indicate scale. The more abstract components of the game are there to set a tone and player mindset for the story developments, which are generally treated as less abstract[2].
The 3D Zelda games, though, have a different focus. For one thing, the biggest abstractions in Zelda games are the puzzles; not the player’s actions but the environments that induce them. The player’s attention is drawn more to the phenomenal/sensory qualities of their actions – the flight of the boomerang, the heft of the megaton hammer, the whoosh of flying through the air with the hookshot.
As a complement to this, Zelda games generally have less involved storylines. It’s telling that the games that do have stronger emphasis on storytelling – Majora’s Mask and especially Twilight Princess – have more in the way of player action that mediates story. Moments like the sequence where you carry the injured Midna to Zelda, or the horse-and-cart bit where you transport Ilia to Kakariko Village, are more about the urgency of the moment, the dramatic interruption to the otherwise pervasive melancholy of Twilight Princess’ Hyrule, than the phenomenal qualities of the specific actions the player takes[3].
There are exceptions on the other side of the equation as well, of course. Action RPGs and even some more recent turn-based ones do take an interest in the intrinsic qualities of their abstractions. This can take the form of Tales-style combat, levelling systems like Final Fantasy X’s sphere grid and the Lillium Orbs from Tales of Xillia, or even quicktime events, as in Final Fantasy XIII-2.
Almost every game that has a story dabbles in abstractions that favour the story; similarly, almost every game period dabbles in abstractions that feed the senses. The question is one of balance. When I go to my collection of Zelda games, it’s because I’m looking to have my attention drawn to a particular sensory/phenomenal mode of engagement. When I go looking specifically for a (J)RPG, I want to focus on the narrative and register other interactions as in service to that.
[1] I think this is true whatever RPG you play, but it’s probably less true for more modern western RPGs than JRPGs.
[2] There’s a whole complicated question of the role of abstraction in fantasy narratives – magic and magical creatures as metaphor, fantasy hierarchies as engagements with real politics and so on – but it’s too big a topic to get into here, hence the ‘generally treated as’.
[3] The cart-and-horse sequence is also a call-back to the similar escort mission in MM, an explicit link between the two games.
Showing posts with label Majora's Mask. Show all posts
Showing posts with label Majora's Mask. Show all posts
Monday, 24 August 2015
Saturday, 15 August 2015
The Price of Time
A couple of weeks ago, I said I’d be talking about time in JRPGs, and one of the particular issues I picked up on was this: “Plot developments that are tied to player progress can seem preposterous coincidences.”
When plot events in a game are tied to triggers based on player progress, whether that’s beating a particular encounter, arriving in a particular location or just talking to the right NPC, that connection can be pretty obvious. Sometimes this is fine, but often it centres the player characters, and through them player action, at the expense of effective storytelling.
Tales of Vesperia, for all its subversion, never quite escapes this. The first half of the story is characterised by coincidences – every other town you arrive at gets attacked or otherwise disrupted within minutes of your arrival – and despite the characters joking that protagonist Yuri must be ‘cursed’, it’s impossible to miss the underlying artificiality of the plot structure. Nor does this crack in the façade feel as planned, as deliberate as other things the game does; Vesperia fails to provide contrast by handling its triggers better elsewhere.
There are ways around the problem, though. Final Fantasy XII is at its strongest when confronting this head-on. It has to be, given its theme of the insignificance of the individual. It would be strange to spend most of the plot declaring Ashe inconsequential only for the grand schemers of the world to wait on her every move.
So, for the most part, FFXII does something a little different. You spend much of the game out of touch with events, travelling on foot through the wilds[1]. The plot triggers are generally associated with your arrival at the end of the journey, whether you travel to defeat or just to meet a plot-relevant NPC. When you arrive, what you feel is not that you have caused something to happen, but that you have missed something happening and must struggle to catch up.
When you return to Rabanastre after escaping prison near the start of the game, it’s the kidnapping of Penelo. When you arrive at Mt. Bur-Omisace after travelling across half the world in search of support for Ashe’s royal claim, it’s the replacing of the kindly Emperor Gramis with his merciless son that removes all hope for parlay. Later, arrivals at the Imperial capital Archades and the summit of the Pharos lighthouse are similarly recontextualised.
The exception to the pattern is after the first long journey in the game – here, you’re swooped down on by the Imperials right after subduing and recruiting the powerful spirit that guards Ashe’s inheritance. Why? Because for a brief moment, holding that inheritance, the characters are globally significant. Then the Imperials take it off you and destroy it.
This symbolic disenfranchisement of the player is very FFXII, but doing things this way doesn’t have to be so stark. The key is not that things happen without the player involved (though that helps) – it’s that things happen without a precisely-defined moment. The plot develops while you travel, however long that takes. Even if a specific timestamp were to be given for the event when you’re told about it (‘three days ago’, ‘last week’), the fact that different players will have taken different amounts of ‘real-world’ time to get from trigger to trigger establishes ambiguity.
Plot developments can only seem temporally coincidental if they can be tied to specific moments[2]. The ambiguity of the translation between play-time and narrative time can be used to break these ties and make the narrative feel much more (for want of a better word) organic.
There’s also the brute-force solution, of course: the Majora’s Mask approach. Games like MM and Lightning Returns: Final Fantasy XIII keep the clock ticking throughout. Events happen at precise moments whether you’re there or not. This is, in a sense, the most realistic way of presenting time.
But it has costs, at least if you want to tell a conventional story. Narrative triggers must be stretched, pulled out of shape, or repeated, to prevent the player missing them altogether. It’s telling that both MM and LR let you supernaturally manipulate time – without that affordance, the games would be unnavigable.
What FFXII shows is that the structure of in-game time can contribute powerfully to the meaning of the events portrayed. Temporal structures need not be neutral, invisible systems for the delivery of cutscenes; and they need not function based on an analogue of real time to do so.
[1] There’s something to be said, I realise now, about the relationship of this narrative device to the communicative intensity of the modern world. I’ve felt for a long time that this is something that fantasy narratives will struggle (or are struggling) to adapt to, and I’ll probably return to this theme later.
[2] This is actually tautologous, but I couldn’t think of a better way to put it.
When plot events in a game are tied to triggers based on player progress, whether that’s beating a particular encounter, arriving in a particular location or just talking to the right NPC, that connection can be pretty obvious. Sometimes this is fine, but often it centres the player characters, and through them player action, at the expense of effective storytelling.
Tales of Vesperia, for all its subversion, never quite escapes this. The first half of the story is characterised by coincidences – every other town you arrive at gets attacked or otherwise disrupted within minutes of your arrival – and despite the characters joking that protagonist Yuri must be ‘cursed’, it’s impossible to miss the underlying artificiality of the plot structure. Nor does this crack in the façade feel as planned, as deliberate as other things the game does; Vesperia fails to provide contrast by handling its triggers better elsewhere.
There are ways around the problem, though. Final Fantasy XII is at its strongest when confronting this head-on. It has to be, given its theme of the insignificance of the individual. It would be strange to spend most of the plot declaring Ashe inconsequential only for the grand schemers of the world to wait on her every move.
So, for the most part, FFXII does something a little different. You spend much of the game out of touch with events, travelling on foot through the wilds[1]. The plot triggers are generally associated with your arrival at the end of the journey, whether you travel to defeat or just to meet a plot-relevant NPC. When you arrive, what you feel is not that you have caused something to happen, but that you have missed something happening and must struggle to catch up.
When you return to Rabanastre after escaping prison near the start of the game, it’s the kidnapping of Penelo. When you arrive at Mt. Bur-Omisace after travelling across half the world in search of support for Ashe’s royal claim, it’s the replacing of the kindly Emperor Gramis with his merciless son that removes all hope for parlay. Later, arrivals at the Imperial capital Archades and the summit of the Pharos lighthouse are similarly recontextualised.
The exception to the pattern is after the first long journey in the game – here, you’re swooped down on by the Imperials right after subduing and recruiting the powerful spirit that guards Ashe’s inheritance. Why? Because for a brief moment, holding that inheritance, the characters are globally significant. Then the Imperials take it off you and destroy it.
This symbolic disenfranchisement of the player is very FFXII, but doing things this way doesn’t have to be so stark. The key is not that things happen without the player involved (though that helps) – it’s that things happen without a precisely-defined moment. The plot develops while you travel, however long that takes. Even if a specific timestamp were to be given for the event when you’re told about it (‘three days ago’, ‘last week’), the fact that different players will have taken different amounts of ‘real-world’ time to get from trigger to trigger establishes ambiguity.
Plot developments can only seem temporally coincidental if they can be tied to specific moments[2]. The ambiguity of the translation between play-time and narrative time can be used to break these ties and make the narrative feel much more (for want of a better word) organic.
There’s also the brute-force solution, of course: the Majora’s Mask approach. Games like MM and Lightning Returns: Final Fantasy XIII keep the clock ticking throughout. Events happen at precise moments whether you’re there or not. This is, in a sense, the most realistic way of presenting time.
But it has costs, at least if you want to tell a conventional story. Narrative triggers must be stretched, pulled out of shape, or repeated, to prevent the player missing them altogether. It’s telling that both MM and LR let you supernaturally manipulate time – without that affordance, the games would be unnavigable.
What FFXII shows is that the structure of in-game time can contribute powerfully to the meaning of the events portrayed. Temporal structures need not be neutral, invisible systems for the delivery of cutscenes; and they need not function based on an analogue of real time to do so.
[1] There’s something to be said, I realise now, about the relationship of this narrative device to the communicative intensity of the modern world. I’ve felt for a long time that this is something that fantasy narratives will struggle (or are struggling) to adapt to, and I’ll probably return to this theme later.
[2] This is actually tautologous, but I couldn’t think of a better way to put it.
Subscribe to:
Posts (Atom)