Perfect State Annotations

Event details
Name
Name Perfect State Annotations
Date
Date June 22, 2016
Entries
Entries 2
Upload sources
#1 Copy

Brandon Sanderson

Why I cut the deleted scene

This story began with the idea of taking some common tropes in science fiction—the brain in a jar, the Matrix-like virtual existence—and trying to flip them upside down. In every story I’ve seen with these tropes, they’re presented as terrible signs of a dystopian existence. I asked myself: What if putting people into a virtual existence turned out to be the right thing instead? What if this weren’t a dystopia, but a valid and workable system, with huge benefits for humankind?

Kai’s and Sophie’s stories grew out of this. I loved the idea that putting people into simulated worlds might actually be the rational solution, instead of the terrifying one. An extreme, but possibly logical, extrapolation of expanding populations and limited resources. There are certain branches of philosophy that ask us to judge what is best for all of humankind. I think an argument could be made for this case.

This is the first reason why I cut the deleted scene. It shifted the focus too much toward “Let’s escape the Matrix” instead of the theme of technology doing great things at the price of distancing us from human interaction.

All that said, Sophie’s arguments in the story do have validity. One of my thematic goals for the story was to reinforce how the fakeness in Kai’s and Sophie’s lives undermines the very things they’ve built their personalities upon.

For Kai, this is his heroism. The fact that there was never any actual danger for him meant that he was playing a video game on easy mode—all the while assuming he was on the most hardcore setting. This asks a question, however: if his heroism felt real to him, does it matter if he was never in danger? I’m not sure, but I found it one of the more intriguing elements of the story to contemplate.

Sophie has a similar built-in conflict. Just like Kai’s heroism is undermined by his safety net, her revolutions and quests for human rights are undermined by the fact that she was fighting wars that had already been won in the real world. Her state was intentionally built without these things, just so she could earn them.

And yet, does the fact that the conflict has been won before make her own struggle any less important and personal to her?

She thinks it does. She thinks that the conscious decision of the Wode to put her into a world with fake problems and suffering is an unconscionable act. One that undermines any and all progress she could have made.

I like that the deleted scene helps raise the stakes for questions like this. However, there’s a more important reason why I felt I needed to cut it. And that has to do with a problem I have noticed with my writing sometimes: The desire to have awesome twists just because they are unexpected.

In early books, such as Elantris, this was a much more pervasive a problem for me. I was eventually persuaded by my editor and agent that I should cut some of the twists from that book. (There were several more twists in the ending; you can see the deleted scenes for Elantris elsewhere on my website.) I was piling on too many surprises, and each was losing its impact while at the same time diluting the story’s theme and message.

I felt like this ending was one “Gotcha!” too many. I see this problem in other stories—often long, serialized works. The desire to keep things fresh by doing what the reader or viewer absolutely would never expect. Some of these twists completely undermine character growth and audience investment, all in the name of a sudden bang. Sometimes I worry that with twists, we writers need to be a little less preoccupied with whether or not we can do something, and a little more focused on whether it’s good for the story. (With apologies to Ian Malcolm.)

A twist should be a natural outgrowth of the story and its goals. In Perfect State, I decided that my story was about Kai getting duped: duped by the Wode, then duped by Melhi. The twists in the published version contributed to this goal, giving in-story proof that his heroism could be manipulated, and that his existence had grown too comfortable.

I worried that the extra epilogue would divert the story away from these ideas. And so, in the end, I cut it. (Though I’ll talk in the next annotation about some ramifications of this that still trouble me.)

#2 Copy

Brandon Sanderson

Consequences of the cut

Cutting the last scene was not without costs to the story. For the longest time, after removing this scene, something about what remained bothered me. I had trouble placing what was wrong.

The story went through editorial revisions and beta reads, none of which revealed what was bothering me. This process did convince me to add two scenes. The first was scene with the “paintball” fight in the noir city, which was intended to mix some action and worldbuilding in while revealing more of Kai’s personality. The second was the flashback scene where Kai and Melhi meet on the “neutral zone” battlefield, intended to introduce Melhi as more of a present threat in the story.

Something was still bothering me, even after these additions. It took me time to figure out exactly what it was, and I was able to pinpoint it in the weeks leading up to the story’s publication. (Which was good, as it allowed me to make some last-minute changes. I’m still not sure if they fixed the problem, but we were satisfied with them.)

The problem is this: removing the final scene hugely undermined Sophie as a character.

The deleted scene provides for us two complete characters. We have Kai, who wants to retreat into his fantasy world and live there without ever being forced to think about the falsehood he’s living. He wants just enough artificial challenge to sate him, but doesn’t want to explore life outside of the perfect world prepared for him.

As a contrast, we have Sophie, who refuses to live in the perfect world provided for her—and is so upset by it that she insists on trying to open the eyes of others in a violently destructive way. She tries to ruin their States, forcing them to confront the flaws in the system.

Neither is an ideal character. Sophie is bold, but reckless. Determined, but cruel. Kai is heroic, but hides deep insecurities. He is kindly, but also willfully ignorant. Even obstinately so. Each of their admirable attributes brings out the flaws in the other.

This works until the ending, with its reversal, which yanks the rug out from underneath the reader. Sophie’s death and the revelation that Kai has been played works narratively because it accomplishes what I like to term the “two-fold heist.” These are scenes that not only trick the character, but also trick the reader into feeling exactly what the character does. Not just through sympathy, but through personal experience.

Let’s see if I can explain it directly. The goal of this scene is to show Kai acting heroically, then undermine that by showing that his heroism was manipulated. Hopefully (and not every scene works on every reader) at the same time, the reader feels cheated in having enjoyed a thrilling action sequence, only to find out that it was without merit or consequences.

Usually, by the way, making readers feel things like this is kind of a bad idea. I feel it works in this sequence, however, and am actually rather proud of how it all plays out—character emotions, action, and theme all working together to reinforce a central concept.

Unfortunately, this twist also does something troubling. With the twist, instead of being a self-motivated person bent on changing the mind of someone trapped by the establishment, Sophie becomes a pawn without agency, a robot used only to further Kai’s development.

Realizing this left me with a difficult conundrum in the story. If we have an inkling that Sophie is Melhi too early, then the entire second half of the plot doesn’t work. But if we never know her as Melhi, then we’re left with an empty shell of a character, a direct contradiction to the person I’d planned for her to be.

Now, superficially, I suppose it didn’t matter if Melhi/Sophi was a real character. As I said in the first annotation, the core of the story is about Kai being manipulated by forces outside his control.

However, when a twist undermines character, I feel I’m in dangerous territory—straying into gimmicks instead of doing what I think makes lasting, powerful stories. The ultimate goal of this story is not in the twist, but in leading the reader on a more complex emotional journey. One of showing Kai being willing to accept change and look outward. His transformation is earned by his interaction with someone wildly different from himself, but also complex and fascinating. Making her shallow undermines the story deeply, as it then undermines his final journey.

There’s also the sexism problem. Now, talking about sexism in storytelling opens a huge can of worms, but I think we have to dig into it here. You see, a certain sexism dominates Kai’s world. Sophie herself points it out on several occasions. Life has taught him that everyone, particularly women, only exist to further his own goals. He’s a kind man, don’t get me wrong. But he’s also deeply rooted in a system that has taught him to think about things in a very sexist way. If the story reinforces this by leaving Sophie as a robot—with less inherent will than even the Machineborn programs that surround Kai—then we’ve got a story that is not only insulting, it fails even as it seems to be successful.

Maybe I’m overthinking this. I do have a tendency to do that. Either way, hopefully you now understand what I viewed as the problem with the story—and I probably described this at too great a length. As it stands, the annotation is probably going to be two-thirds talking about the problem, with only a fraction of that spent on the fix.

I will say that I debated long on what that fix should be. Did I put the epilogue back in, despite having determined that it broke the narrative flow? Was there another way to hint to the reader that there was more going on with Melhi than they assumed?

I dove into trying to give foreshadowing that “Melhi” was hiding something. I reworked the dialogue in the scene where Kai and Melhi meet in person, and I overemphasized that Melhi was hiding her true nature from him by meeting via a puppet. (Also foreshadowing that future puppets we meet might actually be Melhi herself.) I dropped several hints that Melhi was female, then changed the ending to have Wode outright say it.

In the end, I was forced to confront the challenge that this story might not be able to go both ways. I could choose one of two things. I could either have the ending be telegraphed and ruined, while Sophie was left as a visibly strong character. Or I could have the ending work, while leaving Sophie as more of a mystery, hopefully picked up on by readers as they finished or thought about the story.

The version we went with has Sophie being hinted as deeper, while preserving the ending. Even still, I’m not sure if Perfect State works better with or without the deleted scene. To be perfectly honest, I think the best way for it to work is actually for people to read the story first, think about it, then discover the deleted scene after they want to know more about what was going on.

Even as I was releasing the story, I became confident that this was the proper “fix.” To offer the story, then to give the coda in the form of Sophie’s viewpoint later on. It’s the sort of thing that is much more viable in the era of ebooks and the internet.

Either way, feel free to drop me a line and let me know what you think. Does it work better with or without the deleted scene? Do you like having read the story, then discovered this later? Am I way overthinking what is (to most of you) just a lighthearted post-cyberpunk story with giant robots?

Regardless, as always, thanks for reading.

Event details
Name
Name Perfect State Annotations
Date
Date June 22, 2016
Entries
Entries 2
Upload sources