Beyond being a surprisingly well-written entry among Traveler’s Tales’ more recent Lego-Whatever titles, Lego Batman 2 may contain the most poignant expression I’ve seen of Superman’s perhaps most obvious narrative problem: how does one make a literally omnipotent character dramatically interesting? What does it mean when there’s this one guy always front-and-center who can outdo any individual, super-powered or otherwise, at whatever thing they feel makes them special?
Lego Batman 2 shines a spotlight on these questions in the very best way a videogame can, purely through play mechanics, and with reserved brilliance. Much like the first (much weaker, far buggier) Lego Batman game, the first few acts of the story mode lend Players One and Two the unsurprising respective roles of Batman and Robin. At the start of the second act, the plot twists in such a way that the latter finds himself bumped into the wings when Superman swoops into the Player Two spot. And then things get interestingly weird.
A question from the blog-topics backlog which I’d now like to throw out to the readership: If you have ever played a combat-oriented tabletop role-playing game like Dungeons & Dragons, did you ever actually use miniatures on a grid, as the rulebooks generally assume of their players, with each square representing a 10’-by-10’ area? Or did the combat, as with the rest of the gameplay, stick to an entirely verbal format?
Washington Post columnist Gene Weingarten has announced a new book project with the working title 12.28.86: One Day. For the next two years, he’ll research stories about what happened all around the United States on that date, whose numbers he drew from a hat.
Gene is currently collecting stories and research leads on the project’s Facebook page; one can also email stories privately to an address found in that page’s description. He states openness to anything from headline-making news down to personal narratives.
The date held immediate resonance with me, and so last night I wrote up a little remembrance. It crosses over with games (and the roots of my lasting interest in games) enough that I feel like sharing it here as well.
The XYZZYs are trying something new this year: every nominee must have an IFDB entry. While a perhaps bit wobbly in its homegrown editing interface, the IFDB nevertheless allows anyone to edit its existing game entries, or create new ones. In particular, a game’s creators are not barred from creating or updating their own works’ IFDB entries.
I stress that games you’d like to make eligible via the IFDB needn’t adhere to the classic parser-based IF format. This month I myself have added IFDB entries for both a web-based hypertext game and a commercial game-book adaptation for tablets, both of which I hope to see among the 2013 nominees. The competition’s post on the subject goes into more detail on what is and isn’t acceptable, under the section “Interactive fiction” — though it allows that this style of play does find itself in a period of definitional transition at the moment.
I shared the source of The Warbler’s Nest to GitHub last weekend, a project that took a couple of hours by one measure and nine months by another. I started getting the codebase ready for sharing last spring, shortly after giving an invited presentation about the game at MIT. I considered the event as good a capstone as any on the game’s active presence in my mind, and releasing the source struck me as appropriate epilogue. As it turned out, this preparation would end up perhaps the last personal project I picked up before a family crisis would occupy much of my attention until wintertime. And when, things calmer, I happened across this MetaFilter thread asking about Inform source examples shortly after I received an email from a Warbler player pointing out an embarrassing typo in the story, I thought: Oh, right. And so GitHub.
Mere hours after announcing all this on Twitter and such, I would laugh out loud from the solid upstaging my little effort would receive next to a truly delightful surprise: Daniel Ravipinto announced a special 10-year-anniversary re-release of Slouching Towards Bedlam, an IFComp-winning masterpiece released by Star C. Foster and himself in 2003. Daniel recast the game into Inform 7 (which didn’t publicly exist ten years ago) as an exercise, and this in turn allowed him to easily publish a web page linking to both the downloadable game file and its source text. I sincerely recommend taking this opportunity to try the game if you haven’t already; I quite look forward to playing it through again, myself.
Yes, it's early. No, it's not the Ides of December yet. That's tomorrow. Good thought, though.
I said that I wanted to place the final rooms and cabinets. That's now complete. With all the locks, navigation, and goal-traversal that they required.
I also decided to implement a lot of bits of paper. You'll recall that over the past two months, I chose locations for all the "magic words and recipes" to be found in the game. (Physical objects were basically all nailed down by November.) This information would appear on sheets of paper that you'd collect as the game went on. The first such sheet appears in the HL teaser.
So I decided, what the hey, I'll implement all of those objects. Not their text -- I mostly haven't gotten to scenery descriptions yet. But I wanted to create the objects, place them in the game, and assign their effects: what rituals and formulae do you learn from reading each one? This is all scutwork; I have all this information in my notes, I just have to crank through them. It'll maybe take me one day. And then that'll be done.
I am happy to report that all the items are placed. Every line in my recipe chart has a "found in" notation! ...I'm telling this out of order.
The first half of the month, I caught up on the implementation that I planned last month. That is, I created the ten new rooms (plus some cabinets) that all of October's placements required. And the navigation between them. And the locks on their doors, where appropriate. And the goal-tracking to open the locks.
In the second half of November, I decided all the placements for the latter half of the game. (Two "chapters", but as I said, the chapter numbers do not reflect either game pacing or numbers of objects.) The map grew another couple of rooms, and several more locked cabinets, but I have not yet implemented these.
You might think that the first half of the month was difficult coding work, and the second half was lazily scribbling in locations on a chart. Ha. No. Code is easy. Decisions are difficult.
Every decision is wading into a hazy cloud of "this will probably be okay" and throwing away 99% of it. Most of the possibilities that I discard are fine. Some look fine, but will trip me up later. I have to make sure that the one I keep doesn't trip me up. And then I have to make sure that I like the pacing -- where it shows up in the player's run-through. Or rather, the range in which it might show up. Too soon? Too much confusion early on? Might the player run into the hard-but-correct solution to a puzzle before the easy-red-herring solution? That would be embarrassing.
And then I do it again, and again. I've been doing it all day. My brain hurts.
(Yeah, I'm writing this on the evening of Dec 1st. Procrastination struck after Thanksgiving. I caught up.)
So, okay. I have (nearly) hit a serious milestone, and I am declaring a (sort of) vacation month. My brain needs to stop hurting for a while.
In December I will implement those last rooms and cabinets, so that I can say I've actually placed everything in the game. But I'm not going to work on HL otherwise. I will do holiday things. I will bake a lot of cookies. I may play the latest Bioshock.
I have a sneaky idea for another iOS text game, which I might try to crank out by the end of the year...
I spent the weekend at a delightful little game-dev conference at NYU. Much cool stuff happened there. However, I want to focus on Saturday morning.
Saturday's first talk was by Warren Spector, who has recently switched from developing games (Deus Ex, etc) to teaching the subject at UTexas. His thesis was simple: emergent gameplay, emergent gameplay, emergent gameplay are you listening people.
Here's a writeup of Spector's talk, thanks to Leigh Alexander and Gamasutra.
(Footnote: the quality of emergent gameplay should be referred to as "emergency". As in, "Yeah, that game had a lot of emergency." Hat tip to Vernor Vinge for pointing this out.)
Spector tried not to say "Everything else sucks." He stated right off that he was oversimplifying, and that he's just presenting the kind of games that interest him. But it was hard to avoid the subtext that any scripted, linear, or single-solution interaction was inferior -- bad game design. Inherently. That if players tried the emergent (simulative, rules-based) gameplay they'd be happier and never go back.
To celebrate this, I am declaring an Age Jam! Stop by, build an Age, show it off. It doesn't have to be a prize-winner. In fact there will be no prizes. This is an opportunity to try the tools and get some feedback.
I'm not going to get formal about the rules, but I do want to have some fun with it. Therefore, a schedule!
- Sunday, Nov 10, 1 pm Eastern time: Opening ceremony in the Seltani district plaza. I announce the theme: "Remaining Light".
(The plaza is in the Seltani district. Sign in, link into the Cavern, follow the path along the shoreline and then head right at the fork. Can't miss it.)
(The theme is just for inspiration. Interpret it however you want.)
Nov 10-23: Work on your Age! (Or Ages; multiple entries is cool.) When it's ready, add it to the bookshelf in the Seltani plaza. Or if you want to go for the dramatic reveal, wait and add it on...
Sunday, Nov 24, 1 pm Eastern time: Wrap-up. Meet back in the plaza, start visiting Ages. We can have group tours over the course of the afternoon, and then hang out and discuss what we've seen.
(I know that the meeting time is not ideal for everybody in every time zone. I have schedule restrictions too, so I just picked a time. If you can't be at either ceremony or both, I apologize -- follow along on the blog or the forums.)
I will be around these on-line areas (including Seltani itself) to answer questions during the two-week period. Hope to see you there.
Not goodbye forever, or even for the rest of the year. But it's Halloween; it's been damp and grey all day; and I just returned from the annual Somerville Anti-Morris Dance. Feels like putting the sun to bed.
I spent the first half of October dealing with the remaining major puzzles -- the ones outside the starship. Naturally, this was more work than I expected (it's always more work than you expected) but I got it hammered out.
Then, on to the map! This was more than just adding rooms -- it's about positioning objects and clues.
I've long had a list of important puzzle elements, and a sense of where they appear in the storyline: these in chapter one, those in chapter two, that one behind locked door X, and so on. But most of them weren't actually present on the map. So for the past week, I've been going through the storyline, chapter by chapter, and marking down locations for absolutely everything.