The Sins of Omission: Building Season 2 of True Crime, Wrong Story

The Sins of Omission: Building Season 2 of True Crime, Wrong Story

The Sins of Omission: Building Season 2 of True Crime, Wrong Story is both a visual novel and a production diary for a real podcast season. In the game, you play Cassie Lark’s researcher, building case files, timelines, and interview packs instead of chasing car chases or jump scares. In the podcast, those same choices and documents become episodes about a murder that was framed as “violent ex” when the real engines were caregiving, money, and a detective’s convenient omissions.

This devlog is a postmortem of that process: how The Sins of Omission evolved from notes and Ren’Py errors into a playable season, why it exists alongside the True Crime, Wrong Story podcast, and what went right, wrong, and ethically complicated along the way.

Why this case, why this form

True Crime, Wrong Story exists because “true crime” has a pattern: flattening complex cases into neat narratives with one villain, one victim, and one hero. In the Grenfell case, that neat story was “woman killed by abusive ex.” Jeri Grenfell’s murder was packaged as domestic violence: a jealous ex who finally snapped, a victim framed as “legal secretary,” and a detective who supposedly wrangled chaos into a clean conviction.

The more I read, the more wrong that felt. Jeri was also a caregiver for her dying mother, Jody. She was investigating fraud for her community stream. There was a son, Austin (“Aussie”), whose caregiving hours were tied to inheritance, and a detective, Shel Hooper, whose drunk hit‑and‑run and missing tape sat in the middle of the evidence chain. The official story turned caregiving, money, and suppression into background noise.

That’s why this case became Season 2 of True Crime, Wrong Story. And that’s why the form is a visual novel that behaves like a podcast production:

• You’re not a cop; you’re a researcher.
• Cassie isn’t a narrator; she’s your executive producer.
• The “gameplay” is building the same research packs, memos, and case boards that feed episodes on the podcast side.

The visual novel and the podcast talk to each other: one is the playable version of the ethics and arguments the other records.

Designing Cassie and the researcher

Cassie Lark is the spine of True Crime, Wrong Story. In the game, she isn’t just a character; she’s a curator and executive producer who:

• Sets weekly assignments (door, omission, alibi, dual motive).
• Pushes you to distinguish feelings from facts.
• Refuses to let you say “I just know” without documents, timelines, or witnesses.

Mechanically, that meant building the game around check‑ins:

• Every week starts with a Cassie Zoom.
• She frames the questions and the stakes.
• You choose how you respond, in both content and tone, and your choices affect her approval and the route you end up on.

Your role is deliberately uncomfortable:

• You’re building a case that might put a different man under suspicion while a wrongfully convicted one sits in prison.
• You have access to families under strain, including a dying mother.
• You have to keep remembering that Jody, Jeri, Ana, Lee, and Austin are people, not plot devices.

The game needed to keep you inside those tensions. That’s why there’s no combat, no inventory, no branching romance. There are documents, interviews, research packs, and Cassie’s recurring question: “Can you stand this up in a room?”

Episodes 1–6: structure and themes

Season 2 is six in‑game episodes that mirror a podcast season arc. Each episode has a thematic job.

Episode 1: The Assignment

You meet Cassie, the Grenfell file, and the idea of “wrong story.” Lee Haus is the convenient villain; Jeri’s stream is a marginal note; Ana Reese is a “bystander struck by unknown vehicle.”

Your job is not to declare Lee innocent. Your job is to learn to say: “This feels wrong structurally, not exculpatory.”

Episode 2: The Wrong Story

You follow Ana and the cameras. The case shifts from “was Lee bad?” to “why did Ana vanish from the story and why did the tape die?” You start building surveillance gaps and an omission map.

The episode ends with Cassie deciding to treat Grenfell as a TCWS special in active build, not just a development exercise.

Episode 3: The Missing Witness

You do the unglamorous work: file audit, media comparison, and a second conversation with Ana. You discover how often paperwork and coverage downgrade:

• Ana from witness to “unrelated injury.”
• Jeri from journalist to “legal secretary with a hobby podcast.”
• Shel from bottleneck to “hero detective.”

Episode 3’s job is to prove that the problem is not just an abusive ex; it’s a system that chooses smaller versions of people to keep the story tidy.

Episode 4: The Door

This is the caregiving episode: Jody’s decline, Jeri’s work, Austin’s presence, and the Hoyer lift pretext. You build Jody’s timeline, Aussie's access notes, and the door engine:

• Jody: fully dependent, transfers hurting.
• Jeri: exhausted, asking for extra hands.
• Aussie: PSW experience, conditional inheritance tied to care hours, offering to help with the lift.

By the end of Episode 4, you’re able to say: “The killer did not break in. The killer was let in.” Not through romance, but through equipment and duty.

Episode 5: The Alibi Week

Holiday week. No Monday. Less time, more to prove. You:

• Break Austin’s hospital alibi with rosters, a manager’s statement, and a late domestic newsletter.
• Find the “Ana’sBoy” forum handle and his crypto panic about a podcast.
• Pull FOIA files that show Shel’s proximity to Ana, the “technical issue” on the tape, and an internal directive to frame as domestic violence to “avoid contagion narratives.”

You build a RESEARCH PACK and a HANDLE ANALOGY:

• Care as access.
• Money as pressure.
• Resentment as accelerant.
• Door as crime.

By Friday, you have a one‑page synthesis: Wrong man. Detective. Door. Fraud. Will.

Episode 6: The Gauntlet

Gauntlet week. Three acts:

• Act One: you defend dual motive, handle, and ethics to Cassie.
• Act Two: you defend what you can and can’t say to Legal (Willow).
• Act Three: you defend why this case deserves airtime and money to Exec.

Your routes branch:

• Golden route: inheritance and fraud motives are solid; the door and Shel’s omissions are clear; Legal signs off; Exec grants a season order. You get an RV Cassie epilogue where the episode aired and the newsletter finally uses the words care, fraud, and equipment.
• Lesser route: the motives are partial; you can’t fully stand them up. The episode dies in development. The Grenfell file becomes a diagnostic: a case study in how wrong stories happen and when the ethical choice is to walk away without pretending certainty.

Both routes are canon. One is about winning the gauntlet. The other is about ethics over heroics.

Production postmortem: Ren’Py, routes, and sprites

On paper, this structure is clean. In practice, building it in Ren’Py while juggling writing, podcast work, and real life was messy.

Some highlights (and lowlights):

• Menus and indentation: Ren’Py is unforgiving about indentation. A single misaligned menu: or label turned Episode 4’s Cassie door and check‑in scenes into error storms. This forced a reset of entire blocks and a discipline: never mix story edits and structural edits when you’re tired.
• Sprite paths: For a while, Jody and Aussie were invisible because their sprites pointed at images/characters/… while the files actually lived under images/sprites/…. The logic worked; the faces didn’t. Fixing those paths suddenly made the interviews feel real.
• Scaling: Shel and Cassie RV both came in “headless” at full resolution. Attempts to fix them with inline zoom and colon blocks triggered more Ren’Py errors. The eventual solution was simple: use im.Scale in the image definitions and keep show syntax boring.
• Cancelling Jody’s interview: Originally, the plan was to have Jody as a full interviewee in Episode 5. Reality pushed back: her health arc in the narrative made “holiday week interview” feel exploitative. The game now reflects that: Jody gives you crucial information in Episode 4, but by Episode 5 she is too sick. Cassie cancels the interview, and the player has to carry the lost intel as part of the case.
• Persistent data and saves: During development, dozens of saves kept the build from starting at square one after every crash. Clearing those required understanding Ren’Py’s dual save system . Only after deleting both did the game truly reset to first‑run behavior.

Technically, The Sins of Omission is a Ren’Py 8 build with:

• Desktop distributions for testing.
• A web/HTML5 build for itch.io and embedding.
• A music map using royalty‑free tracks that signal mood without overwhelming the narrative.

Emotionally, it’s a map of my own fight with tooling, time, and the demands of telling a complicated story honestly.

Linking the game and the podcast

The game is not a literal “adaptation” of the podcast; it’s the research side of it. Some points of connection:

• The podcast episodes follow the same arc: assignment, omission, Ana, door, alibi week, gauntlet.
• The memos you write in the game (EPJG_SURVEILLANCE_GAPS, EPJG_OMISSION_MAP, EPJG_AUSSIE_ALIBI, EPJG_DOOR_SYNTHESIS) are the kind of documents that sit behind podcast scripts.
• The golden route RV epilogue reflects what happens when a show airs carefully wrong: systems move a little, people argue, but no single case “fixes” everything.
• The lesser route epilogue reflects what happens when a story is too fragile to put in front of millions: the file stays in a drawer, and the only honest win is refusing to add another wrong story to the pile.

Playing the game before listening to the season gives you a sense of how much work and doubt sits behind each “episode.” Listening first and then playing lets you see where the show had to simplify and where the game leans into complexity.

What went right, what went wrong, and what’s next

What went right:

• The spine: care, fraud, omission, wrong story, held through code, routes, and episodes.
• Cassie as curator/executive producer works as both character and structural force.
• The golden and lesser ending exist as ethics, not just “good” and “bad” outcomes.

What went wrong (and got fixed):

• Over‑attachment to the idea of a “missing tape” and a magical clip almost turned the game into the same kind of infotainment it critiques.
• Ren’Py’s error messages forced structural discipline at 11 PM when I least wanted it.
• Jody’s interview had to be cancelled in a way that respected her as a person, not a “motive engine,” which meant reconstructing parts of Episode 5.

What’s next:

True Crime, Wrong Story is not done. The Sins of Omission is Season 2 of the game and the podcast, but the project has other wrong stories waiting: different cases, different systems, different ways narratives hide harm.

From here, the plan is:

• Treat this season’s game and podcast as a baseline for how ethics, empiricism, and storytelling can coexist.
• Use what this build taught me about tooling, routes, and pacing to make future seasons smoother technically and sharper narratively.
• Keep refusing to turn complex harm into neat villains and neat heroes, even when platforms and audiences are hungry for exactly that.

If you’ve played The Sins of Omission, thank you for sitting inside a long, uncomfortable case. If you’ve listened to the podcast, thank you for letting us try to tell a wrong story right. And if you’re here for the devlog, thank you for caring about how these things get made.

That’s the best kind of golden ending I know.

If you want to listen to the podcast, explore interactive documentaries, and read true crime dossiers, klueiq.com is the place for you.