• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Spoilers Star Trek: Prodigy 1x19 - "Supernova, Part 1"

Rate the episode...


  • Total voters
    77
It may not even be the animation teams fault. Perhaps the holodeck got the Sovereign class registrations wrong? If this is *not* all in a holodeck, then we could even be seeing a multitude of multiverse Enterprise E’s which are being brought together by the Living Construct like in the TNG episode Parallels? Perhaps the Living Construct acts across inter-dimensional realms and draws it’s prey in through time and space once it has locked on to and infected a ‘source’ ship? :shrug:
 
Last edited:
Much like an effective biological virus, if you kill the host too quickly you limit your potential to spread. If it blows up every ship it infects immediately then those ships don't have the opportunity to spread the virus to other ships.
I'm not sure the virus is spread though, more like every ship is getting affected directly from the living construct. It seemed to steer the actions of each ship separately, like ordering the weapons to fire.

The point of doing things slowly may be that the Construct is actually overwhelmed by having to control so many ships at once, and because it also wants ships to keep sending distress signals (which presumably would stop if they all got core breaches).
 
I'm not sure the virus is spread though, more like every ship is getting affected directly from the living construct. It seemed to steer the actions of each ship separately, like ordering the weapons to fire.

The point of doing things slowly may be that the Construct is actually overwhelmed by having to control so many ships at once, and because it also wants ships to keep sending distress signals (which presumably would stop if they all got core breaches).

This implies that the Living Construct is not a virus, but a remote control ‘Wannacry’ ransomeware type weapon operated remotely. If the Living Construct is ‘remote controlling’ the starships and not actually infecting them, then surely flying the Protostar in to a sun (not near Romulus or other life etc. incase it causes a nova) or auto destructing the ship would be the only solution? We do not know if once the starships are infected that they would not still be infected by the weapon, even if the Living Construct itself is neutralised. I think that the main question in this case would be does the virus which has taken over the weapons systems self replicate and act independently of the Living Construct once ‘activated’, or is the weapon dependent on a connection to the Living Construct to ‘work’. :shrug:

Also, why did Gwen not send out a distress signal warning non Starfleet ships to warn Starfleet ships to stay away rather than encouraging more ships to come and join in the mosh pit? Obviously the Protostar still had communications channels, The Captain of the Vulcan or Ferengi ship could have sent out a message warning Starfleet to stay away from the Protostar and explain what was going on.

“Computer, end program!” :brickwall:
 
Last edited:
Good catch. Still wish they would have made something newer-looking.
I think that this new design emphasises the scale of this version of the Klingon Bird of Prey a bit better. If you look at the ships bulbous command head module, there are now many windows for Klingons to look out of. They may even have a window on the bridge. Older model Klingon ships of this style did not have as visible windows, or any at all, often making earlier models of ship seem similar in size to a small scout ship or shuttle craft - this Bird of Prey is obviously much larger and formidable. This could be a similar model Bird of Prey to the version that destroyed the Enterprise D in Generations? :shrug:

https://twitter.com/gaghyogi49/status/1606719354913099780?s=46&t=m-OlUoo0DdkabnsZ24o2LQ
 
I think that this new design emphasises the scale of this version of the Klingon Bird of Prey a bit better. If you look at the ships bulbous command head module, there are now many windows for Klingons to look out of. They may even have a window on the bridge. Older model Klingon ships of this style did not have as visible windows, or any at all, often making earlier models of ship seem similar in size to a small scout ship or shuttle craft - this Bird of Prey is obviously much larger and formidable. This could be a similar model Bird of Prey to the version that destroyed the Enterprise D in Generations? :shrug:

https://twitter.com/gaghyogi49/status/1606719354913099780?s=46&t=m-OlUoo0DdkabnsZ24o2LQ
Scaling the same ship design doesn't actually work (in real life), so it isn't good practice to do it in a fictional universe (it's merely a shortcut because there is no budget or no imagination for an entirely new shape of vessel):

It's explained perfectly on the Ex-astris-scientia site:
https://www.ex-astris-scientia.org/articles/scaling.htm

See also http://www.ditl.org/pagarticle.php?ArticleID=22&ListID=Articles
 
Last edited:
And that’s my point: there’s no budget consideration now between making a brand-new CGI ship of a new design and making a brand-new CGI ship of an older design.
 
Or likely they are right, and the registy number on the ncalle was set up for that shot (which is the only one where the nacelle registry is clearly visable to the normal viewer in the course of the episode), and they just saved on FX time and budget by using the same model for the uss soverign close up by putting that name and registry on the model as well.. then reusing that exact same model for all the background ships as well.

The fact that the nacelle egistry was shot in such a way to be clearly visable in that one scene, suggests they they wanted people to see that registry. The same for the soverign in its close up scene.
 
I’m only going to believe the Enterprise-E was in that scene if they mention it in dialogue. Otherwise it’s no different from TNG reusing the Hood footage from Encounter at Farpoint to represent other ships. If the USS Sovereign can be both at the initial battle AND be one of the reinforcement ships to arrive later, then that’s pretty conclusive evidence that we’re not supposed to take the markings on the hull seriously, or at best, it’s up to an individual viewer’s opinion as to what those ships were.
 
Using the wrong ship name and registry is nothing new in Star Trek. Both Defiant class ships sent to retake the Prometheus in VOY Message in a Bottle have "USS Defiant NX-74205" written on their hulls.

Mind you, since the officers who beam aboard the Prometheus bridge were regular background extras on DS9, maybe one of those ships really was the Defiant?
 
read the whole article
It's speculation based on a selective interpretation of a Matalas tweet regarding the Enterprise F from a few weeks ago. Basically, there's nothing there that conclusively confirms that the Enterprise E was definitely in that fleet.
 
It's speculation based on a selective interpretation of a Matalas tweet regarding the Enterprise F from a few weeks ago. Basically, there's nothing there that conclusively confirms that the Enterprise E was definitely in that fleet.
Maybe they can clarify in the finale, but I like to think that it was - even if it was only a holo Enterprise E.:shrug:
 
Good thing Starfleet have rubbish WiFi or the whole Federation would be doomed already.
I'm actually kind of confused as to how this whole "once you hail a ship, they're infected" thing works. The ships are responding to an SOS from the fleet, but don't actually get infected until they arrive. Shouldn't receiving an SOS from an infected ship infect the receiving ship? Therefore negating the need to arrive at the scene of the battle.

But even if it does for some reason require the ships to actually show up at the fleet to get infected, doesn't Starfleet have a system in place to prevent the entire fleet from going to a trap just because there's an SOS?
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top