Some of this material used to be over in the “Practical Pedagogical Notes on Games” section of the site. I’ve decided to migrate it to a blog post, however, for logistical reasons.
It’s an HTML5 world out there. The plug-ins that used to define the landscape of the internet—Flash, in particular—are a dying breed.
If those previous two sentences don’t mean anything to do: Congratulations! You are like most people. This guide is for you. It is a practical, logistical resource to take a peek at when a browser-based game doesn’t work.
Two weeks ago, I taught Gone Home (The Fullbright Company, 2013) for my “Frames, Claims and Videogames” course. I hadn’t played the game in quite some time, so, in the run-up to the course, I re-played it, searching through the house exhaustively, reminding myself of where every last note and prop was, re-acquainting myself with the ins and outs of everyone’s story. Taking some notes, it occurred to me that it would be nice if there was a guide to it online. Not just a guide to picking up all of the items that give you achievements, or something like that—there are plenty of those online, already. Rather, a guide to the stories Gone Home tells, and where exactly you can find the environmental elements that move those stories forward, and flesh it out.
Well, I guess it falls to me to create what I’m looking for. Again.
My guide to Liz Ryerson’s Problem Attic (2013) was just a walkthrough. This is a bit more, as I have specifically designed it to aid in things like class prep and analysis. It isn’t, by itself, analysis, but tends closer to that direction than the Problem Attic one does. (I’d place it roughly in the realm of my Virginia videos.) Enjoy!
Liz Ryerson’s Problem Attic (2013) is a classic of the personal games movement. It is also notoriously difficult, for a number of overlapping reasons. I have come to realize that there are no real walkthroughs of it online, to help players that might be interested in examining Ryerson’s game and seriously considering its themes, but simply cannot get through an especially tricky area without help. I have decided to rectify this, before I teach the game for a class.
If you are looking for pedagogical notes or analysis, be forewarned: there will be none of that in in this post. This is a walkthrough, pure and simple. I’m planning on posting something more genuinely analytical on this game in the weeks ahead, but first I thought I’d do the world a public service. (If only making walkthroughs was something one could put on a CV…)