Hand of God

NOTE: The first part of this review was written about an earlier version of the game, which had a game-ending bug; read on for an addendum written after I finished the updated version.

Oof, I have to say I did not get on with Hand of God. Partially this is because I couldn’t figure out how to get to the revolt of robot fanatics promised by the blurb, and instead got stuck in the white-collar drudgery also promised by the blurb. And partially this is because I noticed an ugly detail about the characterization I couldn’t unsee, and it killed my willingness to push past the bug that was blocking my progress.

First things first – this is a Twine game, in default style though with some animated text and changes to the font colors to denote when different people are speaking. The player character is a fortysomething husband and father who’s got a government job helping develop a robot interpreter, and those two strands – family life and robot stuff – are set up to bear equal weight, at least in the portions of the game I got to. You start out at home, going through your weekday morning routine and interacting with your family; then drive to work, and after a nose around the environs and learning more about the project, check in with your coworkers.

The first section is OK as far as it goes. The family interactions are pleasant and low-key, and if they seem a bit schematic (just about the first thing we learn about the player character’s wife is that she’s a GenXer, and the daughter doesn’t have much personality besides liking an MMORPG), well, there’s nothing wrong with starting simple. There are a few implementation niggles – there isn’t any branching but you can choose which order to do some necessary tasks before getting ready for work, and they’re repeatable, meaning you can eat infinite pop-tarts. And the commuting sequence managed to confuse me since I wasn’t sure whether I was meant to be continuing on the highway or taking the first exit in order to get to work.

The writing throughout is a bit weak, with fairly unimaginative prose and a scattering of typos. The author also tends to really overuse certain words. Like, here’s a paragraph from a dream sequence that comes at the beginning of the game:

"The winds blow against your pale, fleshy body, scratching you thoughout (sic) your body. You sweat like a pig as the sun pulses upon your body. It will not be long until all of the water leaves your body and you die of dehydration."

Reading that many instances of “body” is actually kind of unsettling!

Where things really went wrong, though, is at the office. Most immediately, this is where I reached the impasse I described above – after I parked, checked out the other buildings on the campus, walked into the high-security area to check out the robot (whose name and function appear to be setting up a Tower of Babel allusion), then entered my office to greet my boss and coworkers, I got stuck in a similar cycle as at home, except this time I was unable to get a new option to appear no matter how many times I went to the water cooler or checked in with my cube-mate. From a quick look at the html source, there’s a lot more story to come, but it does seem like there’s a bug that blocks the way forward.

More significant than any bug, however, was an ugly realization I made after meeting all my coworkers. Here’s the receptionist, Julia:

"A brown skinned woman in her late twenties, her casual hoop earrings and red headband hide the wit of someone able to obtain an $80,000 job doing nothing."

Here’s Emily, a fellow coder:

"A woman of Chinese descent in a bright purple suit, her smugness radiates wherever she goes. You KNOW that she is the one to blame for your food poisoning. She will handle you (sic) being better than her at your jobs."

Here’s our boss:

"A dark skinned man in his 50s, his imposing 165 cm looks upon you from his shrub enshrined desk…. This man’s harsh demands will never cease."

And just by way of contrast, meet the aforementioned cube-mate:

"A bright eyed young man, his blue eyes light up the room… Andrew is a nice kid."

So to recap – we have a lazy, flashy-dressing black woman who’s living large in a government sinecure; a stuck-up, msg-dosing Chinese-American; a cruel, physically-imposing black man; and a nice friendly blue-eyed kid. I’m sure Hand of God is not intending to be racist, but – excuse my French – holy hell this is some racist bullshit right here. I think the problem is that, much like with the player character’s family, the author is relying on stereotypes to come up with the cast of characters, and possibly had the admirable impulse to make the game more representative by including some people of color. But the problem with doing that unreflectingly is that you can wind up regurgitating some really really ugly caricatures that draw on boogeymen first conjured up by reactionaries and then filtered into pop culture – and racist tokenizing is way worse than no representation at all.

Anyway, like I said this really killed my will to continue; hopefully there’ll be an update to fix the bug and the bad racial dynamics, since I like a good story about robot zealots (admittedly, there’s Battlestar Galactica and then I’m not sure what the second example would be). But for now, I’m taking a pass.

ADDENDUM: Since I wrote the above, Hand of God has seen an update that fixes the aforementioned game-stopping bug, so I went back and finished it. The story does work a bit better now that I’ve seen all of it – in particular, it looks like some of the main character’s negative traits are intentional, and are meant to provide a bit of a character arc (I didn’t mention it in my review, but he appears to have some anger issues and is overly nostalgic for his youth). The weird racial stuff remains as it was, however, including a “joke” about how one time the translator robot malfunctioned and ran around yelling racist slurs – and with the added twist that the enemy hacker the main character thinks is behind the robot rebellion 1) is actually innocent, so the rebellion is unexplained as far as I could tell; and 2) is a Palestinian Arab who’s assassinated in what’s meant to be a feel-good epilogue, completing the perfect record of unpleasant characterization and negative outcomes for POC in this story.

Speaking of the story and the rebellion, I found this rather unsatisfying too. The robots suddenly start killing or capturing humans while spouting Gnostic buzzwords, but their plot (to annihilate humanity via nuclear war) doesn’t seem to square with Gnosticism as far as I understand it. And then the stratagem the main character uses to foil their scheme is about the oldest, hoariest chestnut there is (Spoiler - click to show)(saying a paradox aloud, at which point smoke starts coming out of all the robots’ ears). Maybe the focus is meant to be more on the family dynamics, because that’s where the denouement wraps up, but even there, the final moral – “Your loved ones don’t have to be a shackle to misery. They can be the keys to enjoying life together” – feels oddly negative, and runs up against the overall flatness of the characters.

The choice mechanics of the second half of the game also felt a bit clumsy to me, since the story requires you to be captured – escaping the robots leads to unsatisfying bad ends, meaning seeing the full story play out requires making decisions that don’t make sense for a character who’d presumably be very focused on getting away from the killbots. There were no further bugs, at least!

This game is written in Twine, and features you, a programmer, working on a secret government project when things go wrong.

It uses colored text for emphasis. The structure for much of the game is a small section where you pick 3 options in any order, then moving on, sometimes with a branch when moving on. The branches are big, with no coming back together in the end (essentially a 'time cave').

The overall storyline isn't bad, involving a kind of robot apocalypse.

There are several errors. One of the largest is that in the Twine code, many of the sections check the 'history:' feature of twine to see if you've visited a passage, but types the names of the passages wrong, so you never get to proceed unless you load it into twinery and proceed by yourself.

This, connected with the semi-frequent typos, leads me to believe that the other never played through the finished game or had testers try it. Having someone play through your game from end to finish really helps when submitting to a competition!

I agree with the other reviewer that this game's protagonist has problematic views. They're part of an overall bigger issue, which is that he is more or less a jerk. I've noticed when looking at choice-based games that while many people like being a 'bad guy', very few people like being a jerk.

-Polish: The game has gamebreaking bugs.
-Descriptiveness: The game's text was most interesting when describing the robots, but was otherwise fairly vague.
-Interactivity: The bugs threw a wrench in things.
-Emotional impact: I felt disconnected from the protagonist.
-Would I play again? Not until it's polished a bit.

I would definitel bump up the rating if the major bugs were resolved!

This game reminded me a lot of choose-your-own-adventures mixed with Office Space mixed with a Heinlein book. It was a fun play, even though there were some typos and small proof-editing things that could have improved the reading. It's ironic, because I also ended up using Google to look up some words I had seen before but never read anywhere (demiurge, monad, cast mares, aeon, gynoid) in this game (so I am happy to walk away with some new words).

The story revolves around a programmer working a corporate job who lives out an existence (what David Foster Wallace called the "grind of day-to-day living"). I could relate to the character's desire for adventure. I liked the overall theme and enjoyed the different characters that were introduced. I most enjoyed the different paths and was intrigued by exploring how the story would play out. Even after I got the optimal ending, I kept playing to explore every option. I used to do this with CYOA books when I was a kid. It left me satisfied learning about all the possibilities in this fictional universe that was created. I would recommend playing it just to get a sense of what it must be like for people with jobs who feel trapped in grueling jobs working for companies that are too demanding on their personal lives. I know it is a work-in-progress, so I recommend some more play testing from friends to edit the text-- or running the text through a spellchecker/proofreading tool grammarly.

Unlike some other IF experiences, I didn't quit in frustration. It was a pleasant escape. I'm glad I played it.