NosDdraig

Thanks, I already had Ghostwise's patch but had overlooked Bugsby's patch. Bugsby's edits in his patch largely mirrored the edits I'd been making to the Bash Patch but the Bashed Patch still steps Bugsby's patch. What I've done is be more selective in what weapon mods I'm importing stats into the Bashed Patch and that has cleaned up some of the undesirable edits. It still needs a post Bash patch to override which I'll probably create it this weekend.

I've modded Skyrim for several years now and it took me a couple weeks to realize how limited the number of BSAs is for FO3. However, once I extracted the non-DLC BSAs I was able to run DCInteriors without extracting it's BSA. Until then I could only start FO3 with DCinteriors BSA extracted which was obviously contrary to the guides recommendation. FO3 seems to have a very small finite bsa limit which was something I wasn't looking for being use to modding Skyrim. Following the CaPD guide for FO3 regarding BSAs, I didn't realize how limited FO3 is in this regard. I'm doubtful about the pathnames I'm running DCInteriors BSA unextracted and its not having a problem. I extracted four tiny BSAs to get FO3 to work with DCInteriors active - I wasn't even sure why the mod authors didn't just go with loose files. I'm not sure how Mod Organizer handles the collection of BSA as a whole when loading the FO3 into memory but given that limit for the sum of characters for all of the BSA is apparently 255. I'd guess it's related to the fact the Windows operating system limits file names to 255 characters. Taking a wild guess, I'm guessing the BSA titles are concatenated together in some fashion to be used as label for some file that Mod Organizer uses for handling the BSAs hence the character limit. My policy is to always remove such subrecords. I'm new to modding FO3 but I've run heavily modded Skyrim setups with 300+ esps before merging. What I've found is that if this occurs that one of two things typically has occurred either Skyrim fails to launch or CTD during gameplay - either way the problem is fixed by removing the offending subrecord. I have fixed a couple of this error by pointing it to the right location but its not that easy typically. For instance, it will have a dependency on some other mod which has been since updated and not containing that subrecord anymore resulting in a bad reference. Has anyone else been having problems with BASH reverting weapon damage back to vanilla values form FWE values? I've haven't seen it mentioned on this thread and was wondering if I'm missing something. I been using FO3Edit to revert them back in the BASH patch. I'll create a BASH Override patch eventually once I've settled on a stable load order.