Samustus

Did you resolve this? All I can suggest is to check that 'ia_class7_087.tga', 'PMBF87.tga', 'PMBF87.txi' and the UTI file are in your override folder. Also make sure that Bao-Dur is part of your group, save the game, and THEN edit the save file. Editing/changing NPC stats and gear when they are outside your current group will require changing a different section in the editor. If it's still not working, try my personal version attached. NOTE: The attached version has dialog removed and will require an editor to give it to Bao-Dur. Bao-Dur's Charged Armor Fixed - Editor Version.7z

Sorry for the late reply. Haven't been around. For those having probs with the dialog, you can remove the dialog entirely when installing the armor and add the armor manually using the editor. Follow my previous instructions, except this time there are different line changes. ------------------ Under the Header "[install_folder0]", Delete/Change the lines to look like the following (only three lines under the Header): File0=ia_class7_087.tga File1=PMBF87.tga File2=PMBF87.txi Save and install. ------------------ All this does now is add the armor to the games' item list. There is no dialog and no autoequip. Once the mod is installed you have to add it manually to BaoDur using a save game editor. Hope this helps.

It's called "Bao_Charged_Armor" and should be at the end of the list after installing.

Got a problem with the Mandalorians appearing see-through after installing this. A shame really, looks great in the picture.

Well.. I found the problem.. and it's really simple! If you can do a fresh install of this mod and return 'baseitems.2da' to how it was prior to installing this mod (from the backup folder), then read on. If not, and you've installed other mods that change 'baseitems.2da' and it will be too much hassle, then follow the instructions I wrote previously. What the problem is, is that the patcher tries to install 'bao_armor.uti' twice and gets an error and skips the .uti alteration. What you need to is actually very easy. Assuming this mod is completely removed from your override folder and the 'baseitems.2da' has no reference to the charged armor, then do the following: 1/ Unpack the mod and go into the 'tslpatchdata' folder. 2/ Open 'changes.ini' 3/ Scroll down and find the section '[install_folder0]'. 4/ Find the line 'File3=bao_armor.uti' and delete it completely. 5/ Renumber the next two lines to file 3 and 4 e.g.'File3=231bdur.dlg' and 'File4=equip_bcarmor.ncs'. 6/ That's it, you're done. Save 'changes.ini'. Install the mod. Now the patcher should install 'bao_armor.uti' and alter it to match the row number in 'baseitems.2da'. A single line caused so much hassle. Oh well. Good luck.

First of all I want to say thanks for all your hard work. Really enjoyed a play through with all your changes. Couple of things to note when playing, however. The Circlet of Saresh was changed to some heavy armor for some reason. Also, on Korriban in the final tomb in the caves trial, when opening the tomb I got 16 (yes 16) 'shroud' armors LOL. Two sets of 8. I forget the exact name other than it had shroud in it, sorry, but it made me laugh so it's not all bad I think there were a couple of other non armor items changed to armors too, but alas I uninstalled without writing it down. Apart from that, I really liked what you did. Appreciated!

If you're having problems with this, such as crashing when Bao-dur tries to put the armor on, it's because your game has an issue with "bao_armor.uti". 1. Install the mod and then using Kotor Tool, open 'baseitems.2da' and make a note of the 'Row Label' for the charged armor (last in list after installing). The row is 109 in the original .uti file in the mods 'tslpatchdata' folder. If it doesn't match, then that's your problem and you need to edit the .uti file. 2. Using a GFF editor (not Kotor Tool - doesn't seem to like it) open 'bao_armor.uti' in your Override folder and change 109 to whatever number you noted previously. Make sure the number is changed and then save overwrite. It should work now. I thought the TSLpatcher had facilities to accommodate these sorts of issues, but then again I don't know much about the patcher. Hope someone fixes this. Anyway. Hope this helps someone