Adapted from an IFCOMP23 Review
James A. Michener (JAM! called by no one. UNTIL NOW.) was a singular author, wasn’t he? His most famous, well-received works were meticulously researched historical tapestries. They were fiction, or maybe fictionalized narratives where he portrayed broad sweeps of history through created characters (often generationally related). He crafted historical mosaics composed of individual, detailed shards of fiction. Characters were sketched only roughly, kind of subordinate to the march of time but just present enough to shade events in human terms. Michener was pretty good at it. He also was SPOT on about the American Electoral College, but I digress.
Anyway, Michener has nothing to do with anything. Shanidar is a tale that… no of course he is relevant. Shanidar is strongly Michener-esque. Michenery? JAMmy! Those JAMmy synapses closed in my brain early and stayed with me through the entire piece. A work could do far worse than to evoke that comparison!
Before we really invoke JAM though, let’s start with presentation, because it is noteworthy. The work is choice-select, with each choice pulling up a window of text, overlaid on a (mostly) black and white illustration. The illustration style is tuned directly to the narrative. It is reminiscent of cave drawings, often conveying things with almost abstract line work. When it does ahistorically increase detail to capture a character’s emotion or likeness, it retains the flavor of cave drawings, which is enough. It is a really nice effect, enhancing the proceedings at every turn. I particularly liked the rendering of (Spoiler - click to show)the group’s emergence from a tunnel to their new home.
It is all underlaid with music and sound effects similarly tuned to the current scene. The choice to make individual text blocks short and concise gives the sound work its best shot at not over- or under-staying. Text discipline was also an evocative choice. Mostly two to three very short paragraphs conveying the action and a bit of environment and off to the next. This is where the JAM of it really rang out for me. You see just enough of the onscreen cast to get a feel for them, but as much or more of the community impact on and from their actions. To be clear, I found this a compelling narrative choice.
The story itself is told in three parts: an initial tense escape, some community building, then a final migration to a new home. I didn’t get it right out of the gate. There were two things that made the work harder to engage for me, I think. For one, the cast is just on the fat side of ‘wait, who is that again?’ Particularly early on, a lot of names are thrown at us, some of them phonetically similar, though only a few get ‘screen time.’ Names without scenes are just names to a reader. (Notably, Michener himself has sometimes fallen into this trap.)
If not clear by now, this is an interactive fiction, not a game. The interactivity is a nifty thematic echo/expansion of broad sweep storytelling. Let’s think of a JAMmy story thread as a series of discrete action snapshots, implicitly connected by the reader into a larger timeline. Are you thinking of it? Just do it, humor me. We’ll call that the X direction. In the Y direction, we have discrete characters intersecting or not with each other, each with their own suite of discrete scenes that march forward along X. The interactivity lets us decide which threads to look in on. It makes us a drone of sort - where our autonomy is expressed in what we choose to watch while concurrent actions happen outside our view. We are experiencing two-dimensional historical sweep with a one-dimensional camera! Y’know LIKE WE DO EVERY DAY OF OUR LIVES. The corresponding downside to this is that characters we DON’T follow remain opaque and maybe even forgettable to us. The story sometimes concedes ‘flashback’ options to catch up on concurrent activities, but that seemed unevenly applied to me.
The author does one really vital thing - allows a ‘restart this chapter’ option at the end, so the reader can maybe go back and drone-stalk threads they missed the first time. Really the presence of this option is what won me over. I intellectually appreciated the 2D approach, but found it sometimes made the narrative difficult to follow and engage. By letting you cycle a few times, you can explore the entire two dimensional space. Don’t sleep on this capability, fam!
The middle part of the narrative to me was where the work fired on all cylinders. Characters introduced, short one-off scenes with subsets of cast members, deeper intersections between the threads (and maybe fewer to manage) all painting the picture of a community coming together two or three characters at a time. I mostly had the cast in hand by this point. Strong, effective stuff, no notes.
The third part pulled away from me again. It is presenting a much larger time window than the prior two parts, so the sampled character work has a lot more to do and doesn’t quite succeed as well. Characters age, life events that plausibly happen in large timeframes are mentioned in passing leading to a ‘well I guess that happened offscreen?’ kind of feeling. The follow-a-thread architecture meant you were missing a lot MORE of the other threads as time whizzed by. It had a distancing effect, or at least more distancing. I feel if it had adhered more to the fuel-air mixture of part two, or even accelerated more evenly to the faster pace I would have better enjoyed the ride. As it was, it started to feel not just like acceleration but also getting thinner?
I don’t want to sound too down on this thing. Despite the taffy pulling sensation of part 3 it nevertheless really captured the sweet melancholy of time passage and generational handoff. And it paid off many of the recurring characters. This work stands out in epic sweep and subject matter; in narrative style; in thematic use of interactivity; in whole-package presentation. I really really liked it, but couldn’t quite overlook the minor burrs on the way. Sparks of Joy, Mostly Seamless, bonus point for a thrilling mix of uncommon artistic flexes.
…
Ok, you may be asking ‘why just Mostly Seamless?’ Was hoping I could just drop that and run. Part of it was the sometimes jarring time jump transitions in the third part, not fatal but noticeable. But really the big thing was, and I’m putting reviewer-is-petty blur on this: (Spoiler - click to show)At one point, in lieu of the evocative illustrations we instead get a 3D modeled archeological artifact. It felt unwelcome in the moment, but by the end there was a scene with actual archeologists. WHY WAS THIS NOT USED THERE INSTEAD? I don’t know why this obvious-to-me missed opportunity is such a rock in my mental shoe, but there it is. Look, the gap between Mostly Seamless and Seamless is pretty thin and doesn’t even affect the score. You gotta give me a pass on this.
Played: 10/17/23
Playtime: 35min, finished
Artistic/Technical ratings: Sparks of Joy, Mostly Seamless, bonus for kicking out the JAMs!
Would Play After Comp?: No, but I will probably check out the rest of the series
Artistic scale: Bouncy, Mechanical, Sparks of Joy, Engaging, Transcendent
Technical scale: Unplayable, Intrusive, Notable (Bugginess), Mostly Seamless, Seamless