I stand corrected. But thanks anyway. 

Not to pick on this post, but it illustrates a common thing that happens when hardcore fans critique a story or try to wrote one: not focusing on the drama but on some aspect of the plot or setting that to any non-fan would just be background.**** POTENTIAL SPOILERS ABOUT STARSHIP INTREPID ****
My biggest issue with Heavy Lies the Crown and Transitions and Lamentations is that I would expect the Federation to reassess the colonization request after the first attack, before allowing colonization to proceed. In particular, I would expect the Federation to wish to determine first why the Surai are attacking, and whether they already have any legitimate claim to the Charybdis Sector...
Respectfully, I have to disagree (at least partially) on this point Maurice, because I think what happens to Hunter after the teaser does drive his decision to assume the mantle of command, we just don't do as good a job of portraying that as we should have.My problem with the episode is more fundamental. My take on it is the Problem is that Hunter must decide whether or not to accept promotion to a position he's not comfortable taking, which is all fine and good, and a valid Problem. The trouble is, the Complications in the story don't take off from the Inciting Incident that put Hunter in this position, and the plot event don't actually seem to make his decision harder. What in the ensuing situation makes drives Hunter to make the Decision he ends up making?
Now you see that doesn't work for me dramatically. Hunter may be the Captain, but Stiles is the science officer. That sort of thing should come from her, IMO. She made the suggestion, as CO Hunter ran with it. That's the way it should be. Indeed, he goes on to do exactly what you then suggest, insisting he lead the Away Team, and pushing Prentice to let him do it (against another officers objections). Which, to my mind, is pretty proactive.Here's my stab at critiquing the drama. The end of the opening segment of Heavy Lies the Crown is one of the finer moments I've seen in Star Trek fan films. I guess what Maurice is getting at is that, in the context of the episode then, fallout from that decision should have made another, later choice more agonizing.
Here are three opportunities that I've identified in the story to do that:
1. The first is in the decision to go down on the away mission in order to avoid bombarding the site. From a dramatic perspective, perhaps the problem here is that it was not really Hunter's idea to go down to the surface; it was Stiles'. It's fine to have competent officers, but this should be Hunter's story. If it had been wholly Hunter's idea, then it could have been framed as Hunter trying to avoid directly repeating what he had to do to Captain Talath in the teaser, by risking his own life to give those whom he might need to bombard more of a chance. The point is more or less made, but Hunter is reacting rather than driving the action (another common complaint in fan films, I believe). But even at this point, the story still has a long way to go (ETA: i.e., it is far from over).
In fact, that is in there, specifically in the transporter room scene, IIRC, but I realise a lot of stuff gets lost in the awful audio track. Also, I'd say Hunter gets his moment here by pretty much doing the Security Chief's job for him.2. I apologize if you did this in the episode, but I don't remember exactly, but making it so that the phaser modifications to cut through the dampening field only worked for kill settings on the phasers would have made things much more dramatic when Hunter and S'Ceris are pinned down by the pair of obstinate colonists. Again Hunter should be the one to reason with the pair, and Hunter should be faced again with a decision of whether to kill them in order to carry out the mission.
That's a fair point, but there were two reasons I didn't do that. Firstly, I really wanted to have S'Ceris prove his worth to Hunter. Secondly, I desperately wanted to avoid making Hunter a Mary Sue. Having Hunter come up with all the solutions, then implementing them himself, and being the one to make the big run, then drag Cole to safety would have been just too much to my mind.3. Finally, the decision to home in on the communicator to target phasers should have been Hunter's. Hunter himself should have had to run closer to the target area, before throwing his combadge, because it was that far.
The thing is I don't see Hunter as a bystander here. He's fairly proactive where it matters. What we needed was more time to get under his skin, so see what he's thinking and what he's going through, and why he does what he does. We get a bit of that in the early scene with Prentice, then again in the final scenes with Caed, then in the office with S'Ceris, but not enough to make his journey as satisfying as it could be.A common thread here is to make Hunter less of a bystander and more a driving force in the action. Constantly weighing decisions of life and death, whether to kill others, whether to risk their lives, and whether to risk his own, fits in with the theme suggested by the title, "Heavy Lies the Crown". It lies heavy, not just because of what he did to assume command, but from the decisions he must make continually while in command.
In summary, my suggestions revolve around the idea that the away mission is the setting for the drama to unfold. Finally, trimming the running time to focus more specifically on the story of the hero, Hunter, and the away mission in particular, might be indicated.
And to you.I'm out till the New Year probably. Season's Greetings to all.
My pleasure. And my thanks to you, I'm enjoying it.P.S. Oh, and last but not least, thanks, Nick, for being so gracious, in encouraging discussion of your work.![]()
As always, thanks for being so open to discuss. I always appreciate that you're willing to entertain critique even if you happen to disagree. That's a very professional attitude.Respectfully, I have to disagree (at least partially) on this point Maurice, because I think what happens to Hunter after the teaser does drive his decision to assume the mantle of command, we just don't do as good a job of portraying that as we should have.My problem with the episode is more fundamental. My take on it is the Problem is that Hunter must decide whether or not to accept promotion to a position he's not comfortable taking, which is all fine and good, and a valid Problem. The trouble is, the Complications in the story don't take off from the Inciting Incident that put Hunter in this position, and the plot event don't actually seem to make his decision harder. What in the ensuing situation makes drives Hunter to make the Decision he ends up making?
I also don't entirely agree that the events from the teaser aren't related to the rest of the plot. It is the driving force behind Hunter's actions, his dilemma arises directly from that incident. Again, though, I'd agree that's not as clear as it could be. However, I would suggest that just because it isn't a physically linked event doesn't separate it emotionally from everything else.
There are essentially two stories running side by side here. The situation with the colony, and Hunter's dilemma (which is really the major plot). Hunter works through his issues by actually being a good leader when it counts, eventually deciding he is (mostly) competent and the right person to assume command, having grown into the role throughout the story. Now this may not be entirely clear in what ended up on screen, but that's what I was going for.
I think some of this is lost in the shuffle because there's actually too much plot (another reason I really regret the Section 31 subplot). And that really is the major issue I personally have with it; there's far too much going on, and the major theme does tend to get a lost.
Now I do agree, the script really could have done with another pass or two, but like I said, for a first effort its really not that bad. Heck, I didn't know anything about three act structure back then, so it's a miracle it's as coherent as it is.
As far as comparing it to The Cage, keep in mind I was trying to emulate a TNG/DS9 type story, so the intent was for more of an ensemble show than TOS.![]()
Possibly, but that wouldn't solve the problem, IMO. It'd really need a rewrite and additional material. And if we were going to do that, we'd be as well just remaking it. Which is actually an idea I've occasionally toyed with, but to be honest the story's been told, warts and all. It is what it is, and I'd rather move on to new material.I haven't watched the entire episode closely enough to make this anything but an off the wall suggestion, but would it be possible to re-edit the episode to excise the Section 31 plot without eviscerating the story flow? Just a thought...
I agree, that's pretty much what I was saying upthread.While I take your point, I agree that perhaps the flaw is in the implementation rather than in the through-line of the story.
That's pretty much spot on. I'll also add, I didn't want Hunter to be 'Captain Perfect' either, I wanted a flawed hero (and I use the term hero very loosely here) rather than another cookie-cutter perfect Star Trek captain. But yes, that is exactly the journey I was going for. I do think it gets lost in the shuffle a bit, and doesn't get the attention it should have, but I do believe the core of that journey is there.What I thought you were trying to get across was what I call "betraying yourself to yourself", in which a character thinks they shouldn't/cannot do something, but their very actions reveal to them that they actually can/should do it. Hunter doesn't think he should be the Captain, but he ends up acting like one, and comes to recognize this in himself.
Am I warm?
I think it's a major problem, and some of the finer points are undeniably lost to sound issues. It's long been one of the more frustrating elements for me.I agree that the sound issues hurt the overall presentation. I'm not thrown by the accents, but the sound was pretty muddy in places and I did have a difficult time catching everything that was said.
We use essential cookies to make this site work, and optional cookies to enhance your experience.