“My Millennium Falcon’s only a small converted freighter, and a rather elderly one at that, I’m afraid.” – Lando Calrissian
I had no expectations when I started reading L. Neil Smith’s Lando Calrissian Adventures trilogy. Though I had yet to read a Star Wars Expanded Universe novel that I didn’t like, with something like 200 novels in the Expanded Universe library, I knew it was bound to happen eventually.
But it didn’t happen with this book.
Lando Calrissian and the Mindharp of Sharu is probably the goofiest Star Wars book I’ve ever read. I mean, just look at that title. Look at the titles of all three books in the series. “Mindharp of Sharu,” “Flamewind of Oseon,” “Starcave of Lonboka.” Just two random nouns smashed together with a place name attached at the end. Based on the titles alone, I assumed these books were going to be different than any other Star Wars book I’d read. And I was right!
The book is just very campy. It sort of downplays the science fiction aspect of Star Wars and really upscales the fantasy aspect. Sometimes it felt like I was reading the plot of a Legend of Zelda game instead of a Star Wars novel. Lando is on a quest for an ancient instrument that has magical powers? Sounds… familiar…
It’s a fun adventure that doesn’t take itself too seriously and isn’t afraid to really push the limits of “believable” fantasy within the context of the Star Wars universe. In some ways, I love the book for that. If nothing else, it was a very entertaining read, and in the end that’s what you want out of a book, right? On the other hand, sometimes it felt too out-there. Just a little bit too ridiculous, even for Star Wars. This book takes place a few years before the original Star Wars trilogy. I find myself having a hard time believing that the Lando Calrissian I saw in The Empire Strikes Back and in Return of the Jedi would have a backstory like the one I read in this book.
The book definitely does still have a Star Wars feel to it. First off (and probably most importantly) Smith writes Lando very well. His characterization is great, and it truly feels like the same character we love from the movies. Obviously having Lando in the starring role is going to make the story at least a little bit Star Warsy. There’s the Millennium Falcon, space travel, and even a fun new droid companion. And honestly, the things that didn’t feel like Star Wars are mostly excusable because the story takes place in a new solar system that we haven’t seen on-screen before. Obviously things are going to be a little bit different on new worlds, with new alien races and different cultures and technology. So, the “weirdness” of this story actually might not be that weird if we remember that it actually makes sense that things are super different in different parts of the galaxy.
The story starts off a short time after Lando won the Millennium Falcon in a game of sabacc. He’s not very familiar with the ship yet, and he’s a pretty terrible pilot. That was one thing that annoyed me from the beginning. This doesn’t take place very long before the original movies, and I very clearly remember Lando expertly piloting the Falcon through the insides of the Death Star, which would, y’know, be basically impossible to do. So the fact that he is a terrible pilot in this story was kind of hard to accept. Though, I assume over the course of the three books that is going to change.
Lando is once again playing sabacc. We get to see a lot of sabacc in this trilogy, and the books do a pretty good job of explaining the rules of the game to us. Star Wars Rebels has given us our first on-screen look at sabacc (and at Lando playing the game) in the season one episode Idiot’s Array (which is named after a winning move in sabacc, as revealed in this novel). During this particular game of sabacc, Lando is told about a treasure called the Mindharp of Sharu. This intrigues him. He wins a droid in the game, but he has to go pick the droid up in the Rafa system, which just so happens to be where the Mindharp is located. He goes to the system and gets the droid, a meter-high, starfish-shaped robot (though he looks more like R2-D2 on the book’s cover) named Vuffi Raa. This little guy sort of fills the same role that Bollux and Blue Max filled in Brian Daley’s Han Solo Adventures trilogy. Though I didn’t love the character quite as much as I did Bollux and Max, Vuffi Raa was still a fun character whose presence I enjoyed throughout the story.
Lando gets arrested, on stupid charges, and is brought to the governor’s office. He is given a strange key, that is said to unlock the Mindharp, and is forced to go retrieve the instrument by a sorcerer named Rokur Gepta. Lando has no choice, and goes off to find the Mindharp.
Along with his new partner, Vuffi Raa, Lando meets a humanoid native of the Toka species, named Mohs. Mohs’ people know the legends of the Sharu (the now-extinct ancient race who created the Mindharp and all of the colossal architecture in the Rafa system) and Lando decides to let the him come along to help find the treasure. The Toka, however, are not a very advanced race, and Mohs seems kind of crazy throughout the story. Still, Lando thinks he’ll be a valuable asset to his quest, since Mohs knows more about the Mindharp of Sharu than anyone else he’s met.
Throughout the story Lando has the worst of luck, with seemingly everything working against him to prevent him for retrieving the treasure and finally getting back to his normal way of life. It’s almost frustrating to read at times because the guy just can’t get a break. He’s always getting attacked, arrested, betrayed, or whatever else that could possibly prevent him from getting the harp.
Being one of the earliest Star Wars books ever written, there were a few things that stood out to me as feeling out-of-place in a Star Wars story. Cigarettes abound in this book. Everyone, including Lando, smokes cigarettes. Now, I’ve watched every Star Wars movie there is–including the spin-off movies–and I don’t remember ever seeing a cigarette. Another funny thing is that Lando’s drink of choice is something called “coffeine.” That’s pretty creative, I have to say. Honestly, it’s no worse than “caf,” which is what became the more commonly accepted fake coffee ripoff in Star Wars literature as the years went on.
Also, apparently jackalopes exist in the Star Wars universe. On the planet “Douglas III” in fact. I don’t know what I think is funnier. The fact that jackalopes are real in Star Wars, or the fact that a planet is called Douglas III. They don’t even appear in the story. They are just mentioned one time. It was such a pointless inclusion in the story that it makes me laugh.
The story ends pretty abruptly, and it became clear to me that this is not meant to be a standalone book, and should be followed up by reading the other two books in the trilogy to get the full story. I haven’t read them yet–at the time I’m writing this–but the story didn’t feel finished, and it definitely left you on a cliffhanger. It caught me a little off guard, but it’s not really a bad thing. I am looking forward to reading the next book.
Lando Calrissian and the Mindharp of Sharu isn’t an amazing book, but it is a fun story despite being so goofy. It left me excited to read the sequel, which is always a good thing. Plus it’s just nice to have Lando take the lead role for once. Outside of this trilogy, and Marvel’s new Lando comic mini-series, we don’t see him at the center of the action very often. I can’t say I’d recommend the book to all Star Wars fans, but I think if you enjoy the other early Expanded Universe novels like Splinter of the Mind’s Eye or The Han Solo Adventures trilogy, you’ll probably enjoy this book too.
Before I get started with this review, I want to announce the launch of our social media channels! We’ve had a Twitter account for a while now, but with this review we are officially launching our Facebook and Instagram channels. Follow us on any of these channels for some extra Star Wars book news, and to connect and chat with fellow fans of Star Wars literature! Links to all three accounts can be found right here, but they are also now found on under the “Categories” section on our right-hand sidebar (on mobile view this is at the bottom of the page). We’d love to connect with all of you!
On an unrelated note, Chuck Wendig’s highly-anticipated conclusion to the Aftermath trilogy, Aftermath: Empire’s End, was released this week. I just wanted to remind those of you who have not read it yet to be careful online of unwanted Aftermath: Empire’s End spoilers! I’ve seen a few article headlines and YouTube video titles already that I wish I hadn’t. We promise that we will not spoil the story for you on this blog (our upcoming review will be spoiler-free!) or on any of our new social media channels!
With that out of the way, let’s get back to book reviews…
“You will never stop us. We will not be broken. However long it takes, we will never stop fighting.”—Caluan Ematt
Immediately after finishing Brian Daley’s trilogy of Han Solo novels, I decided I wanted to jump back in to the new Star Wars canon to catch up a little before The Force Awakens came out (yes, this was a long time ago now). I decided to do that by reading yet another Han Solo story. Smuggler’s Run: A Han Solo & Chewbacca Adventure is the first Star Wars book written by Greg Rucka. This book takes place immediately after the events of Star Wars Episode IV: A New Hope. It is a short story, and it is aimed at a younger audience than the adult novels I’ve been reviewing so far. However, it is still a lot of fun to read.
Part of me wanted to read this book immediately after reading Daley’s Han Solo trilogy so that I could compare and contrast them. Did Daley or Rucka write a better Han Solo? Who told the better story? I don’t feel it’s fair to compare this junior novel to full-fledged adult Star Wars novels, but I will say this about Rucka’s Solo story: I was not disappointed. Smuggler’s Run holds up quite well to the adult novels.
Like Daley, Rucka nails writing Han Solo. You can just see Harrison Ford speaking Han’s dialogue in this story, and that is a great thing. The way Han speaks and the way he acts feels perfect, and that has to be the most important thing when writing a Han Solo story.
Aside from the depiction of Han, my main point of praise for this book is the rest of the main cast in the story. I loved the characters this book introduced us to. In this story, Leia sends Han on a mission to rescue a man named Ematt, who was the leader of a small recon team for the Rebellion called the Shrikes. The Shrikes were ambushed by imperials, and Ematt was the only survivor. Ematt is the only person who knows some information that is vital to the success of the Rebellion, so rescuing him is urgent. We don’t get to see much of Ematt in this story, but he is a very interesting character that I would love to learn more about in future stories, especially since he’s already popped up in a few novels and he actually appeared in The Force Awakens!
Another character I loved was a woman named Alicia Beck. She is an officer of the Imperial Security Bureau. She is missing one eye, and has it replaced with a mechanical one that can see in multiple spectra. Commander Beck is very good at her job, and she will do whatever it takes to complete her assigned tasks, including shedding the blood of fellow Imperials. She is feared by those around her, and she leads a large squadron of Stormtroopers for a good portion of this story. When we are introduced to her, our narrator tells us that “she was a woman—and there were very few of those holding high ranks in the Empire.” That seemed kind of strange to me, because so far in the new canon there have been quite a few high ranking women in the Empire. Whatever. Beck was also mentioned (though not seen) in Rucka’s comic series, Shattered Empire. I always love it when these stories reference each other. I hope to see Beck make another significant appearance in a Star Wars story in the near future.
Like in Weapon of a Jedi, the prologue and epilogue of this story take place shortly before The Force Awakens. They’re mostly irrelevant to the story, but reading this book before the movie came out, it sure helped to get me excited to see an older Han Solo on screen! It wasn’t until after the movie came out that I realized how little these stories in the “Journey to Star Wars: The Force Awakens” series actually have to do with The Force Awakens. I expected that all of these stories were going to be much more relevant to the movie, and after seeing The Force Awakens on opening night I felt confused as I left the theater and realized that nothing in the “Journey” series really had anything to do with the movie. Oh well! They’re all still good reads.
This adventure is short and sweet. In a way it feels like reading an episode of an ongoing TV series. This is the adventure of the week. A short but exciting story that leaves you wanting more. Since it’s so short, I can’t say much about it without giving away most of the story. But, it’s a great Han Solo adventure. It does hold up to Brian Daley’s Han Solo Adventures trilogy, even though it’s probably not fair to be comparing them. It’s written really well, like Rucka’s other works in the Star Wars canon. Personally I’d love to see Rucka tackle a full-length adult Star Wars novel.
If you’re just looking for a fun, quick read, and aren’t really too concerned about reading anything “important” when it comes to Star Wars lore, then definitely check this one out. If you’re more interested in “big” events in Star Wars canon, this book is extremely skippable, as nothing of note really happens. I enjoyed it quite a bit.
“The Rebel fleet has gathered all its forces into a single giant armada. The time is at hand when we can crush them, without mercy, in a single blow.” – Darth Vader
Two weeks before Return of the Jedi premiered in theaters, it was released as a novel written by James Kahn. Can you imagine having read the final chapter of the Star Wars trilogy before actually having seen the movie? I guess some people did that. What a strange thought. This novel is Kahn’s first and only contribution to the Star Wars universe.
Being a novelization of the movie, this book is pretty much what you’d expect. It’s the same story, and there isn’t much added to it. What little extra bits of information the book does give us are pretty great though, and they really made this novelization worth reading.
One thing I noticed right off the bat when I started reading was that I really liked Kahn’s writing style. I’m afraid I can’t really describe what exactly I liked about it. There’s just something about it that intrigued me and held my interest even though I already knew the entire story I was reading.
A few scenes that were deleted from the movie still appear in this book, to my delight. Most notably, we get to see Luke building his new lightsaber at the beginning of the story. It doesn’t flat-out say “Luke is building a lightsaber” but, he totally is. He assembles his lightsaber in a cave, and gives it to Artoo. Then, like in the movie, R2-D2 and C-3PO make their way off to Jabba the Hutt’s palace.
Speaking of Jabba, this book is, to my knowledge, the first time “Hutt” was ever spelled with two T’s instead of one. And, finally, he appears as we know him from the movies. He’s a big ol’ giant ol’ ugly ol’ slug. Not a human. Not a… yellow… guy… He’s normal Jabba the Hutt. However, when describing Jabba in the first chapter of the book, Kahn writes: “He had no hair–it had fallen out from a combination of diseases.” So, apparently, Jabba the Hutt had hair once. I can’t picture him looking anything but ridiculous with hair on his head, which is why I kind of love this random detail.
For me, the best parts of the book were parts where we got to get into the heads of the characters a little more. Through the narration we get to know and understand the characters better than we do in the film. For example, it is pretty obvious right away that Leia is in-tune with the Force (though she doesn’t know it), as there are many times throughout the entire story where she connects with the Force unknowingly. These are things that cannot be shown in a movie. We only learn about them through reading.
Another thing that this book did great that the film couldn’t do was describe to us Luke’s struggle with the dark side of the Force. The dark side is really starting to creep into Luke’s life here, and not just at the end of the book during his confrontation with Vader and the Emperor, but there are hints of darkness from the very beginning. Here’s an example:
“[Luke] found Jabba despicable–a leech of the galaxy, sucking the life from whatever he touched. Luke wanted to burn the villain, and so was actually rather glad Jabba had refused to bargain–for now Luke would get his wish precisely. Of course, his primary objective was to free his friends, whom he loved dearly; it was this concern that guided him now, above all else. But in the process, to free the universe from this gangster slug–this was a prospect that tinted Luke’s purpose with an ever-so-slightly dark satisfaction.”
And then, a few pages later:
“The deck gunners were lining up . . . their shots for the coup de grace, when Luke stepped in front of them, laughing like a pirate king. He lit his lightsaber before they could squeeze off a shot; a moment later they were smoking corpses.”
Though still the clear hero and protagonist of the story, darkness is beginning to overtake the light, and Luke is enjoying it. Towards the end of the story this becomes much worse, as we realize how close Luke almost came to actually turning to the dark side while in the Emperor’s presence, like his father did at the end of the Clone War. “In this bleak and livid moment, the dark side was much with him.”
In the Expanded Universe, in a comic series set a few years after Return of the Jedi called Dark Empire, Luke actually does fall to the dark side for a short time before turning back to the light. I guess his struggle wasn’t over after the Death Star blew up.
This novelization includes another deleted scene from the movie of when Luke, Han, Leia, Lando, Chewbacca, R2-D2, and C-3PO are all walking back from Jabba’s palace to their ships through a sandstorm (and in the words of nine-year-old Anakin Skywalker: “Sandstorms are very, very dangerous!”). It doesn’t add much to the story, and it’s easy to see why it was cut from the movie, but it did offer some great moments and good dialogue. It was a welcome addition to the book for sure.
Many moments are expanded upon and leave us with some great new insights about the story. Early on in the book we learn more about Darth Vader’s desire to kill Emperor Palpatine and rule the galaxy in his stead, with his son at his side.
We learn that Obi-wan never told Luke about his real father because Yoda forbade him from revealing the truth to him.
When Obi-wan appears to Luke, he says “If I was wrong in what I did, it certainly wouldn’t have been for the first time. You see, what happened to your father was my fault.” Obi-wan blames himself for Anakin’s fall to the dark side. Like in the movie, Obi-wan tells Luke that he believed he could train Anakin as well as Master Yoda. He then says “My pride had terrible consequences for the galaxy.”
He regrets training Anakin. He was told not to train Anakin in The Phantom Menace, but he still did, against his own better judgment, because he promised Qui-Gon that he would. He trained the boy anyway, taught him about the Force and how to be a Jedi knight, and then Anakin became a Sith Lord. Obi-wan thinks this is all his fault. Man, he’s being pretty hard on himself.
The scene goes on, and it is one of my favorite scenes in the novel, because Obi-wan tells Luke more about Anakin than what he told in the movie:
You should not think of that machine as your father. When I saw what had become of him, I tried to dissuade him, to draw him back from the dark side. We fought . . . your father fell into a molten pit. When your father clawed his way out of that fiery pool, the change had been burned into him forever–he was Darth Vader, without a trace of Anakin Skywalker. Irredeemably dark. Scarred. Kept alive by machinery and his own black will . . .
Sound familiar? Like how the novelization of A New Hope basically summarized the entire prequel trilogy in its prologue, this novelization of Return of the Jedi once again shows us just how much of the prequel trilogy George Lucas already had in mind when making the original trilogy. It’s pretty fascinating to me. And reading this really made the two trilogies feel more connected. Having old Ben Kenobi describe a scene to Luke from Revenge of the Sith is kind of awesome, especially since the book came out more than 20 years before Revenge of the Sith premiered in theaters.
One of my favorite things about reading these old novelizations of the original Star Wars trilogy is trying to pick out the differences between the films and the novels. Luke flew in Blue Squadron in the A New Hope novelization, Yoda was blue in The Empire Strikes Back novelization. Something had to be blue in this book that wasn’t blue in the movies, right?
But there were still a bunch of things that didn’t quite match up with what we see in the movie.
I’m gonna jump right to the biggest, most well-known difference: Obi-wan Kenobi and Owen Lars are brothers. Uncle Owen is Obi-wan’s brother, instead of Anakin’s stepbrother. There’s not much else to say about this. Obi-wan simply says “I took you to live with my brother Owen, on Tatooine.” That’s all that is said about it. Obi-wan and Owen are brothers in this version of the story.
Which leads into the next big difference that I noticed: not only does Leia remember her mother, but Luke does too. Luke and Leia both somehow remember Padmé even though she was only alive for like the first five minutes of their lives. Apparently Padmé lived for much longer in this version of the story. When Obi-wan appears to Luke on Dagobah, he tells Luke a little about his mother. He says “When your father left, he didn’t know your mother was pregnant. Your mother and I knew he would find out eventually, but we wanted to keep you both as safe as possible, for as long as possible. So I took you to live with my brother Owen, on Tatooine . . . and your mother took Leia to live as the daughter of Senator Organa, on Alderaan.” Leia has many memories of her real mother. In this book it makes more sense than it does in the movies, now that we’ve seen the prequels.
One thing I praised the novelization of The Empire Strikes Back for was how it depicted Vader’s relationship with the Emperor. In that book, Darth Vader was terrified of Emperor Palpatine. I loved that detail and hoped to see it expanded upon in this book. But, Vader doesn’t seem afraid of Palpatine in the slightest in this novelization. He respects him, but it doesn’t seem like he fears him. Though this is more true to the movies, I was hoping it would be different. I liked the idea that Darth Vader lived in constant fear of his Master.
During the confrontation between Luke and Vader on the Death Star, Luke tells Vader “You could not bring yourself to kill me before–and you won’t destroy me now.” This happens in the movie. It is a line most people would be familiar with. What is different, however, is that afterward the author goes to write “Twice before, in fact–to Luke’s recollection–Vader could have killed him, but didn’t. In the dogfight over the first Death Star, and later in the lightsaber duel on Bespin.” Seems accurate, right? Well, this one line shows that the Star Wars Expanded Universe was still not being acknowledged by official media at this point. If we take the Star Wars Expanded Universe into consideration, there was a third confrontation where Vader did not kill Luke in a duel on the planet Mimban, in the book Splinter of the Mind’s Eye.
Another thing that stuck out to me while reading was that the name “Palpatine” was used many times in this book, both in the narration, and in character dialogue. Despite the name also appearing in the novelization of A New Hope, the Emperor’s name is never once uttered in any of the three movies in the original Star Wars trilogy. For this reason, little-kid-me who was young Ani Skywalker’s age when The Phantom Menace was released had no idea that Senator Palpatine was the man who would become the Emperor. I don’t think I knew this until the trailer for Revenge of the Sith made it clear. Now it seems so obvious, but I was a kid at the time and the name “Palpatine” meant nothing to me. I find it interesting how often his name was used in this book.
I could keep going on, and mention every little thing I liked about this book, and talk about every little detail that I found interesting. I think I’ve already done that enough. But, I do want to say that my favorite part of the entire book is at the end, after Vader threw the Emperor to his death, when he asks Luke to take his mask off. This scene was written so beautifully, and was really enhanced by allowing us to get inside Anakin Skywalker’s head as he looks at his son for the first time with his own eyes.
Tears fall down Luke’s face when he see’s his father’s real face for the first time. Anakin feels very self-conscious, and thinks Luke is crying in horror at the sight of his horribly scarred and sickly pale appearance. His mind starts to wander. He remembers what he used to look like: “striking, and grand, with a wry tilt to his brow that hinted of invincibility and took in all of life with a wink. Yes, that was how he looked once.” Ah, yes, just like Hayden Christensen!
These memories lead to more memories. Anakin thinks back to his time as a Jedi. He thinks about Padmé, and he thinks about Obi-wan. Then, he thinks about molten lava crawling up his back, and at that moment he stops, not allowing himself to think of such terrible things.
Anakin looks back up at Luke, and the scene is described like this:
“The boy was good, and the boy had come from him–so there must have been good in him, too. He smiled up again at his son, and for the first time, loved him. And for the first time in many long years, loved himself again, as well.”
Still believing that look is disgusted by his physical appearance, Anakin echos the words of Yoda, saying “Luminous beings are we, Luke–not this crude matter.”
The rest of the scene plays out like it does in the movie. But these extra details really made this scene so much more powerful. Knowing exactly what Anakin was thinking in these last moments of his life, knowing the memories that were coming to his mind and the emotions that he was feeling before he died made reading this small section of the novel a real treat. These are things we can’t be shown on film, and it is one of the rare moments where the novel really outshines the movie.
For whatever reason, I really enjoyed this novelization. I complained that the novelization of Empire Strikes Back didn’t really add anything new to the story, and this novel is guilty of the same thing in most instances, but there’s something about Kahn’s writing style that did a great job of pulling me in, even though I already knew the story. That, combined with the moments I’ve pointed out that let us get into the heads of the characters, which are the few moments that do provide us with extra details that the movies do not, makes for a genuinely entertaining read.
If you’re really just interested in getting “new” information, then this review is probably all you need to read, but if you’re just looking for a well-written novelization of a movie you like, then yes, definitely read this one. I certainly enjoyed it.
The star cruiser’s almost fixed. We’re gonna have to say goodbye.” – Cindel Towani
Well, I’ve been putting this one off. I had the goal of watching and reviewing all existing Star Wars spin-off movies before Rogue One opens in theaters, but turns out I really didn’t want to watch this one. I had seen it once before, and I only remembered two things about it. First, I didn’t like it. Second, there’s some weird witch lady in the movie who can turn into a crow. So, I wasn’t thrilled about sitting through the movie again, but I finally got myself to do it.
Ewoks: The Battle For Endor is the sequel to Caravan of Courage: An Ewok Adventure that had come out a year earlier. Like the first film, this was made-for-TV. It aired on ABC on November 24th, 1985.
For not wanting to watch this as much as I did, this movie caught me off guard. This movie is actually far better than the first Ewok movie. I don’t know why I remembered hating this one specifically so much, but it is actually a much more entertaining film than the first one. Maybe I had the two movies confused in my memory. Who knows. When I watched the first movie a few weeks ago I realized that it actually wasn’t that bad, and this one is even better. Does that mean it’s a good movie? No, not really, but it was enjoyable for what it is: an ’80s fantasy movie made for children.
This movie is a direct sequel to Caravan of Courage, so let’s recap what happened in that movie a little bit. In Caravan of Courage, the Towani family star cruiser crash lands on the forest moon of Endor. The Towani family consists of two children, Mace and Cindel, and their parents. Their parents go missing shortly after the crash, and Mace and Cindel take it upon themselves to go find them. They befriend some Ewoks–including Wicket, the Ewok who befriends Leia in Return of the Jedi–who tag along to help them get their parents back. They eventually find and rescue their parents from the evil Gorax. They have a happy reunion, and the movie ends.
Ewoks: The Battle For Endor picks up right where the first movie left off. The family is back together, and the childrens’ father, Jeremitt, is doing some last-minute repairs to their ship so that they can finally leave the forest moon. Cindel is walking through the forest with Wicket, who can apparently have entire conversations speaking semi-fluent English now. Suddenly, an army of strange alien creatures (called “Sanyassans” apparently. Thanks, Wookieepedia!) raids the Ewok village and starts burning the dwellings and attacking those who live there. The Sanyassans, along with a creepy witch named Charal, find Jeremitt and insist that he gives them the “power of the stars.” Jeremitt has no idea what they are talking about. They pull apart the ship until they find a power cell, which is apparently what they were looking for.
Then, THE SANYASSANS KILL CINDEL’S ENTIRE FAMILY.
Cindel is a five-year-old little girl, and her whole family is killed at the very beginning of this movie, including her brother, Mace, who was one of the protagonists of the last film! Whose idea was this?! The whole plot of the last movie was that Cindel and Mace were trying to reunite their family, and they finally succeed at the end of that movie, only for everyone but Cindel to get murdered at the beginning of the next movie. Are you kidding me? This is brutal! This is basically the same thing that happened in Alien 3. In Aliens, Ellen Ripley risks everything to save a little girl named Newt from the Queen Xenomorph, the biggest and baddest alien out there. They barely escape, along with Corpral Hicks, a U.S. Marine who helped fight the aliens in the movie. Ripley, Hicks, and Newt all make a safe escape off-planet, and enter hypersleep on their ship as they fly to safety. The movie ends on a happy note. Then, Alien 3 starts with their ship crash-landing and Hicks and Newt die in their sleep, off-screen. What the hell?! Who thinks immediately killing off the heroes of the previous movie is a good way to start the sequel? Cindel doesn’t seem that sad about her entire family being dead though, so I guess it’s okay.
Anyway, Cindel is now on her own, and she is captured by the Sanyassans. The Sanyassans look like a cross between the Yuuzhan Vong, the goombas from the live-action Super Mario Bros. movie, and Sarris, from Galaxy Quest. In other words, they look weird. Cindel is reunited with Wicket, who was also captured, and the two escape into the forest.
Cindel and Wicket find a strange rodent creature named Teek, who can run super fast. They follow Teek to a house in the middle of the forest. The house appears to be abandoned, so Cindel and Wicket decide to clean it up and live there themselves. They’re wrong though, and the owner of the home–an old man named Noa–returns and angrily tells them to get lost.
Is Noa the only person in Star Wars to wear glasses? Are glasses canon? Who knows!
Noa eventually feels bad and lets the two of them stay with him. Noa crash landed on the moon of Endor a very long time ago, and has never been able to leave because his ship’s power cell is broken.
One day, Cindel hears a strange voice calling her name. She wanders off into the forest to find whoever’s calling to her. She finds a pretty woman in a long white dress and with a white horse. This woman reminds me of Mombi from Return to Oz, the first time Dorothy meets her when she still has her nice head on (if you haven’t seen it, don’t ask…). Then the woman transforms into the witch, Charal. Now she reminds me of Mombi when she puts her angry head on becomes super evil. Charal kidnaps Cindel and brings her to the fortress of the Sanyassans.
Oh yeah, did I mention that Charal has the ability to transform into a crow? Y’know, because she’s a witch. Wait, are crows canon?!?!
…are horses canon?!
Oh wait, the last movie had horses…
The moon of Endor is just full of Earth animals.
Charal takes Cindel to who I assume is the king of the Sanyassans. He tells Cindel to activate the “power of the stars” (the power cell they stole from Cindel’s family’s ship) for them with magic, but she’s a five-year-old and she doesn’t have a clue what he’s talking about, so they lock her up. They also lock up Charal, and take her magic ring that allows her to turn into a crow.
Noa, Wicket, and Teek find their way to the fortress and are able to unlock Cindel’s cell and break her out. Wicket is about to open Charal’s cell too, but Cindel takes the keys from him and throws them down a drain, saying he can’t free her because she’s evil. Yeah! Take that!
So they take the power cell and escape the fortress, and then suddenly this movie becomes The Lord of the Rings. A huge army of Sanyassans, with their swords and armor, gathers together and rides off on horseback to find the Cindel and her friends. They chase them into the forest and a battle breaks out between the Sanyassans and the Ewoks. This really does feel like a low-budget Lords of the Rings battle scene mixed with the Ewok vs Stormtrooper battle from Return of the Jedi. It’s actually kind of cool! And it’s extra fun, because in this movie, the Ewoks use guns instead of rocks! Ewoks with blasters. So good! When are we going to get Battlefront DLC of this??
Noa and Cindel run inside Noa’s crashed ship. They start shooting the Sanyassans with the ships turrets and it’s great because who wouldn’t want to see a Lord of the Rings movie where halfway through the battle a spaceship starts shooting up the battlefield?
Long story short, eventually the plug the power cell into the ship, and Noa and Cindel are finally able to leave the moon of Endor. They all say their goodbyes to their friends. Cindel and Wicket have become best friends and Cindel is way sadder about saying goodbye to him than she ever is about the deaths of her entire family. The ship flies off, and Wicket and Teek run after it, with Wicket shouting “Cindel! Bye Cindel!” It’s actually very touching and kind of sad and I hate that a movie like this can make me feel sad.
The ship flies off into the distance, and the movie ends.
There are some cool things about the movie. The special effects are pretty great for a low-budget made-for-TV movie from the ’80s. Obviously they aren’t anywhere near as good as the effects in an actual Star Wars movie, but they’re still pretty good. There are more alien species and creatures than there were in the first movie, and they all look pretty cool. I was especially impressed with Teek, the little rodent character. The costume and effects used to bring that character to life looked really good.
I still can’t get over all the Earth animals that are on Endor. We’ve now seen llamas, horses, crows (well, at least one crow who is actually a witch), chickens, and more on Endor. It’s kind of like if Noah’s ark was actually a spaceship, and that spaceship flew to a galaxy far, far away, and landed on the moon of Endor.
Wait a minute… Could the Noa in this movie actually be the Biblical Noah? Both stories take place a long time ago. Wow, it makes so much sense!
And, wait a minute! In the Bible, in the 28th chapter of Samuel, Saul goes to meet “the Witch of Endor.” Witch of Endor?… you mean like the witch on Endor who is in this movie??
Wow! Turns out Ewoks: The Battle For Endor is actually a sequel to the Holy Bible!
One interesting thing that was apparently later clarified is that Charal, the witch, is actually a Nightsister from the planet Dathomir. The Nightsisters are a group of female witches who practice dark magic using the Force. Asajj Ventress is the most well-known of the Nightsisters. The Clone Wars taught us that the Nightsisters actually raised Darth Maul. The Nightsisters were first introduced in 1994, in Dave Wolverton’s novel The Courtship of Princess Leia. Obviously, that was almost a decade after this movie was released, so calling Charal a Nightsister is just a big ol’ retcon, but it’s still kind of a cool detail.
This movie has more going on than the last one did. It’s faster-paced, which for me makes it more entertaining to watch. Though I wouldn’t ever choose to watch this on my own, I could definitely see myself watching it with younger children, and I think it is something that most kids would enjoy watching if they enjoy fantasy stories or big teddy bears.
You know what really bugs me though? Why can Wicket speak English?! Why?! This movie supposedly takes place before Return of the Jedi, but Wicket can’t speak English in that movie! Why couldn’t he have a conversation with Leia? How did he forget English? Why does this bother me so much?! It’s a kid’s movie! I DON’T CARE I WANT EVERYTHING TO MAKE SENSE.
This actually isn’t the only time this happens in Star Wars. In one episode of The Clone Wars, our favorite shooting-first-friend Greedo makes an appearance, and he speaks in fluent English the entire episode. Okay, if Greedo can speak English, they why doesn’t he speak English with Han in A New Hope, instead of having the weird two-language conversation that they have in the movie?
The easy answer to both of these questions is that this movie and that show are made for kids, and kids don’t want to read subtitles. But still, the continuity-conscious part of me really hates this stuff. Wicket and Greedo both speak English, but they don’t speak English in the regular Star Wars movies. Okay. Weird.
Overall, this is a pretty good movie, all things considered. It’s made for kids, and the acting is poor, and the story is weird, but it’s still pretty entertaining for what it is. This is the better of the two Ewok movies, for sure. This is a good movie to watch with your kids. If I had seen this movie as a kid I’m sure I would have loved it. Seeing it for the first time as an adult is kind of weird, but it reminds me of the kinds of movies I used to love when I was growing up.
This movie adds nothing important to the Star Wars universe as a whole, but it’s still a cute movie. If you want your Star Wars movies to “matter” in the overall story of Star Wars, then the only spin-off movie you should watch is The Clone Wars. With that said, I actually think Ewoks: The Battle For Endor is a better movie than The Clone Wars, even though The Clone Wars is actually a somewhat important chapter in the story of Star Wars as a whole, especially since it acts as an introduction to Ahsoka Tano.
This movie’s not great, but it’s not bad, especially if you’re going to be watching it with younger kids.
“It’s people like you who continue to inspire me to play a part in exposing the Empire’s machinations. Not everyone understands the sacrifices necessary to stop them. If we don’t use every opportunity, every secret, every weapon available to stop them, how can we face our children? How can we hand them a future with such injustice?” – Saw Gerrera
This is weird for me. A new Star Wars movie is coming out in just over a week, and I just read a lead-in novel for it. I’ve never gone into a new Star Wars movie with real background knowledge from tie-in books before. Though there was a novel called Labyrinth of Evil (also by James Luceno, I might add) that led directly into Revenge of the Sith, and I almost bought it before seeing the movie, I decided against it, making Catalyst: A Rogue One Novel my first time reading a Star Wars novel that is meant as a prequel to a movie, before seeing the movie.
Like with the Ahoska novel that I recently reviewed, I expected something different than what I got with this book. With Ahsoka, I expected an immediate continuation of Ahsoka’s story following her last appearance in The Clone Wars TV series, but that was not at all what the novel was. With Catalyst, I expected a story that would take place much closer to the actual events of the upcoming movie. Instead, Catalyst starts during the Clone Wars.
Galen Erso is essentially the main character in this story. He is the father of Rogue One protagonist Jyn Erso, though when this novel starts Jyn isn’t born yet. This is another thing that caught me off guard. I didn’t expect this to be a book about Jyn’s father. I thought it would be about the main rebel characters we keep seeing in all the Rogue One trailers. I have to say, I’m actually happy it didn’t end up being like that.
Though the novel starts during the Clone War, there are no Jedi in this story. They are mentioned, but never seen. I liked this touch, because the movie is being branded as the first Star Wars movie without Jedi in it (*cough* except for the Ewok movies… *cough*). It’s nice to get some Star Wars stories about “normal” people for once. Not even Vader or the Emperor make an appearance. There are no Force-users in this story, light side or dark side.
The story centers on Galen Erso, a scientist (played by Mads Mikkelsen in Rogue One) who specializes in kyber crystal research in hopes of discovering a way to bring renewable energy to systems that need it. I briefly talked about kyber crystals in my review of Splinter of the Mind’s Eye, which was the first Expanded Universe Star Wars novel ever written. In that review I said that kyber crystals are lightsaber crystals in the Star Wars canon, and that they also power the Death Star. The Jedi see kyber cystals as sacred, and have kept the crystals mostly to themselves, preventing them from being thoroughly studied.
Enter Orson Krennic, the man in the white Imperial uniform who we keep seeing in the movie trailers. Krennic works for the Republic (remember, this starts during the Clone War, before the Empire exists). Krennic is part of the Republic’s Special Weapons division, and he is one of the very few people in the galaxy who knows about Palpatine’s plans to build a superweapon / space station that will go on to be known as the Death Star. When they were younger, Orson Krennic and Galen Erso were both part of the Republic’s Futures program, where exceptionally talented young people studied and worked for the Republic in different fields of expertise. Krennic remembers Erso from those days, and knows that with his experience studying the kyber, Erso would be a tremendous help in the development of the Death Star’s superlaser.
Galen Erso is politically neutral, wanting nothing to do with either the Republic or the Separatists, and works for a company that has no allegiance to either side of the war. Eventually, Krennic is able to convince Erso to begin doing research on the kyber crystals, telling him it is for an energy renewal project, when in reality it is for the weaponization of the crystals to be used for the Death Star.
This is not the most exciting Star Wars story in the world. It’s not an adventure story, and there’s little action. In a way, Catalyst is more of a history lesson on the development of the Death Star than anything else. Part of me wants to be disappointed by this, but there is another big part of me that loves getting this background information. We get to know Galen Erso and his wife, Lyra Erso very well, and we even get to meet a very young Jyn Erso. We get to know Orson Krennic, and we get to see some other characters who will appear in the movie. I’m eager to see what watching the film will be like, knowing all of this background information about the characters and their motives. The story is very character driven, and it works.
While the purpose of this novel is to tie-in with Rogue One, Luceno does a great job of connecting it with other Star Wars stories as well, making reference to other novels in the canon, and to The Clone Wars. There were little details that made me happy too, like the brief appearances of certain alien species like the Ryn, who first appeared in Luceno’s Agents of Chaos duology in The New Jedi Order book series, and the Tynnan, who are otter-like creatures from Brian Daley’s Han Solo novels (plus, the Tynnan appeared in the Corporate Sector of the galaxy, which was the setting of Daley’s novels). Though the novel is a prequel to Rogue One, it also feels like somewhat of a prequel to Luceno’s 2014 novel Tarkin, as Governor Wilhuff Tarkin plays a fairly big role in this story, showing us some of the events that took place in his life prior to his eponymous novel.
Catalyst takes place over the span of only a few years, starting during the Clone War and ending in the early years of the Empire’s hold over the galaxy, so there are still many years between the end of this novel and the upcoming movie which takes place immediately before the original Star Wars movie. Like in Ahoska, Tarkin, and a few other novels set in between Star Wars trilogies, this novel does an excellent job of showing us the damage that the Empire is doing to the galaxy. Worlds are being occupied and scourged, people are being killed, and most of the galaxy is unaware of it. These stories make the fight against in the Empire that we see in the original Star Wars trilogy feel so much more justified, and it makes every victory that the Rebellion has over the Empire feel that much more satisfying. We know the Empire is bad from the movies, but these stories show us that the Empire is really, really bad. And I love it. Having more reasons to hate the bad guys is always fun.
Whether you’re reading this before or after you’ve seen Rogue One, if you’re looking for background information on some of the characters and events seen in the movie, then I would definitely recommend this book. Having not seen the film yet, I feel I already have a good grasp of who the Ersos are, and of who Orson Krennic is. If you’re just looking for a new Star Wars book to read, and you don’t really care about the movie tie-in, then this might not be at the top of my recommendation list unless you’re fascinated by the development and history of the Death Star (which I totally am).
Catalyst was a good book, though it is one of the weaker Luceno novels I’ve read. I definitely enjoyed it, but I don’t know that it is exciting enough to hold the attention of more casual Star Wars fans. It’s just a little too slow-paced I think. James Luceno is one of my favorite Star Wars authors out there, so I’m always very excited to check out anything Star Wars with his name on it, and this book didn’t disappoint, but holding it up to his other novels, and to a lot of the other books in the overall Star Wars canon, this wasn’t the best. I liked it, but I don’t see more casual readers enjoying it as much as I did. Still, I this book is worth checking out. This book definitely did it’s job of making me even more excited to see Rogue One! December 16th can’t come soon enough! Especially after reading this book.
“If you’re not a Jedi, then what are you, Ahsoka Tano? Because to be honest, you still sound and act like a Jedi to me.” – Bail Organa
Ahsoka is the canon novel I have been the most excited about, ever since it was announced (well, until Timothy Zahn’s upcoming Thrawn novel was announced, at least. I’m dying to read that one). Though I did my fair share of complaining in my review of the 2008 Clone Wars movie, and even complained about not liking Ahsoka Tano in the movie, at the end of that review I wrote about how Ahsoka eventually became one of my favorite Star Wars characters of all time. She still is, so I couldn’t wait to read this book.
Ahsoka was written by E. K. Johnston, a newcomer to Star Wars literature. Part of me is always excited about reading Star Wars from a new author, though I won’t deny how much more excited I get when my favorite Star Wars authors of the past come back to write new stories. But, after having read this book, I’m glad to say that E. K. Johnston is a good fit in the Star Wars universe, and I would love to see more Star Wars stories from her in the future.
Ahsoka was released on October 11th, 2016. The novel takes place about one year after Revenge of the Sith, and gives us a glimpse into what life was like for Ahsoka Tano in the aftermath of Order 66. One thing I love about the new Star Wars canon is that it isn’t shying away from the time period in between the first two Star Wars trilogies. The Expanded Universe (now “Legends”) rarely told stories in between Revenge of the Sith and A New Hope. In the new canon, we’re getting plenty of these stories (most notably with the upcoming movie Rogue One, and the ongoing TV series Star Wars Rebels), and the gaps are beginning to get filled in.
With this book, I did something that I have never done before; I listened to the audiobook instead of reading the physical novel. Usually, I hate audiobooks, but when I heard that this one was narrated by Ashley Eckstein, the voice actor for Ahsoka Tano in The Clone Wars, and Rebels, I couldn’t resist. I was traveling all week for Thanksgiving, and I thought this would be a good thing to listen to as I was driving. Usually, when I read a book that I’m going to review, I take notes as I’m reading. I couldn’t take notes while I was driving, so my thoughts are pretty scattered. I might not be able to go into as much detail as I would like because of it, but my opinion of the book should still be clear.
The prologue of the novel takes place just before Revenge of the Sith. Ahsoka is on a mission to capture Darth Maul, who has overtaken the planet Mandalore. Though she left the Jedi Order in The Clone Wars fifth season finale, she is still working alongside them for the good of the Republic. She recently said goodbye to Anakin Skywalker, who has been called away to Coruscant to rescue Chancellor Palpatine from General Grievous, which is where Revenge of the Sith starts off. Ahsoka finds Maul, and the two briefly fight before Ahsoka springs her trap and captures the former Sith Lord. Though we don’t find out what happens next, because chapter one takes place a year later, this prologue was a treat to read because it continues Darth Maul’s story that was never finished in The Clone Wars or in the follow-up comic Darth Maul: Son of Dathomir, and provides us with some connecting tissue between that story and Darth Maul’s later appearance in Star Wars Rebels, where he mentions this encounter with Ahsoka.
In the first chapter of the book, the very first Empire Day celebration is about to occur. It is the one-year anniversary of the formation of the Galactic Empire, though Ahsoka remembers it as the anniversary of the Great Jedi Purge. She mourns the loss of the Jedi Order, of the Republic, and of her friends. She believes Anakin and Obi-wan to be dead. All of the Jedi are dead. She has gone into hiding, no longer using her Force abilities, in fear of being seen and hunted down by the Empire. She no longer goes by her real name, and instead goes by “Ashla” (which is a weird name for someone who is trying to hide her Jedi roots, since “Ashla” means “the Light Side of the Force” in the Star Wars universe). It reminds me a lot of Kanan Jarrus in the novel A New Dawn. In that story, Kanan, another survivor of Order 66, has also gone into hiding and is trying to blend in with “normal” people, no longer using his real name (“Caleb”), ignoring his Force abilities, hiding is lightsaber, and trying to cut all ties to his Jedi past so that the Empire doesn’t find him. Their situations are very similar.
Ahsoka eventually finds her way to a small farming moon in the Outer Rim called Raada (pronounced “rah-aida”), where she tries to start a new life as a mechanic. The moon is out of the way and relatively unknown, and is somewhere the Empire would never have a reason to look for her. She meets a girl named Kaeden who she quickly becomes friends with, even though she doesn’t want to get attached to anyone, and she doesn’t want anyone to get close to her as she tries to live life as inconspicuously as possible. The less connections she makes with others, the safer she (and they) will be.
The Empire eventually makes its way to Raada anyway, and instead of running, Ahsoka decides to try to help the people there–her new friends–and to do it while still hiding her Jedi abilities.
There are a few interludes scattered throughout the book. Most of them are flashbacks that deal with parts of Ahsoka’s past. We learn a little bit about her life before joining the Jedi Order, and we get some new insight into her time as a Jedi. Some of the interludes include some familiar faces from the movies or TV series. These interludes are very interesting, and help to flesh out Ahsoka and the other characters who appear in them. I feel like I can’t say too much about this story without giving a lot of it away, but I was very satisfied with the book as a whole. The first half of the novel was pretty good, not amazing, but it held my attention. It really picked up in the second half though, and I really loved all the connecting threads it made between The Clone Wars, Star Wars Rebels, and the first two Star Wars trilogies. In a way, both of the TV series have always felt sort of separate from the movies, but this book made them all feel very connected, which was something I loved about it.
There are many cool details in this book. We get to see how Ahsoka got her white lightsabers that we see in Star Wars Rebels, and we learn a bit more about lightsaber construction in general, and how Dark Side Force-users get their blades to turn red. We get to see what the galaxy is like during the first year of the reign of Emperor Palpatine. We get a look inside Ahsoka’s head, which gives us greater insight into who she is and how she thinks.
Even disregarding the character of Ahsoka Tano, this book really sets the stage for things to come in the Star Wars universe after the formation of the Empire. There is no Rebel Alliance yet, but we get to see some of the earliest stages of organized rebellion taking shape. If you read the other canon novels that take place in between Revenge of the Sith and A New Hope, you can see how this rebellion slowly but surely starts becoming the Rebel Alliance that we see in the movies. This is very fun to see, especially with familiar faces like Bail Organa at the helm.
Along with seeing the Rebel Alliance take form, this book, and the other novels in the canon, do a fantastic job of showing the oppression of the Empire. We don’t see this in the movies. We hear about it, the characters in the movies know about it, but we as the audience never get to see what the Empire is really like, because most of the original Star Wars trilogy takes place on uninhabited or undeveloped worlds. In these stories, we get to see how brutal life under the Empire really is, and these stories actually strengthen the movies quite a bit because of it.
This book was very entertaining. Though I listened to the audiobook, I’d still love to go back and read the book on my own (hearing Ashley Eckstein voice Ahsoka Tano was great, but hearing her voice every other character in the entire novel–especially characters we’ve seen on-screen before–was a little bit silly. This is one of the main reasons I avoid audiobooks in general). Ahsoka truly is one of my favorite characters in the Star Wars universe, and getting a whole novel about her was a huge treat. Ever since seeing Ahsoka walk away from the Jedi Order in The Clone Wars, I’ve always wanted to know what she did next. Where did she go? How did she deal with Order 66? Did she continue living as a Jedi, or not? We get answers to those questions. Getting to see her character develop from what we saw in The Clone Wars, to what she was in Rebels (which takes place approximately 15 years later) is very cool, and leaves me hoping for more Ahsoka stories in the future.
As a huge fan of the character, and as a huge fan of little universe-building details and connecting tissue between the TV shows, movies, and other canon stories, I really enjoyed this book. It’s a short one, much shorter than your standard adult Star Wars novel, which makes it a great book to read if you don’t have much free time to commit to reading. E. K. Johnston did a very good job with this, and most importantly, did justice to the character of Ahsoka Tano. If a writer can’t write a character in a way that feels like what we’ve seen on-screen, that can ruin a story. Luckily, Ahsoka feels like Ahsoka in this book, and so do the other characters who we’ve seen before.
I have one minor gripe about the audiobook version of the novel, which doesn’t affect my opinion of the novel itself or alter the score I’m giving it, but it was something that bothered me. Star Wars audiobooks are cool because they generally have Star Wars music and sound effects playing in the background. This audiobook was no exception, but the thing that annoyed me is that even though we were getting familiar Star Wars themes from the movies playing in the background, in a book called “Ashoka” we never, ever hear Ahsoka’s theme music from The Clone Wars and Rebels, and instead we get themes that feel out of place, like Padmé’s theme, even though she’s not in this book, or even alive at this point in the Star Wars timeline. Having Ahsoka’s theme in the audiobook would have been a huge plus. Oh well.
If you’re a fan of The Clone Wars and Rebels, then I definitely recommend this book. If you don’t care much about either TV series, you probably won’t get the same level of enjoyment reading this, but you’ll still probably appreciate it for the way it builds the universe in between the movie trilogies and fills in some of the gaps in the story. Now that this book is out, and there’s no sign of Ahsoka reappearing in Rebels anytime soon, we might be done with Ahsoka Tano stories for a while. The book does leave room for a potential sequel, or continuation of the storyline in some form, so I hope we get more eventually, but this book definitely satisfies my want for more Ahsoka, for now.
“We came on a star cruiser and we crashed . . . Don’t you have a star cruiser?” – Cindel Towani
Well, I committed to reviewing the rest of the Star Wars spin-off movies, so here goes. The thing I never realize when I decide to do something like this, is that reviewing them means that I have to actually watch them! I haven’t seen this movie in a very long time, and I wasn’t particularly excited to sit down and watch it again.
Caravan of Courage: An Ewok Adventure came out in 1984, just one year after Return of the Jedi. It was a made-for-TV movie that was aimed at children, though it was eventually released on home video as well (however the last time it was released was in 2004 on DVD, so there is no blu-ray version available).
The story takes place a few years before Return of the Jedi. Wookieepedia places the movie in the year “3 ABY” so I’m just gonna go with that. This means it takes place around the same time as The Empire Strikes Back. This is all pointless information though, because there is no real connection between this movie and the main-saga Star Wars movies other than the shared setting of the Forest Moon of Endor, and a few Ewok characters who appeared both in this and Return of the Jedi.
The movie starts up with no opening crawl, just like every other Star Wars spin-off movie, apparently including the soon-to-be-released Rogue One. This movie is interesting though because it is narrated by the snowman from Rudolph the Red-Nosed Reindeer (Burl Ives). A narrator in a Star Wars movie seemed like a weird choice at first, until I realized that this is a movie about Ewoks, who don’t speak English, and nobody wants a repeat of The Star Wars Holiday Special where you just have to sit through scenes of unintelligible Wookiee noises for ten minutes.
The Towani family star cruiser has crash-landed on the moon of Endor. A boy named Mace and his much younger sister, Cindel, end up alone when their parents go missing after the crash. These two kids are the main characters in the movie. It gives me some serious Anakin Skywalker Phantom Menace flashbacks. At first, the kids really annoyed me, especially Cindel, who is about five years old. The bad acting stopped bothering me as much when I just sat back and took this movie for what it is: a made-for-TV kids movie. (Sorry, that exact same realization was still not enough to save the Holiday Special.)
The two kids are found by a group of Ewoks. Warwick Davis reprises his role of Wicket, the little Ewok who finds Leia in Return of the Jedi. The kids follow the ewoks to their village, which is on the ground instead of in the trees. These Ewoks raise animals, including horses, goats, rabbits, chickens, llamas, and more, so it kind of makes sense for them to live on the ground. Seeing all of these animals in a Star Wars movie was a little bit jarring, but Obi-wan talks about ducks in the novelization of A New Hope, so who cares! (“What’s a duck?” – Luke Skywalker)
The kids are eventually able to explain to the Ewoks that their parents are missing, and the Ewoks decide to help the kids find them. Though the Ewoks don’t speak English, they eventually learn some English words from the children, including “star cruiser,” “crash,” “dad,” and a more. Why didn’t the Ewoks know any English words in Return of the Jedi then? Especially since these are the same Ewoks. Apparently when the crew was making this movie, they assumed that it took place 150 years after Return of the Jedi. Sometime after that, they changed the date, because it didn’t really make sense to have Wicket the Ewok still so young 150 years after we first met him.
There is some pretty cool (albeit, very fake-looking) stop-motion animation in this movie. The group gets chased through this forest by this pretty terrifying creature who makes really creepy noises. I feel like this would have seriously scared me as a kid. Even today, there’s something about stop-motion that just kind of creeps me out. Take the stop-motion Terminator at the end of the first Terminator movie, and compare it to the CGI Terminators from the later movies. The original stop-motion one is waaayyy creepier. It is truly a thing of nightmares. The CGI ones? Not so much. Am I the only one who thinks that? Okay, I’m getting off-topic.
The group eventually does go to an Ewok village up in the trees, just like what we remember from Return of the Jedi. Here, the group receives some magic items that are supposed to help them on their quest. Oh yeah, there’s magic in this movie. My first reaction to this is “that’s stupid,” until I remember that Star Wars isn’t actually science-fiction, and is really much more of a fantasy story. Plus, there are a lot of other instances of magic in Star Wars, including very prominent uses of magic in The Clone Wars TV series. It doesn’t make that much sense to complain about magic in a universe that has things like The Force, which is, you know, basically magic.
Though, this does leave me with one question. If the Ewoks are able to use magic, why are they so amazed by a flying C-3PO in Return of the Jedi? And why don’t they use magic in the battle against the Empire? Am I overthinking this? I don’t care!
Another interesting thing is that apparently the Forest Moon of Endor isn’t just a forest. Our group of Ewoks travels across plains, deserts, and mountains in this movie. “Forest Moon” is a bit of a misleading description I guess.
Eventually the group makes it to the cave of the evil Gorax, a giant Wookiee-like creature who trapped the childrens’ parents in a cage that is hanging from the ceiling. With the help of the Ewoks, Mace is able to jump up to the cage and climb inside it. Well, great, now isn’t he stuck in there too? Apparently not, because I guess there was a super-long rope in there! So Mace and his parents climb out of the cage with the rope. Why couldn’t his parents have climbed down on their own if they had a rope in there the whole time?? I actually rewatched this part of the movie just to make sure that Mace didn’t bring the rope up there with him. He didn’t. It was already in the cage. I DON’T GET IT.
The kids are eventually reunited with their parents and everyone seems happy and then the movie just ends. They never fix their ship and they never get off the moon of Endor.
Apparently this movie was successful enough for a sequel to be made, so one year later, Ewoks: The Battle of Endor was released. I have seen it before, but I really don’t remember what happens. Something about a witch who can turn into a crow or whatever. Sounds weird to me. But I’ll review the sequel next time!
This movie isn’t that bad. I mean, it’s not good, but for a kids movie it’s pretty decent. I honestly think I enjoyed this more than The Clone Wars movie. Maybe it’s my nostalgia for ’80s movies (almost all of my favorite movies are from the ’80s), but there is a certain charm to this movie. This is definitely something that young children would enjoy, and that adults can at least tolerate. This is a movie I would recommend to parents of young children. Other than that, I think most people wouldn’t get much out of this, as it doesn’t have much to offer, and it really has nothing at all to do with Star Wars.