Showing posts with label dark side. Show all posts
Showing posts with label dark side. Show all posts

Wednesday, March 21, 2018

Rebels: "Shroud of Darkness" (Ep. 2.18)

-- "Don't worry; I wouldn't do anything you would do."


A note before I start watching this episode:
I always pull the image for whatever episode I'm about to watch before I watch the episode. It's a bit of a teaser for the episode in question, but, usually, the images are fairly innocuous. You know, Ezra or Kanan standing with a lightsaber or something. Oh, but not this episode! This episode gave me the above image, which is hella cool! AND this episode has Vader and Ahsoka! So, yeah, I'm stoked for this one, so I'm going to go watch it now.
And, no, I don't know who those guys are in the image above, but I certainly want to find out!

After watching:
The guys in the picture? Jedi Temple Guards. So cool...
Evidently, the Grand Inquisitor was a fallen Jedi. And, possibly, a Temple Guard. That's probably a bit of a spoiler but not so much of one that I feel bad about saying it.

This is a big episode. Ahsoka, Vader, Yoda (yes, Yoda!), and, even, Anakin. Yes, Anakin is Vader so, of course, Anakin, but it also has Anakin before he was Vader. Let me explain:
Ezra walks in on Ahsoka watching old training holograms that Anakin had made. We find out that Ezra uses them for his training, and Ahsoka tells Ezra about Anakin as she knew him, not as the most fierce warrior of the Clone Wars. It's a very touching moment.

I really loved this episode.

BUT!

I am reminded again how different this series is from Clone Wars. The very best episodes or story arcs in Clone Wars were the ones that dealt with questions, usually moral questions, but Rebels really doesn't have that. There is little to no moral ambiguity in this series. It's all about putting together a resistance movement against the Empire. It's, generally speaking, an action/adventure show. Also, there are no story arcs. Each episode is self contained. And, while I am enjoying Rebels, I miss the deeper questions that Clone Wars asked and seldom answered. The only real question we have in Rebels is whether Ezra will turn to the Dark Side or not, a question, actually, that this episode touches on.

Anyway, it leaves me feeling like my reviews for this series are nothing more than plot synopses, and I hate doing plot synopses. Anyone can do a plot synopsis.

Tuesday, September 19, 2017

Clone Wars -- "Sacrifice" (Ep. 6.13)

-- Facing all that you fear will free you from yourself.


[Hop over to The Armchair Squid for his take on this, the LAST, episode.]


A bit of foreshadowing for your final episode? Yes, please.
This, the final released episode of The Clone Wars, doesn't exactly have what one would call "closure." In fact, it might ask more questions than any other Star Wars anything. Maybe, it's hard to tell. And there will be spoilers here so, if you think you might possibly watch this episode, you should stop reading now.

First, Darth Bane. That's really all I'm going to say about that since I'm only bringing him up because Mark Hamill voiced him.

Then all the other stuff...

Yoda is faced with one of those "would you kill Hitler as a baby" kind of questions, except it's not Hitler, it's Anakin. During a confrontation with Darth Sidious, Sidious tells Yoda he can spare the galaxy from what it's going to face if he will just allow Anakin to die. Of course, it would be Yoda's first step onto the path of the Dark Side to do so... I want to leave it at that, but I'm sure you all know which way that went since we already know Yoda didn't go to the Dark Side, and we all know that Sidious and Vader conquered the galaxy.

During the episode, Yoda is told, "There is another Skywalker." Now, here's the thing: The Clone Wars is canon. That means it's Star Wars fact. Which begs the question: What does that mean, there's another Skywalker. Is it a glimpse of  the future when Yoda will tell that to Luke and it will mean something real? Does it mean there will be another Skywalker and that it's referring to Luke? Or does it mean there is another Skywalker at that very moment? In which case, is it referring to Padme or to some other unknown Skywalker?

We don't get an answer!

And with the series cancelled... Well, this episode in particular makes me wish Clone Wars had kept going. As I've said before, Rebels just isn't the same.

With that, I would say that this two-parter is definitely top five for story arcs. One of the top four, actually.


"We have failed to break Master Yoda."

Tuesday, September 5, 2017

Clone Wars -- "Voices" (Ep. 6.11)

-- Madness can sometimes be the path to truth.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]
[Well, actually, considering that we're into season six, now, probably no one new is going to sign up, BUT! Hop over to The Armchair Squid for his take on the current episode.]


Sometimes the way we answer questions is to merely remove the question one step back. This is the problem with, say, crediting aliens for creating life on Earth, or, at least, human life. The question then gets pushed back to, "Well, who created the aliens?" It's a poor way to answer a question, basically, a cop out. I feel like that's what they're doing in this arc with the question, "How do Jedi talk from the dead?"

I also feel like this is a question that doesn't need to be answered, not in any concrete way. I mean, how do the Jedi do anything? The Force. It's a mystery to those of us (all of us) who aren't Jedi. Just leave the answer at that. It doesn't need an answer.

Having said that, I think this is a really great episode and an important arc. Top 10 for sure, probably top five.
Yes, I'm biased because it focuses on Yoda, a character who really, despite always being around, hasn't received enough attention throughout the series. Just casually thinking back, I can only think of one other arc that focused on Yoda as a character.

There is a thing I like very much about this episode: It highlights the way in which people, even Jedi, are unable to think outside of the boxes they've put themselves in. When Yoda is troubled and brings his question to the Jedi Council, most of the Jedi but Ki Adi Mundi in particular, dismiss what Yoda is saying as something that is impossible. They've already decided their answers on the subject because they're certain they already have all the answers. Ki Adi Mundi goes so far as to assert that Yoda must be under the influence of the Dark Side and, mostly, the other council members don't reject that notion.

Which, of course, means Yoda has to rely on Anakin for help, seemingly the only Jedi other than Yoda who doesn't get trapped in dogma. Which isn't really a great thing for Anakin in the end, but being trapped in dogma isn't a good thing for the Jedi, either, considering what's in store for them.

Anyway... This is another of those arcs that real Star Wars fans should watch. Which is not to imply that you are not a real fan if you don't watch it, but, if your interest in Star Wars goes beyond the movies, this is an arc you should see.

Oh, one last thing...
There is a question that everyone asks (I use "everyone" loosely.): Why Dagobah?
Why did Yoda choose, of all places, to exile himself on Dagobah? This episode gives some insight into that.

Tuesday, January 3, 2017

Clone Wars -- "Crisis on Naboo" (Ep. 4.18)

-- Trust is the greatest of gifts, but it must be earned.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


This arc bounces back from last episode with an attempt to kidnap Palpatine. Obi-Wan is, of course, undercover within the group of bounty hunters attempting the kidnapping. Even so, Dooku still nearly succeeds in his attempt. Clearly, though, this is not the abduction attempt that leads into Revenge of the Sith, though it could have been! Considering the fact that Palpatine is later abducted, this is some vital part of the Sith plan, of Palpatine's plan.

That is kind of intriguing in and of itself.
But I suppose that's a question for another time.

This arc drives a clear wedge between Anakin and the Jedi Council and, more importantly, between Anakin and Obi-Wan. Or deepens an earlier wedge. This isn't the first time that Anakin and Obi-Wan have come into conflict over something due to some manipulation by Palpatine, which could be the point, the only point, of Palpatine's schemes, though I suspect Palpatine's schemes are quite multi-layered.

At any rate, Anakin is quite self-righteously pissed at being left in the dark about Obi-Wan's faked death and, possibly, righteously pissed that Obi-Wan made that decision himself. What it comes down to, though, is the planting of seeds of doubt in Anakin about the Council and what their intentions are.

Episodes like this really help to fill out Anakin's fall to the Dark Side.


"One shudders to think where the galaxy would be without the Jedi."

Tuesday, December 20, 2016

Clone Wars -- "Friends and Enemies" (Ep. 4.16)

-- Keep your friend close, but keep your enemies closer.

[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


Cad Bane needs a new hat. Of course, the first one he picks up is a very familiar looking fedora. It's worth the whole episode.

Which is saying a lot, because it's a good episode. This is a good arc, possibly a very important arc; I just can't remember how important.

Anakin is hot on the heels of Obi-Wan's killer, the problem being that Obi-Wan's killer is in fact Obi-Wan. (Oh, come on. If you watched the previous episode (and you should have watched the previous episode!), you already know this.) Considering the animosity between Rako Hardeen and Cad Bane, this only makes things worse.

Of course, it's Palpatine who plays on Anakin's anger and puts him on the trail of Hardeen. Every time we have one of these instances where Palpatine encourages Anakin in his anger or jealousy or whatever negative emotion it is, I wish I had kept a record of how many times it had happened. How many times does a Jedi have to give into anger to fall to the Dark Side?

This arc is where season four really begins to heat up.

Friday, September 2, 2016

Clone Wars -- Season Three

When the Clone Wars was conceived as a series, it wasn't meant to be a linear telling of the events of the Clone Wars. It was meant to be a collection of stories of events from the Clone Wars, meaning that the stories told could be from any time during the war since many things were all happening at once. If you've studied closely the Civil War or either of the World Wars, you will know that you can't really study those things linearly. It's more like studying a tapestry. And that's what Clone Wars was meant to be.

Season three is the only season that really makes the attempt to jump around in time; at least, if I'm remembering correctly, that's true. And from what I'm remembering at the time, people didn't respond well to the falling back to the past to tell other stories that weren't told initially. That's too bad, I think, because there is so much there. At any rate, I think season four goes back to a straight linear progression that's never deviated from again.

Unless I'm just not remembering, which is entirely possible. I'm not always all that linear.

This season has a lot of important stuff. When I say important, I mean it's important to the larger Star Wars Universe. Primarily, the Mortis story arc. As I said back in my review of the arc, this trilogy of stories provides more information about the fundamental nature of the Force than we get from any other source. If you're a Star Wars fan, this, being canon material, is a story you should see, whether or not like The Clone Wars itself as a show.

Savage Opress is also introduced in season three. He's the brother of Darth Maul, and his arc is interesting and exciting. And hints at some things that will be revealed later. This story line also deals with the fall from grace of Asajj Ventress and the fallout that happens because of it. Besides Savage, we are also introduced to the Nightsisters, a splinter group of Dark Side Force wielders. They will be back.

Duchess Satine returns for another series of appearances. I didn't like these as much as her appearances in season two, but it's good to see her again.

Tarkin is also introduced as a character in season three, and the groundwork is laid for the later relationship between him and Anakin.

Plus, there's some exploration into the lives of people who have sided with the Separatists. That's an interesting arc and deals with some heavy themes. It's well worth watching.

Overall, season three is a real winner, I think. The only off episode I can think of (without looking back at my reviews) is "Evil Plans." It's entertaining enough, I guess, but it has some real plot issues.

As far as single episodes go, I might have to go with "Clone Cadets" as my favorite, but it's outmatched when you look at some of the story arcs in the season.

Probably, you can still come into season three of Clone Wars without having seen the first two seasons and be just fine bit, seriously, just go watch it. It's a good show, and there are some things you shouldn't miss as a Star Wars fan. Of course, if you're not a Star Wars fan, it really doesn't matter that much.

Tuesday, August 2, 2016

Clone Wars -- "The Citadel" (Ep. 3.18)

-- Adaptation is the key to survival.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


At some point in the past, probably the far past, a prison was built -- it sounds like it was built by the Jedi -- to hold Jedi who turned to the Dark Side. Having been built to hold Jedi, it's a very secure facility, the kind of secure from which no one has ever escaped. I'm inferring from the presentation in "The Citadel" that the prison has been unused for quite some time. That's probably why the Separatists were able to get their hands on it.

It's also of note that the Separatists haven't put the prison to use holding Jedi any earlier than this, but that's probably because, really, they just kill Jedi rather than taking them prisoner. Mostly. Maybe it's because of Grievous' earlier failures at holding Jedi captive that Even Piell has been taken to the Citadel for torture and questioning.

We don't get a lot of background information on the Jedi in what is now canon material, so this is an interesting piece to pick up. Both that the Jedi at one time took precautions against themselves and that they haven't had to use them in so long that they have no recent records of the interior layout of the Citadel.

This is also what I think is the first meeting between Anakin and Tarkin. And Tarkin's first appearance in Clone Wars? I can't remember (having already watched the entire series before confuses the issue, and I'm not going to do the research, right now, to find out). At any rate, it's an interesting meeting and beginning to what will become one of the essential pairings in the Star Wars universe.

All of that and carbon freezing, too!


"Are you sure this thing is safe? I don't want to end up a wall decoration."

Tuesday, July 26, 2016

Clone Wars -- "Ghosts of Mortis" (Ep. 3.17)

-- He who seeks to control fate shall never find peace.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


The Force is no longer in balance.

If you haven't watched the previous two episodes of this arc, you should really go do that. While I will try to keep spoilers from this episode mostly out of this post, I need to be able to refer back to the other episodes. Seriously, if you are any kind of Star Wars fan, these three episodes are a must.

As we were watching this one, my son said to me in reference to the Father, Son, and Daughter, "Are these physical entities or embodiments of the Force?" My best answer: Yes. That the Daughter is dead, murdered by the Son, spells disaster for the galaxy and the universe. Interestingly, in the previous episode, the Father spoke repeatedly of the danger to the galaxy if the Son was able to escape the planet Mortis but, this episode, after the death of the Daughter, the Father has escalated his warning to a danger to the universe.

The question in all of this is what it means that Anakin is the Chosen One. In the last episode, Anakin refused to take up his role as the person who would maintain the balance in the Force, that balance being the equivalence between the Son and the Daughter. Obviously, the choice Anakin had was real, and his decision not to take his place had dire consequences. Will have dire consequences.

And, now, they have to keep the Son from escaping Mortis so that he doesn't wreak havoc across the galaxy.

So, what we know based on the previous episode: The Dark Side is in ascendance. The Light Side, effectively, at least for now, is dead.

To say more would be to give too much away.



"I am an old fool who believed he could control the future."

Tuesday, July 19, 2016

Clone Wars -- "Altar of Mortis" (Ep. 3.16)

-- He who surrenders hope surrenders life.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


"Is the Dark Side stronger?"
"No! Quicker, easier, more seductive."

In the context of the original trilogy of Star Wars movies, we tend to just accept that Yoda is right. Yoda is always right. And, at one point, he probably was right. Well, definitely, at one point, he was right. The Force was in balance, kept that way through the will of the Father. However, by the time Yoda is stating this to Luke, that the Dark Side is not stronger, the Force is out of balance, and the Dark Side is most definitely in ascendance. The Son has shifted the balance.

There's also what is probably very important stuff with Ahsoka. Definitely foreshadowing. I know that Ahsoka comes back in Rebels, though I'm not that far into it, yet, but I don't know if this has to do with what is going to happen there or if it has to do with anything that's going to happen in the new trilogy [There has been a lot of speculation and rumors about Ahsoka appearing in the episode eight or nine.] or if it's just a plot line that got left blowing in the wind due to Disney dropping Clone Wars. Whether it comes back or not is immaterial, I suppose, considering it's good stuff in this episode.

All of this is also a direct repercussion of Anakin turning down his role as the Chosen One. In the typical story of this nature, the "chosen one" character ends up being compelled in some way to take up the role, but, as we saw last episode, Anakin refused to be the guy to maintain the balance in the Force. Which begs the question, "Is he still the Chosen One?" Does what happens later in both Revenge of the Sith and Return of the Jedi come out of his status as Chosen One or is it because of his refusing to be that person?

I hope in some way Star Wars addresses what happens in this trilogy arc.

Tuesday, December 8, 2015

Clone Wars -- "Weapons Factory" (Ep. 2.6)

-- No gift is more precious than trust.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


Most of what The Clone Wars has dealt with up to this point in regards to the relationship between Anakin and Ahsoka has focused on how Anakin allows his relationship to get in the way of doing his job. Much of the relationship is there to demonstrate how Anakin's attachment issues affect his ability to live up to the Jedi code and show his slow slide to the Dark Side (rather than the sudden shift as it appears in Revenge of the Sith).

However, this episode uses Anakin's issues with attachment to show where the Jedi code is itself weak and how other Jedi could perhaps do well to be more like Anakin.

"Weapons Factory" features Luminara Unduli and her apprentice, Bariss Offee. Bariss and Ahsoka get sent on a mission together. Anakin... well, Anakin frets and doesn't want Ahsoka to go. Anakin and Ahsoka are having issues, just in general, over whether Anakin trusts Ahsoka or not. However, when the apprentices get into trouble, it's Anakin who has faith in his apprentice while Luminara, basically, writes her apprentice off with "if it's her time..."

What we see in the episode is one Jedi, one who strictly follows the code and has no sense of attachment to her apprentice other than her duty to train her, who feels no compulsion to try and save her apprentice and, thus, would have left Bariss and Ahsoka to die if it had been up to her, and one Jedi who has difficulty (unknowingly) with some aspects of the code, specifically in his tendency to form attachments, who is unwilling to give up on his apprentice until he has proof that she's dead. It this attachment that Anakin has with Ahsoka that leads Anakin and Luminara to rescue the two apprentices.

It's also a demonstration of Anakin's trust in Ahsoka's abilities. He believes that she is still alive because he believes in her capacity. Luminara immediately decides that Bariss has failed.

The episode provides an interesting contrast between the two styles and shows, at least from the standpoint of our own sensibilities, that the Jedi have a thing or two they can learn from Anakin and how to invest in those around them.

Tuesday, November 24, 2015

Clone Wars -- "Senate Spy" (Ep. 2.4)

-- A true heart should never be doubted.

[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]

This is an episode with, kind of, a deliberately misleading title. I'm not going to explain that more than to say it; if you want to know what I mean, you should watch the episode. It's a stand alone, so you can get away with that even if you haven't been watching the series.

However, it isn't the story that interests me about this episode, though the story is fine. Good even. No, what interests me is the continued exploration of Anakin and his attachment issues.

I suppose it might not be entirely clear why the Jedi are not allowed to have attachments, at least from the prospective of the movies. I mean, it's never stated why Jedi are not supposed to own things or form romantic entanglements or, well, have children. Because it seems like having Jedi have children would be the thing to do if you wanted more Jedi children, right? So the underlying reason for the "no attachments" rule is never given. Anywhere. But The Clone Wars gives us plenty of examples, through Anakin, of the issues that arise from having attachments, everything from disobeying orders to retrieve some personal object, to making some one person a priority over completing a mission, to, well, jealousy.

And that's the real issue: Attachments open the Jedi to the negative emotions that lead to the Dark Side of the Force. And that's what's explored in this episode: Anakin's jealousy over a previous lover of Padme's.

So, yeah, the story of the "Senate Spy" is fine. It's good. But it's Anakin's jealousy and his anger and attempt to control Padme's actions because of those things that make the story of real interest.

And, actually, importance.

It's these episodes where we can see Anakin's slide to the Dark Side and that it wasn't some sudden change during Revenge of the Sith.

Also, we get to see, again, a glimmer of Obi-Wan's suspicions about Anakin and Padme, which is good. I mean, it's good that we get to see that he had suspicions, because it's a bit much to believe that Obi-Wan, of all people, had no idea what was going on.

Tuesday, November 17, 2015

Clone Wars -- "Children of the Force" (Ep. 2.3)

-- The first step to correcting a mistake is patience.

[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]

We all know that Palpatine used Order 66 to wipe out the Jedi, but that doesn't answer the question of how Force users became, basically, extinct (as far as we know) across the galaxy within a generation. Sure, you could say that without the Jedi and the Temple that Force-sensitive children simply grew up without ever harnessing their abilities, and, to some extent, I'm sure that's true. However, in this episode we see that Darth Sidious' plan is much more insidious.

Part of the plan is to wipe out those children before they ever have a chance to grow up and potentially become a threat. Palpatine doesn't, after all, mess around.

However, the true horror is not that he wants to wipe out the young Force-sensitives, it's that he wants to bend all of them to the Dark Side and use them as a network of spies and assassins.

This whole plot provides background for the long time fan favorite Expanded Universe character Mara Jade.
As far as a I know, Jade is not currently a canon character (you can see my discussion of Star Wars canon here), but there has been talk that she is going to be included somewhere in the new canon and, possibly, the new movies. At any rate, she was a Force-sensitive child who was molded by the Emperor to be his prime assassin, such that she was called the Emperor's Hand,

So there you go. A bit of Expanded Universe history to tie into The Clone Wars.


"What could possibly have happened since I last spoke with you?"

Monday, May 23, 2011

"Danger, Will Robinson!" (Or Story Gimmicks We Can Do Without) Part 2

Part 2: How bad is bad?

As an author, one of the things you have to do is convince your readers that the bad guy is a bad guy. The reader has to know that the hero is in real and imminent danger. There's a short cut for this that, really, I just hate. Every time I see it. Unfortunately, I have to blame it on George Lucas and Darth Vader.

Vader is easily one of the most menacing villains ever created. Ever. Total aside:
I'm sure this is one of the things that lies at the heart of many people's dislike of the prequels. No one really wanted to know that Vader had once been a lovable kid and whiny teenager. They wanted to believe he'd been the kind of kid that set banthas on fire and pulled the legs off of womp rats. But the point was that he had been just a normal kid. The lesson being, as Yoda showed Luke in Empire, that anyone (everyone) has the capacity to turn evil. To go to the dark side.

The thing is is that no one ever doubts that Vader is a bad guy. From the moment he steps through the smoke filled airlock littered with bodies, everyone knows this dude is bad. If you didn't know it, the casual way he tosses aside the dead Captain Antilles, whom he has just choked to death while holding him suspended several feet off the ground with one arm! proves it. I could go on.

Still, no one really knew just how Bad Vader is until The Empire Strikes Back. I mean, we all know he'll kill his enemies without a second thought. Even casually. Without regard. But when he force chokes Admiral Ozzel via hologram for messing up the Hoth invasion (which he wasn't really to blame for, because it was the probe droid that had alerted the rebels), that's when we know. Really know. Vader is BAD. He's so bad he'll kill, well, anyone. The lesson here is that, man, you really don't want to piss off Vader.

But Lucas didn't do any of those things to prove to us how bad Vader is. We know. We've always known. Since that first moment at the airlock. Everything else flows out of just how BAD Vader is. Somewhere in there, though, the lesson that was communicated was that if you want to prove just how bad your villain is, have him kill some of his underlings. Usually without any legitimate provocation.

Here's the one I hate the most:
Main bad dude is trying to kill some good dude(s). He decides the way to do this is by using some weapon that has a mass effect. Like a bomb. Or a missile. Something  that will make a huge explosion and kill everyone in the area. The problem is that the good dude is fighting the underlings of the main bad dude. He shows his disregard for his men by ordering that the device that will cause a huge explosion be used to kill the good dude(s) and, thus, his own men.

Okay, so he's a bad guy. We get it. However, he really needs to kill the good dude(s), and his men are expendable. And in the way. But, wait! We're not finished, yet. Because that's not bad enough. Nooo! Because you can (almost) make a case for what he's doing. He needs to get rid of the good dude(s), and the men that are fighting the good dude(s) are probably going to die anyway while failing at their job of killing the good dude(s). So we have a bad guy, but, really, is that bad enough? Evidently not.

Invariably, what follows here is that some well meaning underling stands up to the main bad dude and says, "But, wait, sir; that will kill all of our men, too!" A legitimate concern. I mean, when you see your boss killing your fellow employees, it doesn't say much for your job security, now does it? How can you rule the universe alongside the big bad dude if you're dead? Underling wants to know that the main bad dude really does care and that he just didn't realize he'd be killing his own men. He wants the guy to say, "Oh! Well, we can't do that. Cancel that order."

But that's not what happens. Ever. If some guy stands up and tells the big bad that he's about to kill his own men, the thing that always happens is that the big bad pulls out a gun (or appropriate equivalent) and turns and shoots his underling in the head. This is usually followed by some sort of question along these lines, "Does anyone else have anything to say?" Of course, all the other underlings busily return to their tasks. You know, of making sure their co-workers end up dead.

There are two main reasons I hate this:
1. It's lazy writing. This almost always happens sometime in  the first third of the story. It's just a short cut so that we can see that the bad guy really is a BAD guy. But it just doesn't work for me. It's too done, now. It doesn't make the bad guy any badder. Really, it's enough for me to know he's the bad guy. It's enough for me to know that he wants to kill the good guy. I don't care if he's so bad that he's willing, or even eager, to kill his own men. It's a short cut that doesn't go anywhere. It's not like the audience cares if he's going to off his own men. If you want us to believe that your villain is really vile, build it up. Don't use it as a short cut.

2. It's completely unrealistic. Seriously, if you knew your boss was willing to kill you to achieve his own agenda, would you keep working for him? Well, maybe, if it was just you that thought that, but if everyone believed that? People would be bailing at the first chance they got. Historically, we know this is true. There have been times when the means of various armies of motivating their men was "go fight our enemy or we'll kill you." The role officers played was to stand at the back and shoot people trying to run away. The men would fight because they might survive against the enemy, which was better odds than they had if they tried to run. However, they deserted in droves every chance they got. The bad guys that resorted to these methods never succeeded because they couldn't keep any men working for them. In fact, bad guys that did things like disregard the safety of their men often got killed in their sleep (or on the toilet) by those same men. So it doesn't work for me when an author expects me to believe that underlings will go blithely about their business while their boss randomly culls them.

Of course, there are other ways to short cut the villain. Undermine his villain-ness by having him do senseless things. Often, it's to have him go out of his way to kill civilians or other people not involved in the story. And that can be okay. The trick is to not resort to, well, for lack of a better way of putting it, senseless violence to sell your villain as a bad guy. I mean that in the sense that the violence needs to have a reason for the villain. Let me say that another way: The villain must have a reason for his behavior. It doesn't matter if it's a reason that the audience doesn't understand, but it must be the villain's reason, and it must be consistent. Vader is a great villain not because he kills his underlings but because he kills those that fail him. Failure is not tolerated. Vader has a reason for the things he does as opposed to doing things to fulfill the reasons of the author.

If a hero can only be as "good" as his villain, then give me good, well thought out villains. Don't give me cardboard villains doing cliche things like shooting their underlings for airing a legitimate concern.