A Long Way to the Nearest Star

In A Long Way to the Nearest Star, you play as a criminal on the run after an almost unsuccessful heist. You escaped with the goods but damaged your spacecraft along the way, forcing you to find a place to hide and make repairs. Luckily, you stumble across a seemingly abandoned research vessel that may solve your predicament.

Gameplay
After a brief intro, the gameplay begins in the landing bay of the mysterious ship where you discover that you are not alone. Your presence caught the attention of the ship’s AI, Solis, who communicates through terminal screens placed throughout the ship. Solis is eager to help but clearly guarded about the circumstances surrounding its own ship. The player is reliant on Solis to help them navigate the ship but is also compelled to find ways to sneak around the system.

The story and characters are worth about three stars, but the overall game gets four because of its puzzles and how those puzzles are implemented in a choice-based format. This is a puzzle-intensive Twine game with free range of movement. You have access to a fairly large ship, and the game lets you wander through it almost like you would if it were a parser game. This approach may appeal to some players. Some of the gameplay mechanics are quite clever. I especially liked how the game allows you to program the janitor bot to go to a location and then automatically follow it. Useful for puzzles while reducing travel time.

There is a lot of in-game guidance. In your inventory is a notes section giving you an overview of what you have learned, and if you take a break in your own ship the game gives you some suggestions of what to do. The author also has hints cleverly formatted into a Twine piece included separately with the game. All of this was nicely done, and I felt it was worth a mention.

The author gets some bonus points for worldbuilding. The terminal in the research lab allows you to look up planets in a digital encyclopedia. When the game ends, you are presented with the statistics of your playthrough which includes how many planets you researched. That alone was enough for me to replay the game just to comb through to find any planet names that I could punch into the encyclopedia. In case you are interested, I found 11 planet names.

Story
The story retains a suspenseful and intriguing quality. The gist (I do not consider this part to be a spoiler since we know this at the start of the gameplay) is that there was a collision with the ship that caused toxic gas to enter the ship, killing everyone onboard. We learn this from Solis, (Spoiler - click to show) but the player knows right away that Solis is not being entirely truthful. It is not a matter of discovering whether Solis is hiding something. It is a matter of finding what it is hiding. Entering the medical bay was kind of chilling. On top of that, it has six endings which encourage replays.

At the end of the game there is this abrupt plot twist that it failed to pull off. This sudden twist, mega spoilers by the way, occurs (Spoiler - click to show) when you learn that Berthold was behind it all. It turns out Solis did not kill Trill, but Berthold did and made Solis think otherwise. That part had some decent backing. But then there is ambiguous explanation on the other ways Berthold potentially interfered, followed by an avalanche of speculation of why he attempted sabotage. You show Solis the captain’s real data pad, and the game rushes to explain everything in one swoop. Yet, it does not even clarify everything. The game says, yeah, Solis gassed the crew, but it also did not gas the crew. Any uncertainties are blamed on glitches. It seemed flimsy in comparison to the rest of the story which had been carefully constructed.

Characters
The player can choose the protagonist’s (fake) name and their brief cover story, but otherwise the game is hesitant to give out details about the protagonist since they are on the run. You can still get to know the PC in subtle ways, such as reprogramming the food options in food synthesizer and eat them. This gives you a look into the protagonist’s previous experiences. Some are quite interesting.

I did not particularly care about the characters which surprised me (This game is almost NPC-less. By "characters" I mean Solis, the protagonist, and the janitor bot. Okay, the janitor bot was nice). If anything, I was more interested in the crew (Spoiler - click to show) which is a shame since they are dead. We only get to know them through video recordings and see their corpses in the medical bay. They seemed to be a unique blend of species and cultures.

AI characters can be a lot of fun regardless of if they are villainous or friendly. I like it when such characters engage with the player, and Solis does just that. But for some reason, Solis did not have much of an impact on me. I find it hard to pinpoint why.

Despite the (Spoiler - click to show) ominous feeling we get from the “account” of what happened to the crew, Solis does seem genuinely interested about the player. The early gameplay has some cliché “gee, hello there, organic life form,” banter that stretches on a bit. Other times the exchange is more meaningful. I like how discussions tend to incorporate mentions of planets or civilizations that give you a broader sense of the story’s world.

Still, the character lacked in dimension. Remember how I said the game gives you a statistical report of your playthrough? It includes Solis' attitude towards the player which I thought was interesting because it made me reevaluate some of my choices to see how they influenced interactions.

Visuals
Generally, the game uses a black screen and links clearly indicated with light grey rounded boxes. This basic look is offset by some stylization that adds some flair.

For Solis’ dialog, visuals are used to create the impression of looking at a terminal screen, featuring a rounded black textbox with a thick border and green text. This was a simple but effective look. Similarly, when it comes to reading data pads the game puts the text in colour-tinted boxes with rounded corners to simulate the feel of reading off a tablet. All of this was creative and eye-catching.

Final thoughts
Overall, it is a quality game. It was not as potent as I expected, but the gameplay is solid and will likely be appreciated by players. This would be a good choice if you are someone who likes Twine games with a little more technicality because it has plenty of puzzles and freedom of movement to interact with the setting. Its IFComp submission says that its playtime is about two hours which is about accurate. Give it a shot.

If you enjoyed A Long Way to the Nearest Star, you may like Lux, another puzzle intensive sci-fi Twine game where the player heavily relies on the guidance of a mainframe AI as they navigate a nearly NCP-less setting in the aftermath of an unknown disaster. It is also an IFComp game from a few years back.