Somewhere between the comfort of canon and the freedom of consequence, a new Star Trek: Voyager game is trying to find its footing. Developer Gamexcite released a demo this week that places players in command of a stranded starship 70,000 light-years from home, promising that every choice — who survives, who is sacrificed, whether to honor duty or seize escape — will carry real weight. The survival mechanics suggest a genuinely thoughtful design, but the tutorial's tight grip on the story raises an older question that haunts every licensed game: does the fiction liberate the player, or does it
Star Trek: Voyager Game Demo Shows Promise But Lacks Real Choice
The narrative path remains largely the same.
So the core idea—managing Voyager's survival while making choices that reshape the story—that's genuinely interesting. Why does the demo feel so constrained?
Because it's following "Caretaker" almost beat-for-beat. The tutorial is designed to teach you the mechanics by recreating the pilot episode. You're learning how to scan for resources, manage crew morale, assign away teams. The narrative is the vehicle for the tutorial, not the other way around.
But here's the thing: they could have taught those mechanics in a tutorial that didn't pretend to offer choice. If the demo is going to show branching paths—save Chakotay or Torres, destroy the array or use it to go home—it should show that those branches actually lead somewhere different. Instead, you get the same story either way.
Right. The only real consequence is which crew members become available afterward. Harry goes missing if you save Chakotay; Paris goes missing if you save B'Ellana. Everything else stays the same.
So when you tried to be a terrible captain—sending unprepared people on dangerous missions, letting morale tank—what happened?
The game shut down the away mission and asked me to reload. There are hard fail states: run out of fuel, morale drops too far, and you're done. But it won't let you actually fail in a way that changes the narrative.
That's the real problem. A game about choice needs to let you fail in interesting ways. If every failure just bounces you back to a save point, you're not making decisions—you're solving a puzzle with a predetermined solution.
Did anything feel genuinely consequential?
One moment. When I chose to use the array to send Voyager home instead of destroying it, Chakotay confronts you for abandoning the Ocampa. You can arrest your Maquis allies or threaten Tom Paris. That felt like it had weight.
But did it actually change what happens next? Or does the demo just end there?
The demo ends. You don't see the ripple effects. So you can't tell if that moment actually matters or if it's just flavor text on the way to the same ending.
What about the resource management? That seemed to work.
That's the strongest part. Balancing power allocation, crew morale, deciding where to spend limited supplies—there's real tension there. It's genuinely engaging.
But it's separate from the narrative choice system. You can have a great survival game and a broken choice system in the same box. The question is whether they'll integrate them in the full game or keep them as two different experiences.
Le Pouls
- The demo's core tension is immediate and compelling — Voyager is crippled, resources are scarce, and every decision about crew, power, and supplies feels like it could tip the ship toward survival or collapse.
- But the tutorial's insistence on recreating the pilot episode beat-for-beat exposes the seams: choices that feel meaningful resolve into the same narrative destination regardless of what you decide.
- A deliberate attempt to play recklessly — tanking morale, sending unqualified crew into danger, choosing to abandon the Ocampa — was met not with cascading consequences but a polite prompt to reload the save.
- One genuinely dark moment breaks through when you choose to use the array to go home, triggering a confrontation with Chakotay that hints at the morally complex game this could become.
- Developer Gamexcite promises that post-tutorial play will allow truly consequential decisions — including whether Tuvix lives — but the demo offers no evidence yet of whether those choices will reshape the journey or merely redecorate it.
Somewhere between the comfort of canon and the freedom of consequence, a new Star Trek: Voyager game is trying to find its footing. Developer Gamexcite released a demo this week that places players in command of a stranded starship 70,000 light-years from home, promising that every choice — who survives, who is sacrificed, whether to honor duty or seize escape — will carry real weight. The survival mechanics suggest a genuinely thoughtful design, but the tutorial's tight grip on the story raises an older question that haunts every licensed game: does the fiction liberate the player, or does it simply dress up a predetermined path in familiar clothes?
The premise is immediately arresting: take command of Voyager after it's hurled 70,000 light-years into unknown space, and let every decision — who goes on away missions, how power is rationed, whether to fight or negotiate — ripple outward through the story. When Gamexcite released a demo during Steam Next Fest this week, that promise felt within reach. What the opening hours actually deliver is a game caught between two competing identities: a survival simulator with genuine teeth, and a narrative experience that, so far, feels more like following a script than authoring one.
The tutorial recreates the events of the pilot episode "Caretaker" with careful fidelity — the Delta Quadrant arrival, the mysterious array, the Ocampa underground, the Kazon, and the central dilemma of whether to destroy the array or use it to jump home. Layered beneath the story are the game's real mechanics: scanning for resources, managing ship systems, balancing crew morale, researching technology, and slowly rebuilding after the catastrophic jump. The interface is functional and LCARS-faithful, leaning on spreadsheet-style management over cinematic spectacle. It works, but it's skeletal.
A second playthrough designed to stress-test the game's flexibility — deliberately neglecting maintenance, starving crew morale, sending the least-qualified officers into danger — revealed the limits quickly. When an away mission collapsed into failure, the game offered a reload screen rather than a consequence. The narrative wouldn't break. A third attempt, choosing to use the array and abandon the Ocampa, produced the demo's most genuinely affecting moment: Chakotay confronting you for the betrayal, a small window into what moral weight this game could carry. But even that sequence ended with a prompt to load a save rather than pressing forward into the aftermath.
The resource management layer is where the game earns its keep — the tension of survival logistics is real and absorbing. Space combat, by contrast, feels thin and peripheral. The deeper uncertainty is whether the narrative system will ever truly open up. Gamexcite promises future decisions with real stakes, but the demo leaves the central question unanswered: once the tutorial ends, will the game trust you to break the premise, or will it keep steering you gently back toward the familiar shore?
The premise hooked immediately: take command of the Voyager after it tumbles 70,000 light-years into unknown space, and every decision—who you send on away missions, how you allocate power and supplies, whether you fight or negotiate—ripples through the story. When developer Gamexcite released a demo this week as part of Steam Next Fest, the promise seemed within reach. But the opening hours reveal a game caught between two competing visions: a genuinely interesting survival simulator and a narrative experience that, at least so far, feels more like following a script than writing one.
The demo walks you through the tutorial by essentially recreating the events of Voyager's pilot episode, "Caretaker." You get pulled into the Delta Quadrant, encounter the mysterious array and its strange inhabitants, discover the underground Ocampa civilization, run into the Kazon, and face the central choice: destroy the array to prevent the Kazon from seizing it, or use it to jump home to the Alpha Quadrant. Along the way, the game layers in its core mechanics—scanning planets for resources, managing ship systems from power capacity to crew morale, researching new technology, and slowly clearing debris and rebuilding facilities after the catastrophic jump that disabled the vessel. The interface is functional rather than cinematic, relying on LCARS-style windows and spreadsheet-like management rather than lavish set pieces. There's no voiceover dialogue yet, which gives the whole thing a skeletal quality.
On the first playthrough, staying faithful to the original episode felt natural. The game subtly encourages this by giving characters who actually went on those missions in the show the right stats and expertise to succeed at skill checks. When you choose which crew members to send on away missions or assign to ship stations, the mechanics reward you for matching the show's canon. When presented with choices—rescue Chakotay or Torres from the array's lab, destroy the array or use it to go home—you make them. But here's where the railroads become visible: the demo ends right after that final choice, so you never see how your decisions actually reshape what comes next. The one branching point about who you try to save simply determines which crew members become available for future assignments. Harry goes missing if you save Chakotay and Tuvok; Paris goes missing if you save B'Ellana and Tuvok instead. The narrative path remains largely the same.
To test the game's actual flexibility, a second playthrough attempted something different: being the worst Captain Janeway imaginable. Deliberately neglecting ship maintenance beyond bare minimum power and fuel, denying the crew proper rations to tank morale, refusing to build rest quarters, sending the least-equipped people on away missions, and making them take high-risk choices designed to fail. When B'Ellana, Harry, and Neelix beamed down to Ocampa, got caught in a desert storm, made aggressive contact with the Kazon, and bungled a tactical retreat, the question became: would the game actually let someone die? Would failure cascade into real consequences?
Instead, an "Away Mission Failed" screen appeared, asking to reload the save. The game had a hard stop for failure states—not enough fuel to run the warp core, morale dropping too far—but it wouldn't let the narrative break. On a third attempt, playing less overtly self-destructive but still choosing to use the array to send Voyager home, the game delivered one genuinely dark moment: Chakotay confronts you for betraying his trust and abandoning the Ocampa. You can then arrest your Maquis allies or suggest Tom Paris is heading back to his penal colony. It's a small window into what the game could be. But even that sequence ends with the demo asking you to load a save and try again, rather than continuing forward to show how that choice echoes through the rest of the story.
The resource management layer is genuinely compelling—balancing survival needs against crew welfare, deciding where to allocate limited supplies and personnel, watching systems degrade and rebuild. Space combat, by contrast, feels thin: you pick which enemy subsystem to target and occasionally trigger a cooldown ability. The real tension lives in the spreadsheet, not the firefight. But the narrative choice system, at least in this tutorial phase, feels more like a series of branching paths that all lead to the same destination than a genuine sandbox where your decisions reshape Voyager's journey. The game promises future choices like letting Tuvix live or using Borg technology to shorten the trip home, but from this slice of the game, it's impossible to know whether those decisions will actually matter or simply unlock different flavor text on the way to a predetermined outcome.
What emerges is a game with real potential in its survival mechanics but genuine uncertainty about whether it will actually let you make Voyager's journey your own. The demo is explicitly a tutorial, so some hand-holding is expected. But it leaves the central question unanswered: once the training wheels come off, will Across the Unknown trust you to break the show's premise, or will it keep steering you back toward the familiar path?
Citations marquantes
Chakotay confronts you for betraying his trust and abandoning the Ocampa— In-game dialogue when choosing to use the array to send Voyager home