Follow TV Tropes

Following

History Recap / StarTrekTheNextGenerationS5E18CauseAndEffect

Go To


Added DiffLines:

* GettingCrapPastTheRadar: Data's reference to the voices including "romantic encounters" reflects the greater reluctance of the franchise, at least until the Series/StarTrekDeepSpaceNine years, to use the word "sex" on screen.

Added DiffLines:

* TheTell: Crusher claims that Riker's left eyebrow raises slightly when he bluffs, but then says that she's just kidding.


[[quoteright:350:https://static.tvtropes.org/pmwiki/pub/images/tng_cause_and_effect_hd_380.jpg]]
[[caption-width-right:350:''"Do you have the feeling that you've done this before?"'']]



[[quoteright:350:https://static.tvtropes.org/pmwiki/pub/images/tng_cause_and_effect_hd_380.jpg]]
[[caption-width-right:350:''"Do you have the feeling that you've done this before?"'']]


->''"All hands abandon ship! Repeat, all hands abandon--"'' '''''[[KilledMidSentence (BOOM!)]]'''''
-->-'''Picard''', saying something viewers will get used to hearing a few times.

to:

->''"All hands abandon ship! Repeat, all hands abandon--"'' '''''[[KilledMidSentence (BOOM!)]]'''''
-->-'''Picard''',
[BOOM!] ]]'''''
-->--'''Picard''',
saying something viewers will get used to hearing a few times.



We begin this episode InMediasRes, with the ''Enterprise''[='=]s engines on fire and the ship out of control. The bridge crew is frantically trying to steady the ship long enough to launch the lifeboats as Picard orders all hands to abandon ship. And just as the audience is thinking "LikeYouWouldReallyDoIt", they [[GutPunch really do it]]: the ''Enterprise'' [[WhamShot vanishes in a huge]] [[ExplosionsInSpace space explosion]].

to:


We begin this episode InMediasRes, with the ''Enterprise''[='=]s engines on fire and the ship out of control. The bridge crew is frantically trying to steady the ship long enough to launch the lifeboats as Picard orders all hands to abandon ship. And just as the audience is thinking "LikeYouWouldReallyDoIt", thinking, "LikeYouWouldReallyDoIt," they [[GutPunch really do it]]: the ''Enterprise'' [[WhamShot vanishes in a huge]] [[ExplosionsInSpace space explosion]].



Act I seems to be a HowWeGotHere, as we're re-introduced to the ''Enterprise'' entering an unexplored sector. We first look in on Riker, Data, Worf and Crusher engaging in their regular poker game. After much banter (and a win for Crusher, who calls Riker's bluff), Crusher is called to sickbay to help La Forge deal with a major dizzy spell — but she experiences a bit of ''[[Main/DejaVu déjà vu]]'' whilst treating him. Later that night, in her quarters, Crusher hears what seem to be a mass of disembodied voices and, in switching on the light, breaks a glass she'd left on the night stand.

Crusher reports her experiences to the rest of the senior staff, but is interrupted when sensors detect a NegativeSpaceWedgie nearby. As the bridge crew attempt to deal with the situation, the ship begins losing power and is unable to move — just as a starship emerges from the Space Wedgie on a direct collision course. With no power to the engines, Riker (standing at Data's side for no apparent reason) suggests decompressing the main shuttlebay to provide the necessary thrust to get out of the way, while Data counter-suggests using the tractor beam to push the other ship aside. Picard goes with Data's plan, which is not entirely successful; the other ship is deflected, but not by enough, and smashes the ''Enterprise''[='=]s warp nacelle. This quickly causes a series of catastrophes and the events of the teaser play out before us again and the ''Enterprise'' is destroyed.

Act II re-re-introduces us to the ''Enterprise'' entering an unexplored sector; it's at this point that savvy viewers will recognize the GroundhogDayLoop at play. Again we visit Riker, Data, Worf and Crusher playing poker, with much familiar banter. Crusher is about to win when Riker folds, realizing that she is going to call his bluff. Crusher is called to sickbay to help [=LaForge=] deal with a major dizzy spell — and again experiences ''déjà vu''; only this time, La Forge feels it as well. Later that night Crusher again hears voices in her quarters and quickly calls the captain — breaking that glass once again.

to:

Act I seems to be a HowWeGotHere, as we're re-introduced to the ''Enterprise'' entering an unexplored sector. We first look in on Riker, Data, Worf and Crusher engaging in their regular poker game. After much banter (and a win for Crusher, who calls Riker's bluff), Crusher is called to sickbay to help La Forge deal with a major dizzy spell — but spell--but she experiences a bit of ''[[Main/DejaVu déjà vu]]'' DejaVu whilst treating him. Later that night, in her quarters, Crusher hears what seem to be a mass of disembodied voices and, in switching on the light, breaks a glass she'd left on the night stand.

Crusher reports her experiences to the rest of the senior staff, but is interrupted when sensors detect a NegativeSpaceWedgie nearby. As the bridge crew attempt to deal with the situation, the ship begins losing power and is unable to move — just move--just as a starship emerges from the Space Wedgie on a direct collision course. With no power to the engines, Riker (standing at Data's side for no apparent reason) suggests decompressing the main shuttlebay to provide the necessary thrust to get out of the way, while Data counter-suggests using the tractor beam to push the other ship aside. Picard goes with Data's plan, which is not entirely successful; successful: the other ship is deflected, but not by enough, and smashes the ''Enterprise''[='=]s warp nacelle. This quickly causes a series of catastrophes and catastrophes, the events of the teaser play out before us again again, and the ''Enterprise'' is destroyed.

Act II re-re-introduces us to the ''Enterprise'' entering an unexplored sector; it's at this point that savvy viewers will recognize the GroundhogDayLoop at play. Again we visit Riker, Data, Worf and Crusher playing poker, with much familiar banter. Crusher is about to win when Riker folds, realizing that she is going to call his bluff. Crusher is called to sickbay to help [=LaForge=] La Forge deal with a major dizzy spell — spell, and again experiences ''déjà vu''; only vu''--only this time, La Forge feels it as well. Later that night Crusher again hears voices in her quarters and quickly calls the captain — breaking captain--breaking that glass once again.



Act III. The ''Enterprise'' enters an unexplored sector. By this time, even the characters are starting to catch on, after a fashion; at their poker game, Worf recognizes their banter; and then he, Riker and Crusher correctly call out the hand Data is dealing even before he deals it.

-->'''Data:''' "[[{{Understatement}} This is highly improbable.]]"

to:

Act III. The ''Enterprise'' enters an unexplored sector. By this time, even the characters are starting to catch on, after a fashion; at their poker game, Worf recognizes their banter; banter, and then he, Riker and Crusher correctly call out the hand Data is dealing even before he deals it.

-->'''Data:''' "[[{{Understatement}} ->'''Data:''' [[{{Understatement}} This is highly improbable.]]"
]]



The next morning, Crusher and La Forge fill the others in on what they think is going on: a NegativeSpaceWedgie is going to entrap the ''Enterprise'' in a GroundhogDayLoop. They listen to parts of the recording which suggest the severity of the encounter's outcome, while trying to think of a way out. The problem is (unlike most instances of this trope) that if/when the Loop "loops", they all lose their memories of the previous loop, except for feelings of ''déjà vu''. La Forge suggests rewiring Data's AppliedPhlebotinum to mirror the previously established TechnoBabble so that, if/when the Loop "loops", he can send a message into the next loop — albeit an extremely short one, one word at most, which will show up only as a sort of post-hypnotic suggestion so Data won't know initially what it means. The plan is carried out, and no one feels like they've tried this before, which is a good sign. RedAlert! NegativeSpaceWedgie! Ship on collision course! The tractor beam doesn't work! ''Enterprise'' explodes! Only this time Data manages to activate the TechnoBabble message at the last second.

Back in that unexplored sector, back to the poker game. Worf experiences ''[[PardonMyKlingon nIb'poH]]'', and Crusher attempts to predict the hand that Data is about to deal. Instead, he deals all 3s; then, three of a kind to each. Crusher is called to sickbay to help La Forge deal with a dizzy spell; she inspects his VISOR on a hunch and finds that it is being affected by TechnoBabble. In Engineering, Data runs a diagnostic on ship's systems, and the results come up all 3s. They get a call from Crusher, telling them she's just recorded a mass of disembodied voices in her quarters — [[BrickJoke and they hear a glass shatter]].

to:

The next morning, Crusher and La Forge fill the others in on what they think is going on: a NegativeSpaceWedgie is going to entrap the ''Enterprise'' in a GroundhogDayLoop. They listen to parts of the recording which suggest the severity of the encounter's outcome, while trying to think of a way out. The problem is (unlike most instances of this trope) that if/when the Loop "loops", "loops," they all lose their memories of the previous loop, except for feelings of ''déjà vu''. La Forge suggests rewiring Data's AppliedPhlebotinum to mirror the previously established TechnoBabble so that, if/when the Loop "loops", "loops," he can send a message into the next loop — albeit loop--albeit an extremely short one, one word at most, which will show up only as a sort of post-hypnotic suggestion so Data won't know initially what it means. The plan is carried out, and no one feels like they've tried this before, which is a good sign. RedAlert! NegativeSpaceWedgie! Ship on collision course! The tractor beam doesn't work! ''Enterprise'' explodes! Only this time Data manages to activate the TechnoBabble message at the last second.

Back in that unexplored sector, back to the poker game. Worf experiences ''[[PardonMyKlingon nIb'poH]]'', and Crusher attempts to predict the hand that Data is about to deal. Instead, he deals all 3s; then, 3s, then three of a kind to each. Crusher is called to sickbay to help La Forge deal with a dizzy spell; she inspects his VISOR on a hunch and finds that it is being affected by TechnoBabble. In Engineering, Data runs a diagnostic on ship's systems, and the results come up all 3s. They get a call from Crusher, telling them she's just recorded a mass of disembodied voices in her quarters — [[BrickJoke quarters--[[BrickJoke and they hear a glass shatter]].



As before, the ship is without power and unable to move as another ship emerges from the Wedgie. Riker (standing at Data's side for no apparent reason) suggests decompressing the shuttlebay but Data counter-suggests using the tractor beam to push the other ship clear. Picard sides with Data, but Data suddenly has a EurekaMoment and goes with Riker's plan instead; the main shuttlebay decompresses, pushing the ''Enterprise'' clear and allowing the other ship to pass safely. The NegativeSpaceWedgie vanishes, power is restored and the ''Enterprise'' crew greet the crew of the U.S.S. ''Bozeman'' (commanded by none other than Captain [[Series/{{Frasier}} Frasier]] [[Series/{{Cheers}} Crane]]), which was either stuck in the Loop for some 90 years or got teleported by the rift 90 years into the future. Data explains his EurekaMoment: glancing at Riker, Data noted the number of rank pins on his collar (3) and deduced that the various phantom 3s referred to Riker, indicating that Riker's plan would be the successful one. Good thing he didn't think it referred to himself, since he is 3rd in command of the ship behind Riker and Picard.

!!Tropes featured:

to:

As before, the ship is without power and unable to move as another ship emerges from the Wedgie. Riker (standing at Data's side for no apparent reason) suggests decompressing the shuttlebay shuttlebay, but Data counter-suggests using the tractor beam to push the other ship clear. Picard sides with Data, but Data suddenly has a EurekaMoment and goes with Riker's plan instead; the main shuttlebay decompresses, pushing the ''Enterprise'' clear and allowing the other ship to pass safely. The NegativeSpaceWedgie vanishes, power is restored restored, and the ''Enterprise'' crew greet the crew of the U.S.S. USS ''Bozeman'' (commanded by none other than Captain [[Series/{{Frasier}} Frasier]] Series/{{Frasier}} [[Series/{{Cheers}} Crane]]), which was either stuck in the Loop for some 90 years or got teleported by the rift 90 years into the future. Data explains his EurekaMoment: glancing at Riker, Data noted the number of rank pins on his collar (3) and deduced that the various phantom 3s referred to Riker, indicating that Riker's plan would be the successful one. Good thing he didn't think it referred to himself, since he is 3rd in command of the ship behind Riker and Picard.

Picard.
----
!!Tropes featured:
featured in this episode include:



* BottleEpisode: Sets on the Enterprise are all reused sets, the ''Bozeman'' is a retooling of the USS ''Reliant'' from ''Film/StarTrekIITheWrathOfKhan'', and Bozeman's interior is from the recently produced ''Film/StarTrekVITheUndiscoveredCountry''. Creator/KelseyGrammer's guest appearance is the only aspect that deviates from this trope.
* BrickJoke: At the start of each time loop, Riker wonders aloud if Data is using his high-speed shuffling ability to stack the deck. In the final loop, that's exactly what Data does (albeit subconsciously).
* CallBack: ''[[Recap/StarTrekTheNextGenerationS3E15YesterdaysEnterprise Yesterday's Enterprise]]''. That episode featured a Federation ship from the past stumbling through a time rift as well.

to:

* BottleEpisode: Sets on the Enterprise ''Enterprise'' are all reused sets, the ''Bozeman'' is a retooling of the USS ''Reliant'' from ''Film/StarTrekIITheWrathOfKhan'', and Bozeman's the ''Bozeman'''s interior is from the recently produced ''Film/StarTrekVITheUndiscoveredCountry''. Creator/KelseyGrammer's guest appearance is the only aspect that deviates from this trope.
* BrickJoke: BrickJoke:
**
At the start of each time loop, Riker wonders aloud if Data is using his high-speed shuffling ability to stack the deck. In the final loop, that's exactly what Data does (albeit subconsciously).
** Despite her best efforts, Crusher manages to break her wineglass in every iteration of the loop. The final time, we don't even see it, but La Forge and Data hear it shatter over the comm.
* CallBack: ''[[Recap/StarTrekTheNextGenerationS3E15YesterdaysEnterprise "[[Recap/StarTrekTheNextGenerationS3E15YesterdaysEnterprise Yesterday's Enterprise]]''. That episode Enterprise]]" featured a Federation ship from the past stumbling through a time rift as well.



* DejaVu: The crew are caught in a GroundhogDayLoop, Doctor Crusher begins to experience ''déjà vu'' and so do the other crew members when she brings up the issue.

to:

* DejaVu: The crew are caught in a GroundhogDayLoop, Doctor Crusher begins to experience ''déjà vu'' vu'', and so do the other crew members when she brings up the issue.issue. In subsequent loops, this progesses to predicting events before they happen.



* FateWorseThanDeath: It is heavily implied that the ''Bozeman'' crew have relived their own loop for the better part of a century.

to:

* FateWorseThanDeath: It is heavily implied that the ''Bozeman'' crew have relived their own loop for the better part of a century. century--though unlike the ''Enterprise'' crew, whether they are at all aware of it is left unclear.



* [[FlingALightIntoTheFuture Fling a Light Into the Next Temporal Loop]]: How they end up saving the ''Enterprise''.

to:

* [[FlingALightIntoTheFuture Fling a Light Into the Next Temporal Loop]]: FlingALightIntoTheFuture: How they end up saving the ''Enterprise''.''Enterprise''; La Forge comes up with a way for Data to send a brief message to himself in the next loop.



* HearingVoices: Caused by timelines bleeding over.

to:

* HearingVoices: Caused by timelines bleeding over. It's not only mental, either; Crusher manages to make a recording of the voices for Data to analyze.



** Each loop takes roughly a day, and they find out at the end they're out of sync by seventeen days. So the episode opening destruction is roughly the twelfth time it was destroyed.

to:

** Each loop takes roughly a day, and they find out at the end they're out of sync by seventeen days. So the episode opening episode-opening destruction is roughly the twelfth time it was destroyed.



* RippleEffectProofMemory: Downplayed. Crew members do not entirely remember previous loops, but do experience ''déjà vu'' moments, which grow in intensity with each new iteration. [[Literature/StarTrekDepartmentOfTemporalInvestigations One of the]] ExpandedUniverse novels also mentions that the ''Bozeman'' crew experienced the same effect, but didn't have the knowledge to break themselves free like the ''Enterprise'' did, resulting in [[FateWorseThanDeath 90 years of feeling trapped in a perpetual cycle of death]].

to:

* RippleEffectProofMemory: RippleEffectProofMemory:
**
Downplayed. Crew members do not entirely remember previous loops, but do experience ''déjà vu'' DejaVu moments, which grow in intensity with each new iteration. iteration.
**
[[Literature/StarTrekDepartmentOfTemporalInvestigations One of the]] ExpandedUniverse novels also mentions that the ''Bozeman'' crew experienced the same effect, but didn't have the knowledge to break themselves free like the ''Enterprise'' did, resulting in [[FateWorseThanDeath 90 years of feeling trapped in a perpetual cycle of death]].



* TooMuchInformation: When Data is summarizing his analysis of the "overlapping voices" phenomenon that Dr. Crusher recorded, Picard cuts Data off when he ends up listing the number of couples who he determined were engaged in "[[CoitusUninterruptus romantic encounters]]".

to:

* TooMuchInformation: When Data is summarizing his analysis of the "overlapping voices" phenomenon that Dr. Crusher recorded, Picard cuts Data off when he ends up proceeds to listing the number of couples who he determined were engaged in "[[CoitusUninterruptus romantic encounters]]".



* WhamShot: The ''Enterprise-D'' going kablooey in space in the cold open.
* WhatYearIsThis: Inverted. Picard asks Bateson what year he thinks he's in, with Bateson assuming it's still 2278. The ''Enterprise'' crew also has concerns about this for themselves, but are relieved that it hasn't been anywhere near that long for them when they ring up a timebase reading.

to:

* WhamShot: The ''Enterprise-D'' ''Enterprise''-D going kablooey in space in the cold open.
* WhatYearIsThis: Inverted. Picard asks Captain Bateson what year he thinks he's in, with Bateson assuming it's still 2278. The ''Enterprise'' crew also has concerns about this for themselves, but are relieved that it hasn't been anywhere near that long for them (only about 17 days) when they ring up a timebase reading.

Added DiffLines:

* WarmMilkHelpsYouSleep: Picard's Aunt Adele has a recipe for steamed milk which he shares with Crusher.


* CallBack: ''[[Recap/StarTrekTheNextGenerationS3E15YesterdaysEnterprise Yesterday's Enterprise]]''. That episode featured a Federation shipship from the past stumbling through a time rift as well.

to:

* CallBack: ''[[Recap/StarTrekTheNextGenerationS3E15YesterdaysEnterprise Yesterday's Enterprise]]''. That episode featured a Federation shipship ship from the past stumbling through a time rift as well.

Added DiffLines:

* GivenNameReveal: Nurse Alyssa's last name was finally revealed in this episode: Ogawa.


->''"All hands abandon ship! All hands abandon--"'' '''''[[KilledMidSentence (BOOM!)]]'''''

to:

->''"All hands abandon ship! All Repeat, all hands abandon--"'' '''''[[KilledMidSentence (BOOM!)]]'''''


->''"All hands abandon ship! All hands abandon--" '''''[[KilledMidSentence (BOOM!)]]'''''

to:

->''"All hands abandon ship! All hands abandon--" abandon--"'' '''''[[KilledMidSentence (BOOM!)]]'''''

Added DiffLines:

->''"All hands abandon ship! All hands abandon--" '''''[[KilledMidSentence (BOOM!)]]'''''
-->-'''Picard''', saying something viewers will get used to hearing a few times.

Added DiffLines:

* ChekhovsSkill: In [[Recap/StarTrekTheNextGenerationS5E9AMatterOfTime "A Matter of Time,"]] Data explained that he was capable of listening to and distinguishing over 150 musical works at the same time. Here, he uses the same skill to sort through the jumble of voices from the previous time loops.


* StableTimeLoop: When Riker suggests that reversing course could be the cause of the ship's destruction, he is implying, whether he realizes it or not, that this trope is in effect. The irony is that [[AvertedTrope it isn't]], and had the crew not been overthinking the situation in this way, they might have broken free after the first loop.[[note]]Though it's also possible that the spacial rift was drawn to the ''Enterprise's'' position, not a static point in space, in which case it would make no difference.[[/note]]

to:

* StableTimeLoop: When Riker suggests that reversing course could be the cause of the ship's destruction, he is implying, whether he realizes it or not, that this trope is in effect. The irony is that [[AvertedTrope it isn't]], and had the crew not been overthinking the situation in this way, they might have broken free after the first loop.[[note]]Though it's also possible that the spacial space-time rift was drawn to the ''Enterprise's'' position, not a static point in space, in which case it would make no difference.[[/note]]



* TooMuchInformation: When Data is summarizing his analysis of the "overlapping voices" phenomenon that Dr. Crusher recorded, Picard cuts Data off when he ends up listing the number of couples which he determined were engaged in "[[CoitusUninterruptus intimate encounters]]".

to:

* TooMuchInformation: When Data is summarizing his analysis of the "overlapping voices" phenomenon that Dr. Crusher recorded, Picard cuts Data off when he ends up listing the number of couples which who he determined were engaged in "[[CoitusUninterruptus intimate romantic encounters]]".



* YouCantFightFate: Dr Crusher very deliberately tries to avoid breaking her glass in the next loop but just ends up breaking it another way. It achieves BrickJoke status when Geordi contacts her on the com, and in the background you hear a glass breaking.

to:

* YouCantFightFate: Dr Crusher very deliberately tries to avoid breaking her glass in the next loop but just ends up breaking it another way. It achieves BrickJoke status when Geordi contacts her on the com, intercom, and in the background you hear a glass breaking.


* BottleEpisode: Sets on the Enterprise are all reused sets, the Bozeman's exterior is directly from ''Film/StarTrekIITheWrathOfKhan'', and Bozeman's interior is from the recently produced ''Film/StarTrekVITheUndiscoveredCountry''. Creator/KelseyGrammer's guest appearance is the only aspect that deviates from this trope.

to:

* BottleEpisode: Sets on the Enterprise are all reused sets, the Bozeman's exterior ''Bozeman'' is directly a retooling of the USS ''Reliant'' from ''Film/StarTrekIITheWrathOfKhan'', and Bozeman's interior is from the recently produced ''Film/StarTrekVITheUndiscoveredCountry''. Creator/KelseyGrammer's guest appearance is the only aspect that deviates from this trope.

Added DiffLines:

* TooMuchInformation: When Data is summarizing his analysis of the "overlapping voices" phenomenon that Dr. Crusher recorded, Picard cuts Data off when he ends up listing the number of couples which he determined were engaged in "[[CoitusUninterruptus intimate encounters]]".

Added DiffLines:

* BottleEpisode: Sets on the Enterprise are all reused sets, the Bozeman's exterior is directly from ''Film/StarTrekIITheWrathOfKhan'', and Bozeman's interior is from the recently produced ''Film/StarTrekVITheUndiscoveredCountry''. Creator/KelseyGrammer's guest appearance is the only aspect that deviates from this trope.

Showing 15 edit(s) of 79

Top

How well does it match the trope?

Example of:

/

Media sources:

/

Report