Halo Nation

Blooding Years

Redirected from Sangheili Civil War

9,960pages on
this wiki
Add New Page
Talk0 Share

This article is a stub and does not have enough relevant information. You can help by expanding it.

The Blooding Years, also known as the Sangheili Civil War, was an armed conflict between the Swords of Sanghelios and different factions opposed to Thel Vadam's rule.[1]


The seeds of the Blooding Years began immediately after the end of the Great Schism and the Human-Covenant war. In January 2553, the Arbiter Thel 'Vadam began to visit the various states to propose a peace treaty with humanity. He argued that too many Sangheili had been lost in the Great Schism, and that Sanghelios had to be rebuilt. This proposal was not well received by all, and civil unrest ensued. Dissident Sangheili began to join the Servants of the Abiding Truth, an old orthodox religious group who opposed the Arbiter led by Avu Med 'Telcam.

In February 2553, Fleet Admiral Terrence Hood arrived on Sanghelios to formalize the cease-fire with the Arbiter. They met in the state of Vadam and formally ended hostilities, solidifying the Treaty of 2552.[4]


This section requires expansion.

Opening BattleEdit

Main article: Assault on Vadam

After a Jiralhanae rebellion began in Ontom, the Servants of Abiding Truth decided it was the time to strike against the State of Vadam.[5] This assault was met with massive resistance including forces from the Swords of Sanghelios and the UNSC Infinity. The attack would ultimately fail with the Servants eventually retreating to New Llanelli.[6]

Final StandEdit

Main article: Battle of Sunaion

After the losses encountered during the Battle of Kamchatka, the Swords of Sanghelios decided that the they were going to strike at Jul 'Mdama's Covenant's final Sanghelios stronghold at Sunaion.[7]


Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.