Forums > Senate Hall archive > SH Archive/Battle of Nar Shadaa in 3,951 BBY

I've had a recent thought while replaying KOTOR II for like the hundredth time, shouldn't we add a Battle of Nar Shaddaa during this time period? I mean, when the Exile leaves GO-TO's yacht, a space battle is clearly being played out in the cut scene and NPC's on Nar Shadaa clearly are in disbelief that the Republic had attacked the Exchange, so again I ask, shouldn't we add a page about a battle over Nar Shaddaa in 3,951 BBY? RushinSundaws 14:07, 11 August 2006 (UTC)

  • Do we know enough about it to write a factual and speculation-free article? If yes, go ahead. I don't agree with it that it should be called a "battle", but you know more about it than me, so I let it up to you to decide if that qualifies as a battle. - TopAce 17:54, 11 August 2006 (UTC)
    • I guess it wouldn't actually be a battle, but there clearly is some kind of skirmish going on in the background, I'd say it would probably be better qualified as a skirmish or minor conflict. Though I'm not sure who was entirely involved, the Republic and GO-TO for sure and possibly the Exchange and some bounty hunters, beyond that I'm not sure how to move on this one. RushinSundaws 18:04, 11 August 2006 (UTC)
      • For anyone and everyones warning, I added a page about this. I'm not good with battles, maybe someone can fix it up. RushinSundaws 06:58, 16 August 2006 (UTC)
        • What was the Republic's reason for firing on Goto's yaught anyway? Is that ever mentioned in the game?--Darth Oblivion 14:02, 16 August 2006 (UTC)
          • The Republic, technically, wasn't involved. Possibly the reason they might think it was the Republic was becuase the Ebon Hawk was considered to be Republic property, since the Exile was a Jedi. I really don't know why. NKSCF 00:55, 23 August 2006 (UTC)

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.