Reviews by Wade ClarkeView this member's profile
View this member's reviews by tag: ADRIFT ADRIFT 3.8 ADRIFT 3.9 ADRIFT 4 ALAN Apple II BASIC browser-based choice-based comedy commercial Commodore 64 CRPG Eamon educational fantasy Halloween horror Hugo IFComp 2010 IFComp 2011 IFComp 2012 IFComp 2013 IFComp 2014 IFComp 2015 incomplete Inform Lovecraft Python Quest RPG science fiction Scott Adams spring thing 2020 StoryNexus TADS thriller Twine Undum Unity 1-10 of 146 | Next | Show All
Version five of Necron's Keep is a great advance on the buggy original I tried many years ago. I played this hardcore CRPG to completion over four hours and found it to be very entertaining, in spite of the continued presence of many bugs of inconvenience (mostly involving the automatic inventory management). In a nutshell, Necron's Keep is a challenging, detailed and unforgiving single-character fantasy CRPG. There's no UNDO, and you'll need to keep and label many a save file to make it through. What you get in return is an interesting spellcasting system, transparent die-rolled combat and a satisfying gaming challenge with plenty of danger. The story style is probably most like that of a 1980s Fighting Fantasy gamebook, complete with nasty surprises, while the combat adds some AD&D-like detail.
You wouldn't expect someone called Necron to be a nice guy, but the truth of this game's background story is that you don't know. He's an archmage who went off to live with his people in an enchanted castle and fell out of contact with the world. The king has sent you, a mage, to Necron's place to find out what's going on.
In the fashion of many an old-school (or old-school-styled) RPG, the beginning of this game can be the roughest time. It's when random die rolls and traps can kill you off quickly. Traps and monsters will eat your hp (there are both fixed and random encounters), and the spells you cast to try to protect yourself also cost hp. The multi-page tome you're given to read at the game's start is semi-overwhelming, but it combines lore on how the spell system works with hints that will help you later in the game. You start off with a good number of spells; they show up in your inventory. More spells can be learned from scrolls you find (doing that also costs hp!) and some require material components that you need to find on your journey. This is quite a cool aspect of the game, though it takes a lot of observation to work out which components get eaten by the casting of spells. In bad but amusing news, the game is prepared to incinerate your only held wooden weapon to cast a spell requiring wood if you don't have any other wood in your inventory. You can detect traps, mend broken items, divine the nature of things, cast offensive spells in combat. There's a good range of stuff and a lot of it works on a lot of the game's contents.
The thing that might drive some players spare is the inventory. You've got an unlimited holdall, but only finite hand space. So the game autoswaps items in and out of your holdall as required. This constantly results in situations like you putting away one of two things you need simultaneously when you take the first one out, or accidentally forgetting to get the wood out and burning your weapon as a spell component. This is the main site of bugs in the game that still needs fixing.
The early game is about battling through and finding healing items to sustain you. Once you have the power to create your own healing sphere (this is a cool effect, where you ENTER SPHERE, then sleep or meditate to recover), you enter the midgame, roaming around fighting monsters, collecting xp, healing, learning new spells. The late game could be considered tackling the bigger puzzles and challenges of the keep directly. I was stuck for ages in the midgame because one room exit wasn't mentioned, but I'm not sure if this was semi-intentional – there's a magic item you can acquire that gives you an exit lister, and it was the exit lister that showed me the new way to go.
Once you've worked everything out in Necron's Keep, there's a degree of optimisation in stringing all your knowledge together, and probably revisiting older saves where you were in a better position. I felt really satisfied when I completed it.
This is definitely one for people who like this kind of game, and in spite of its inconveniences, I think it's a good example of the CRPG in parser game form. I wouldn't normally give a game with this many bugs remaining a four, but I can't go below four for a game that kept me this involved.
I didn't know who John Napier was before I played this game, and didn't research him until after. He was a noted sixteenth century mathematician with religious and occult interests. The occult angle is the launching point for this parser-based adventure in which the player takes on the role of Napier's assistant in a treasure hunt of sorts.
Napier's Cache is effective and uncomplicated. Simple puzzles are a vehicle for the evocation of servant-filled historical atmospheres, with locations such as the eccentric mathematician's quarters and a windswept Scottish castle. The PC, also a servant of sorts, is observant and resourceful, and views his master through a lens of dependable but arms-length loyalty. NPCs range from dim guards to blustery lords, and the social stratosphere is conveyed by the way the high-ranking characters deliver orders and exposition while 'the help' actually interact with or help the PC. The implementation of the characters is solid enough for each one's purpose.
The game potentially feels a bit short, but this is a sign that what's here is engaging. It delivers a bit of a lot of different effects – multiple locations, exploration, treasure-hunting, easy puzzling, human and animal NPCs – to create a satisfying experience.
(I wrote the original version of this review in my blog upon the game's initial 2013 IFComp release.)
This is a short (ten minutes) CYOA Twine piece about a small-minded masculinity-conscious dad, his overweight and troubled son and how they are eventually attacked by a unicorn. I can let on about the unicorn attack because it's in the blurb of the game and also strongly implied by the title in the first place. I found the experience mildly unpleasant and lacking some other resonance to sufficiently make up for that. The game has swearing, sexual content and violence.
Dad vs. Unicorn carries the fire of anger, manifest as sarcastic energy, and it uses highly crafted minimal prose which is sometimes hard to follow due to its frequent stylistic omission of the verb to be or other sentence-launching entities. This wasn't the first ten-minute Twine game I'd played brandishing the particular combination of anger, swearing, sexual politics and characters throwing their entrails around, and my reaction to each such game tends to be half instinct, and half – if I have ideas about what I think the game was on about – what I think the game was on about.
I read Dad vs. Unicorn as a short assault on traditional ideas of masculinity and how they can screw people up. You can click your way through either the dad's thoughts as he prepares a manly BBQ or his son's thoughts as he looks for his dad around the house. The dad's recollections show how boxed in he is in his thoughts and how disappointed he is in his unmasculine son. The son's recollections are a series of vignettes about being embarrassed or shamed. Both stories lead to the encounter with the unicorn, who kills someone, and you get to pick who dies. After those two experiences you can play from the unicorn's point of view, where you discover that he's not just literally a dickhead, but figuratively one, too. Hypermasculinity leads only to stupid destruction, perhaps?
The dad has only small thoughts and appears to have stopped evolving completely, which obviously isn't impossible, but makes me feel that the pervading angriness is the game's main point, since games in which you can choose which person to play usually use that opportunity to let you experience varying perspectives.
The act of writing about this game showed me I took more from it than I thought I did, but it felt too much like having one angry note yelled at me.
* I wrote the following review of Final Girl for my blog upon the game's initial IFComp 2013 release. The game is no longer available for tech reasons, and may not become available in its original form again, so I've left this review 100% as I originally wrote it. I'm not sure that there are/were any specific solutions to the game that could be 'spoiled' by what I've written, but that said, this review looks extensively at the content and mechanics.
Final Girl is a highly innovative horror-thriller delivered via the StoryNexus platform. The player takes on the role of a teen girl who must identify a masked staple gun(!) killer in the wake of a cabin-in-the-woods-vacation massacre of her friends. I haven't played anything quite like Final Girl before, and while some of that will be down to me never having used StoryNexus before either, it's also clearly down to the game itself. I've not seen a game manage horror genre microscopy like this before, with stats like Squick, Terror, Exertion and Badassery. You even need to manually control your out-of-of-control breathing. The whole thing is framed as a slasher flick, and there are some touches of meta level commentary, but they don't come at the expense of the effect of the core story. As it is tense and gruelling to be the final girl in a horror film, it is tense and gruelling to make your way through this game. This is why I find the author's 'send up' description in one of his blurbs (though not the other, and I prefer the other) somewhat off target.
(The other day I read that a term emerging to describe a variety of ironic storytelling less aggressive and more affectionate than postmodernism's is 'metamodernism', but since I've only heard it once, I'd best not harp on it.)
It may be possible to complete Final Girl in under two hours but I died at around the two hour mark, then accidentally conceded my death, losing all my progress. Well, I'm pretty sure I lost it. The trouble with StoryNexus is that there isn't one piece of freaking documentation for players. While working out how to play was a broadly intuitive experience, finer points like 'Is there an undo? Can I save? Do I need to save?' were all left blowing in the wind. Maybe some veterans can chime in here.
The upshot is that Final Girl is a substantial game with some demanding elements, and it might take you to the two-hour mark or beyond. You'll also need to create a StoryNexus account or log in via Facebook or Twitter to be able to play. It's absolutely worth doing these things, unless you hate horror, because this is an unusual and surprising game. It also has an attractive visual style and an effective audio soundtrack. And more than once it says: "You no longer have any of this: 'staples in your face'". Low level spoilers ahead.
The term Final Girl, describing the lone female survivor at the end of many a horror film, was coined by Carol Clover in her book of horror film criticism "Men, women and Chainsaws". When Final Girl, the game, started with what appeared to be the final scene of a slasher film, I was disappointed with both of the trajectories I anticipated. I thought that either (a) the game was going to cut away from this final scene back to the very start of the story, one of my least favourite filmmaking devices, or (b) the game was just going to be really short and end then and there.
The first surprise of Final Girl was that neither of these things happened. The scene ended with the apparent death of the bad guy, but then the debriefing just kept going until a new investigatory story began. And this story becomes the game, interspersed with flashbacks to the prior story which led to the first scene. So the game's title is a good one. Final Girlness is normally a state acquired by a film's end. In this game, you begin as the final girl, fully formed and already possessed of a degree of savvy – which you'll need because as you'd expect, the killer isn't really dead, and you need to work out who he or she is.
StoryNexus play is based around cards. In Final Girl, these represent locations you can explore. To play certain locations you'll need to have already played particular cards, acquired certain items or set certain stats. Conditions like these can also apply to actions which might appear on the screen. To be able to move, you might need to rest to lower exertion. To do something particularly cringeworthy, like examine a corpse, your Squik level might first need to be reduced, or you might need to take a deep breath to reduce your fright levels. This micromanagement is a good match for the minutiae of horror films the game is simulating, because they're all about microscopic detail: a foot trying to not squeak on the floor, someone hiding in a closet trying to hold their breath, a door handle being turned as slowly as possible, etc. In response to your decisions, the game produces a ceaseless and fascinating parade of cards, badges, icons, skill updates and status reports. If you get better at something like using a pair of pliers, you'll be told exactly how you just got better at using them, whether you learned from fumbling or whether you learned how to wield them with sweaty hands.
Amidst all of this mechanical fun there's still a mystery which needs solving. You went to the cabin by the lake for a vacation with a dozen friends. Where are they now, and is any one of them the masked killer? Flashback scenes round out your relationship with each of these horror archetype teens. So much of this game comes in short stabs of prose, but these slightly longer memories are well written and do a little for each character. They also allow you to act upon the knowledge gained from them back in the present.
The lone element of Final Girl I disliked was the ubiquity of the killer. He (or she or it) attacks you again and again as you explore, and it's a time-consuming and no-gain encounter each time. This kind of ongoing harassment of the player is a pretty common stress tactic in horror games, but it's not handled well here. I suspect its random occurrence rate has been set too high, and similarly, too much of the encounter itself is down to 50/50 luck. That said, it is kind of StoryNexus to either explicitly tell you the odds of success of an action you're about to take or to give you a broad estimate of your chances in words (EG 'nearly impossible').
Dying and accepting your death leads to a game over screen with a movie review assessment of your playing style. This is the most overt display of the game's meta film material, though there are scattered in-game jokes as well. However, Final Girl walks the walk so well, the commentary comes across mostly as a fun addition. The game's act of quoting so many slasher films in its performance is its major gesture, a much stronger communication delivered at a more fundamental level. This is an excellent horror game with a sense of fun, but which doesn't skimp on tension or grizzliness either. It's got a few grindy elements, but with the exception of the repetitive run-ins with the stalker, I think they help make the experience what it is.
The Paper Bag Princess is a short Z-code adventure in which you play a beautiful royal lass whose beloved is snatched up by a dragon during her wedding, and who then sets out to get him back. When I reviewed the game in my IFComp blog of 2013, I quizzed its design extensively. Very extensively! It turns out that the answer to almost all the numerous questions I rhetorically asked is: "This point is only explained in the book upon which this game is based, or depicted in an illustration in that book." Therefore, the summary of my review is that The Paper Bag Princess is only for people who have read the eponymous book by Robert Munsch. To consider, spoilingly, what the game may be like through the eyes of someone who hasn't read that book (me in 2013, and still me today) you may read on.
Quoth me in 2013:(Spoiler - click to show) I found The Paper Bag Princess to be a curiously toneless game, but it has a few amiable moments. The basic idea is of a mild subversion of the prince-rescues-the-princess story, but this idea is never played up all that much in either the dialogue or in the small inventory of actions the princess will take in the course of the rescue. The role reversal idea could be played for laughs, but isn't, really. The before and after scenes of the wedding lean in the direction of black comedy, what with the contrast between the storybook wedding and the charred field of burning furniture the dragon replaces it with, but I thought the writing didn't sell the contrast strongly enough to deliver an effect.
I didn't really get the choice of puzzles for the game, either. Making a torch is a pretty basic adventure game kind of task. I found it strangely difficult to do in The Paper Bag Princess, in spite of the heroine being conspicuously surrounded by scenery and objects which should have made it easy: smoking ground, burning chair legs, a stick, a vial of oil. All the game wanted was for me to type 'make torch', but the wide range of alternative commands I tried as I attempted to make any of these props interact with one another in a fire-producing way were either not understood, or prompted a "You've got the right idea" message. I think the game should have leapt from giving such a nudge to just saying: "Ok, you do such-and-such and go on to successfully make a torch."
Then there were a couple of quotes from classic adventure games; the PLUGH command and a twisty tree maze to navigate. The walkthrough reads apologetically in the case of the latter, just saying: "the maze is entirely random... sorry!" My question is: Why include these in this game? The Paper Bag Princess doesn't seem to derive any particular meaning from recalling the specifics of old games. It's not a pastiche or in the style of, or saying these were good or bad or anything. These features just appear, unremarked upon in any way, and then it's on to the next puzzle.
The final puzzle of outwitting the dragon at least makes sense on the game's own terms. This ostensibly powerful beast is shown to be easily outwitted, a staple gag of much fantasy and classic storytelling. Doing so involves guessing a couple of topics using one of my least favourite IF mechanics - ask (so-and-so) about (topic). If the classic "guess the verb" problem in IF is about knowing what you want to say to the parser but being unable to say it, I would describe the problem of having to come up with the correct topic to ask a character about as a worse problem in which you potentially don't even know what you want to say in the first place. This is a traditional rant for me which I need to deliver about twice a year and have now delivered here. It's not a problem unique to The Paper Bag Princess.
Mostly I just wanted The Paper Bag Princess to start throwing its eggs into some particular baskets. It could have delivered really strongly on the character of the princess, but she doesn't get to say much and the tone of the prose is too often neutral. The role reversal gag isn't played up. The nature of the tasks the princess performs doesn't say much about either her character or the gameworld. The paper bag she dons is not talked up. I don't get why things like PLUGH and a twisty maze were chosen for inclusion, unless the intent was to quote old games while being subversive about the kinds of things you'd often do in them - but this game isn't very subversive.
This review has probably read heavily for a game this light. It's not that I believe people can or have to be able to explain every choice they make as they create something. But considering the smallness of this game, the author doesn't seem to have made choices that aim it in any particular direction. The result is too flavourless for me, and that's why find myself wondering about all those choices so much.
(I wrote the original version of this review in my blog upon this game's initial 2013 IFComp release.)
Mark Marino's entry into IFComp 2012, the one preceding the one in which he entered Mrs Wobbles, was The Living Will, a curious Undum game which I didn't really get. Mrs Wobbles is a far more vivid and transparent affair, a pro-reading, episodic and illustrated adventure tale aimed at younger readers (7-11 it says) and again delivered with Undum. While there is a fair bit to read here, it turns out that this game is also an introductory one, with more episodes potentially to come in future. Folks have entered introductions into IFComp before, and while I don't think there's any rule against doing so (and Wobbles is voluble, not a tiny tease) it's just in its nature that the Wobbles we're being presented with in IFComp has some of the density of a novel without the payoffs of a novel. I also find it hard to gauge how hooky it might be for those future episodes, but I'm not the core audience. Mrs Wobbles feels to me like the opening of an attractive e-novel for tablets. Interactivity is mostly at the level of deciding in which order to read things, and while this area isn't of much personal interest to me, when I consider the overall quality level of the project I think most players will find something to like here. Some may find a lot.
I think the "A Series of Unfortunate Events" books by Lemony Snicket were probably a big influence on the tone of Wobble's prose, and probably more than an influence on its specific content. The protagonists are fostered siblings, their parents died in a mysterious fire and when the game begins, they're going to live in a weird house with a strange adult. The narrator is a magical talking book which can insert whimsical asides into the prose of a kind we'd be hard pressed to get from child protagonists. Production values are consistently high. The game includes some superb woodcut / etching / lithograph style illustrations. The prose is pretty good at any point and you can have it read out to you from author-made recordings. This also means that the speech feature is platform and software independent, and kid-friendly.
What I'm unsure about is how satisfying the scope of this introduction is. It's an introduction for the characters and the setting of the house, but there's no real story vector in place for either of these elements yet, as good as they are. The brother protagonists have a cute rapport, and the fussy girl they meet later, Mildred, is a good foil for them. The house is full of magical rooms and fantastic machinery which may be of use in the future. I suppose the experience of Wobbles is like being introduced to Hogwarts via an explicit tour but then having the book end suddenly. It may be safer to make a self-contained and expositional starting adventure, but it's probably less interesting than throwing players/readers into a story which sets up some plot hooks and mysteries. In the end, my to-ing and fro-ing about Wobbles comes down to the fact that this is an introduction competing in a venue not particularly suited to introductions.
(The original version of this review was split over two blog posts I wrote upon this game's initial 2013 IFComp release.)
Dream Pieces is a friendly-feeling bedroom adventure of word puzzling delivered via the Quest platform. It has semi-rhyming (and semi-straining) prose and some nods towards helpful production values – for instance you can choose whether the presentation is delivered to suit a desktop computer, a tablet or a mobile phone. The goal in Dream Pieces is to manipulate domestic objects in your bedroom to create tools and methods to further manipulate domestic objects in your bedroom, but it's more fun that I just made it sound. Tools can split the names of objects into constituent letters which can then be rearranged to create new props. The game uses some features of Quest well, like being able to right click a wordlet, click 'Mix', then click the thing you want to mix it with from a menu.
When I initially apprehended this mechanic, I felt my interest prickling, and since the game gives the impression of being easy enough for a child to complete, what with its child-like font and enthusiastic outlook, I figured I was about to power through the whole thing for some simple satisfaction. I ended up abandoning my first playthrough due to a moment of inflexibility that I mistook for a bug. Other IFCompers cleared me up on this point and brought it to my attention that there was a colour-related mechanism in play that I hadn't noticed. I then powered through to victory like I'd thought I'd been about to the first time. The game has apparently been significantly updated since I played its original incarnation.
Dream Pieces certainly offers easy word-chopping for an adult but would probably be more outwardly satisfying for a kid. It was also the first word game I'd seen released for the Quest platform, and it came out after a year that birthed a decent number of sophisticated word games in IFdom.
(I wrote the original version of this review in my blog upon this game's initial 2013 IFComp release.)
100,000 years is a sci-fi Twine piece about galactic-sized spans of time. It is easily worth any comp-goer's time to try as it is very short. I almost said "ironically very short," but that would have been silly as the smallness/largeness thing is obviously a feature.
The goings-on in a chunk of the universe are described in a few lines of verse. Clicking the left arrow takes you 100,000 years into the past while the right arrow takes you the same distance into the future. Changes over that time period are then described, but the arrows remain, ready to move you forward or backward again. The result is a tiny existential text toy. What you discover if you go far enough in either direction is equally likely to make you feel more a part of the universe or just less significant. The achievement of 100,000 years is that it can touch on those feelings quickly and with such a simple device, though the whole piece is definitely short-lived.
In 1984, Usborne published Island of Secrets, a fantasy text adventure not delivered as software, but as a book enabling players to generate the program themselves by typing its BASIC listing into their computer. The book doubles as an illustrated reference to the world of the game, containing the background story, character and location guides, coded hints and a map. The game’s prose and engine are so sparse that the book comprises at least half the experience, making it considerably more fundamental to the accompanying game than, say, Infocom feelies are to Infocom games. The story concerns Alphan, a young scholar tasked with collecting objects of power in order to restore a war-darkened Earth.
The Island of Secrets book was a great inspiration to me when I was a kid. The illustrations have a lot of mood and character, the allusions to all the mysteries in the game’s world are intriguing, and the book is full of footnotes about text adventure design and programming. I had to take considerably more from the book than from the game because I never succeeded in getting the game running; I made too many mistakes while typing it in. I was in my twenties before I found a working copy on a public domain disk.
The main reason the book is so essential to playing Island of Secrets is that at least half the findable objects in the game are only cued by their appearance in the book’s illustrations. Island has about sixty locations, but is limited in its overall capabilities by having to support such a wide range of microcomputers out of the box (the Apple II, the C64, the VIC-20, the BBC, etc.). This means the whole thing has to sit and function in about 32kb of RAM after a single load. There’s no space left to hold descriptions of most objects, or to describe or implement scenery that could conceal those objects. All of that work and more is passed off to the illustrations and clues in the book. Mercifully, by holding the back page of the book up to a mirror, a player can obtain the short list of supported verbs and nouns.
Technically, the gameworld’s sophistication is above the level you’d expect from an adventure that presents itself mostly using the Scott Adams aesthetic. There’s a food and drink system, random events such as a storm, and characters who can move around. The characters have histories and motivations detailed in the source book. Amongst them are a Charon-like boatman, a scavenger who’s lost his memory, a depressed swampman and a missing scholar. You need to consult the book to guess at what might variously turn these people into allies, get them out of your path or help you defeat them. The particular solutions the game wants in these departments can be a tad abstract. While the source material is rich, the feedback delivered by the necessarily lean game program is poor. In this respect, Island of Secrets is definitely a story and a game whose visions seriously outpace its game engine. If I’d got it running back in the day, I can see that it would still have been a challenge to complete (without cheating) due to its sparseness, but I might have had the patience for it. In revisiting the game for this review, I was momentarily saddened to acknowledge I no longer have the time or patience. I used a walkthrough.
In its time, the Island of Secrets book provided a way to deliver to kids an adventure game with a deeper story than a BASIC program alone could normally pull off while teaching those kids about programming and game design. As a kid in the relevant demographic, I found all of the related Usborne books exceptional at doing these things, and official versions of them all have now been released as free PDFs. (scroll down on the target page):
Island of Secrets – along with The Mystery of Silver Mountain, Usborne’s other major type-in game presented using the same book and BASIC program combination – now seem unique in the way they’re meant to be experienced. That said, that way did grow out of necessities presented by the limitations of BASIC and the computer hardware of the time. IF players still seem to like feelies, so maybe there’s some weird mine of book-game interdependence that could be retapped for a new project today.
(I give the Island of Secrets book five stars in any year. As a text adventure played today, I can only give Island of Secrets two stars.)
Awake the Mighty Dread takes place in a fantasy dreamworld fuelled by Alice In Wonderland, The Wizard of Oz and the aesthetic of steampunk. It's got orphans, air travel, capricious NPCs ranging in scale from an amphibian to a deity, and a reverence for storybooks. And all that in a smallish game. It's alluded to that its orphan protagonist slips away to the dreamworld in order to avoid abuse back in the real world, but the social system in the dreamworld turns out to be a troubled one, too. The heroine's spiky curiosity about what's going on there is well written, and provides motivational fuel for the player in a game which turns out to be not very good at signalling progress through it.
Awake is actually the IF dimension of a larger project by its author which can be found at
However, the game was basically presented as a standalone entity in the 2011 Interactive Fiction Competition. Exploring the rest of the project might thicken Awake's backstory, but I doubt it would actually help in the playing of Awake for reasons to be enunciated in this review.
Awake received mixed reviews when it appeared in IFComp. My own private review (for other game authors that year) began:
"Since people have been saying that they found this baffling, I secretly patted myself on the head for not being baffled."
So, I liked the overall experience more than most, but the game's delivery is clearly a failing one. In spite of the author's writerly prose and obvious knowledge of some advanced parser conceits, the game exhibits no awareness of how to steer a player through its contents via the parser. Location descriptions are aesthetically pleasing but player-insensitive, with almost none of their interesting features implemented. The features that are implemented are there to service plot points in a story that only seems threadable in retrospect. Trying to make the story happen yourself with the game's minimal direction and tech oversights is futile-leaning, and so the game's solution file is essential.
In the case of contemporary IF, I have low tolerance for being involved with walkthrough/hint systems unless they're really well considered. I also have design philosophy qualms about some games I consider to be impossible without a walkthrough. Awake bypassed my concerns in these areas because it's an interesting failure of an accessible kind. Reconsidering it five years down the track, I'd say it's definitely of more interest to people who create IF games than it is to player-players. In this capacity, it's substantial enough not to feel too small or inconsequential, but still small enough not to feel like a time burglar in spite of its black box implementation.
That black box is actually the point of interest; playing Awake feels like trying to build a Lego model without being able to see your hands. A lot of interconnecting prose seems to be absent in this game. There's a train you start out on, and which automatically travels from station to station, and there's an effect whereby you can see what station you're at out the window. But the descriptions within and without can be indistinguishable. Being on a train in a location can be the same as just being in the location – until the train moves, of course. Similarly, objects sometimes appear 'painted on' in room descriptions, and stay there even after you've taken them. NPCs speak at appropriate moments but don't show up as prose entities when they're not speaking. It's hard to tell when conversations have ended, or if the conversants are still about. Finally, the most important action you must take in the whole game is unguessable, and deliverable as a command in a form that only hardcore parser folk would be aware of. Collectively, these sophisticated-leaning bugs at the coalface of interactivity suggest the author had strong familiarity with parser games but didn't run Awake through a sufficiently typical or robust group of playtesters.
I find the story in Awake interesting, and the game succeeds in feeling like a window onto a larger fantasy world, but in the end its technical oddities render it mostly a curio for parser nerds. Its contents can't be unspooled easily the way the contents of the famous stories it most emulates can. The site of the obstacles is its interactivity.
1-10 of 146 | Next | Show All