Yoon's talents lie strongly on the writer side, as an author of lyrical, strange, high-concept SF/F in traditional prose formats. She has a proclivity for improbable fanfic mashups. And thus, here we have a short, poetic, lachrymose and opaque piece -- a fragment, really -- about Swan Lake and Klein bottles.
As an Artshow piece, there is not a great deal to do in Swanglass except to try out commands and piece together fragments of story, until you find the thing that ends the game. The writing sometimes works and sometimes is too overwrought to take seriously (">X MOSS Soft and green and vulnerable. Like your heart, once.") If you're not vaguely familiar with the plot of Swan Lake, it'll make very little sense; even if you are, you'll get little more than glimpses.
One of the big problems with more serious IF is how to maintain tone when the player resists it by entering silly or out-of-character commands. This is more of a problem when tone-viable, useful actions aren't obvious. It's tempting, in this situation, to write in snarky dismissive responses, in the same general style as the rest of the game; this works very well for some narrative voices, and quite poorly for others. Swanglass, with its tone of highly-strung, lyrical grief, is not really appropriate for response-snark, but the snark's there regardless. The answers to >EAT SWANGLASS or >COUNT LEAVES are entertaining, but give up too much: you get the sense of the author lampooning her own style. A larger game might get away with this.
In most respects this is like a tiny, puzzleless Moonlit Tower. If you enjoyed that and want more, this will deliver a very small taste, but probably not one that will satisfy.
One of a small but important subgenre, the single-NPC conversation game. Games of this form inevitably have a romantic subtext: you are, after all, focusing intently on a single person for quite a while. ("I think I can fall in love with anyone," a friend once said, "if I spend enough time looking into their eyes. Hairdressers are a problem.") In Snowblind Aces, the subtext stops being subtext and dances around in the foreground.
During a war roughly analagous to WWI (but with more steampunk-fantasy elements), two fighter aces on opposite sides collide, crash in a snowbound waste, and must work together to survive; this is the climax of a long flirtation based on being honourable to one another in dogfights. The attraction is obvious: the question is what you do about it.
Pacian is consistently good at creating characters who are, if not particularly deep or complex, at least memorable and attractive. If IF fanfic were a thing, Pacian would be the genre's biggest ship-baiter. I've always felt that this character-design approach feels much more like a visual medium, and that of comics in particular: and the first impression that I got on examining Imelda was "man, this feels like a Phil Foglio character."
So the game succeeds at the first hurdle of romance-oriented plots: the audience should like the leads and want to see them get together. At the second requirement (there should be serious obstacles to the relationship) it's a little more shaky. As in Walker & Silhouette, the leads begin the conversation totally eager to jump into one anothers' pants, and largely remain thus throughout. This, combined with the highlighted-keyword conversation system, makes the flirtation feel like an effortless glide rather than a dogfight or a fraught landing. You have opportunities to disrupt it if you want, true, but doing so by mistake is unlikely. And because the game is so centrally focused on the romance, you're not really given any motives to do so, except to be perverse: I never felt as though Lucas' love of flying, or for his homeland, were evoked strongly enough to make for character conflict. You do not feel as though you're sacrificing a great deal by spending the rest of the war in prison. And of course, that frission is the obvious point of the game's premise -- so if it comes across weakly, that's a big problem.
Though generally strong and efficient, the writing is conspicuously less smooth than in Pacian's later works. There were a number of moments in the dialogue that broke the tone for me. The cutting banter is good at times, but less convincing at others; and the tone doesn't shift enough in response to key events in the conversation.
The game states that there are a good number of endings, but I didn't find myself wanting to seek out more than a couple. I can't help but compare the play experience to that of Galatea. There, conversation was much more of a struggle: finding enough topics to discuss in order to reach an ending can take a while. But because you have to search for them, there's a stronger feeling of things to find. After one playthrough of Snowblind Aces, however, there's a pretty strong sense that you've exhausted the great majority of topics.
But there's much to like about Snowblind Aces: a satisfying epilogue section, mostly fluid play, a distinctive and engaging premise. Like Pacian's output in general, it's overtly pulpy, but it's tasty pulp. (For me, this was one of those games that you save up for when you want to play something that you can be sure is going to be pretty good.)
TriadCity is an ambitious MUD with some unusual goals, set in a fantastic, genre-bending city.
Given the long-term nature of play, and the world's very-incomplete status, this review should be treated as more provisional than usual, and less likely to age well. Also, I am inexperienced in MUDs generally -- but, since TriadCity seems to be aiming at a fairly different audience, that shouldn't be a disqualification.
The game really, really wants you to acknowledge that it's postmodern and literary. (When you log out, it gives you Amazon referrals to all the books it's referenced.) I'll grant this, but with the caveat that these categories aren't really badges of honour; what's important is whether it's good literature.
And as a literary work, TriadCity leaves a good deal to be desired. Compared to the average work of IF, or mainstream CRPGs, there is very little active narrative; at least at lower levels, it's more of a sandbox than a quest-driven system, and more about exploration than either. Apart from a number of chatbots that seem disconnected from the world proper, NPCs are minimally reactive. There seems to be the idea that player-driven roleplay would fill a lot of the space, but at present the users are too sparse for this to be viable; and it seems likely that there is more to do at moderate-to-high levels, but leveling is quite slow.
To repeat: sloooow. At low levels, much of your time will be spent managing sleep. There are hunger and thirst counters too, but these are less obnoxious. While fatigue is a MUD convention, it adds very little to gameplay, detracts a great deal from the enjoyment of exploration, and is most annoying at the worst possible time -- that is, the very early game. There are ways to make it less awful (make a high-CON character, invest in certain magic items) but these are largely just compensation for a terrible idea.
The game has some pretty laudable ideas about how it would like to work: less gameplay focus on combat and theft (they exist, they're just hard), with a polite and supportive player culture of intelligent adults. How much this is actually achieved is another matter; the people who are on are friendly and very helpful, but too few to really constitute a culture. And there doesn't seem to be much to replace combat and theft.
The prose tends towards the genially brief; it's competent, in general, but not strong enough to constitute an attraction in its own right. NPCs receive very light characterisation and, as already mentioned, are largely non-interactive. Some of these characters are drawn from literature and folklore and oddly juxtaposed into the world -- but this is a common practice of games of this ilk, and I don't think it's inherently better literature just because they come from books rather than pop-culture.
The main immediate attraction of the game, as it stands, is exploration of the City. Most low-level experience is gained by walking around and looking at stuff. Roughly, the city is divided into three sections: the anarcho-socialist, hippy-agrarian Northwest, the morally ambiguous high-tech, artsy, technocrat-capitalist South, and the dystopian, authoritarian-capitalist Northeast. If you have detected a slight element of political bias in the above, you don't know the half of it. While TriadCity purports to be interested in subjectivity and morally complex issues, it pretty much establishes who the good guys and the bad guys are from the outset; and further, because most of its elements are versions of real-world things, it often comes across as sorting things into neat little Good/Bad/Ambiguous boxes. (Good: vegetarianism, liberation theology, wine, kaballah. Evil: guns, goths, slavery, smoking, cannibalism.) As satire, it's not enormously sophisticated. Now, I'm pretty damn close to this thing's political demographic. I enjoy a socialist-utopia fantasy as much as the next pinko. But even so, jeez, this needs to be rendered a whole lot more problematic. Possibly it gets more nuanced later on -- but there's little sign of it thus far, and I doubt too many people would be willing to stick around and find out.
The other thing about exploration is that the map is quite large and often very empty. The game touts its thousands of rooms; people from an IF background, where four high-detail rooms are usually considered superior to any number of low-detail ones, will generally react to this as a reason to run away screaming, possibly undergoing flashbacks to Time Zone. The huge map multiplies the fatigue problem, and makes it necessary to map; plenty of user-made maps exist, but they're poorly indexed. Because the world is very much under construction, it's possible that more richly-detailed rooms are intended; but it seems as if the idiom is inclined towards much, much more of the same.
Which brings me to the next point: at present, it seems as though a lot of the draw of TriadCity lies in the opportunity to contribute to the world. Characters can earn in-game roles and rewards by contributing code and worldbuilding to the game itself, or art, maps, and various categories of writing to the website that supplements it. With this in mind, I started to design a small area for the game -- but then I balked, because I felt as though I was creating something dead. The game doesn't need more areas; it needs more active narrative, more detail, more things to do in the world that already exists. And after several days of pretty intensive play, I just haven't seen any examples of how the game might do that kind of thing.
The Forgotten Girls is about child sex slavery in the developing world. This is difficult material, and the author seems to be a novice at both writing and IF design. You play a child prostitute who attempts to rescue another and escape slavery.
Narratives about atrocity have a particularly strong relationship to authenticity. First-hand accounts by victims or witnesses are highly potent, even if the narrator is unskilled; second-hand accounts, by people who have spoken with actual witnesses, still have the impact of immediacy, but require somewhat more technical skill. Third-hand accounts, fictionalised, seriously reduce the impact, and a great deal of skill is required to impart the appropriate feeling to the audience. And interactive narratives are generally harder to get right. So I can't really blame the author for too much, here, other than underestimating the difficulty of the task.
Verisimilitude is the biggest weakness of The Forgotten Girls. It's set in a specific culture (India, with Hindu and Sikh surnames) with which the author does not seem to be particularly familiar. That said, the NPCs are not convincing as humans of any culture; their dialogue is stilted and unnatural, and they're conspicuously pawns of a puzzle structure. This makes it difficult to take them seriously as monstrous abusers. While the intention here seems good -- showing abuse victims working actively to empower themselves, rather than passively awaiting rescue -- the effect kind of diminishes the seriousness of the issue. If you can easily manipulate your abusers with adventure-game tricks, the power dynamic is all wrong. (I'm reminded, again, of the slapstick ghetto scene in The Great Dictator, in which Jews outwit beer-gutted, oafish Nazi police with skillets and flower-pots.) Depicting abused women as active agents in their own rescue has its virtues, but depicting victims as more resourceful than abusers makes the entire scenario nonsensical.
The problem's compounded because this world-illogic-for-the-sake-of-puzzles isn't just about NPC behaviour; the physical world works like this as well. A wooden cupboard can be set alight with matches. An ordinary car can smash through a brick wall from a dead start. A girl is able to walk (let alone flee) immediately after a vicious and prolonged beating with an iron rod. This could have been glossed over if the characters were less mechanical, and fixing it wouldn't compensate for the mechanical characters; but it does make the problem worse. Along similar lines, room descriptions are often laid out as ungainly inventory listings, and synonyms and close-but-wrong attempts are rarely implemented; you're never allowed to forget the artifice of your environment. (And from a gameplay perspective, read-author's-mind is a huge problem. There is, at least, a pretty good hints menu.)
It's worth comparing this to another game about real-world atrocity, Gigantomania. While suffering from similar problems (counternarrative gameplay elements; a general feeling of sophomore inauthenticity), Gigantomania made a creditable attempt to represent life under Stalin through modes of interaction, to explain experience through doing, to bring home a point by exploring how a system works. The Forgotten Girls doesn't really do anything like this; it's really just the statement "sex slavery in the developing world exists." That's not a pointless statement, for all that it makes for a less interesting work. But I think there's little point in fictionalising that statement if the fiction has less force than the bare facts.
Heavily reliant on cult JPRG Suidoken II, this is a minigame about head-to-head cooking contests. The only possible interaction is cooking, which is a two-step process; you pick a base food from a list, then modify it with seasonings from a second list. The modification is more conceptual than literal; mayonnaise turns into cream if you combine it with a quiche, or transforms fried chicken into french fries. Add salt to a sandwich, and it becomes peanut butter and jelly. There's no way of getting any more information about these ingredients -- such as the ones with Japanese names -- or predicting what effect a seasoning will have, short of experience. Other than this, play consists largely of pressing any key over and over to see what happens.
The NPCs -- your cook-off opponent, and the judging panel -- are drawn from Suidoken II, which you are assumed to be familiar with; each is described with only a brief phrase that makes little sense out-of-context. Sometimes there's a hint about the sort of food they prefer, but not enough to formulate anything like a strategy with. Still, random selections will usually be enough for victory. Winning contests unlocks more base recipes, but other than this there appears to be no progress; win or lose, you still go around and play another contest.
The writing has a sort of manic anime feel about it, but is generally not really enough for the job. It doesn't provide either enough information or enough interest. It does not seem designed with a prose format in mind; rather, it's a little as if someone stripped out the text from a medium more reliant on visuals. The effect is a bit like a radio broadcast of a gymnastics contest; sure, you get the general idea of what's going on, but it's clear that you're missing out on the most crucial element.
As a coding exercise, it might be considered a small success; the presentation is smooth enough. As game design, it leaves something to be desired.
A game that feels very much like an exercise in learning the multimedia features of Glulx, and using them in puzzle-critical ways. The basic conceit is that, eyes dilated and without your glasses, you must rely on your next-generation smartphone to deal with the world.
Your ultimate objective is to reach your wedding rehearsal, and the tone is generally light-hearted and wacky; but the TMBG song on which the game is based is about trying to screw up the courage to end a loveless relationship, and there are enough hints of correspondence between the two early on in the game to give a suspicion that all is not necessarily well.
The core of the game is a punishing puzzle highly similar to (Spoiler - click to show)the classic boardgame RoboRally, in which players control robots racing through a factory full of laser beams, pits and conveyor belts. Most of the entertainment value comes about because commands are pre-programmed in blocks of five, which has unpredictable and messy results when robots interfere with one another. Narrow Your Eyes' version is in some respects simpler; there is a single robot, control of which alternates between you and an evil scientist. Instead of relying on drawing the right cards, you can enter any commands you like. (To work this out, you absolutely need to go straight to the hints.)
On the other hand, the commands are entered by entering two-digit numbers, and you have to figure them by trial and error; firing the robot's laser is not automatic; and the board is unusually complex for a RoboRally map, being entirely covered in conveyor belts.
There are two big appeals of RoboRally: the spatial-logic challenge of setting up a good turn sequence, and the entertaining chaos when sequences get broken. Narrow Your Eyes places the emphasis heavily on the former -- which may appeal to people who prefer more pure logic puzzles, but which I find less interesting.
What's lethal, though, is the combination of less-than-ideal graphics and the trial-and-error commands. Each turn, the robot alternately moves under its own power and is moved by the conveyors; sounds are included to help distinguish between them, but the timing of these is Not Right somehow, and I found the effect confusing. The images are not animated, but simply disappear and reappear in their new location -- which is considerably more difficult to follow than visuals of a robot actually twisting and jiving. And in order to figure out commands, you'll need to take notes, and while taking notes you take your eyes off the screen and lose track of the sequence. Also, the robot kills you quite a lot, so heavy UNDO is required.
It's possible that this represents intentional design, and the game is aimed at people who really enjoy tracking and processing many pieces of hard-to-track, logically tidy information in quick sequence.
So this struck me as a successful coding exercise but an intensely frustrating user experience, and I cannot report on the ending.
Citing Ray Bradbury as a primary influence, this feels very much like a SF short story from the 50s or 60s, the sort of SF you could make a movie about without any need for a special effects budget. The protagonist, a child, lives with his parents on an island across the bay from Astro City. Earth is at war with Mars, and the protagonist plays make-believe games based on this distant conflict. But then a rocket-man washes up on the shore, and reality and fantasy intermingle. (There is a general feeling of WW2 fiction here.)
Though capable overall, both the writing and the overall design have some rough patches. The prose feels a little first-draftish in places. Most of the gameplay is quite narrowly focused -- probably too much so, in the make-believe sequence -- but there are a couple of points where the solution is a little counterintuitive. The denouement is rather heavily foreshadowed, the protagonist is perhaps a little bit too much of a Disney innocent. But there are many gleaming moments here, little bursts of rich, world-grounded imagery that make this feel less like a fantastic piece and more like a childhood memoir.
As science fiction IF goes, it's uncommonly good in that it has its feet planted on the ground, it grasps and is concerned about the flight-of-fancy aspect of the genre.
A feckless loser, likeable but kind of awful, has his life even further ruined by the intrusion of an SF/F trope. He joins up with a group of yet-more-awful guys and an cute girl or two; together they navigate a grody, nocturnal Americana fever-dream, overcome obstacles through randomised combat, and squabble interminably; a extensive range of graphics and atmospheric music rounds the experience out. Scatology, sass and geekery abound. If you've enjoyed previous Robb Sherwin games, then, this is a safe bet.
In Cryptozookeeper the subject is aliens and cryptids; the result is something that feels like The X-Files cross-bred with Pokemon, with an all-slacker cast. A lot of things don't make sense, and the general feeling is of a partial hallucination; wisecracking is juxtaposed with graphic horror, the plot develops tangled corners that you don't need to keep track of, and gameplay alternates between drifting easily along while expostulation happens, and being stuck in a frustrating corner with a skewy puzzle just beyond your grasp. And it's always night. And characters point out, repeatedly, the many aspects of the story that make no sense. It's a very particular kind of surreal.
At Cryptozookeeper's heart is a mini-game in which you create cryptids by combining DNA that you've collected, then battle them in an underground animal-fighting ring, in order to level them up to face a final challenge. The design is such that collecting all the DNA and discovering all the cryptids is optional. Combat is old-schoolish and random, but handled automatically and quickly; your main decisions are about gaining stats. On the other hand, you'll do a very great deal of it, it involves few strategic decisions, and it's not very clear how much is enough; players who dislike grinding may grit their teeth.
Thorough implementation is often talked about as a sine qua non of IF authorship, but it comes at a high cost. Sherwin puts as much effort, care and love into his games as anybody making IF, and does extensive testing; but robust implementation comes fairly low on his list. (Save often.) Among his higher priorities, it seems, is long-arc story. Cryptozookeeper is sometimes buggy or cumbersome, and often sparse and linear -- but it's also large and brim-full of content.
For much of the game you have three or four NPCs in tow, but you can talk to them rarely and on very limited topics. Despite this, they feel more developed than many NPCs with ten times their conversation topics -- Robb writes very well, the images help, and you have time to get to know them. (Too, you're constantly sniping at one another; the silences feel, appropriately, like irate sulking.)
Like most Sherwin games, this is basically about how the world is dark and horrible but even the most abject can be redeemed; it manages the difficult task of making both the darkness and the light seem genuine.