History Headscratchers / StarTrekNemesis

25th Oct '17 8:59:10 PM costanton11
Is there an issue? Send a Message


** That they reward people who unite two hostile crews, cross a considerable portion of a hostile, uncharted quadrant, making friendly contact with dozens of species, saved the galaxy from a species from another dimension or two and crippled the borg? And they don't punish people for getting grabbed by hyper advanced technology against their will. And hell, she DID bring them back like she was supposed to.

to:

** That they reward people who unite two hostile crews, cross a considerable portion of a hostile, uncharted quadrant, making friendly contact with dozens of species, saved the galaxy from a species from another dimension or two and crippled the borg? Borg? And they don't punish people for getting grabbed by hyper advanced technology against their will. And hell, she DID bring them back like she was supposed to.



*** This troper I don't think she was in charge of diplomacy anymore then any other branch. She's either just happened to be the one on duty at the time or she just was the one selected to call Picard. Stafleet Command probably received the Romulan call for a diplomatic meeting, relayed it to the Federation Council and then the Federation Council (doubtlessly after some debate) called up Starfleet Command and told them to send somebody to take the Romulans up on their offer. Janeway just probably happened to be around at the time.

to:

*** This troper I don't think she was in charge of diplomacy anymore then any other branch. She's either just happened to be the one on duty at the time or she just was the one selected to call Picard. Stafleet Starfleet Command probably received the Romulan call for a diplomatic meeting, relayed it to the Federation Council and then the Federation Council (doubtlessly after some debate) called up Starfleet Command and told them to send somebody to take the Romulans up on their offer. Janeway just probably happened to be around at the time.



* During Data's wake at the end of the film, the remaining crew toast their fallen comrade... using a wine labelled ''Château Picard''. Huh? given how Picards whole family was killed years before, who the hell is still bottling this stuff? clearly it isn't Jean Luc and Robert had no visible staff during ''Family'' - and given how his brother chastised Jean Luc's wine palette getting degraded by synthahol, I find it highly unlikely he actually kept bottles of the stuff just lying around his quarters.

to:

* During Data's wake at the end of the film, the remaining crew toast their fallen comrade... using a wine labelled ''Château Picard''. Huh? given how Picards Picard's whole family was killed years before, who the hell is still bottling this stuff? clearly it isn't Jean Luc and Robert had no visible staff during ''Family'' - and given how his brother chastised Jean Luc's wine palette getting degraded by synthahol, I find it highly unlikely he actually kept bottles of the stuff just lying around his quarters.



*** The "phaser to the warp core" method would require someone in engineering to know they needed to take a phaser to the warp core... which I don't think they could do, since I believe shipboard communications were down. (Besides, if you were in the middle of a fight with a ship that you knew had a clone of your captain on board, and your captain suddenly called you and said "Blow up the warp core!", would ''you'' do it?) Add to that, since a warp core breach is pretty much "instant death for the ship and anything within viewing distance of it", there's probably pretty heavily-done safeguards... like a nuclear weapon, causing an explosion to the warp core itself might indeed cause a nice big explosion, but only enough to wipe out engineering and the deck above and below or somesuch. Causing a deliberate warp core breach is probably actually quite difficult, as it ''should be''.

to:

*** The "phaser to the warp core" method would require someone in engineering to know they needed to take a phaser to the warp core... which I don't think they could do, since I believe shipboard communications were down. (Besides, if you were in the middle of a fight with a ship that you knew had a clone of your captain on board, and your captain suddenly called you and said "Blow up the warp core!", would ''you'' do it?) Add to that, since a warp core breach is pretty much "instant death for the ship and anything within viewing distance of it", there's probably pretty heavily-done safeguards... like a nuclear weapon, causing an explosion to the warp core itself might indeed cause a nice big explosion, but only enough to wipe out engineering and the deck above and below or somesuch.some such. Causing a deliberate warp core breach is probably actually quite difficult, as it ''should be''.



*** This is something that's bugged the crap out of me about Star Trek for a long time. Whenever the ship has a hiccup, the intercoms go down; right along with, for some reason, the commbadges. We've seen commbadges used for person-to-person communication on away missions before, so you would expect them to be able to work independently of the ship. How is it that there's never a backup system? A pair of simple, been-around-in-the-real-world-for-70-years, sound-powered telephones could ensure that the bridge could always stay in touch with the engine room even if the power was out and all of the batteries on the ship were completely dead.

to:

*** This is something that's bugged the crap out of me about Star Trek for a long time. Whenever the ship has a hiccup, the intercoms go down; right along with, for some reason, the commbadges. combadges. We've seen commbadges combadges used for person-to-person communication on away missions before, so you would expect them to be able to work independently of the ship. How is it that there's never a backup system? A pair of simple, been-around-in-the-real-world-for-70-years, sound-powered telephones could ensure that the bridge could always stay in touch with the engine room even if the power was out and all of the batteries on the ship were completely dead.



** Deep space nine concluded, with almost all of the main characters going separate ways, and leaving the station. Worf was specifically mentioned as the new ambassador to the Klingon homeworld. He mentions early in ''Nemesis'', during Riker's wedding, that he didn't like it. Worf, though more disciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on Deep Space Nine for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as chief tactical officer. It was brought up at times, even a full episode of Deep Space Nine saw him not feeling as comfortable as he did compared to his life on a starship. He did not even take quarters on the station for the first few months. By the time of ''Nemesis'' he was an extremely decorated officer and hero of the dominion war. He probably had enough clout to just ask for an assignment to the Enterprise-E, which the senior crew was only to happy to have him back, as he was part of their family for a long time.

to:

** Deep space nine concluded, with almost all of the main characters going separate ways, and leaving the station. Worf was specifically mentioned as the new ambassador to the Klingon homeworld.home world. He mentions early in ''Nemesis'', during Riker's wedding, that he didn't like it. Worf, though more disciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on Deep Space Nine for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as chief tactical officer. It was brought up at times, even a full episode of Deep Space Nine saw him not feeling as comfortable as he did compared to his life on a starship. He did not even take quarters on the station for the first few months. By the time of ''Nemesis'' he was an extremely decorated officer and hero of the dominion war. He probably had enough clout to just ask for an assignment to the Enterprise-E, which the senior crew was only to happy to have him back, as he was part of their family for a long time.
23rd Sep '17 6:47:29 PM thespecialneedsgroup
Is there an issue? Send a Message


*** Granted that it's counter intuitive, but canonical evidence strongly indicates that the ''Miranda''-class is significantly older than the ''Constellation''-class. The USS ''Reliant'', the first ''Miranda'' that we ever see on-screen, was operating as early as 2267, as evidenced by her registration number being seen a fleet status display in ''TOS'': "Court Martial." The oldest ''Constellation''-class ship that we've seen, the USS ''Hathaway'', was constructed almost two decades later in 2285, according to her dedication plaque. That just happens to be the same year that ''Reliant'' was attached to Project Genesis, meaning that we can't just write off the reference in "Court Martial" as a careless ContinuitySnarl. It confirms that ''Constellation''-class ships were still rolling off of the assembly line well into the ''Miranda''-class's service life. In fact, the ''Soyuz''-class's very existence seems to add credence that idea, because the ''Miranda'' and the ''Soyuz'' are quite obviously two variants of same basic space frame.

to:

*** Granted that it's counter intuitive, but canonical evidence strongly indicates that the ''Miranda''-class is significantly older than the ''Constellation''-class. The USS ''Reliant'', the first ''Miranda'' that we ever see on-screen, was operating as early as 2267, as evidenced by her registration number being seen on a fleet status display in ''TOS'': "Court Martial." The oldest ''Constellation''-class ship that we've seen, the USS ''Hathaway'', was constructed almost two decades later in 2285, according to her dedication plaque. That just happens to be the same year that ''Reliant'' was attached to Project Genesis, meaning that we can't just write off the reference in "Court Martial" as a careless ContinuitySnarl. It confirms that ''Constellation''-class ships were still rolling off of the assembly line well into the ''Miranda''-class's service life. In fact, the ''Soyuz''-class's very existence seems to add credence that idea, because the ''Miranda'' and the ''Soyuz'' are quite obviously two variants of same basic space frame.
23rd Sep '17 6:46:50 PM thespecialneedsgroup
Is there an issue? Send a Message


*** Granted that it's counter intuitive, but canonical evidence strongly indicates that the ''Miranda''-class is significantly older than the ''Constellation''-class. The USS ''Reliant'', the first ''Miranda'' that we ever see on-screen, was operating as early as 2267, as evidenced by her registration number being seen a fleet status display in ''TOS'': "Court Martial." The oldest ''Constellation''-class ship that we've seen, the USS ''Hathaway'', was constructed almost two decades later in 2285, according to her dedication plaque. That just happens to be the same year that ''Reliant'' was attached to Project Genesis, meaning that we can't just write off the reference in "Court Martial" as a careless ContinuitySnarl. It confirms that ''Constellation''-class ships were still rolling off of the assembly line well into the ''Miranda''-class's service life.

to:

*** Granted that it's counter intuitive, but canonical evidence strongly indicates that the ''Miranda''-class is significantly older than the ''Constellation''-class. The USS ''Reliant'', the first ''Miranda'' that we ever see on-screen, was operating as early as 2267, as evidenced by her registration number being seen a fleet status display in ''TOS'': "Court Martial." The oldest ''Constellation''-class ship that we've seen, the USS ''Hathaway'', was constructed almost two decades later in 2285, according to her dedication plaque. That just happens to be the same year that ''Reliant'' was attached to Project Genesis, meaning that we can't just write off the reference in "Court Martial" as a careless ContinuitySnarl. It confirms that ''Constellation''-class ships were still rolling off of the assembly line well into the ''Miranda''-class's service life. In fact, the ''Soyuz''-class's very existence seems to add credence that idea, because the ''Miranda'' and the ''Soyuz'' are quite obviously two variants of same basic space frame.
21st Sep '17 11:56:52 PM thespecialneedsgroup
Is there an issue? Send a Message

Added DiffLines:

*** Granted that it's counter intuitive, but canonical evidence strongly indicates that the ''Miranda''-class is significantly older than the ''Constellation''-class. The USS ''Reliant'', the first ''Miranda'' that we ever see on-screen, was operating as early as 2267, as evidenced by her registration number being seen a fleet status display in ''TOS'': "Court Martial." The oldest ''Constellation''-class ship that we've seen, the USS ''Hathaway'', was constructed almost two decades later in 2285, according to her dedication plaque. That just happens to be the same year that ''Reliant'' was attached to Project Genesis, meaning that we can't just write off the reference in "Court Martial" as a careless ContinuitySnarl. It confirms that ''Constellation''-class ships were still rolling off of the assembly line well into the ''Miranda''-class's service life.
21st Sep '17 4:25:52 PM thatsnumberwang
Is there an issue? Send a Message

Added DiffLines:

*** It is extremely unlikely that the Miranda class is of a similar age to the pre-refit Constitution class given how the entire line is going to be decommissioned in a few decades time even with retrofitting whereas the Miranda is still going strong by the late 24th century. And what is the only other ship class we know of that has lasted a similar length of time? The Excelsior, introduced as brand new but one film later (which in-universe is only a matter of days). It seems more probable given how we know both ships to be obsolete by the mid 24th that Kirk flew a Constellation-class similar to Picard's ''Stargazer'' or a Soyuz-class as seen in ''Cause and Effect.''
21st Sep '17 12:49:11 PM thespecialneedsgroup
Is there an issue? Send a Message

Added DiffLines:

**** It should be noted that ''Enterprise'' wasn't Kirk's first command. Scattered remarks throughout the series indicate that Kirk had a very brief stint commanding an unnamed starship prior to his taking command of ''Enterprise'' [[note]] Some ''Trek'' novels identify that vessel as the USS ''Aloia'', a ''Miranda''-class ship.[[/note]].
21st Sep '17 11:22:27 AM TTP
Is there an issue? Send a Message


** In ''Insurrection'' Worf is on board for the reception in the beginning of the movie. During which Picard is then called by the admiral to give him the update on Data. Picard says "We'll have Worf delay his return to DS9 for a bit". It is less about running Starship security, then it is Picard has worked with Worf for many years, and knows he is skilled, so he wanted another ace in the hole with him for the mission to Baku, a man who he could trust and rely on.
** Deep space nine concluded, with almost all of the main characters going separate ways, and leaving the station. Worf was specifically mentioned as the new ambassador to the Klingon homeworld. He mentions early in ''Nemesis'', during Riker's wedding, that he didn't like it. Worf, though more disciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on Deep Space Nine for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as cheif tactical officer. It was brought up at times, even a full episode of Deep Space Nine saw him not feeling as comfortable as he did compared to his life on a starship. He did not even take quarters on the station for the first few months. By the time of ''Nemesis'' he was an extremely decorated officer and hero of the dominion war. He probably had enough clout to just ask for an assignment to the Enterprise-E, which the senior crew was only to happy to have them back, as he was part of their family for a long time.

to:

** In ''Insurrection'' Worf is on board for the reception in the beginning of the movie. During which Picard is then called by the admiral to give him the update on Data. Picard says "We'll have Worf delay his return to DS9 Deep Space Nine for a bit". It is less about him running Starship security, then it is Picard has worked with Worf for many years, and knows he is skilled, so he wanted another ace in the hole with him for the mission to Baku, a man who he could trust and rely on.
** Deep space nine concluded, with almost all of the main characters going separate ways, and leaving the station. Worf was specifically mentioned as the new ambassador to the Klingon homeworld. He mentions early in ''Nemesis'', during Riker's wedding, that he didn't like it. Worf, though more disciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on Deep Space Nine for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as cheif chief tactical officer. It was brought up at times, even a full episode of Deep Space Nine saw him not feeling as comfortable as he did compared to his life on a starship. He did not even take quarters on the station for the first few months. By the time of ''Nemesis'' he was an extremely decorated officer and hero of the dominion war. He probably had enough clout to just ask for an assignment to the Enterprise-E, which the senior crew was only to happy to have them him back, as he was part of their family for a long time.
21st Sep '17 11:14:19 AM TTP
Is there an issue? Send a Message


** Deep space nine ended, with almost all of the main characters going separate ways. Worf was specifically mentioned as the new ambassador to the Klingon homeworld. He mentions early in "Nemesis", during Rikers wedding, that he didn't like it. Worf, though more diciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on DS9 for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as tactical officer. He mentioned a few times about how he did not feel quite as at home on DS9, not even taking quarters on the station for the first few months. He probably had enough clout to just ask to go to the Enterprise-E, which the crew was only to happy to have them back, as he was part of their family for a long time.

to:

** Deep space nine ended, concluded, with almost all of the main characters going separate ways.ways, and leaving the station. Worf was specifically mentioned as the new ambassador to the Klingon homeworld. He mentions early in "Nemesis", ''Nemesis'', during Rikers Riker's wedding, that he didn't like it. Worf, though more diciplined disciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on DS9 Deep Space Nine for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as cheif tactical officer. He mentioned It was brought up at times, even a few times about how full episode of Deep Space Nine saw him not feeling as comfortable as he did not feel quite as at home compared to his life on DS9, a starship. He did not even taking take quarters on the station for the first few months. By the time of ''Nemesis'' he was an extremely decorated officer and hero of the dominion war. He probably had enough clout to just ask to go for an assignment to the Enterprise-E, which the senior crew was only to happy to have them back, as he was part of their family for a long time.
21st Sep '17 8:43:04 AM TTP
Is there an issue? Send a Message

Added DiffLines:

** In ''Insurrection'' Worf is on board for the reception in the beginning of the movie. During which Picard is then called by the admiral to give him the update on Data. Picard says "We'll have Worf delay his return to DS9 for a bit". It is less about running Starship security, then it is Picard has worked with Worf for many years, and knows he is skilled, so he wanted another ace in the hole with him for the mission to Baku, a man who he could trust and rely on.
** Deep space nine ended, with almost all of the main characters going separate ways. Worf was specifically mentioned as the new ambassador to the Klingon homeworld. He mentions early in "Nemesis", during Rikers wedding, that he didn't like it. Worf, though more diciplined then the average Klingon because his duty demands it, still has the same irritability. This being said, if he was at a job he did not like, he would seek a new one out. To much had changed on DS9 for him to feel comfortable their. However, most of the Enterprise-E crew was inherited from its direct predecessor, the Enterprise-D where Worf served as tactical officer. He mentioned a few times about how he did not feel quite as at home on DS9, not even taking quarters on the station for the first few months. He probably had enough clout to just ask to go to the Enterprise-E, which the crew was only to happy to have them back, as he was part of their family for a long time.
15th Jul '17 10:50:24 AM nombretomado
Is there an issue? Send a Message


*** Both Khan Noonien Singh and Noonien Soong were named after a real person named Kim Noonien Singh, a pilot that Gene Roddenberry served with during WW2. Taken from Wikipedia: Khan's full name was based on that of Kim Noonien Singh, a pilot Gene Roddenberry served with during the Second World War. Roddenberry lost touch with his friend and had hoped that Khan's similar name might attract his attention and renew his old acquaintance.

to:

*** Both Khan Noonien Singh and Noonien Soong were named after a real person named Kim Noonien Singh, a pilot that Gene Roddenberry served with during WW2.UsefulNotes/WW2. Taken from Wikipedia: Khan's full name was based on that of Kim Noonien Singh, a pilot Gene Roddenberry served with during the Second World War. Roddenberry lost touch with his friend and had hoped that Khan's similar name might attract his attention and renew his old acquaintance.



*** Mind you, when Wolf 359 happened, the Alpha and Beta Quadrants were more or less at peace. Starships are probably ''expensive'', space socialist utopia or not, and that's a ''lot'' of people that could be occupying themselves with doing something useful instead of crowding the cosmos. Around the time when the Borg attacked, Starfleet would quite possibly have been more like a cross between the Coast Guard and NASA than the Pacific Fleet of WorldWarII. The Borg attacked, cleaned Starfleet's clocks, and along with the Romulans and Cardassians stirring up trouble in later seasons and leading into ''Deep Space Nine'', Starfleet has probably been on a huge expansion program until we see the massed fleets mixing it up on ''[[Series/StarTrekDeepSpaceNine Deep Space Nine]]''. But back at Wolf 359? We probably saw quite a bit of Starfleet's experienced cadre of officers get atomized and assimilated there.

to:

*** Mind you, when Wolf 359 happened, the Alpha and Beta Quadrants were more or less at peace. Starships are probably ''expensive'', space socialist utopia or not, and that's a ''lot'' of people that could be occupying themselves with doing something useful instead of crowding the cosmos. Around the time when the Borg attacked, Starfleet would quite possibly have been more like a cross between the Coast Guard and NASA than the Pacific Fleet of WorldWarII.UsefulNotes/WorldWarII. The Borg attacked, cleaned Starfleet's clocks, and along with the Romulans and Cardassians stirring up trouble in later seasons and leading into ''Deep Space Nine'', Starfleet has probably been on a huge expansion program until we see the massed fleets mixing it up on ''[[Series/StarTrekDeepSpaceNine Deep Space Nine]]''. But back at Wolf 359? We probably saw quite a bit of Starfleet's experienced cadre of officers get atomized and assimilated there.
This list shows the last 10 events of 195. Show all.
http://tvtropes.org/pmwiki/article_history.php?article=Headscratchers.StarTrekNemesis