Around 14,500 BBY, war again broke out between Coruscant and Alsakan. The Third Alsakan Conflict opened with the Commenor Run Campaign, a multi-world operation whose surviving battlefields included Tepasi, Alderaan, and Kattada. The war would last about two centuries, ending in 14,300 BBY. Yet the opening survives only in outline. The sources do not identify a single incident that triggered hostilities, name commanders on either side, specify who attacked first, or preserve casualty figures. What remains is the route, the worlds, and the fact that the old rivalry had returned.
Nine centuries after the Second Conflict
The Second Alsakan Conflict had ended around 15,400 BBY.
The Third began roughly nine centuries later.
That interval was long enough for many generations to live without an active Alsakan war, but not long enough to erase the structural rivalry between the two political centers.
Coruscant and Alsakan again
At the center of the conflict were Coruscant and Alsakan.
Their rivalry had already shaped Republic politics for thousands of years.
Both worlds led wider networks of allies, aristocratic houses, commercial interests, and dependent systems.
This was not a feud between two individuals
No single ruler or commander explains the recurrence of war.
The rivalry persisted through institutions rather than personalities.
Generations inherited political alliances, economic competition, route interests, and memories of earlier wars.
The trigger is not preserved
The source does not tell us what specific event caused the Third Conflict to begin.
There is no securely named assassination, trade dispute, border incident, Senate vote, succession crisis, or ultimatum.
Any such explanation would be reconstruction rather than established history.
The Commenor Run Campaign
The first recorded operation of the war was the Commenor Run Campaign.
The Commenor Run was a hyperlane stretching from Brentaal toward Commenor through a chain of strategically important worlds.
Its route crossed the Core Worlds and Colonies, making it valuable for trade, communications, and military movement.
A route lined with important worlds
The Commenor Run connected or passed systems including Brentaal, Tepasi, Caamas, Alderaan, Kattada, and Commenor.
The opening campaign did not need to seize every point on the lane for the route to matter.
Control of selected worlds could affect movement across the entire corridor.
Tepasi
Tepasi was one of the named battlefields of the opening campaign.
Its location near the Coreward end of the Commenor Run gave it strategic value for movement between established Core systems and the route beyond.
The source does not preserve the specific battle fought there.
Alderaan
Alderaan also became a battlefield during the campaign.
This is one of the oldest known military associations with a world later famous for pacifism and diplomacy.
The ancient battle should not be used to project later Alderaanian politics backward across fourteen thousand years.
Do not impose later Alderaan on the ancient world
The Alderaan of Bail Organa and the Galactic Civil War belonged to an enormously later social order.
Political culture can change radically over deep time.
The fact that Alderaan was fought over in 14,500 BBY does not contradict its later reputation for peace.
Kattada
Kattada was the third named battlefield.
The Kattada system lay in the Colonies and directly on the Commenor Run.
Its position made it a natural strategic point for forces attempting to control passage between Core and colonial space.
Three battlefields, no preserved sequence
The sources name Tepasi, Alderaan, and Kattada.
They do not tell us the order in which fighting reached them.
Nor do they identify whether one side advanced down the route while the other defended, or whether fighting broke out at several points independently.
A campaign is larger than one battle
The term “campaign” suggests a connected series of military operations rather than a single engagement.
That is consistent with three named worlds spread along one route.
But the exact operational plan is not preserved.
Who attacked first?
The source does not securely establish an attacker for the Commenor Run Campaign.
Later knowledge that Coruscant and Alsakan were rivals does not answer that question.
IDS therefore avoids assigning one side the offensive without documentation.
Hyperlanes as strategic geography
In an interstellar civilization, distance is shaped less by straight-line space than by navigable hyperspace routes.
A world on a major lane can matter more strategically than a physically closer world that is difficult to reach.
The Commenor Run therefore functioned like a road, rail corridor, shipping channel, and communications artery at once.
War follows logistics
Fleets require fuel, maintenance, ammunition, food, replacement crews, intelligence, and repair yards.
Controlling a hyperlane can determine whether those resources reach the front.
The campaign's geography strongly suggests the importance of logistics even though the specific supply plans are unknown.
Trade routes become military routes
The same lane that moved merchants in peacetime could move warships during conflict.
Commercial infrastructure therefore became military infrastructure when war returned.
This dual use is one reason economic geography repeatedly shaped the Alsakan Conflicts.
Civilian traffic would have been affected
A campaign spread across a trade route would almost certainly disrupt ordinary movement.
Merchants, passengers, couriers, and local economies depended on predictable access.
The sources do not preserve civilian losses or displacement, so the scale of that disruption cannot be quantified.
The archive remembers worlds, not people
The surviving chronology names three planets but not a single civilian affected there.
That is a familiar pattern in ancient military history.
Strategic geography survives more readily than ordinary experience.
War across Core and Colonies
The Commenor Run crossed from the Core Worlds into the Colonies.
The campaign therefore linked the political heartland to regions shaped by earlier Republic settlement.
The Coruscant–Alsakan rivalry was never confined to the two capitals themselves.
Networks of allies
Previous Alsakan conflicts had shown that both sides depended on allied systems and political blocs.
That meant a route campaign could affect worlds whose local interests were not identical to either capital's.
Imperial-style maps can make war look binary even when local loyalties were more complicated.
A civil conflict inside a republic
The Alsakan Conflicts were not conventional wars between wholly separate galactic civilizations.
They were struggles among major powers inside the wider Republic political order.
That made questions of legitimacy, representation, and authority inseparable from military strategy.
The Republic's paradox
The Republic could contain competing worlds powerful enough to wage centuries-long wars against one another.
Its institutions were broad enough to survive those conflicts, but not always strong enough to prevent them.
The Third Conflict demonstrates both durability and weakness.
Inherited memory of earlier wars
By 14,500 BBY, political elites on both sides inherited stories of the First and Second Alsakan Conflicts.
Those memories could shape expectations about betrayal, sacrifice, territory, and prestige.
Historical memory can make renewed war easier to imagine even after centuries of peace.
The Second Conflict's unresolved ending
The Second Alsakan Conflict had ended in a draw rather than a decisive political settlement preserved in the sources.
Coruscant remained the capital and Alsakan remained a major rival.
The structural competition therefore survived the peace.
But a draw does not prove direct causation
The absence of a decisive settlement helps explain why rivalry could continue.
It does not establish that one unresolved clause directly caused the Third Conflict nine centuries later.
The initiating crisis remains unknown.
A two-century war
The Third Alsakan Conflict lasted from about 14,500 to 14,300 BBY.
That makes it far shorter than the Second Conflict's roughly eight centuries.
Even so, two hundred years is longer than many entire political eras.
Several generations knew only war
A two-century conflict can encompass multiple generations of soldiers, officials, and civilians.
People born after the opening campaign could die before peace returned.
Calling the war “shorter” is meaningful only in comparison with the extraordinary scale of the Alsakan sequence.
Fifty years later: Rucapar
In 14,450 BBY, the war reached the city of Rucapar on Alsakan itself.
The confrontation known as the Cleansing of Rucapar destroyed the centerpiece of the famous Alsakan Mosaics.
That event provides the next securely dated episode of the war.
The Alsakan Mosaics
The mosaics were a mountain-scale artwork whose centerpiece stood in Rucapar's central square.
Five lanes of gleaming tile extended from the center toward five equidistant mountains.
Their destruction turned the Third Conflict into another episode of cultural heritage loss.
Republic forces at Rucapar
Later chronology identifies Republic forces as responsible for destroying the centerpiece during the Cleansing.
That fact should not be projected backward to prove who initiated the Commenor Run Campaign fifty years earlier.
Different phases of a long war can reverse offensive and defensive roles.
The final stage at Raxus Prime
By 14,300 BBY, the conflict's final stages involved fighting around Raxus Prime.
The Machinists of Nikato defeated the Duros Red Credit Brigade.
The aftermath produced an independent pocket state known as Nikato's Bootheel.
Not every combatant was simply Coruscant or Alsakan
The Raxus Prime episode shows that later stages involved factions with their own names and agendas.
Large wars create political opportunities for regional movements, mercenary formations, commercial groups, and local powers.
The two-capital rivalry did not erase third-party agency.
Nikato's Bootheel
After defeating the Red Credit Brigade, the Machinists established Nikato's Bootheel around Raxus Prime in 14,300 BBY.
The pocket state outlived the immediate battle.
War therefore changed political geography even when the overall Coruscant–Alsakan rivalry remained unresolved.
The war ends in 14,300 BBY
The Third Alsakan Conflict ended in 14,300 BBY.
The surviving summaries do not preserve a decisive peace treaty, surrender document, or clear overall victor.
The end date is more certain than the mechanism of peace.
It was not the last Alsakan war
Another Alsakan conflict would begin around 13,800 BBY.
The fifty centuries between the First and Fifth conflicts demonstrate the durability of the rivalry.
The Third Conflict solved no permanent constitutional problem.
Current canon and the route worlds
Alderaan and other worlds associated with the campaign remain part of current canon, and Kattada has also appeared on modern galactic mapping.
The Third Alsakan Conflict and its Commenor Run Campaign remain Legends chronology.
Current geography should not be mistaken for current confirmation of the ancient war.
Why the campaign is best understood on a map
The event makes little sense as a list of three disconnected worlds.
Tepasi, Alderaan, and Kattada become strategically coherent when understood as points along the same hyperlane.
The route is the connective tissue of the campaign.
Anthropological assessment
The beginning of the Third Alsakan Conflict shows how infrastructure can organize violence. Hyperlanes were created to make travel and exchange easier, yet the same connectivity produced corridors along which military power could move rapidly.
The conflict also demonstrates the persistence of institutional rivalry. No individual from the First Alsakan Conflict was still alive to fight the Third, yet the political structure survived. Wars can be inherited through institutions, alliances, economic systems, and historical memory.
Finally, the sparse record is itself meaningful. We know where the campaign happened but not who experienced it. Deep-time history preserves routes and capitals more readily than families, refugees, workers, or ordinary soldiers. A responsible timeline should make those absences visible rather than filling them with dramatic invention.
What the sources establish
Canon versus Legends
The Third Alsakan Conflict
Sources and further reading
- Jason Fry with Paul R. Urquhart, The Essential Guide to Warfare: Star Wars, Random House, 2012.
- Daniel Wallace and Jason Fry, Star Wars: The Essential Atlas, Del Rey, 2009.
- Random House Worlds, The Essential Guide to Warfare
- Third Alsakan Conflict, Wookieepedia
- Commenor Run Campaign, Wookieepedia
- Commenor Run/Legends, Wookieepedia
- Cleansing of Rucapar, Wookieepedia