In 3957 BBY, the Republic and Jedi executed a desperate plan to remove Darth Revan from the Sith war effort. Bastila Shan led a strike team onto Revan's flagship during a staged fleet engagement. As the Jedi reached the bridge, Darth Malak ordered his own ships to fire on Revan's vessel. Revan was gravely wounded, but Bastila kept him alive and escaped with him.
3957 BBY · Legends · Evidence review
REVAN CAPTURED
Documented history and chronological boundaries
In 3957 BBY Bastila Shan led a Jedi team onto Darth Revan's flagship as Republic forces tried to capture the Sith leader. Malak ordered his own ships to fire on his master's vessel as the strike team reached Revan. The bombardment gravely injured Revan but did not kill him. Bastila sustained his life and escaped, creating a Force bond that later shaped their shared visions. The assault was both a Republic attempt to remove an enemy commander and Malak's opportunistic bid for supreme power.
People, political institutions and material life
The same incident looks different from the perspectives of the Republic, the Jedi and Revan's second-in-command. One side sought intelligence or a prisoner; Malak sought succession through treachery. Bastila's intervention transformed an apparently fatal attack into a captured and rehabilitated person whose former identity was concealed. The episode shows how victory in a command raid can create a new ethical problem about what a government may do with its captive.
Source trail: Knights of the Old Republic (2003), identity revelation; Campaign Guide, flagship assault. Explore source and bibliography →. The original conceptual banner is not documentary or game footage. Dialogue and print-page-level citations remain subject to primary-source checking.
The Republic targets leadership rather than the whole fleet
The Jedi understood that conventional attrition favored a Sith military supplied by the Star Forge.
Removing Revan was an attempt to create political instability at the center of the enemy coalition.
Malak attacks both enemy and master
By firing on the bridge, Malak tried to kill Revan and the Jedi strike team simultaneously.
Succession inside the Sith hierarchy became part of the battle itself.
Bastila creates a Force bond while saving Revan
Her effort to preserve Revan's life created an unusually strong connection between them.
That bond later became central to the Jedi plan for recovering the location of the Star Forge.
Anthropological assessment
The capture demonstrates how political systems centered on charismatic leaders can be vulnerable to targeted removal.
It also shows that internal succession struggles can unexpectedly reshape an external war.
A leadership operation inside a larger war
The Republic could not assume it could defeat Revan simply by destroying enough ships. The Star Forge allowed the Sith fleet to be replaced at a rate that made ordinary attrition costly. Bastila Shan's mission targeted Revan himself, aiming to break the central command and create space for a military recovery. The operation also depended on extraordinary risk: a small Jedi strike team had to reach a hostile flagship rather than strike from safety.
Malak's attack creates an unintended prisoner
As the Jedi reached the bridge, Malak ordered fire on Revan's vessel. He intended to eliminate his master and seize control of the Sith Empire. This betrayal could have destroyed the Jedi team as well. Instead, Revan was seriously wounded and recovered alive by Bastila. The event combined an outside attack with an internal succession struggle, and those two motives cannot be separated when explaining why Revan survived.
A secret identity becomes a military plan
Jedi healers preserved Revan's life, and the Order later used an altered identity while seeking information about the Star Forge. This is not evidence that the person had never been Darth Revan. It is evidence that different characters knew different parts of the history. The player learns those facts gradually, and the later revelation aboard the Leviathan changes the meaning of earlier dialogue with companions and Jedi.
The bond with Bastila influences later events
Bastila's act of saving Revan also initiated the bond that helps guide the Star Map quest. That relationship becomes militarily significant again when Malak takes Bastila prisoner. The attempt to remove one Sith leader ultimately produces the two people who help defeat his successor. This is a consequential chain, not an assumption that Bastila could have predicted the later outcome when she rescued Revan.
Anthropological extension: memory, consent, and political identity
Revan's capture raises questions about whether identity belongs to an individual, to a governing institution, or to a community of people who remember a person's past. The Jedi's plan treats knowledge of Revan's history as a strategic resource. It allows the Republic to use a former enemy while controlling what the person knows about that history. The ethical difficulty does not vanish because the plan succeeds. Revan's later actions require a distinction between recovered information, decisions taken under deception, and decisions made after the truth is known.
Check the historical evidence
Which parts belong to established Legends continuity?
The event and its outcome are recorded in the cited original game or official reference material. When an RPG offers branching dialogue or endings, this article identifies the outcome used in the subsequent Legends chronology.
What does the illustration show?
The diagram is an original IDS sequence summary. It does not depict a screenshot, official character likeness, ship design or exact map coordinates. Verifying a suitable event-specific publisher illustration is a separate editorial task.
Interactive evidence test · 3957 BBY
Test your historical judgment
Answer both questions for corrections, documentary context and a score. You can revise answers and try again.
Legends · historical source review
The Sith leader is captured by a fractured alliance
Bastila Shan leads a Jedi strike aboard Revan's flagship to capture the Sith leader. Malak chooses that moment to order fire on his own master's vessel, attempting to remove a rival even at the cost of the ship's destruction. Revan survives gravely injured and is taken into Jedi custody. The Council subsequently makes the controversial decision to remove his memories and create a new identity.
The operation is a reminder that military authority and personal ambition may clash within an authoritarian command system. Malak's betrayal changes the structure of the Sith leadership, but does not mean every subordinate knowingly joined his conspiracy. The Council's treatment of the captive raises a different ethical problem: whether protecting a political community can justify radically altering an individual's remembered identity. These actions are linked, yet the strike, betrayal, recovery and memory intervention have separate institutional authors.
Historical judgment: Malak's attack and the Jedi Council's memory decision are separate choices. Publisher's related original account →. The analysis of political institutions is IDS interpretation, not game dialogue. Day-level event dates and player-defined decisions are not asserted.
Original-source investigation: Revan's capture is not the same event as his later awakening
The capture of Revan is revealed after the opening identity mystery of Knights of the Old Republic. Bastila Shan's intervention and Malak's attack explain how Revan survives with altered memory and later appears under a new identity. This is an earlier event than the 3956 BBY Endar Spire and Taris sequence, even though the game reveals key facts after the player has already completed multiple missions.
A story told through flashbacks should be sorted by the events' in-universe chronology, not the order in which a player learns about them. Lucasfilm's general game record does not identify which choices the player made. The historiographic issue here is the ethics of state and Jedi control of a person's memory and political identity; it should remain analysis rather than a claim that the game offers one uncontested moral interpretation.
Follow the sources: Original KOTOR game · SWTOR in-universe Galactic History. Publisher overviews and in-universe narrators do not replace original game scenes, chapters or comic panels.
3957 BBY · Legends · Narrative vs. later chronology
The bridge mission that changes Revan's identity
A strike against command, not an ordinary naval engagement
In the Legends background to Knights of the Old Republic, the Republic and the Jedi were being overwhelmed by Revan's military campaign. Bastila Shan led a strike team to reach the Sith leader aboard his flagship. The objective was Revan as a person and commander, not the destruction of every ship in the fleet. It is important to distinguish the team's boarding operation from the larger battle that put the vessel within reach. The boarding scene is reconstructed through the game's later revelation rather than presented in the player character's opening memories.
Malak's intervention redirects the story
When Bastila's team confronted Revan, Darth Malak ordered his vessel's weapons to fire on the flagship bridge. The act endangered both master and Jedi attackers, and became the decisive opening for Malak's own succession. Revan was grievously injured but not killed. Bastila sustained Revan's life and the surviving captive was brought under Jedi control. Describing the event simply as an ordinary surrender would erase the combination of assassination attempt, rescue and subsequent custody.
Identity becomes an institution's secret
The Jedi Council sought to use Revan's damaged memory and recovered life in its struggle against the Sith. That decision created an ethically difficult situation: the person later serving the Republic did not initially know the history being withheld. Bastila's bond with Revan is an actual feature of the game's story, while the questions of consent, secrecy and institutional obligation are IDS historical interpretation. The 3957 BBY dating belongs to the established Legends chronology; the first game's promotional overview does not itself give that exact date.
Check your historical interpretation: Did Bastila simply execute Revan when Malak opened fire?
Explanation: No. The later game's central revelation establishes that Revan survived and was taken into Jedi custody. Malak tried to eliminate his master and the Jedi together, but the outcome was a living prisoner.
Original publication: Lucasfilm: Knights of the Old Republic. Publisher overviews confirm the RPG and its branching design, not every cutscene or exact 3950s BBY event date. Continue this timeline sequence →
Jedi Civil War · Legends evidence file
Revan's capture: the Jedi mission and Malak's betrayal happen together
Event and historical sequence
In 3957 BBY, Republic and Jedi leaders sought a way to end the Sith offensive by removing Darth Revan. Bastila Shan led a strike team onto Revan's flagship during a fleet engagement. Darth Malak ordered his own ships to fire on his master's bridge, attempting to kill Revan and the Jedi attackers at once. Revan was gravely injured but survived. Bastila's intervention helped preserve his life and produced a Force bond between them. The Jedi Council later suppressed or rewrote Revan's memories and placed him under a new identity, hoping his remaining knowledge could lead them to the Star Forge.
Institutions, everyday life and political power
Two institutions pursued different goals in a single crisis. The Jedi tried to neutralize a powerful enemy through capture and intelligence, while Malak treated his master's apparent death as an opportunity for personal succession. Revan's survival then allowed the Council to shape his identity and future actions. This raises a difficult question about agency: a new public role imposed upon a person with disrupted memories is not equivalent to a freely chosen prior biography. The later story explores whether he can exercise moral judgment after learning the truth. A historical account should also acknowledge that the strike team suffered losses rather than treating the operation as costless.
Limits and conflicting evidence
Revan's rescue and the Council's later identity intervention are sequential, not the same act on the bridge. Malak initially believed Revan had died, and the 3956 BBY revelation aboard the Leviathan came later. In the 2003 game, some later dialogue and decisions vary with player choice; default Legends narrative uses the redeemed Revan.
Historical judgment: Did Malak's shot kill Revan and thereby end his participation in the war?
Correction and educational insight: No. Revan survived in Jedi custody, while Malak mistakenly treated him as dead and assumed Sith leadership.
Source trail: Knights of the Old Republic (2003), Bastila and Malak dialogue; Knights of the Old Republic Campaign Guide. Reference and bibliography ↗. Primary-source location checks remain in progress.
Sources and further reading
- Lucasfilm: Knights of the Old Republic (official product overview; game scenes supply event details).
- Star Wars: Knights of the Old Republic.
- Star Wars: The Old Republic, Timeline 8: “The Jedi Civil War.”