star trek generations – Trekking with Dennis

What If…? Star Trek Edition!

A Star Trek-themed spoiler warning graphic.

Spoiler Warning: Beware of spoilers for the following Star Trek productions: The Next Generation Season 1, Deep Space Nine Season 6, Voyager Season 1, Generations, Star Trek ’09, Discovery Season 2, and Picard Season 2.

Almost four years ago I had a lot of fun writing a piece here on the website called “What If…? Star Trek Edition!” I took the basic concept behind the then-new Marvel miniseries What If…? and applied it to several storylines from the Star Trek franchise that I found interesting. Speculating and getting creative was a blast, so… let’s do it again!

If you missed the miniseries (or my earlier post), I’ll briefly explain how this works! We’re going to look at five stories from across the Star Trek franchise and ask a simple question: what if things went differently? What would the consequences be for Starfleet, the Federation, and some of the characters we’ve come to know and love if, for example, Spock wasn’t resurrected on the Genesis Planet or Captain Janeway and the USS Voyager tried to reach the Gamma Quadrant terminus of the Bajoran wormhole? I covered both of those topics in my post from 2021, by the way, so be sure to check it out – you can find it by clicking or tapping here.

Still frame from Star Trek: Voyager showing Kim and Quark. — Harry Kim and Quark.

Alternate history has been an interest of mine for a long time – so we can consider this an “alternate history of the future,” if you like! With the Star Trek franchise slowly but surely heading toward the 1,000-story mark, there are a lot of places where narratives could branch, and where the Star Trek galaxy could end up in very different situations! As a Trekkie, and as someone who likes to spend time in this setting, it’s a ton of fun to come up with these ideas and consider how they might play out.

As always, a couple of important caveats! All of this is the entirely subjective take of one old Trekkie. If you hate all of my ideas, think I’ve got the wrong end of the stick, or if I miss something that seems totally obvious to you… that’s okay! There ought to be enough room in the Star Trek fan community for differences of opinion. None of this is close to being “canon,” anyway, so there’s even less of a reason to get upset about completely made-up Star Trek stories that will never be seen on screen!

Alright, let’s jump into the “what if” scenarios!

What If…? #1:
What if… Captain Picard and Q never met?
The Next Generation, Picard Season 2

Still frame from Star Trek: The Next Generation Season 1 showing Picard meeting Q for the first time. — Picard’s first encounter with Q.

This is a really interesting one – and it might not go the way you think! Looking back over Picard’s run-ins with Q during The Next Generation, there really aren’t many places where we could say that their interactions had wide-ranging consequences. I have my pet theory that Q deliberately saved Picard and the Federation by making them aware of the Borg threat (click or tap here for that one, it’s one of my favourite Star Trek theories!) but that’s not the angle I’m gonna take today. In this case, we’re going to say that – for whatever reason – Picard and Q never met, never developed their complex relationship, and Q never set any puzzles for Picard to solve. In fact, Q stayed away from humanity and Starfleet altogether in this alternate timeline.

As noted, Q’s interactions with Picard and the crew of the Enterprise-D almost always involved problems or scenarios of his own devising. So without Q on the scene, the Enterprise-D’s mission actually proceeds slightly more smoothly than it did in the series; the absence of Q doesn’t matter in a big way to the seven-year cruise. Every other episode and story plays out more or less the same, from the mystery at Farpoint Station to the ship’s destruction over Veridian III. Picard assumes command of the Enterprise-E, then the Romulan rescue armada, before retiring from Starfleet.

Still frame from Star Trek: The Next Generation showing the Enterprise-D in orbit of a green planet. — The voyages of the starship Enterprise would proceed in exactly the same way… just without Q’s occasional shenanigans!

But here’s where things change. After the mission to rescue Soji and being named Chancellor of Starfleet Academy, Admiral Picard is aboard the USS Stargazer when a mysterious anomaly is detected. The Stargazer, the Excelsior, and a handful of other ships race to the scene, where they’re confronted by a massive subspace anomaly that Seven of Nine thinks could be a huge transwarp conduit. Attempts at communication fail, and with only a handful of Starfleet ships on the scene, there’s no way to prevent the conduit from unleashing its triquantum waves.

Aboard the Stargazer, Picard and the crew look desperately for solutions – but there are none. Without the Borg, their vessel, and their knowledge of the situation, there’s no way to stop the transwarp conduit from doing what it was designed to do: launching a massive attack on the Federation. Its triquantum waves blast across several sectors of space, destroying the Starfleet ships as they attempt to escape, as well as several starbases and Federation colonies. Having expended its initial wave of energy, the conduit then falls eerily silent, as if waiting for instructions… or for its operators to emerge.

Still frame from Star Trek: Picard showing the mysterious transwarp anomaly. — This time, there’s no one to stop the transwarp anomaly…

Because Star Trek: Picard was a jumbled mess of a show, we don’t know who made the transwarp anomaly. My pet theory is that it’s something to do with Season 1’s super-synths, but it could also be the Borg, the Dominion, or any one of a number of Star Trek baddies! In this timeline, though, the anomaly’s initial attack would be successful – because there’d be no Q to throw Picard and his friends into the alternate reality that eventually led to Dr Jurati’s assimilation and the creation of a Borg splinter group. Without the Jurati-Borg’s presence at the site of the transwarp anomaly, there was no way to stop its energy from being unleashed.

What would happen next? I’d imagine that whoever made the anomaly would be pleased with its success, and if it was a transwarp conduit – as Seven theorised – then it could serve as a gateway for any ships that the attacker had. With a devastated sector and no intact ships remaining in the area, any invader would quickly be able to establish a massive bridgehead right in the heart of Federation territory, and if they have more transwarp conduit weapons… who knows? The next target could be Earth.

What If…? #2:
What if… Section 31 and the Federation accidentally created the Borg?
Deep Space Nine, First Contact, Discovery Season 2

Concept art for Star Trek: The Next Generation showing three Borg designs. — Early concept art of the Borg.

If you’re a regular reader, you might remember my theory that Discovery’s second season – which featured a time-travelling spacesuit and an AI that could “assimilate” humans using nano-bots – was originally pitched as a “Borg origin story.” So what if that’s actually what happened? In this timeline, Section 31 and the Control AI are going to be uncovered as the true progenitors of the Borg!

Here’s how it went down: after chasing Captain Pike and the USS Discovery all over the quadrant, Control and its fleet of automated drone-ships finally have them cornered. Using the assimilated body of Captain Leland, Control boards Discovery and attempts to seize the all-important Sphere Data that it needs – but the battle in space is going poorly, and Control seems to be on the verge of defeat. Not wanting to give up, Control switches tactics. Instead of the Sphere Data, Control races to the science lab and steals the Red Angel suit that Burnham and the crew have finished working on.

Still frame from Star Trek: Discovery Season 2 showing Captain Leland holding a phaser. — The “assimilated” Captain Leland.

Staring down an armada of allied ships in space and Discovery’s security team just outside the doors, Control is trapped. With no other options, Control uses the Red Angel suit to escape – but because the suit is malfunctioning, Control ends up in the distant past. Trapped on a planet in the far-flung Delta Quadrant, anchored in time the same way Gabrielle Burnham was, Control surveys its surroundings. The planet is primitive, populated by humanoids in an early stage of development – with no spacefaring technology. Control has some nano-bots remaining, and the Red Angel suit… but that’s it. It decides that the best course of action is to assimilate some of the local humanoids and work on producing more technology – hoping to one day return to Federation space and finish what it started.

For me, the biggest question is this: does the Borg Collective still know all of this as of the late 24th Century? Or has the passage of time and countless assimilations over the millennia led to this information being forgotten, buried somewhere in the depths of the Collective’s knowledge? My personal take is that this is something the Borg Queen would know – but in the Collective’s run-ins with Starfleet, it’s gone out of its way to avoid revealing this truth.

Still frame from Star Trek: Discovery Season 2 showing the Red Angel suit opening a portal. — The Red Angel suit can be used to travel through time.

But the Borg Queen is clearly not the same as Control – so what happened there? Perhaps the Queen regards Control as her “ancestor,” in a sense, or maybe Control merged with a particularly strong personality that it assimilated early on. Dr Jurati, in Picard’s second season, merged with the Borg Queen rather than simply becoming a Borg drone, so the same principle could apply here. It does beg the question, though, as to why the Borg Collective didn’t set its sights on Earth and humanity decades earlier if Control’s desire for revenge is hard-coded into the Collective’s DNA!

More interestingly, I wonder what Starfleet would make of this revelation. Let’s say that, after the Battle of Sector 001, Starfleet was able to analyse the remains of the Borg Cube and found remnants of 23rd Century Federation programming in the Borg’s systems. Further analysis eventually led to one inescapable conclusion: the Control AI is the basis for the Borg, making the biggest threat to the galaxy an accidental Federation creation. Perhaps that knowledge could be used by Starfleet’s Borg experts to find a weakness or a way to communicate… but it would also be a serious blow to morale.

What If…? #3:
What if… the USS Voyager was destroyed over Ocampa?
Voyager Season 1

Still frame from Star Trek: Voyager showing the USS Voyager exploding. — The destruction of the USS Voyager!

In this alternate timeline, we’re going to say that the USS Voyager and the Val Jean – Chakotay’s ship – were both transported to the Delta Quadrant as we saw in Caretaker. But during the battle for the Caretaker’s Array, it’s Voyager, not the Val Jean, that ended up being destroyed by the Kazon. Some survivors made it to the escape pods and were taken aboard by the Maquis, with Chakotay ordering B’Elanna to fire up the engines and get the ship out of range of the Kazon as quickly as possible!

The first character we’d miss would be the Doctor – and with no surviving medical staff (and apparently no medically-trained Maquis, either) that would quickly become a problem for the crew of the Val Jean. I’m also going to suggest that Neelix and Kes wouldn’t be a part of this crew – or if they were involved, they’d remain aboard Neelix’s ship rather than try to cram aboard the already-overcrowded and cramped Maquis raider. As to what else would be different… well, it depends on who survived the destruction of Voyager.

Photograph of the original Maquis Raider model from Star Trek: Deep Space Nine and Star Trek: Voyager. — Chakotay’s Maquis raider – the Val Jean.

I’m going to assume that Captain Janeway went down with the ship – as she once told Naomi Wildman that it’s part of a captain’s duty. That was half-joking, perhaps, but I can’t see Janeway abandoning the ship while any members of the crew were still aboard, so I’m gonna say she was lost with Voyager. Among the survivors, though, would be Tuvok, Harry Kim, Tom Paris, and B’Elanna Torres, as well as Seska, Ensign Wildman, and engineer Carey. There’d likely be a clash between Tuvok and Chakotay over command decisions, but Chakotay would pull rank – figuratively speaking – and remind the Starfleet survivors that they’re aboard his ship, so he’s in charge. However, as a concession given the difficult situation, he’d offer senior roles to Tuvok and Carey, and Kim would take up a role on the bridge.

Living conditions would be difficult, though. Voyager was kind of inconsistent with this, but we got hints in several episodes that there might’ve been about twenty-five or so Maquis aboard Voyager. If we assume that there’d be at least forty survivors from Voyager’s original complement of 150, the Starfleet personnel would outnumber the Maquis – which could lead to a lot more tensions aboard a Maquis ship than it did aboard Voyager. The small raider – which probably wasn’t equipped for a long voyage – would struggle to accommodate so many people, and with fewer replicators (if they even worked at all) the ship would have to make many more stops to forage and hunt for food and supplies.

Still frame from Star Trek: Voyager showing a close-up of Chakotay in the series premiere. — Chakotay would remain in command of his Maquis vessel.

Equinox offers an excellent look at how a ship less well-equipped than Voyager might’ve handled being stranded in the Delta Quadrant. Despite the Val Jean’s personnel being arguably better prepared to survive than Captain Ransom’s crew, the limitations of the ship, the difficult living conditions, and the constant danger would all take a toll on the survivors. Morale would be low among the Starfleet personnel after Janeway’s death, and the reality of the situation would sink in for them over the first few days as they struggled to adapt. Having to share bunk beds and malfunctioning replicators would lower morale even further.

Chakotay would do his best to avoid the Kazon, and without the technologically-advanced Voyager to pursue, I daresay they’d be less interested in chasing the Val Jean, so the ship would make slow but steady progress toward the Alpha Quadrant. After several months (or perhaps a year) of planet-hopping, the Val Jean would encounter something strange: an old Earth automobile floating in space. This would lead them to a planet with a human settlement; the descendants of abductees from Earth. Most of the Starfleet personnel would disembark here, choosing to stay on the planet rather than remain aboard Chakotay’s ship. Chakotay and the Maquis would stay for a while, too, enjoying the friendly atmosphere and making repairs to their ship. After an extended stay, though, would anyone want to re-join the mission back to the Alpha Quadrant on a ship dangerously unsuited for such a voyage?

What If… #4:
What if… the Romulans figured out what Sisko and Garak did?
Deep Space Nine Season 6

Still frame from What We Left Behind: Looking Back At Deep Space Nine showing a sketch of Garak. — Garak.

Perhaps this one won’t always be a “what if!” One of my fantasy Star Trek episodes is a follow-up to the outstanding Deep Space Nine episode In The Pale Moonlight, and I’d really love to see a sequel of sorts one day. But for now we’re going to make up our own version – and connect it to other parts of Star Trek, too!

There are two time slots for this, and both are interesting – so this is kind of two “what ifs” in one!

Firstly, we have the obvious question: what if the Romulans figured out what happened before the end of the Dominion War?

Still frame from Star Trek: Deep Space Nine showing Senator Vreenak. — The Romulans have figured out that “it’s a faaaaaake!”

Shortly after the Breen joined the Cardassians and the Dominion, the Tal Shiar uncovers the truth behind the assassination of Senator Vreenak. How they figured it out doesn’t matter; all we need to know is that the proof is irrefutable. As a result, the Romulans terminate their alliance with the Federation and Klingons at the worst possible moment – just as Breen weapons are proving to be a tactical and technological hurdle for the allies to overcome. Worse, a few days later the Romulans announce a non-aggression pact with the Dominion, shortly followed up by an official alliance. In short, the Romulans have switched sides.

It’s no secret that the Romulans have long coveted Federation systems, and promises from the Dominion about ownership of Vulcan combined with a need for revenge swayed the Romulan senate. They began collaborating openly with the Dominion, sharing technology like cloaking devices with their new allies. The Cardassian rebellion led by Damar would be quickly crushed by the combined might of the Dominion, Breen, Romulans, and Cardassian collaborators, and would be far less effective and far-reaching. With the axis shored up and bolstered by Romulan troops and Romulan intelligence, they’d be back on the front foot ready to press home their advantage. The obvious first targets are Bajor and DS9; control of the wormhole would be vital. From there, it could be a very short war indeed…

Still frame from Star Trek: Deep Space Nine showing Garak and Sisko. — Garak and Captain Sisko.

The second scenario is the one I still hope to see on screen one day. In this timeline, the Romulans discover what happened – but only years after the war is over. The destruction of their homeworld took a toll, and the Romulan Empire is in a difficult position. Romulan leaders demand the extradition of those responsible, but with Sisko “missing in action” and apparently residing with the Prophets, there’s really no one to prosecute. Garak’s involvement remains unknown, and he wouldn’t stick his head above the parapet!

But the Romulans would make a fuss, doing whatever they could to make life difficult for Starfleet. One action the Romulan government takes is cutting off Federation researchers from a derelict Borg vessel that they control, and ordering all Romulans to leave Federation space. The result? Soji doesn’t head to the Artifact, Laris and Zhaban leave Earth, and the synths at Coppelius Station remain hidden from Starfleet. But not necessarily hidden from everyone…

What If…? #5:
What if… Captain Kirk didn’t die on Veridian III?
Generations

Still frame from Star Trek: Generations showing Picard at Kirk's grave. — Picard stands over Kirk’s grave.

This is one of the biggest “what-ifs” in Star Trek – at least for fans of a certain age! Kirk’s death in Generations was controversial, though I’d argue it was at least fitting for his character that he gave his life in an act of sacrifice, saving the crew of the Enterprise-D and the population of Veridian III from the Nexus. But in this alternate timeline, Kirk and Picard are able to stop Soran without Kirk losing his life.

Kirk would reunite with Picard and then meet up with the crew of the crashed Enterprise-D, before boarding a rescue ship bound for Federation space. Upon reaching a starbase, Kirk would be absolutely stunned to disembark only to be greeted by Spock and Montogomery Scott! Scotty had survived to the 24th Century in a transporter buffer (as seen in the episode Relics) and of course, Vulcans live longer lives than humans so we know that Spock is also still alive. This reunion would be incredibly touching, and Kirk would spend time with his old friends, catching up on almost eighty years of Spock’s life and also learning of Scotty’s 24th Century adventures.

Still frame from Star Trek: Generations showing three starships departing Veridian III. — Kirk would board a rescue ship and return to Earth.

Kirk would be debriefed by Starfleet Command about his time in the Nexus and would also seek out other members of his crew. Dr McCoy would have passed away, but at least one other member of the Enterprise’s bridge crew – someone like Uhura or Chekov – could still be alive in this time period, though they’d be very old! Kirk would visit them at their home, catching up on the events of their lives after he’d last seen them. Having decided to retire from Starfleet around the time the Enterprise-B was commissioned, Kirk would consider returning to his home – which has been preserved as a museum by Starfleet for the last eighty years – but I’m not so sure that that’s what he’d do.

We know that, in between the events of Relics and Star Trek ’09, Scotty was still working in some capacity – it’s in this era that “transwarp beaming” is invented. I’m going to say that, for the purposes of this alternate timeline, Kirk would return to Starfleet. In an unofficial capacity at first, he’d work with Scotty and Spock, and might also be visited by an old rival: the Klingon Captain Kor, now a Dahar master. Kor would invite Kirk to Qo’noS, where he’d see the results of his work to bring about peace between the Federation and the Klingon Empire.

Still frame from Star Trek III: The Search for Spock showing Kirk out of uniform at his home. — Kirk could still have some adventures and new experiences in the 24th Century.

Kirk would also be present at the launch of the Enterprise-E, reuniting with Picard as the ship undertook her first cruise. Scotty would also be present, having opted to join his former captain at the launch of the latest ship to bear the name Enterprise. Kirk and Scotty would have departed the ship shortly before the Battle of Sector 001, though. Kirk would be offered a promotion back to the rank of Admiral, and he’d join Starfleet Command in an advisory role; many senior Starfleet officers and admirals would call upon the famed officer for advice.

Where I think Kirk could be most influential, though, is in the aftermath of the synths’ attack on Mars. In the prime timeline, Picard was unable to convince Starfleet to proceed with their plan to help the Romulans, but I think Kirk would be on Picard’s side here. As a living legend and someone of such high standing in Starfleet Command, Kirk’s word would carry a lot of weight. As a result, Picard’s rescue armada would be rebuilt, and many more Romulan lives could be saved before the Hobus supernova. Among the evacuees would be Nero’s family – meaning Nero never attacks Spock’s ship, the two are never pulled into a black hole, and the alternate reality seen in Star Trek ’09 would never begin.

So that’s it!

Concept art for Star Trek: The Motion Picture showing the USS Enterprise in drydock. — Concept sketch of the USS Enterprise in drydock from *The Motion Picture*.

We’ve taken a look at five “what if” scenarios set in the Star Trek universe. I hope this has been interesting – and perhaps a bit of fun, too!

There are a lot of places in Star Trek where things could’ve gone very differently, and something as small as the absence (or presence) of a single individual has literally changed the course of history for the Federation and the entire galaxy. I can already think of plenty of other “what ifs,” so stay tuned! I’d love to revisit this idea again one day.

There’s plenty more Star Trek content coming up here on the website. So far in 2025 we’ve talked about some of my head canon, as well as some Star Trek stories that I wish weren’t canon at all! I’ve also reviewed the Section 31 film and finally caught up with Season 2 of Strange New Worlds. Season 3 will premiere later this year and I’ll definitely have something to say about it when it’s here! Until then, see you… out there.

Most Star Trek series and films discussed above are available to stream now on Paramount+ in countries and territories where the service is available. The Star Trek franchise is also available on DVD and Blu-ray. The Star Trek franchise – including all films, shows, and properties discussed above – is the copyright of Paramount Global. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Star Trek Films: My Tier List

Sun 16.02.25Dennis

Spoiler Warning: There are spoilers ahead for all fourteen Star Trek films, including Section 31.

Almost five years ago, I put all of the Star Trek films into a ranked list. I talked about what I liked and didn’t like about each, and tried to justify my choices! But since I wrote that list, a couple of things have happened. Firstly, I’ve gotten better at using images here on the website – that old piece looks pretty janky in comparison to some of my more recent articles. But secondly – and way more importantly – there’s been a new Star Trek film since then!

I think Trekkies are still a little divided on whether the made-for-streaming Section 31 should count as a Star Trek “film,” and I get that. But for me, Section 31 has the runtime of an (admittedly rather short) film, it’s not a series, miniseries, or anything like that, it has mostly original characters, and it was afforded a higher budget than any individual Star Trek episode would’ve been. For all intents and purposes, Section 31 counts as the newest Star Trek film – the fourteenth since 1979… and hopefully not the last!

Promo photo of Star Trek: Section 31 showing Quasi. — *Section 31* is the most recent Star Trek film, and it’s on this list!

So today, I’m going to revisit the Star Trek films, this time using the internet-friendly tier list format that you might’ve seen on a couple of other occasions here on the website! I think most folks have a vague idea about tier lists at this point – but if you don’t, I’ll happily explain how it works.

Instead of giving each film a number from 1-14, which would be hard, we’re going to assign each film one of five tiers: D, C, B, A, and S. D-tier films are the least-enjoyable with noticeable flaws, C-tier titles are average or “just okay,” B-tier films are a step up, being above average, A-tier titles are getting really good, and S-tier is reserved for the absolute cream of the crop! Why is S-tier the top instead of A or something like A-plus? The truth is… I don’t know! But that’s the way everyone else does it, so I’m sticking with it! Some tier lists also include an F-tier for absolute disasters, but since I don’t consider any of the fourteen Star Trek films to be that bad, I’ve opted not to include it on this occasion.

A tier list with ranks S through D and fourteen question marks where the entries would be. — Let’s fill out this blank tier list together!

Now that the explanation of the format is out of the way, a handful of important caveats!

Firstly, all of this is subjective, not objective. There is no “objectively best” Star Trek film, and even within the fan community opinions vary wildly on which titles are better and what makes for a good Star Trek story. So if I rank a title you hate highly or speak ill of your favourite… that’s okay! There ought to be enough room in the fan community for civil conversations and polite disagreement.

Secondly, this piece supersedes my old film ranking list, and I have made a couple of changes to where films were ranked five years ago. I’ll be leaving the old piece as it is, though – it’s a part of the website and it would be silly to delete it! But going forward, this is the official Trekking with Dennis Star Trek films tier list!

Still frame from Star Trek: The Motion Picture showing the assembled crew. — Admiral Kirk addressing his crew in *The Motion Picture*.

Third, I’ll rank each production in order of release, beginning with The Motion Picture and finishing with Section 31. Then I’ll show you the final tier list at the end. I’ll do my best to explain what I liked and/or didn’t like about each title to justify my ranking – but please feel free to vehemently disagree if you like!

Finally, all of this is just for fun! I like writing, I like Star Trek, and finding an excuse to talk about some of the Star Trek films that I love – or that I haven’t seen in a while – is supposed to be a bit of escapism. Nothing about this should be taken too seriously, because the point of Star Trek for me has always been entertainment and escaping to a fun vision of the future.

With all of that out of the way, let’s begin.

Film #1:
The Motion Picture (1979)
Tier: S

Still frame from Star Trek: The Motion Picture showing Spock in a space suit.

The Motion Picture had a complicated production history! It was originally envisioned as a television series, bringing Star Trek back as Phase II in the late 1970s after re-runs of The Original Series had been growing in popularity. Actors had been cast, sets were being designed, and scripts were written… but then, in 1977, another sci-fi film’s wild success led to Phase II being reimagined as a feature film. Star Trek as a cinematic franchise was born!

In my experience, Trekkies tend to underrate and underappreciate The Motion Picture. In a very literal sense, much of the visual language of Star Trek was born here, not in 1966: metal Starfleet badges, the warp core as an upright glowing tube, angled corridors, Starfleet Headquarters, the re-designed Klingons… and so much more. Sets built for The Motion Picture would remain in continuous use all the way through Enterprise’s cancellation in 2005, defining what makes Star Trek look like Star Trek for millions of viewers.

Still frame from Star Trek: The Motion Picture showing Admiral Kirk in a hallway.

The Motion Picture also has one of what I consider to be the best starship introductions in the franchise – something that set the bar for other shows! Kirk and Scotty’s shuttlepod flight to the refit Enterprise – complete with Jerry Goldsmith’s Academy Award-nominated score – is beautiful, and I get teary-eyed every time I watch it. It’s one of the best moments in Star Trek for me, and everything about it is pitch-perfect.

I get that The Motion Picture’s main story isn’t for everyone. It was also a bit of a mess, with re-writes continuing even during filming, and that probably didn’t help. But for me, The Motion Picture plays out like an extended episode of The Original Series. It’s ethereal, thought-provoking, and not overladen with fast-paced action set-pieces. I think that’s to the film’s credit, even if many don’t agree.

I have a longer piece about The Motion Picture, written in 2019 to mark the film’s 40th anniversary. You can find it by clicking or tapping here.

Film #2:
The Wrath of Khan (1982)
Tier: S

Still frame from Star Trek II: The Wrath of Khan showing a close-up of Khan.

For many folks, The Wrath of Khan is still the Star Trek franchise’s high-water mark; a film that no other in the franchise has even come close to. I wouldn’t go that far personally – I think there are a couple of other equally brilliant films, as we’ll talk about in a moment – but The Wrath of Khan is definitely up there! The mix of sci-fi with high-octane action proved to be a perfect blend for Kirk and the crew, with a vengeance-obsessed Khan becoming one of the best villains not only in Star Trek, but in all of cinema.

The Wrath of Khan has one of the best and most intense starship battles in the franchise. Drawing inspiration from submarine and naval battles in World War II films, the fight between the badly-damaged Enterprise and Khan’s USS Reliant is incredible. The sequence builds up tension masterfully – by showing the extent of the damage to the Enterprise, by robbing Kirk and Khan of their sensors in the nebula, and with Spock cleverly explaining Khan’s “two-dimensional thinking” as a way to convey the tactics of starship battles in a three-dimensional space.

Still frame from Star Trek II: The Wrath of Khan showing the USS Reliant on the Enterprise's viewscreen.

Toward the end of The Wrath of Khan, we also get one of the most poignant and emotional moments in any film in the franchise… or really anywhere in the entirety of Star Trek, come to that. Spock’s death – sacrificing himself to save the Enterprise and his friends – really hits hard. Even though on my first viewing of The Wrath of Khan I already knew that Spock would be resurrected, there’s still a real emotional weight to this moment. Star Trek has attempted to do similar things with other characters (we’ll look at a couple further down the list) but none came close to matching this moment.

Ultimately, The Wrath of Khan was the first film to wrest control of Star Trek away from its creator, Gene Roddenberry, and to try new and different things with this cast of characters. It’s very different in tone and style from The Original Series, but that turned out to be a net positive for many fans – and many new fans, too. The Wrath of Khan firmly established Star Trek as a cinematic franchise.

Film #3:
The Search for Spock (1984)
Tier: A

Still frame from Star Trek III: The Search for Spock showing the surface of the Genesis Planet.

Sandwiched in between the ever-popular Wrath of Khan and the light-hearted Voyage Home, I think some folks can overlook The Search for Spock. As the middle part of a trilogy, the film has the difficult task of moving the story along but without being able to draw all of its story threads to a firm conclusion. For my money, though, it’s a great film – and it manages a complicated sci-fi story exceptionally well.

The Search for Spock gave us an extended look at the re-designed Klingons from The Motion Picture, and also introduced the Klingon Bird-of-Prey, arguably the faction’s most iconic spaceship. It’s the film which re-introduced the Klingons in a big way, expanded the Klingon language, and introduced starship and uniform designs that have become inseparable from the faction. The Klingon Empire as we know it would not be the same – and might not be a big part of Star Trek at all – without The Search for Spock and its main villain, Kruge.

Still frame from Star Trek III: The Search for Spock showing Uhura wielding a phaser pistol.

I’ve always appreciated the design of the Genesis Planet. The story of its creation is a bit “out there,” even by Star Trek standards, but the practical sets, props, and puppets created to represent the Genesis Planet all feel like ’80s sci-fi at its best. And yes, as a child of the ’80s I’m acutely aware of my biases here! But when I compare the way that The Search for Spock looks to modern Star Trek, with its CGI and AR wall… I can’t help it. I know what I like!

As the film that destroyed the original USS Enterprise, The Search for Spock was always going to court controversy. But I don’t agree with the take that “all of the odd-numbered Star Trek films are bad,” lumping The Search for Spock in with The Final Frontier. There are some wonderful moments of characterisation for David Marcus, Kirk, Dr McCoy, and others. And thanks to the insistence of director Leonard Nimoy, all of the main cast members got moments in the spotlight.

I have a longer piece about The Search for Spock – which was the first Star Trek film I watched – and you can find it by clicking or tapping here.

Film #4:
The Voyage Home (1986)
Tier: B

Still frame from Star Trek IV: The Voyage Home showing Kirk and Spock on a bus.

Maybe this is a “hot take,” but I’ve never been wild about The Voyage Home. As with similar Star Trek stories involving time travel to the modern day, its ’80s setting has left the film feeling so much more dated than any other in the cinematic franchise, and while I enjoy a good ’80s comedy as much as anyone else… it’s not necessarily what I want from a Star Trek film.

That being said, I don’t hate The Voyage Home by any stretch. It has some incredibly funny moments as Kirk and the crew attempt to navigate a time period that’s completely alien to them. Moments like Kirk asking if $100 is “a lot” of money, or Scotty trying to use a mouse to talk to a computer spring to mind as laugh-out-loud moments, and Spock having to cover his Vulcan ears to pass as a human is a fun look. Kirk and Spock’s confrontation with a punk on a city bus was also a hilarious moment.

Still frame from Star Trek IV: The Voyage Home showing HMS Bounty approaching the sun.

On the sci-fi side of things, I really like the design and power of the “whale probe.” I think it’s unintentionally one of the franchise’s most unnerving alien creations, too. Its design harkens back to The Doomsday Machine’s planet-killer, but its power is used completely differently. The idea that this machine could simply disable all of Starfleet – and Earth – without breaking a sweat is already frightening, but when it can’t be reasoned with or even communicated with… that’s outright terrifying. Sometimes the Star Trek franchise can lean too heavily on “nose and forehead” aliens, but the likes of the “whale probe” remind us that the galaxy is a dangerous and sometimes incomprehensible place.

The Voyage Home did something Star Trek has often done: used a sci-fi lens to examine real-world issues. In this case, the loss of biodiversity and humanity’s impact on the environment were in the spotlight. The message was simple: we can’t predict the consequences of even a single species going extinct, and we should do everything we can to preserve biodiversity on Earth. That’s a good message, and it’s presented in a fun, creative story.

Film #5:
The Final Frontier (1989)
Tier: D

Still frame from Star Trek V: The Final Frontier showing Kirk, Spock, and Dr McCoy camping.

I said at the beginning that I wasn’t giving any F-tier rankings, and The Final Frontier is kind of the reason why. I get why folks don’t like it, and I think it has some obvious narrative weaknesses, as well as a smattering of sub-par special effects that make it less visually impressive than other titles in the franchise. But it isn’t a complete cinematic failure on par with something like Baz Luhrmann’s Australia or The Rise of Skywalker, so I think we can safely say that even the least-impressive Star Trek films avoid that ignominious fate!

Star Trek has delved into religion and religious-adjacent subjects before, so the idea of an alien claiming to be the god figure from various cultures isn’t totally out of left-field. But the execution of this storyline leaves something to be desired, and I just don’t think The Final Frontier really knew what it wanted to say or where it wanted to take this heavy idea.

Still frame from Star Trek V: The Final Frontier showing Scotty laying unconsious on the floor.

The film also suffers from a little too much interference from William Shatner, who exercised his contractual right to helm a Star Trek film after Leonard Nimoy had his turn in the director’s chair. Shatner wanted to tell a story that put Kirk – and Kirk alone – centre-stage, as the sole character who could stand up to Spock’s villainous half-brother. Changes were made to the first draft of that story, when Nimoy objected to Spock’s characterisation, but Shatner’s determination to put Kirk front-and-centre still comes across.

I don’t believe that The Final Frontier is irredeemably bad. There are some wonderful moments, too, like the campfire sequence with Kirk, Spock, and McCoy, Scotty’s line “I know this ship like the back of my hand,” and the away mission to Nimbus III. McCoy’s incredibly painful backstory is also one that hits close to home, and has to be one of DeForest Kelley’s best and most emotional scenes with the character. Kirk’s line to Sybok about “needing” his painful and traumatic moments – that they define who he is – is a powerful idea, too. I just feel that, taken as a whole, The Final Frontier misses the mark with some of its storylines and loftier concepts.

Film #6:
The Undiscovered Country (1991)
Tier: A

Still frame from Star Trek VI: The Undiscovered Country showing Starfleet officers and Klingons at a diplomatic dinner.

After the disappointment of The Final Frontier, it took some persuading for another Star Trek film to be greenlit. In 1991, with The Next Generation well underway and work progressing on spin-off ideas, there were some at Paramount Pictures who argued that Star Trek had moved on from The Original Series and its characters. A proposal to reboot Star Trek with a Starfleet Academy film was seriously considered, but ultimately Gene Roddenberry and others were able to convince the studio to allow the cast one final film to end on. The Undiscovered Country was thus given the green light.

The story here is great, and incredibly timely! The script uses the Federation and Klingons as a metaphor for the end of the Cold War; communists had been swept from power in 1989, and the Soviet Union was itself dissolved just days after the film’s premiere. The story of old rivals finding a path to peace, and old warriors with grudges finding a way to bury the hatchet, was an exceptionally powerful one – even if Gene Roddenberry hated the depictions of Kirk and Starfleet when he was shown an advance copy of the film.

Still frame from Star Trek VI: The Undiscovered Country showing the attack on Kronos One.

We get to see an exploration of the Klingon Empire, including one of its brutal prison colonies, and how the Klingons of the 23rd Century came to be neighbours and rivals rather than enemies by the time of The Next Generation’s 24th Century. There was even a role for TNG’s Michael Dorn, who played an ancestor of Worf. The Undiscovered Country did a lot to bring Star Trek’s two eras together, and as one crew departed the stage, work on the next expansion of the franchise began. Deep Space Nine would premiere just over a year after The Undiscovered Country had been in cinemas.

The “Praxis effect” – a two-dimensional circular shockwave created by a planet exploding – was named for the destruction of the Klingon moon seen in The Undiscovered Country! In a very real sense, the film’s legacy goes far beyond the Star Trek franchise, with similar visual effects still being used in sci-fi and fantasy to this day. Special effects were great across the board, and The Undiscovered Country also has a fantastic ship battle between the Enterprise, Sulu’s Excelsior, and a cloaked Bird-of-Prey.

Film #7:
Generations (1994)
Tier: S

Still frame from Star Trek: Generations showing Picard and Data in the stellar cartography room.

Is it controversial to say Generations is a good film? Because I honestly think it’s one of the franchise’s best. Bringing Kirk and Picard together was an absolute joy to watch, and I think it came at just the right moment, too – the film represents a handing of the torch from one crew to another. It didn’t come too soon, as this kind of story would’ve overshadowed The Next Generation’s characters before they’d found their feet. But by 1994, I really think the time was right for this kind of epic crossover.

I find Dr Tolian Soran to be an incredible villain, too. His motivations were easily understood, and while he absolutely needed to be stopped… part of me sympathises with him. The presentation of the Nexus as this heaven-like paradise realm, where time has no meaning and your heart’s desires can be made manifest, is the perfect motivation for someone like Soran – whose quest takes on a quasi-religious tone as a result.

Still frame from Star Trek: Generations showing the Nexus approaching Soran, who has his arms raised.

Generations killed off Captain Kirk, drawing a line under Star Trek’s original incarnation. Kirk would, of course, remain important to Star Trek, and it wouldn’t be the final time we’d see a member of his crew on screen. But in that moment it did feel very final – and Kirk’s act of sacrifice to save Picard’s crew and the population of a planet he didn’t even know… it was an intensely emotional sequence.

Generations does a lot to explore the connection between Picard and Guinan, which would go on to be important in Star Trek: Picard, too. It was also a great film for Geordi and Data – the latter receiving his emotion chip and really expanding his programming beyond what he’d been capable of before. All of the main characters got a turn in the spotlight, and there were moments of mystery, emotion, and action throughout this wonderful film.

I wrote a longer piece about this film’s villain, Dr Soran, and you can find it by clicking or tapping here.

Film #8:
First Contact (1996)
Tier: A

Still frame from Star Trek: First Contact showing the Enterprise-E and other Federation vessels firing their weapons.

First Contact is a fantastic film. But I’m docking a couple of points because of one element it introduces that I feel complicates – and crucially, detracts from – one of the franchise’s best, most iconic, and most frightening villainous factions. I’ll have to elaborate on this one day in a standalone piece, because there’s too much to fit into a few sentences right now, but in short: the Borg Queen kind of ruins the Borg for me. Worse, her presence takes away a lot of the Collective’s fear factor – especially when we get to her later appearances. I get it: First Contact is a feature film and it needed to have a single villain for Picard and Data in particular to face off against. But on the whole, I’d say the Borg Queen was not a net positive for the Collective or Star Trek.

But enough about that for now! First Contact re-introduced the Borg in style, depicting a deadly battle in space, and a slow-paced assimilation of the brand-new Enterprise-E. The scenes aboard the Enterprise’s lower decks in particular are incredibly tense; the Borg are far more frightening here than they had been in any of their earlier appearances. And although I have gripes with the Borg Queen as a concept, her scenes with Data and Picard – and the latter’s trauma stemming from his earlier assimilation experience – are all played exceptionally well.

Still frame from Star Trek: First Contact showing Captain Picard on the bridge.

First Contact also did a lot to set the stage for Enterprise – though that wasn’t necessarily the intention at the time! Enterprise does, though, build on what First Contact did with its depiction of Earth and humanity’s first efforts to build a faster-than-light engine. James Cromwell, who played Zephram Cochrane, would even have a cameo in Enterprise’s premiere.

Picard is the real star of the show this time, as he lets his emotions overwhelm him when faced with the Borg’s return. After the episode Family, we didn’t really get much exploration of Picard’s mental state and how he was coping with having been assimilated by the Borg, but First Contact took that as a starting point to tell a story touching on things like post-traumatic stress. It was genuinely interesting – and also left a lot for Star Trek: Picard to build on a quarter of a century later.

Film #9:
Insurrection (1998)
Tier: B

Still frame from Star Trek: Insurrection showing Data wielding a phaser pistol.

Insurrection gets an unfairly bad rap, in my opinion. I like some of the connections in the film to the wider world of Star Trek – nowhere else will you hear Troi and Riker mention the Dominion War, for instance! The Briar Patch is a fun idea both narratively and visually, leading to the crew being cut off from Starfleet HQ. It also sets up a particularly creative starship battle, which as always is something I appreciate!

Star Trek has, on several occasions, had a “badmiral” (a portmanteau of ‘bad’ and ‘admiral’) as a villain, and the concept of a rogue or renegade senior officer is an interesting one. The best villains have some degree of nuance, and Anthony Zerbe does an excellent job conveying this with the character of Admiral Dougherty. Dougherty genuinely believed that he was doing something great for the Federation… even though, with the story being told from the perspective of the Enterprise crew and the Ba’ku, he was the villain.

Still frame from Star Trek: Insurrection showing a close-up of Admiral Dougherty.

The Son’a were an interesting addition to Star Trek, and I’d love to explore a bit more of their culture one day – it’s a shame they’ve never returned. I would posit that the film’s twist – that the Son’a and Ba’ku are the same race – was imperfectly executed, but it was an interesting idea that achieved most of what it was aiming for. It’s also an idea that felt very “Star Trek,” harkening back to The Original Series episodes that had messages about war, race, and so on.

Insurrection has another great villain in Ru’afo, who doesn’t have that same nuance we were talking about, but was delicious to watch nevertheless thanks to an excellent performance from F Murray Abraham. It’s also a great film for Riker – who gets a turn in the captain’s chair during a tense battle, and also sees a starship manoeuvre named after him – and Data, whose “injury” and ethical reset kicks off the entire story. A story about a renegade crew who have to operate outside of the law to do the right thing? That’s something I love – and while I get there are criticisms of the main cast apparently acting “out-of-character,” that’s explained well enough in Insurrection itself.

Film #10:
Nemesis (2002)
Tier: D

Still frame from Star Trek: Nemesis showing Picard and Data, illuminated by a green light.

Walking out of the cinema after the credits rolled, I remember feeling okay about Nemesis. But looking back, particularly after seeing Data being laid to rest in Star Trek: Picard’s first season, the deficiencies of the film are much more apparent. I would argue, with Brent Spiner ageing out of the role by 2002, that killing off Data made some degree of sense as a narrative point. But it wasn’t handled well in Nemesis, with the film rushing past Data’s death, pushing his friends to a “let’s all move on” type of ending that was just weirdly out-of-place and had completely the wrong tone.

Sci-fi tropes and character archetypes will land differently for different folks, and what I’d say about Nemesis’ main villain – played by Tom Hardy in one of his first big-screen roles – is that the idea of a clone of Picard isn’t as silly as it sounds! There’s genuine lore and story here, expanding our understanding of the Romulans and the way they operate, and I really did enjoy that side of the story. Shinzon also makes for a complex character; a human raised by Reman slaves, who has Picard’s DNA but none of his humanity.

Still frame from Star Trek: Nemesis showing the damage to the Enterprise-E's bridge.

Shinzon quite quickly turns to “I’m evil for no reason and I love it” with his characterisation, though, despite some early promise, and by the time the film moves to his plot to attack Earth and the Federation, the plot kind of goes off the rails. Much has been made of director Stuart Baird’s lack of experience and knowledge of Star Trek at the time of the film’s production (he hadn’t so much as watched a single episode of The Next Generation) and I think that comes across in the way the film treats most of the main characters, too.

After Insurrection hadn’t been particularly well-received, and with Enterprise struggling to find an audience, Nemesis didn’t do the Star Trek franchise any favours in 2002. It also seemed – for close to twenty years, anyway – to be a weak and unimpressive ending for The Next Generation characters and Star Trek’s 24th Century setting. As in any Star Trek project, pretty much, there are moments in Nemesis that work, but not enough of them to make the film a success.

Film #11:
Star Trek (2009)
Tier: C

Still frame from Star Trek (2009) showing the Narada on the Enterprise's viewscreen.

I have some conflicting thoughts about 2009’s Star Trek. On the one hand, I was absolutely thrilled to learn of the film’s existence after Enterprise’s cancellation seemed to signal the demise of the entire Star Trek franchise. I did my best from 2006 to support the film while it was in production, and raced to the cinema to see it on the first day it was available. And I would make the case to anyone that Star Trek ’09 is a solid action/sci-fi film, a great introduction to Star Trek for newbies, and a successful title that proved the franchise could still bring in audiences and money at the box office.

But on the other hand, the film’s action-heavy storyline, re-cast classic characters, and fairly basic villain just aren’t what I come to Star Trek for. The new actors were given an exceptionally difficult job and were brave to take it on; I know some Trekkies who, to this day, have refused to watch any of the Kelvin timeline films because of the decision to re-cast Kirk and the crew. Some of the new actors got a lot of criticism before the film had even premiered due to that. Personally, I generally feel they all did a solid job… but there’s always gonna be a sense that they aren’t the “real” Kirk, Spock, Uhura, and so on. Some decisions – like pitting Kirk and Spock against one another, even coming to blows at one stage – really hammers home how different these versions of the characters feel.

Still frame from Star Trek (2009) showing Spock Prime.

Star Trek ’09 is unashamedly a reboot, and if you meet it where it is and you’re able to accept that, I think there’s a good time to be had with at least parts of it. But as someone who’d been a Trekkie for close to twenty years when the film premiered, who’d been immersed in the world of The Next Generation era in particular… I wasn’t really interested in a reboot. After Enterprise, I wanted to see Star Trek move its timeline forward again, not stepping back to re-cast classic characters for a pretty basic action story.

All that being said, I appreciate what Star Trek ’09 did for the franchise. If this film hadn’t found an audience and proved to studio executives that there was still life in Star Trek and still stories to tell here, that would’ve almost certainly been the end of the franchise, and I doubt we’d have seen Lower Decks, Strange New Worlds, and the rest of modern Star Trek. Keeping the flag flying for the franchise after it had burned out on the small screen is the real legacy of Star Trek ’09 – at least for me.

Film #12:
Into Darkness (2013)
Tier: B

Cropped promotional poster for Star Trek Into Darkness.

I would argue that Into Darkness is the high-water mark of the Kelvin timeline. There are still issues with the characters, some contrivances with the story, and so on… but the film’s script is generally much stronger than either of the other Kelvin films. Not only that, but this particular story – featuring notorious villain Khan and a “badmiral” scheming from within Starfleet itself – lends itself much more to the kind of action-packed film that JJ Abrams wanted to make.

Captain Pike’s death in Into Darkness genuinely hit me – it was unexpected in the moment, and Kirk’s reaction to the loss of someone he viewed as a surrogate father figure was truly heartbreaking. It’s definitely one of the most powerful moments for this version of the character, and the way it spurs on the plot was good, too. I also liked the callback to Star Trek ’09 with the “transwarp beaming” idea returning, this time as a problem to be overcome.

Still frame from Star Trek Into Darkness showing Khan and Kirk.

If you were online and involved in Star Trek discussion groups and forums circa 2011-2013, you would’ve almost certainly had Into Darkness’ big reveal spoiled for you ahead of time. Unfortunately, fans correctly guessed that Benedict Cumberbatch would be playing the legendary Khan – and going into the film with that expectation certainly put a downer on the scene where Kirk learns the truth. I always prefer to see films un-spoiled, but this rumour was everywhere at the time, so it was unavoidable.

For a variety of reasons, this story just feels stronger and, most importantly, better-suited to these characters and this style of film. Into Darkness is a better film as a result, with a consistent tone, understandable character motivations, and a pair of solidly entertaining villains. There are some contrived moments – and I don’t think Kirk’s sacrifice and “death” works anywhere near as well as Spock’s did in The Wrath of Khan, which Into Darkness tries to emulate in more ways than one – but on the whole, it’s not a bad film by any stretch.

Film #13:
Beyond (2016)
Tier: C

Still frame from Star Trek Beyond showing Kirk with a seatbelt on.

Penned by Scotty actor Simon Pegg, Beyond was a genuine, well-intentioned attempt to bring the Kelvin timeline films slightly closer to “classic Star Trek” in terms of tone and themes, and I really do admire the effort. There are moments that link up with Star Trek’s past – most notably Enterprise – and parts of the film, particularly its opening scenes, succeed at recreating at least some of that “mission of exploration” feeling that the other Kelvin timeline films didn’t spend even a second on.

But there are some flaws and weaknesses, though. The destruction of the Enterprise is by far the weakest loss of a ship in the franchise, as we just don’t have anywhere near as much attachment to it as we did to the original Enterprise, the Enterprise-D, and other ships that have been destroyed. The sequence was tense, particularly as the crew rushed to their escape pods, but the emotional weight of the moment didn’t ring true for me.

Still frame from Star Trek Beyond showing a Federation security team aboard the Enterprise.

I felt that an actor of Idris Elba’s calibre was also squandered on a pretty basic “I’m mean and I hate everyone” type of villain. Krall had potential – the “lost” captain who felt abandoned by Starfleet and the Federation, and whose xenophobic and war-like traits were a century or more out of date. But the film didn’t do enough with Krall, and the big reveal that this alien-looking alien was, in fact, a human didn’t really stick the landing. Again, it was interesting in theory but kind of wasted by the time it came to the screen.

I might be alone in this, but I detest the name “Jaylah” for the film’s new character. A homonym of “J-Law” – the tabloid nickname given to American actress Jennifer Lawrence, who was a big star at the time thanks to her role in The Hunger Games – this reference just felt cringeworthy and unnecessary. I’m happy for Star Trek to take inspiration from a wide range of other films, including the likes of The Hunger Games, but don’t stoop to this level when it comes to character naming. It’s just… well, it’s pretty pathetic, to be honest.

I couldn’t end this section without also noting that Beyond was rather overshadowed by the deaths of Leonard Nimoy and Anton Yelchin in the months leading up to its premiere.

Film #14:
Section 31 (2025)
Tier: C

Still frame from Star Trek: Section 31 showing a trio of main characters.

You have to try to meet Section 31 where it is. It’s a B-movie; the Star Trek equivalent of The Fast and the Furious or Transformers, complete with a cookie-cutter plot, some pretty mindless action, and plenty of tropes of both action flicks and spy movies. Once I realised that that’s what I was watching… I just kind of went with it. On those terms, I found Section 31 to be just fine.

Where my disappointment comes in is in the wasted potential. There was scope for Section 31 to be the kind of film that brings new eyes to Star Trek for the first time, genuinely expanding the fan community by making what can feel like a nerdy and overcomplicated franchise approachable. I don’t believe Section 31 came close to achieving that goal, unfortunately. And from my perspective, that felt like the biggest point in its favour and a key reason for making it.

Still frame from Star Trek: Section 31 showing Sahar and Fuzz fighting.

I would also argue that Georgiou’s arc in Section 31 was pretty repetitive, dragging up her Mirror Universe origin and forcing her through a story that we’d already seen a lot of in Discovery. Dragging her back from the more complex character we’d started to see so she could re-start that arc wasn’t great. And that’s before we get into the weeds on whether a redemption story for someone at least as evil and despotic as Star Wars’ Emperor Palpatine was even possible, let alone successfully executed in Section 31.

There are also gripes with how disconnected this film feels from the rest of Star Trek, with the barest of references and none of the franchise’s visual language present. If, however, you can set most of that aside… there are fun moments hiding under the surface. And as I said a moment ago, if you can meet Section 31 where it is, on its own terms, I think it’s a perfectly adequate B-movie.

I have a two-part review of Section 31. You can find the non-spoiler part by clicking or tapping here and the part containing story spoilers by clicking or tapping here.

So that’s it!

We’ve put all fourteen Star Trek films into a tier list. So let’s take a look and see how we did:

The finished tier list with all fourteen Star Trek films.

Well, I hope that was worth it! As you can see, we have more films in the upper tiers than the lower ones, and even the “worst” Star Trek films still have redeeming qualities – at least in my opinion.

I wanted to put this list together after Section 31 had premiered, updating my older list to include the new film. This piece almost certainly concludes my Section 31 coverage for the foreseeable future, as I really don’t have much more to say about the made-for-streaming movie at this point. If you’ve been following my coverage of Section 31, thank you! I hope you’ve found my take to be interesting.

Still frame from Star Trek: The Motion Picture showing the Enterprise at warp. — The USS Enterprise at warp.

At time of writing, there are supposedly two Star Trek films in pre-production or at least being worked on in some capacity. The first is a Beyond sequel, bringing back the Kelvin timeline cast for another outing. And the second is supposedly set in between Enterprise and Star Trek ’09, perhaps serving as a kind of Kelvin timeline prequel. You can read my thoughts on that idea by clicking or tapping here.

There have been other film proposals pitched over the years. Sir Patrick Stewart teased fans in early 2024 with news of a Picard movie idea, but I don’t think anything came of that. For my money, I’d like to see Paramount do more with the TV movie format, using it to tell one-off stories that wouldn’t necessarily fit anywhere else in the franchise. With new sets having been constructed, and the AR wall too, there are almost no limits on the kinds of stories that could be told as one-off specials – and the budget for such a production would be lower than a feature film, too! With Section 31 proving to be a disappointment, though, I’m not sure whether that’ll ever happen.

Still frame from Star Trek VI: The Undiscovered Country showing two starships, a planet, and a star. — The Enterprise and the Excelsior in orbit over Khitomer.

So I hope this has been a bit of fun! Beginning with Generations, I watched every Star Trek film at the cinema. Unfortunately, due to my health, I won’t be able to do that in future – which is why I enjoyed having Section 31 as a TV movie! But if there ever is another full-length Star Trek film, I’ll do my best to support it here on the website.

Until next time… Live Long and Prosper!

Most of the Star Trek films are available to stream on Paramount+ in countries and territories where the platform is available. The first thirteen films are also available on Blu-ray and DVD, and a Blu-ray release of Section 31 is planned. The Star Trek franchise – including all films and properties discussed above – is the copyright of Paramount Global. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Ten Things That Have Always Bugged Me In Star Trek

Mon 20.05.24Mon 20.05.24Dennis

Spoiler Warning: Beware spoilers for the following Star Trek productions: The Original Series, The Next Generation, Deep Space Nine, Voyager, Enterprise, Discovery, Picard, Generations, and First Contact.

Let’s have a little bit of fun today at the expense of the Star Trek franchise! I’ve been a Trekkie for almost thirty-five years at this point, and I’ve seen a lot of Star Trek in that time! For a franchise that now runs to over 900 individual episodes of television, Star Trek’s internal consistency and the attention to detail shown by the writers and creative teams are generally incredibly good, and there aren’t many true inconsistencies or things to get worked up about. But that doesn’t mean there are zero!

If you’re a regular reader, you might’ve seen me use the expression “glorified nitpick” in some of my Star Trek episode reviews. Sometimes I’ll point out something that I felt didn’t work very well or that seemed to run counter to what we already knew about a situation or character. Well… most of what we’re going to talk about today doesn’t even rise to that level! These aren’t things that I’m cross about or that “ruined” an episode or story for me. They’re just, as the title says, little things that bug me!

Publicity photo for Star Trek: Picard showing the rebuilt Enterprise-D bridge. — The bridge of the Enterprise-D.

Before we go any further, here are my usual caveats! Firstly, all of this is my entirely subjective opinion. If you disagree with any or all of the points below, think I’m “overreacting,” or feel that I’ve totally got the wrong end of the stick… that’s okay! These are just a few stray thoughts that I have about Star Trek, and most of them are so minor that they’re not gonna be worth getting into an argument about! Secondly, this is intended as light-hearted, tongue-in-cheek fun – so I encourage you not to take me too seriously and to engage with this article in that spirit!

Finally, I’m not counting the old excuses of “it’s just a story” or “because the writers thought it worked better that way” as explanations! Sure, everything in Star Trek is “just a story,” and if the writers needed to move characters into place or kick off certain storylines in a way that opens up a minor inconsistency, that’s just the way it goes sometimes. But as a fan, and as someone engaged with this fictional setting, that excuse doesn’t really work for me – and it never has. So it’s true that “none of this is real,” but that doesn’t change anything for me!

With all of that out of the way, let’s get started!

Number 1:
Why was the unfinished Enterprise-B the only ship within several light-years of Earth?
Star Trek: Generations

Still frame from Star Trek: Generations showing the launch of the Enterprise-B. — The Enterprise-B embarks upon her ill-fated maiden voyage.

Kicking off the plot of Generations is the maiden voyage of the Enterprise-B under the command of Captain John Harriman. Joining him for the voyage are Captain Kirk, Montgomery Scott, and Pavel Chekov, but during what was supposed to be a short shakedown cruise entirely within the Sol system, a distress call was received that took the Enterprise-B right into the path of a dangerous energy ribbon called the Nexus.

But here’s my question: why did Starfleet have no other ships anywhere close to the SS Robert Fox and SS Lakul? This is Sol – the home system of the Federation and Starfleet, where Starfleet Headquarters, the Federation government, and Spacedock are all located. With the Enterprise-B on a glorified joy-ride to show her off to a gaggle of journalists, and with weapons and other essential systems still not installed… why would she be the only ship in the area?

Still frame from Star Trek: Generations showing the Enterprise-B in the Nexus. — The Enterprise-B encounters the Nexus.

Think about it: this would be like the only military unit within a hundred miles of Washington DC being a single brand-new tank without its gun barrel. If the Enterprise-B’s shakedown cruise had taken her beyond Sol, then things might feel a little better. But having no other starships anywhere close to the stricken refugee vessels always struck me as bizarre!

If Starfleet leaves its home system and institutions of government so sparsely defended, it’s a miracle that the Klingons, Romulans, or Borg haven’t been able to warp into the system and conquer Earth! Jokes aside, I think the opening of Generations is pretty great – and the film in general is one of my personal favourites. But that doesn’t mean I can just overlook what appears to be Starfleet’s atrocious planning and non-existent defences!

Number 2:
What’s the United Earth Space Probe Agency?
Star Trek: The Original Series

Still frame from Star Trek: Voyager showing the probe Friendship One. — Friendship One, a probe launched by the UESPA.

Prior to settling on more familiar terms like the United Federation of Planets and Starfleet, the United Earth Space Probe Agency (or UESPA) was an organisation that was mentioned in a couple of early Star Trek stories. But what the organisation is and what its relationship is with Starfleet and the Federation was never elaborated upon, and plot points in Enterprise have further muddied the waters.

The out-of-universe explanation for this one is simple enough: as Star Trek was being created and those early episodes were being written, some titles and names were still being decided upon. It wasn’t even settled until well into production on The Original Series’ first season that the show was set in the 23rd Century – the original pitch for the series didn’t specify an exact time period, and the 27th Century was also suggested as a possibility.

But as I said at the beginning, out-of-universe explanations don’t count!

Still frame from Star Trek: The Original Series showing Kirk and Spock. — The UESPA was mentioned a handful of times in the first season of *The Original Series*.

Enterprise could have put this to rest, but instead the series – quite understandably – wanted to use familiar names like Starfleet, so the UESPA wasn’t included in a big way. Occasional references to it have popped up, including in Voyager where the UESPA had sent out at least one unmanned probe, but nothing to definitively explain what it was and whether it was independent of Starfleet.

To me, the “United Earth” part of the name seems to suggest that it’s a human-only organisation, but with humanity’s ships all seemingly flying under the Federation flag, what role there could be for a United Earth fleet – and where any of its ships or probes actually are – remains unknown.

Number 3:
Why was Starfleet unable to detect the octonary star system?
Star Trek: Picard

Still frame from Star Trek: Picard showing eight stars in formation. — Eight stars in perfect gravitational harmony.

In Season 1 of Picard, the ancient super-synths that I nicknamed the “Mass Effect Reapers” literally moved eight stars to form a stable octonary star system. They did so to make their presence known, and on the planet in that system they left their beacon behind. But… how did Starfleet – with all of its sensors, missions of exploration, advanced telescopes, and stellar cartography departments – fail to notice such an apparently obvious and incredibly interesting stellar phenomenon?

Using technology that we have right now – today, in the early 21st Century – we can look not only at stars, but detect the planets orbiting them, view distant galaxies, and even find black holes. I find it impossible to believe that Starfleet hasn’t at least scanned the entire Milky Way, detecting every star and star system – so how did they miss something so obviously artificial in nature?

Still frame from Star Trek: Picard showing Raffi and the ENH. — The symbol representing the octonary star system.

If Picard had explained that, for instance, the Romulans deployed a cloaking device to shield the octonary system, or that Starfleet did know about the system but couldn’t explore it because of its location behind the Neutral Zone, then I’d have nothing to complain about. But a fairly sizable plot point in one episode involved the crew of La Sirena finding out that this star system had been deliberately hidden from Romulan star charts… when surely the Federation, who aren’t that far away from it in the same region of the galaxy, would have been able to see it through their telescopes! Again, if this system was in a far-flung part of the Gamma or Delta Quadrants, I’d still argue that Starfleet should’ve detected it, but its distance could be its saving grace. However, the octonary star system was supposedly in or near Romulan space – meaning it’s a mere stone’s throw away from the Federation.

In The Next Generation, the Enterprise-D is transported by Q to a system that would’ve taken them years to reach at top speed. But Starfleet already had a designation for this system: J-25. To me, that implies that the Federation has already categorised at least the Alpha and Beta Quadrants, even if ships haven’t been able to explore all of these systems yet. So once again… how did Starfleet miss an entire eight-star solar system?

Number 4:
How did the Enterprise-E reach Earth so quickly from its position near the Neutral Zone?
Star Trek: First Contact

Still frame from Star Trek: The Original Series showing a map on the main viewscreen. — A map of part of the Neutral Zone.

Star Trek’s geography has always been kept vague, and I think that’s been to the franchise’s overall benefit! But there are a few places where the distance between planets and systems seems to be inconsistent. At the beginning of First Contact, for example, we have the Enterprise-E sent away from the main fleet to patrol the Neutral Zone – despite an imminent Borg incursion. But when the battle turns against the Federation fleet, Picard is able to get the Enterprise back to Sector 001 in what seems to be a matter of hours, if not minutes.

Prior Star Trek stories, including in The Original Series and The Next Generation, had seemed to depict the Romulan Empire as being on the Federation’s far border, with outlying colonies disappearing in The Neutral Zone and “Earth Outposts” in Balance of Terror all being depicted as far-flung places. Even if we assume that Romulus is relatively close to Earth, and that the Enterprise-E was very conveniently positioned at the near end of the Neutral Zone, getting back to Earth while the battle was still raging still feels like a tall order.

Still frame from Star Trek: First Contact showing the Enterprise-E firing phasers. — The Enterprise-E at the Battle of Sector 001.

Warp factors in Star Trek are kept pretty vague – so that could account for some of this apparent discrepancy, I suppose. If the Enterprise-E could travel significantly faster than the Enterprise-D, the travel time from the Neutral Zone could be reduced. Again, it still seems to rely on the ship being fortunate with its positioning, but maybe that’s something that could be accounted for by Captain Picard preparing for this eventuality!

Still, it’s always struck me as more than a little odd that the Enterprise-E was able to reach Earth in time. Not only was Picard able to follow the Borg Sphere through the portal it created, but there was even time to save the USS Defiant and Worf before destroying the main Borg Cube. A very quick turnaround indeed!

Number 5:
Why wasn’t there a debate about which route to take?
Star Trek: Voyager

Still frame from Star Trek: Voyager showing Captain Janeway. — Captain Janeway ordered her crew to take the most direct route back to Earth.

After the crew of the USS Voyager found themselves stranded on the far side of the galaxy, Captain Janeway very quickly ordered her crew to set a course for Earth. But the most direct route to Earth, through the Delta Quadrant and later the Beta Quadrant, took the ship right into the heart of Borg territory. Janeway knew this – Starfleet had at least some idea of where the Borg’s territory was located. Even if the Delta Quadrant offered the quickest way home, I’m surprised that nobody objected or tried to propose an alternative – especially when there was a good one.

Before getting transported to the Delta Quadrant, the USS Voyager made a stop at Deep Space Nine. And what’s located right next to the station? The Bajoran Wormhole! The wormhole offers a shortcut to the far side of the Gamma Quadrant – and heading in the direction of the wormhole rather than directly for Earth is something that Janeway and the crew could have considered.

Still frame from Star Trek: Voyager showing the rear of the USS Voyager. — The USS Voyager prepares to begin its long journey.

At this point in the timeline, the Dominion War hasn’t started – so that can’t be used as a justification for not heading that way. And while all we have to go on are non-canon sources, there’s at least some tentative evidence that the wormhole’s terminus is located roughly the same distance from the Ocampa homeworld as Earth. If that’s the case, it would be no slower to head that way. Based on the Borg threat alone, I would have argued that heading for the wormhole is actually the smarter play.

Obviously Voyager was pitched as “the Delta Quadrant show,” and we got some fantastic stories out of that premise. But given the way that Voyager’s writers handled the Borg when that time came… maybe there’s an out-of-universe argument to be made here, too! In any case, even if Janeway had ultimately made the decision to head back to Earth via the most direct route, some discussion or debate would have been an interesting inclusion as the series got going. It could’ve been a way to draw some dividing lines between Starfleet and Maquis characters – making more of the “one ship, two crews” idea that Voyager never really explored in much depth.

Number 6:
Why did Michael Burnham and the USS Discovery head into the far future?
Star Trek: Discovery

Still frame from Star Trek: Discovery showing the Red Angel opening a time-wormhole. — The USS Discovery approaches the time-wormhole.

Wait, stop! I know what you’re thinking: “this is the entire plot of Season 2 and was well-explained! They had to leave the 23rd Century to stop Control from wiping out all life in the galaxy!” And you’re correct, of course – but I’m not looking at the season as a whole or the entire plan. I’m focusing in on the final moments before Burnham opened the time-wormhole and the ship disappeared.

During the climactic battle against Control, the “assimilated” Captain Leland boarded the USS Discovery to attempt to seize control of the ship and its invaluable Sphere data. But after being cornered by Georgiou, Leland – Control’s human avatar – was defeated and killed. At that moment, the entire battle seemed to stop, and as Pike and his crew noted aboard the Enterprise, Control’s entire fleet of drone ships were simply hanging there, apparently dead or deactivated.

Still frame from Star Trek: Discovery showing Control's fleet. — Control’s fleet of drone-ships.

At this moment – before Burnham had entered the time-wormhole and before Saru, aboard Discovery, had followed her – there should have been a moment’s pause. Maybe Burnham herself couldn’t see what was going on, but Saru and Pike could, and even communicated with one another confirming the death of Captain Leland. There was still time for the time-wormhole to be closed, for Discovery and Enterprise to regroup, and potentially for Discovery to remain in the 23rd Century.

Even if Pike and Saru had decided that the risk of Control re-establishing itself was too great, it’s bizarre to me that neither of them even considered the possibility for a moment. With their enemy apparently vanquished – at least temporarily – and with Discovery’s spore drive meaning the ship could’ve evaded Control by jumping to a different part of the galaxy, there was time to regroup and come up with a plan that didn’t involve stranding everyone in a totally different century.

Number 7:
How could Starfleet possibly prioritise anything other than hanging onto Bajor and the wormhole?
Star Trek: Deep Space Nine

Still frame from What We Left Behind showing Deep Space Nine. — Deep Space Nine remastered, from the documentary *What We Left Behind.*

I adore Deep Space Nine’s Dominion War arc – it’s one of the best (and most under-appreciated) in the franchise, in my opinion. But as the war got started, Starfleet made what appears to be a catastrophic strategic blunder. In the episode Call to Arms, which ended the show’s spectacular fifth season, Sisko informs his crew that Starfleet won’t be sending any reinforcements to hold DS9 – their priorities lie elsewhere.

We later learn that Starfleet used the diversion of the attack on DS9 to destroy a Dominion-Cardassian shipyard… but given the strategic importance of the wormhole, and the fact that the Dominion is more than capable of producing vast quantities of ships and Jem’Hadar troops in the Gamma Quadrant, it never made sense to me that Starfleet wouldn’t have thrown every available resource at the galaxy’s most strategically vital location.

Still frame from Star Trek: Deep Space Nine showing a battle in space. — DS9 could only hold off the Dominion-Cardassian attack for a short time.

The minefield that the crew of DS9 erected bought the Federation some time (as did the subsequent intervention by the Prophets), but Starfleet must’ve known that, even with the best will in the world, the minefield wouldn’t last forever. With the Dominion in control of Bajor and DS9, they could work on shutting it down without interference. The successful attack on the Toros III shipyard may have been little more than a morale-boosting pyrrhic victory.

In war, you’d almost always rather be defending a position than having to attack – and it would have been far easier to try to hold onto DS9 while the station was still under Federation control than to try to re-capture it later after the Dominion had been given a chance to entrench. For a number of reasons, the decision to essentially abandon the station is questionable at best! If part of the story had been to show Starfleet’s admiralty as out-of-touch or incompetent, that might’ve worked. But that didn’t happen, either, so I’m just left wondering what went wrong at Starfleet Command! Still, at least we got some spectacular episodes out of this storyline.

Number 8:
What happened to Dr Pulaski?
Star Trek: The Next Generation

Still frame from Star Trek: The Next Generation showing Diana Muldaur as Dr Katherine Pulaski. — Dr Pulaski in the episode *Time Squared*.

Although I really liked the character of Dr Pulaski in Season 2 – you can find a longer piece about her here, if you’re interested – I think it’s fair to say that she didn’t really knock it out of the park! A letter-writing campaign from viewers and an intervention by Patrick Stewart contributed to Gates McFadden being re-hired in time for Season 3… and then Dr Pulaski was just never mentioned again.

The nature of her departure always struck me as odd, and it feels more than a little disrespectful to both an actor and a character who, for better or worse, had been a part of the series for an entire season. When Dr Crusher disappeared at the beginning of Season 2, there was at least some effort to pay lip service to her absence – it was explained that she was on another assignment at Starfleet Medical on Earth. Dr Pulaski didn’t even get that, and to the best of my knowledge has never been so much as mentioned since.

Still frame from Star Trek: The Next Generation showing several characters on the bridge. — Dr Pulaski with Riker, Worf, and Troi on the bridge.

We can argue the toss about the benefits or drawbacks of keeping her around – and I go over that in a bit more detail in my character study which I’ve linked above, if you want to see my thoughts on that. But whether you think she was a fun addition to the crew, an annoyance, or whether you just liked Dr Crusher better… you gotta admit that it’s odd that she didn’t get so much as a log entry from Captain Picard to acknowledge her departure.

The second season of The Next Generation was my “first contact” with the Star Trek franchise. The first episode I can solidly remember watching is The Royale – which Dr Pulaski is barely in! But maybe that’s why I’ve always had an appreciation for her character. I like the dynamic that she brought to the crew as someone a bit older, a bit less personable, and who had history with some characters and seemed to be developing new relationships with others. There have been opportunities in recent years for Dr Pulaski to have returned – or at least to have been mentioned. But I doubt that will happen now!

Number 9:
Who invented the cloaking device and when did Starfleet first encounter it?
Star Trek: Enterprise

Still frame from Star Trek: Enterprise showing Enterprise and two Romulan ships. — Two 22nd Century Romulan vessels de-cloaking.

This is a point that I have a personal “head canon” explanation for that I’d love to elaborate on in a full article one day! I’ll get into that in a moment, but for now, suffice to say that this is a classic example of a “prequel problem.” In short, The Original Series first season episode Balance of Terror clearly established that the Federation had never encountered a ship that could cloak, but Enterprise and Discovery – both set prior to The Original Series but produced decades later – show Romulan and Klingon ships operating under cloak and Starfleet being fully aware of this.

This raises several questions! What are cloaking devices, how do they work, and why would Starfleet not share the details of their existence with its captains, at the very least? Kirk and his crew seemed shocked that the Romulan vessel could cloak – but the Romulans had been seen cloaking and de-cloaking more than a century earlier, as had other races like the Suliban. We can debate whether the words “cloak” or “cloaking device” were spoken in those episodes – but the technology appears to be functionally the same, so semantics won’t cut it here!

Still frame from Star Trek: Strange New Worlds showing a Romulan vessel cloaking. — A Romulan ship engaging its cloaking device in the 23rd Century.

When Enterprise was on the air I wasn’t a regular viewer, but I remember that I did catch the episode Minefield – in which a Romulan vessel is seen de-cloaking – and that led to me creating my own “head canon” explanation for this problem. I remember seeing debates on Star Trek message boards in the early 2000s about this topic, and I felt that all the producers would need to do would be to explain, somehow, that there are different types of cloaking devices. Perhaps Starfleet felt that they’d cracked the code, but the Romulans then invented a newer and better cloak. Perhaps there was even a cloaking and un-cloaking arms race between the factions.

In short, I think Star Trek can just about get away with this one by explaining that, when Starfleet figured out how to penetrate one style or type of cloaking technology, the Romulans or Klingons would refine it, re-modulate it, or invent something new. It’s not a perfect explanation, but it plugs most of the hole that Enterprise and Discovery have dug. I still think it would be nice to see something like this made official, in-universe – and let’s be honest: it would be better if these prequel-created plot holes didn’t exist in the first place!

Number 10:
What’s up with the inconsistent uniform changes?

Still frame from Star Trek: The Next Generation showing Captain Rachel Garrett. — Captain Rachel Garrett of the Enterprise-C.

The series premiere of The Next Generation established that the Enterprise-D’s voyages took place almost 75 years after Kirk’s tenure in the captain’s chair, but the “monster maroon” uniforms from The Original Series films would often make appearances in flashbacks or episodes set in the past. Starfleet appeared to have stuck with that design for decades, albeit with a few minor tweaks. Using those uniforms for such a long time already felt odd, but then things started to take a turn!

The Next Generation switched uniforms at the beginning of Season 3 for its main characters, but the Season 1-2 uniform variant was still showing up on secondary characters and background characters well into Season 4. There was also a total mess in Generations, which seemed to depict a moment of transition from one uniform style to another – although Deep Space Nine seemed to have established that space stations might use different uniforms from starships? I’m still not sure about that!

Still frame from Star Trek: Lower Decks showing the four main characters. — Two different uniform styles seen in *Lower Decks*.

Deep Space Nine made an abrupt switch to the gray-shouldered uniforms midway through its run (to coincide with First Contact’s premiere), and that was okay, I guess. Far more of an instant transition than we’d seen in Generations or The Next Generation, but not necessarily a problem. But then the alternate reality films and post-2017 TV shows have really shaken things up! I’ve said before that I don’t like to get hung up on minor things like aesthetic choices, and I was generally accepting of Discovery’s all-blue look, even if it was supposedly set in between The Cage and The Original Series whose uniforms are well-known. But Lower Decks definitely complicated things by seeming to suggest that different “tiers” of starship would get different uniforms… for some reason.

In short, Star Trek hasn’t always been consistent or clear with the way Starfleet uniforms are used, how long they’re in use for, or which types of officer/crewman should wear what type of uniform. When watching an individual episode – or even a whole season of TV – this doesn’t really seem all that noticeable. But when you pick out different stories or take a big-picture look… these inconsistencies stick out.

So that’s it!

Still frame from Star Trek: Strange New Worlds showing the USS Enterprise. — The USS Enterprise in *Strange New Worlds*.

We’ve nitpicked the Star Trek franchise and pulled out ten little things that have always bugged me! As I said at the beginning, none of these really spoil Star Trek for me, and I’m more than willing to overlook minor inconsistencies or small plot holes – especially in strong, otherwise entertaining stories. But when you step back and take a look at Star Trek – or any fictional world, come to that – there are always gonna be things that don’t quite make sense or that don’t seem to fit with the rest of the setting.

All of this was just for fun, and I hope it was an interesting look at a handful of minor issues that have emerged over the years. When a franchise has been running on and off for close to sixty years, that kind of thing is inevitable! Although I’ve been feeling a bit burned out on Star Trek of late, it was still enjoyable to jump back into some of these stories – several of which I hadn’t seen for years – to put together this list.

Until next time – and Live Long and Prosper!

The Star Trek franchise – including all films and series discussed above – is the copyright of Paramount Global. Most Star Trek films and episodes are available to stream on Paramount+ in countries and territories where the service is available. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Great Star Trek villains: Dr Tolian Soran

Fri 23.07.21Sun 13.11.22Dennis

Spoiler Warning: There are spoilers ahead for Star Trek: Generations. Minor spoilers may also be present for other iterations of the Star Trek franchise.

The Star Trek franchise has featured some absolutely terrific villains across its fifty-five year history. Characters like Khan, Gul Dukat, the Borg Queen, and many, many more have gone on to play significant roles in the franchise, cranking up the tension and drama while giving fans someone to truly despise. One of my all-time favourite Star Trek villains comes from what may – controversially – be my favourite Star Trek film: Dr Tolian Soran from Star Trek: Generations. It’s this character that I want to talk about today.

Although their motivations are very different, I feel that Dr Soran fills a similar role as an adversary for Captain Picard specifically as Khan did in The Wrath of Khan for Captain Kirk. Khan was motivated by vengeance and hatred for Kirk in particular, whereas Soran sees Picard as little more than a bump in the road on the way to completing a scheme he’s worked on for decades, so there are clear differences, yet in their two films the characters play similar adversarial roles for Star Trek’s first two captains.

One of Dr Soran’s lines has stuck with me ever since I first watched Generations in the cinema in 1995 (which is when the film was released here in the UK). The line is this: “Time is the fire in which we burn.” Delivered with menacing clarity by actor Malcolm McDowell, Soran’s view of time as an all-consuming fire is dark, yet beautifully poetic at the same time. Though Captain Picard would argue against this notion at the end of the film, the line, and the way it was delivered, is permanently etched in my memory. At times, it has been a motivating factor in my life, which may seem strange for a line delivered by a villain! As I said last November when I commemorated this website’s anniversary, the notion that time was catching up to me was one of the motivating factors I had in setting up my website and writing about Star Trek and other topics.

What I love most about the fire analogy is the way in which it describes the one-way flow of time. When an object is burned in a fire, an irreversible reaction takes place at the molecular level, and no matter how much we might regret burning something or wish we could undo a disastrous fire, doing so is impossible. The same is true of time – going back in time, changing the past or reliving a moment isn’t possible. (Except when Star Trek does time travel episodes, but that’s a different subject altogether!)

Although Soran was an obsessive, desperate to get back to the Nexus, his philosophical side shines through at several key moments in the story, and the way this side of his character comes across elevates him. No longer a one-dimensional villain with a singular purpose, Soran is a thinker, someone who has an understanding of the world and his place in it. His interpretation of the world, or rather his reaction to it, may be extreme, but nevertheless the mere existence of this deep-thinking aspect of his character makes him feel a lot more significant and a lot more well-rounded. Soran has clearly considered the implications of what he’s doing, even if it means sacrificing millions of lives for his own benefit.

The attacks of September 11th, 2001 brought religiously-motivated terrorism to the fore in a way that was new for many people in the western world. Yet even before then, the idea of sacrificing one’s life in order to reach paradise, or heaven, had been a significant force. Soran’s quest to reach the Nexus at any cost can be seen through this lens; a dangerously obsessed man willing to do whatever it takes to reach his version of paradise.

The desperation etched on Soran’s face shows how obsessed he had become with returning to the Nexus.

At the same time, the Nexus storyline rebuffs the idea of religion in general, at least insofar as Soran is concerned. If Soran believed in an afterlife – a belief which is not uncommon even in Star Trek’s 24th Century – then his quest to re-enter the Nexus wouldn’t make sense. He could be comforted by the belief that the afterlife would be just as good, if not better than, what he experienced there. The fact that Soran is a scientist and he’s chasing an interstellar energy ribbon that is observable and definitely exists (within the confines of the story, of course) seems to pour cold water on the idea of Soran as a religious fundamentalist; his desire to reach the Nexus is based on his own experience of the phenomenon, and not simply on the nebulous concept of “faith.”

Star Trek’s history with religion is complicated. The Original Series once showed a “chapel” aboard the USS Enterprise, and in Deep Space Nine Kasidy Yates claimed her father was a minister, so human religion definitely still exists in the 24th Century and the franchise hasn’t tried to erase it. At the same time, however, Star Trek has often tried to offer alternative explanations for gods, miracles, and other religious experiences. The Final Frontier depicted the “god” at the centre of the galaxy as a beligerent alien. Q fills a similar role on occasion in The Next Generation. The Prophets in Deep Space Nine are noncorporeal aliens. And so on.

Star Trek has frequently looked at other explanations for things like the afterlife. (Pictured: Q in *Tapestry*).

So if the Nexus represents heaven or the afterlife for the sake of Soran’s story, it’s still a scientific and secular take on the concept. Soran isn’t like Sybok, a man on a mission with faith at its core. He’s a scientist, trying to solve a scientific puzzle. The fact that it has religious comparisons is neither here nor there for him; he sees the Nexus as his one shot at paradise.

Though we don’t see anything on screen of Soran’s life prior to his encounter with the Enterprise-B, given what happened to the El-Aurians and Generations’ focus on Picard’s family, there are the building blocks to see Soran through a semi-sympathetic lens if we’re so inclined. The Borg destroyed or assimilated the El-Aurian homeworld, and during the attack they killed Soran’s family, including his wife and children. When Picard visits the Nexus, he sees a version of the life he could have led, as did Kirk. What Soran sees in the Nexus – and what he wants so desperately to recapture – is his family. At a personal level we can understand and even empathise with that, even if it doesn’t come close to excusing his actions.

Soran immediately after being beamed aboard the Enterprise-B.

A villain that we as the audience can relate to is something the best stories manage to have, and a villain who isn’t simply evil for the sake of it also makes for a much more satisfying and fulfilling narrative. Soran ticks both of those boxes. We could even argue that Soran isn’t “evil” in the strict sense of the word; he’s merely uncaring and ambivalent to the lives of others due to his single-minded dedication to his quest.

For Trekkies, Soran is perhaps most significant and best-remembered for being the character who killed Captain Kirk. Star Trek’s first captain carried the torch for the franchise for more than two decades prior to the inception of The Next Generation, and while characters like Scotty, Spock, Dr McCoy and others all had their fans and their moments in the spotlight, Kirk was the most significant character from The Original Series. His death in Generations arguably marked the end of an era, and the definitive passing of the baton from one set of characters to another.

Soran is responsible for Kirk’s death – a seminal moment in the history of Star Trek.

Though we have since had a version of Captain Kirk back in the Kelvin timeline films, and Star Trek has of course returned to the 23rd Century with Discovery and Short Treks, the death of William Shatner’s Kirk is an incredibly significant moment in the history of the franchise. While it’s true that Star Trek had already moved beyond The Original Series by 1994 thanks to The Next Generation, Deep Space Nine, and the gentle yet clear ending to The Undiscovered Country, there was still a sense that any of the main characters could return – something epitomised by the return of Spock in Unification and Scotty in Relics. Captain Kirk did get the chance to make a triumphant return to the franchise – but doing so led to his death.

Kirk’s death is clearly a hugely emotional moment, especially for Trekkies who’d been with the franchise since the beginning. But his sacrifice stopped Soran and prevented the deaths of millions, as well as the deaths of the crew of the Enterprise-D. Even though the film doesn’t really acknowledge his death in this way, he died a hero.

Soran’s scheme brought Kirk and Picard together.

It was Soran’s scheme that killed Kirk, but it also brought Captains Kirk and Picard together. Between them they had to figure out a way to prevent Soran going through with his plan, and thus Soran became the unintentional catalyst for what has to be one of my favourite moments in all of Star Trek. Marvel films have shown that a good team-up story can be emotional and exceptionally fun, but putting together two of the most significant characters in the entire Star Trek franchise? It’s a moment that’s very hard to beat even more than 25 years later!

Without Soran, none of this would have come to pass. While we may lament Captain Kirk’s death, in a franchise that runs as long as Star Trek and where the in-universe timeline spans centuries, characters are eventually going to die. Maybe Captain Kirk would have preferred a quiet retirement, but as a satisfying story beat, making the ultimate sacrifice in order to save the lives of millions and a crew of Starfleet officers could not be more quintessentially Kirk.

Soran was a fantastic villain in *Generations*.

I find Dr Soran to be an absolutely fascinating character in his own right. But more than that, he’s responsible for perhaps the most ambitious crossover that the Star Trek franchise has yet attempted, and brought together Captains Kirk and Picard for an amazing adventure in a truly excellent film.

It’s hard to pick a fault with the way Soran was brought to screen, too. Malcolm McDowell put in an outstanding performance that was intense and riveting to watch. Even Soran’s lighter moments, such as his conversations with Geordi and the Duras Sisters, have a distinct edge to them. McDowell makes it clear with every syllable and every movement that Soran doesn’t care about any of them or their goals, and would hurt or kill them in a heartbeat if they got in his way. He comes across as a powerful, intimidating adversary thanks to this no-holds-barred approach.

So that’s about all I have to say, really! I find Dr Soran to be one of Star Trek’s most compelling villains.

Star Trek: Generations is available to stream on Paramount+ in the United States, and is also available on Blu-ray and DVD. The Star Trek franchise – including Generations and all other properties mentioned above – is the copyright of ViacomCBS. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Star Trek: Discovery – eight “gravitational anomaly” theories

Wed 07.04.21Sun 13.11.22Dennis

Spoiler Warning: There are spoilers ahead for Star Trek: Discovery Seasons 1-3 and the teaser trailer for Season 4. Further spoilers are present for the following: Star Trek: Picard Season 1, Star Trek: The Next Generation, Star Trek: Generations, Star Trek: Voyager, and Star Trek: Enterprise.

Star Trek’s First Contact Day virtual event has given us an awful lot to digest! We got teasers for Picard Season 2, Lower Decks Season 2, Discovery Season 4, and more details about Prodigy. If you missed the event, I wrote up my impressions of everything we saw, and you can find that article by clicking or tapping here.

This time, I want to look at the teaser for Discovery’s impending fourth season in more depth, and in particular start making some guesses about what may be going on! The teaser was barely ninety seconds long, and with the show at least six months away it may be futile to speculate about pretty much anything! But that hasn’t stopped me in the past, so let’s jump in!

Sonequa Martin-Green plays Captain Michael Burnham in *Discovery*, and introduced the Season 4 teaser during the First Contact Day event.

My usual disclaimer applies: I don’t have any “insider information.” I’m not offering up these suggestions saying any are unequivocally true. This is nothing more than speculation from a fan – and a chance to spend some more time talking about Star Trek, which I absolutely adore.

In the run-up to Season 3 last year, I spent a lot of time speculating about the event that ultimately turned out to be the Burn. When we first heard its name I put together a list theorising a number of possible connections to past iterations of Star Trek – but as you know by now, none came to pass!

Michael Burnham in Season 3, trying to figure out what caused the Burn.

Discovery has had an on-off relationship with Star Trek’s broader canon. Season 1 sidestepped a lot of things, redesigning the Klingons, visiting the Mirror Universe years before Kirk’s first crossing, and fighting a major war. Season 2 tied itself much closer to canon, bringing in Captain Pike, Spock, and revisiting Talos IV. Season 3 shot forward into the future, and told a story that touched on past iterations of the franchise at points, but had an overall narrative that stood on its own two feet.

In short, trying to guess whether Season 4’s main storyline will be related to something we’ve seen in the past or not is a crapshoot. Maybe it will be, maybe it won’t. Regardless, if it’s going to be something brand-new then naturally the details become impossible to predict! So in this list I’m going to look at eight possibilities from Star Trek’s past that could explain what we saw in the teaser.

A determined-looking (and armoured) Burnham in the Season 4 teaser.

First of all, let’s explain what exactly we saw! Stamets described a “gravitational anomaly” that’s at least five light-years in diameter. This anomaly appears to be incredibly destructive, and if Burnham is correct, it’s appearing and disappearing at random. As a result, it could potentially strike any Federation or non-Federation world or starship without warning.

Assuming that this anomaly is the main problem facing Captain Burnham and her crew in Season 4, I’ve got a few ideas for what it could be, or what it may be related to. I quite like the idea of Discovery sticking with the “natural disaster” concept from Season 3. It worked well last time, and presenting the crew with a puzzle, mystery, or challenge that’s more scientific in nature than military could be wonderful to see. As long as such a storyline manages to avoid feeling either repetitive or anticlimactic, I think it works in principle.

Stamets in the Season 4 teaser. He told us about the “gravitational anomaly.”

One final point of note is that, due to disruption caused by the pandemic, Discovery Season 4 began filming back in November, well before Season 3 had finished airing – and crucially, before the creative team had time to process any feedback they were getting about the season’s themes and storylines. As a result of that, it may be the case that Season 4 doesn’t make as many changes from Season 3 as some fans would have wanted to see. But once again, that’s speculation on my part!

So let’s consider this “gravitational anomaly,” then. What could it be? What have we seen in past iterations of Star Trek that could potentially be involved? Will there be any tie-ins to other ongoing series, such as Picard, or will the show set up something we’ll see return in a future project, such as Strange New Worlds? Let’s jump into the list and see if we can make some reasonable guesses!

Number 1: The Nexus

The Nexus approaching the planet Veridian III.

When I first saw the teaser, my mind immediately went to the Nexus, the energy ribbon seen in Star Trek: Generations. The Nexus was large, more than large enough to engulf an entire planet, and while it may not have been light-years in diameter when we saw it in that film, it’s possible it grew… somehow! The Nexus was incredibly destructive, causing the destruction of two transport ships and seriously damaging the Enterprise-B, not unlike some of the damage suffered by the USS Discovery in the teaser.

There are two crucial points which made me think of the Nexus, though. The first is that the energy ribbon was said to contain a “gravimetric field,” which sounds an awful lot like Stamets’ “gravitational anomaly.” Both seem to be connected to gravity, and as we saw in the teaser, the USS Discovery appears to lose its artificial gravity at one point.

The Enterprise-B trying to manoeuvre inside the Nexus.

The second point I consider key to the Nexus being a possibility is that we already know it’s something that recurs. The Nexus returns to the Milky Way galaxy every 39.1 years (according to Data in Generations) and unless something major happened in the intervening centuries, this force of nature should still be present, periodically crossing through the galaxy.

At a couple of points in the teaser we saw members of Discovery’s crew looking dazed and confused, not unlike how Soran and Guinan appeared after being transported out of the Nexus by the crew of the Enterprise-B. Perhaps we can infer from their demeanours that they’re not quite sure where they are or what just happened – maybe that means they’ve just spent time inside the Nexus’ paradise-like realm.

Though the stated size of the anomaly relative to what we saw in Generations may count against it, I like the idea of revisiting the Nexus. Would Discovery bring aboard a Soran-like villain, someone hell-bent on getting to “paradise?” Maybe!

Number 2: The super-synths from Picard Season 1

It’s absolutely true that I also suggested the super-synths could’ve been the cause of last season’s disaster! But that doesn’t mean I’m done suggesting ways for this unnamed faction to reappear in Star Trek, especially considering that the teaser for Picard Season 2 suggested that series is moving away from them.

At the end of Picard Season 1, we learned that there is a race of super-synths that exist somewhere out in deep space – perhaps many thousands of light-years away from the Milky Way galaxy. They offered to come to the aid of any synths that ask for their help, though whether this offer was genuine or not was not clear – as indeed was very little about the faction!

Jean-Luc Picard managed to prevent the arrival of the super-synths, along with Soji.

Soji and Sutra, two of the synths from Coppelius, attempted to make contact with the super-synths, but despite opening a beacon and a portal to their base, Soji was ultimately convinced to shut it down and cut off her attempt to communicate. We thus learned precious little about who the super-synths are or what their objectives may be. They seemed menacing, and may harbour an anti-organic hatred that could make them diametrically opposed to the Federation.

We know that, in principle, this faction can open portals in space to allow for travel far faster than warp drive. Perhaps getting too close to one of their portals causes the kind of damage seen to the USS Discovery, and their portals may appear to be “gravitational anomalies” when detected on sensors. The super-synths clearly have a powerful understanding of gravity, such that they were literally able to move stars and create a stable eight-star octonary system. It’s thus at least possible that they use gravity or gravitational anomalies as some kind of weapon.

One thing that Picard Season 1 left unresolved was the fate of the super-synths. Having been contacted, were they now aware of the Milky Way and the Federation? Might they be hell-bent on attacking the Federation? If their offer of help wasn’t genuine, might they arrive to attack the synths who live in the Milky Way? There are a lot of unknowns, but it’s at least plausible that they could be involved. As I’ve said numerous times, finding a way for Picard and Discovery to work together, using similar themes, factions, or even characters would be fantastic and something truly worth doing. This may not be the way it happens… but it could be!

Number 3: A graviton ellipse

The USS Voyager once encountered a graviton ellipse.

The Voyager Season 6 episode One Small Step introduced the graviton ellipse, a fast-moving anomaly that can travel through subspace, normal space, and even other dimensions. The ellipse was drawn to electromagnetic energy – such as that emitted by spacecraft! One ellipse appeared in the Sol system in 2032, during an early manned mission to Mars, and “swallowed” the Ares IV ship. It later attempted to do the same to the USS Voyager.

The graviton ellipse was smaller than five light-years across, so again we have to contend with size. But there are points in its favour! Firstly, the ellipse was specifically drawn to spacecraft and other future technology. Though we didn’t see it attempt to “eat” anything on a planet’s surface, it stands to reason that similar technologies used in power generation may emit the same kind of electromagnetic radiation that an ellipse would be drawn to.

The Delta Flyer inside a graviton ellipse.

Secondly, the ellipse moved essentially at random, disappearing into subspace to reappear many thousands of light-years away. One single ellipse was known to have visited both the Alpha and Delta Quadrants. This seems to fit with what we know of Discovery’s “gravitational anomaly” – specifically the part Captain Burnham told us about its random, unpredictable appearances.

Finally, the graviton ellipse was known to cause damage to spacecraft, draining their power, as well as gravity-related disturbances in space. An encounter with an ellipse may not have destroyed Ares IV or the Delta Flyer, but they were known to be very difficult to escape from.

The drawbacks of this option are that graviton ellipses were relatively well-understood as early as the 24th Century, and with Discovery Season 4 set over 800 years later, it stands to reason that the Federation would be well-equipped to at least know what they’re up against if an ellipse seemed to be in the vicinity. Secondly, there was no indication that the ellipse would stay in one area, causing widespread damage in the way Discovery’s fourth season teaser suggested. Despite those negative points, however, I think it’s at least a possibility. Perhaps post-Burn technology has drawn an ellipse to Federation space, or it’s even possible that someone has found a way to weaponise one to attack the Federation.

Number 4: The Sphere-Builders from Enterprise

Discovery’s third season had a couple of interesting references to Enterprise, specifically the “Temporal Cold War” arc. One faction involved in the Temporal Cold War were the so-called Sphere-Builders: extradimensional beings who were attempting to convert part of the Milky Way galaxy to match their native realm so they could colonise it.

Though the time-travelling agent Daniels told Captain Archer that the Sphere-Builders were definitively defeated in the 26th Century, Daniels was from a time period before Discovery Season 4 is set, so he may not have been aware of any future involvement they had in galactic affairs!

Captain Archer looks at a projection of spheres in the Delphic Expanse.

The Sphere-Builders, as their name implies, built spheres. These moon-sized objects were spread throughout a region of space known as the Delphic Expanse, and emitted huge amounts of gravimetric energy, causing the entire region to become unstable and peppered with anomalies.

The spheres were also able to cloak, concealing them from 22nd Century human and Vulcan ships. The region of space a single sphere could affect was huge, and in the mid-22nd Century there was a large network of them, perhaps consisting of over 75 individual spheres. A hidden anomaly-generating piece of technology with a connection to the Temporal Wars? That sounds like something that could cause the problems afflicting Captain Burnham’s ship as seen in the teaser!

If a rogue sphere were on the loose, if the Sphere-Builders were returning, or if a single sphere had been left in the Milky Way, forgotten about since the 22nd or 26th Centuries, it stands to reason based on what we know of them that it could be the cause of the “gravitational anomaly.” This concept is potentially interesting; a leftover “doomsday weapon” unattended for centuries could make for a fun story. It would also be great to see a tie-in with Enterprise!

Number 5: Tyken’s Rift

Data explains how a Tyken’s Rift works to the crew of the Enterprise-D.

A Tyken’s Rift was mentioned in the Picard Season 1 episode Nepenthe, but before that one had been seen in more detail in The Next Generation fourth season episode Night Terrors. It was described as a rare spatial anomaly, one capable of encompassing entire star systems.

Unlike some of the other entries on this list, size isn’t a problem for a Tyken’s Rift! If a whole binary star system (i.e. a system with two stars) was able to fit inside, it’s more than possible such an anomaly could be five light-years in diameter!

A Tyken’s Rift was mentioned by Kestra Troi-Riker in *Picard* Season 1 last year.

The Enterprise-D wasn’t badly damaged by its encounter with the rift, but it was trapped inside and unable to escape. The Tyken’s Rift was also said to drain power, trapping ships inside. Perhaps the damage to the USS Discovery was not caused by the anomaly itself, but by pushing the ship past its limits trying to escape?

The drawback to a Tyken’s Rift being the cause of Discovery’s anomaly is twofold. Firstly, aside from a slow but steady power drain it didn’t seem to be harmful, and we saw nothing in Night Terrors to suggest this anomaly could or would cause catastrophic damage to a ship. And secondly, the Tyken’s Rift that the Enterprise-D encountered appeared to be stationary. It was even included on stellar maps, so it would be easily avoided.

I don’t think either of these points totally rule it out, and as one of the relatively few named anomalies in Star Trek that are massive enough, it seems fair to still include a Tyken’s Rift as a possibility.

Number 6: Species 8472 and Fluidic Space

One of Voyager’s most interesting adversaries was Species 8472, known only by their Borg designation! This powerful extradimensional faction were able to outwit even the Borg, fighting a very successful war against them for a time.

Species 8472 were native to a realm filled with an organic compound. Voyager’s crew named this region “fluidic space,” and it seemed as though Species 8472 based much of their technology on this organic material, including their spacecraft.

The USS Voyager being pulled toward a fluidic space portal.

The Borg became aware of fluidic space some time in the mid-late 24th Century, and attempted to travel there and assimilate it. But Species 8472 proved resistant to assimilation, and waged a war on the Borg, eventually travelling through to normal space to continue the fight. The intervention of the USS Voyager gave the Borg an advantage, but it seemed shortly thereafter as though the war ground to a stalemate.

Species 8472 made one further incursion, but after an agreement with the USS Voyager, agreed to return to their own dimension, content that the Federation proved no threat. However, that was 800 years ago! A lot can change, and perhaps Species 8472 have decided to make a return.

This would change the “natural disaster” concept, making it perhaps a precursor to invasion. Whether that would be good or not depends on how well it was executed – as well as your personal preferences for storylines! Given what we know of Species 8472 and their technology, I think it’s at least possible they could be the cause. Perhaps Stamets’ anomaly is some kind of gateway to fluidic space.

Number 7: The Borg

On the other side of the war with Species 8472 were the Borg! I also suggested Star Trek’s iconic cybernetic villains as a possible cause of the Burn last season, and despite seeing some ex-Borg in Picard Season 1, we haven’t really seen the faction proper in Star Trek since Enterprise Season 2 in 2003. Perhaps now is the right time?

Borg technology outpaced the Federation in the 24th Century by a considerable margin, and I’ve seen nothing to suggest that wouldn’t continue to be the case. The anomaly Stamets and Burnham discussed in the teaser may well be a natural phenomenon, but if it turns out to be a weapon, I can think of few other factions capable of creating and wielding one so massively powerful. Other Borg technology, such as their transwarp network, was known to have gravitational effects as well, so perhaps that’s another sliver of evidence.

The Borg were known to possess powerful technology.

This doesn’t really fit with the Borg’s usual modus operandi, and that is certainly a mark against it! But then again, the Borg are very adaptable, and travelling back in time several centuries is not exactly standard procedure for assimilating a planet either, yet that’s what they tried to do in First Contact! The gravitational anomaly could be the opening salvo of an attack; the artillery barrage to soften up the Federation before the Borg drones rush in to assimilate the survivors. The Borg certainly seem capable of doing something like this, and with the Federation having been on the back foot for more than a century as a result of the Burn, the Borg may have been using that time to build up and prepare for a large-scale invasion attempt.

We don’t know for sure if the Borg are still around in the 32nd Century, or if they still hope to one day conquer and assimilate the Federation. After more than 800 years, anything could have happened to them! However, it’s plausible that they still exist in similar form to how we last saw them.

The anomaly seemingly “attacking” both Federation and non-Federation targets could be indicative of an intelligence at work behind it. Space is huge after all, and the chances of it hitting a target as small as a starship, starbase, or planet regularly seems unlikely without some kind of explanation. Is it a force of nature drawn to energy, like the graviton ellipse mentioned above? Or is it a Borg weapon deliberately targeting Starfleet? The latter may seem unlikely, but it’s not impossible!

Number 8: The Burn

I certainly hope that Discovery Season 4 doesn’t just drop the Burn and proceed as though it never happened. After the cataclysm caused huge disruption to the Federation and the wider galaxy for over a century, I think we need to see a lot more of the consequences of that event before we even consider a “reset” of the Federation!

Perhaps what this anomaly will be is some kind of “mini-Burn,” affecting a smaller area. It could be a ripple effect of the original event, or otherwise connected to it in some way. Hopefully it won’t be caused by poor Su’Kal, who’s been through enough over the last 125 years! Though the Burn was presented as a unique event, perhaps it had lingering effects that are only just becoming known.

Season 4 needs to walk a line between acknowledging the events of Season 3 without dwelling on them the whole time. I understand that the writers and producers have other stories to tell in the 32nd Century beyond the Burn, but given how catastrophic it was I feel strongly that we need to see at least some of its lingering impact. Connecting the Burn to this new problem would create a degree of separation, allowing the season to go in new directions but without dropping the massive event entirely.

The Burn was a disaster which “caused dilithium to become inert,” and which caused active warp cores to explode. It wasn’t known to have gravitational effects, instead being some kind of shockwave that travelled through subspace. That could certainly count against it!

However, if this event were connected to the Burn in some other way, rather than being a direct result of Su’Kal’s outburst, perhaps it could be explained. I couldn’t even guess how such a connection could be made; it would be some kind of technobabble connecting the anomaly to dilithium and/or subspace. But it could be done, and it could be made to fit!

So that’s it. Eight very early theories about Discovery Season 4 and the mysterious “gravitational anomaly!”

Yes, Season 4 is scheduled to premiere this year!

As mentioned at the beginning, I quite like the idea of the series going down a “natural disaster” route, allowing the crew to solve a puzzle and unravel a mystery, rather than simply pitting them against a Federation-threatening adversary. Perhaps that will be what ultimately happens, but I think it’s at least possible we’re seeing some kind of attack or weapon as well. Time will tell!

The teaser was action-packed, and the new season looks to be in great shape. I think that there are possible downsides to another “huge galactic disaster” storyline so soon after resolving the Burn, in that it risks feeling tacked-on, derivative, or even anticlimactic if it’s an event smaller in scale. But despite that, if this anomaly is going to be one of the main storylines in Season 4, there’s a huge amount of potential.

Star Trek’s past didn’t provide the key to understanding the Burn last season. Will something we’ve seen before come into play in Season 4? Maybe!

Star Trek: Discovery Season 4 will debut on Paramount+ in the United States, and on Netflix in the United Kingdom and elsewhere, sometime later this year. Star Trek: Discovery Seasons 1-3 are available to stream now. The Star Trek franchise – including Discovery and all other properties mentioned above – is the copyright of ViacomCBS. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.

Ten games that I’d remaster (if I could)

Wed 26.08.20Sun 20.11.22Dennis

A few days ago I looked at the possibility of a remastered Mass Effect trilogy. While unconfirmed, this project has been rumoured to be in development for at least the last six months, and while I could certainly consider the argument that we don’t need a remaster less than a decade after the trilogy wrapped up, it got me thinking about games that I really would like to see given a proper update for 2020.

When it came to choosing titles, I excluded anything from the last couple of console generations, as those are new enough – in my opinion – to hold up reasonably well in 2020. I excluded titles that have been remastered already, as well as one title (Super Mario 64) that has been the subject of intense speculation regarding a potential upcoming remaster. I considered a number of titles from the 1980s and early ’90s, but despite some good contenders, the titles I ultimately chose are all from the mid ’90s through to the mid 2000s. Remember that these are just my opinions; the list is subjective.

This list is just a fantasy. Some of the games below may one day be remastered, but others are so obscure that I may be one of only a handful of people who knew they existed even when they were new! So don’t get excited at the prospect of an impending remaster; if you must play a title on this list… I dunno. Try eBay?

Number 1: Star Trek: Generations (PC, 1997)

When it comes to naming my “all-time favourite” game, I struggle. There are so many good video games that I’ve played over the years, and what I enjoy playing changes with my mood. That said, the PC game Star Trek: Generations has to be a contender. Part Doom-clone, part puzzle game, part tactical ship-to-ship combat game, featuring fully-voiced characters and some great sequences set in stellar cartography that I don’t even know how to categorise, Generations was a fantastic and incredibly well-rounded experience. It’s such a shame that it released way too late – several years after the film – and was overlooked by even the hardest of hardcore Trekkies.

The main part of the game is a series of Doom-inspired first-person missions to various planets. Generations took a randomised approach – there are a number of planets that the villainous Dr Soran can visit, and which ones he travels to differs with each playthrough. All of the main characters from The Next Generation have their own missions, and the final act of the game lets players take on the role of Kirk. The story sticks to the film in the beginning and near the end, but diverges greatly in the middle during some of the away missions. It’s a fantastic title, and a few years ago I was able to track down a copy on eBay. I’ve been intending to replay it but haven’t got around to doing so yet.

Number 2: Jet Force Gemini (Nintendo 64, 1999)

Jet Force Gemini was a Nintendo 64 exclusive just before the turn of the millennium, and it was a fun sci-fi adventure in an original setting. The game gave players three characters to control: twins Juno and Vela, and their dog Lupus. An action/adventure title with some basic 3D platforming sections, the game had a slightly over-the-top story that involved saving teddy bear-like creatures and defeating a nefarious villain. Considering how many sequels and franchises exist right now in all forms of entertainment, Jet Force Gemini could offer something different – or at least something most players in 2020 haven’t experienced before!

Developed by Rare, the game had weapons that could be upgraded as well as an open level design that was comparable to other Nintendo 64 titles at the time. Though it was included in the Rare Replay compilation a few years ago, no remaster – or even a sequel – has been attempted, which is a shame. If a title like Jet Force Gemini were to launch today it would undoubtedly spawn a whole franchise!

Number 3: Knights of the Old Republic I & II (PC & Xbox, 2003-04)

I talked about Knights of the Old Republic a few times during my playthrough of Jedi: Fallen Order, because some aspects of the two titles are comparable. I’ve made no secret of the fact that I didn’t enjoy the Star Wars prequels, and the first two films were especially bad. But in the aftermath of Attack of the Clones I got to have two of my favourite ever Star Wars experiences – these two games.

With all the discussion around a Mass Effect remaster, Bioware’s Star Wars game hasn’t been mentioned. But it should be – both Knights of the Old Republic and its Obsidian-developed sequel are phenomenal. The Star Wars franchise has struggled to break away from its original trilogy and characters for a long time, but Knights of the Old Republic took a genuinely original and interesting setting and told a story that took place millennia before the films. These games did wonders for the Star Wars brand at a time when two crap films had tarnished it, and playing them again but with the enhanced graphics of a title like Jedi: Fallen Order would be amazing.

(A KOTOR remake was subsequently announced in 2021!)

Number 4: Blue Stinger (Dreamcast, 1999)

Protagonist Eliot explores Dinosaur Island.

The only Dreamcast exclusive on this list was a bargain-bin find even at the time it was released! But that’s such a shame, because if you can look past the hammy dialogue and silly premise there’s a fun game hiding just beneath the surface. Blue Stinger didn’t pretend to take itself too seriously. Its dinosaurs-from-space apocalypse setting precluded that! But not every game – or every film – has to be dark and gritty; there’s plenty of room in the gaming realm for titles like this.

What I liked most about Blue Stinger was the fact that the game offered a lot of customisation. Different outfits and different weapons for the multiple playable characters all contributed to making my playthrough feel unique, that I was having an adventure all my own. Few games at the time offered that kind of experience, and I appreciated it.

Number 5: Arx Fatalis (PC & Xbox, 2002)

After playing and loving The Elder Scrolls III: Morrowind on the original Xbox, I was looking for another fantasy-inspired roleplaying game to play. There were a few such titles around, but after finding Arx Fatalis and seeing little more than the box art I was convinced it was going to be the next big thing. The PC version of the game – which I didn’t play – is generally considered to be better, as its spellcasting system involves using the mouse to draw symbols in the air. That extra sense of immersion must have felt great!

Arx Fatalis’ underground setting was amazing, with towns and settlements built into caverns, and I had a great time exploring the dungeons and caves of this unique world. There was a decent amount of choice, both in what quests I could take on and how to go about completing them. While Arx Fatalis arguably offered less than Morrowind, it was a solid and decent title nevertheless. Sadly it didn’t sell very well, partly due to being overshadowed by Morrowind, and remains in relative obscurity.

Number 6: Star Trek: The Next Generation – Future’s Past (SNES & Sega Mega Drive, 1994)

Riker, Worf, and Picard on the bridge of the Enterprise-D.

You knew that there was going to be at least one more Star Trek title on the list, right? Future’s Past (or Echoes from the Past if you got the Sega Mega Drive version) plays out like an extended episode of The Next Generation in a lot of ways, and there are things to do on the bridge of the Enterprise-D as well as on away missions. A team of up to four crew members – including both redshirts and major characters – can be assembled for away missions, and different combinations of characters can yield different results.

The away missions take a top-down view, making the game a kind of real-time tactics game as well as being a fun Star Trek adventure. Some of the game’s systems are quite in-depth for a mid ’90s title, and performing tasks like navigating the ship from one star system to another actually made it feel like you were a crewman on the Enterprise-D!

Number 7: FIFA 97 (Multiplatform, 1996)

Though the FIFA series had been running for three years by the time FIFA 97 arrived on the scene, it was the first iteration that I owned. FIFA 95 had introduced club teams after the first entry only featured national sides, but it was only available on the Sega Mega Drive. FIFA 96 was the first truly multiplatform release, and after the excitement of the 1996 European championships in England I was craving a football game to play!

*FIFA 97* had a choice of indoor or outdoor stadia to play in!

Nostalgia is big in entertainment at the moment, as people look back fondly on the past. What could be absolutely fascinating to see, as a football fan, is a recreation of the various leagues and divisions as they were in the 1996-97 season, but with the graphics of modern FIFA titles. I think such a game would play on the nostalgia that football fans have for the players, stadia, and kits of their younger days, and if it were successful, there could even be a whole range of legacy FIFA titles going all the way back to the inception of competitive football leagues! Can you imagine a FIFA game set in the 1890s featuring clubs like Northwich Victoria, Glossop North End, and Small Heath? Maybe it’s just because I’m a history buff but I’d love something like that!

Number 8: Pirates of the Caribbean (PC & Xbox, 2003)

Ship combat in *Pirates of the Caribbean* was great.

Despite the name, 2003’s Pirates of the Caribbean has very little connection to the film series – the first iteration of which was released the same year. Though the Black Pearl makes an appearance, the story is really that of Captain Nathaniel Hawk, an original character. Hawk must put together a crew and then can sail across several islands in a shrunk-down map based on the Caribbean. There’s a main quest involving a war between England and France, and a number of smaller side-quests too.

The player character – Captain Nathaniel Hawk.

The popularity of titles like Sea of Thieves and Assassin’s Creed IV shows that gamers love a good pirate-themed title, and I think the under-appreciated Pirates of the Caribbean could work brilliantly in 2020. It had a fun and engaging story, and was a title that allowed a decent amount of player choice.

Number 9: Donkey Kong 64 (Nintendo 64, 1999)

As I mentioned at the beginning, Super Mario 64 has been rumoured to be the target of a remaster. But the Nintendo 64 also saw the first 3D adventures of that other great Nintendo character – Donkey Kong. Where the Donkey Kong Country games on the SNES had introduced Diddy Kong and a couple of others, Donkey Kong 64 kicked things into high gear by having five playable characters.

The game is similar to both the aformentioned Super Mario 64 in terms of its 3D platforming as well as titles like Banjo-Kazooie, which was also developed by Rare. It had a multiplayer mode, well-designed and diverse levels, and while the plot was pretty basic it was a lot of fun. The game was re-released on the Wii U as a download title, but wasn’t remastered.

Number 10: Max Payne (PC, Xbox, and PlayStation 2, 2001)

Despite receiving two sequels and a feature film adaptation, no attempt has yet been made to remaster the original Max Payne. I’ve often talked about how Shenmue on the Dreamcast was my first experience with a game that felt genuinely cinematic – well Max Payne was the second such game I played. Gaming before the turn of the millennium was a lot of fun, but as an art form and entertainment medium, it hadn’t fully hit its stride. Many games had stories which were childish, over-the-top, or just silly; Max Payne was a classic detective/noir adventure that would have been just as at home on the big screen.

The story and even 95% of the gameplay would need absolutely no adapting; this is one game that just needs to be updated using today’s better graphics! The story is what makes Max Payne worth playing. Its sequels were fine, but nothing can top the original experience. Though the game’s signature “bullet time” has since been reused in many other titles in the years since its release, the story underneath the gameplay is still one that players today could enjoy.

So that’s it. Ten games that I’d remaster if I could. In the years since I got my first home console in the early 1990s – a SNES – I’ve been lucky to play many different games on a range of platforms. These are just a few that I’d love to remaster – if I had a studio, an unlimited budget, and a willingness to lose money!

This has been a fun topic, and it’s one I may revisit in future. I had at least ten more titles lined up that could have made the list, and with so many great games from the past, there’s no shortage of options! It was great fun to talk about some games of yesteryear that I enjoyed during the 1990s and early 2000s.

All titles listed above are the copyright of their respective developers, studios, and/or publishers. Some screenshots courtesy of IGDB. This article contains the thoughts and opinions of one person only and is not intended to cause any offence.