Read & Play: Game Design as Narrative Architecture – Noé Chicas-Aranda

Spoilers for Chapters One and Two of The Great Ace Attorney Chronicles.

I played The Great Ace Attorney Chronicles, a courtroom mystery developed and published by CAPCOM, on Steam for about four hours, completing Chapter Two after previously finishing Chapter One. You play as Ryunosuke Naruhodo, a Meiji-era university student accused of murder before traveling to Britain. Rated T for Teen, the game seems aimed at teenagers and older players who enjoy mysteries and visual novels.

Henry Jenkins argues that game designers can act as “narrative architects,” and I think Chapter Two of The Great Ace Attorney Chronicles is a great example of this. Chapter One taught me to expect a villain behind every murder, so when Kazuma died, I immediately started looking for his assassin. But the more I investigated, the less his death felt like a murder mystery and the more it felt like a tragedy. What I found interesting was that the game didn’t need to change its mechanics to make me feel differently about the investigation. It just changed what the evidence meant to me.

To recap the story so far, Chapter One, “The Adventure of the Great Departure,” begins with me accused of shooting a British professor. My friend Kazuma Asogi helps me defend myself in court (Fig. 1), and we eventually uncover a poisoning plot. As a tutorial, the chapter teaches me to expect a certain pattern. I get accused, investigate what happened, and eventually expose the real culprit. I carried that expectation into Chapter Two.

Fig. 1: Ryunosuke on trial alongside Kazuma.

Chapter Two opens with an account of a snake called “the speckled band.” Aboard the SS Burya, detective Herlock Sholmes declares that the suspect in a locked-room murder is hiding in a wardrobe (Fig. 2). Sailors pull out the sleeping suspect, who turns out to be me. I wake up handcuffed, accused of killing Kazuma. I was disappointed to be framed (again), especially when Susato, Kazuma’s assistant, suspected me too. She even throws me to the floor when I try to investigate! Only one person believes me, Hosonaga, the inspector who coughs up blood. He tells me he was assigned to protect Kazuma, and given how similarly the previous chapter began, I expected to uncover the real assassin once again.

Fig. 2: Herlock Sholmes getting ready to uncover me sleeping in wardrobe

Jenkins describes four ways games can tell stories through space: evocative, embedded, enacted, and emergent. Chapter Two’s evocative storytelling borrows from Sherlock Holmes, especially Arthur Conan Doyle’s “The Speckled Band,” with its snake, vent, and mysterious death. Its embedded storytelling is even more interesting to me. The cabin contains evidence of an event that happened before I could witness it, and each object helps me reconstruct what occurred. The room itself becomes a way of telling the story. The enacted narrative comes from examining objects and challenging Sholmes’s deductions. Emergent storytelling is more limited because the story and its ending are already decided. Still, I found myself coming up with theories about what happened, only to realize how wrong I was as I uncovered more evidence. Even after the chapter ended, I still didn’t fully agree with how Ryunosuke felt about Susato. I think it’s interesting that the game can control what happens in the story, but not necessarily how I feel about it.

The game mixes visual novel storytelling with adventure-game investigation and courtroom evidence mechanics. Surprisingly, Chapter Two has no trial. Once I realized I would prove my innocence by searching the ship, I was happy to do so. The visual novel format allows for detailed dialogue and expressive character reactions, while the investigation lets me take part in discovering what happened. Jenkins’s accordion idea fits here because the main events are fixed, but I still have some freedom to explore and spend time examining different parts of the ship. Still, I sometimes found the vast dialogue exhausting.

The main mechanics involve examining objects, collecting evidence, and presenting contradictions. These mechanics made me constantly question what I thought had happened, which connects to the types of fun of Narrative and Discovery. My favorite example was correcting Sholmes’s theatrical but mistaken deductions. He mistakes me for a revolutionary and eventually blames a trained snake (Fig. 3). But Kazuma’s post-mortem points to a broken neck, and the supposed “speckled band” turns out to be a fluffy cat toy. Instead of just watching a detective reveal the answer, I get to help him figure out what actually happened.


Figs. 3: A mistaken Sholmes deduction

The clues lead to Nikolina Pavlova, a fifteen-year-old runaway ballerina traveling with her cat, Darka. When Kazuma recognizes her, she fears being sent back to the ballet’s exhausting conditions. In a panic, she pushes him, and he falls and breaks his neck. But Kazuma was actually about to consult me, not report her. The “assassin” I had pictured turned out to be a frightened girl who misunderstood his intentions (Fig. 4).

Fig. 4: Pavlova trying to conceal her identity.

I was genuinely devastated by Kazuma’s death. Before I started Chapter Two, the person who introduced me to the game asked who I thought would die in this chapter. My immediate response was that Kazuma, my mentor, was the last person I expected to die. He had so much left to accomplish, and I couldn’t imagine the creators killing him off so early in the story. I was convinced he would remain an important character throughout the game. So when he died, it hit me pretty hard.

Yet by the end of the chapter, I found myself mourning Kazuma while also feeling sorry for the person responsible for his death. I had expected a villain, much like in Chapter One, but instead discovered a frightened girl who had made a terrible mistake. Pavlova was still responsible for what happened, and she and the sailor who helped conceal the incident still had to face the consequences. But knowing why she did it made it difficult for me to see her as a villain. Somehow, this made Kazuma’s death feel even more unfair. He hadn’t died because of some elaborate assassination plot or a villain’s evil intentions. He died because of a misunderstanding. There was something deeply unsatisfying about realizing that he should have been standing beside me if not for one unfortunate accident.

What struck me most was the parallel with my own position. I had spent Chapter One being wrongly accused, yet in Chapter Two, I was quick to imagine malicious intent in someone else. Pavlova wasn’t innocent in the same way I was, but I still found myself judging her before knowing the full story. Early on, gathering clues felt exciting because I thought I was hunting an assassin. Later, those same actions felt sad because I was piecing together a tragedy. The mechanics stayed the same, but I felt completely differently about what I was doing. Suddenly, I cared more about the why than the how.

Not every intended feeling worked for me, though. By the end, Susato becomes my assistant as I promise to continue Kazuma’s journey (Fig. 5), yet I still resented her for immediately suspecting me. Ryunosuke may be ready to trust her, but I still hold a grudge against her! Even though the game wanted me to accept Susato as my new partner, I wasn’t quite ready to do that. I was actually frustrated that I had to continue working alongside her, even though Ryunosuke seemed to have forgiven her. It made me realize that players don’t always feel the way the story expects them to.


Fig. 5: Susato asking for repent.

The MDAO reading argues that aesthetics don’t always have to be positive, and I think Kazuma’s death is a good example of that. I was upset by what happened, but that frustration made the story much more memorable to me. Beyond entertainment, I also took away some Information (apparently snakes do not drink milk) and got to practice Implicit Skills, particularly questioning my assumptions and revisiting evidence.

For my own interactive fiction, I want to establish patterns that players trust, then use clues they personally uncover to complicate those expectations. I also liked how the Court Record preserves important evidence (Fig. 6), especially when the dialogue gets dense or players skim. I would borrow that accessibility without making answers too obvious.

Fig. 6: The Court Record organizing collected evidence.

My biggest criticism is still the limited agency. I can investigate and figure out what happened, but I can’t save Kazuma or change what Pavlova did. And honestly, I wish I could! I still feel like Kazuma’s death was unfair, especially knowing how easily it could have been avoided. But I also wonder if being unable to change anything is part of why his death affected me so much. No matter how many clues I find, Kazuma is still gone. I went into this chapter expecting to find an assassin, just like in Chapter One. Instead, I ended up feeling sorry for the person I had been trying to catch. I knew how Kazuma died, but by the end, I cared much more about why. I think that’s something I’ll remember when designing my own mysteries. Sometimes, finding out who did it isn’t nearly as interesting as understanding why they did it.

 

P.S. Unfortunately, all of the documentation and screenshots I took during my playthrough are stored on a borrowed PC that I no longer have access to. As a result, I used footage from this YouTube gameplay archive to source the figures included in this analysis.

Sketch note:

 

 

About the author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.