FANDOM


The Desmoth Siege, also referred to as the Desmoth Massacre and the Battle in Desmoth, was a military operation waged by the Harbian Eclipse Agency against the residents of the Arme Selax Compound near the town of Desmoth, Renshaw.

Desmoth Siege
Harbian Siege
Conflict:

HEA Operations

Date:

Nahvidax'k'ver VII, 1996

Place:

Desmoth, Renshaw, Harbitros

Outcome:
  • The Arme Selax Compound is burned to the ground
  • The survivors are arrested by the Harbian Eclipse Agency
Combatants

Alt Harbitros Flag2 The Corporatocracy of Harbitros

  • HEA Seal Harbian Eclipse Agency

Suvion Order flag updated Suvion Order of Collectivism

Commanders
  • HEA Seal Seth Baxter
  • HEA Seal Trey Gregory
  • Suvion Order flag updated Ricky Plyes
  • Suvion Order flag updated Amanda Wiles
Strength

Harbian Eclipse Agency

  • 120 operatives
  • 3 helicopters

Suvion Order

  • 640 members
Casualties

1 (5 wounded)

est. 600

The Siege

On Nahvidax'k'ver VII, a taskforce of agents and operatives from the Harbian Eclipse Agency traveled to Desmoth, Renshaw, to siege a compound full of supposed communists by the name of the Suvion Order of Collectivism. When Amanda Wiles, a ranking member of the order, refused to open the Arme Selax Compound's doors to the agents, they retaliated by firing detonating the front door. Immediately, the agents were met by gunfire from the collectivists. A large firefight broke out around the compound, with agents and cultists firing at eachother. During the chaos, an HEA helicopter mistook orders and fired several napalm-filled rockets onto the roof of the compound, immediately setting it ablaze. By the end of the battle, over 600 Suvion members had died either from burning alive or being shot by agents. In juxtapose, only one agent was killed and five were wounded. The remaining Suvion collectivists were incarcerated. 

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.