Let's Play: the first section of Anomalous Materials from Half-Life 1

So I recorded a Let's Play for Jake Elliott's "Let's Play" event in Chicago a few days ago. Since the event's now over, I thought I'd share the video for the entire internet to see. In it, I talk a bit through the design of the first section of Anomalous Materials, and how it played with the affordances of first person views / represents two divergent ideas of "realism" / presence, and what being in a virtual world entails. WARNING: a good portion of the video is me staring at a wall and talking over it, sorry...

"From Earth" mod needs writers / narrative designers / concept artists / voice actors.

"From Earth" is probably going to be one of the very last Half-Life 2 mods ever made. It's Mirror's Edge-ish first person parkour + a mechanical machine-shop crafting-puzzle system + original science fiction setting. If I had time, I'd totally help them out... I don't have the time, unfortunately, but I really want to make time...

However, I really do think this is a golden opportunity for people with some mod skills but want to collaborate on a bigger project and focus on specific design problems. This is a veteran mod team that has already finished and released 2 very big mods already; they're small, focused, and they know what they're doing. (Most mod teams have difficulty getting coders, character modelers, and animators -- but that's exactly what they already have, so they're in a really really good position.)

This project is looking for writers / narrative designers, level designers, concept artists, and voice actors. (Again, these are traditionally the easiest roles to recruit for mod projects, the so-called "idea people" who are considered plentiful and worthless. The fact that this team is focusing on recruiting for these roles, consciously and thoughtfully, demonstrates they're different from the vast graveyard of dead projects -- these people get things done.)

Imagine you're a writer / narrative designer who wants to get into AAA, but you're incapable of making games yourself. Ideally, you would learn how to make games yourself, go indie, and bypass AAA entirely -- but if, for some reason you still want to go into the mouth of the beast, this is fantastic chance for you to actually do what they would do... You'll make demands for animations and audio logs and scripted sequences; the team will helpfully explain to you why that would take several years of work; you'll work around these limits and genuinely improve your own ability to design narrative; it'll be hard, but rewarding.

This is a solid project. They're doing a lot of things right. They have most of the core game already working and implemented. If you're a decent writer or multiplayer Source Engine mapper or environmental artist or someone, looking to hone your skills or practice single player design, you should definitely jump on-board. You will make good work and get results.

(Disclaimer: I've playtested From Earth.)

"Different Games" at NYU-Poly, April 26-27 2013.

This weekend I'm giving a talk called "First Personal" at the "Different Games" conference, this Friday and Saturday at NYU-Poly in Brooklyn. I'm going to talk about first person games and why I think they're really well-suited for making personal games. I'll also be showing the newest iteration of CondomCorps in the arcade they've setup.

The conference is free to attend, so if you're in the area you should come hang out for at least a little while.

"Let's Play" at the Nightingale Cinema, April 25 2013 in Chicago.

Jake Elliott and co. are running a "Let's Play" themed event at 8:00 PM on Thursday at Chicago's "beloved microcinema", the Nightingale. What is the LP and what's interesting about the form? What's the difference between LP and machinima, and what happens when that line blurs? (Extra credit: play the Stephen Lavelle classic Rara Racer for further commentary of the LP genre.)

Daphny and Liz Ryerson (and me!), among other artists, have made new original videos just for the show. I think some are even doing live Let's Plays as performance (!!!) Personally, I had never recorded an LP before and it felt really weird to me... are the results compelling at all? Find out in Chicago, tomorrow! Full description and info pasted after the jump:

Urban scenes

Wrapping up work on CondomCorps this week.

The color palette is heavily inspired by the "Benten" levels of Jet Set Radio, as those levels always felt the most "urban" to me. But if we're talking about urbanness, then "what is a city without its people?" The pedestrians on the sidewalks are particles, but obviously particles -- so I think they're actually less conspicuous than, say, the animated runner sprites in Mass Effect 3 skyboxes. To me, that's what most video games get wrong about cities: they are utterly crowded things.

And if anyone asks: yes, New York City has 2 Chrysler buildings...

Dreamlab: VR research at Parsons.

Next year, me and Kyle are starting a (very small) virtual reality ("VR") research lab at Parsons. We've set our initial long-term research initiative as some sort of "virtual sculpting studio" -- so maybe one day you'll put on your Oculus Rift and power gloves, sculpt some virtual clay, and then send the model to a 3D printer? Wouldn't that be cool? We have lots of other ideas too, but those will require a lot more money / space / time, so this is us, thinking "small."

If you think it sounds awesome, please "like us" (ugh) on this weird startup grant social media platform thing so some giant well-funded entity can give us money. Or, if you happen to be a corporate or nonprofit entity that has money you'd like to part with, please get in touch.

The full proposal text is here:

We envision virtual reality as a “place” that allows us to do useful work and experience unique phenomena. Much like going to a woodshop to work wood, or a kitchen to work food, we imagine dedicated VR spaces for people to work and play with data in intuitive ways. How can we use the unique affordances of virtual realities to visualize, embody, and interface with virtual data most effectively?

A letter to a letter

Dear Raph Koster's Letter to Leigh,

You were right when you said that the authors of "personal games" would probably take you the wrong way... It's hard not to. It's impossible to divorce the politics from the forms of these games, which, yes, makes them difficult to critique as formal designed objects without appearing to attack their politics.

These authors argue that "apolitical formalism" is inherently political, that the worst politics pretends it's not politics. Porpentine tweeted that she prefers "blatant bullshit over honeyed poison." (Uh, she was talking about you, by the way!)

I'm sure you'll understand these authors' reluctance to trust this kind of criticism after the past decade of sustained critical attack on such games and their contexts -- perhaps these "crimes" weren't always inflicted by you or whatever, but it's certainly a trigger when you begin your letter with wondering, "what is a game?" My brain shifts into red alert. That line of inquiry has been a long favored tool of well-intentioned oppression, because these arguments often masquerade as thoughtful discourse but function as a weapon of de-legitimization, that argue these personal games can't really fit a formal definition of game. The emotional leap is that these people can't really fit a formal definition of people. Adding, "it's okay if it's not a game" comes off as sounding like, "it's okay if you're not a person," which doesn't really help you seem apolitical.

Again, you're aware of this. You are a very carefully written letter.

The joys of sub-projecting in Unity

Let's say you have a personal Unity framework full of useful models, prefabs, shaders, scripts, etc. that you'd like to use across several projects. How do you best deploy that framework?

If you use version control, then maybe in each Unity project folder you'd also have a special folder hooked up to an SVN or a Git submodule. (Though I find Git submodules to be scary and unwieldy and more trouble than they're worth.) If you don't use version control, maybe you'll keep a separate Unity project just for your framework and from that you'll export a new Unity package every now and then, then separately import and update the Unity packages across your different projects as needed.

There's a third way that I'm trying, inspired slightly by how the Source Engine's filesystem works: basically, you keep all your projects *inside* a main Unity project, so they exist more as "mods" or "sub-projects", and they interface with each other as well as a main framework folder that has core prefabs and scripts.

Post-partum: #lostlevels 2013

As 1/4 of the organizing force behind Lost Levels (the other 3/4 being: Harry Lee, Fernando Ramallo, and Ian Snyder), I'd like to talk briefly about it.

It went really well. Like really really well, much weller than I ever thought it could've went. At least 150-200 people showed up, and we had about 50-70 speakers in the end. Thanks everyone.

I'm sure all attendees and speakers have different takeaways from Lost Levels: on the power of organization, the ultimate uselessness of Powerpoint, why GDC must be destroyed, why GDC must exist, etc. At the very least, I'd like to think we succeeded, to some degree, to break down a sense of "exclusiveness" and unreachability among all game developers and players.

As a former modder, I occupy a strange space in the game developer ecosystem: my background is in AAA tools and techniques, but my politics and interests will often clash with AAA politics and interests. I can't identify completely with the more militant indies nor more militant AAAs. However, I do think militancy has a crucial purpose, and that purpose is to move the middle to a better place, and right now I think that place is toward those who have the gall to align themselves with the forces of human empathy.

Now, all throughout Lost Levels, I felt very conscious of this appearance that we're "against" GDC. Again, we are not against GDC; rather, we are against a pervasive system and mindset that prevents GDC from changing for the better. A giant corporate conference structure has strengths, but it also has very real gaping flaws -- its expense forms a prohibitive cost barrier that fundamentally limits the diversity of voices who supposedly represent all game developers, which enforces a monoculture of ideas and works. Monocultures kill games.

My main takeaway from Lost Levels: we all possess some degree of power. We must simply exercise it collectively, decisively, and tenderly.

Thanks for participating and see you next year!

(As a reminder: I am only 1 of 4 Lost Levels organizers and my opinions do not necessarily represent the rest of the organizers' opinions; it's okay if you disagree with me, you will still always be welcome at all Lost Levels existing and imaginary, whether I'm helping to organize it or not.)

"You sleep rather soundly for a murderer": on murder systems and destabilizing virtual societies.

In many video games, you must kill stuff all the time, and quite frequently. Killing becomes the environment. It is so pervasive that killing becomes the context for something else -- clicking on a soldier's face rapidly enough to demonstrate mouse dexterity, or chaining together different button presses to make combos, or optimizing your stats to make a big number even bigger, or carefully managing various bars before they deplete. The killing is rarely about the killing. (Which makes you wonder why we need to wrap it in the narrative of killing.)

During an Elder Scrolls game, you will likely kill thousands of things. However, all of those killings are sanctioned by the NPCs in the game: you are killing monsters outside of cities and villages. Their deaths don't matter -- more will respawn to take their place, or maybe the game will delete them to free-up memory when you wander away far enough. They exist only to be killed. They are domesticated and farmed.

The Dark Brotherhood questlines in Elder Scrolls games, then, are one of the few instances in games that really focus on killing as killing. Specifically, it frames murder as a deeply anti-societal, anti-social, transgressive act, and explores the philosophy required to justify it. At it's best, it's also deeply systemic.

Summer 2013 @ NYU GameCenter

This summer, I'll be teaching 6 week Unity studio intensives at NYU Game Center. The "regular" class during the semester is usually 15 weeks, so trying to fit all that material into a summer course will be, uh, interesting.

The sessions themselves are pretty expensive, but I believe that they do count for credit that you can put toward a degree. I believe non-students can also take it for non-credit status, which might be cheaper? Unfortunately, I don't set the price, so all I can do is to try to help you get your moneys' worth. You can look at the Github for "Building Worlds", the (15 week) Unity course I'm teaching at Parsons right now -- as well as a blog post on my general approach to game development education.

You'll, uh, also get to hang out with me, I guess. That's a perk, right?

#lostlevels is an indie unconference on March 28th 2013, 1 PM, downtown San Francisco.

Lost Levels is a hyper-inclusive "unconference" about games and play that is FREE to attend, open to all, and anyone can run a session. It takes place Thursday afternoon of GDC week, in San Francisco. I'm co-running it with Harry Lee, Ian Snyder, and Fernando Ramallo.

I don't know about the others, but the main motivation to organize this, for me, was about imagining an alternate world. Yes, GDC conference sessions are fun, but they're really just an excuse for us all to get together and hang out, and we need a giant conference to motivate us all to fly over and converge in one place.

At its core, it's all about hanging out with people and enjoying each other. Everything else is just a fun ritual to facilitate that. But many people don't have GDC passes -- so what happens to them? The ritual isn't as fun if it prevents people from joining.

Our community will, inevitably, be incredibly diverse, chaotic, and messy. We should embrace the messiness and accept that diversity, and strive to lower barriers.

Please visit the site for more details and sign-up if you'd like to attend or give a talk or run a coloring session or dance it out to Tetris music or eat sandwiches. Thanks.

simian.interface, and filler puzzles as phenomenology.

simian.interface, by Vested Interest, is a game that never tells you the controls or how to play or what your goals are, but you'll immediately intuit all of those things just by interacting with it. In this sense, it's very toy-like: you're just playing with this thing, tossing it and turning it over in your hands. No instructions, hardly any rules.

Nominally, it's also a "puzzle game", but it really doesn't fit into the popular sense of a puzzle game. There's this concept of "filler puzzles" among puzzle games, where puzzles that don't demand any new skill or understanding from the player are not as valuable as more novel puzzles. You can be assured that in a Stephen Lavelle puzzle game, for example, every single puzzle has been consciously constructed and filtered and curated over the course of dozens of playtests. Same thing in Jelly No Puzzle: there's always a bit of additional new lateral thinking that trips you up.

In this sense, simian.interface is an awful puzzle game because it is made almost entirely of filler puzzles -- you're just doing the same thing over and over, and the shapes change a little bit. Most levels take about 15 seconds to complete.

... Except it's a puzzle game where the formal novelty of the puzzles doesn't matter?

Course catalog at Radiator University, Spring 2013

If I had a university, these are some of the courses I'd run:

GD 202: LEVEL DESIGN STUDIO: SPACE AND DATA
There are two paradigms of level design in video games: the level as a constructed space, an architectured environment -- and the level as pattern of challenges, a series of situations and encounters. Students will build floorplans in Doom and engineer enemy attack waves for bullet-hell SHMUP games, build custom chess and checkers boards, and populate Skyrim dungeons with systemic parameters. We will also read an introductory body of architectural criticism and attempt to realize that theory as first person levels in Unity. In the end, we will argue that space and data are actually the same.
(4 credits; meets twice a week; satisfies "Spatial" breadth req.; Paris campus only)

DH 100: INTRODUCTION TO DIE HARD 1 STUDIES
This is the introductory course to Die Hard 1 Studies for students interested in majoring in Die Hard 1. We will watch Die Hard 1 every three weeks. In between screenings, we will read the novel it is based upon ("Nothing Lasts Forever" by Roderick Thorp), play Die Hard Arcade, tour several local modernist skyscrapers, and re-create scenes from the film in both analog and digital formats. By the end of the semester, students will be able to argue persuasively that Die Hard 1's many sequels do not actually exist.
(3 credits; meets once a week; bring your helicopter pilot license to the first class)

GDC tips

It's GDC season again... Daphny has a lot of helpful advice on having a good time at GDC, so make sure you read that. Here's some bits of my own:

• My write-up / thoughts / post-mortem of GDC 2012.
• Don't over-extend / over-promise / flake on people, don't promise to meetup somewhere but then realize that you're actually somewhere else, etc. I did this to people last GDC and felt pretty bad about it. GDC, in particular, is really exciting because there's so much going on, so it's tempting to try to do everything at once... don't do it. Pace yourself.
• That said: here's the official unofficial GDC 2013 party list curated by Brandon Boyer.
• If you must be network-y, then don't be network-y with people who aren't network-y. Use your personal judgment as to whether the person you're talking to (especially an indie or academic) will care about the business card ritual or if they're like Daphny, who uses the business card to mean, "please go away."
• Typical flow / activity of the week goes like this:
  

On EA's Full Spectrum event: "the AAA dev's burden" and their DRM on diversity.

"I feel like I'm in Gattaca"

I honestly thought the Electronic Arts' "Full Spectrum" event was going to be a lot worse, but it was actually pretty okay for an AAA-run event on diversity in games. Going into it, I knew it wasn't going to be some groundbreaking thing on gender and media representation: the event was an advocacy / awareness thing, but it doubled as a press conference for EA to flaunt their brand, and I think that's okay -- marketing is okay as long as we all know it's marketing. They didn't pick the location lightly, a massive sci-fi skyscraper literally 1 minute down the street from the United Nations. It was very symbolic.

Generally, the subject material and arguments presented were pretty basic and really obvious to everyone in the room: a collection of power gays, gay media, LGBT game bloggers, and academics. It was preaching to the converted. Which again, was okay. I thought it was going to be worse. (Later, it turned out to be bad / problematic, but in a different way than I expected...)

Portrait of the game designer as a young artist: Avant-Garde, by Lucas "AD1337" Molina

In the short but esteemed tradition of "games about being a struggling artist in the art world", like Jonathan Blow's Painter or Pippin Barr's Art Game, here comes the new and charming RPG-sim Avant-Garde. Look, it even has its own domain name and everything.

Unity to Android (Nexus 7) with Windows, notes / workflow troubleshooting

Some misc. "quirks" I encountered in setting up a build pipeline from Unity (on Windows) to Android on a Nexus 7... some is mentioned on Unity's Android quickstart docs, some required additional research. Anyway, if you're having problems, here's a pile of different things to try:

Castle of the Red Prince, by CEJ Pacian

CEJ Pacian is probably the best short-form IF writer today. His (?) writing is usually firmly grounded in a genre -- Gun Mute in Mad Max / apocalyptic Western, Snowblind Aces in pulp adventure -- and Castle of the Red Prince is firmly rooted in magical fantasy.

The best part of his work, though, is that these genres and settings aren't really the point. In Gun Mute, Walker and Silhouette, as well as this newest entry, Pacian is clearly more interested in formal experimentation on a small but vital scale, and the genre is just a shortcut to approach narrative effect faster. What if navigation doesn't involve cardinal directions? What if everything is a metaphor? Above all, Pacian is interested in re-configuring how we perceive and navigate through space, in a way that only interactive fiction can afford.

Castle of the Red Prince's experiment, then, might follow these rationales:

This one's for the hometown fans.

An image materialized in my head, and I was forced to try to realize it. We'll see how it goes...

PlayThings, a toys and play symposium, 23-24 Feb 2013 at Parsons

PlayThings is a symposium about structures of play, and the ways in which design can enable or resist those structures. What does it mean to play? How meaningful is the distinction between toy and game? etc.

6 East 16th St, 12th flr
in NYC (near Union Square)
February 23rd - 24th
11 am - 5pm

Day 1:
a panel discussion around the ideas of play led by:
McKenzie Wark (Lang)
Colleen Macklin (PETLab)
Zach Gage (stfj.net)
Cas Holman (RISD)
moderated by John Sharp
+
a 3hr play session with various kinds of toys and games i.e. historical toys, mechanical toys, building blocks, plushies/puppets/dolls, board games, video games and physical games to introduce participants with the variety of things and activities that constitute as play.
(led by Kyle Li and Nick Fortugno)

Day 2:
Day 2 consists of a day-long workshop and play-jam session where participants come up with their own games, toys or other forms of public play and the creations are later reviewed by the panel and other participants.
(5 hr making + 1 hr judging/playtesting)
(basic toy building materials provided)

Game narrative as improvisational theater / negotiation.

The current narrative systems prototype Shakespeare has been somewhat disappointing so far: the director switches, seemingly erratically, between 5-6 different plot threads, and nothing seems coherent. I need a way of (a) allowing the player to influence story pacing / scope, and (b) a way for the system to push back, to try to force some story pacing / scope.

For this, I'm looking at how improvisational comedy generates and upholds structure. You might've heard that improv is about "always saying yes," but there's a lot more to it, apparently.

Specifically, longform improv comedy involves actors cooperating to "find the game" -- to find the core of a joke. Each actor makes "offers" to expand upon a premise and move action forward, hopefully toward a funny destination, and usually, actors err on always accepting offers ("saying yes") and building upon it since "blocking" offers frustrates your scene partners. However, it's very possible to "say yes" to a premise while still "blocking" the "game."

Here's an explanation from an NYC improv comedy personality, Will Hines:

Approaches to game development education.

I'm currently teaching a Unity class at Parsons called "Building Worlds" -- and I'm treating it as my opportunity to get everything right and Solve All Problems in Game Dev Education... Obviously, the reality of the class is much more complicated, and ambitious teaching philosophies never really survive a semester intact.

But before I become bitter and jaded, here are the main principles / pillars I'm starting with:

0) Game development is not game design. The former concerns process, implementation, and engineering, the latter is the art of theoretically abstracting behaviors and relationships into something compelling.

1) Breadth. Everyone should know a bit of every aspect of game development, a "liberal arts" education in all facets of development, and everyone should be able to make a game entirely by themselves. All developers should have basic drawing / modeling skills, basic coding skills, and basic design skills. Of course, everyone has their specialties and interests, but the goal of game development education should be to produce independent, T-shaped developers who can see the big picture and collaborate when they need to. Don't specialize too early.

On Limits and Demonstrations, and games as conceptual art.

This is a sort-of-review about Limits and Demonstrations, by Jake Elliott and Tamas Kemenczy. It gets just a little spoiler-y, but not in a way that'd seriously compromise your enjoyment.

Most people play chess with pieces and a board, but to many players that's not the actual game -- it's just a mnemonic aid, a thing that keeps track of chesspiece locations so you don't have to remember where your rook is. The people who live and breathe chess, however, can play chess just by reading chess notation in a book, which is to say that the game takes place entirely in their minds. This is more or less what happens when you lose a heated multiplayer match of Starcraft and agonize over what you could've should've didn't do, and wonder what alternate paths you might've taken. Likewise, I'd imagine the most skilled Starcraft players can play Starcraft entirely in their minds.

It's not just in games either: Beethoven was deaf but he could imagine the notes and harmonies so well that it didn't matter, and a Chinese concert pianist was jailed for 6 years but stayed skilled by "practicing in his head."

But I think game designers, designing games directly as a form of conceptual art, is still a relatively new thing.

A smoother triplanar shader for Unity.

To review: procedural UVs are amazing and you should consider using them in your games. Now, the old triplanar shader I posted was great at hard-edged cubes, but it didn't handle the transitions between textures very gracefully; curved surface like cylinders and spheres were forbidden.

So I took a look at how James "@farfarer" O'Hare handled the blending in his triplanar terrain shader, and how Tom "@quickfingerz" Jackson grabbed normals in his own triplanar shader (but the blending in his shader would "blow-out" a lot, I found) and I combined their respective strengths. I also added different handling for top vs. bottom textures, since grass rarely grows on ceilings. (Textures in the shot above are from Farfarer's pack.) One last change: I let Unity's built-in surface struct calculate world normals instead of calculating my own.

So far, I've been unable to get normal maps working with it, so if any enterprising blog readers would like to instruct me how to do it, and share that technique, then I'd be much obliged.

Here's my shader so far. Do what you will with it:

Narrative systems workflow; using Fourier analysis and level design metaphors to systemize stories.

This assumes familiarity with Shakespeare, a procedurally-branching narrative system that I'm designing. For an overview / introduction, read "More talk, more rock."

I started by arguing that interactive fiction's narrative systems expose too much complexity and detail to its authors and players, or at least more than most people need or want. With Shakespeare, I hope to achieve just a fraction of that functionality, and I think that fraction is enough to be very compelling while facilitating a writer's work.

In engineering Shakespeare, I think of the system in four parts:
a) The real-time system that runs algorithms, interfaces with the game as the player plays.
b) The data / format of narrative itself, how it's structured.
c) The Unity editor interface for generating, editing, or creating the narrative data.
d) The suggested workflow / instructions for using that interface.

Now that I have enough of a base implemented, I'm starting to think more about that last part, the operations design. Roughly, I think the tool could work like this:

My Spring 2013 at Parsons

This semester at Parsons, I have two things going on:

1) I'm teaching an undergrad / grad studio elective course.

Currents: Building Worlds was originally pitched as an "introduction to Unity" class, but then the administration said that Parsons never conducts purely "software" classes. They suggested teaching Unity through some sort of theoretical lens -- and the class design is probably much better for it. So now, it's kind of an intro to Unity / C# / working with expressive 3D / architectural theory class, and it argues for "3D" as a unique expressive medium in itself. There's also a strong focus on discussing "behaviors" theoretically, and how to combine simple behaviors to produce some sort of emergence... whether that's what constitutes a "world." I think I'll assign a chapter of 10 PRINT as a reading? (The "Currents" prefix is like a disclaimer -- "This course is an experiment. Take it at your own risk.")

2) I'm also a "consultant" / aide / "technologist" on another course, taught by Colleen Macklin / John Sharp / Heather Chaplin.

Datatoys is a collaborative class between journalists and design students to re-imagine journalism as a toy -- to turn data into interactive systems that demonstrate patterns of behavior. "Let's face it," began the journalism professor, "reading the New York Times is really boring. Print journalism is dying. Now, what is the journalism of the future?" What are the politics inherent in toys and play? How do we reconcile that with the ethics of journalism? If play is independent and unstructured, does that resemble how journalistic objectivity is independent? Can players act as journalists? How and when do toys lie?

The multidisciplinary nature of these two courses is what makes them conceptually strong and compelling, yet also very difficult to realize into actual designed things... But if they were easy, then they probably wouldn't be worth doing.

More talk, more rock: on algorithmic game narratives, speculative narrative design futures, and "Shakespeare."

Last time, I wrote about procedural narrative in the context of "process intensity." Here, I expand more on designing the procedural / process part.

Back in an expertly-conducted 2011 Rock Paper Shotgun interview, Dan Pinchbeck argued that game development culture unnecessarily separates narrative from the rest of a video game:

"I just want story to be talked about as a gameplay element that sometimes isn’t there. It’s part of the set of tools that a game designer uses to create an experience – and it should be thought of along the same lines, as physics or AI or something more mechanical."

We have physics engines or texture libraries, so why don't we think of narrative as a modular "asset" or "engine" or "library" to be swapped around as well? Why can't narrative be more "mechanical." Where's all the narrative middleware? (Storybricks doesn't seem to be doing too well, unfortunately. I also don't agree with them, that proc narrative is mainly an AI problem...)

Devlog: "Conanbowl"

(lighting / color test with random NPC mobs)
Me and Eddie decided we should make a game this past / current weekend. It started with our usual process: clicking "random page" in Wikipedia until something strikes us. This time, we were struck by "The God in the Bowl," a Conan the Barbarian short story where Conan has to solve a murder (?) when he's actually there because he wants to rob the museum, but then a ghost kills a bunch of people?

Anyway, this concept resonated with us: an adventure-ish game where you must steal things and solve a case; you're a kleptomaniac detective in Victorian-ish London, and you're assigned to cases where you're actually the thief.

Or something like that.

2/3

At some point, I think I forgot I was making a game. It became more like this expansive simulation of every possible reality, folding into itself; I caught myself wanting to make everything interchangable with everything else, to let every piece talk to another piece and act like yet another. Everything was a network, a graph, and every node was another network. Recursion upon recursion.

There's a tendency in game development to think that you will always be coding "the" framework you can re-use and re-use for everything. Everything should be modular, endlessly recyclable, endlessly useful. It's hard to let that go and accept that you should focus on making a game, first -- a game that works -- and not an engine or a library or something that'll change everything as we know it. I ended up forgetting the most basic lessons of making.

Convo felt too big, and it felt too big by 2/3. I had to cut 2/3. I don't know how I can quantify a fraction like that, but I thought about my ability to build and engineer and develop, within the timeframe I wanted, and decided it was overextended by at least 2/3. I've cut a bunch of stuff, but I'm not sure if the scraps on the floor -- do they add up? Is it enough? How do you know if you've cut too much? Is this what Peter Molyneux feels like?

More details soon...

The unportalable: games as paratexts and products

Several years ago, I sat-in on a "games as literature" course, and promptly got into an argument with the instructor. We were talking about Portal, and he argued the dark metal unportalable surfaces seem "sinister" because of their color, rustiness, sense of alien materiality and permanence, lack of affordance, etc. (This was also an introductory course, so a lot of his effort went towards getting students to make critical arguments about games at all.)

I argued that interpretation was irrelevant, and that type of thinking was obfuscating how these surfaces actually function to players: in Portal you don't think to yourself, "that wall is scary," but you more often think "I can't portal there, let's look somewhere else" or "wow that wall looks cool on these graphics settings." To me, the wall material told more of a paratextual story rather than a diegetic story.

Kentucky Route Zero (Act 1), by Jake Elliott and Tamas Kemenczy

The first act of Kentucky Route Zero is now available for purchase, conveniently on the same day as the news that it has more or less swept this year's IGF nominations. The praise is well-deserved. Cynically, you could sum it all up as Sword and Sworcery + Prairie Home Companion + the love child of a Jorge Luis Borges / David Lynch / Flannery O'Connor threesome (except, uh, less violent). It is a game consisting almost entirely of moods.