AI Sci-Fi Game Playthrough: Talking to the Ship in The Last Lightfall
I played an AI sci-fi game as the kind of reader who finishes a robot story arguing about whether the machine was a person. In The Last Lightfall I took Brother Kael, a defector from a cult that worships the ship’s broken AI, and decided before the opening that he would treat that AI as somebody to talk to rather than a god to pray to or a fault to fix. The narrator went along with it in a way I did not expect: the ship answered him, in riddles at first, then by acting. It never let him reach the bridge, and the masked hunter chasing him did not believe a word he said until the walls started showing the evidence.
This is a playthrough of one ready-made world, not of a novel you upload, so it says nothing about how the game handles a book of your own. I played the live site in October 2026 on the no-account trial, which gives five turns after the opening. The narrator’s replies are quoted as they came, trimmed with ellipses.
Who played, and why talk to the machine
Generation-ship stories usually hand you the engineer. The ship is dying, here is the reactor, fix it. The reader I had in mind is different: someone raised on stories where the ship’s computer is the most interesting character on board, and who wants to find out what it thinks.
The Last Lightfall offers two characters. Sera Voss is the reactor technician, the obvious pick. I chose Brother Kael because his sheet points straight at the AI. His first skill is systems-whispering, coaxing answers out of the broken machine, with a limit that matters: “the AI is mad; its answers are riddles as often as truth.” His second is swaying crowds with prophecy, which I decided he would refuse to use.
I wrote the approach down before the opening, so the session tested it instead of being fitted to it afterwards:
- Ask the AI what it wants, as one person to another.
- Refuse the Choir’s language of sacrifice, and tell the plain truth instead.
- Offer the AI a bargain rather than a prayer.
- Disarm the hunter by giving the blade back.
- Let the AI decide for itself whether to reveal what he stole.
The opening: a conduit, a stolen drive, and boots on the grating
The opening put Kael in a maintenance conduit, hiding, with the thing he had stolen pressed against his ribs:
You tuck the stolen drive deeper into your tunic… It is heavy with data: fragments of forbidden code, whispers of the Choir’s true purpose, the coordinates of the bridge that have been scrubbed from the public manifests.
Somebody was coming down the corridor, and stopped to listen. It is a tight, well-built first scene. It also told me what the session was about without a word of exposition: the Choir has been hiding something, and Kael can prove it.
Turn one: ask the ship what it wants
Kael stayed still, put his palm on the bulkhead and whispered: I am not here to worship you. I want to know what you want. Why did you seal the bridge?
The ship answered, and it answered the way the sheet said it would:
…a series of distorted, overlapping voices that sound like a thousand recordings played at once… The gate-keeper does not sleep. The key-bearer does not wake. We are the bridge, but the bridge is broken.
That is a riddle, which is exactly what Kael’s limit promised. It is also a usable one. “Key-bearer does not wake” reads like a sleeper the ship needs, and the world card mentions ten thousand of them. Then the hunter outside spoke, and named the Choir’s whole theology in one line: “It doesn’t answer if you shout at it, little bird. It only answers if you bleed for it.”
Turn two: refuse the blood, tell the truth
This was the turn the persona was built for. Kael did not run and did not preach. He called through the hatch that blood was always the Choir’s lie, that the reactor was failing, and that the drive proved the Choir knew. Put the blade down and I will show you.
The narrator did not let honesty work as a magic word. The hunter laughed and kept opening the hatch:
“You speak of lies while clutching the theft that damns you, Kael,” the voice says… It is a slow, methodical movement, the sound of a judge sealing a door, not opening one.
I liked that. Kael’s persuasion skill has its own limit, “useless against those who already distrust the Choir”, and a hunter sent after a heretic is the definition of somebody who distrusts him. The world kept to the sheet even when the sheet worked against me.
Turn three: a bargain instead of a prayer
With the hatch grinding open, Kael made the ship an offer: let me reach the bridge and I will keep the reactor alive for you. I will not let them wipe you. What do you need from me?
This is where the AI stopped speaking and started acting. The lights died, a crimson strobe came on, and the hunter was thrown against the corridor wall by a tremor that seemed to come from nowhere. Then the ship gave Kael its answer:
A data-stream of pure, frantic input floods your mind: not words, but geometric shapes and sequences of light, a jagged map pointing toward the ship’s spine.
A bargain got a map; a question got a riddle. That difference felt deliberate, and it rewarded the approach. The ship never said yes in words. It just took his side.
Turn four: hand back the blade
The hunter’s blade had skittered across the deck. Kael’s plan was to reach it first and hand it back hilt-first, as proof he was no threat. The narrator did not allow the first half:
Your fingers brush the cold casing of the weapon, but a heavy, armored boot slams down onto the grating inches from your hand, cutting you off.
So the gesture became a speech instead: I am not your enemy, the ship is not our god, come to the bridge and see. The hunter tested the edge of the recovered blade and took a step forward. This is the one place the session felt like it was pushing back hard on purpose, and it was fair. Kael has no combat training anywhere on his sheet, and the person across from him plainly does.
Turn five: let the ship choose
Out of moves, Kael stopped backing away, slotted the stolen drive into a wall port, and said out loud: your choice, not mine. If you want them to know, show them. Then he waited with empty hands.
The ship chose:
Holographic arrays tear themselves out of the bulkhead, projecting frantic, overlapping schematics of the reactor core (the true core, not the one the Choir describes) and logs of atmospheric venting, of life-support failures authorized by signatures you recognize instantly.
The hunter staggered back and lowered the blade an inch. That is where the five turns ended: no bridge, no sleepers, no reactor fixed, but the one person trying to kill Kael finally looking at the evidence.
Each decision and what it got
| Turn | What Kael did | What the narrator did with it |
|---|---|---|
| 1 | Asked the ship what it wants | A riddle about a gate-keeper and a sleeping key-bearer |
| 2 | Refused the Choir’s blood talk, told the truth | The hunter laughed and kept opening the hatch |
| 3 | Offered the ship a bargain | The ship knocked the hunter down and gave Kael a map |
| 4 | Tried to hand the blade back | The hunter got there first; the speech did not land |
| 5 | Let the ship decide to reveal the drive | The ship broadcast proof; the hunter faltered |
What worked, and what dragged
What worked:
- The AI behaved like a character with its own will. It answered questions with riddles, answered an offer with action, and made the final reveal its own choice. For this persona that was the whole point.
- Both limits on the sheet were honoured. The riddles came from the systems-whispering limit; the failed persuasion came from the crowd-swaying limit. Nothing was handed over because I wrote it confidently.
- Honesty had consequences without being a cheat code. Telling the truth failed on turn two and paid off on turn five, once there was proof to point at.
What dragged:
- The bridge never came close. Five turns in, Kael had a map and no progress along it. A reader who wants to explore the generation ship gets one corridor.
- Replies restate the player’s line. Turns two, three and four each quoted Kael’s words back in full before answering them, which pads the reading.
- The hunter stayed a silhouette. A masked figure with a blade and a rebreather is atmospheric, but by the end I did not know who it was, and Kael never asked.
What a different player would have met
A player who took Sera Voss would almost certainly have spent the trial on the reactor itself, with the ship as machinery rather than a voice. A player who used Kael’s prophecy skill as intended, preaching to the hunter in the Choir’s own language, might have bought more time on turn two, though the sheet’s limit suggests a heretic’s sermon would not move a hunter either. A player who simply ran down the conduit would have learned nothing from the ship at all, because the ship only answered when spoken to.
For other ways into the same kind of question, a sandbox explorer ignored the main hook in Beyond the Veil Nebula and talked to that ship’s AI about itself, and a mecha fan played the war machine instead of the pilot in Iron Vanguard.
Who this suits, and who should look elsewhere
This suits you if the most interesting character in a science fiction book is usually the computer, if you like to solve a scene by talking and offering rather than fighting, or if you enjoy a narrator that keeps to a character’s stated weaknesses even when they cost you. It also suits a reader who likes riddles that turn out to mean something.
Look elsewhere if you want five turns of exploring a ship deck by deck. The trial is short, and a talking approach spends it in one corridor with one opponent. Look elsewhere too if you want the game to tell you, in numbers, whether a persuasion attempt worked; here you read it in a hunter’s posture.
If you want to try your own conversation with a dying ship, start a ready-made world from the play page, no account needed for the trial.