Adapted from an IFCOMP26 Review
The latest in DiBianca’s ouvre’ is recognizably of a piece with his signature style. An ascii-graphics map, peppy command space, tight descriptions, all wrapping a challenging and engaging puzzle. Here, you are attempting to complete a scavenger hunt before the haunted mansion site turns on you.
As the title clearly conveys, you are on a timer. Naturally, everything you do takes time. In additions to multiple possible objects to satisfy the search list, you also encounter numerous time-reducing objects that will trim your execution times, at cost of time to secure them. It is a deep optimization puzzle of where and how to expend your time to try and get all 10 objects. Boy did I embrace the hell out of it.
For the longest time there lingered, on my desktop, a color-coded spreadsheet annotating each location with objects available, time costs, remote objects that can REDUCE time costs, and scavenger hunt objectives. Sortable and cross-linked. Is this document redundant to an inherent RECALL command that provides some of that data? Not really, it proved essential to my completion. I threw myself into the problem - exploring every place I could find, documenting everything, then immersing myself in the data, digesting the possibilities.
Does it sound like I was Engaged? More like, sounds like I was OBSESSED. Which, for purposes of scoring we’ll just alias to Engaged. The time I was playing just FLEW by. It culminated in a 9/10 object run, where I escaped at the last possible moment: 11:59. That was thrilling! SO thrilling, that despite having a half hour left on my review clock, I decided to wrap the session, write the review, and save the final run for a triumphant post-COMP reward.
[two days later]
As is my wont, my COMP routine is to play a game, compose a review a day or so later, then sit with it for a while to make sure it reflects my thoughts to my satisfaction. (And to give the typo gnomes an opportunity to do their nocturnal work.) A funny thing happened in that maturing span. The feverish spell it cast on me receded. I started to question the impulse to make that garish spreadsheet that still hovered on my desktop. It started to feel like the work of a crazy person, silently and sternly judging its author harshly. My triumphant 11:59 finish still left a warm glow, but the extreme effort felt almost… embarrassing? No, not that, I would need a LOT more sense of shame for that. Perhaps just eliciting a vague sense of unease about my life choices.
I also started to consider how much MORE effort that 100% finish was going to demand. What kind of MENTAL SPIRALING would be required by that intrepid player. And then I considered the undeniable RUSH of finishing at exactly 11:59. Could the effort/reward ratio POSSIBLY deliver more than I had already received? I mean, it is a DiBianca jam, certainly possible it could. But.. what if it didn’t? Am I not better off quietly disposing of the evidence of my mania, and letting that last run be the victorious ringing bell of my experience?
Are we not all, all the time, weighing the Known against the Potential? And does not the Potential, when realized, so frequently disappoint? ESPECIALLY against particularly triumphant Knowns? Can I somehow sublimate my deeply trivial, all-consuming obsessions into a semblance of Truth by throwing syllables and Capital Letters at them?
InDubiTably!
Ah! Fortified with Universal Truth, and with lingering suspicion that the pendulum could yet swing back the other direction, I regretfully conclude that its Seamless, Engaging impact was undeniable, magnificently rewarding, but also seeding its own ephemerality.
Played: 9/2/26
Playtime: 50% @20m; countless mapping runs; 60% @ 1hr; 90% (11:59) @1.5hr
Artistic/Technical ratings: Engaging/Seamless
Would Play After Comp?: I thought so, but turns out no? Gonna enjoy what I got.
Artistic scale: Bouncy, Mechanical, Sparks of Joy, Engaging, Transcendent
Technical scale: Unplayable, Intrusive, Notable (Bugginess), Mostly Seamless, Seamless