Simple looking timing library
Oh god this is like catnip. I am going to pore over this in a bit. The gifs are fantastic.
Adam Saltsman on Vanquish. This is good.
"Winning and losing are only defined in their relation to us. Their meaning doesn’t come from an abstract ideal that is buried in the rules of the game, but from our experiences in life, such as witnessing war; or watching Garry Kasparov’s erratic behavior during his matches with Deep Blue; or having once won the emotionally fractured heart of the blonde from class, only to have it crumble in my hands. A game like chess is meaningful because it comments on our wider view on culture—not because placing pieces in a certain position leads to an endgame." On the battle between the logic of systems and the illogic of meanings. Useful food for thought right now.
"The nature of an interactive medium should be the feedback loop between the player and the game; to not explore (or, at least, consider) the expression space of this cycle seems to be a missed opportunity." Trent raises some good points about the relationship between narratives and the systems that tell them.
04 November 2010
There was a reason I wrote a piece of fanfiction based on a game that boils down to a spreadsheet.
Game Dev Story is interesting, for me, because, when you take it apart: there’s almost no Story within the game. It’s just a mechanical engine for simulating a games company (and not even that sophisticated an engine). People work; numbers go up; games either sell or don’t, with sales figures rarely correlating to review scores.
But where’s the story?
There’s a loose theme, sure, with a defined arc: start small, grow into a bigger company by selling more games. There’s almost no writing; what there is is weakly translated, rammed into a line or two of the lazy port. There’s a lot of Devving of Games, but, in the code that executes, there’s relatively little Story to speak of. Just numbers, going up, or down.
Every now and then, the game asks you to type something in: the name of your company, the name of a game. And that’s where the magic begins.
In that little flight of creativity, the game opens up: the player starts writing their own story. The player isn’t just typing names into boxes. They’re saying the words aloud in your head – and that conjures images of box-art, screengrabs, scathing magazine reviews; cardboard standees packed full of buggy, terrible, detective puzzle games, waiting to be flogged.
Sometimes, the companies we invent ring true. Gnarly Games, though named as a pastiche of Visceral, turned out to become a strange mix of From Software and Konami, through their constant return to dour mecha-games and campy vampire nonsense. Their greatest success was, essentially, a Castlevania MMO. Or rather: that’s what I saw in my head. A goofy name, combined with two drop-down fields defining the type of game, led to a moment of wishful, what-if? thinking.
Sometimes, we just give things rude names for the fun of it. But so often that’s a joke that keeps on giving. As the eager secretary tells you again of the wild sales figures for Buggy Shit!! 3, it’s hard not to raise a smile.
The stories you end up telling yourself are surprisingly complex, too. The rise and fall of little companies, kept down by absurd devkit costs and the inability to shift enough units on consoles with dwindling popularity; the companies that held on to founding staff as totems too long, rather than hiring the staff they need; the companies that failed to diversify out of the genre they first found success in. All that is in your head; all the game presents is numbers and loose encouragement.
Game Dev Story exemplifies a kind of mechanical storytelling: stories told not through text or voice-acting, but through coherent systems that cannot help but generate stories. I’m not waving my hands in my air here and making an excuse – “Oh, it has emergent narrative“; my point is that, in good mechanical storytelling, narrative cannot help but emerge. It’s designed into the system.
Such systems are shaped to tell tales of lower-tier football teams, or the survivors of a zombie apocalypse, or mercenaries in Africa, or little companies trying to make videogames. Experiences you play, and feel, and believe, because you’re as much a part of the telling as the machine throwing its myriad D20s.
And, for all its lazy porting, weak writing, and repetitive formula, that is something Game Dev Story does remarkably well. It turns out that it’s not a story in itself. It’s a tool to help players tell thousands of stories. Telling your own stories about running a games company – through the medium of tapping on icons, and waiting – is far more compelling than any description could make out.
It’s a tool to help you do something. That notion led to the thought that mechanically-realised stories – the kind that movies can’t really ever tell, and the kind that games are invariably best at – are a kind of narrative exoskeleton.
Exoskeletons can do two things. Firstly, they can enhance your own abilities: they make you better at something you can already do – faster at running, stronger at lifting. And secondly, they can give you superpowers: things you could never do yourself – such as flying, or breathing in a vacuum, or surviving intense heat.
The best narrative exoskeletons do a bit of both. Off the top of my head: Left 4 Dead; Far Cry 2; Championship Manager; MUD; Acquire; Illuminati!; Werewolf; almost any tabletop RPG. Stories are baked into systems, but told through the by – and through – the players operating within them. Sometimes, we bring our own stories and personalities to the table, and the system amplifies them – the individual relationships between each player in a Left 4 Dead game add as much to their realisation as the characterisation in the script. Sometimes, those systems allow us to do things we could never do: they kill off characters we were too fond of; they force us to move out of our comfort zones; they have a grace of language or performance that we might be unable to attain.
I’m fed up of talking about stories in games (and I say that as someone who has loved many narrative-heavy, densely-plotted titles). Games are much more effective – and interesting – as tools for delivering stories, and, given that players will find their own stories anyway, why not build interesting systems that will shape their tales in exciting and unexpected ways?
Why not build story-telling engines, and narrative exoskeletons?
And that’s why I like Game Dev Story so much: for a game with so little of what most games would call “story” in it, it turns out to live up to the promise of its name in so many ways.
"This is what the next generation of the mega-selling phone will look like. They'll be rough facsimiles of the high-end smartphones forged for well-heeled buyers, stripped of fat and excess—an embodiment of compromise. They'll be 90% of the phone for 20% of the price, with FM radios instead of digital music stores, and flashlights instead of LED flashes. This is how the other half will smartphone, if you want to be so generous as to call the developing world's users a half. We're not even close." Yes.
"Sahel Sounds rounded up music salvaged from the discarded mobile phone memory chips in West Africa." Wow; the after-life of dead electronic media made real.
"Board games are different. Sure, while you might love a board game for the sense of immersion it provides, or the way the game lifts off the table and fills the room, you also might love it for how beautiful the mechanics are. It’s like looking inside a clockwork watch. That fascination, as you see how all the pieces fit together, how everything is timed to perfection, how balanced it all is. With a beautiful board game design, you can love it for that craftsmanship you can feel with every turn." Yup. But, of course: this is, increasingly, why I like any game. It's just much more visible in boardgames – where you have to wrangle the rules yourself. And everything else – the immersion, the involvement – will come too; it just comes from that clockwork heart.
"…what Civilization provides is a story with a beginning, middle, and end, which is three times more than what you probably started with. If you play the game in particularly interesting way, then you can be rewarded with a delightful, surprising experience that you can’t help but weave into a story, inventing characters and lovers and intrigues all round. This story might tug at you so insistently that you begin to jot down notes and timelines, writing diary entries and newspaper reports of battles. Eventually, you might join all those pieces up, rewrite them, throw it all away, and rewrite it again – and then you might call yourself a storyteller." And this is one of the kinds of storytelling that games are best at: collaborative tales weaved between ruleset and player, between man and machine.
Wow. One to return to: a super-comprehensive look at Pac-Man, including its AI routines and collision detection.
"In cinema and theater, we often hear about method acting, a technique by which actors try to create the situations, emotions, and thoughts of their characters in themselves in order to better portray them. In creating Cow Clicker, I rather felt that I was partaking of method design, embracing the spirit and values and ideals of the social game developer as I toed the lines between theory, satire, and earnestness." Bogost calls it Method Design; I've been describing it as "systemic satire" – the making of satirical mechanics.
"The secret to winning this game is rolling "Rock." If you can continue to roll "Rock", you're going to win eventually, because Nothing Beats Rock."
Brenda Brathwaite is awesome. This is brilliant. You should watch it. (This is also in tune with so many things I'm banging on about at the moment).
Spy Part is sounding – and looking – increasingly good. Can't wait.
"But imagine if the writer came up with a "story" before the rules. A "pre-rules story." At that point, you could create the rules around that story, and even if the rules seemed unconventional or unbalanced, you could be confident that they would work as long as the story works." Erm, not really; crap rules are crap rules, even if they make sense within the story. This paragraph directly contradicts his previous (accurate) paragraph, that stories must follow the rules of the game. To then say: "but we can retrofit rules onto the story if the latter was done first" just feels wrong. One more thing on my pile of "stuff about rules".
Just beautiful: an implementation of a Turing Machine, as described by Turing; not only is it ingenious – reading characters written on tape with pen via OCR – but it's also a beautiful piece of hardware; it feels as elegant as the point it is illustrating.