|
Adapted from a SpringThing24 Review
Played: 4/3/24
Playtime: 1hr, 14/16 clues, right cause of death, wrong drug
If I part the opaque mists of time, push back untold eons to my reentry to this hobby, reaching, reaching nearly two entire trips around the sun to the barely discernible epoch of Fall 2022… this authorspace was virgin snow to me. Every game came as single line on a blank slate - no context of author idiosyncrasies, platform biases, tell-tale prose and fascinations. Just the raw work itself. Ah, such a simple, untarnished time and state for a reviewer full of unearned confidence and bluster.
An interminable 18 months later finds the withered, corrupted husk before you: penetrating brilliance and revelatory insights dimmed and drowned beneath a cacophony of prior art and superficial connections. You require evidence of my tragic artistic collapse? Not even past the cover page of this game, the eureka that pushed all other thoughts from my head was “Oooh! Oooh! I know this!” For a mad minute, I thought it could even be a Twine reimplementation of that former parser effort.
As final, damning evidence of my intellectual bankruptcy let me now proceed to review this work, liberally comparing it to its predecessor.
IT IS BETTER IN EVERY WAY.
The Twine platform is used to great effect in this work - its game-pane setup, liberal use of mood-setting graphics, case file/interview subscreens, and even text organization all combine to immediately cast the player in role of no-nonsense, just-the-facts-ma’am detective. The Twine command paradigm of selecting highlighted links on the page provide a superior framework where links only allow actions that support the investigation, as opposed to a parser’s need to accommodate any number of mimesis-breaking player fumblings.
The mystery is very capably put together - enough red herrings and dead ends to make searching out truths fun and challenging, not too many to drown the player. Many different items and leads that branch and intersect in interesting ways. Even the flourishes like timed text are used to advantage that could easily be intrusive.
The author uses all these tools to push the player into the role of Forensic Detective, then opens the door on clinical test results, chemical names and lateral thinking. My biggest beef with the previous game was that it didn’t sufficiently show its stripes, and let the player muck about with parser puzzle toys instead. It wanted Quincy, but let you be Clouseau. This time, the player is aligned from the jump - get that Keystone Cops nonsense outta here, pros are at work! The work is better focused, and better showcases its strengths, for it.
I really had fun with this one. In the end, I drew satisfaction from legitimate deduction and clue connection to determine cause of death. I failed however to identify the chemical source of the problem. I did miss two clues somewhere, perhaps those held the final piece I needed. OR PERHAPS NOT. Because the first thing I did after informed of my failure was Google search some chemicals, and ON THE FIRST RESULTS PAGE, THE MYSTERY WAS SOLVED.
I COULDA USED GOOGLE TO HELP SOLVE THE MYSTERY ALL ALONG! God, I love that so much. This thing made me a detective and with just one more bit of extra-game lateral thinking I might have closed the case. LIKE A REAL DETECTIVE. I can’t remember a failure so satisfying, and the credit goes to the real-world, clinical vibe the game created through graphic layout, mystery construction and tight UI control.
I kinda can’t wait for the next one in the series. You better BELIEVE I will be testing if it measures up to this one. [spoiler aside to author - that said, there is a discernible pattern in these two works that casts a shadow… beware!]
Mystery, Inc: Velma
Vibe: Forensic Detective
Polish: Smooth
Gimme the Wheel! : If it were my project, only one tweak: the body’s apparent sex is left unrevealed when examined, leading to a strange few minutes of disconnect when finding female name references around the apartment. Yes, it can be deduced but doesn’t feel like that detail should need to be.