The author of this short adventure bills it as "an old-fashioned 1980's style text adventure" and notes: "[T]his isn’t modern IF, it’s an old-fashioned puzzle game with a wafer-thin plot and dated concepts like darkness, And, yes, there are a couple of things you can do to make the game unwinnable, although I’ve tried to make these somewhat obvious." It was also apparently produced as a first attempt of using the PunyInform library (version 4.0), and officially left beta status last month.
The premise seems intentionally absurd: You are a duck -- a toy plush duck -- living in a world that seems to be made of a combination of toy building materials, natural caverns, and occasional technology ranging from antique to futuristic. If that bothers you even a little, then you will find little to enjoy about this game. If the idea of a mashup between "A Bear's Night Out," "Planetfall," and a generic Scott Adams game sounds fun, however, then keep reading.
The PC wakes with amnesia and does not seem to understand why he/she is a plush duck. The "wafer-thin" plot consists of trying to escape an abandoned research complex by summoning help from the associates that left you behind while evacuating. To do this you will need to solve a series of arbitrary puzzles. So far, so good.
The gameplay experience rapidly breaks down, however, because many of these puzzles are significantly underclued. This is aggravated by the fact that there are numerous red herrings. It is further aggravated by the presence of what look like serious bugs that can lock out a win state without explanation or warning. (Spoiler - click to show)I don't know for sure what is causing these, but they seem to be related to lighting conditions. Key objects and object components can "disappear" either intermittently or permanently. Make sure that you have light when conjuring vegetables, and try turning the torch on and off if anything seems to be missing an essential component.
The essential flaw of the design is a failure to provide feedback to the player regarding partial progress on puzzles. This is absolutely critical for any complex puzzle requiring an extended series of actions, so that players can understand that they are on the right track. The most egregious example here is the puzzle involving retrieval of a piece of paper wedged under a heavy desk. Despite understanding the basic idea of needing to lift the desk to free the paper, this was not easy to accomplish even with a found item that seemed perfect for the task. (Spoiler - click to show)The actual solution requires use of multiple objects stacked onto one another in order to get the jack high enough to work, but there is no indication that the reason it doesn't work is that the jack is not high enough on its own. Multiple items must be stacked under the desk to get it high enough. (NOTE: The first version of this spoiler said that the need to turn one of these items over was "inexplicable," but it is in fact quite explicable and consistent with a similar item. I just wasn't paying very close attention to the default game output about this object. My apologies to the author!) There is no indication that the player's plan could work if conditions were adjusted. I had to resort to decompiling the game file to get the solution here.
Another flaw, arguably one that is stylistically appropriate for 1980s works, is that certain events occur "off-screen" as a result of your actions without any indication that this has occurred. The key example here involves obtaining a head of celery; the player simply won't know when this puzzle has been solved. In fact, the feedback given when the correct action is taken implies that the task failed. The player must wander to another part of the complex to find that the celery can now be obtained (with a little more work).
The last serious flaw involves a failure to communicate important in-game information to the player. I'm thinking here of a snake that prevents access to certain areas. Although the PC claims to remember something about the species, the essential information (Spoiler - click to show)(what it eats) is not provided, even after a puzzle has been solved that the game states should improve your memory. Good luck finding the solution here via anything other than brute force.
This game is littered with what look like author in-jokes, or possibly references to sources (like cartoons) not made explicit. A mysterious "ethereal" voice that harangues you every so often has no explanation, but it seems to be linked to a red herring that can be found. An even more mysterious event that happens at move 37 seems to have no bearing on the plot or in-game explanation. The ending makes no sense at all, as far as I can tell.
Despite the above, I basically wanted to like this game. The author clearly put a significant amount of work into the implementation, and the main set piece puzzles (involving a blender and an automated surgeon) are competently executed. There are some clever bits here (like a light puzzle not based on batteries running out), and the oddball humor appealed to me where it was accessible. The two-star rating that I'm giving it means "almost there" in my ranking system, and it would rate three stars (aka "good, not great") with better focus and the cleanup of game-threatening bugs. I'll keep an eye out for a release 2.
The Lost Islands of Alabaz has been out for more than a decade now, and, while it did make a splash by winning the Spring Thing 2011 competition, it seems to have faded into something like obscurity in the years since.
This is a grave oversight.
Michael Gentry's overlooked gem is an exquisitely well-planned introductory adventure for children (or, indeed, for adults sufficiently young at heart). Developing it in the years after his work on Jack Toresal and The Secret Letter, he seems to have been prompted to write this piece as a test of his own insights about how to craft a kid-friendly IF experience.
In the same way that his genre-savviness elevates Anchorhead above the pack, his deep intuition about children's storybooks serves him well here. The very first interaction, the simple device of asking for the protagonist's name, is a remarkably-effective hook for young players, especially as it is phrased ("What is your name, brave Knight?"). Immediately, the player is invited to either enter his or her own name (thereby stepping into the story with an actual identity) or to invent a heroic-sounding name (creating an avatar to embody an archetypal persona). From there, the target player is deftly drawn into the fairytale world that will be the story's setting while at the same time being shown the ropes of interactive fiction. The spare text style of just a few lines to describe each room is appropriate to the genre, won't tax even intermediate readers, and leaves plenty of room for the imagination to fill in the details -- especially after it has been sparked by a few carefully-chosen adjectives. The tropes at play are simple, and the story progresses with a light-hearted sense of fun that is both charming and compelling. In the first few moves, during which the tutorial mode is active, I was powerfully reminded of Infocom's Wishbringer, but it is important to note that this isn't an "old school" style game.
Once again, the author's talent for integral design of the play experience is evident; a few careful changes to the mechanics of interaction do much to set the mood for those familiar with interactive fiction, while smoothing the way for newcomers. The world model is somewhat simplified from the standard: Only four cardinal directions are supported, and objects never leave inventory once acquired. NPCs are talkative enough within the game's ASK/TELL model, which can be daunting for beginners, but implementation of a "topic-prompting" system (similar to that of Lost Pig) and functional combination of the verbs ASK and TELL make it very easy to get started. The SHOW and GIVE verbs also can also be used, a discovery that new players seem to make intuitively once they have had a few interactions with people in the world.
Trig, an almost ever-present sidekick who is the most prominent NPC, arrives early and takes over as the game's tutorial voice after the first few moves. By the end of the first chapter, he stops dispensing tutorial advice, and from that point on he doubles as a hint system. Repeatedly asking Trig about an active problem (as identified in the self-updating journal) will yield increasingly larger hints. It's quite intriguing how this plays out psychologically with young players -- they seem naturally resistant to asking him for help whenever they think it is something that they should be able to figure out themselves, even when stuck. Perhaps this has to do with the way that Trig's personality is implemented; he is somewhat dull, in the style of Trent/Tiffany from the Infocom canon. (The logic seems to be "If even Trig can figure it out, I should be able to!")
NPCs are an integral part of the game. In addition to Trig there are two other crew members, Javier and Zoey, that the protagonist is nominally in charge of as captain of a ship. These at first seem to be information-dispensing cardboard cutouts (the dominant but wholly-appropriate style used in the game), but at several points the protagonist needs to gain cooperation from one of these team members to complete a puzzle. This is a small but important touch, moving them out of the realm of background decoration and into the realm of supporting characters. At least one of these occasions requires issuing a command to Trig, an affordance that might not be obvious to new players but which Trig himself introduces as an optional interaction during one of his last tutorial voice comments.
Although the hint system is in place, it is rarely needed because the puzzle structure is masterfully designed. It works marvelously in conjunction with the game's "journal" system that serves in place of a score. Reading the journal lists achievements that have been accomplished as well as the pertinent puzzles to be solved at that point. The effect of reading over the list is much like a FULL SCORE command without any numbers attached, and it's interesting how over time this creates a sense of progression through the story's highlights without implying a precise measure of how much of the game remains.
Initial puzzles barely count as such, with solutions on the order of opening a container or walking between rooms, but the difficulty level slowly increases over time. While even the most difficult puzzles in the game are on the easier side for experienced players, several are clever in their construction and require small leaps of intuition that are just the right length for kids. Using Andrew Plotkin's definition of a good puzzle as being one that makes the player feel smart, these are very good puzzles indeed. There is also quite a bit of variety to the types of puzzles, including a superb racing sequence that makes for a very memorable action scene (and adds a new companion NPC: the mount, which the player must name). Wonderfully, the puzzles dramatically reduce in difficulty as the plot reaches the top of its arc, allowing for a quick denouement before the sense of victory is lost.
The story's pacing is also excellent. Its structure involves exploration of several islands, each consisting of a small number of rooms (generally 3 to 10) and each relatively self-contained. Access to each island is granted by obtaining one of ten magical pearls, and much of the functional plot revolves around obtaining these. As the range of traversable locations expands, more and more interactions between locations become possible (and necessary to progress). Although the central mystery of the plot remains a mystery until near the end, the player is rewarded with snippets of history that are revealed through exploration. These snippets contrast with the expectations set by the game's well-crafted "feelie" (an almanac of the kingdom written 50 years previously), giving a sense of deep dynamism to a world whose present is generally static. The command GO TO assists in navigation on each island, but it is not 100% reliable, suffering bugs in certain places(Spoiler - click to show) [confused by basket-o-vator, or presenting occasional malformed disambiguation questions] and outright refusing to cooperate if the destination is too nearby. This is another of Gentry's bits of subtle genius; it frees players from long sequences of navigation commands while still encouraging them to create a map of their own, in their heads if nowhere else.
One feature that I particularly liked about this work was that it includes some strategically-placed red herrings in a couple of places. These are items that seem like they could have a use somewhere, but which never actually do. Players are left to mull over these and deduce which items among them are the ones that can actually be put to use. Their presence does quite a bit to vary the pace of the story (allowing for thoughtful, slow-paced experimentation phases) and to engender the sense of a world of possibilities, even when in practice there are few options for progress. They also contribute to the satisfaction of working out the relevant solutions by sorting trash from treasure.
Although a version 2 was released to correct bugs, there are still a noticeable number of typos and a few issues with the interaction. These are minor, and they do not detract from the story. Perhaps these will be addressed in a future release, but most players will probably be more interested in seeing the sequel that is promised at the game's end.
There's something in the alchemy of this work that may particularly appeal to those who enjoy games in the old school style. It manages to retain the heart of some of the best elements of that style while adopting (and adapting) several innovations that inarguably improve the play experience. I'm not sure how well playing this would prepare someone to try older games, which might seem primitive in comparison to this work, but it certainly seems likely to encourage young players to view interactive fiction as a category in a positive light, and that aspect alone makes this a valuable contribution to the field.
This game earns five stars for me, as it has become my first suggestion whenever someone asks for a recommendation for a children's game. If you are looking to introduce a grade school child to interactive fiction, this is definitely the one to try. Even middle school aged children may enjoy it if they can get into the proper mindset -- especially if they are teamed up with younger kids and can help them think through the puzzles. The same applies to parents: It's sure to be fun if played with kids, even if it's not the kind of thing that you would choose for just yourself.
Having very much enjoyed Risorgimento Represso, I was eager to play this sequel when it was first released in 2018. It didn't manage to grab me the way that its predecessor did, so I put it aside and only got around to trying again recently. It was definitely enjoyable for someone who appreciates the old school style of play, and it is a solid sequel to a well-regarded first episode.
One of the hallmarks of the old school style -- found abundantly in the most popular games of Infocom -- is a kind of wacky comedy to interactions with the presented world. Plenty of more modern works offer the same, but this is not mere imitation. Instead, the technique survives because it is a relatively easy way to deliver entertainment to the player that is of particular value within interactive fiction because it doesn't rely on proper pacing. After all, "brevity is the soul of wit," and bite-sized jokes fit neatly between command prompts.
Although this piece frequently incorporates that type of comedy, it takes the form of more than one-off jokes. Instead, it is the framework for an extensive comedy of errors, a genuine farce growing like rich ivy over the cottage of the game's simple action plot. Jokes build on one another and escalate over time as the player, in the typical old school PC style, conducts a minor crime spree in pursuit of purely personal goals.
It should be noted that knowledge of the original is wound throughout the sequel, though not in ways that make that knowledge required to finish the game. If you happen to have played Risorgimento Represso recently, Illuminismo Iniziato will feel like an unbroken continuation -- following almost as directly as Zork II follows Zork. (In theory, quite a bit of time has passed between the two episodes, but it's not clear what the player character has been doing in the duration. You don't seem to have changed, and you begin with a few familiar items.) In the first half of the game, the setting will be Blumph, a city mentioned but never visited in the original. In the second half, the scene will change(Spoiler - click to show), and you will return to the town of Vechlee, revisiting many of the same locations and objects from the first game.
Several characters appear in both episodes, albeit in different capacities. Ninario, the centerpiece NPC of the first episode, barely appears in this one, and he is never on-stage. Instead, pride of place is given to Crystal, a talkative companion that serves up continuous "color commentary" on your actions. Much of this takes the form of reminders/exposition about events in Risorgimento, but over time this slowly morphs into observations that help to focus attention on the central thread of the plot.
Crystal is an extensively-implemented sidekick(Spoiler - click to show) who develops into a G-rated love interest. She has a ton of things to say, quite a lot of which is non-essential. This creates a life-like presence, but the drawback is that players expecting typical goal-directed expository interaction may find themselves stuck in a morass of verbiage with no end in sight. [In fact, the reason that my first attempts at playing didn't grab me is that I found myself standing in the first room talking endlessly to Crystal about seemingly inconsequential topics(Spoiler - click to show). After her insistent introduction, I assumed that speaking with her was important at that point. Perhaps a device such as her refusing further conversation by saying "We can't stand around all day." after a certain number of interactions in the same location would have served well here.] She is explicitly cast as the "talks too much" type, and one humorous innovation is that her replies for unrecognized topics often take the form of anecdotes about unrelated matters, each of which eventually ends with the acknowledgement that she didn't really hear your question.
Once one realizes that conversation with Crystal is entirely optional, the rest of the game beckons. Although the player is warned by the opening sequence that Big Things Are Afoot, the protagonist's quest begins as the simple task of picking up some dry cleaning. This task is quickly derailed, and in the "natural" course of events (i.e. initiation of the aforementioned crime spree) the protagonist and Crystal catch up to what the player already knows: The villain from the first episode is trying to widen the interdimensional rift that brought the PC to this world. Although it might not seem like this would be a problem to solve, it is(Spoiler - click to show) because, as it surprisingly turns out, the returning villian is some sort of vampire who plans to suck the life force out of students back on Earth. That this was never mentioned in the first episode -- and that this changes my earlier metaphor in a way that suggests the ivy is the only thing holding the ramshackle cottage together -- is beside the point. As with the first episode, the emphasis here is on having fun, not making dramatic sense. This becomes clear through the use of "tyromancy" (a hallmark of the series), which is the art of using cheese for divination. Tyromancy works somewhat differently in this episode, functioning as a series of dramatic cut scenes while also occasionally reprising its previous role of inciting curiosity through clairvoyance of yet-to-be-visited locations(Spoiler - click to show). Most of the cutscenes take place in locations that seem copied word-for-word from the original, which is probably useful for those who haven't played the original for some time but is less effective for those who have recently replayed Risorgimento.
The puzzle structure is a little uneven. Some solutions are quite obvious by virtue of being repeats of tropes from the first episode. Others involve repetitive use of the same objects for similar tasks. Few mysteries are present, and none of them seem exceptionally difficult to resolve, with discovery of the function of the hoop(Spoiler - click to show) and its interaction with the satchel being the most obscure. (The major clue to its use cites the zifmia and aimfiz spells from Infocom's works without mentioning what they do, which are to summon a target person to the caster's location and to send the caster to the location of a target person, respectively. This is a minor unfairness to someone not familiar with those works, but there are other clues available to make up for it.) It is worth taking particular note of how Coyne varies between playing some solutions "straight" while others have surprising and delightful twists.(Spoiler - click to show) The bit about the grappler and the gate of the estate that one plans to burgle is especially funny. These shifts in tone play well with the dual nature of the plot's "unseriously serious" core, with the balance heavily weighted in favor of light-hearted amusement.
Coding quality is improved over the original, with the "graphical" map and continously updating front page of a magical newspaper being the most apparent results. I don't recall encountering anything that seemed like a significant bug, though there are some quirks of interaction that I'm not sure were intended.(Spoiler - click to show) (For example, it is possible to solve the vault puzzle while retaining both the hoop and the satchel, which doesn't seem right given the setup.) The play experience is quite smooth, and the use of sound livens up the occasional sequence without being a functional requirement.
All in all, this work does exactly what a sequel should, namely to deliver more fun with familiar elements. It is well worth playing if you are a fan of Risorgimento Represso, and if you're not familiar with that work, consider this as an invitation to check it out.
Barry Volain, the author of Myth makes no secret that the puzzles in this work are grounded in well-known Greek and Roman mythology. In the "readme" file accompanying the game file, he even goes so far as to recommend reading Bulfinch's Mythology (which is out of copyright and available via Project Gutenberg and at this web site) as a primer. In the era of Google and Wikipedia, such preparation is probably not necessary.
Myth is austerely minimalist. Descriptions are short for both rooms and objects. Many words mentioned in the text aren't recognized by the parser. It falls victim to a few First-Timer Foibles, including laconic locations, oral offenses (though only mildly), and close-mouthed characters. Yet somehow, this work did intrigue me, and I felt compelled to play through to the end.
I wish I could say that my patience paid off. Instead, it wore thin. After making about 100 points worth of progress, I hit something of a wall. As I could find no hints other than the walkthrough, my only choice was to read it and hope I didn't get too much given away.
Of course, I saw several things I didn't want to, including some things that I had tried to do but hadn't used the right word for. Once I realized synonym sickness was one of the first-timer foibles I was up against, I was a lot less willing to sit and puzzle things out when I was stuck. Doubly-so when I realized there were areas you could only visit once in a game with an inventory limit.
It's really too bad, because there were quite a few puzzles in the "hard but fair" category that I ended up missing out on this way. In the interest of letting others avoid that, here are my own hints -- restricted to extreme guess-the-verb problems and things that are basically impossible to figure out without mind-reading:
#1 (Spoiler - click to show)The sapling (yes, it's important)(Spoiler - click to show) - you need to get it(Spoiler - click to show) - with something sharp(Spoiler - click to show) - it's for making a weapon(Spoiler - click to show) - a spear(Spoiler - click to show) - like the ancients made them without metal(Spoiler - click to show) - "sharpen sapling" is part of it(Spoiler - click to show) - they were also treated some way(Spoiler - click to show) - for hardening(Spoiler - click to show) - "put sapling in <fire source>"
#2 (Spoiler - click to show)The grapes (yes, they're important)(Spoiler - click to show) - you need them to make wine(Spoiler - click to show) - you'll know how to make wine when you find the right equipment(Spoiler - click to show) - it's not the oak bucket, it's something with purple stains(Spoiler - click to show) - put the grapes in it(Spoiler - click to show) - how can you squish them? can't get in with them or stand on them or crush them or press them(Spoiler - click to show) - "step on grapes" is the magic phrase here
#3 (Spoiler - click to show)fighting things(Spoiler - click to show) - at least one critical battle appears to be semi-randomized, save before fighting and try again if you die, if you don't die the same way every time, keep trying
Don't worry, there are multiple layers of spoiler tags in the above, so you will have to click multiple times to be completely spoiled.
The size of this game surprised me. There must be around 75 locations. You will want to create a map for this one, complete with notes of the objects found in each location. It's probably too big to fit it all in your head.
Some of the puzzle designs in this work are clever. While in some cases the cliff notes of mythological texts provide virtual step-by-step instructions, in others the author takes license with the mythology to make you think a little sideways. This work would have benefited tremendously from a more literary touch and more thorough programming.
It's unfortunate that the scoring is implemented in such a way that necessary and irreversible steps don't always award points. It's a bit unnerving, leaving you wondering whether you're on the right track or heading for a dead end. Although I believe you can get this game into an unwinnable state, it's generally safe to assume that anything that appears to make things happen is a step in the right direction -- there is little interactivity that isn't directly aimed at the conclusion.
Another note about scoring: The walkthrough seems to indicate that its author got less than the maximum points. I got more than him, but less than the max. Out of curiosity, I decompiled the source code to look for those last lousy points, but it seems that they should all be awarded if you win the game. It looks like some actions may award points if you use one verb but not its synonym, so I wouldn't worry about it if you finish with less than 300.
Maybe it's because Halloween is coming up, or maybe it's because I just read Jimmy Maher's analysis of Transylvania at The Digital Antiquarian, but when I saw the announcement on IFDB that release 7 of this game was available, I decided to give it a try.
According to the author's own description of the game's origin, it was inspired in large part by a carnival ride of the same name. My own experience with such rides is very limited, but the ones I've encountered all seem to suffer from at least two common failings. First: In their quest to create a suitably "scary" setting, the makers heap image upon image until they have far overshot the mark, resulting in a panoply more bewildering than frightening. Second: The production quality is usually so low that suspension of disbelief is impossible for anyone but very small children. Unfortunately, Ghost Train seems to reflect both of these qualities, leaving the player with sense of having run into something that had the potential to be terrifying but didn't quite pull it off -- an encounter with Cabbage Man instead of the Creature from the Black Lagoon.
Although I give this work 2 stars, it does show some promising elements. The thing that impressed most me was the author's attempt, for at least the first half of the story, to keep the setting alive and vibrant through the use of transitory events and details happening "in the background". This isn't easy to do well, and it shows a dedication to polishing the player experience that is very much to the author's credit.
However, this level of polish is not consistent, and it is most noticeably absent in some key scenes(Spoiler - click to show): as an example, the encounter with "The Demon" that opens the final act. Here, the challenge is not pulling the player's attention to the background to give the illusion of a broader world, but focusing the player's attention on the foreground and (ostensibly, at least) forcing a plot-critical choice. It's quite odd that the player can dither about for as many turns as he or she likes while the antagonist waits patiently for a keyword.
Coding quality was, in general, good enough, though there is definitely room for improvement in those cases where the author feels compelled to clumsily spell out the correct grammar to achieve certain actions. The only thing that looked like a true bug to me ended up helping instead of hurting(Spoiler - click to show), when 'x parchments' was interpreted as referring to an object named parchment due to Inform's word length limit.
This game would benefit significantly from additional attention to proofreading and editing. It is rife with errors in spelling, punctuation, capitalization, and other aspects of grammar, and it suffers from an irritating tendency to repeat the same adjective, phrasing, or information multiple times in quick succession. In some cases this is probably not desired by the author (as when an object is mentioned both in the location's description text and via default room description rules(Spoiler - click to show), e.g. the clock in the abandoned station), but in other cases it appears to be the result of simply not re-reading what was written(Spoiler - click to show) (e.g., in the opening sequence: "On silver moonlit track it races clear" followed shortly by "The steam engine 'Bluebell,' races fast and clear").
As I've said elsewhere, horror is an exceptionally difficult genre within interactive fiction, and this piece is another example in support of that claim. I would expect most players would find it about as entertaining and diverting as the carnival ride that was its namesake -- amusing enough if you're in the right mood for it. Outside of those rare occasions, its main value is in challenging the aspiring author to ponder how one might improve on the original.
On that note, I point the reader to Michael Coyne's list of First-Timer Foibles as an evaluation guide for this work. I spotted #2, #4, #8, #10(Spoiler - click to show) (most bothersome in situations where multiple locations are used when one would suffice, such as the signal booth area), #12, and #13(Spoiler - click to show) (e.g. the spelled-out instructions for certain actions, the prompt encouragements like 'Tell me what to do.' that aren't set off as being separate from normal story text).
This slightly silly (but highly enjoyable!) piece by Ryan Veeder is perhaps inspired by Rosencrantz and Guildenstern Are Dead, as its story is built around the escapades of two minor characters from his previous work, Taco Fiction.
I came across this work first, then later played Taco Fiction to compare. The two are not related in any meaningful way, so perhaps it's not really appropriate to think of Dial C for Cupcakes as a sequel. Certainly, this piece works well on a standalone basis.
The first act of the story seems almost conscientiously designed around exercising some of the latest features of Inform 7, specifically the ability to do floating point math and to switch the perspective and tense of rendered text. Once the exposition is done, however, it settles into a more typical style of interaction, in a scenario that poses the question: Just how far are you willing to go for friendship, justice, and/or frosting?
The second act is well-paced and entertaining, and it does a good job of demonstrating how careful design of NPC interaction can provide an appropriate level of satisfaction to the player without demanding too much from the author.
With a semi-realistic setting and a story that gives license to be somewhat mischievous, this is one of those pieces that probably has broad enough appeal to hold the interest of casual mainstream players -- or even those new to interactive fiction. I'll be adding it to my short list of recommended pieces for those just trying IF, and I would definitely point it out as a great seasonal piece around Halloween. While it might not quite be kid-safe (since an understanding of certain adult motivations is necessary to complete the story), it's certainly no worse than PG.
I'm not a huge fan of one-room games, but, as others have noted, this game turns what is normally an artificial limitation into a natural extension of the premise.
The start of the game is, aside from its unusually long length, a textbook example of how to provide immersion, orientation, and urgency all in one go: The initial diary entries set the humorous tone and sketch the broad outlines of the main characters' personalities, the problem to be overcome by the player is both clear and logical, and the first steps on the path to winning are almost immediately apparent.
Most importantly, this game was fun! The mounting tension had me both typing and reading faster as the game progressed, with just enough comic relief thrown in to keep me grinning.
Though I did find some bugs, they were not enough to seriously impact the playing experience. Definitely worth checking out if you've missed it so far.
Simon Deimel's Enigma starts out like an off-kilter version of "Hello, World" for Inform 7.
You start in a room frozen in time, and the whole game plays out as the protagonist's experience of a single moment oriented around one decision(Spoiler - click to show): to shoot or spare your best friend. Starting with only immediate sensations, you must build a chain of association between memories and perceptions that let you come to a realization about the truth of the situation you are in.
Exploring a memory may let you perceive things more clearly. Exploring a perception may trigger a memory. On occasion, a threshold can be reached that allows a kind of breakthrough into new conceptual spaces. Sometimes memories or perceptions will be enhanced, providing a more connected impression over which to mull, so you must return to a topic to see how new scraps of information fit into it. The text is delivered in a fast-paced, heart-hammering style that seeps into your attitude and keeps you rapidly typing until you arrive at the conclusion.
There are really only two verbs that make a difference(Spoiler - click to show): 1) "examine" and 2) "remember" or "think about". If you somehow get lost, the "hints" command will offer specific topics for introspection. This is probably not a good thing to use as a first resort, but it's helpful on a second run through.
It's really quite remarkable that Mr. Deimel has managed to create such a compelling experience out of such a small range of action, and the extent to which he has achieved this speaks to his creativity in developing and executing the concept. While he notes in the post-game INFO block that the basic concept is not new, it was new to me.
From a technical standpoint, the execution is good but could use a bit more refinement to reduce repetition of certain topics and smooth the experience. As a player, it's sometimes clear that you have hit a dead end, but it's also difficult to ascertain which topic will advance the situation without resorting to hints. Perhaps a routine that would "auto-associate" previously-explored topics that have been updated due to new information after a certain number of turns?
On the other hand, the sense of urgently and repetitively reviewing bits of experience very much conveys the mindset of the PC, and perhaps it enhances rather than detracts from the play experience overall.
From a writing standpoint, there are opportunities for improvement(Spoiler - click to show)-- for example, it's not made at all clear what drove Tim over the edge, and this leaves the whole scenario feeling a bit forced. Then again, it's not always clear in real life, either, so perhaps that's intentional.
In addition, although I liked the writing style, some additional work to smooth out the line breaks when reviewing the scene would have greatly improved the impression of a fully completed and polished work.
Overall, a good comp entry and an enjoyable short work. I look forward to more from Mr. Deimel in the future, and will be interested in exploring some of his past works.
This decade-old SpeedIF entry takes only a few minutes to complete, and is not a fully-developed work by any means. Still, it seemed worth it to put together a quick write-up, since it demonstrates a narrative device from which would-be authors can learn.
The interaction here is done in the style of a combat scene in a typical war movie, though the setting is a strange blending of fantasy and modern (or possibly sci-fi?) tropes. The action starts in media res, with you pinned down, low on ammo, and basically doomed.
What's interesting here is the way that you, the player, are not given a complete description of your environment; instead, significant new elements are injected serially over the course of several turns.
This is a clever trick, in that it takes advantage of the deeply-ingrained player's instinct to examine everything new to encourage him or her to "play along" with the developing narrative. (A similar "pointillist" style can be seen in Ashwell's Ugly Chapter, but in that case it is used more for the background than the foreground.)
While this piece is almost over before it has begun (it only lasts 10 turns or so), and there doesn't seem to be any possibility for meaningful interaction with the scene playing out, I was struck by how cinematic the sequence feels. Forcing the player to constantly reorient to the PC's situation this way seems similar to the technique of fast panning used in cinema to draw the audience "into" the action.
If you're a long-time player of IF, you might have skipped this work by Andrew Plotkin, which is typically billed as an "introductory" piece for those new to the genre. If you approach The Dreamhold with this mindset, that's almost certainly how you'll experience it, but that is not all that is offered.
Upon first completing this game many months ago, I found it to be a typical Plotkin work in the sense that it almost flippantly demonstrates the power of top-notch prose and programming to revitalize otherwise stale conventions in the genre, but I didn't see much else to recommend it. The most obvious innovation is the "tutorial voice" (well-covered elsewhere) which earns the work its status as one suitable for novices, but this held little magic to me: first, because I'm not a novice; second, because its success is questionable based on the various online reactions of actual newbies; and third, because this approach has been pushed even further since The Dreamhold was released, rendering it no longer state-of-the-art.
I gave an up-vote to Brian Campbell's IFDB review, decided I had nothing to add, and moved on... until the next day, when, still puzzling over the somewhat cryptic ending and the various loose ends, I started playing again with a walkthrough nearby for reference. Before long, I had experienced many of the hidden nooks of interaction and seen the alternate ending, which was equally cryptic and not particularly more satisfying.
Over the ensuing weeks, however, I slowly came to realize that this alternate ending is not your typical example of branching narrative structure, and that realization is what eventually drove me here to write this.
Most interactive experiences with multiple endings very explicitly present the choices relevant to shaping the outcome as choices; that is they are framed as mutually-exclusive, either-or options that can reasonably be expected to alter the outcome in a significant way. For many games, some or all of these choices are illusory, as multiple branches of interactivity will converge on the same situation again later, but generally at least a few will genuinely change the outcome.
In addition, most games that have multiple "winning" endings are quite careful to remain neutral or ambiguous in the guidance they offer about which branch to take. The signposts are up indicating the forks of the road, but there is no author influence about which direction to take. One reason for this may be that, given the amount of work required to implement the different branches within the game, the creators don't wish to do anything to discourage players from exploring them all in separate playthroughs.
In The Dreamhold, Plotkin does not follow these conventions. Challenging them seems to be one of the key experiments of this work.
With respect to determining which ending the player will see, the important branches in the action are not explicitly framed as choices for the player. Only one branch of action is even implied by the prose, and that path is framed not as one of two binary choices but as the single solution to a particular challenge. These are well-designed puzzles in the sense that they are well-hinted without the solution being immediately obvious, but, for clarity, I will term these the "obvious" paths.
Here is the part that I find fascinating: (Spoiler - click to show)The obvious path (i.e. hinted puzzle solutions) is often dependent on a particular linear mechanic, meaning the solution is driven by moving a world state in a specific direction(Spoiler - click to show). Examples that spring to mind are the puzzle about finding your way in darkness and interacting with the hot springs. In each case, however, there is a corresponding solution using the same linear mechanic, but requiring that the player push the world state in the opposite direction from that needed in the obvious path. I'll call doing so taking a "non-obvious" path.
"Non-obvious" is perhaps not strong enough of a description -- "obscured" might be better. The prose does not hint at this option in any way I detected. The only hint is found in the very nature of the underlying linear mechanic; there is no reason, in the abstract, that the mechanic should not be reversible.
On the somewhat less abstract plane of writing code, the very fact that the author has to program interactions in both directions means that any theoretically invertible game mechanic will normally only have one "interesting" (i.e. story-relevant) direction. Not so in The Dreamhold, where Mr. Plotkin has taken the trouble to create what almost amounts to a secret game accessible only to those who discover the uniquely reversible nature of the puzzle structure.
I want to be clear: I don't think I would have known anything about this "other" side of the game if it weren't for the walkthrough. I feel confident that most of the people who play through this (especially novices!) would not hit on even one of these non-obvious solutions. (Spoiler - click to show)To hit on enough of them to see the pattern, to grasp the... meta-puzzle? meta-mechanic? and work all of the alternate solutions through to the end is asking a lot. In a piece with a significant number of intentional red herrings and dead ends, offering only the slightest and most indirect indications of the existence of the alternate solutions or the fact that associated prizes have any significance (via the mural) can be fairly called unfair. But then again, asking a lot from players is par for the course in much of Mr. Plotkin's work.
So, given the lack of a direct explanation, what's it all about? (Spoiler - click to show)Having mulled over both endings at length, the overarching theme seems to be about the choice of how to use power. The PC has reached the extreme of power within his current plane of existence, and the player's actions drive him towards one of two paths. In the first, via the "obvious" path, the PC continues his attempt to dominate the entire plane. This is perhaps a more dubious endeavor than the PC believes, given that it was an error during a previous attempt that left him in the state in which you find him at the start of the game. In the second, via the "obscured" path, the PC turns that power inward and transcends to a new plane of existence -- beginning anew to start the climb all over again from the bottom. This is the path of legend as laid out in the game world, the path that is perhaps more promising for the PC and more satisfying for the player, since it lacks the malevolent and maniacal overtones of the first path. Of course, the preceding is my own interpretation; your mileage may vary.
As a final note, I think it's worth pointing out that, despite the prose's uncanny ability to make you feel "there" (as Magnus Olsson's review puts it) in terms of the game world, it seems to intentionally avoid trying to do the same thing in terms of the PC's mind. True, the PC quite deliberately begins as a blank slate, but surely some of the previous personality should be emerging as the player progresses through either of the two core collection quests? Given the arguably distasteful nature of the obvious ending, adding an ever-more-megalomaniac tinge to the PC's thoughts would provide some players the motivation to avoid it. This, coupled with a some real hinting at the existence of the second path would elevate the overall narrative structure to a true and conscious choice for the player, which I, personally, would have found tremendously more satisfying. As it is, the effect of hiding the second path so thoroughly is to render it invisible in the course of typical play, leaving the average player with seems like half of the intended experience.
Somehow, I doubt this is unplanned. It seems clear that Mr. Plotkin wants you to work for the extras offered, that this other path (and the resulting opportunity for greater insight into the story) is primarily there for elite players. Whether intended or not, hiding one path results in players being directed towards the other; The Dreamhold does not seem neutral here, even though it can be argued that such neutrality is implicit in a game about unguided exploration of an unknown environment. The counter-argument is that players cannot assume that a work of IF is open-ended -- they are at the mercy of authors to provide nudges about which of the endless possibilities of imagination are realized within the work at hand.
Perhaps Mr. Plotkin thought this all out, and perhaps this is The Dreamhold's central challenge to the player: to make the choice to look for a choice, instead of following the obvious path. If so, the unconventional design is very cleverly and subtly executed, but it's not clear to me why this poker-faced approach is superior to offering additional encouragement (delivered in his deftly minimalist style) to players to discover the alternate path.
In conclusion, this is a game well worth your time, but I do not recommend it for novices. Long-time players who have not yet experienced it should approach The Dreamhold with explicit instructions to dig deep and try to think outside the box of how IF typically works; without such preparation you are likely to miss the aspects of this work that separate it from the pack.