Archive

Tag Archives: Game Design

Game design is a trust exercise. The player has to be able to trust that the game designer’s decisions make sense, that when they take an action within the system the resultant reaction will make sense and be predictable. “Predictable” might sound overly constraining, but there’s a lot of room in between a “technically possible to predict” result and an “immediately obvious” result – that is, as long as the player can still generate a mental map of how state A became state B the system as a whole will seem trustworthy, even if they never in a million years could have predicted that state B would have been the result.

A good example of technically predictable design is Spelunky: Every object in the game interacts with every other object in mostly very simple ways. For instance, a rock, flung through the air, will damage anything in its path. While each interaction is, individually, very easy to understand, in aggregate, they become wildly unpredictable (while still being technically possible to predict). The rock might only fly through the air and do damage, but in so doing it might also knock out the yeti who falls on the landmine which blasts the rock back up into the sky which knocks down the UFO which falls on you and explodes and kills you. There’s a certain kind of satisfaction to dying to something so wildly improbable and byzantine but completely mechanically predictable.

If the player loses trust in the game design, though, everything in the game becomes suspect. A hilarious fluke may instead start to seem like a dirty trick. Goals no longer seem worth striving for because they could be snatched away. Failure seems arbitrary and no longer worth actively avoiding. The game becomes a gamble, with unknown odds and random payout.

I’ve recently been playing through an extensive Dark Souls mod called Daughters of Ash. There are a number of really interesting ideas contained within the mod, but it’s difficult to trust the decision-making behind it. Part of what made Dark Souls such a valuable experience when it came out was that it flouted a lot of the conventional rules of ‘good game design’ – sometimes it wasn’t clear what the game expected of you, movement was heavy and clumsy, and the story was distant and confusing, requiring careful attention to piece together. However, it established its own set of rules to replace these, rules which you learned through hard experience: Caution and exploration were rewarded, if you can see a place you can go there’s usually a worthwhile reason to go there, and if you pay careful attention then you can usually avoid traps and ambushes.

Unfortunately, while Daughters of Ash correctly perceives that Dark Souls broke many rules, it had little appreciation for the new rules created to replace them. Invisible traps, baffling cause and effect, huge detours and difficult acrobatics to get useless items – in the first place it’s harder to trust a mod than the game it was based on, and each decision like these just makes it even harder.

Trust isn’t uniquely important in the medium of games though. Trust is important in all forms of art. You have to be able to trust the painter for long enough to see the painting properly, to appreciate the forms and structure. You have to be able to trust a movie or TV series to be going somewhere, to have some sort of structure of intent and planned payoff. The recent wave of disappointment in the conclusion of the Game of Thrones series is an interesting example of what happens when you start to lose that trust. Retroactively, people start to regard earlier episodes less well, knowing that they don’t like where they end up, and decisions that people might otherwise be forgiving of are judged harshly knowing that there’s no longer any possibility of a long distant future payoff.

I find myself having a hard time trusting most media these days. There’s a few reasons for this. One is technique: There’s a lot of similarity of approach in most popular entertainment, and once you get acclimated to this you tend to see where each scene is going as soon as it starts. It’s hard to trust the artist to take you anywhere interesting when each step along the way seems rote. The other difficulty comes from my increased critical awareness of the tacit implications and arguments forwarded, often unconsciously, by popular art. The weight of the stories that center around a person who is usually some combination of lone genius, borderline abusive, incredibly wealthy, white, and male becomes crushing, the myth-making of a society that has become overtly and obviously cruel and unjust, creating heroes in the mold that coincidentally resembles those who benefit most from that society.

Thus I have become suspicious. I have lost trust. It sort of sucks, because it means that I can often only enjoy movies on a second viewing, only once I know there’s something worthwhile there. It means I avoid watching television or playing new games a lot because the sheer energy output it takes for me to enjoy things is so much higher now.

I don’t mind, though. I prefer this to naiveté. If something is worth doing, it’s worth doing correctly – even if it’s harder to enjoy things, I can enjoy things in more different ways, on more different levels, now. It’s better to be aware, even if it’s more difficult. It’s not like trust is impossible, I just can no longer give it by default. The benefit of the doubt has eroded.

Perhaps trust was always meant to be precious. Do your best to earn it, and do your best to bestow it where it is deserved.

If you enjoyed this essay, please consider supporting me on Patreon. Support at any level lets you read new posts one week early and adds your name to the list of supporters on the sidebar.

Advertisements

Every day that passes, the events in our lives create for us a unique blend of experiences and emotions. Most of the time these aren’t very interesting, but every once in a while it creates something incredible, a moment of transcendence, joy, elation, wonder. Then it passes. That’s just how things happen. Some of us, though, just can’t let it go. We try to capture the moment. Crystallize it. Preserve it. That’s how art is born.

Those emotions and experiences that we try to preserve, though, don’t exist in a void. What creates the moment is the moments that came before it, and it becomes a pressing question: How much of this experience can we carry away from the preceding experiences? How can we separate it from the whole? We can’t completely: That’s why we tell stories instead of moments, why we build to crescendos instead of constantly playing at maximum volume. There’s a desire in inexperienced artists to be at maximum intensity at all times, without really acknowledging that things can only feel intense if there’s a corresponding calmness, lack of intensity, to contrast against.

That’s pretty elementary though. Most artists figure it out pretty fast. Contrast is the foundation of art. However, if you’re trying to create a particular emotional experience, that raises a lot of questions about what that balance ought to look like. How much time should an experience about triumph spend in despair to make the triumph taste sweet? How much time should an experience about love spend in loneliness and disaffection? There’s different ways to answer this, different balances to strike, but over time a set of formulas emerge. The most popular of these is probably the hero’s journey formula, which many set out as the archetypal formula which all stories are cut from – this is an absurd pronouncement that requires many increasingly tenuous analogies to make fit, but it is nevertheless a common argument.

Regardless, the hero’s journey is a useful formula for creating a certain kind of story (the kind where there’s a hero and they journey). Many games, being stories where there’s a hero and a journey, seek to adhere to this formula, but in this medium we have fairly limited control over the exact narrative arc of the experiences we create: Though we might set out to tell a story about a call to action, an ordeal, a boon, and so forth, just as often we create an experience of getting stuck on the first boss for 3 infuriating hours then getting a magic sword and easily murdering the lord of darkness. The dynamic nature of games makes it even harder to create a consistent emotional response, makes it even harder to stick to a formula that strikes the exact balance of sensations we might desire – and, correspondingly, makes it harder for the hero’s journey to be crafted into a game narrative, as gamey as that narrative might at first sound in the abstract.

These are, in short, the two main ways that video game stories suck. Either they try to create a consistent experience of the same emotion – such as, say, empowerment – or they try to recreate a tried and true narrative formula such as the hero’s journey within a dynamic framework that cannot accommodate it. The first is completely untenable, since feelings can only be meaningfully experienced in relation to each other. The second is… difficult, but not actually impossible.

Many game designers would then take that as the challenge: How to systematize the hero’s journey. How to create a narrative-making machine, a myth-making machine, something that takes in player inputs and spits out a grand epic tale. I don’t think that’s a particularly worthwhile goal. The most interesting stories that games spit out right now aren’t imitations of the hero’s journey or some other hackneyed formula, but startling stories of systems gone rampant, results that make sense but are utterly surprising, with the all the perverse interconnectedness and none of the post-hoc narrativization of real history.

Rather than this, we should seek to understand how game systems can lead to emotional outcomes, both in terms of the primary emotion we seek to elicit and the secondary emotions, its opposites, which we seek to define it by. If a game system has an understanding of how it can create frustration and elation, confusion and understanding, joy and sorrow, power and weakness, then it can balance these against each other into a satisfying complete experience. Perhaps this is a more challenging goal than creating a systematization of the hero’s journey, but I believe it is one far more worth striving towards.

If you enjoyed this essay, please consider supporting me on Patreon. Support at any level lets you read new posts one week early and adds your name to the list of supporters on the sidebar.

A few nights ago I was wedged between my bed and the shelves I was trying to cram into my closet. I was soaked in sweat, and resting my head against the flimsy particle board backing of the shelves, which was becoming increasingly flimsy the more I tried to push them into place against the evidenced will of the laws of space and physics. Everything I owned was piled up around the room, and for each new other angle I tried to fit the shelves into the closet I had to move everything around again, each thing blocking where the next thing needed to go, or getting caught on every other thing, or tipping over and scattering things everywhere. So many things. Each action had prerequisite actions, every object a series of locations it had to be shuffled to before it could go where it was supposed to, and at the end, when I was forced to give up, the stacks of possessions piled up behind that stoppage like a train jam, and I felt despair out of any proportion to the problem of fitting a set of crappy Ikea shelves in a closet.

Of course, while the shelf situation was frustrating, it wasn’t the source of despair. The despair that was waiting to raise to the surface was over the chain of prerequisites, the stack of laundry that had to go on the bed so I could open the closet, the boxes that had to go on my computer chair so I could remove the old shelf, the whole room becoming chaotic and unusable just to clear a path, and the path in the end being useless – but then the car I needed to borrow as well, the money I needed to spend as well, the time I needed to make, the projects I needed to plan, as well, as well, as well.

When we speak of the belief that all things are connected, we speak of it as though it ought to make things easier somehow. As though there’s a difference between a web and a tangle when either one can make you drown.

A belief in a the vast interconnectedness of all things is not a cure for anxiety.

It feels like Sokoban, a game of pushing boxes into place, where each box requires pushing other boxes requires pushing other boxes before anything can go where it actually needs to go. It should seem repellent in this aftermath, but Sokoban seems so appealing to me as a game right now because it would be nice to know what the actual boxes are, where the bounds of the arena where they can be moved lie, and to be certain that the posed problem can in fact be solved. Games promise self-contained problems, problems that don’t connect to anything outside of themselves and that you can therefore give yourself wholly to solving without constantly worrying about whether you have to do something else outside of them first. They promise not to be approachable – not necessarily easy, but quantifiably difficult. They promise to have a beginning and an end, to have boundaries instead of the constant hell of shifting walls that the vast sloppy systems of the outside world offers.

They did, anyway. Now games are a service, with boundaries that shift, with ‘new’ services on offer that may in fact just be keyed doors in front of the parts of the game you originally wanted to play. We have gleefully broken down the boundaries of the game that offered such comfort in the naive belief that to have no boundaries is to be free and that to be free is to be unbound. These games are just a symptom of a deeper rot of disruption, naturally. Why have boundaries between work and leisure when you can do both at once? Why have boundaries between work and entertainment when you can do both at once? Why not just have a little bit of work happening all the time, every day, forever? Be a bit more productive whenever you’re idle so you can feel good about yourself? How else could you possibly feel good about yourself?

And before you know it, everything in your life is just a box needing to be shoved into place so everything else can fit. Your chair and bed are boxes to be moved into place. Your friends and family are boxes to be moved into place. It’s all Sokoban now, and what is vitally important is that everything be moved into place, and it’s all interconnected, a puzzle of unverifiable size and complexity and of inescapable urgency.

If you enjoyed this essay, please consider supporting me on Patreon. Support at any level lets you read new posts one week early and adds your name to the list of supporters on the sidebar.

I finished my playthrough of Sekiro a couple of weeks ago, and I’ve had some time to sit and reflect on the experience. If you aren’t familiar with Sekiro, it’s the newest game by From Software, developers of the Dark Souls series, and it’s a continuation of that style of design as well as a spiritual successor of Tenchu, a beloved stealth game which I’ve never played and know very little about. Since I know nothing about Tenchu, I’m going to be talking a lot more about where Sekiro lies as a successor to Dark Souls than as a successor to Tenchu.

The original Dark Souls is still a powerful experience – dark and foreboding and inscrutable, Dark Souls offers many approaches to surmounting its various obstacles but obscures much of its narrative and mechanical breadth behind cryptic clues and interfaces. Sekiro is somewhat different in this regard: While it still maintains several of the mechanics and elements of exploration established by the Souls series, it does not shroud itself in mystery in terms of either its systems or its narrative and it provides relatively few ways to approach any given obstacle. Although I’ve been disappointed by the recent Souls games’ tendency towards simplicity, towards always funneling you into the same approach both in terms of movement through the world and tactics in combat, I enjoyed Sekiro’s even more streamlined approach. Sekiro’s commitment to this style takes simplicity and turns it into refinement.

Combat in Sekiro is usually a duel: Getting up in someone’s face and staying there, answering their every motion, call and response, until the heat gets too much and you need to retreat. While the overall sensation of move in, do damage, move out, is frequently the same as in a Souls, you no longer have the stamina system enforcing that behavior and thus you have much more leeway to keep pressing the attack – and are even encouraged to stay up close and personal for as long as possible before retreating by the game’s posture system, a mechanic of trying to push enemies off-balance through constant pressure so you can deliver a single lethal blow.

However, because there’s no longer nearly as much flexibility in how you approach obstacles – no bows, no bombs, no spells, no shields – the game is rather less forgiving than Dark Souls if you have a hard time engaging with the core mechanic of approach, deflect, counter, and various permutations on same. The game does offer numerous ‘shinobi tools’, such as shuriken, firecrackers, and a flamethrower, to give you these sorts of advantages – but, in the end, they’re all quite limited, and while they will help you they’re not so much an alternate path to victory as a way to gain an initial advantage on the same fight you’d be doing anyway.

Like the Souls games before it, Sekiro is a game about immortality: This thematic element makes a lot of sense as a way to integrate gameplay largely about getting the shit kicked out of you over and over again into a larger narrative. Most games, particularly before the Souls series arrived at prominence, simply narratively discarded any part of your gameplay that didn’t result in success. You reloaded, you rewinded, it never happened, forget about it. What having a game about immortality allows the developers to do is integrate every attempt, every failure, into the player’s story, a story of defeating death itself to right wrongs, of being a ghost or revenant set out to achieve one last vital task. It integrated the video game meta-narrative of undoing failures into an explicit narrative of fighting through them.

(Here’s where I get into the specifics of these games’ narrative. This is what would be considered spoilers for the Dark Souls series and Sekiro, so if you haven’t played these games and want to come to them fresh then you may want to stop here.)

While the immortality of Sekiro and of Dark Souls is treated nearly the same way mechanically, they’re treated quite differently by the narratives of each game. The story of Dark Souls is a story about systems of power and authority, and the existence of immortality within that context is evidence of how those systems have begun to fail – the powers of life and death have started to collapse, and the ancient undifferentiated stasis that held sway before gods and humans has started to take hold. Those who hold the reigns of power try to con those who suffer from this curse – you the player, as well as implicitly a huge number of other undead including all others who may have played the game – into sacrificing themselves in a ‘heroic’ quest to prop up this authoritarian system of divinity… Until it collapses again, presumably, at some point in the future, which the sequels imply happens many many times with each successive iteration becoming more corrupt and exhausted. Alternately, you can choose to subvert the system of divine authority and usher in a new age of dark – which sounds quite foreboding, but is presented more as an age of human self-determination in the absence of the divine than as something eldritch or unholy as standard video game symbolism might have such a name imply. In Dark Souls, ‘Dark’ isn’t so much evil as it is empty, the gaping nothingness we are confronted with when we seek for grand meanings and symbols, terrifying and comforting in equal measure, the pupil at the center of the iris.

However, Sekiro is almost aggressively unconcerned with the systems of power and what immortality might mean within these systems. Sekiro’s story is about what immortality might mean to individuals – old men faced with the decline of their bodies, young men who feel compelled to tackle tasks that are beyond the capacity of any single person, and the children whose youth and boundless potential these men covet and seek to exploit. It’s a game about dropping the ultimate gift of undeath into a world like our own and the strife and desire and bloodlust that would inevitably bubble up around it – in short, a game about greed.

In the story of Sekiro, your first priority is to ensure the safety of your master, the young lord Kuro, a child who has the power to give immortality. Others also want this power, most notably Genichiro who wants it to save the kingdom of Ashina where the game takes place. Along the way other objectives emerge, since Kuro himself decides that this power of immortality is going to keep causing trouble as long as it exists he dedicates himself, and therefore you, to the task of ending immortality, of letting humanity be merely human. Yet, though you are set this grand task, the top priority of the story is generally on protecting Kuro, and you are in the end mostly on this quest because he asks it of you.

Put succinctly, Dark Souls is a game about systems and Sekiro is a game about people, and this affects every aspect of both games. Combat in Dark Souls is largely against huge monsters, creatures who if they ever were human have long since lost contact with that humanity. It is a matter of distance and timing, dashing between gigantic legs or away from gigantic claws to deliver a strike or two and eventually putting the poor thing out of its misery. Sekiro is mostly about fighting people, opponents who move and act very much like you do, who one could easily imagine playing as with only minor tweaks to the control scheme. It’s about pushing up against them, engaging with their every move, answering each motion with a motion of your own, almost collaborative, almost a dance. There’s an intimacy to it, very different in tone to the cold calculation of Dark Souls combat.

The priorities of Sekiro’s story, as well, lie with individuals, not systems: It is a journey to save Kuro and to help him in the gargantuan task he has set for himself. You don’t set out to change the world, only to help Kuro, but circumstances demand that in order for that to happen the world must first be changed. Structures mean nothing without the people that inhabit them.

Genichiro fights to save Ashina, and is willing to sacrifice his people, himself, and his humanity to achieve that – so what is he actually fighting to preserve? An empty name? A ghost kingdom? The battle to save Ashina has gone on so long that the land is deeply scarred, its animals have picked up weapons and learned to fight. The best thing for it would be to let it go. To give up, and see what comes next. The biggest difference between Dark Souls and Sekiro is how they portray giving up. In Dark Souls, to give up is to lose yourself, to become hollow, a shell. In Sekiro, giving up is presented as sometimes the only reasonable option: Lord Isshin, who saved Ashina from a bloodthirsty despot, sits alone in his besieged fortress (aside from occasional outings), content to die while his grandson Genichiro goes to extraordinary measures to save Ashina because he knows there’s nothing there left to fight for. As the player dies over and over, refusing to give up, unleashes a sickness called dragonrot on the world, poisoning all of the people you meet along the way, it raises the question: Is what I’m doing for the best? Or am I just doing my duty, even if it does harm?

Perhaps one of the reasons From Software’s games have done so well is because there’s a certain thematic resonance between their stories and the daily tolls of our lives. Being conned into propping up deeply cruel and unjust systems, feeling hollow but persevering, being caught between an old prosperous generation and a young one full of potential but being pushed into a deeply fucked up world, it’s all a very millennial experience. It doesn’t offer any answers, but there’s something reassuring about believing that at least, somewhere on the other side, there’s something else – an escape, a change of state, or merely progression, perhaps no better than the world we have now, but at least it’s one step away from where we stand.

If you enjoyed this essay, please consider supporting me on Patreon. Support at any level lets you read new posts one week early and adds your name to the list of supporters on the sidebar.

Habits are helpful. Habit is a place to nail down the flapping edges of your behavior, to train consistency in yourself. But as with all points of stability, every habit rests on something else, and those things can be shaken loose. A home, a person, a job, any one of these may seem rock-solid only to roll away, and that’s when habits tend to slip. I’ve been letting habits I’m really quite fond of slip mostly from being distracted, by projects, novelties, and significant life changes both good and bad. I haven’t been writing blog posts – I’m going to be trying to do better on that score, since I think it’s good for my brain to get those thoughts out there and these posts are also the most consistent creative work I’ve produced in my life.

But okay, what about last month’s monthly project? By which I mean the month before last’s monthly project, which then expanded to become a 2-month project? It has, I guess, now further expanded to become a ?-month project.

I should probably talk a bit about what the project is before talking about how it went/is going. I decided going in that it was going to be a 2d platformer, and that for the first time I was going to seek out collaborators instead of trying to go it alone. With input from other people interested in the project it shifted into a 2d stealth platformer with some environmental interaction – think of, perhaps, a cross between the N series of games and Spelunky. Many of these elements are still, ah, a little rough around the edges, but I think the idea still has a lot of merit.

It was and is going well, but I got kind of burned out working on it — part of the idea behind these one-month projects in the first place was that they would be projects I could work full-force on and then complete and put down right around the time my enthusiasm might start to wane. This is the first such project I’ve tried to work with other people on, and I wasn’t prepared either for how that would affect this dynamic or for how busy I would be during that time period. Everyone has their own way of working, and on a freeware-type project like this everyone has a dramatically different scope of time they can bring to bear on the work.

So, right now, I don’t see any reason to rush this project to completion. I’ll be taking the next month or two to work on other monthly projects, while picking away at the most urgent tasks on the platformer as they become necessary, and then revisit the project in a couple of months to try to wrap things up.

In the meanwhile, for this month’s project I’m going to work on creating a vector drawing tool for Unity. This is something I came up against while I was building the lighting system for the 2d platformer project: Unity has very few tools for vector drawing, and those that exist are either no longer supported or aren’t very good yet. I’d like to take this opportunity to try to create a tool for creating vector graphics based off of the Flash graphics class. I’m not sure how far I want to take that approach, how full-featured it will be or what other capabilities it will encompass, but I at least have Flash (and OpenFL, the open source Flash-inspired game dev tool) to refer to for ideas and inspiration. Next month I’ll probably return to EverEnding… sort of! I’m going to try to basically port all the work I’ve done on the project into Unity and see if I can effectively use that to streamline and improve the quality of the work. It’s mostly a feasibility study/experiment. Either way, hopefully having this vector tool available will help in that process as well!

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.

Well, it’s been a busy month. That’s putting it somewhat mildly – the last week or so has been possibly the hardest I’ve ever worked on a project, putting in anywhere from 8-12 hours every day and culminating in one last completely brutal 14 hour day on the first of February to wrap the project up. It’s still not perfect, I could definitely find plenty to do if I wanted to spend a week or so on polish and fixes, but for now I really just need to let this one go, because I’m exhausted and I want to move on to something else.

For January, I participated in Wizard Jam, the Idle Thumbs community game jam. The premise of the jam is to create a game based on the title of an Idle Thumbs network podcast, and since many of those titles tend to be weird and imaginative to start with there’s plenty to work with. I picked The Convergence Compulsion, and then later when I found out that someone else was interested in using the same title, appended the subtitle “The Satisfaction of a Job Well Done”, another podcast title. My very early conception of a game to go with this title was a fast-paced 2d puzzle game in the vein of a match-3 or Tetris where you tried to get different laser beams to line up, but the idea that eventually captured my imagination was a game where you build machines out of elements that emit power, manipulate it, and then turn it into some sort of work. Along the way, it shifted away from the idea of building complex machines and towards figuring out a solution to a puzzle made out of a few components and a number of simple humanoids, kind of like the games The Incredible Machine and Lemmings. At the end it came out pretty close to that, except most of the humanoid behavior had to be cut/simplified.

The concept of Convergence Compulsion is that you work for The Convergence Corporation installing hardware in different locations. The hardware usually consists of at least one power orb, which emits power particles, and at least one converger, which attracts them, and then using these and some other devices which focus, reflect, or split these particles you need to power different machinery. This ended up being kind of a finicky concept – Sometimes machinery ends up getting accidentally powered on just due to random chance, sometimes it takes a while to get the equipment specifically where it needs to be to focus particles, sometimes solutions I didn’t anticipate work and sometimes solutions that should work fail to because I didn’t script the levels to account for them. For the most part, though, I think I’ve managed to achieve the game I had in mind.

Here it is:

Convergence Compulsion: The Satisfaction of a Job Well Done

 

In addition to this, Wizard Jam 8 participants created a number of other great games, many of which I commend to your attention. A few standouts among those I’ve played or seen played thus far:

I’m exhausted but generally pleased with what I accomplished during January, which brings us to February. Now, I had originally planned on making another game this month, a 2d platformer project so I could better understand the capabilities and methodologies of Unity 2d development, but right now I’m really ready to just not work in Unity for a while. Thus, the 2d platformer project is getting pushed back one month to March, and for February I’m going to be focused on writing music, ideally with the end-goal of making another album. I have a few tracks floating around already, so it will really only take maybe 5 or so more to have enough for an album, but we’ll see where I end up. Even if I don’t end up having enough it’s fine, I just want to spend this month making as much music as I can and definitely not programming.