Archive

Narrative Design

Playing games is largely a process of exploration. Often this is in a very literal sense, where you’re given a simulated physical space and part of the challenge is learning the ins and outs of it, but just as often the heart of the game lies in exploring the the edges of the game’s design or of its story. What actually is exploration though? What separates exploring a world from merely experiencing it? How can we support exploration, make it fun and interesting? Or, perhaps more saliently, how can we avoid undermining exploration without meaning to?

There’s two parts to exploring: Methodology and results. Methodology is what separates the process from pure random trial and error – even if you feel that you are wandering aimlessly and finding things as you go, you’re still building up an understanding of the environment in your head and applying that towards your movements. At the very least, you avoid exploring areas you’ve already been through in favor of finding new areas. Results are whatever you get using your method of approach. So, when we’re designing for explorability, we must have both a world that is consistent and predictable, so there can be method to measuring it, and a world that contains interesting things worth discovering. There is also a prerequisite to exploration: In order for something to be revealed, in must first be concealed. In order for it to be discovered, it must first be covered, so the world must also have parts of it which are not immediately obvious.

If you lack consistency of world, then surprises come randomly and without justification, and the player tends to meander interminably before finding anything of interest. If you lack anything worth discovering, that’s obviously even worse, and if everything is already obvious then there’s nothing to find. As an example, if you create a world that’s continuously being randomly generated, it might be an interesting experience but there’s no way to effectively explore it: methodology is useless, the discoveries pointless, and you could never expect to have any more knowledge of the world than one had first coming to it, meaning a world completely uniform in its inscrutability, an open book containing nothing but nonsense. This conflict between randomness and exploration is one reason why games attempting fusion of the randomized worlds of roguelikes with the exploration-heavy worlds of metroidvania tend to succeed far more as roguelikes than they do as metroidvanias.

In creating a simulated physical space to explore, using these concepts of methodology, result, and concealment is a pretty straightforward task to grasp. First, make it so your world has some logical spatial relationship – most games are like this by default, since they’re built on modeling a 3d space, though some like text adventures struggle a bit and map transitions can always throw a wrench in the works. Note that this is not to say you can’t or shouldn’t have weird and impossible architecture, just to note that the more confusing and counterintuitive it becomes the harder it becomes to effectively explore the space, which may or may not be something you want. Second, make the world also have things worth discovering: In purely spatial terms, this would just be an interesting location such as a cave or grove, but more practically this is where the ‘physical’ space of the game starts to overlap into the design and narrative spaces, since most actual interesting locations in games are interesting either because they contain gameplay advantages such as powerups or tactical positioning or because they contain narrative content such as historical information or new characters to meet. Third, make it so it isn’t immediately evident where these points of interest are – this is why having things like minimaps, fast travel, and x-ray vision can work against the sensation of exploration, since providing this information directly often works directly against concealment. Too much information is provided for free, so there’s no real room for method to beget discovery.

So, carrying these concepts over from the spatial realm to the game’s design, if we want to have an explorable design space it must be, first, consistent: This, like spatial consistency, tends to come for free in a highly systemic game but become scarcer the more separate systems or special exceptions exist. If every game element exists within a consistent system, people can devise and improvise interactions, can plan out experiments and log their results. They have a territory to map. Second, the game’s design must have things worth discovering – understanding the bounds of the design is usually a core part of what it means to become better at a game, so this is covered as long as the game’s challenge isn’t trivial. This is part of what difficulty offers us, is a system worth exploring. Third, the system must not be obvious, must conceal parts of itself: This is one that a lot of modern games struggle with. There’s a tendency to clip off surprising and unexpected parts of a game’s design, to ensure that the experience always feels ‘fair’, to set the boundaries of the design strictly at those of the developer’s imagination. It seldom works completely, but to the extent which it works it impoverishes the game.

Narratively, the tenets of explorability tend to resemble a great deal of existing storytelling advice. Avoid plot holes and give characters motivations to create a consistent narrative reality, include drama, jokes, and surprises to generate interest, and don’t lean on cliche and trope so much the entire arc is obvious from the first moment.

As mentioned earlier, these spaces all overlap. The surprises you discover in the spatial layer may have implications for the design, the techniques you discover in the design layer may have implications in the narrative, the story you uncover in the narrative may lead you to new places in the spatial. These aspects are all woven together, and the ability to uncover them collectively is one of the greatest things games can offer as a medium.

Advertisements

For those who may be unfamiliar with The Return of the Obra Dinn, it’s a first-person adventure game by Lucas Pope (the developer of Papers, Please – a game which I keep intending to play but putting off, probably at least in part because it seems incredibly bleak). Obra Dinn itself is hardly un-bleak: In it, you play as an insurance assessor sent out to the titular Obra Dinn, a recently recovered wreck of a ghost ship. You are sent to deduce the fate of all those aboard, and deduce appropriate deductions for the insurance company to make. In order to achieve this task, you are given the “Memento Mortem”, a pocket watch which, when presented with the remains of a once-living creature, can take you back to the moment that creature died. Once in these memories, you can find other remains and follow them back further, and move from the moment this person or animal died to the moments leading up to it, following the chain of disaster back to its inception.

The style of the game is eye-catching, and along with the reputation of Papers, Please drove a lot of the initial interest in the title. Everything is rendered in a pixelated black and white style – or a dark color and a light color, the specifics of which can vary, but in each case is styled after a classic computer system. This is an interesting choice, since the style is unusual and the classic computer systems it harkens back to don’t really have anything to do with the plot of the game, but it creates an overall sensation of being unstuck in time. Here you sit, playing the game in the modern day on your modern machine, rendering in a style reminiscent of several decades ago, exploring a ship from hundreds of years ago, exploring memories of sailors who died several decades before. It expresses a chain of time very well, and reminds us that these weird chains of causality, of death to life to death to life, are all around us, and dictate the flow of our lives to this day.

Something that struck me about Obra Dinn was how unusual it was to have a game where death is commonplace, but is still treated with respect. There’s two molds that games usually, broadly, fall into: Either death is avoided strenuously, or it’s so commonplace as to be meaningless. Either you’re a gentle spirit wandering the world and trying to achieve your goals without confrontation, or you’re a murderous monster leaving a trail of hewn body parts behind you. While you do, in Obra Dinn, fit into the gentle spirit mold, the world you are trying to navigate is one of blood, desperation, and violence. It neither avoids death nor glories in it, merely tests its boundaries and affirms, for those of us who might ever forget, that each death is unique, that each death comes from a seed of causality and can be tracked to its roots. No one is unimportant. No one is indispensible.

A naive reading of the design of Obra Dinn might believe that there’s little actual “gameplay” in the game – that is, the majority of the actions the player takes are walking to the next cutscene trigger, activating it, and occasionally marking down one of a few options in the big book of names that you begin the game with. We’re not accustomed to thinking of things like the shape of a character’s face, their accent, who their friends are, what their job description is, as components of gameplay – but each of these becomes important in Obra Dinn. Understanding the relationships underpinning the tragedy of the ship, understanding why characters choose to do the things they do, is necessary to unravel the mystery that brought the Obra Dinn to its current fate. So often the concept of ‘gameplay’ is pitted against concepts of ‘narrative’ and ‘graphics’, as though these are all completely discrete components that have nothing to do with one another, as though pouring more resources into one might steal resources away from another. One might consider this to be most literally true in a game like The Return of the Obra Dinn, made by a lone developer, where time he spends on one aspect is time he cannot possibly spend on another. Perhaps it’s because it was made by a solo developer, though, that these aspects work so closely together – the graphics are exactly what they need to be to support the narrative, the narrative is exactly what it needs to be to support the gameplay. No, even ‘support’ seems incorrect: These facets of the game aren’t separable. What seems most remarkable to me about Obra Dinn is how all of these components we regard as discrete combine together and become one complete work – the graphics are the narrative is the gameplay.

I’ve played games that have had more emotional impact, games that have interested me more intellectually, games that have amazed me more, games that spoke to me more, games I felt were more meaningful – but Obra Dinn is still something special in a different way. It’s finely crafted, like a pocketwatch, and I think though the details of the tragic voyage will fade, the Obra Dinn will stick with me for a long time.

I’ve been playing a lot of XCOM 2 recently, and after a discussion on the differences between it and its precursor the other day I started thinking about the nature of decisions in games. In XCOM (the first one), you’re expected to make a few very clear-cut decisions in the strategy layer – what to research, what abilities to train, what missions to take, and so forth. Each of these has extremely clear trade-offs. The tactical layer, similarly, has fairly clear-cut decisions, though the effects of decisions can be a bit confusing – it’s not clear, for example, whether you’ll be able to see an enemy unit if you reposition, or see why your odds of hitting are particularly high or low. In XCOM 2, the strategy layer has more decisions with murkier effects: Rather than having a choice of three missions pop up periodically, events you can investigate are constantly popping up all over the map, and since it takes time to investigate these or to do anything else on the map you can realistically only get to so many of them. The tactical combat, however, is much more clear-cut: You can see everything that affects your shot percentages, and the UI will tell you whether you can see an enemy or not when you move, and helpful icons will show if you’re moving a soldier into harm’s way.

It’s interesting to me, given all this, that players generally seem to prefer XCOM to XCOM 2. I think there are a few reasons for this, but the confusing unquantifiability of XCOM 2’s event system is probably the main turn-off, especially nestled, as it is, within the highly regimented and quantifiable decision-making that defined XCOM and, to a lesser extent, its sequel.

It all just goes to make me think about the old Sid Meier quote (or misquote?) about a game being a series of interesting decisions. Though I love XCOM, a game with a relatively few important decisions, a lot of the games I like most have you making little decisions constantly, all of which add up to a big effect in aggregate. In a game like PlayerUnknown’s Battlegrounds, the decision to crouch or not to crouch, lean or not to lean, go full-auto or single-shot, equip an angled or a vertical foregrip, run into the circle at a 5 degree angle or a 6 degree angle, any one of these can be the difference between life or death – and that’s what makes it, despite its many flaws, still so fun to play for me.

In thinking about this, I started classifying the differences in decisions. In general, I think a decision in a game can be considered in two parts: One, how the decision is made (choice properties), and two, the effects of that decision (effect properties). Each of these have three parts – that I’ve thought of so far, anyway.

Choice properties:

  1. Frequency: How often decisions are made
  2. Quantity: The number of options available with each decision
  3. Temporality: How much time pressure there is to make the decision

Effect properties:

  1. Impact: How much they can change the game state
  2. Clarity: How evident these changes are beforehand
  3. Expression: How much the player can express themselves using the decisions

Different games prioritize aspects of decision-making differently. XCOM has medium-low frequency decisions with little temporal pressure and high impact and clarity, with little focus on player expression. The Street Fighter games have fairly high frequency of decisions, making choices at each moment of where to position yourself and which attack to use, with a fairly high quantity of different attack maneuvers, high temporal pressure and impact and moderate clarity (since move effects depend on what your opponent is doing) and a small-moderate amount of player expression… except, that is, in the menu where you select which character you want to use, which is a single (minimal frequency) choice with large quantity, no temporality, and huge impact, clarity, and expression. Super Hexagon is a game with extremely frequent decisions with almost no quantity (left, right, or neither), unbelievably high temporal pressure, high impact and clarity, no expression. The Walking Dead, Season 1 has low-frequency, low-quantity decisions, with some temporal pressure, moderate impact, relatively little clarity, but a huge amount of player expression.

Genres start mapping pretty closely to different decision models, when viewed in this respect. Strategy games prioritize low frequency and temporal pressure with high impact and clarity, tactical shooters like PUBG value high frequency, quantity, temporality, and impact with moderate clarity, RPGs like Fallout medium frequency, impact, and clarity, high quantity, low temporality, and extremely high expression.

From this viewpoint, it becomes clear why many of the decisions made in XCOM 2 rub people the wrong way. The decisions presented to the player in the strategic layer of the game don’t hew as closely to the ideal of what strategic gameplay decisions look like, and though they’re valid as a design in their own right, and I still find them enjoyable, and while they don’t necessarily make it a worse game, they may, in fact, make it a worse strategy game.

It’s important to know what sorts of decisions you want to present to the player, and what sorts of decisions they came to you to get. Trade-offs which may seem like good design when viewed through the lens of balance or of excitement may simply not fit the type of decision system the game is most suited to.

 

Another month has gone by, and though a short vacation, a nasty little cold, and a number of other minor distractions got in my way, I still managed to make a little bit of progress.

First, and most importantly, I put quite a few hours into writing the music for the first boss of the game. I may have gone a little bit overboard on this one: The concept I wanted to pursue was a track with multiple phases that mapped to different parts of the boss encounter, bouncing back and forth between them until finally reaching a conclusion. I’m not sure if I can possibly create a boss encounter that stays interesting long enough to accompany this track, coming in at almost 9 minutes long, but it will be fun to try once the rest of the chapter is complete.

The phases of the track are:

0:00-1:47 Intro
1:47-4:13 The Chest
4:13-6:16 The Mask
6:16-7:49 The Heart
7:49-8:40 Conclusion

This one honestly ended up getting quite a bit out of hand, and I spent quite a bit more time than I’d originally expected to on it, but I’m quite pleased with how it turned out. I also just enjoyed doing music work again! I’m going to carry on with composing the soundtrack even though I’ve effectively completed all the tracks for the first chapter of the game now, which is the part of the game I’m focused on finishing. The reasons why I’m going to continue doing music work, despite otherwise attempting to contain my efforts to this first chapter, are several-fold: first because, as mentioned, I like making music and I want to do more of it, second because if I can’t make this game in a timely fashion I can damn sure make its soundtrack, which is a discrete sub-creation that I can be proud of in its own right, and third because I find music so compelling that I think just having the soundtrack to the game will motivate me more to finish the rest of it. There’s also a fourth, more pragmatic reason: Inspired by UNDERTALE’s soundtrack, I’m really trying to integrate motifs from different characters and locations into tracks with a narrative connection to those characters and locations. It’s going to be really hard to do that until I know what those motifs, for later parts of the game, actually are! I’m not really going to be able to consider chapter 1’s soundtrack complete until I’ve written the rest of the soundtrack and know better what my overall thematic tools and goals are.

Anyway! Aside from music, I’ve been working on a few things. I’ve been feeling my way around programming the main narrative component of the game, the storyteller. This is going to be something pretty similar to what Supergiant does in their games with an ongoing narration element, except I would like to integrate these narrator lines a little bit more closely with the music, syncing the lines up with particular parts of the track and so forth. Additionally, I want to have text appear in the world synced with the audio, so it’s a bit like playing a storybook. Figuring out how I’m going to pragmatically handle the synchronization of these elements and making them play nice with a player who may or may not be interested in the narrative taking place is going to be a challenge, but I’m getting close to having a simple version ready to test so that I can iterate on it.

I’ve also been thinking a lot about what the interface of the game is going to look like. There are really only two elements that need to be displayed under normal circumstances: The player’s current health, and how many sparks you’ve collected, which also maps to your max health. I could just have a red bar along one side of the screen, but that felt inelegant. A sphere that fills and empties like the health meter in Diablo might have been a bit more thematic, since there’s some sun/moon symbolism I’m playing with in the game, but it felt like a circle would take up a lot of screen real estate for how much info it would impart and probably wouldn’t look very good. What I’ve come up with instead is an idea that’s… actually a little bit difficult to express here. It’s basically a life bar along the left side of the screen, except it looks like an engraved stone tablet. Only a small part of the tablet is visible early on, but as you gain more power the tablet expands and you can see more of it, and the engravings on it. I can actually directly tie the health meter into the narrative of the game in what I think is a pretty interesting way. However, because you don’t gain power at a constant rate, but instead end up collecting more and more as you defeat more powerful opponents, I’m going to have to figure out a curve that reveals the tablet at a rate that’s satisfying over the course of the game. I have a logarithmic function in mind that may work well, but it will have to be tested. I’ll also need to figure out how to have the tablet build up in such a way that it feels satisfying, and ensure that no matter what its interim shape is it still gives satisfactory feedback as a health meter. This will all take a bit of experimentation, but it’s an idea I’m excited about.

Finally, I’ve been working on the game’s first animation. I mean, I’ve already built several animations, but this is the first one that will play in the game: The player character awakening, standing up, and taking her weapon at the very beginning of the game. I started creating this animation, and then had to start over after working on it for a few hours because my first take on it sucked. I think my second take on it has potential, though it’s still very rough the motion feels good to me.

The actual removing-sword part of the animation still needs to happen, and of course all of the detail and the tween frames need to be added, but I think I’m on the right track this time.

So, the plan for August is to finish working on these things, write the music for the first area of chapter 2 (I’ve already started), create more main-character animations, and maybe get some basic sound design in. Of course something else may capture my fancy and I’ll end up working on that, but as long as I stick to my big task list I think I can maintain forward progress.

We operate by symbols. Everything we think we see is, by the time we perceive it, converted from the light that enters our eyes into a collection of ideas, into symbols for objects and creatures we know – or, for those things we cannot readily categorize, into a vague description of form and color and behavior. Everything we think we hear is, as well, converted into discrete sounds and music, as best as we can wrap them with understanding. All this happened in our minds long before we ever came up with actual words to describe things: Only much later did we create verbal language to be another set of symbols, verbal symbols we could readily convert to and from these symbolic perceptions of objects and creatures in the world around us.

We navigate by analogy. That is, we have no contact with the world that isn’t mediated by our brain’s model of it, which is constructed out from symbols – we are in a Choose Your Own Adventure novel, manipulating our reality at one layer of removal, always.

These verbal languages are fairly effective at describing the things we can perceive with our senses, but struggle to describe more abstract and ambiguous concepts and systems – so we have other languages and methods to approach these. We created mathematics, a whole new language, to describe the abstract idea of multiple discrete identical objects and how these operate in relationship to each other – when, really, no such ideal differentiated objects actually exist. And, in the same vein, we created fiction to be a meta-language, a language made out of our verbal language, to describe the social, cultural, and technological systems that quietly control our lives.

I’m using fiction in a very broad sense, here. One thing I would include under this heading, for example, is history: The main difference between history and fiction is that the former purports to portray the reality of a thing that has happened. However, this claim to reality is one that anyone can make, and which many spuriously try to. Even when the historical facts are well known and established, the interpretation of those facts – that is, the portrayal of the underlying systems that generated that particular chain of events – is very much a product of the author. Even an author attempting in all good faith to avoid influencing their interpretation with preexisting biases cannot possibly manage to do so: Our assumptions run too deep. Nevertheless, no matter how much empty space the author fills in, no matter how questionable the systems implied by their interpretation, the history takes on the authority of indisputable fact, suitable only to be challenged by other equally authoritative historians.

At one step removed from history, we have fiction that is intended to be ‘realistic’. The underlying systems of reality that govern the fiction are presumed to be the same as the ones that govern our lives, with the only difference being that the characters and situations are invented. In other words, the system, the machine, is intended to be a replica of the original, while the data set it operates upon is wholly fabricated. At another layer of remove there are science-fiction and other alternate reality stories, where the system of the world departs from reality in major ways – though also, usually, remains the same in several vital ways. Humans, or something very much like them, generally still exist in these stories, and they have cultures and laws and societies like ours. They still need to eat and to breathe, they still like to play and to fuck.

How much people tend to enjoy these stories tends to rest a great deal on how plausible they find these systems – that is, once we discount the obviously and acknowledged fantastical elements (suspension of disbelief), how closely does the remainder mirror what we understand reality to be? By replacing elements of the systems of reality with obviously fantastical ones, we can examine the remaining systems more closely, a way of holding a magnifying glass up to some aspect of our world, a way of color-coding the gears of reality. If the rest of the system that drives the fiction is shoddy, though, or if it otherwise fails to be plausible, the reader will reject it. Of course, this is the same situation as the external tensions I mentioned last week: What’s plausible and what isn’t plausible depends as much on the reader as the content. For some people, all robots being sapient is plausible. For some others, all humans being sapient is not.

Every fiction, though, carries an implicit argument: The systems portrayed in this story would create the results portrayed in this story. Because of this implicit argument, all art presents an idea of what the world is, could be, or should be.

A few weeks ago I wrote about how insufficient the idea of all stories being rooted in conflict is – actually, I mostly wrote about how our assumption that conflict is the core of stories affects the way we design games, but most readers seemed more interested in whether stories inherently need to be about conflict. While I never claimed the conflict model of storytelling was worthless, I raised questions about why it was assumed that conflict was regarded as inherently and uniquely necessary to create and tell a story. Discussing and thinking about this afterwards, I think we tend to focus on conflict because it’s the most readily available way to create tension, which is, perhaps, a necessary component of storytelling – or, at least, we can define tension in such a way that that’s a defensible assertion. And, reading this, you might say “okay, conflict, tension, same thing right? A rose by any other name yada yada yada,” and for many kinds of tension that’s basically true. In many cases, even if we split hairs about conflict and tension and which arises from the other and which is a better word for the thing we’re describing, it’s entirely a semantic argument. The reasons why I choose to say ‘tension’, though, are twofold: First, because ‘conflict’, though it can broadly describe any two forces in a story that work against each other, tends to push us towards the idea of interpersonal conflict – so the choice of words matters here. Tension is an inherently vaguer term with less power to dictate the form the action of the story takes. Second, because there are forms of tension that simply cannot be readily described as conflict – foremost among these are what I’m going to call external tensions.

As I see it, every story has internal and external tension. Internal tensions are the places where the forces in the story aren’t aligned and push against each other in some way – sure, there’s good versus evil, but there’s also Denise trying to make an early appointment versus traffic and daylight savings, or Gordon trying to clean his apartment vs his apartment being extraordinarily gross and also he’s still kind of hung over. These map fairly readily, albeit in a somewhat tortuous way, to the idea of conflict – whether “man vs man”, “man vs nature”, or “man vs self”, these have been described as conflict. I would argue that that’s not a very good or intuitive description, but I wouldn’t bother writing about it if that was my only critique of the model.

External tensions, on the other hand, are those places where the story and the reader’s understanding of the world we live in do not agree with each other. It’s why portrayals of flawless beauty or a utopian world are almost painful to experience, because they scrape up against our understanding of the limits and expiration of beauty and our knowledge of the deep and ugly flaws of our world. External tension is how a story can be compelling with nothing approaching what we would call conflict, simply by pushing against our expectations or beliefs in some way. When we look at it this way, stories begin to look like physics energy diagrams, where tension is never really resolved, just converted. Happy endings don’t erase the internal tension of the story’s conflicts, just convert that tension into an external tension against our knowledge of how much rarer and more complicated happy endings are in our world – that they are seldom uncomplicatedly happy, and never really endings.

However, because external tension is contextual, its nature depends on the reader. If the values of the story and its understanding of the world line up fairly closely with your own, you won’t experience much external tension, and if they don’t then you will. Unlike internal tension, external tension produces an implicit demand on the audience to consider why they feel this way and whether to change their understanding of the world, or their understanding of the story, to resolve this tension. This is why stories can be powerful agents of change, because of this implicit demand for action. However, the author can’t know exactly where this tension will fall or how it will be perceived, so attempting to change minds this way can be a risky business – A tension against fascistic elements in a story can frequently be resolved just as easily by embracing as by opposing fascism, and the same story may lead different people to either or neither.

In all likelihood, this is still a flawed way of viewing a story, flawed in ways I haven’t yet noticed, but it still seems at least more encompassing and accurate than declaring that a story is based on its conflicts. It’s a lens, a way of viewing a story: What here generates internal tension? What here generates external tension? And these start to map pretty closely to genres: Drama and suspense and action stories are built on internal tension, on the conflicts between the characters and their aspirations and the world. Satire, science-fiction, and comedy rely more on the external tensions, absurdity and surprise and commentary on real things and events.

The conflict model is valid inasmuch as it’s a smaller version of this model, which encompasses more story possibilities. It’s highly likely that this, too, is a small part of a greater whole, that this still shuts out a great number of possible stories, stories without tension. I don’t know what those look like, yet.

Well, I’m back to working on EverEnding. That side-project ended up being exactly what I didn’t want it to be, an excuse to work on a whole bunch of tools without ever making an actual game to go with them. We’ll call it a learning experience. What did I learn? I learned that I have a habit of avoiding the scary unquantifiable parts of a project in favor of working on parts that feel like safe investments – that I feel, somewhere inside myself, that if I pour my efforts into making tools and systems that that’s a safer gamble to me than pouring them into the actual core of a game. Art is scary! The more time you have to put into making it, the scarier it gets – in the first place, making art is like putting a message in a bottle and letting it out to float on the sea, and it only gets more stressful when you spend more than a year creating that message. The solution is not, I think, to spend another year developing new bottle and paper and ink production facilities to make creating each message that tiny bit less terrifying, but it’s an appealing option to take whenever it presents itself.

Oh, also in addition to those big existential questions I guess I learned a lot about making a scripting system and working with OpenFL. So that’s good too.

Once I decided I’d basically dead-ended, it was clearly time to head back to EverEnding. However, I’d left the project in uh… not a great place. I’d completed about half of the OpenFL port, and lots of systems weren’t running and I’d left lots of bugs in the systems that were running. Eventually, after lots of debugging and deliberation, I ended up rolling back a number of the changes I’d made and reverting back to Adobe AIR… for now. The reason for this is that switching to OpenFL would not only require me completely rewriting all my rendering systems, it would also make a couple of the special effects I’m planning extremely difficult. I really want to be actually working on a game now, so I figure rather than resolving all these issues right away I can defer them for a while. A big thing that enabled that is that OpenFL now supports Adobe AIR as a target platform, so with a few checks in my code to handle cases that are unique to OpenFL (most of which I’d already implemented) I can have something that can run on that version of OpenFL with no changes and, perhaps soon after, build to other OpenFL target platforms. Even if I’m not prepared to implement OpenFL just yet, with my experimentation here and with the side-project I think I have a pretty good idea how I’ll handle it when that time comes.

So, back to working on EverEnding: There were a few big design decisions I’d been deferring, one of which was specifically how to handle the narrative of the game and the other was creating some sort of special moves the player could unlock over the course of the game. I think I figured out a good system for creating a narrative in the style of sort of a story-book, with narration synced to music and text fading in – this is probably something I’ll want to prototype, though, to make sure it actually feels right. The special moves are like 75% figured out, but only the smallest slice of that stuff will be in the first chapter of the game, which is the one I’m focusing on right now, so I can figure out the last of that later. After I got that stuff basically sorted, I created a big task-list for creating chapter 1 of the game. I already had a task-list, but I made one that was bigger and more thorough, and had accompanying time estimates for each task. I tried to overshoot every estimate, but if they’re accurate than I have something in the region of 1300 hours to put into the project before the first chapter is complete. That’s a lot. Then again, I’ve put that much time into TF2, and I didn’t even make that game.

I have my work cut out for me. I’m going to start scheduling myself a bit more strictly again, though I may only get a few days to work to that schedule before I have to leave for a family thing, but with all this down and planned out I feel – well, not exactly optimistic, but determined I guess. I just turned 35, I’m starting to get the tiniest bit of grey in my beard, I got a blood pressure monitor for my birthday. I really do need to actually finish a project.