Event Directory
Event Directory
Embedded Files
Explore selected turning points in StarForgeRP’s shared history: what happened, what changed, and which consequences continued into later lives and stories.
This directory covers major SWTOR developments alongside established community-created events. Its focus is the significance of each event, from changes in galactic power to a rescue or failed evacuation whose surviving evidence still matters.
Spoiler notice: This page discusses major SWTOR story developments through Legacy Reborn. Current Setting establishes StarForgeRP’s adopted story boundary and shared present.
Using the Event Directory
Using the Event Directory
Use the Galactic Timeline for dates and sequence, Era Overview for the circumstances of each period, and Wars & Conflicts for broader military history. Detailed campaigns, missions, and investigations belong in Roleplay; RP Events provides the directory for roleplay occasions.
BBY means Before the Battle of Yavin. BTC and ATC mean Before and After the Treaty of Coruscant, which falls in 3653 BBY. BBY dates are an archival reference for players, not knowledge of a future battle available to contemporary characters.
Confirmed dates have direct historical support.
Reconstructed dates express a working chronology derived from narrative evidence and chronological guidance.
Approximate dates or periods use “c.” to indicate limited precision.
Sequence-only entries preserve event order without assigning an unsupported year.
Established StarForgeRP dates identify documented community history. They do not independently establish dates for surrounding SWTOR events.
The galactic entries summarize SWTOR history as incorporated into StarForgeRP. Community-created events appear separately. Continuity & Canon explains how source differences, branching outcomes, and shared continuity are handled.
These are player-facing accounts. An event can be established while its causes, private circumstances, or detailed sequence remain unknown to a character.
The Great Galactic War
The Great Galactic War
The Empire’s Return
The Empire’s Return
3681 BBY · 28 BTC · Confirmed date
The concealed Sith Empire returned with a coordinated offensive against the Galactic Republic. Surprise attacks and preparations made before the invasion helped Imperial forces seize the initiative, beginning the Great Galactic War.
The invasion changed the Republic’s strategic position for a generation. What began as a sudden external assault became twenty-eight years of warfare, ending with the Treaty of Coruscant. Its legacy could reach later characters through military service, lost homes, inherited property claims, or family histories shaped by changing borders.
The Sacking of Coruscant & Treaty of Coruscant
The Sacking of Coruscant & Treaty of Coruscant
3653 BBY · 0 ATC · Confirmed date
While Republic and Imperial representatives negotiated on Alderaan, Imperial forces attacked Coruscant, destroyed the Jedi Temple, and held the capital hostage. The assault compelled the Republic to accept unfavorable peace terms.
The treaty ended the Great Galactic War but required withdrawals that left other worlds exposed to Imperial control. It also became the reference point for BTC and ATC dating. For those affected, the settlement could mean relief from sustained fighting, separation from the Republic, or displacement rather than a secure peace.
The Cold War
The Cold War
Return to Open War
Return to Open War
c. 3641–3640 BBY · c. 12–13 ATC · Approximate transition
The Treaty of Coruscant restrained open warfare without ending the struggle between the Republic and Empire. Covert operations, political interference, and contested territories eroded the settlement until renewed fighting became a general war.
The transition renewed demands on personnel, supplies, and transport while exposing the limits of the treaty. A character’s experience should follow the circumstances of a particular world or institution: a deployment, interrupted journey, threatened employer, or local confrontation may matter more than a single declaration marking the end of peace.
The Renewed Galactic War
The Renewed Galactic War
The Battle of Ilum & Malgus’s Rebellion
The Battle of Ilum & Malgus’s Rebellion
c. 3640 BBY · c. 13 ATC · Reconstructed date
During the Ilum campaign, Darth Malgus broke with the existing Sith leadership and attempted to establish a rival Imperial order. Republic and Imperial forces opposed his rebellion, which ended in defeat. Malgus was believed dead afterward.
The revolt weakened an Empire already committed to renewed war and exposed divisions within its leadership. Its failure could leave surviving personnel with compromised service histories, divided loyalties, or obligations to former comrades. Malgus’s later reappearance also makes it important to distinguish what people believed at the time from what subsequent events revealed.
The Makeb Crisis & Hutt Expansion
The Makeb Crisis & Hutt Expansion
c. 3638 BBY · c. 15 ATC · Reconstructed date
Toborro occupied Makeb to exploit isotope-5, an energy source he intended to use to expand Hutt power. Destructive extraction destabilized the planet. Republic intervention concentrated on evacuation, while Imperial forces pursued the resource and prevented the planet’s immediate destruction.
Toborro’s defeat ended his bid for supremacy, but Makeb remained strategically important. Continued Imperial access to isotope-5 supported recovery from earlier setbacks. The crisis also left consequences beyond military competition: displaced residents, lost livelihoods, and technical knowledge could connect later stories to the struggle over the planet.
The Revanite Crisis
The Revanite Crisis
c. 3637 BBY · c. 16 ATC · Reconstructed date
Under Revan’s leadership, the Order of Revan developed into a conspiracy operating inside both the Republic and Empire. Revan sought to restore the Sith Emperor to a physical form that could be destroyed. His plans culminated on Yavin 4, where a temporary coalition opposed him.
The coalition defeated Revan, but the attempt to destroy Vitiate instead helped restore the Emperor to activity. The crisis exposed the danger of covert allegiance within apparently opposed institutions. For later histories, suspected membership, compromised records, and cooperation between former enemies can matter without making every earlier Revanite equally informed or responsible.
The Devastation of Ziost
The Devastation of Ziost
c. 3636 BBY · c. 17 ATC · Reconstructed date
Vitiate seized control of people on Ziost, turning inhabitants and defenders against one another. Evacuation efforts saved some, but the intervention failed to stop him from consuming the life that remained on the planet.
Ziost survived physically as a devastated world. Its ruins and abandoned infrastructure preserve evidence of a society whose surviving members were scattered elsewhere. The catastrophe can remain significant through bereavement, lost homes, recovery work, or a survivor’s relationship with the institutions that once governed the planet. Knowing that Ziost was devastated does not establish firsthand knowledge of Vitiate’s methods.
The Eternal Empire & the Alliance
The Eternal Empire & the Alliance
The Zakuulan Conquest & Years of Rule
The Zakuulan Conquest & Years of Rule
c. 3636–3631 BBY · c. 17–22 ATC · Reconstructed period
The Eternal Empire, centered on Zakuul, overwhelmed the weakened Republic and Sith Empire. Under Arcann, the Eternal Fleet enforced submission and tribute. Both defeated governments survived, but neither could freely challenge Zakuulan supremacy.
This period covers the conquest and subsequent domination during the Outlander’s approximately five-year captivity; it does not mean the conquest itself lasted five years. Tributary governments and directly occupied communities faced different conditions. Service, resistance, collaboration, and displacement could leave lasting consequences without making every world’s experience identical.
The Alliance War Against Zakuul
The Alliance War Against Zakuul
c. 3631–3630 BBY · c. 22–23 ATC · Reconstructed period
After escaping captivity, the Outlander became the central figure in resistance to Arcann. The Alliance established its headquarters on Odessen, drawing together former enemies and independent allies. Its campaigns brought down Arcann and Vaylin, and the Commander ultimately claimed the Eternal Throne.
Control of the throne and fleet transformed the resistance coalition into the Eternal Alliance, briefly giving it exceptional galactic influence. Victory also created difficult relationships between former occupiers and those who had fought them. Shared service could produce trust and obligation without erasing earlier losses or settling future allegiance.
After the Eternal Throne
After the Eternal Throne
The Iokath Crisis & Fractured Alliance
The Iokath Crisis & Fractured Alliance
c. 3629 BBY · c. 24 ATC · Reconstructed date
The discovery of powerful weapons on Iokath drew Republic and Imperial forces into confrontation. The Alliance faced competing demands from the two governments while attempting to protect its own position. Subsequent crises on Umbara and Copero intensified uncertainty within the coalition.
The struggle tested whether cooperation built against Zakuul could survive renewed factional competition. Personnel might retain obligations to the Alliance while facing pressure from former governments, colleagues, or families. Those tensions provide historical context without imposing one playthrough’s political choices or personal outcomes on every StarForgeRP character.
The Nathema Conspiracy
The Nathema Conspiracy
c. 3628 BBY · c. 25 ATC · Reconstructed date
The Order of Zildrog infiltrated Alliance systems and brought its campaign against the Commander to Nathema. The confrontation destroyed the Gravestone and devastated the fleet strength on which Alliance supremacy depended.
The Alliance survived, but its remaining forces could no longer enforce its former dominance. Odessen, experienced personnel, and relationships built during the war against Zakuul retained their importance. For those connected to the coalition, the loss could change assignments, access to resources, or prospects for continued service while older Republic–Imperial loyalties regained practical weight.
The Renewed Republic–Imperial War
The Renewed Republic–Imperial War
Ossus & Onslaught
Ossus & Onslaught
c. 3628–3627 BBY · c. 25–26 ATC · Reconstructed period
The campaign connected political allegiance with the resources needed to sustain war. Fuel, reinforcements, and ship production mattered alongside battlefield victories. Its consequences could reach transport crews, industrial workers, medical personnel, and displaced households. A connection to this period need not imply participation in the Alliance Commander’s operations.
Darth Nul’s Legacy & the Hidden Chain Campaign
Darth Nul’s Legacy & the Hidden Chain Campaign
After early 27 ATC · Sequence only; exact calendar placement uncertain
Renewed fighting over Manaan and its kolto supplies unfolded alongside Malgus’s pursuit of knowledge associated with Darth Nul. Among the Mandalorians, Heta Kol’s Hidden Chain challenged Shae Vizla and continued its campaign after the confrontation on Ruhnuk.
The struggle spread through further investigations and operations, including Voss, Ord Mantell, Hutta, and developments involving Odessen. Nul’s surviving work increasingly connected the Sith and Mandalorian conflicts. Communities caught in those operations could experience raids, disrupted work, or displacement without understanding the research or private objectives driving them.
The Confrontation on Khar Shian
The Confrontation on Khar Shian
Following Master’s Enigma · Sequence only; exact SWTOR calendar placement uncertain
The struggle converged on Khar Shian, where the Hidden Chain reconstructed Darth Nul’s machine in Naga Sadow’s fortress. Heta Kol, Shae Vizla, Darth Malgus, and Darth Jadus entered the confrontation with competing objectives. In StarForgeRP’s adopted account, Heta died, Shae suffered a mortal wound, and Malgus used the machine to transmit his legacy to Force-sensitive beings across the galaxy.
The confrontation broke Heta’s leadership and left the transmission’s wider consequences unresolved. Receiving it does not automatically reveal the machine’s operation, events inside the fortress, or the truth of Malgus’s claims. Current Setting establishes the adopted aftermath and the boundary for subsequent developments.
StarForgeRP Community Events
StarForgeRP Community Events
The following events belong to established StarForgeRP-created continuity. Their significance lies in the lives, relationships, evidence, and unanswered questions that survived them.
These summaries are player-facing. Access to sensitive testimony, operational methods, or investigative findings depends on a character’s actual involvement and circumstances.
3630 BBY · 23 ATC · Established StarForgeRP date
A humanitarian emergency on Ord Mantell became a hostage crisis and failed civilian evacuation. Jedi Master Jasmin Dawnseer and multiple civilians died. Amara Noxstar and Kleya Noxstar survived, but the available accounts did not establish an uncontested sequence of decisions or allocation of responsibility.
The Ord Mantell Evacuation Site preserves physical context for later examination. Survivor testimony, humanitarian records, droid memory, and separately held documentation support The Ord Mantell Reconstruction. Their comparison may clarify the disaster without requiring every recollection to agree or treating survival as proof of either fault or innocence.
Later 3630 BBY · 23 ATC · Established StarForgeRP date
During Vaylin’s Grand Festival and the surrounding palace crisis, Bella Tenebrix falsified a detention-transfer route. Brina Tenebrix used the opening to extract Kylia Tille and Raeya Tille from Zakuulan custody. Both escaped and subsequently entered monitored Alliance custody and review.
Dragon’s Maw Extraction occurred alongside the Alliance’s wider operation without replacing its participants or outcome. It left an authentic institutional record containing false routing information. The rescuers’ methods and involvement remain restricted knowledge, while the precise technical intervention, complete route, and extent of advance coordination remain unresolved.
3621 BBY · 32 ATC · Established StarForgeRP date
An Imperial Army operation on Korriban suffered casualties amid interacting failures in communications, movement, coordination, authorization, and emergency response. Later medical examination identified preventable or potentially preventable losses, while disputed accounts and evidence-handling problems complicated reconstruction.
The Ash Corridor Incident Site allows investigators to test claims against physical circumstances. Ash Corridor examines what personnel knew, what authority and resources they possessed, and whether an effective response remained possible. Medical possibility alone does not settle responsibility, and findings from the separate 3622 BBY escalation failure do not automatically determine conduct during this later operation.
Grey Ledger connects later comparisons involving Ord Mantell, Ash Corridor, and the Dragon’s Maw transfer record. These documentary relationships do not establish a common cause, one coordinated conspiracy, or unrestricted access to the evidence. Each event retains its own circumstances and unresolved questions.
Using Historical Events for Roleplay
Using Historical Events for Roleplay
Choose a concrete point where history intersects with the character’s life.
Was the character alive and old enough to remember the event, or did they learn about it afterward?
Where were they, and what changed locally?
How did the event affect their household, work, training, or institutional ties?
Which knowledge comes from experience, and which depends on testimony, records, education, or propaganda?
What loss, promise, debt, relationship, or unfinished responsibility survived?
Which unresolved consequence could give another character a reason to become involved?
Shared history establishes circumstances, not identical beliefs or predetermined responses. People can remember the same event differently, revise their understanding, or choose different ways to meet its consequences. Use Current Setting to connect those histories with StarForgeRP’s shared present.
Page updated
Google Sites
Report abuse