Showing posts with label A Taste Of Armageddon. Show all posts
Showing posts with label A Taste Of Armageddon. Show all posts

Saturday, March 22, 2014

The Cloud Minders

The ghost of Castles In The Sky haunts this episode. Castles In The Sky was David Gerrold's outline for the episode which became The Cloud Minders and David Gerrold considers Castles In The Sky to be superior to the episode which bears his name; probably not unreasonably. The circumstances of how The Cloud Minders came to be written are widely available on the internet but the short version is that producer Fred Freiberger disliked Castles In The Sky and teamed David Gerrold up with Oliver Crawford to write a revised story outline. Fred Freiberger then decided to start again from scratch by giving Margaret Armen a very broad outline of the story and asking her to produce a revised story treatment which was built up into the finished teleplay. Knowing about the existence of Castles In The Sky makes it difficult to see The Cloud Minders properly because it's too easy to start comparing the finished episode with its unmade precursor; The Way To Eden suffers from a similar problem once you know it is based on an outline from D.C. Fontana for a story called Joanna.

Actually the quality of The Cloud Minders surprises. In the sub-genre of Star Trek stories that David Gerrold called Mary Worth stories (the Enterprise meddles "her way across the Galaxy, solving problems as she goes," The World Of Star Trek) The Cloud Minders comes out very well. It's comparable to A Taste Of Armageddon but lacks that story's sense of place. In A Taste Of Armageddon we meet several representatives of the High Council of Eminiar VII, as well as assorted extras done up as guards and civilians. The Cloud Minders is a little more sparingly populated. Representing the population of Stratos the cloud city is Droxine and Plasus, Droxine's father, and that's it. Still, Stratos may have a low population density but it feels like a real place. Matt Jefferies' sets look lavish, and they are unusual in being split level with a balcony area up some stairs; director Jud Taylor makes good use of this layout. Stratos itself comes via Laputa the flying island from Gulliver's Travels. Margaret Armen ditches the satire of Jonathen Swift's novel for a more obvious metaphor of the ruling class living literally in the clouds, high above the working class they rely upon to sustain their lifestyle.

There may not be many characters but they are well defined. The characters in The Cloud Minders are some of the most interesting and complex we have seen in the third season. Droxine begins as one of Star Trek's more vapid characters, she is considerably less interesting than her costume which is one of William Ware Theiss' more extraordinary designs, but by the end of the story she has questioned her father's actions, expressed a desire to go to the mines, and realised the cost of her pampered lifestyle. Plasus has also changed but for the worse. Through the episode his diplomatic mask slips and by the end he's much more entrenched in his views and open in his bigotry against the Troglytes. Best character of all is Troglyte leader Vanna an angry revolutionary who sometimes even gets frustrated by the limited intelligence of her fellow Disruptors ("can you do nothing but argue?" she snaps at Midro when he suggests killing Kirk and is unable to grasp the value in keeping him alive). It's pleasing to note that at the end of the episode she is the least affected by exposure to the zenite gas. When Kirk and Plasus start brawling she's smart enough to work out what has happened and uses Kirk's communicator to call for help.

The Cloud Minders is also a good story for Kirk. He starts out understandably reluctant to get involved in the dispute with the Troglytes. Then he takes a stand against Plasus' use of torture to locate the missing zenite. Finally he makes a command decision to place the need for zenite above his duty not to interfere with the government of Ardana. His suggestion of masks to counter the effects of the gas is more pragmatic than altruistic and his impatience to get the urgently needed zenite to its destination leads him to mistakenly trust Vanna, who promptly takes him hostage. The scene where Kirk forces Plasus and Vanna to dig zenite with their bare hands is surprisingly shocking and works because it shows how the zenite gas brings out an ugly, cruel side to his personality. It's important to establish the effects of the gas to the viewers as well as Plasus and Vanna, and the best way to do that is to show Kirk behaving as he did in The Enemy Within; to show the gas bringing out the same side of his personality revealed by the transporter malfuction. By contrast Spock seems to get a week off. He's given a lengthy, and unusual, voice over to speculate about social inequality on Ardana but that's his most significant action. For most of the rest of the episode his involvement tends to be restricted to acting as the voice of conscience when debating with Plasus and Droxine about their treatment of the Troglytes.

The ending of The Cloud Minders is pleasantly mature. In A Taste Of Armageddon when Kirk destroys the war computer on Eminiar VII he instantly changes their society. His intervention has an immediate and noticeable effect and he changes their world for the better, although long term peace between Eminiar VII and Vendikar will still depend on the locals. The same is true of other Mary Worth stories like The Apple or The Return Of The Archons. At the end of the episode their respective societies are already visibly different. The Cloud Minders shows how long social change can take. Although Ardana can never be the same after the events of The Cloud Minders the world has not changed overnight. Plasus and Vanna have not become friends after their shared experience. They do not suddenly understand the other's point of view. If anything the lines separating the pair have become more clearly defined. Plasus and Vanna have both begun to realise that the masks will make all Troglytes articulate enough to argue the injustice of the current system and the case for fairer treatment. What's going to happen on Ardana is right, but right doesn't mean pleasant or nice or easy. As Plasus and Vanna argue and snipe at each other we see that the immediate future on Ardana is going to be difficult.

PLASUS: They will all be like her. Ungrateful, vindictive.
VANNA: Yes. Our demands have just begun.
 

Enterprise crew deaths: None.
Running total: 56

Thursday, February 20, 2014

Requiem For Methuselah

Requiem For Methuselah was written by Jerome Bixby who contributed the impressive script threesome of Day Of The Dove, By Any Other Name, and Mirror, Mirror. It contains some of the finest individual lines in Star Trek. "A very old and lonely man. And a young and lonely man. We put on a pretty poor show, didn't we?" Kirk's line deserves to be quoted alongside Spock's, "I have killed my captain and my friend," from Amok Time. Even better, William Shatner responds to the obvious quality of the dialogue and turns in some of his best acting work for a long time. In fact this may be one of the best acted episodes of the series. Guest stars James Daly as Flint and Louise Sorel as Rayna, also turn in sterling work; we're a very long way from the arch performances of Spock's Brain. And Flint is an intriguing creation. An immortal man who began as "a soldier, a bully and a fool," and met the great minds of history, "Galileo, Socrates, Moses," and learned from them. He evolved from cruelty and barbarism and educated himself to become a succession of brilliant men; Leonardo, Brahms, Solomon, Alexander, and so on. He is almost the incarnation of Kirk's speech at the end of A Taste Of Armageddon. "The instinct can be fought. We're human beings with the blood of a million savage years on our hands, but we can stop it. We can admit that we're killers, but we're not going to kill today. That's all it takes. Knowing that we won't kill today." Flint is the soldier who learned not to kill.

So what's the problem? If
Requiem For Methuselah contains such great acting and a scintillating script then why does it drag? The most obvious flaw is that this is a love story for Kirk. Another one. There comes a point where no matter how beautifully you tell your love story it's simply going over the same old ground. How many times can Captain Kirk meet the love of his life and begin an affair which ends tragically? About three. There's an additional issue. To inject some urgency into the plot an arbitrary deadline has been added. The Enterprise is in the grip of an outbreak of Rigelian fever. McCoy has, "four hours to process [the ryetalyn cure], otherwise the epidemic will be irreversible." Unfortunately this results in the problem everyone notices with the story, in the space of less than four hours Kirk falls so deeply in love that at the end of the episode he seems barely able to function. Imagine The City On The Edge Of Forever rewritten so that Kirk and Spock arrive five hours before McCoy, and Kirk and Edith Keeler fall in love across a single afternoon. That's the story presented by Requiem For Methuselah. The script's justification for Kirk's abrupt fall for Rayna is that she is unusually captivating and beautiful and extraordinary. Except that all the women Kirk falls for(as opposed to the ones he more cynically seduces such as Kelinda in By Another Name) are unusually captivating and beautiful and extraordinary. Edith Keeler was. So was Miramanee from The Paradise Syndrome. Kirk has a definite type and his type is the woman who dies tragically around the 48 minute mark.

The plotting of
Requiem For Methuselah is spartan. In The City On The Edge Of Forever Kirk has a stark choice; save the future or save Edith Keeler. There is no similar conflict in Requiem For Methuselah. Kirk falls in love with a woman who dies. The end. The Rigelian fever outbreak is a device to get Kirk into the story and is then largely forgotten;
like the duplicate Earth in Miri,. There's no attempt to bring the romance and the disease story together and have, for example, Rayna die of Rigelian fever. The developing love story between Kirk and Rayna is the only significant story and it's simply too slender to support an episode all by itself. The City On The Edge Of Forever keeps several plots running simultaneously; the hunt for McCoy, restoring history to the right path, and Spock's attempt to learn the fate of Edith Keeler.

It's tempting to excuse the plot light nature of
Requiem For Methuselah by describing the episode as a character study of Flint. Unfortunately Flint simply isn't interesting enough as a character. Yes, he is an intriguing creation but in practical terms his background plays no part in the story beyond the moment when he tells Kirk, "I am Brahms." Flint is a character for a film or a book. We need to explore Flint's life, because the story of how he came to be the person living on this unnamed planet far from the rest of humanity is more interesting than Flint the person. Unfortunately that is a story Star Trek cannot tell. When Doctor Who created a similar, if more humorous, character in the alien Scaroth from the story City Of Death the Doctor was able to travel in time and explore Scaroth's life; on a BBC budget. We saw Scaroth in 1979 Paris, and the year 400 million BC (approx.), and 1505 Florence, and we saw hints of his life elsewhere as an Egyptian god. We get a sense of a life lived. More than that we get a sense of how frustrating it must be for Scaroth to live among these primitive creatures which were created as as result of the accident which destroyed Scaroth's race and made him immortal.

Metamorphosis has a similar problem. The story makes a big deal out of Kirk meeting Zefram Cochrane, the discoverer of the space warp, a man out of time who has been kept alive for 150 years by the mysterious alien Companion but Cochrane's background ceases to have any impact on the story the moment McCoy says, "that's impossible. Zefram Cochrane died a hundred and fifty years ago." Ultimately Zefram Cochrane could be any Joe Sixpack who crashed his shuttle. Likewise there's nothing about the character space occupied by Flint which specifically requires a 6000 year old man who was a succession of famous historical figures. Flint needs to be brilliant but he could still be any 23rd Century robotics genius who decided to drop out and live with his android girlfriend.

Lastly there's the final scene. Your mileage will vary but I find it creepy and wrong. Spock takes it upon himself to edit Kirk's memories and presumably dull the pain caused by the death of Rayna. What frustrates about this scene is that the mind meld is not necessary. Simply showing Kirk grieving is unusual enough to demonstrate the depth of his feeling for Rayna. It establishes that what Kirk has been through is more than just another space fling. The mind meld is there because someone on the production side wanted to show that Rayna meant more to Kirk than all those other space babes, but also wanted to explain why Kirk isn't still prostrated with grief at the start of next week's episode. It's a classic example of over-thinking a problem because simple implied passage of time between episodes will take care of the mourning period. If the audience wasn't bothered at the end of
The City On The Edge Of Forever or The Paradise Syndrome then they won't be bothered now. As it is, when Spock starts whispering "forget", I just wonder how many other times has he crept into Kirk's room and done this?

Enterprise crew deaths: Three Enterprise crew die off-screen because of Rigelian fever.
Running total: 56

Sunday, January 12, 2014

Let That Be Your Last Battlefield

Balance Of Terror told this story more effectively. In that episode you've got the outright racism of Lieutenant Stiles who has learned from his family to hate the Romulans for the deaths of some of his ancestors a century ago. "There was a Captain Stiles in the space service then. Two Commanders and several junior officers. All lost in that war, sir." Stiles' attitude is contrasted unfavourably with Kirk's more enlightened perspective, "their war, Mister Stiles. Not yours. Don't forget it." Then once Spock taps into the Romulan bridge Stiles bigotry and paranoia, "we could have Romulan spies aboard this ship," becomes attached to Spock. The focus, as all Star Trek should be, is always on the Enterprise and her crew.

Contrast that with Let That Be Your Last Battlefield in which Lokai and Bele bring their aeons old dispute onto the Enterprise. The pair run around making speeches at everyone while the Enterprise crew raise their eyebrows at the aliens "primitive thinking" and simper about there being persecution on Earth once and how they, "remember reading about it in my history class."

One of the great things about
Balance Of Terror is that it reflects flawed humanity. Someone like Stiles can be a good bridge officer but a bad person. He can hate Spock for the wrong reasons but be right about what it means for galactic peace if the Romulan ship is allowed to return home. Presenting the Enterprise crew as beyond racism in Let That Be Your Last Battlefield reduces them to the status of observers. Literally considering the only decisive action Kirk takes in the story is when he sets the ship to self-destruct and makes Bele briefly return control. For the most part he stands around watching Lokai and Bele argue. Understandably he prefers to take the pair to Starbase Four where they will become someone else's problem. The Enterprise crew can see the hatred between Lokai and Bele but it's not something they can understand. This distances the Enterprise crew from the viewer because it's never explained how they reach this enlightened perspective, understandably given that the writers have no more idea than the viewer how this can be achieved; although one point in the episodes favour is that it does make their values aspirational, something which humanity should work towards.

Unfortunately the lofty post-racism of the Enterprise crew also allows the production team to avoid making an unambiguous statement condemning bigotry. Kirk needs to clearly and explicitly condemn the attitudes of Lokai and Bele in the same way he publicly dresses down Stiles. "Leave any bigotry in your quarters. There's no room for it on the Bridge. Do I make myself clear?" In
A Taste Of Armageddon Kirk gives a speech in which he admits that humanity, like the people of Eminiar VII, is a race of killers. "We're human beings with the blood of a million savage years on our hands, but we can stop it. We can admit that we're killers, but we're not going to kill today. That's all it takes. Knowing that we won't kill today." Let That Be Your Last Battlefield is crying out for a speech like this from Kirk in which he compares humanity to Lokai and Bele and admits that we are flawed but work to constantly overcome the hatred Lokai and Bele feel for each other. However the script doesn't want to admit that Kirk, and by extension the audience, are anything like Lokai and Bele. This is a story which could explore the Vulcan idea of IDIC more effectively than IsThere In Truth No Beauty?
Worse, the script is determined to be oddly even handed. The anger of Lokai, the oppressed, is presented as being as bad as the bigotry of Bele the oppressor. This massive oversimplification of a complex issue might be necessary to make the episode work but in the end what should be a clear message condemning racism becomes fudged. The story ends up as a shrugged statement that bigotry and hatred are stupid but both sides are as bad as each other. In the end it's redundant to talk about the acting or the direction or the editing or the make-up because the moral lesson is the point of the episode, unlike Balance Of Terror which keeps the moral lesson as a subplot to a larger story, and the episode fails the moment it fumbles the clear delivery of it's own message. It's not clear why Let That Be Your Last Battlefield should fumble its message but it's possible that
when this episode was written and filmed in 1968 , which was a terrible year around the world, anything stronger was seen as inappropriate.

E
nterprise crew deaths: None.
Running total: 50

Sunday, November 3, 2013

Day Of The Dove

Day Of The Dove is one of those episodes Star Trek occasionally produces where all the interesting stuff is going on at the edge of the story. A Private Little War's dull central idea of nice hill people vs nasty villagers is much less interesting than the motivation of Krell the Klingon. What's does he want from the planet? Is he helping build a network of satellite planets to act as a buffer zone against the Federation? Are the Klingons also excited about the, “interesting organic compounds,” McCoy has found? Is he just messing up the planet for sheer devilment? The concept of the Gorgon, and its vague resemblance to H. P. Lovecraft's ideas of ancient corrupting evil, is far more interesting than anything else to be found in And The Children Shall Lead.

Day Of The Dove
is a better episode than either A Private Little War or And The Children Shall Lead but the central message is spelled out so clearly it becomes obvious and trite. Peace is better than war. Far more interesting is the unnamed and unexplained alien.
At the start of the episode the Enterprise is investigating a distress call. One hundred men, women, and children have been wiped out by an unidentified craft. No trace of the colony, or any residue of the force used to destroy it, remains. The implication seems to be that the distress call was faked by the alien (in fact there probably wasn't even a colony) and that the alien is also playing with the perception and memories of the Enterprise crew to stop them noticing any holes in this scenario. At the same time the alien has also faked an attack on a Klingon ship. Physical damage has been inflicted on the ship and, again, the crew's perceptions altered to make them believe the Enterprise crew is to blame.

This is an astonishingly powerful alien. It can manipulate memories emotions and matter, and yet here it is setting up a fight between 38 humans and 38 Klingons to turn the Enterprise into an eternal all it can eat hate buffet. How did it end up here, in reduced circumstances, faking distress calls in some galactic backwater? It's fun to imagine what it got up to in the past. Perhaps it visited the Eminiar system to provoke the war between Eminiar VII and Vendikar. It probably fed off that conflict for years until both planets instigated the simulated war we see in
A Taste Of Armageddon, and the alien found that computer controlled wars were too emotionless for its taste.

The story isn't about the alien, it's about Kirk and the Enterprise crew and the Klingons breaking their cycle of prejudice and hatred. It's fun, and the message is meant well and delivered sincerely, but ultimately the storytelling is too convenient to make for a great episode. The all-powerful alien becomes oddly powerless at times. When Kirk, Spock, and Mara find it in the Enterprise corridors it cowers as if trapped in the corner of the ceiling although we've already seen it move effortlessly through walls. Then while the three watch it demonstrates its dependence on hostile emotions before floating away. Several times in the episode the alien provokes Enterprise crew members into mutinous rages, Chekov on the bridge when he talks about his non-existent brother Piotre and Johnson just before he is knocked out by Spock, and yet a simple command across the ship's intercom from Kirk and Klingon Commander Kang is enough for all fighting to immediately stop.

It's also difficult to square the anti-war message of Day Of The Dove with earlier episodes especially A Private Little War in which Kirk argues for war when he says, “war isn't a good life, but it's life.” A Private Little War writer Jud Crucis (actually Don Ingalls hiding behind a pseudonym) cannot be blamed for the contradictions caused by a later episode but it's a good demonstration of how little overall continuity there was between different episodes of Star Trek.

Enterprise crew deaths: None again.
Running total: 48.

Sunday, October 6, 2013

Spectre Of The Gun

CHEKOV: Where are we now, Captain?
KIRK: Spock, evaluation?
SPOCK: Obviously this represents the Melkotian's concept of an American frontier town, circa 1880.
MCCOY: It's just bits and pieces. It's incomplete.
SPOCK: Perhaps the Melkotians have insufficient data about this era.
KIRK: Or perhaps this is all they require to complete the pattern of our death.

The set design is what elevates Spectre Of The Gun. Gene L. Coon's script is fun but run of the mill by his own standards. It's a mash-up of Arena (powerful aliens force Kirk into a fight to the death to punish him for trespassing on their territory, at the end Kirk's refusal to kill convinces them to give him a second chance) and A Taste Of Armageddon. Spectre Of The Gun and A Taste Of Armageddon both use the same mechanism to get the Enterprise crew into the story; the Enterprise trespasses into a sector of space against the express wishes of the inhabitants. In both cases Kirk is under express orders to make contact but his attitude couldn't be more different. In A Taste Of Armageddon Kirk displays clear contempt for Ambassador Fox and his orders, all part of making sure the audience find Fox as unsympathetic as possible, but here his attitude is pragmatic and Kirk displays a lot less concern for the welfare of his crew even though the Melkotian warning is more explicit than the Federation code sent from Eminiar VII. Surprisingly when Star Trek: The Next Generation wanted to spoof the then current vogue for Robin Hood films they ended up writing an episode very much like Spectre Of The Gun; a powerful alien creates a self-sustaining world and drops in our heroes.

The weakest element of Gene L. Coon's script is his use of Chekov who manages to fall
deeply in love during his short stay in fake-Tombstone despite knowing he is scheduled to die at 5pm. At the end of the episode he has this exchange with Kirk.

CHEKOV: What happened? Where have I been?
KIRK: Right here, it seems.
CHEKOV: But that girl. She was so beautiful. So real.
KIRK: Do you remember anything else?
CHEKOV: No.
KIRK: Good. Perhaps that explains why he's here. Nothing was real to him except the girl.

“That girl,” was so real to Chekov he can't even remember her name. There's always been a brash juvenile streak to Chekov's character, look at the opening scenes of TheTrouble With Tribbles and Chekov's attempts to impress Kirk, but here he spills over into outright immaturity and it's a mystery why Kirk displays such tolerance for the romance.

The stars of the episode are the sets. Faced with a workable script which called for either location filming or the construction of a Western town set, both unaffordable on Star Trek's third season budget, someone -probably Robert Justman or Matt Jefferies- came up with the idea of the half-constructed town. Director Vincent McEveety carefully uses the resulting sets to make Tombstone feel like a real place with its own dreamlike logic and rules.

Despite the half-constructed sets, no one leaps over any of the waist high walls or has a conversation with someone within a building. Everything is treated as if it were solid. Even the characters seem to appear and disappear when no one is looking. Watch the moment when the Sheriff first appears; on his line, “Ike,” he's already outside the closed door of the Sheriff’s office and walking towards the landing party as if he just popped into existence. Likewise, at the end of his first scene the Sheriff walks off the left-hand side of the frame and it's as if he disappears. A similar trick is pulled when the landing party enter the Tombstone bar. From the street the bar is clearly empty, but as the landing party walk through the doors it is suddenly full of people; including some sitting where they should have been visible from outside. It's a simple directing trick but it makes Tombstone feels strange and disorientating. What makes the moment more effective is that none of the landing party react to the sudden appearance of all these people. The disorientation is only there for the viewer. The set for the OK Corral at the end of the episode is suddenly much more solid and realistic. Possibly this was done to stop the climax from looking too fantastical, there is already the very theatrical effect of lightning casting shadows on the sky and the brilliant visual of bullet holes appearing in wood as the Clanton's fire at the unaffected landing party.

Enterprise crew deaths: None this week.
Running total: 48.

Wednesday, May 29, 2013

The Enterprise Incident

On 23rd January 1968 the USS Pueblo was boarded and captured by North Korean soldiers. The ship had been monitoring Soviet Union naval activity and gathering signal and electronic intelligence from North Korea. The United States maintained the USS Pueblo had always remained in international waters while North Korea claimed the ship had violated its territory. For D.C. Fontana this was the inspiration for the story which became The Enterprise Incident. Star Trek has dealt with contemporary issues before but this is bold even by their standards. The Pueblo incident, as it has become known, bubbled away through 1968 as the script was written, filmed, and broadcast. The crew were finally released from North Korea on 23rd December 1968, some three months after The Enterprise Incident was first aired.

The main strength of The Enterprise Incident is that the plot barrels forwards at top speed. By the end of the teaser the Enterprise is surrounded by Romulan ships, then act one ends with Spock betraying Kirk, act two with Kirk being pronounced dead, and act three with Scotty in a race against time to install the stolen cloaking device on the Enterprise. There's very little slack in the script. Unlike the act one Enterprise bridge scenes in Spock's Brain where the bridge crew work through the problem of locating Spock's purloined organ; those scenes don't do anything except pad out the running time to the required length. Although it's great to see the bridge crew working as a team it's the work of the actors, and Marc Daniels inspired decision to use back projection for the bridge viewscreen, which makes those bridge scenes interesting. In The Enterprise Incident each time the viewer thinks they've got a handle on the plot something new is thrown into the mix. The most obvious example being the act three reveal that this is all a big bluff to steal the new improved Romulan cloaking device. Then Kirk is disguised as a Romulan, and the episode turns into something more like Mission: Impossible; a spy/caper story in space.

The big advantage of keeping the plot moving like this is it stops the viewer noticing how conveniently everything falls into place. Kirk and Spock are consistently insanely lucky. Under orders from the Federation to steal a cloaking device they fly into Romulan space and are intercepted by a ship which has exactly what they need. Rather than destroy the Enterprise, “standard Romulan procedure” according to Spock, the Romulans decide the ship would make a great prize and invite Kirk and Spock across to the flagship. The Romulan commander is a woman who is attracted to Spock, which gives him a chance to distract her. When Spock “kills” Kirk his body is returned to the Enterprise before Spock's nerve pinch wears off. When the theft of the cloaking device is noticed the Romulan commander delays any action for 20 minutes while she takes Spock's confession, giving Scotty time to fit the device on the Enterprise, and Chekov time to locate Spock with the sensors. There's nothing wrong with having a character saved by a moment of luck but there's only so long a script can rely on coincidence before it starts to feel contrived, and as The Enterprise Incident moves into act four it does feel as if the coincidences mount up too much.

Worse, as the coincidences pile up it makes the viewer more sceptical and less willing to allow the story the required suspension of disbelief. Essentially it encourages them to actively pick holes in the story, and there do seem to be plenty to find. It sure is lucky that the Romulan cloaking device is compatible with the Enterprise systems. Just as it sure is lucky the Romulans don't search Spock and find the hidden communicator he is carrying. Just as it sure is lucky the Romulans notice Spock's transmissions but don't notice Kirk beaming over from, and back to, the Enterprise. Just as it sure is lucky the Romulans bring Kirk and Spock onto their ship. It would have wrecked Kirk's plan if the Romulans had kept everyone on board the Enterprise. The Enterprise Incident is a good script, but there's just too much narrative cheating for it to ever be great.

Another strength of The Enterprise Incident is that it paints the Federation with a little more grey than we normally see. The Federation is prepared to use sneaky and underhand tactics to gain an advantage and by ordering the Enterprise into Romulan space on a spying mission the Federation risks the crew of the Enterprise and, more seriously, war with the Romulans. This acknowledgement that sometimes even the good guys have to use morally dubious methods is a sign of maturity not always seen in Star Trek. Standard practice is simply to not discuss the subject. It's just taken as read that the Federation is a force for good. Which is fine until something comes along which makes the Federation look bad. How many lousy Federation officials have we met? Or insane starship captains?

At its worst Star Trek will assume that anything its heroes do must be right, simply because they are the heroes and therefore incapable of doing anything wrong (and this is true of any television series not just Star Trek). Look at The Apple where Kirk's destruction of Vaal is presented as heroic because now the Feeders of Vaal can kiss and have babies; never mind that the entire planetary population is 15 people and their world is a lethal death trap. Or compare the way the Terran Empire's threatened standard procedure (“phaser barrage on Halkan cities”) is presented as evil in Mirror, Mirror but Kirk's threat to use Starfleet General Order 24 (“the entire inhabited surface of your planet will be destroyed”) is a heroic way to force Anan 7 to listen in A Taste Of Armageddon.

This pragmatic Federation feels more realistic. A return to the complexities of episodes like
Errand Of Mercy where every decision Kirk makes is for the right ethical reasons, but at the end of the story he is on the side arguing for war. What's particularly pleasing is that none of the characters are used to justify the Federation's actions. There is no The Apple style speech telling us that the Romulans are so bad that anything the Federation does against them is justified. Instead Kirk and Spock are carrying out orders they have been given as part of what seems to be routine toing and froing of secrets between the Federation and Romulans and, as Spock acknowledges at the end of the episode, he and Kirk went to all that effort and exposed themselves to danger for what was probably only a short term gain. “Military secrets are the most fleeting of all.”

Enterprise crew deaths: None again, Kirk's risky plan works perfectly.
Running total: 46

Friday, April 26, 2013

The Ultimate Computer

Back in 1990 when the BBC finally decided to start showing Star Trek: The Next Generation I was watching Datalore with my parents. Within about a minute of Lore being reactivated my mum said, “I'll bet he turns out to be evil.” Some stories have a weight of inevitability about them. If a character develops a cough or a headache then they will be dead soon. In The Ultimate Computer it's obvious things are going to go badly from the moment Commodore Wesley tells Kirk the Enterprise will be used to test the new M-5 computer, and that all he has to do is, “sit back and let the machine do the work.”

Sure enough the M-5 goes berserk after mistaking simulated war games for the real thing and, as is always the way in these situations, Captain Kirk talks the M-5 to death. However, if the overall course of the plot runs on rails
The Ultimate Computer deserves some credit for taking an unexpected detour on the way. The first two acts are more character driven than might be expected in a rogue computer story as Kirk tries to cope with discovering that the M-5 really can do his job better. This still gives the story a weirdly contemporary edge. Who wouldn't worry about being replaced by a computer? It's odd to see Kirk so rattled. A man who has faced down Klingons and alien invasions, and generally shown himself to be a decision making machine, is faced with the prospect of being replaced by a machine better at making decisions.

MCCOY: We're all sorry for the other guy when he loses his job to a machine. When it comes to your job, that's different. And it always will be different.
KIRK: Am I afraid of losing command to a computer? Daystrom's right. I can do a lot of other things. Am I afraid of losing the prestige and the power that goes with being a starship captain? Is that why I'm fighting it? Am I that petty?

Kirk has dabbled with self-doubt before but it's never really convinced.

KIRK: I could've prevented all of it.
SPOCK: I don't see how.
KIRK: A walk in paradise, among the green grass and flowers. We should've beamed up at the first sign of trouble.
SPOCK: You are under orders to investigate this planet and this culture.
KIRK: I also have the option to disregard those orders if I consider them overly hazardous. This isn't that important a mission, Spock. Not worth the lives of three of my men. I drop my guard for a minute because I like the smell of growing things, and now three men are dead. And the ship's in trouble.
 
In that scene from The Apple Kirk's self-doubt is there to justify the Enterprise crew massacre which it follows. Three crew have been killed and the script needs Kirk to seem affected. It's an artificial script device because once Kirk has beaten himself up over the deaths of Kaplan, Hendorff, and Mallory it's never mentioned again in the episode; not even when Marple is also killed.

Kirk's self-doubt is handled much better in The Ultimate Computer . “I've never felt this way before. At odds with the ship. I sat there and watched my ship perform for a mass of circuits and relays, and felt useless. Unneeded.” It makes Kirk petty and he takes any chance he can to downplay the achievements of the M-5. “All it's done is make the required course changes and some simple turns. Mister Sulu and Mister Chekov could've done that with their eyes closed.” This time self-doubt is not an emotion he indulges in and forgets, it's a theme running through the first two acts. It humanises Kirk because we can relate to what he is going through. He's not declaiming, “why oh why didn't I realise this weird alien planet was alien and weird?” He's faced with the realisation that he is the best person he knows at doing his job, and yet the machine is better.

With this in mind it's interesting to see the end of act one used as a red herring. “Captain, I've located the source of the power shutdowns. It's the M-5 unit, sir. That thing's turning off systems all over the ship.” Scotty's line bluffs the audience into thinking M-5 is out of control. Throughout act one Kirk and the audience have seen the M-5 unit performing flawlessly. Kirk and the audience are both waiting for the M-5 to fail. Kirk because he doesn't want to be replaced in a job he loves, and the audience because they know the M-5 won't be around next week so it's due to be proved faulty at some point. When Daystrom discovers the reason for the shut downs in the opening moments of act two it's designed to confound audience expectations, “as I suspected, it is not a malfunction. M-5 was merely shutting down power to areas of the ship that do not require it.”

In a different episode the M-5 going mad would be the moment of crisis. Act one would have ended with the discovery that M-5 will not allow itself to be turned off and the remaining three acts would have been about the crew's attempts to disable the rogue machine. Instead of being the crisis point for the whole story the M-5 seizing control is the resolution to the plot about Kirk's fear of replacement, and also ups the stakes for the second half.

Ironically it's the characterisation which stops The Ultimate Computer from achieving it's full potential. Not the characterisation of Kirk, Spock, and McCoy which is spot on. In fact McCoy get all the best lines in the episode, and this is some of the best material he's given across the series. “Did you see the love light in Spock's eyes? The right computer finally came along.” The problem lies with the characterisation of the secondary characters which never quite seems right.

Commodore Wesley really dislikes Kirk. There's his “Captain Dunsel” comment (Dunsel apparently being an academy term for a part which performs no useful purpose) made over an open communicator so the Enterprise bridge crew, and possibly the crew in the other ships, can all hear him burn their captain. Then when the M-5 has taken over and is using lethal force during the war games Wesley believes it's Kirk who is out of control. “Jim. Have you gone mad? What are you trying to prove? Break off the attack! Jim, we have fifty three dead here... If you can hear us, stop the attack.” When the Lexington takes damage there's a shot of Wesley on the bridge asking, “what the devil is Kirk doing?” It brings to mind the season one story Court Martial where the other starship captains at Starbase 11 are all too willing to believe Kirk killed Ben Finney. Unfortunately the episode wants to end with a point about the M-5 lacking the human factor by having Wesley make a leap of faith, “the Enterprise looks dead. I'm going to take a chance he's not just laying a trap.” Kirk is gambling on Wesley's humanity, but if Wesley really thought Kirk had gone mad (and note the 'he' in Wesley's line about laying a trap) and murdered so many with his attack, then would Wesley show any compassion?

Likewise Daystrom is written a little off beam. He's great for the majority of the episode, acting exactly like a proud parent indulging his baby, and always trying to find the best motive for the M-5's increasingly bizarre actions. After the M-5 overrides the off switch Daystrom convinces himself it's in the best interests of the unit to not switch it off. When the M-5 destroys an automated ore freighter he describes this as, “minor difficulties,” and when the computer vaporises engineer Harper while directly tapping the power of the warp engines Daystrom tries to dismiss this as an accident. “The ensign simply got in the way.” However, no matter how wilfully blind Daystrom wants to be there is one moment he can't really ignore.

After the M-5 destroys the automatic ore freighter Kirk, Spock, and Daystrom head to engineering to turn off the M-5, only to find it has protected itself with a force field. “ It's not my doing, Kirk,” says Daystrom, and presumably this means the M-5 was not built with the ability to project force fields; this makes sense it would be rather like fitting airbags to a desktop PC. Still it's not just Daystrom who overlooks this new ability. Once M-5 has repelled Kirk, it's never mentioned again, in fact this amazing ability of the M-5 unit is demonstrated and then shuffled off screen as quickly as possible because it's a sticking plaster on the story logic. An easy answer to someone's question during script development wondering why Kirk didn't just head down to engineering with a phaser and melt the M-5 into slag. Sometimes these fixes make the story stronger, see By Any Other Name and the Kelvan's ability to distill humans into solid shapes which results in the memorable death of Yeoman Thompson, but here it fixes one story logic question only to raise another; why doesn't Daystom notice his computer can do things it was not designed or built to do?

Lastly there's M-5 itself which counts as a character because it's based on Daystrom's engrams. It's never clear why the machine goes mad. It just goes from coping with a surprise simulated attack, to taking pot shots at automatic ore freighters, before moving on to mass murder. Still there's enough slack built into the script to allow viewers to supply their own explanations. Given that Daystrom did imprint his own engrams on the machine it's possible that what we see is overconfidence. The M-5 is as frustrated, for want of a better word, at Kirk for constantly taking the Enterprise back under control as Daystrom, “you'll find it won't be necessary for you to regain control of the unit after it's completed each manoeuvre.” It sees the ore freighter as an opportunity to cut loose and show what it can really do. Overconfidence blinds the M-5 to the consequences of destroying the freighter, and once it realises what it has done it has no alternative but to protect itself by destroying any pursuing ship. 

It's easy to watch The Ultimate Computer and wonder what benefits Starfleet expected from the M-5. Yes the computer was incredibly good at small details, such as recalling personnel details even Kirk didn't have instantly to hand, and it could steer the ship as efficiently as a human navigator, and it was better in direct combat, but when have we ever seen the events in an episode hinge on one of those factors? It's difficult to see what advantages M-5 could have brought to the battle against the Gorn in Arena. How would it have dealt with the Kelvans from By Any Other Name or Apollo in Who Mourns For Adonais? But asking this question misses the point. The episode is not about why Starfleet would want to replace Captain Kirk with a computer, it's about what will happen when computers get clever enough to replace even Captain Kirk. Thematically The Ultimate Computer belongs with stories like The Return Of The Archons, or A Taste Of Armageddon where people's lives and deaths are planned centrally by a big computer. That seems to have been the future perception of computers in 1968. Not the internet, but a big central IBM computer which told you when to work, when to sleep, and when to eat your protein pills. This attitude is the reason Commodore Wesley demands to know what Kirk thinks he is doing when the M-5 attacks the war game fleet. The Ultimate Computer is warning that in the future the infallible computer will be your boss, and when it goes wrong you'll still get the blame.

Enterprise crew deaths: Just one, engineer Harper.
Running total: 46

Sunday, April 7, 2013

By Any Other Name

When talking about Star Trek it's easy to get hung up on big name stories like The Trouble With Tribbles. While these episodes have come to define the series the real joy often comes from discovering (or rediscovering) the stories which don't persistently hang around in top ten lists. By Any Other Name is one of those episodes and it turns out to be a little gem. 

By Any Other Name has a script which constantly wrong foots the viewer about exactly what kind of story they should expect. The episode starts out looking as if it will be I, Mudd with aliens. The teaser, and act one, focus on the Kelvans plot to take over the Enterprise. Kirk, Spock, McCoy, and two other Enterprise crew, are kept hostage to ensure the good behaviour of everyone else while the Enterprise is converted for the 300 year journey back to the Kelvan's home in the Andromeda galaxy. This episode being another addition to the list of stories suggesting the universe outside our galaxy is full of hideous monsters. Spock describes the Kelvans in their native form as, “immense beings [with] a hundred limbs which resemble tentacles."

The Kelvan's main weapon is a nifty little belt device which neutralises nerve impulses to the voluntary muscles leaving the target paralysed. All the elements are in place for this to be a generic Star Trek episode. The conversion of the Enterprise for its intergalactic voyage looks as if is there to add an arbitrary deadline to the story; forcing Kirk to save the day before the Enterprise departs. The aliens main advantage is technological, the belt paralyser, and when head alien Rojan mentions the neural field radiates from a central projector the episode looks set to turn into a game of hunt the power source; like Catspaw. It's easy to imagine how the next three acts will play out. A sequence of captures and escapes as Kirk tries to get hold of a paralysis projector, locate the central unit, and then turn the tables on the aliens by paralysing them until they have learned their lesson.

Still, even at this early stage it's clear the story is more interesting than average. There's an unusual amount of continuity. Spock's prison break technique from A Taste Of Armageddon (using the Vulcan mind meld to trick a guard into believing the Enterprise crew had escaped) is mentioned along with the energy barrier around the galaxy from Where No Man Has Gone Before. We also get to see the Kelvans take over the Enterprise, something which happened entirely off screen in I, Mudd. The takeover is a brisk little 60 second sequence of Kelvans appearing in key sections of the ship and paralysing the crew. It nicely demonstrates the Kelvan's technical superiority and ruthless efficiency. Plus, someone has found some money to give the Kelvans a signature effect. A blue twinkling visual when people are paralysed. This effect is completely unnecessary from a storytelling perspective. It's obvious when the the belt paralyser is used. There's a sound effect and everyone freezes (usually in some exaggerated “oh I can't move” pose, I particularly like Deforest Kelly's finger pointing, opened mouthed, position when McCoy is frozen while turning to say something to Spock). Still it's great that someone found the cash for the effect. It really adds visual interest to the scenes where it features, and its use is positively lavish considering Star Trek's normal frugal use of effects. Where you might see phasers fired once or twice in an episode, the Kelvan's belt paralyser is used twice in the teaser, and then another five times in act one.

The first real indication that events are not going to run as expected comes after the first escape attempt when Rojan tells Kirk, “this cannot go unpunished.” It turns out the Kelvans can reduce humans to small three dimensional objects, “the flesh and brain and what you call the personality, distilled down into these compact shapes.” People distilled down can be restored, but if the shape is crushed the person dies. Rojan demonstrates this on Lieutenant Shea and Yeoman Thompson, crushing Yeoman Thompson's distilled essence and killing her.

Yeoman Thompson's death may be the most disturbing seen on Star Trek. All we see on screen is a three dimensional shape being crushed to powder but somehow it's a weirdly graphic moment. What makes this killing so gruesome? It's hard to describe exactly but it's a combination of causes. There's the demonstration of Rojan's ruthlessness in forcing Kirk to watch a crew member being killed, and his killing of Thompson is literally more hands on than if he had shot her with a phaser, or zapped her with a bolt of lightning. There's the demonstration of Kirk's powerlessness, he cannot do anything except stand and watch. There's also an illogical attachment between Yeoman Thompson and the crushed shape. We've seen Thompson reduced, and we've been told the shape represents her very essence, so it feels as if we are watching Rojan's hand squeezing not just her body but somehow her brain and thoughts as well. On a more physical level crushing the object is not easy. Rojan squeezes once, twice, three times. Each time breaking the object into smaller chunks. Thompson's death would not seem nearly so prolonged or brutal if the shape had immediately exploded into a puff of power, or if Rojan just squeezed it once before dropping the remains on the floor. Lastly it's all too easy to start trying to imagine what the ruin of Thompson's body would look like. Rojan says Thompson cannot be restored to life, but presumably her body could be reconverted back into flesh and blood.

Yeoman Thompson's death is one of those moments which grips the imagination. As the story heads into act two it surprises again when the Enterprise warps out of orbit, and what had looked as if it would be a largely planet based story instead transfers completely to the Enterprise. It rapidly becomes clear that talk of the energy barrier around the galaxy wasn't just to set up the plot. We will actually see the ship attempt to do what it could not in Where No Man Has Gone Before, breach the barrier and head out into intergalactic space. At the same time Spock and Scotty have come up with a suicide plan. The barrier is composed of negative energy. On Kirk's order Scotty will flood the matter-anti-matter nacelles with positive energy and the ship will be destroyed. The result is a tense sequence as Kirk agonises over his decision. It's well edited by film editor James D. Ballas, and made more exciting by simple but effective use of the standard Enterprise control panel beeping noise as Scotty waits for Kirk's order, and by reusing part of Sol Kaplan's score for The Doomsday Machine. The whole sequence is capped cleverly by splitting Chekov's line, “we... made it,” around a shot of the Enterprise zooming towards Andromeda.

Obviously in the end Kirk decides not to blow up the ship, and it's a matter of personal taste as to whether you think his decision was correct or not for the character. As Kirk says in Star Trek II: The Wrath Of Khan, “I don't believe in the no-win scenario.” Sacrificing the crew and ship would feel like Kirk was admitting there are no other possibilities. It solves the short term problem of what to do with this Kelvan scouting party, but for all Kirk knows there could be others. Or the failure of Rojan's group to report in could prompt the Kelvans to send another scouting party which the Federation don't know about, or worse a full scale invasion fleet. Plus at this point Kirk still has a full compliment of crew, he doesn't know Rojan plans to reduce them, so the humans outnumber the Kelvans, and the odds are in his favour. 

The scope of the story narrows in the later part of act three, and act four. With only four Enterprise crew remaining, Kirk, Spock, McCoy, and Scotty, the solution to the problem of defeating the Kelvans turns out to be tempting them with the pleasures of the flesh. Scotty gets Tomar drunk, Kirk seduces Kelinda, Spock expertly plays on Rojan's jealousy of Kirk and Kelinda, and McCoy starts injecting Hanar with stimulants while pretending to give vitamins to the alien. Amusingly no one seems to remember there's a fifth Kelvan on the bridge, Drea. While Tomar gets drunk, Kelinda gets snogged, Rojan gets furious, and McCoy gets Hanar hepped up on goofballs, Drea sits on the bridge patiently steering the ship on its 300 year journey towards Andromeda. She must be baffled to receive Rojan's order to reverse course. These scenes allow for some very good comedy, especially Scotty's drinking contest with Tomar, but there's something disappointing about By Any Other Name ending up as another story in which clever humans outwit superior beings. It's also not helped by repeating similar themes from Return To Tomorrow, although By Any Other Name was made first and is the superior episode of the two.

If the solution to beating the Kelvans is disappointing By Any Other Name does deserve praise for ultimately being resolved by diplomacy and an offer of assistance; admittedly after a fist fight in one of the recreation rooms. A lesser story might have ended with Kirk hoisting the Kelvans on their own petard, maybe paralysing them, or reducing them to cubes and leaving the problem for the future to deal with. One genuinely nice touch about the ending is that the much sought after neural paralysers end up being a Macguffin, and irrelevant to the resolution, to the extent that Scotty passes out just after getting hold of one. Which is probably just as well. The Enterprise corridors are littered with the shapes of the reduced crew. Imagine Scotty trying to deliver the projector while drunk. Kicking a shape here, tripping on one there, knocking off a corner, cracking another, and then probably falling over and crushing a whole load of them at once. 

Enterprise crew deaths: Just one, poor Yeoman Thompson. 
Running total: 44
Misc: More messing around with the closing credits. This time we have a still not from an episode, or a makeup test but a blooper. As William Blackburn peels the Return To Tomorrow android makeup from his head someone, possibly makeup artist Fred Phillips, says, "well, son, you wanted show business. Goddammit, you got it!" and then walks into shot and helps Blackburn pull off some of the latex."

Thursday, March 14, 2013

A Private Litttle War

A Taste Of Armageddon is an allegory of Vietnam war body counts, and more generally about the dangers of making war easy. The Doomsday Machine is an allegory about nuclear weapons. A Private Little War is a 1968 allegory of the Vietnam war itself. However where A Taste Of Armageddon and The Doomsday Machine are both clearly against the subject of their allegories A Private Little War surprises by being very much a pro-Vietnam war story.

The allegory is most clearly stated by Kirk towards the end of the episode when he decides the only solution is to begin arming the hill people with the same flintlock rifles the Klingons have been secretly supplying to the villagers.

KIRK: .. What is your sober, sensible solution to all this? 
MCCOY: I don't have a solution. But furnishing them firearms is certainly not the answer.
KIRK: Bones, do you remember the twentieth century brush wars on the Asian continent? Two giant powers involved, much like the Klingons and ourselves. Neither side felt could pull out.
MCCOY: Yes, I remember. It went on bloody year after bloody year.
KIRK: What would you have suggested, that one side arm its friends with an overpowering weapon? Mankind would never have lived to travel space if they had. No. The only solution is what happened back then. Balance of power.
MCCOY: And if the Klingons give their side even more?
KIRK: Then we arm our side with exactly that much more. A balance of power. The trickiest, most difficult, dirtiest game of them all, but the only one that preserves both sides. 

There's an often used quote from Gene Roddenberry, “I realised that by creating a separate world, a new world with new rules, I could make statements about sex, religion, Vietnam, politics, and intercontinental missiles. Indeed, we did make them on Star Trek: we were sending messages and fortunately they all got by the network.” In the case of A Private Little War it's hard to believe the network would have cared about the message if it had been spotted. 

Star Trek's contemporary audience is often described as containing a large proportion of  high school and college students. How did they react to being lectured about the importance of the Vietnam war by Gene Roddenberry? There's nothing wrong with confronting your audience with ideas and opinions to which they may be opposed. It makes the audience think about why they disagree with the message, and stops them being just passive consumers. That said there is something distasteful about a 46 year old man, well outside the 18-26 draft range of men eligible for selective service, lecturing about the importance of a war which was a very real worry for a large chunk of their target audience. 

What we have here is an actual, genuine generation gap. In 1968 the Second World War had ended 22 years ago. Gene Roddenberry, Robert Justman, and Gene L. Coon had all fought in different branches of the armed forces. Gene Roddenberry volunteered for the United States Army Air Corps, and took part in missions in the South Pacific. Robert Justman served two years in the Navy. Gene L. Coon was in the Marines from 1942 to 1946, and then having enlisted in the Marine reserves was called back to serve in the Korean war from 1950 to 1952. Unlike their young audience World War Two was a reality to them, as was the development and use of atomic weapons, the rise of the Soviet Union, and the Korean war. To a 20 year old viewer even something as recent as the Cuban missile crisis, took place when they were 14; a quarter of their life previously. Seen in this context A Private Little War seems less like the polemic of a typewriter warrior, and more a warning from someone who had fought in World War Two and didn't want to see it refought with atomic weapons. It also explains the odd, slightly dismissive way anti-war protesters are treated in The City On The Edge Of Forever.

Moving away from the tricky area of politics A Private Little War see the Klingons back after their last appearance in Friday's Child. In Friday's Child Kras the Klingon hoped to persuade the natives of Capella IV to cede to the Klingon Empire by backing the more aggressive tribal leaders. Here Krell, who isn't named on screen, is repeating the trick in a slightly more subtle way by supplying weapons primitive by Klingon standards to the villagers, and encouraging them into a war against the hill people. Friday's Child and A Private Little War both show the Klingons beginning to react to the peace forced upon them by the Organians in Errand Of Mercy. They can no longer add planets to their empire simply by invading them. Instead they act as agents of corruption, feeding on people's greed, and turning them into proto-Klingons by using existing disputes to their advantage.


KRELL: You are late, my friend Apella.
APELLA: A quarrel by my people. A division of some skins and a hill woman taken this morning. It's hard to divide one woman.
KRELL: Give her to the man who killed the most of her people. The others will see the profit in bravery. I'll make a Klingon of you yet. 

and 

APELLA: I thought my people would grow tired of killing. But you were right. They see that it is easier than trading and it has pleasures. I feel it myself. Like the hunt, but with richer rewards.
KRELL: You will be rich one day, Apella, beyond your dreams. The leader of a whole world. A governor in the Klingon Empire.
 

It's not clear why the Organians tolerate this subversion of their treaty. Maybe it's only direct war they care about, but in Errand Of Mercy it was the act of violence itself they found distasteful so presumably they just don't know. There must be some limit to the Organian's ability to detect and prevent conflict between the two sides, and the Klingon's actions here are part of the process of working out exactly what are the Organian's limits.

The script of A Private Little War is a little confused about the exact nature of the peace treaty. Kirk talks about it as if it was an actual physical object signed by both sides, “if the Klingons are breaking the treaty it could be interstellar war,” he says. According to Errand Of Mercy the one thing breaking the treaty cannot lead to is interstellar war. Later when Kirk and McCoy sneak into the village they gather evidence as if there is some Galactic United Nations they can appeal to, and hand over any proof they find. This is a little more consistent with earlier episodes. The Trouble With Tribbles established that Sherman's planet would be given to whichever side could develop it most effectively. Possibly if Kirk can prove the Klingons are cheating then the Organians will enforce some penalty on the Klingon Empire in the disputed quadrant referred to in The Trouble With Tribbles. 

The Klingons motivation for all this secret interference is unclear. In Friday's Child both sides are interested in Capella IV because it is rich in the mineral topaline. At the start of A Private Little War McCoy talks vaguely about interesting organic compounds with medical benefits, and presumably the Klingons are also after these compounds. However they could just be interfering out of sheer devilment. Maybe they read the planetary survey report Kirk wrote 13 years ago, using more of their surgically altered spies, and know Kirk has a fondness for this world. Perhaps it is just a way to expand their empire while keeping within the provisions of the treaty. To extend the Vietnam analogy, if the Klingons are the Soviets then they will want their own Warsaw Pact; dependant territories to act as a buffer zone and provide defence in depth against invasion. 

The skimpy character motivation extends to Nona, Tyree's wife. She is frustrated by Tyree's pacifist ways, and wants him to get some “firesticks” and do to the villagers what the villagers are doing to the hill people. So why did she marry him? Tyree says he married her after she cast a spell over him, so he must have had something she wanted. In the end she's just a power hungry woman who is willing to sell out her husband, and his tribe. There's some poetic justice in the way she ends up dead at the hands of a village hunting party who do not understand the advantage Kirk's stolen phaser would give them.

If Krell was going to all this trouble to turn the planet into a Klingon satellite state then there is also no small irony in the fact that he taught the villagers to act like Klingons. If they had been more interested in the phaser than Nona, they might have brought it to him. He could then present it to the Organians as 'proof' of Federation interference, arming the hill people with superior weapons, and gain whatever benefit Kirk thought would come from exposing the Klingon plan.

This is an episode with a lot of stuff going on in the background, but unfortunately what is foregrounded is a rather dull tale of goodies and baddies in which the nasty villagers wage war on the nice hill people. The morality really is that simplistic. The hill people are the goodies because they are the underdogs in the war, and Kirk is friends with one. The villagers are nasty because they have aligned themselves with the evil Klingons. It's a western, and while the goodies and baddies may not wear white and black hats the hill people do have blonde hair, and the villagers black hair; as does nasty Nona.
 


Extensive location work cannot save this story. Nor can some excellent editing from Donald R. Rode. The Mugato may look silly, think albino gorilla with spines and a single giant horn growing from the top of the head, but its attack on Kirk is well handled and comes out of nowhere. The introduction of Krell is also striking. A cut to a big close-up of the Klingon gazing into the camera as he waits for Apella. 

Is Kirk right? Yes within the confines of the script and the extremely narrow set up of the world. A balance of power is the correct solution. Maybe if the war between the hill people and the villagers can be maintained as a stalemate for long enough then both sides will learn it is unwinnable and return to their peaceful ways. Maybe. But how long can the Federation keep sending down flintlocks every time the Klingons send down flintlocks? What if the Klingons send grenades, or automatic weapons? What happens if the leader of the villagers invites the Klingons to help out by sending in military advisers? Will the Federation follow Kirk's plan and match the Klingons bomb for bomb, adviser for adviser, conscript for conscript? Evidentially not because if it had the space hippies who turn up in The Way To Eden would have sat on the transporter pad, burnt their draft cards, and chanted, “hey, hey JTK, How many kids did you kill today?” 

Enterprise crew deaths: Once again none, the Enterprise crew start making plans for the future. 
Running total: 43

Misc:
Lots of shenanigans with the closing credits this week. To start with the most confusing one, this is the producer credit for the episode.
 My understanding is that the previous episode made, Journey To Babel, marked the first episode produced by John Meredith Lucas so I'm not sure why Gene L. Coon is suddenly being credited as the producer again. The only explanation I can think of is that before he left Gene L. Coon did the bulk of the production work on A Private Little War, and it was felt more appropriate to give him the credit than John Meredith Lucas.

One of the closing stills appears to be a make-up test for a Tellarite from Journey To Babel.

Lastly, the Mugato is credited as the Gumato. Apparently this was the original name for the creature but DeForest Kelly could not pronounce the name so it was changed. Evidently the change never reached whoever did the closing titles: Gumato/Mugato Mugato/Gumato, let's call the whole thing off.