I am working on a large project and we are working on quests now and that means when new scripts get created I need to pack them into a .bsa file with BSAopt.

When I try and edit the scripts I just get a big
instead of a script. The original .psc is in the .bsa.


Could it have something to do with the fact that we are using Version Control? I merge the changes my team makes to the mod into a master .esm file.
Or do I have to do that thing that people are doing with dawnguard? Where you have to add the .bsa file to some config list or something(i've heard)

That happens to me too, still haven't got an answer

The assets have to be loose. The CK doesn't auto-load BSAs by virtue of nomenclature like TESV.exe does.

I think I already tried that before. Let me try it again.

Yup. I extracted all the .psc files in the mod into the scripts/source folder. I opened up the mod and tried opening up a quest and looking at some of the scripts assigned to the quest and they all still say ";CODE NOT LOADED"

Have said PSC's been compiled? You'll need the loose PEX files as well.

Hmm that seems to fix the problem.

There is still a problem because half the scripts are still not there but I'm assuming that's just my fault. Thank you!

Glad things are sorting themselves out I'd imagine when all the PEX files are present, all will load, but you might need to reload the plugin first.