Reviews by Andrew Schultz

The Belinsky Conundrum is a Facebook Messenger app about a top-secret mission to take out a spy who's managed to avoid his kids being chipped. It's a compelling premise, and it's extra-cool that it's on a new platform, and you can do this sort of thing on Facebook, and you (presumably) won't be suckered into in-app purchases along the way to get a better ending. Which gives it a leg up on a lot of games on Facebook.

But unfortunately there wasn't enough of a conundrum to really sink my teeth into. The game follows a pattern of asking for 3 different options, some of which feel very small-talky indeed and maybe did not give all the variety I hoped for, even though they gave a laugh. Given the tone of responese, this would be okay for a comedic slice of life game, but it feels out of proportion in something more exciting–perhaps the author's strength is more with slice of life games. An example is below–I'm not sure of the differences, and perhaps it would be better to have no choice at all, or "nod impressively / stay still ". I think we have some latitude for false choices in choice-based games, but unfortunately here it seemed to contrast with the gravity of the situation. One early example is below:

(Spoiler - click to show)"The national security of the United States is at stake," says Admiral Houfy.

Sweet! / That's messed up / Oh my god

Still, I managed to put up with my boss's orders to succeed or else, and make it to Norway, where I bought a car and gun "off the grid," which was quite fun. Apparently I owned a wind farm, or could pretend to own one, to make the purchases plausible. The only real puzzle I saw was finding the name of the gun dealer, and I chose the most oddly spelled one, because it was foreign, and it worked. I felt satisfied, and I'd have liked more puzzles like that, regardless of how bad they'd kill you off it you messed up. I was also curious who it was that the government had tracking me to make sure I did my job. TBC brings it up on the NorAir flight I took. There are suspects that are so obvious they couldn't be the one and suspects that obviously could be the one.

TBC feels very high-stakes at first, but it seems the only chance to go wrong was at the end, where you had a choice to try a hit on Belinsky or not. I did not and was told to stand down shortly after. This is a point where being able to undo things would've been appreciated, as I was hoping to read about the moral implications or possibilities. But it took a bit too long to get there. That was the first time. Fortunately, TBC was short enough that it wasn't hard to play again. This time, I eyeballed the correct passenger (the old lady) and went to Iceland where I found an underground maze where I met an old contact. Then I burst into the Belinsky house. I had a long, winding adventure with Belinky, escaping both world and US governments as well as some philosophical discussions about safety vs control/surveillance. They were a bit didactic, but they helped me put things together. There was a dramatic end, and yet I still can't help feeling so many of the dialogues and choices were superfluous and missed out on a chance to develop the core story. There was probably more there than what came before, but people might miss it, so I'd like to at least have that for reference..

I think TBC buries the bulk of its good stuff, and not just because it was on Facebook Messenger instead of a more traditional, accessible and lightweight format. But there is good stuff. I mean, I don't want to find out all the surprises at once, but it seemed a bit back-loaded and never quite built to the climax it should or could have had, because after being hit up front with many dialogue choices that didn't seem to matter, I was never really able to get back into a strategic frame of mind. Though without too many spoilers, I think it's satisfying Roosk gets pegged as dislikable in the end. And the chase where you actually try to rescue Belinsky was, for me, probably the best part of the game. So you probably won't want to miss it.

It took a while to update Java so that it would run Wabewalker, and it was time well spent. (Note: download Java 17--you may wish to uninstall your curremt Java version first, too.) It’s a game that’s meant to be confusing at first, I think, but that's not just for its own sake, and certainly not due to the custom parser, which I found worked well. Finding a clue what to do (beyond "explore and take stuff") is a great introduction, and it’s quite possible you’ll solve a puzzle by accident and then realize what’s going on. And that all feels fair.

The oversimplified plot: keep getting killed, sending you to another person’s life, until you organize things right. You become three people total, in three different worlds. If you’re not careful, you get killed for good. At one point, I was quite legitimately worried there was an endless loop, and I very much felt the tension when I was trapped between two worlds, unable to open the third, because I’d forgotten about a door and instead looked for something else that changed game states. That something else was behind the door–I hadn’t taken careful enough notes. If this sounds vague, I want to keep it that way, to avoid spoilers.

Because this game has ambition. It forces you to say “Huh?! What?” and banks on you being able to sort that out. What are the panels with three lights for? How do they work? How do you change lights? And so forth. There’s a certain frustration when you’ve set more lights than you need to open something, then fewer, and you wonder what the heck you have to do. Because there are only so many possibilities, though there seem to be far more when you start.

After I figured what the puzzles were about, the rest seemed like scratchwork, and, well, it wasn’t. There were other moments I hoped I wouldn’t be getting killed like before. I thought I calculated it. But I was still scared. I’d spent all this time scratching out figures to possess three people’s consciousnesses properly, not really knowing who they were, and it had better pay off!

Other than these three people, though, there aren’t many you deal with. Someone invites you in to hypnotize you, for a short segue that lets you see beyond one area where you get killed. This confused me a bit since my host said “No, that worked wrong,” and I still got a scroll. But given I was a bit careless about the narrative, I found it trippy that somehow A might’ve killed B might’ve killed C might’ve killed A. One of them killed the other, though. There’s also a phone call over a landline, which I found amusing, because it plays on a few text adventure tropes. It wasn’t hilarous, because that didn’t fit the game’s tone, but it was a well-paced joke.

So overall, I was pleased. What could’ve been busy work felt like a legitimate adventure. I can’t rigorously decide how true to Buddhism it is, but I do like how things work–there are so many orders to solve the puzzle in, and you may loop around a while before getting it, and quite possibly it’s more rewarding if you loop around more.

As for issues? The end cheesed me off a bit once I knew what to do. All those similar commands to type felt anticlimactic, and between bad memories of Ultima IV shrines (meditating three times in a row, I would go do something trivial and notice my response time had timed out–plus, these games have two mantras in common) and being unable to use an up-arrow, I was ready to get on with things and not particularly close to inner peace. In short, the ending puzzles were what I feared the beginning would be. In fact, one item really seemed to cue that. I saw and thought “welp, I hope they’re not instructions for later.” This all contrasts with how solid the parser is in general and how economical the “open the locked door” puzzles are and how they weave together. So be prepared for a grind at the end, but it shouldn’t outweigh the rest of the game.

The custom parser overall worked very well, though I wish H (hints) would mention the MEMORY command. The author may have updated it by now--I suspect it is an oversight, since they did the hard work of tracking everything you have learned with MEMORY.

This review was moved from the authors' forum, where the author helpfully pointed out some oversights: most notably, hints are written into the game text, and I missed some places to mine credits. But I want it up here so people will have an idea how to approach a worthwhile game that may feel intimidating. The TLDR is, even if you miss some of its neat features, it's still a smooth, rewarding effort.

Cygnet Committee is a big download at 140MB, and I admit I was intimidated by the size and 2-hour playtime suggestion, which was accurate, but I’m glad I pushed through with it in the end. The concept is intriguing: infiltrate a cult that worships Joan of Arc’s AI and destroy it. There’s a good deal of backstory here, which is shown as you get further into the base, where you reach save-points that give you small videos. You learn why Joan of Arc is so appealing and why she rose to prominence. You have a map at the game’s main screen, which is useful to show you how far you’ve gotten. It’s tidy and well-organized and purposeful.

The map’s not intimidatingly big, and the main mechanic is this: you move your mouse to detect sounds. There are four ranges on the screen, and one of them gives the right sound, and the others give the wrong one. Sometimes it’s no sound that’s right, as when you’re crossing a minefield or rotted bridge, and sometimes you want a sound, when you’re fighting a drone or guiding your helicopter. Other times, you’ll start with the same sound, but it changes at the end–punching in a keycode, for instance, or listening for a robot patarol. And in some cases, the same sound in all four sectors means you probably need to solve a puzzle so things quiet down.

This is something that isn’t nearly as dramatic with text. Any sort of typing would drag things out. It’s a neat streamlined way to give you a feel for the game and the mechanics without having instructions, which is handy, because having to remember controls and such would get in the way of the big-picture instructions as you weave your way through the base. Overall, the tension worked well, though I’m not sure if it was fatigue or anticipation that had me anxious at the end. I do think the timed puzzles were ultimately a good idea, though I wish the game had started with 20-second intervals to make 7 successive moves instead of starting at 15 and moving up. I was immersed enough that, on the one-minute puzzle, I faced a drone, and its voice made me think “Ah, I’m surrounded? Not really! But I bet I would’ve been, if I’d tried to make a break for (that one protected area.)” Then when I figured how I goofed, I was a bit scared to do the puzzle. But I had no choice. Similarly I liked the ending–it felt appropriately dramatic. I won in plenty of time. I realized, looking back, the game had more of a sense of humor than I gave it credit for.

So in the big picture, it’s a very strong game. I ran into a few pitfalls here and there, and looking at the long list below, they don’t cancel out the positives above, but they may help people push through bits that seem rough.

In one place, I thought I made a mistake, but a trap was unavoidable, and I took the wrong branch to find healing the first time. The purpose of the trap was to direct you to (Spoiler - click to show)a small cabin off to the side with information and supplies, and once I realized that, it was okay–but since I hadn’t saved in a while, I panicked.

On winning, I was notified I could only replay hard mode if I got 500 credits, which is a lot, because random combats give you 14 or so credits for each win, and while you find some credits, it’s just way too fun to disable cameras or electric fields or whatever so you can skip over the sound-tracking parts. It was a steady enough process–I never expected to mess up, and I was sort of curious what happened if I did, but too often I was a bit worried because I forgot when I’d last saved. Instead of hard mode, I’d have preferred some notes on how to get to the final map area, (Spoiler - click to show)past the waterfall and on top of a cliff, where the sound barriers were the same in all four areas. Or maybe how to fight drones more quickly, so it took less time to unlock hard mode. I couldn’t seem to get the in-game temporary for-x-moves hints (also a neat idea) too work. (I’d also like the option to skip videos–especially the ending one once you’ve escaped–the second time through. I mean, the second time you see them in-game, you can skip, but I’m just impatient like that. It’s a case of, get me to the next good stuff.)

Still I hope to come back and see about all the possible deaths and places I missed and gadgets I couldn’t quite afford–gadgets that let you bypass sound-puzzles you’ve mastered. I admit a walkthrough would help motivate me to revisit the game, with all the others I want to see in IFComp. And I think, sadly, the file size and potential system requirements will leave Cygnet Committee underplayed and undervoted-on in the comp. Which is too bad. On finishing this, I was reminded I did not finish Dr. Sourpuss, the author’s first offering, and I probably proceeded too cautiously with it. I started that way as well with Cygnet Committee, but once I jumped in, time flew–and I still got done in under just two hours.