Saros's Endings: The Road to King and the Second Time You Can't Play the Same Way Again
The first time that Saros It leaves you facing the King, everything seems pretty clear. You've reached Yellow Shore, you've survived the strangest part of the journey, and you have a boss in front of you that must fall. You defeat him. The possibility of finishing him off opens up. And, if you've been playing with the usual logic of almost any action adventureYou do it without overthinking it.
The problem is that Saros It saves the twist for later. It doesn't stop you with a warning or explain that you're agreeing to something bigger than a boss execution. It lets you move on. Only later, when the game returns you to Carcosa with other scenes unfolding—Kayla, Nitya, Kiira, Sebastian Torres, the Holocache, the Banyan Tree—does that same gesture begin to feel less clean. As if the first ending had been less a victory than a test that Arjun Devraj failed to decipher.
This guide maintains a practical approach, because it's necessary to know what to do to see both endings. But it's best not to separate the reading steps too much. In SarosThe order matters. First you see Arjun fall into the logic of the Yellow Shore; then you return to the King with other information, another discomfort, and an option that wasn't available before.
Editorial note: This review works with the annotated version of Saros as of June 2026. If Housemarque or Sony change requirements, scenes, or names in a later update, the practical route should be reviewed. The background reading is supported by the elements that organize the closing: Arjun Devraj, Nitya Chandran, Kayla, Kiira, Sebastian Torres, Carcosa, Yellow Shore, Blue Precipice, and the King.
At MasterTrend we have already discussed how a mechanic can perform narrative work without being overly explained, as is the case with the Wind in Assassin's Creed as a narrative and technical systemHere the idea is simpler: an enemy is on the ground. The game lets you decide whether to turn it into a step.
There are spoilers from here on of the main ending, the secret ending, Arjun's past, Nitya's past, and Sebastian Torres' past.
In short: There are two main endings. The primary ending is triggered by defeating King, finishing him off, and crossing the rift in the yellow barrier. The secret ending appears after completing that first closure and following an additional chain of events that takes you through Kayla, the Blighted Marsh, Nitya's lab, the Holocache, and the Banyan Tree. These aren't two doors placed side by side; one depends on the other.
This explains why the secret ending doesn't work well if it's simply described as "take this route and choose to forgive." Before the player can forgive the King, they need to know what happens when Arjun doesn't. The throne scene needs to exist first. Without that prior image, the alternative choice loses much of its impact.
The direct route starts at Yellow Shore, accessible from the PassageYou advance through the biome, defeating Consort and you continue until the fight against the KingWhen it falls, you approach and use R1 To top it all off. Then you cross the gap in the yellow barrier. There's not much ceremony in the steps; they almost seem designed to keep you from suspecting anything.
The subsequent cutscene concludes the first playthrough and returns Arjun to the Passage. From a gameplay perspective, this unlocks the secret route. From a story perspective, it leaves something more unsettling: Arjun doesn't seem to have left Yellow Shore. He appears to have found a very precise way to get lost there.
The strange thing is that he doesn't fall because the King beats him. He falls after winning.
The secret return begins with less fanfare. You return to the Passage and you look for Kayla at the camp Echelon 3 de Shattered Descenthidden behind a door in the habitat's dome. Then you go to Blighted Marsh You proceed to the enormous red tree, where a cutscene triggers that shifts the emotional focus of the journey. From there, the path leads you to the CathedralBefore the boss area, after ringing the bell, you can find the laboratory of Nitya.
In that laboratory you reproduce the Holocaust recordingThen you return to the Passage, speak to Kayla again, and enter the Banyan Tree And you see the reverse sequence. Only then does it make sense to go back to Yellow Shoreto defeat again the King and choose forgive himWith the King alive, you cross the yellow rift and the alternate ending is activated.
The route It has the form of a secretYes, but it doesn't feel like just any old hidden prize. It's designed to make you return to the same fight with less innocence. The first time, the finisher flows. The second time, if you've been through those scenes, it's annoying.
The image of the throne, or why winning doesn't fix anything
The main ending is brief, but the image lingers. Arjun arrives searching for Nitya, defeats the King, crosses the barrier, and ends up transformed into a replica of the King himself. It doesn't feel like liberation. It feels like substitution. As if Yellow Shore hadn't been conquered, but rather satiated.
Nitya's supposed presence matters a great deal. If it's read as a reward, the ending falls flat. It makes more sense to see her as a temptation, precisely what Arjun was looking for. Yellow Shore doesn't deceive him with just anything; it shows him something that touches his desire, his guilt, and his fantasy of redemption.
At that point, Saros Stop talking only about a defeated boss. Talk about a protagonist who confuses grief with possession, love with recovery, and guilt with the right to correct the past. The game doesn't need to emphasize this. The composition of the throne speaks volumes.
The threads, the reflections, and the visual repetition surrounding the King suggest that the throne doesn't truly belong to a person. It's a position within a machine. Whoever arrives there retains something of themselves, but begins to carry an alien continuity. Arjun doesn't become unique. He becomes usable.
That's the bitterest part of the main ending: it's not a classic defeat. It's discovering too late that victory was already written in the stars, destined for someone else.
What changes when you choose not to finish
The secret ending doesn't make Arjun innocent. That's important. Many stories would use a hidden route to clear the protagonist, give him a scene of forgiveness, and close with gentler music. Saros It's not exactly like that. Arjun might act differently in the decisive moment, but the murder of Sebastian Torres It's still there. Nitya is no longer the person he remembered. Carcosa isn't a sufficient excuse.
The previous events strip away his alibis. Kayla offers a perspective that isn't tied to her obsession. Kiira and Nitya reveal lives that unfolded outside Arjun's emotional framework. Sebastian brings back something that predates the planet, predates the Yellow Shore, and predates any external monster he might conveniently blame.
When the King falls a second time, forgiving him doesn't mean suddenly becoming good. It's more modest than that. Arjun doesn't repeat the move that made him the successor. The game doesn't need a grand redemption speech; it's enough that the hand doesn't complete the previous move.
The sun pendant thrown into the water accompanies that renunciation. Arjun lets go of an object laden with memory, but also of a way of treating memory as property. He doesn't recover everything. It's not even clear how much he can recover. What changes is obedience: the loss ceases to function as a command.
The scene with Nitya is left open because it had to be. It would be a mistake to interpret it as a reward. Nitya doesn't appear to reward Arjun for having suffered or for having made the better choice in the end. Her presence serves a less comfortable purpose: to remind him that understanding something late doesn't make someone yours.
It's not a warm ending. It's more honest.
Yellow Shore doesn't invent desire; it takes advantage of it.
Yellow Shore doesn't need to act like a villain with its own narrative. Its danger lies in its precision. It doesn't offer Arjun just any fantasy, but a distorted version of what already motivated him: Nitya, the possibility of piecing together the past, the relief of not having to look too closely at his guilt over Sebastian.
That makes it more unsettling than a direct threat. The place doesn't invent a weakness; it finds one. It takes something intimate, magnifies it, and turns it into a path. The player sees a landscape. Arjun sees a promise.
The King is the final figure of that promise. He doesn't feel like a free sovereign, but rather like someone occupying a position that others have held before and that someone else might hold after. The question of who was first—Arnold Delroy, another name, another version—matters less than the persistence of the office. The throne seems to need bodies.
Nitya responds with a different kind of intelligence. Her research, the Preserver, the Constant, and the Holocache are not mere set pieces. They speak of restraint, of testing, of limits. Faced with a seductive power, she abandons structures. Faced with Arjun's impulse, she offers uneasy patience.
Carcosa doesn't help us think in a straight line either. The threads, the echoes, and the temporal repetition make King's title read less like a clean succession and more like an accumulation of fragments. Perhaps that's why the ending carries so much weight. If killing the occupant opens the door to taking their place, leaving them alive introduces a minor flaw in the mechanism.
Minimal, but enough to change the ending.
Sebastian and Nitya: two names that prevent easy redemption
Sebastian Torres This changes the player's perspective on Arjun. Until his revelation, it's still possible to see him as someone swept away by the horror of Carcosa. Afterward, that interpretation becomes incomplete. Arjun had already crossed a line before even arriving on the planet.
On Earth, Sebastian was a friend and companion. He also knew too much. He could destroy the life Arjun was trying to build with Nitya, and Arjun chose to kill him. This detail isn't there simply to make the protagonist "darker." It serves to show that his desire had already justified irreversible violence.
Sebastian's presence in Carcosa, linked to the giant tree in the Passage, remains deliberately ambiguous. He could be a ghost, a projection, an echo, or something else entirely. It doesn't matter if it's completely resolved. His function is clear: to prevent Arjun from seeing himself solely as a victim.
The detail of the "Torres" brand beer in a flashback follows the same line of thought. It shouldn't be forced as definitive proof of authorial intent. It works better as an echo. The surname appears on a minor, everyday, almost peripheral object. This is how guilt often operates in Saros: he doesn't always enter through the main door.
Without Sebastian, the epilogue would be easier to digest. With him, forgiving the King no longer seems like an isolated noble gesture. It appears to be the first time Arjun hasn't used violence to resolve a threat that exposes him.
Nitya ChandranNitya, for her part, enters the story as an absence. Arjun searches for her, imagines her, makes her the center of his journey. The epilogue corrects that perspective rather harshly: Nitya is not a reward at the end of Arjun's guilt.
She was part of Echelon 1, arrived on Carcosa with her own history, and developed responses to the Yellow. The lab, the Preserver, the Constant, and the Holocache help us understand that she wasn't simply lost. She was acting. Arjun doesn't arrive to rescue a motionless figure; he arrives too late to a life that continued making choices.
The relationship with Kiira shatters the fantasy of possession. Nitya moved on. That doesn't make Arjun's pain a lie, but it does invalidate his claim to turn that pain into a right. It's a subtle yet brutal distinction.
When she appears in the secret ending, the least helpful question is whether Arjun "wins her back." That phrasing is already tainted. It's better to ask whether he can see her without claiming her. The game doesn't offer an easy reconciliation, and rightly so.
The lights, the Blue, and the temptation to explain everything
The blue and red lights on Arjun's face immediately bring to mind police sirens. The image is too brief to definitively conclude, but enough to shift the tone of the epilogue. After rejecting the throne, perhaps Arjun is no longer fleeing in the same direction.
It can be read as a future surrender. Also as a mental image of accepted guilt. It could even be a final illusion: if Yellow works with desires, the desire for punishment could also serve as its material. The scene doesn't quite choose, and that lack of closure suits it well.
You don't need to see a real patrol boat off-screen for the scene to work. It's enough to notice that Arjun is no longer looking toward the throne. He's looking toward the debt.
That detail prevents the hidden path from becoming comfortable. Forgiving the King doesn't atone for what happened with Sebastian. Letting go of the pendant doesn't return the past to a clean state. The change is smaller: Arjun stops turning guilt into another act of possession.
He Blue Precipice It remains in a more elusive realm. It could be a place, a state of being, an image of resilience, or a combination of all of these. It's best not to confine it too soon, because its strength lies in its contrast with Yellow Shore. If Yellow captures desire, Blue suggests distance. If Yellow promises recovery, Blue seems to ask that something be let go.
What's interesting is that this opposition isn't resolved like a normal war. Arjun doesn't reach the epilogue because he hits harder. He reaches it because, for once, he doesn't finish the job. This detail gives the Blue a clear narrative function: to represent a form of resistance that doesn't involve possessing, replacing, or finishing off the enemy.
Kayla and Kiira fit into this space because they shift the center of gravity away from Arjun's obsession. The story ceases to be solely about his quest and begins to reveal lives, relationships, and memories that don't belong to him. This expansion prevents the ending from being reduced to "Arjun learns a lesson." He does learn, yes, but at the cost of discovering that the world wasn't organized around his pain.
Blue isn't an easy answer to Yellow. It's a different kind of discomfort. It doesn't promise to give you everything back. Perhaps that's why it's more reliable.
The inevitable question remains: was it all a dream? Saros It blends fragmented memory, technology, cosmic horror, and scenes with an almost mental texture, so doubt arises naturally. But answering with a yes or no diminishes the ending. The game works best when the literal and the symbolic intertwine.
Even if some images are projections, their effect is not false. Sebastian Torres transforms Arjun even though he appears as guilt incarnate. Nitya matters even though the protagonist's memory distorts her. Yellow Shore can be both place and metaphor without losing its power. Carcosa doesn't need to be a dream to behave like a sick conscience.
If you've already seen the main ending, the next steps are straightforward: find Kayla in Shattered Descent, follow the trail of the red tree in Blighted Marsh, enter Nitya's lab in the Cathedral, play the Holocache, go through the Banyan Tree, and return to Yellow Shore. When the King falls, don't do the same thing you did before.
Saros There's no need to ask if Arjun can win one more fight. He's already done that. What remains open is whether he can stop the tide just when winning starts to feel too much like doom.
