I'm going to try rewriting "Nemesis" (long post)
Posted: 2003-09-20 04:03am
I've been working on a script for "Nemesis" that makes a little more sense, but find that B&B have made mistakes in the previous flicks' plots (and series' plots, and technology, and Federation politics, and...) that make it pretty hard...but I'd like suggestions on this nonetheless. I guess some specific areas should be established:
1.) The Enterprise-E.
What tech should the Enterprise have or not have, and how should it figure? This being weapons, transporters, engines, what have you.
My ideas for the E-E: It should (like any ship its size) have several thousand of each type of torpedo. I'd like quantum torpedoes of course, and I don't think photons are obsolete either. I think Voyager should be as utterly ignored as possible (no Janeway cameo!!!), but that armor looks great. I'd make it a combination of quickly replicated metal armor, forcefields, and holograms that disguise the weapons ports. The joystick in "Insurrection" wasn't a bad idea at all (Trek controls are generally unintelligible, which this gamer can't stand), but I'd make the manual controls more comprehensive (an obvious throttle on one side, pitch controls and such). And I'd mount them in front of the center chair instead of the middle of the bridge. I'd also work on new controls and displays that look like you can actually understand them. How many numbers do you have to memorize to operate one of these consoles? No. No more Okudagrams or LCARS or whatever you want to call it. I want buttons and handles. And fewer colors on the screens. Glad to finally see pen input again, though. My whole deal with the controls - some Trekkers can't stand a technology if they don't know how it works. I can't stand not knowing how a ship is piloted. I see this or that maneuver and think, how'd they do that? Obviously you can put thrusters all over the ship or say it's got omnidirectional engines, but I always obsess over how you'd TELL the ship to do this or that.
And no more exploding consoles. But I do have one possible explanation for why the inertial dampers don't take care of weapons impacts. Maybe the dampers are part of the engines (one set for warp and one for impulse), and take their cues directly from the maneuvers the ship is making.
2.) Cinematography.
I thought that "Nemesis" had the best photography and rendering of any Trek production, but it lacked a certain scale of the sort found in SW or a decent Spielberg flick (I loved the visuals in "Artificial Intelligence"). There should be oodles of ships flying around Romulus, and I'd like to see the Scimitar's weapon in action, both from space and on the ground.
3.) Plot.
Shinzon didn't have sufficient motivation for his attack on the Federation (the whole "bow before anyone as slaves" bit just doesn't work). Maybe he's still bent on replacing Picard? Or better yet, some Federation mistake during the Dominion War got one of his commands destroyed, and a shitload of his Reman buddies killed. Things have just gotten worse for the Remans since the war, and Shinzon blames the Federation for getting them involved in the first place. Maybe he's come to see the Federation as a magnet for trouble from other quadrants - the Dominion, the Borg, etc. I also had my qualms about his age - he was created long before Picard was captain of the Enterprise, so there'd have to be some explanation for how they knew Picard would become so important. Maybe the Stargazer posting was more momentous than we previously knew?
Let's explain why Worf is back. He really could say, "Diplomacy's interesting, but I'd rather bust some heads." And not see Wesley Crusher. Ever again. And not mention that he ever existed. He's our dark secret, okay?
I hated the way they turned back the clock on Data's emotional development, although I thought the emotion chip was a cop-out to start with. I thought Data should have found emotion through his own efforts. Anyway, I'd have him be somewhat emotional in this one. And I'd have him cry when he realizes that yet another brother is going to be a disappointment. I'd handle it this way. He's wiping tears outside the lab where B4 is stored, then dries his eyes, steels himself and walks in. He has the conversation with B4 about the Reman programming, but just as he's about to turn B4 off, B4 says, "Brother...I...do not want to be dangerous." And this makes Data's whole week. He smiles and replies, "We'll find a way to help you." B4 is satisfied by this, and Data shuts him off. And I think B4 could be just as endearing without having to be a crude prototype. Let's just say he lacks any real-world experience and is basically a really smart child.
I'd also like to see Data angry at the brainwashing of his brother, and have a beatdown scene vs. the Viceroy. I'd cut out the whole mind-rape thing with Troi, and make the Viceroy the one who reprogrammed B4. So one way or another Data finds himself on the Scimitar, and beats the means for de-brainwashing B4 out of the Viceroy. He leaves the Viceroy alive, but the Viceroy moves to get a weapon and shoot Data in the back. He manages to get Data in the shoulder (with little damage and perhaps an amusing expletive from Data), but Data pulls a knife from a desk and chucks it into the Viceroy's throat. Why Data's not armed, I'm not sure. Maybe he's disguised as B4, and this is just before the scene where he rescues Picard from the Reman doctors.
4.) The Scimitar.
I find it wholly absurd that a handful of Reman conspirators could build a ship that two of the biggest military-industrial complexes (Starfleet and the Romulan Star Empire) in the quadrant couldn't rival. So the Scimitar is a captured Dominion experiment, and wasn't used in the Dominion war because the planetkilling weapon didn't work yet. Shinzon perfected it, also adding the cloak. This still makes the Scimitar's acquisition a hell of an accomplishment on Shinzon's part, and explains why he's able to find enough Remans to man it (Dominion ships don't seem to need large crews to operate them).
5.) Data.
Other things I'd establish about Data - he's beefed himself up since the unfortunate impaling incident, and is now fortified against blunt force weapons, stabbing, small firearms, and energy weapons up to a certain yield (although this doesn't have to all be explained verbally). And he's got site - to - site transporters built in.
6.) The Romulan warbirds and other artistic concerns.
I see no reason that any given race's ships have to be of a certain color, so I'd make these things red or silver. And I'd have them called "Tal'aura class." Let's say Senator Tal'aura (the one who kills the Senate) was overseeing the construction of this new class, and had a couple ready to use against Shinzon.
7.) Action.
Let's keep the Argo chase, but make the Kolarins a xenophobic race that's just developed warp drive and is still largely nomadic. So we can fire our phasers all we want. Let's give the Argo seatbelts, armor plating and shields, and make it a little more inventive design (maybe three wheels, 1 in front and 2 in back, each on a housing with a single seat?). I'd also like to see the runabout take missile damage just after the car jumps into it (explaining why the shields aren't up yet), so it can fly but is no longer spaceworthy. The Enterprise has to fly in low and tractor it into a shuttlebay (it could bank sideways to turn the shuttlebay towards the runabout).
I liked the battle against the cloaked Scimitar, but let's send some warp-capable shuttles (fighters) through the Bassen Rift to warn the Fleet. There could be a warp-speed chase, with ships exploding and the debris dropping out of warp. Finally the fleet is warned, and we get a nice big battle against the Scimitar.
I'd explain the Scimitar's ability to disable the E-E's warp drive with the fact that...well, 56 disruptor banks and 27 photorp tubes. As the E-E approaches the Rift, we see an insane hail of weapons fire pouring out of the cloaked Scimitar, targeting the engines (Shinzon can't destroy it, since he needs Picard's blood...). And maybe the E-E's armor can't be deployed at warp.
I'd give the Fleet time to arrive by having a longer battle aboard the Enterprise. Let's say the Scimitar disables one of the Romulan ships, then tractors it into the Enterprise while destroying it with torpedoes. This doesn't totally wreck the armor, but creates a visible gap that lets the Remans beam aboard and try kidnapping Picard. And it allows the holographic face-to-face between Shinzon and Picard, albeit later. And if the armor on the front edge survives, we can rip the Scimitar in half when we ram it.
8.) Other stuff.
A word on the replicated armor - replicators are not the same thing as SW Duplicators (which I'm not even sure are canon tech, canon to me meaning in any SW movie). Duplicators rearrange existing matter. Replicators work more like transporters. They turn energy into matter (and back - that's how you get rid of the dishes). But this would explain why the armor can't be deployed at warp - it takes too much energy at once to replicate the metal bits. Once the armor is up, you can go back to warp, but by then the E-E's warp drive is already damaged.
Any other ideas?[/i]
1.) The Enterprise-E.
What tech should the Enterprise have or not have, and how should it figure? This being weapons, transporters, engines, what have you.
My ideas for the E-E: It should (like any ship its size) have several thousand of each type of torpedo. I'd like quantum torpedoes of course, and I don't think photons are obsolete either. I think Voyager should be as utterly ignored as possible (no Janeway cameo!!!), but that armor looks great. I'd make it a combination of quickly replicated metal armor, forcefields, and holograms that disguise the weapons ports. The joystick in "Insurrection" wasn't a bad idea at all (Trek controls are generally unintelligible, which this gamer can't stand), but I'd make the manual controls more comprehensive (an obvious throttle on one side, pitch controls and such). And I'd mount them in front of the center chair instead of the middle of the bridge. I'd also work on new controls and displays that look like you can actually understand them. How many numbers do you have to memorize to operate one of these consoles? No. No more Okudagrams or LCARS or whatever you want to call it. I want buttons and handles. And fewer colors on the screens. Glad to finally see pen input again, though. My whole deal with the controls - some Trekkers can't stand a technology if they don't know how it works. I can't stand not knowing how a ship is piloted. I see this or that maneuver and think, how'd they do that? Obviously you can put thrusters all over the ship or say it's got omnidirectional engines, but I always obsess over how you'd TELL the ship to do this or that.
And no more exploding consoles. But I do have one possible explanation for why the inertial dampers don't take care of weapons impacts. Maybe the dampers are part of the engines (one set for warp and one for impulse), and take their cues directly from the maneuvers the ship is making.
2.) Cinematography.
I thought that "Nemesis" had the best photography and rendering of any Trek production, but it lacked a certain scale of the sort found in SW or a decent Spielberg flick (I loved the visuals in "Artificial Intelligence"). There should be oodles of ships flying around Romulus, and I'd like to see the Scimitar's weapon in action, both from space and on the ground.
3.) Plot.
Shinzon didn't have sufficient motivation for his attack on the Federation (the whole "bow before anyone as slaves" bit just doesn't work). Maybe he's still bent on replacing Picard? Or better yet, some Federation mistake during the Dominion War got one of his commands destroyed, and a shitload of his Reman buddies killed. Things have just gotten worse for the Remans since the war, and Shinzon blames the Federation for getting them involved in the first place. Maybe he's come to see the Federation as a magnet for trouble from other quadrants - the Dominion, the Borg, etc. I also had my qualms about his age - he was created long before Picard was captain of the Enterprise, so there'd have to be some explanation for how they knew Picard would become so important. Maybe the Stargazer posting was more momentous than we previously knew?
Let's explain why Worf is back. He really could say, "Diplomacy's interesting, but I'd rather bust some heads." And not see Wesley Crusher. Ever again. And not mention that he ever existed. He's our dark secret, okay?
I hated the way they turned back the clock on Data's emotional development, although I thought the emotion chip was a cop-out to start with. I thought Data should have found emotion through his own efforts. Anyway, I'd have him be somewhat emotional in this one. And I'd have him cry when he realizes that yet another brother is going to be a disappointment. I'd handle it this way. He's wiping tears outside the lab where B4 is stored, then dries his eyes, steels himself and walks in. He has the conversation with B4 about the Reman programming, but just as he's about to turn B4 off, B4 says, "Brother...I...do not want to be dangerous." And this makes Data's whole week. He smiles and replies, "We'll find a way to help you." B4 is satisfied by this, and Data shuts him off. And I think B4 could be just as endearing without having to be a crude prototype. Let's just say he lacks any real-world experience and is basically a really smart child.
I'd also like to see Data angry at the brainwashing of his brother, and have a beatdown scene vs. the Viceroy. I'd cut out the whole mind-rape thing with Troi, and make the Viceroy the one who reprogrammed B4. So one way or another Data finds himself on the Scimitar, and beats the means for de-brainwashing B4 out of the Viceroy. He leaves the Viceroy alive, but the Viceroy moves to get a weapon and shoot Data in the back. He manages to get Data in the shoulder (with little damage and perhaps an amusing expletive from Data), but Data pulls a knife from a desk and chucks it into the Viceroy's throat. Why Data's not armed, I'm not sure. Maybe he's disguised as B4, and this is just before the scene where he rescues Picard from the Reman doctors.
4.) The Scimitar.
I find it wholly absurd that a handful of Reman conspirators could build a ship that two of the biggest military-industrial complexes (Starfleet and the Romulan Star Empire) in the quadrant couldn't rival. So the Scimitar is a captured Dominion experiment, and wasn't used in the Dominion war because the planetkilling weapon didn't work yet. Shinzon perfected it, also adding the cloak. This still makes the Scimitar's acquisition a hell of an accomplishment on Shinzon's part, and explains why he's able to find enough Remans to man it (Dominion ships don't seem to need large crews to operate them).
5.) Data.
Other things I'd establish about Data - he's beefed himself up since the unfortunate impaling incident, and is now fortified against blunt force weapons, stabbing, small firearms, and energy weapons up to a certain yield (although this doesn't have to all be explained verbally). And he's got site - to - site transporters built in.
6.) The Romulan warbirds and other artistic concerns.
I see no reason that any given race's ships have to be of a certain color, so I'd make these things red or silver. And I'd have them called "Tal'aura class." Let's say Senator Tal'aura (the one who kills the Senate) was overseeing the construction of this new class, and had a couple ready to use against Shinzon.
7.) Action.
Let's keep the Argo chase, but make the Kolarins a xenophobic race that's just developed warp drive and is still largely nomadic. So we can fire our phasers all we want. Let's give the Argo seatbelts, armor plating and shields, and make it a little more inventive design (maybe three wheels, 1 in front and 2 in back, each on a housing with a single seat?). I'd also like to see the runabout take missile damage just after the car jumps into it (explaining why the shields aren't up yet), so it can fly but is no longer spaceworthy. The Enterprise has to fly in low and tractor it into a shuttlebay (it could bank sideways to turn the shuttlebay towards the runabout).
I liked the battle against the cloaked Scimitar, but let's send some warp-capable shuttles (fighters) through the Bassen Rift to warn the Fleet. There could be a warp-speed chase, with ships exploding and the debris dropping out of warp. Finally the fleet is warned, and we get a nice big battle against the Scimitar.
I'd explain the Scimitar's ability to disable the E-E's warp drive with the fact that...well, 56 disruptor banks and 27 photorp tubes. As the E-E approaches the Rift, we see an insane hail of weapons fire pouring out of the cloaked Scimitar, targeting the engines (Shinzon can't destroy it, since he needs Picard's blood...). And maybe the E-E's armor can't be deployed at warp.
I'd give the Fleet time to arrive by having a longer battle aboard the Enterprise. Let's say the Scimitar disables one of the Romulan ships, then tractors it into the Enterprise while destroying it with torpedoes. This doesn't totally wreck the armor, but creates a visible gap that lets the Remans beam aboard and try kidnapping Picard. And it allows the holographic face-to-face between Shinzon and Picard, albeit later. And if the armor on the front edge survives, we can rip the Scimitar in half when we ram it.
8.) Other stuff.
A word on the replicated armor - replicators are not the same thing as SW Duplicators (which I'm not even sure are canon tech, canon to me meaning in any SW movie). Duplicators rearrange existing matter. Replicators work more like transporters. They turn energy into matter (and back - that's how you get rid of the dishes). But this would explain why the armor can't be deployed at warp - it takes too much energy at once to replicate the metal bits. Once the armor is up, you can go back to warp, but by then the E-E's warp drive is already damaged.
Any other ideas?[/i]