Jump to content

ANOTHER Nar Shaddah Bug


Recommended Posts

I'm about half way through Nar Shaddah (The only place I havn't visited being The Docks) and I encountered a pretty big bug. I already completed the Red Eclipse part where they take over the Ebon Hawk and yet when I try to enter the docks the cutscene comes up again! I found around 3 troops near the entrance to the EH dock but nothing directly around it or inside it. And no matter what I do theres noone to talk too and the EH functions like as if the Red Eclipse were present on the vessel. What do I do?

Link to comment
Share on other sites

This bug occurs when you play with the Restored Content mod...

 

They had this bright idea to add triggers for the Red Eclipse quest all over the Nar Shaddaa Landing Pad instead of just one at the exit of the Refugee Sector...

As a result, the quest will re-trigger each time you hit one of those spots... (don't get near the swoop tracks)

 

First, one way to totally avoid this is to download the *latest* version of the restored content mod (1.7), in which this particular bug has been fixed: http://deadlystream.com/forum/showthread.php?t=240 (won't be compatible with your current save, though)

 

Now, the only way to fix this problem if you have it is to edit you save with the KSE... DO NOT ENTER THE EBON HAWK once the bug is in effect .

 

Under Globals > Numerics > locate the line "351Nar_Bounty_Board" and change the 0 to 1.

and also 301Nar_Red_Eclipse_At should be at 0. Apply/commit change

 

(always make a second back-up save every time you use the KSE)

Edited by Togruta
Link to comment
Share on other sites

What I did with the savegame editor didn't do anything. The cutscene still triggers.

 

It's not supposed to prevent the cutscene from triggering. You can't prevent the bug, you can only fix it.

 

Once the cutscene has triggered, save/quit without ever boarding the Ebon Hawk, and then perform the edit... The EH will no longer be under lockdown and all will be back to normal...

Edited by Togruta
Link to comment
Share on other sites

Alternatively, just update to 1.7, the latest TSLRCM release.

It doesn't have this 1.6 issue.

^

 

 

I agree that that is such a stupid idiotic pathetic garbage hateful retarded scumbag evil satanic nazi like term ever created. At least top 5.

 

TSLRCM Official Forum || TSLRCM Moddb || My other KOTOR2 mods || TSLRCM (English version) on Steam || [M4-78EP on Steam

Formerly known as BattleWookiee/BattleCookiee

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...