Anyway, when Han thinks Leia is in danger (after the speeder bike chase), he is worried, but doesn't do anything crazy that would imperil them all; he keeps his head.
That's debatable. He's General Solo by then, and his mission is to lead a group of rebels to destroy the Death Star's shield generator. If the group fails, the Rebel Fleet will be in big, big trouble, and the entire attack -- which might mean the ultimate defeat of the Alliance -- will go down the drain. Going after his girlfriend could have easily imperiled all the rebels and destroyed their mission; they were captured by the locals after all, and were about to be barbecued. Judging by Han and Luke's reactions when they were first surrounded by the Ewoks, they didn't really know what kind of danger the local population could represent to them. What if they had found an army of human-eating giants instead? They were lucky that things worked out for the best, and that meeting the Ewoks was what ended up giving them the victory
( ... )
Ah, see, I figured they did have to account for what happened to her to see if they could figure out if she'd been captured and if any of the Imperials had gotten back to their base, because if the information that suspicious people/Leia Organa were there had gotten back, the Imperials would probably change their whole defense. Knowing what happened to Leia could help them decide whether they could continue on normally or assume the Imperials knew they were there. So I saw it as important to the mission as well as a personal thing.
But I don't know whether that's what Han was thinking, so you're right.
Even if Leia had to be found for all the reasons you mentioned -- which are very good ones -- Han didn't have to go himself. As the mission commander, he should have assigned the task to somebody else, IMHO, someone who wouldn't be so desperately missed the next day as they charged against the shield generator.
In a way, this sort of reminds me of Captain Kirk, who always insisted on being the one beaming down to dangerous planets to get into fist fights with the villain of the week, usually also taking his second-in-command with him and leaving poor Enterprise to be captained by whoever they had left behind. Some guys are just too heroic to be put in charge.
Very true. They'd all be in Gryffindor, I bet. I've been wondering what the rest of the Rebel team was up to, actually. Were they all searching, trying to have a wide search grid and get it done as quickly as possible, or were most of them just kicking back somewhere?
Of course, I also wonder what how they explained Luke's absence the next day, too. I doubt they told the Rebels he turned himself in, and, "Oh, he disappeared into the woods and hasn't been seen since" probably wouldn't work either. Maybe they said he had some weird Endorian flu? I could imagine when all the extra Imperials showed up that some of the Rebels thought maybe Luke had been captured and broke instead of that it had been a trap all along.
The more I look at it, the more I think GL just didn't work out this section all that well. I mean, it works great cinematically, but not so much with the logic. Kind of like Kirk :D
Comments 7
That's debatable. He's General Solo by then, and his mission is to lead a group of rebels to destroy the Death Star's shield generator. If the group fails, the Rebel Fleet will be in big, big trouble, and the entire attack -- which might mean the ultimate defeat of the Alliance -- will go down the drain. Going after his girlfriend could have easily imperiled all the rebels and destroyed their mission; they were captured by the locals after all, and were about to be barbecued. Judging by Han and Luke's reactions when they were first surrounded by the Ewoks, they didn't really know what kind of danger the local population could represent to them. What if they had found an army of human-eating giants instead? They were lucky that things worked out for the best, and that meeting the Ewoks was what ended up giving them the victory ( ... )
Reply
But I don't know whether that's what Han was thinking, so you're right.
Reply
In a way, this sort of reminds me of Captain Kirk, who always insisted on being the one beaming down to dangerous planets to get into fist fights with the villain of the week, usually also taking his second-in-command with him and leaving poor Enterprise to be captained by whoever they had left behind. Some guys are just too heroic to be put in charge.
Reply
Of course, I also wonder what how they explained Luke's absence the next day, too. I doubt they told the Rebels he turned himself in, and, "Oh, he disappeared into the woods and hasn't been seen since" probably wouldn't work either. Maybe they said he had some weird Endorian flu? I could imagine when all the extra Imperials showed up that some of the Rebels thought maybe Luke had been captured and broke instead of that it had been a trap all along.
The more I look at it, the more I think GL just didn't work out this section all that well. I mean, it works great cinematically, but not so much with the logic. Kind of like Kirk :D
Reply
Leave a comment