The Ways of the Force
My mom likes to say that I went through several phases in my childhood, based on the things I drew. First there were superheroes, then knights, and then Star Wars. And that phase pretty much didn't end until I woke up sometime in the spring of 2000.
I was a huge Star Wars fan. I was about as big a Star Wars fan as you could be before this monstrosity that is the Internet came along. Nowadays, I’m completely outclassed by the likes of Darth_Chocolate32, Grand Moff WampaLoverr, and Ted the Hutt.
Still, I appreciate what George gave to the world, and from time to time fragments of memory combine with experience to produce moments of genuine understanding. For example, I’m mulling over the hows and wherefores of setups and payoffs, done particularly well in current offerings like 3:10 To Yuma and Eastern Promises, and this idea, this insight, pops into my little noggin, and suddenly two seemingly innocuous dots in the rich tapestry that is Lucas’s elegant script slam together with a huge, a gigantic, amount of . . . well, force.
Let’s look at the original Star Wars film. At the end of Act I, Luke has decided to follow old Ben on his “damned-fool idealistic crusade” and become a Jedi Knight like his father. At some point, Ben is going to provide some instruction. You know the scene. While in hyperspace en route to Alderaan, Luke is training with the remote seeker and getting zapped in the process. Han laughs, dismissing the Force, but Ben places a helmet on Luke’s head that completely covers his face.
And thus one of the film’s themes is articulated. Luke relaxes and, trusting the Force, succeeds in blocking the remote’s laser bolts. The scene itself might have worked with just Ben and Luke, and that’s how a novice writer might have constructed the scene. But Han’s doubt provides the contrast necessary to highlight and embolden Luke’s lesson: “Ancient weapons and hokey religions are no match for a good blaster at your side.” In fact, his words echo those of Admiral Motti, proud architect of the Death Star, to Darth Vader: “Don’t try to frighten us with your sorceror’s ways, Lord Vader. Your sad devotion to that ancient religion has not helped you conjure up the stolen data tapes or given you clairvoyance enough to find the Rebel’s hidden fort . . .”
Here, in the conflict between the ways of the Force and the ways of technology, lies the key to Luke’s journey and the resolution of the story. This theme is located in at least two other instances. The first occurs when Luke uses his macrobinoculars to spy on the Sand People. His recklessness and reliance on technology actually prevent him from seeing the danger right in front of him. The second takes place in the Death Star detention area, when Luke, disguised as an Imperial stormtrooper, complains, “I can’t see a thing in this helmet.”
If we jump to the climax of the film, the Death Star battle, we find Luke making what will certainly be his only trench run. All his comrades have fallen prey to enemy fighters. Vader—in whom the tension between faith and technology resides most dramatically—is closing in. The impossible target of the thermal exhaust port looms ever closer. And then Luke, prompted by Ben’s disembodied voice, makes a simple but critical choice. He switches off his targeting computer—to the consternation of Rebel strategists—and, guided by the Force, releases the torpedoes that destroy the Death Star and save the Rebellion.
Looking back to the training scene, which occurs just prior to the midpoint, we see that its structural function is to set up this climax. To prepare Luke (and the audience) for the task he will need to perform at the very end. Let go your conscious self and act on instinct. In a simple scene, complete in itself, Lucas has planted the seed for one of the most joyous and satisfying conclusions in film history.
I was a huge Star Wars fan. I was about as big a Star Wars fan as you could be before this monstrosity that is the Internet came along. Nowadays, I’m completely outclassed by the likes of Darth_Chocolate32, Grand Moff WampaLoverr, and Ted the Hutt.
Still, I appreciate what George gave to the world, and from time to time fragments of memory combine with experience to produce moments of genuine understanding. For example, I’m mulling over the hows and wherefores of setups and payoffs, done particularly well in current offerings like 3:10 To Yuma and Eastern Promises, and this idea, this insight, pops into my little noggin, and suddenly two seemingly innocuous dots in the rich tapestry that is Lucas’s elegant script slam together with a huge, a gigantic, amount of . . . well, force.
Let’s look at the original Star Wars film. At the end of Act I, Luke has decided to follow old Ben on his “damned-fool idealistic crusade” and become a Jedi Knight like his father. At some point, Ben is going to provide some instruction. You know the scene. While in hyperspace en route to Alderaan, Luke is training with the remote seeker and getting zapped in the process. Han laughs, dismissing the Force, but Ben places a helmet on Luke’s head that completely covers his face.
LUKE: (laughing) With the blast shield down, I can't even see. How am I supposed to fight?
BEN: Your eyes can deceive you. Don’t trust them.
BEN: Your eyes can deceive you. Don’t trust them.
And thus one of the film’s themes is articulated. Luke relaxes and, trusting the Force, succeeds in blocking the remote’s laser bolts. The scene itself might have worked with just Ben and Luke, and that’s how a novice writer might have constructed the scene. But Han’s doubt provides the contrast necessary to highlight and embolden Luke’s lesson: “Ancient weapons and hokey religions are no match for a good blaster at your side.” In fact, his words echo those of Admiral Motti, proud architect of the Death Star, to Darth Vader: “Don’t try to frighten us with your sorceror’s ways, Lord Vader. Your sad devotion to that ancient religion has not helped you conjure up the stolen data tapes or given you clairvoyance enough to find the Rebel’s hidden fort . . .”
Here, in the conflict between the ways of the Force and the ways of technology, lies the key to Luke’s journey and the resolution of the story. This theme is located in at least two other instances. The first occurs when Luke uses his macrobinoculars to spy on the Sand People. His recklessness and reliance on technology actually prevent him from seeing the danger right in front of him. The second takes place in the Death Star detention area, when Luke, disguised as an Imperial stormtrooper, complains, “I can’t see a thing in this helmet.”
If we jump to the climax of the film, the Death Star battle, we find Luke making what will certainly be his only trench run. All his comrades have fallen prey to enemy fighters. Vader—in whom the tension between faith and technology resides most dramatically—is closing in. The impossible target of the thermal exhaust port looms ever closer. And then Luke, prompted by Ben’s disembodied voice, makes a simple but critical choice. He switches off his targeting computer—to the consternation of Rebel strategists—and, guided by the Force, releases the torpedoes that destroy the Death Star and save the Rebellion.
Looking back to the training scene, which occurs just prior to the midpoint, we see that its structural function is to set up this climax. To prepare Luke (and the audience) for the task he will need to perform at the very end. Let go your conscious self and act on instinct. In a simple scene, complete in itself, Lucas has planted the seed for one of the most joyous and satisfying conclusions in film history.
Labels: Doug von Koss, George Lucas, screenwriting, Star Wars, structure