IFReviewed by Paul OBrian on 2006-07-21 06:32
Oh boy. Its time for one of my least favorite comp traditions: the homebrewed game. Traditionally, these games have parsers which lack the amenities provided by any major IF development system, and Getting Back To Sleep is no exception. What does it lack? Well, SAVE and RESTORE, for starters. Oh, and SCRIPT, which means that you'll be seeing no quotes from the game in this review. Rather than making notes at the prompt as I usually do, I had to keep switching to a separate file to keep my notes, and felt slightly annoyed each time. Let's see, what else? UNDO, OOPS, and lots of other modern features, and by "modern" I mean "standard as of 1985 or so." Those weren't there. Nor was VERBOSE mode, which sucked for me, since I always play in VERBOSE mode. Instead, I had to keep typing L every time I wanted to look at the room description. Except that L doesn't work either! Yeah, you have to type out LOOK each time. You also can't abbreviate INVENTORY to I, though at least you can abbreviate to INV. Why one abbreviation is present and not the other continues to mystify me. Here's a good one: the parser is case-sensitive. It understands "look" but not "Look." For a long, scary moment, I thought there was no way to see room descriptions a second time. The parser also breaks my Third Law of Parsing, which is "Parsers must not ask questions without being prepared to receive an answer." GBTS is guilty of asking questions that look like disambiguation ("What do you want to get?") without being able to handle a one-word answer at the next prompt.
It's not that I think creating a homebrewed system would be easy. I'm sure it's a hell of a lot of work. But why you'd put in all that work, coding (according to the readme) over 10,000 lines of C# in a state-of-the-art programming environment, to create something that wouldn't have even passed muster as a text adventure twenty years ago... that escapes me. I could see trying it if that was your only choice, but there are multiple very good IF development environments, all of which produce output that's playable on way more platforms than GBTS is, all of which offer all the features I described in my first paragraph "right out of the box", and all of which are completely FREE! It kind of feels like building your own piano while Steinways are being given away around the corner. It'd be one thing if your piano was going to be just as good as the free ones, but when yours has only 20 keys, no pedals, no black keys, and is wildly out of tune, how can you expect your performances to be any good? One of the sadder parts is that the readme proudly states that this homebrewed system has "the flexibility and freedom to accomplish what no other interactive fiction system can do: the game lives in real time." Well, I can't speak for TADS or Hugo, but Inform most certainly can do that. Hell, ZIL could do it. Border Zone had it in 1987.
Of course, GBTS would have its problems even if it were created with an IF development tool. It's one of those games where you might see shelves full of stuff, and X SHELVES would give you a dull description about the stuff being a lot of supplies and junk. X SUPPLIES gives you the same description and X JUNK isn't even implemented, so you move on, only to find out later (from the walkthrough) that SEARCH SHELVES would give you a special key for one of the game's many locked doors. Many many first-level objects are unimplemented. Its/it's errors infest the prose. There's a sorta-maze, with a randomly appearing object that is vital for solving a puzzle. There's tons of stuff like that. The story itself is fine, though highly derivative of Planetfall. But the game is an experience to be missed.